Software Quality & SQA
What is Quality
Quality mean that a product should meet its specification.
This is problematic for software systems because of:
Tension between:
Customer requirements: efficiency, reliability, etc.
Developer requirements: maintainability, reusability, etc.
Specs are often incomplete or inconsistent.
Some quality reqs are difficult to specify.
How to Create a Quality Software Product
Process and Product Quality
Product quality influenced by production process quality.
Complex relationship exists between software processes and product quality.
Quality and Standards
Standards are key for effective quality management (international, national, project levels).
Product Standards define characteristics that all components should exhibit. e.g. common programming styles
Process standards define how the software process should be enacted.
Some Causes of Software Errors
Faulty requirements
Communication failures
Logical design errors
Coding errors
Documentation Errors
What is Software Quality
Conformance to requirements
Lack of bugs
Low defect rate
High reliability (measures as Mean Time To Failure (MTTF)
IEEE defines Software Quality as the degree to which systems, components or process meets specified reqs and customer or user needs or expectations.
2 Core Terms in Software Quality
Verification: Are we building the product right? Performed at the end of a phase.
Validation: Are we building the right product? Performed at the end of dev.
Software Quality in the SDLC
Software Quality activities should be integrated into the software dev plan.
Factors Affecting Required Intensity of Software Quality Activities
Project Factors:
Magnitude
Technical complexity and difficulty
Extent of reusable software components
Severity of failure outcomes
Team Factors:
Professional qualification of team members
Team acquaintance with the project and its experience in the area
Availability of staff that can professionally support the team
Familiarity with the team members
Software Quality Assurance (SQA)
Planned systematic actions to ensure products conform to requirements.
SQA and Risk Management
Risk management is key part of the process to develop software quality. for developing software quality.
Quality is not free. Trade offs are necessary.
It involves Risk Identification, Analysis and Assessment, Planning and Mitigation and Tracking.
Can use Risk Taxonomy as a checklist to identify risk and risk mitigation activities.
Software Quality Control
Evaluates the quality and estimates if it meets customer expectations.
Includes:
Process Enforcement (independent agent, quantitative metrics, authority to act)
Process Assessment
Process Improvement Feedback
Software Metrics
Are necessary, under-used and hard.
Scope includes the process, products or resources.
SQ Goals
Defect prevention detection, and removal
Challenges in Achieving Quality
Struggles with maintaining quality levels and justifying costs.
Quality levels are often subjective, influenced by personal philosophy.
Models of SQ Factors
ISO/IEC 25010
McCall's model
Boehm's model.
Importance of SQ
Essential for avoiding defects and meeting maintainability, reliability, etc.
Standards and reviews are crucial for assessing quality.
Agile practices promote a quality culture within development teams.