Successful software depends not only on technical excellence but on how members of the software team work together. Written in easy to understand language by a leading expert in the field, this ground-breaking volume provides an overview of the team culture required to develop quality software. Reflecting the different views on the nature of software quality, the book helps groups in a software team to communicate more effectively and to overcome the conflict created by their different perceptions of quality. You learn the roles and activities of team members (including customers) throughout the life of a software product, from before the software development starts and during the software development lifecycle, to after the software has been deployed and is in use. Achieving Software Quality through Teamworkdescribes popular software quality models such as EFQM, Watts Humphreys' personal and team software processes, TMAP and CMM. It features numerous examples, sources for further information, and tools and techniques that can be applied to real projects. An indispensable resource for software developers, testers, managers, quality assurance professionals, and customers, the book explains how to clear the way through difficult people issuesù so that software quality can be achieved. Defining the key groups within a software team and their different definitions of quality, this unique reference enables you to improve the communications and relationships between team members throughout a project and the lifetime of the software.
Introduction.; Software Quality Matters - Defining Software Quality. Fundamental Concepts of Excellence. EFQM Model. ISO9000:1994 and ISO9000:2000. IT Maturity Models - CMM and Relations. Team Software Process and Personal Software Process. Bringing the Models Together.; Defining the Software Team - Teams in Disunity. Defining the Team. Interaction Between the Groups and Within Each Group.; Roles and Quality: Customers - Introducing the Customers. Who Could Be in This Group. Quality Viewpoint. Quality Framework. Enablers for the Customers. Results for the Customers. Life Cycle Activities. Summary of the Group.; Roles and Quality: Managers - Introducing the Managers. Who Could Be in This Group. Quality Viewpoint. Quality Framework. Enablers for the Managers. Results for the Managers. Life Cycle Activities. Summary of the Group.; Roles and quality: Builders - Introducing the Builders. Who could be in This Group. Quality Viewpoint. Quality Framework. Enablers for the Builders. Results for the Builders. Life Cycle Activities. Summary of the Group.; Roles and quality: Measurers - Introducing the Measurers. Who could be in This Group. ; Quality Viewpoint. Quality Framework. Enablers for the Measurers. Results for the Measurers. Life Cycle Activities. Summary of the Group.; Roles and quality: Supporters - Introducing the Supporters. Who could be in This Group. Quality Viewpoint. Quality Framework. Enablers for the Supporters. Results for the Supporters. Life Cycle Activities. Summary of the Group.; The Lifespan of a Software System - Lifespan or Life Cycle. Entry and Exit Criteria Between Stages. Changes in Quality Viewpoints Across the Lifespan of a System.; Start-up for a Software Development - Start-up: description. Start-up Viewpoints. Entry Criteria for Start-up. Start-up: Typical Activities. Exit From Start-up Stage.; Software Development Life Cycle (SDLC) - SDLC Description. SDLC Viewpoints. Entry Criteria for SDLC. SDLC: typical activities. Entry and Exit Points Within the SDLC. SDLC Models. Quality Views and the Models - Why Combine Models. Exit From the SDLC. Conclusion.; Delivery and Point-of-Live Support - Delivery: description. Delivery Viewpoints. Entry Criteria for Delivery. Delivery : Typical Activities. Exit From Delivery. Conclusion.; The Life of a System Post Delivery - Post delivery: description. Delivery Viewpoints. Entry Criteria for Post Delivery. Post Delivery: Typical Activities. Exit From Post Delivery. Conclusion.; Appendices - Tools and Techniques. Organizations, Sources and References. Skeleton Documents, Forms and Outlines.;
-
Isabel Evans
Isabel Evans is currently an independent training provision and quality improvement consultant. She has nearly 20 years experience in the IT industry, specializing in quality management, testing, training and documentation. She has aided organizations in the development of standards, methods and procedures to support testing of software during development and maintenance projects. She has also provided quality assurance support, release management, and customer support for IT organizations and has published extensively.