Testing and analysis activities occur throughout the development and evolution of software systems, from early in requirements engineering through delivery and subsequent evolution. Quality depends on every part of the software process, not only on software analysis and testing; no amount of testing and analysis can make up for poor quality arising from other activities. | Test and Analysis Activities within a Software Process (c) 2007 Mauro Pezzè & Michal Young Ch 4, slide 1 Learning objectives • Understand the role of quality is the development process • Build an overall picture of the quality process • Identify the main characteristics of a quality process – visibility – anticipation of activities – feedback (c) 2007 Mauro Pezzè & Michal Young Ch 4, slide 2 Software Qualities and Process • Qualities cannot be added after development – Quality results from a set of inter-dependent activities – Analysis and testing are crucial but far from sufficient. • Testing is not a phase, but a lifestyle – Testing and analysis activities occur from early in requirements engineering through delivery and subsequent evolution. – Quality depends on every part of the software process • An essential feature of software processes is that software test and analysis is thoroughly integrated and not an afterthought (c) 2007 Mauro Pezzè & Michal Young Ch 4, slide 3 The Quality Process • Quality process: set of activities and responsibilities – focused primarily on ensuring adequate dependability – concerned with project schedule or with product usability • The quality process provides a framework for – selecting and arranging activities – considering interactions and trade-offs with other important goals. (c) 2007 Mauro Pezzè & Michal Young Ch 4, slide 4 Interactions and tradeoffs example high dependability vs. time to market • Mass market products: – better to achieve a reasonably high degree of dependability on a tight schedule than to achieve ultra-high dependability on a much longer schedule • Critical medical devices: – better to achieve ultra-high dependability on a much longer schedule than a reasonably high degree of dependability on a tight schedule (c) 2007 Mauro Pezzè & Michal Young Ch 4, slide .
