Software quality practices have evolved over six decades. What began as a response to the “software crisis” of the 1960s has grown into collaborative specification techniques that bridge the gap between business and technical teams.
Contents
- Evolution of Quality Approaches
- The Software Crisis (1968)
- Structured Programming (1968)
- Fagan Inspections (1976)
- Cleanroom Software Engineering (1980s)
- Personal Software Process (1990s)
- UML and Design Communication (1997)
- Extreme Programming (1996-1999)
- Test-Driven Development
- Behavior-Driven Development (2006)
- The C4 Model (2011)
- Given-When-Then Format
- User Stories
- Specification by Example (2010s)
- Example Mapping
- TDD…
Evolution of Quality Approaches
1968-1990s: Quality through PROCESS
The early focus was on disciplined processes to catch defects: Fagan Inspections (formal peer review), Cleanroom (defect prevention), and PSP (individual measurement).
1994-1997: Quality through DESIGN COMMUNICATION
Teams needed shared visual languages. UML unified…














Myth vs reality of AI Work
%E2%80%9D.jpg)







