Developing Software Quality Plans a Ten Step Process. Phil Robinson Lonsdale Systems. Software Quality Plans. We all agree that you need one

Size: px

Start display at page:

Download "Developing Software Quality Plans a Ten Step Process. Phil Robinson Lonsdale Systems. Software Quality Plans. We all agree that you need one"

Jade Franklin
6 years ago
Views:

1 ing Quality Plans a Ten Step Process Phil Robinson Lonsdale Systems lonsdale@iinet.net.au Quality Plans We all agree that you need one but What do you put in them? How do you develop one? This ten-step process Cook book approach Risk driven Basic quality improvement techniques Easy to customise 1

2 1. Work Products Work Products ment Process Work Products 2

3 A Simple ment Process System Component Implementation Construction Detailed Design Specification Changes Operation Design Analysis Architectural Design Specification Specification Analysis is different because requirements are not known Work products must be defined as part of the process There is nothing to verify requirements against After analysis, work products are defined As part of the process By requirements 3

4 2. Work Product Creation Work Product Creation ment Process Work Products Work Product Creation 4

5 Work Breakdown Structure (WBS) Sub-System Component C Component D Design Component C Code Component C Design Component D Code Component D 3. Project Risks 5

Project Risks ment Process Work Products Work Product Creation Risk Factors Project Risks Risk Factors Users ers Product Level of planned user participation in definition of requirements Possibility

6 Project Risks ment Process Work Products Work Product Creation Risk Factors Project Risks Risk Factors Users ers Product Level of planned user participation in definition of requirements Possibility of user requested program User s design view changes Level of of user quality experience with the application area of the project Contribution to end-user efficiency Degree in which software is to facilitate business process change Training requirements er experience and qualifications Level of previous experience with development environment Level of previous experience with an application of similar or greater size and complexity Ratio of staff to duration of the project er s Schedule slip view Cost overrun of quality Resource availability Life-cycle products not available when required Degree of user interface complexity Level of security require programs and data Number and type of com time and resource (disk memory etc.) constraint Degree of data communications involve Amount of distributed functionality (e.g. client- Level of performance re Level Product of transaction rate Complexity view of business Number of quality and type of mathematical calculatio Required ease of install Number and type of inte to other applications 6

7 Risk Dimensions Likelihood Impact High Impact Low Likelihood High Likelihood Low Impact Quantifying Likelihood 1 Improbable 3 Probable 9 Very Likely Low Likelihood High Likelihood 7

8 9 Catastrophic High Impact Quantifying Impact 3 Critical 1 Marginal Low Impact Quantifying Risk Risk Score = Likelihood + Impact Score 6, 8 or 10 High Impact Score 13 or 18 Low Likelihood High Likelihood Score 2 Low Impact Score 6, 8 or 10 8

9 4. Risk Impact on Work Product Quality Risk Impact on Work Product Quality ment Process Work Products Work Product Creation Quality Model Risk Impact on Work Product Quality Risk Factors Project Risks 9

10 Quality Model Functionality Portability Reliability ISO9126 Maintainability Usability Efficiency Risk Impact on Product Quality Risk Factors Relative Importance Suitability Characteristics Functionality Reliability Usability Efficency Ma Accuracy Users unable to define requirements due to a lack of experience with Relative electronic funds transfer. importance of System will not support new business characteristic processes in an efficent manner Interoperability Compliance Security Matruity Fault Tolerance Recoverability Relative importance of risk factor Understandibility Learnability Operability Time Behaviour Resource Behaviour Analysability Transaction rate will not be achieved. System cannot be recovered within an acceptable time frame. Unathorised access to the system to illegally transfer funds. Training will take longer than planned INFLUENCE High 3 3 Medium Low

11 5. Quality Strategy Quality Strategy ment Process Work Products Work Product Creation Quality Model Risk Impact on Work Product Quality Risk Factors Project Risks Quality Improvement Techniques Quality Strategy 11

12 Quality Improvement Techniques Early requirements validation Inspection Test Configuration management Early Validation Product and process redundancy Joint Applications ment (JAD) Quality Function Deployment (QFD) Prototyping 12

13 Work Products and Quality Improvement Techniques Early Validation Inspection Test Specification Architectural Design Specification Detailed Design Specification Component System Configuration Management Risk Reduction Framework Portability Maintainability Efficiency Useability Reliability Functionality Analysis Design Construction Implementation Early Validation Inspection Configuration Management Testing 13

14 Risk Reduction Framework Portability Risk Reliability Functionality Analysis Maintainability Efficiency Useability Acceptable Risk Allocated Budget Design Process Construction Implementation Early Validation Inspection Configuration Management Testing Quality Improvement Technique 6. Quality Products 14

15 Quality Products ment Process Work Products Work Product Creation Quality Model Risk Impact on Work Product Quality Risk Factors Project Risks Quality Improvement Techniques Quality Strategy Quality Products Quality Products Plans Specifications Records JAD session plans QFD session Plan plans Prototype plans Inspection plans Review plans Audit plans Test plans Redundant analysis products Inspection process Inspection completion criteria Test case Specify Functional Structural Error Guess Test procedure Outcomes of JAD sessions Outcomes of QFD sessions Outcomes of prototypes Outcomes of inspections Outcomes of reviews Outcome of audits Outcomes of tests Problem reports Record 15

16 7. Quality Product Creation Quality Product Creation ment Process Work Products Work Product Creation Quality Model Risk Impact on Work Product Quality Risk Factors Project Risks Quality Improvement Techniques Quality Strategy Quality Products Quality Product Creation 16

17 Generic Quality Check for Completion Record Plan Execute Specify Plan This is it! Completion criteria Coverage Statistical models Iterative Stop when completion criteria are satisfied Quality Added to the WBS Sub-System Component C Design Component C Code Component C Unit Test Inspect Design Inspect Code 17

18 8. Configuration Management Configuration Management ment Process Quality Strategy Work Products Quality Products Configuration Management 18

19 Configuration Management Added to the WBS Sub-System Component C Release Sub-System Design Component C Code Component C Unit Test Inspect Design Inspect Code Release Component 9. Estimate Effort 19

20 Estimate Effort Work Product Creation Quality Product Creation Estimate Effort Configuration Management Estimating Approaches Work Products Product metrics Function Point Analysis Quality Coverage Statistical models Configuration Management Count of work products Statistical models 20

21 10. Project Schedule Project Schedule Work Product Creation Quality Product Creation Estimate Effort Project Schedule Configuration Management 21

22 Project Schedule Calendars ID Task Name Duration 1 Sub-System 15.5 days 2 Component C 8.5 days 3 Design Component C 2 days 4 Inspect Design 0.5 days 5 Code Component C 3 days 6 Inspect Code 0.5 days 7 Unit Test 2 days 8 Relese Component 0.5 days 9 Component D 15 days 10 Design Component D 4 days 11 Inspect Design 0.5 days 12 Code Component D 6 days 13 Inspect Code 1 day 14 Unit Test 3 days 15 Relese Component 0.5 days Resources 16 Release Sub-System 0.5 days 14 May '01 21 May '01 28 May '01 04 Jun '01 S S M T W T F S S M T W T F S S M T W T F S S M T W Designer Designer Designer Designer Programmer Programmer Tester Configuration Manager Schedule Programmer Programmer Tester Configuration M Configu Questions? 22

23 Phil Robinson Lonsdale Systems 23

International Standard ISO/IEC 9126

International Standard ISO/IEC 9126 Software Engineering Product quality Part 1: Quality model ISO 9126 - Content Product quality and the lifecycle Quality models for: Internal Quality, External Quality