12-CRS-0106 REVISED 8 FEB 2013 Software Quality Assurance by: tim pengajar RPL 1

12-CRS-0106 REVISED 8 FEB 2013 What is Quality ? “Quality is the relationship between what client expected and what we got.” 2

12-CRS-0106 REVISED 8 FEB 2013 Quality could be free ? Specifications DesignCodeTest Release Cost to fix a bug Rp 1,- Rp 10,- Rp 100,- Rp 1000+,- Time when bug is found 3

12-CRS-0106 REVISED 8 FEB 2013 SW Testers vs SW QAers SW Tester : –Not responsible for the quality of software –Just finding bugs.... Find them as early as possible, and make sure they got fixed SW QAers : –Preventing bugs from ever occuring –Examine and measure the current software development process –Finding ways to improve it.. –Responsible for the quality of software 4

12-CRS-0106 REVISED 8 FEB 2013 Example of quality assurance 5

12-CRS-0106 REVISED 8 FEB 2013 Test management and organizational structures (small project) Development Manager TestersProgrammers 6

12-CRS-0106 REVISED 8 FEB 2013 Test management and organizational structures (medium project) Project Manager Test Manager/Test Lead Testers Development Manager Programmers 7

12-CRS-0106 REVISED 8 FEB 2013 Test management and organizational structures (professional organization) Executive Manager Project Managers QA / Test Managers QAers Testers Development Manager Programmers 8

12-CRS-0106 REVISED 8 FEB 2013 Standards related to software quality 9

12-CRS-0106 REVISED 8 FEB

12-CRS-0106 REVISED 8 FEB 2013 Capability Maturity Model Integration (CMMI) CMM LEVELDEFINITIONWhen To Use Level 1: ChaosLittle documentation and few if any processes and procedures are in place. Success is only achieved by the heroic actions of team members. Used for one of a kind projects of very limited scope. Level 2 – Repeatability Enough documentation exists that the QA process is repeatable. Used for any project that will be done again, whether as an upgrade or a somewhat similar variation. Level 3 - Standardization QA documentation and processes & procedures are standardized. Templates exist for all documentation and a QA "system" exists. Critical for a QA department that must provide QA for multiple projects. Avoids reinventing the wheel for each project. Level 4 - Manageability The exact time & resources required to provide adequate QA for each product is known Precisely Requires an existing data set based on previous QA projects. Level 5 – Optimization QA processes and procedures are understood well enough to be refined and streamlined. Actually should be used in every Stage. By Level 5, this is the only thing left to work on. 11

12-CRS-0106 REVISED 8 FEB 2013 Thank you 12