INTEGRATING QA IN PROJECT LIFE CYCLE

1. INTEGRATING QA IN PROJECT LIFE CYCLE

2. Software Development Methodologies • A Project Manager is the one who thinks 9 women can deliver a baby in 1 month. • An Onsite Coordinator is the one who thinks 1 woman can deliver 9 babies in 1 month. • A Developer is the one who thinks it will take 18 months to deliver 1 baby. • A Marketing Manager is the one who thinks he can deliver a baby even if no man and woman are available. • A Client is the one who doesn’t know why he wants a baby. • A Tester is the one who always tells his wife that this is not the right baby.

3. Software Development Methodologies • Waterfall Model (SDLC) • Object Oriented Model • Spiral Model • Prototyping Model

4. Software Development Methodologies • Waterfall Model (SDLC)

5. Software Development Methodologies • Object Oriented Model

6. Software Development Methodologies • Spiral Model

7. Software Development Methodologies • Prototyping Model (SDLC)

8. Software Development Methodologies • Activity of QA in Development Process • Quality assurance planners for a project are required to determine: ■ The list of quality assurance activities needed for a project. ■ For each quality assurance activity: –Timing –Type of quality assurance activity to be applied –Who performs the activity and the resources required. It should be noted that various bodies may participate in the performance of quality assurance activities: development team and department staff members together with independent bodies such as external quality assurance team members or consultants –Resources required for removal of defects and introduction of changes.

9. Software Development Methodologies • Verification, Validation and Qualification • Verification – The process of evaluating a system or component to determine whether the products of a given development phase satisfy the conditions imposed at the start of that phase • Validation – The process of evaluating a system or component during or at the end of the development process to determine whether it satisfies specified requirements (Compliance). • Qualification – The process used to determine whether a system or component is suitable for operational use • Did We Built the System Right? • Did We Built the Right System?

10. Software Development Methodologies • SQA Defect Removal Model • The model deals with two quantitative aspects of an SQA plan consisting of several defect detection activities: • (1)The plan’s total effectiveness in removing project defects. • (2)The total costs of removal of project defects. • Defect Origins Table

11. Software Development Methodologies • SQA Defect Removal Model • Cost of Defect Removal

12. Software Development Methodologies • SQA Defect Removal Model • Average Relative Defect Cost

13. Software Development Methodologies • Model • The model is based on the following assumptions: ■ The development process is linear and sequential, following the waterfall model. ■ A number of “new” defects are introduced in each development phase. Lihattabel Defect Origin ■ Review and test software quality assurance activities serve as filters, removing a percentage of the entering defects and letting the rest pass to the next development phase. For example, if the number of incoming defects is 30, and the filtering efficiency is 60%, then 18 defects will be removed, while 12 defects will remain and pass to be detected by the next quality assurance activity. Untuk cost dari Defect Removal lihat Cost of Defect Removal Model. ■ At each phase, the incoming defects are the sum of defects not removed by the former quality assurance activity together with the “new” defects introduced (created) in the current development phase. ■ The cost of defect removal is calculated for each quality assurance activity by multiplying the number of defects removed by the relative cost of removing a defect (Tabel Average Relative Defect Cost). ■ The remaining defects, unfortunately passed to the customer, will be detected by him or her. In these circumstances, full removal entails the heaviest of defect-removal costs.

14. Software Development Methodologies • Model • Penghitungan Model: POD = Phase Originated Defects (from Table 7.3) PD = Passed Defects (from former phase or former quality assurance activity) %FE = % of Filtering Effectiveness (also termed % screening effective- ness) (from Table 7.4) RD = Removed Defects CDR = Cost of Defect Removal (from Table 7.5) TRC = Total Removal Cost: TRC = RD × CDR.

15. Software Development Methodologies • Model • Penghitungan Model:

16. Software Development Methodologies • Model • Latihan:

17. Software Development Methodologies • Model • Latihan: • Tentukan TRC padamasing-masingfase! • Fase Requirement Specification POD = 15, PD = 0, • Fase Design POD = 35, • Fase Unit Test POD = 30, • Fase Integration Test POD = 10, • Fase Documentation POD= 10, • Fase System Test POD = 0, • Fase Operation POD = 0

18. Software Development Methodologies • Model • Latihan: Comprehensive Plan

19. Software Development Methodologies • Model • Latihan: • Fase Requirement Specification POD = 15, PD = 0, • Fase Design Inspection POD = 35, • Fase Design Review POD = 0, • Fase Code Inspection POD = 30, • Fase Unit Test POD = 0, • Fase Integration Test POD = 10, • Fase Documentation POD= 10, • Fase System Test POD = 0, • Fase Operation POD = 0

20. Software Development Methodologies • Model • Bandingkanke-dua Model tersebut!