Professional Documents
Culture Documents
The Uniqueness of Software Quality Assurance - The Environments For Which SQA Methods
The Uniqueness of Software Quality Assurance - The Environments For Which SQA Methods
• High complexity
– The potential ways in which a software product can be used with different
data / data paths reflecting different incoming data is almost infinite.
– Manner in which industrial products can be used are usually well-defined.
– Think about software: every loop with different values of data reflects a
different opportunity to see software fail.
• Product Development:
– Industrial: test product; voltages; performance; strength; size; ….ready to distribute
to markets
– Computer Software: once prototype and system testing are concluded, product is ready
for deployment
• About the same approach
• Arguable: equal chance to discover defects?
– What do YOU think??
Product Manufacturing:
– Industrial: Usually defects uncovered here; easily fixed.
• Typical burn-in problems; another view of product; stabilizes.
• These represent additional opportunities to discover defects.
– Computer Software:
• We merely copyright, print copies of software and manuals
• No real chance for additional quality views
• No real chance for discovering additional defects
• “The need for special tools and methods for the software industry is
reflected in the professional publications as well in special standards
devoted to SQA, such as ISO 9000-3, “Guidelines for the application of
ISO 9001 to the development, supply, and maintenance of software.”
• Another: ISO 9004-2: “Quality Management and Quality Systems
Elements: Guidelines for the Services.”
• Being contracted
• Subjection to customer-supplier relationship
• Requirement for teamwork
• Need for cooperation and coordination with other
development teams
• Need for interfaces with other software systems
• Need to continue carrying out a project while the team
changes
• Need to continue maintaining the software system for years
Attendance
control
system