220 likes | 382 Views
Monitoring and Managing Software Quality with Requirements Coverage. TURGAY KOKLU IPEK KOSE SERKAN AKOGLANOGLU. WHO ARE WE ?. TURKCELL SOFTWARE TESTING TEAM @ NETWORK INFORMATION SYSTEMS. Agenda. Do you have auto insurance?. What type of coverage do you have?.
E N D
Monitoring and Managing Software Quality with Requirements Coverage TURGAY KOKLU IPEK KOSE SERKAN AKOGLANOGLU
WHO ARE WE ? TURKCELL SOFTWARE TESTING TEAM @ NETWORK INFORMATION SYSTEMS
Do you have auto insurance? What type of coverage do you have? • LIABILITY COVERAGE (LIABILITY) • PROPERTY DAMAGE LIABILITY (PD) • COLLISION COVERAGE (COLL) Is your coverage Good Enough? What is your Risk Factor? • Covers other people's bodily injuries ONLY • Covers damage to your car ONLY • Covers your vehicle, and other vehicles • Covers you if your car damages someone else's property. • Covers you, and your passengers
Requirement Coverage Requirement coverage ensures that the software architecture, design and test plan meets the expected necessities Analysis Test Architecture Business requirements Acceptance tests Architectural requirements SystemFramework Smoke tests Functional tests Regrssions tests Integration tests Operational requirements Functional requirements Operation Development Performance & Load criterias Design Artifacts*
Case Study System Interruption Needs Publish a bulletin System Maintenance
Requirement mapping UseCase Requirements for 1 Use case Testcases for 1 requirement Create a bulletin Define interruption start date Create a bulletin Define interruption start date NULL start date Update a bulletin interruption end date end date interruption end date end date Delete a bulletin Send bulletin Entering past date
Why requirement coverage is important ? • Manage requirement changes • Provide integrated execution statuses
Why requirement coverage is important ? Offer Enhanced Release Decision
Case Study System Interruption Needs Publish a bulletin System Maintenance
Coverage Views Total number of requirements: 290
Traditional Mapping Test case Requirement
Effective Mapping Test case broken down by requirements Requirements re-mapped
Conclusion • Integrated execution statuses • Enhanced release decision • Monitoring and managing changes on time • Effective testing • Catching defects early • Reduction on production defects
Thank you all Questions