1.13. Putting it All Together (Key Points)
Discussed the elusive nature of quality, especially in the context of software.
Attempted to define quality and highlighted the fact that quality is an attribute “of something” and therefore cannot be defined on its own, without a context.
Defined what is quality assurance and how it differs from testing or quality control.
Defined the four different priorities vying against each other in a project: budget, time, functionality, and quality. Of these four, quality is the least measurable and most elusive. Therefore, it tends to get thrown out when pressure is applied by budget, time, functionality, or their combination.
Defined the six different levels of quality within a software project: data quality, code ...
Get Process Quality Assurance for UML-Based Projects now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
