Quality Exercise 2 Instructions Quality Analysis The current

Quality Exercise 2 Instructions Quality Analysis The current software upgrade project has been in progress for a year now and the project should be well into the Coding and Unit Testing phase. The PM believes that something is amiss and has asked your IPT to perform an in-depth analysis to assess the project’s status from a quality perspective. The PM received from the prime contractor the measurement indicators (without any additional comments or information) and has given them to your IPT to analyze (see Contractor Data Presented to PM). The PM has also identified the program’s specific Quality Attributes and is concerned that the data does not allow for a good quality assessment. The PM wants your IPT to complete the enclosed assessment templates. Tasks: Within your IPT, review carefully the set of charts to identify problems, assess their impact, project the outcomes, and evaluate alternatives. 1. Compare/contrast the PM’s Quality Attributes with the Software Quality Model Characteristics (ISO 9126 -1 : 2001 Software engineering) presented in the lesson material and identify any areas you feel the PM should address. 2. Compare and contrast the ICM Quality measurable concepts (with indicators and measures) from Exercise 1 with the PM’s Quality Attributes. Identify the differences between the ICM table and the PM’s Quality Attributes. 3. Assess the data provided by the contractor - does the data provided meet information needs based on the PM’s Quality Attributes? If not, identify the areas where you need additional data to support the PM’s Quality Attributes. (Note: Each team will focus on one Quality Attribute area - Team 1 = Attribute 1, etc) 4. What recommendations would you make to the PM based on the insight gained from your analysis? Be sure to include recommendations for strengthening the overall SW quality program. What additional analyses you would perform to assess and strengthen the SW Quality activities.

PM Quality Attributes 1. Quality Attribute: Interoperability Attribute Concerns A. Ease of interfacing with using applications B. Ease of interfacing with other systems 2. Quality Attribute: Adaptability Attribute Concerns A. Ability to accommodate new requirements B. Ability to accommodate new technologies C. Ability to field a subset of the current requirements (functionality) D. Ability to support various platforms 3. Quality Attribute: Maintainability Attribute Concerns A. Ability to accommodate new technologies B. Ability to support isolation of faults C. Minimize training for maintainers 4. Quality Attribute: Modularity Attribute Concerns A. Replace an architectural component B. Loose coupling/high cohesion C. Design from a common set of components 5. Quality Attribute: Usability Attribute Concerns A. Minimize user training (operator, user, non-signal user) B. Enable user to perform tasks in allocated time. C. Minimize number of operators. D. Consistent GUI (common look and feel)

Quality Exercise 2 Answer Template Performance Analysis Worksheet 1. Compare/contrast the PM’s Quality Attributes with the Software Quality Model Characteristics (ISO 9126 -1 : 2001 Software engineering) presented in the lesson material and identify any areas you feel the PM should address. 2. Compare and contrast the ICM Quality measurable concepts (with indicators and measures) from Exercise 1 with the PM’s Quality Attributes. Identify the differences between the ICM table and the PM’s Quality Attributes.

Quality Exercise 2 Answer Template Performance Analysis Worksheet 3. Assess the data provided by the contractor - does the data provided meet information needs based on the PM’s Quality Attributes? If not, identify the areas where you need additional data to support the PM’s Quality Attributes. (Note: Each team will focus on one Quality Attribute area - Team 1 = Attribute 1, etc) 4. What recommendations would you make to the PM based on the insight gained from your analysis? Be sure to include recommendations for strengthening the overall SW quality program. What additional analyses you would perform to assess and strengthen the SW Quality activities.

Software Quality Model Characteristics • ISO 9126 -1 : 2001 Software engineering -- Product quality provides a SW quality model that identifies six main quality characteristics: • • • Functionality - Suitability Accurateness Interoperability Compliance Security • • Reliability - Maturity Fault tolerance Recoverability Usability - Understandability Learnability Operability • Efficiency - Time behavior Resource behavior Analyzability Maintainability - Changeability Stability Testability Adaptability Portability - Installability Conformance Replaceability Software Quality Assurance 5

Quality Exercise 1 Potential Solution Measurable Concepts and Questions Addressed Potential Indicators and Measures Priority 2 - Defect Profiles / Defect Density Technical Measurement Trends System Elements Accepted Defects by status, severity, priority, distribution, age, etc. Technical measurement requirement, target, threshold, budget, and actual System elements verified - Mean-Time-to-Failure Availability System element failures by severity, priority System element start, end times 1 - User Interface Acceptability Operator Error Trends Actions from user interface reviews Operator errors 5 - Utilization Throughput Response Time System element capacity available, used Time for function (budget, actual) 6 Maintainability - How much support does the system require? How difficult is it to support? - Interface number (unique), complexity, growth, approval rates, changes, TBD/TBR closure per plan Interface Complexity, Interface Compatibility, Lines of Code Trends Hours to restore Calendar hours and labor hours to repair Number of paths through system 4 - Interface Compliance Interfaces verified 7 Functionality Is the product good enough for delivery to the user? Are identified problems being resolved? Reliability How often is service to users interrupted? Are failure rates within acceptable bounds? Usability Is the user interface adequate and appropriate for operations? Are operator errors within acceptable bounds? Efficiency Does the target system make efficient use of system resources? How big is and how much change is occurring with the product's functional size, content, or logical characteristics? Portability To what extent can the functionality be rehosted on different platforms? Safety and Security How many vulnerabilities are identified and remediated by lifecycle phase? How many relevant attack patterns have been covered by test cases? - - Vulnerabilities discovered, remediated - Cost to fix vulnerabilities - Test cases developed, verified per attack pattern 3