quality Comparison Table

Next criterion: standard Up: criterion Previous criterion: principle

quality comparison table

Subject avoid by cause by be is a subtopic of has definition

atomicity 9.5 - Architectural Patterns A property of a transaction that ensures it is completed entirely, or not at all

concurrency 3.4 - The Client-Server Architecture

requirements churn incremental development, building flexibility into the design, regular reviews of the requirements and, above all, always working with a respect for the inevitability of change rapid changes in requirements 4.12 - Difficulties and Risks In Domain and Requirements Analysis

ripple effect The situation in which removing defects causes new ones to be added

software quality hard to assess 1.5 - Software Quality

Subject	avoid by	cause by	be	is a subtopic of	has definition
atomicity				9.5 - Architectural Patterns	A property of a transaction that ensures it is completed entirely, or not at all
concurrency				3.4 - The Client-Server Architecture
requirements churn	incremental development, building flexibility into the design, regular reviews of the requirements and, above all, always working with a respect for the inevitability of change	rapid changes in requirements		4.12 - Difficulties and Risks In Domain and Requirements Analysis
ripple effect					The situation in which removing defects causes new ones to be added
software quality			hard to assess	1.5 - Software Quality

Next criterion: standard Up: criterion Previous criterion: principle