7a. Software Quality

Quality

A characteristic or attribute of something, defined in software as quality of design, conformance, and user satisfaction.

Quality of design

Encompasses requirements, specifications, and the design of the system.

Quality of conformance

Focused primarily on implementation and ensuring the product meets specifications.

User satisfaction

Characterized by a compliant product, good quality, and delivery within budget and schedule.

Software quality

An effective software process that creates a useful product providing measurable value.

Effective software process

Establishes infrastructure supporting the building of high-quality software products.

McCall's Quality Factors

Factors that assess software quality including correctness, reliability, usability, and more.

ISO25010:2017

A standard detailing quality characteristics for software, including effectiveness, efficiency, satisfaction, and security.

Defect

A quality problem found only after the software is released to end-users.

Defect amplification

Describes how a defect introduced early can grow into multiple errors during software development.

Formal Technical Review (FTR)

A structured assessment aimed at uncovering errors and verifying that software meets requirements.

Postmortem evaluation (PME)

A mechanism to review the software engineering process to identify successes and challenges.

Review meeting

A gathering focused on evaluating a work product, often involving multiple reviewers (between 3 to 5 people), requiring advance preparation for each person.

Effort with reviews

Review processes often reduce the amount of effort needed later in development stages.

Quality dimensions

Factors used to assess software quality, which can be qualitatively or quantitatively measured.

Technical debt

Costs incurred from failing to address defects early in the software development process.

Quantitate Quality Assessment

FINISH LATER

Reviews

systematic evaluation of software work products aimed at identifying issues or ensuring compliance with requirements.

A technical meeting done for a work product to employ software quality assurance.

Error

Quality problem found before software is released to end users

Defect

Quality problem found After software has been released

Design activities introduce ___ to ___ of all defects

50 to 65

Review activities have been shown to be ___ effective in uncovering design flaws

75

Defect Amplification

Term to describe how a defect introduced early and undetected, will probably amplify into multiple errors down the line

Defect Propagation

Term used to describe the impact an undiscovered defect has on future development

Reference Model for Techincal Reviews

Reference Model for Technical Reviews \n**Definition:** Framework that describes the objectives, roles, and processes involved in conducting effective technical reviews in software engineering.

Informal Reviews

A simple desk check of a soft eng product with a colleague for the purpose of reviewing a product or review-oriented aspects of pair programming.

Formal