Introduction to software quality

The fundamental principles of software quality management and software process improvement are discussed in detail, with a particular focus on the capability maturity model integration CMMI framework. Topics and features: includes review questions at the end of each chapter; covers both theory and practice, in addition to providing guidance on applying the theory in an industrial environment; examines all aspects of the software development process, including project planning and tracking, software lifecycles, software inspections and testing, configuration management, and software quality assurance; provides detailed coverage of software metrics and problem solving; describes SCAMPI appraisals and how they form part of the continuous improvement cycle; presents an introduction to formal methods and the Z specification language, which are important in the safety critical field; discusses UML, which is used to describe the architecture of the system; reviews the history of the field of software quality, highlighting the pioneers who made key contributions to this area.

This clearly written and easy-to-follow textbook will be invaluable to students of computer science who wish to learn how to build high-quality and reliable software on time and on budget. Software engineers, quality professionals and software managers in industry will also find the book to be a useful tool for self-study.

Get A Copy. Paperback , pages. More Details Friend Reviews. To see what your friends thought of this book, please sign up. To ask other readers questions about Introduction to Software Quality , please sign up. Be the first to ask a question about Introduction to Software Quality.

Lists with This Book. This book is not yet featured on Listopia. Add this book to your favorite list ». Community Reviews. Showing Average rating 0. This difference is due to the following reasons. It is the number of operational modes the product permits. Normally, an industrial product allows only less than a few thousand modes of operation with different combinations of its machine settings. However, software packages allow millions of operational possibilities. Hence, assuring of all these operational possibilities correctly is a major challenge to the software industry.

Since the industrial products are visible, most of its defects can be detected during the manufacturing process. Also the absence of a part in an industrial product can be easily detected in the product. However, the defects in software products which are stored on diskettes or CDs are invisible. This phase also provides opportunities to inspect the product to detect the defects that went unnoticed during the development phase.

However, in the case of software, the only phase where defects can be detected is the development phase. View an example. You need to Register an InfoQ account or Login or login to post comments. But there's so much more behind being registered.

Your message is awaiting moderation. Thank you for participating in the discussion. Very well-written whitepaper. And, the the circle that represents structural quality has arrows pointing to all people.

Do the arrows in the diagram indicate the relationships between different aspects of quality? If so, how? It is obvious that the 3 aspects of quality are related and influence one another, but I don't think the diagram intends to convey the relationship between them. An Introduction to Software Quality. Like Print Bookmarks. Apr 06, 2 min read by Abel Avram. Chappell distinguishes four attributes of this type of software quality: The software meets the specified requirements It has few defects It has reasonable performance It is easy to learn and use Structural quality measures how well the software is organized, being defined by the following attributes: Code testability Code maintainability Code understandability Code efficiency — does it manage resources efficiently?

Code security — does it prevent common security threats? Such quality defects have the following impact on the business over time, according to Chappell: Financial losses due to lost business Financial losses due to reparations needed to be performed Financial losses due to lost customers Financial losses due to legal lawsuits Brand value losses Lack of quality in internally facing software can lead to the following outcome over time: Slower user adoption Reduced business benefits More challenges for IT leaders Lower brand equity for the IT department Greater chances for outsourcing the software All three quality aspects need to be attended to — functional, structural, process — both for internally or externally facing software in order to reach a successful outcome.

Author Contacted. This content is in the Agile topic.