Sparks 3.0 - Economically Delivering Quality Software
0 likes•81 views
The document discusses the importance of delivering quality software economically, addressing various aspects of software quality such as structural, functional, and process quality through testing methods. It highlights the challenges and practices of QA within agile development, emphasizing the need for continuous integration, automated testing, and regular quality assessments. Additionally, it outlines key metrics and standards for quality assurance in software projects.
Sparks 3.0 - Economically Delivering Quality Software
- 1. Deliving Quality Software Economically Delivering Quality Software Ayaz Farooq
- 2. Risks from software defects 2010 ‘supernodes’ overloaded load testing 2017 ‘Network error’ disaster/stress testing 2005 Hartz-IV Software wrong acc number format unit testing 2011 ‘security breach’ security testing 1996 Ariane 5 integration testing
- 3. Quality Aspects during Software Development Idea Development process Sponsors Developers Users maintainability, testability, complexity, security (structural quality) (process quality) time, budget, repeatable process requirements, defect free (functional quality) performance, usability (non-functional quality)
- 4. QA Activities ● Structural quality (by static testing) ○ Static code analysis ○ Inspections and code reviews ● Functional quality (by dynamic testing) ○ Unit/integration/system testing ○ UI testing (manual/automated) ○ Load and performance testing ● Process quality (by process metrics and standards) ○ Process metrics / KPIs ○ ISO/IEC 15504 / SPICE ○ CMMI / TMMI
- 5. Quality Assurance to Quality Engineering Quality Planning Quality Assurance Activities Quality Assessment & Improvement Quality goals satisfied No Ye s
- 6. QA in Agile Development Characteristics of Agile development ● Welcome changing requirements ● Frequent releases of working software ● Short delivery cycles ● Testing integrated in development iterations Challenges of Agile development for QA ● Continuous integration (avoid integ. problems) ● Automated regression testing (avoid repeated efforts, short test time) ● Automated quality gates Analyse Design Develop Test Plan Iterate Release Iteration
- 7. QA in Agile Development Static testing Unit tests Deploy( CI) Integ/UI/Sys./Stre ss/Perf./Security tests Deploy (ED/Live) Quality gates
- 8. Continuous Integration and Testing compile & unit test static tests combine modules
Editor's Notes
- #4: Software construction is both art and science, wrong perceptions, effort on controlled/checked/improved process
- #5: How do we achieve and assess those different quality goals
- #6: Testing standards (IEEE/ISO), maturity models, test design techniques (black/white box), testing tools (static/dynamic testing, test management), defect management, test metrics for evaluation and reporting