CSE360 Lecture 26

Introduction to Software Engineering
Software Measurement III
(201807)

Transcript

1. CSE360 Introduction to Software Engineering Lecture 26: Software Measurement III Javier Gonzalez-Sanchez javiergs@asu.edu javiergs.engineering.asu.edu Office Hours: By appointment
2. Project 4 Description
3. Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 3 Problem Project 2 (diagrams) <make the ghost display a message after each answer is selected> Project 3 (code generation)
4. Software Measurement Tool
5. Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 5 Resource Standard Metrics Resource Standard Metrics is a source code metrics and quality analysis tool for ANSI C, ANSI C++, C# and Java for use on all Windows* and UNIX operating systems. 1. Download RSM 7.75 Trial (Windows) here: http://msquaredtechnologies.com/ RSM-Download.html * Install the Windows version. It includes a easy to use friendly interface (RSM Wizard).
6. Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 6 Resource Standard Metrics 2. Review the user manual here http://msquaredtechnologies.com /m2wizard/RSM_Wizard_Manual.htm Disclaimer: It is a FREE tool… Issues counting LOCs, eLOCs, Issues counting conditions (syntaxis analysis) BUT ±0..9 does not affect in biggest projects !
7. Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 7 Resource Standard Metrics
8. Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 8 Resource Standard Metrics
9. Software Measurement Example
10. Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 10 Code
11. Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 11 Numbers LOC (in) eLOC (in) lLOC (in) CC (count) CC * m1 5 3 1 3 3 m2 3 2 1 2 3 m3 12 11 10 7 7 m4 6 4 2 3 3 m5 4 3 2 2 3 main 5 5 5 1 1 Total 47 33 22 * LOC + 2 * eLOC + 1
12. Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 12 Homework 4 • Due by Wednesday July 06 • For each of your recitation projects (1,2, and 3) report the following in a table: • #Files, #methods, #lines • LOC, eLOC, lLOC, Lines of comments • % Comments %Blank lines %Spaces, % code • Max CC, Average CC • Parameters (Total, Max Parameters, Average) • Return points (Total, Max Parameters, Average) Write a conclusion in 2 or 3 paragraphs explaining the cualities of your project: positive ones and these that need improvements.
13. Test Yourselves Metrics
14. Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 14 Example Your Project 3
15. Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 15 Example Your Project 2
16. Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 16 What can you say? • Complexity of the Product • Work/Time/Payment to the team ? • Do you hire them? • Understandability of the code?
17. Test Yourselves Metrics
18. Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 18 Test Yourselves Example A • 3 files • 24 methods • 394 lines • 326 LOC • 285 eLOC • 182 lLOC • 20 Lcomments • Comments 5.1% • Blank lines 12.2% • Spaces: 21.0% (79% code) • Max CC: 6 • Average CC: 1.46 Example B • 5 files • 21 methods • 522 lines • 412 LOC • 356 eLOC • 276 lLOC • 72 Lcomments • Comments 13.8% • Blank lines 7.3% • Spaces: 26.7% (73.3% code) • Max CC: 7 • Average CC: 2.24
19. Test Yourselves Coding
20. Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 20 Example A
21. Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 21 Example B
22. Javier Gonzalez-Sanchez | CSE360 | Summer 2017 | 22 Reference Chapter 24
23. CSE360 – Introduction to Software Engineering Javier G onzalez-Sanchez javiergs@ asu.edu Sum m er 2017 Disclaim er. These slides can only be used as study m aterial for the class C SE360 at ASU. They cannot be distributed or used for another purpose.