IS Quality Part 2 Flashcards
(53 cards)
What is the key premise of Dromey’s product quality model?
Software exhibits product characteristics that imply or contribute to quality attributes, rather than directly manifesting quality attributes.
What are the two approaches in Dromey’s model?
Bottom-up: Start with structural forms and their quality-carrying properties.
Top-down: Start with desired quality attributes and determine necessary properties.
What are Dromey’s four quality-carrying properties?
Correctness Properties
Structural Properties
Modularity Properties
Descriptive Properties
What do correctness properties cover in Dromey’s model?
Computability, completeness, and consistency.
What do modularity properties address?
High-level design issues related to how modules interface with the rest of the system.
What are descriptive properties?
They reflect how well the software is described, including comments, documentation, etc.
What is COQUAMO based on?
Adaptation of Boehm’s COCOMO model using Rome Lab Software Quality Framework.
What distinguishes COQUAMO from earlier models?
Integration of user, manufacturer, and product views, and use of both subjective and objective quality measures.
What are the components of the COQUAMO model?
Transcendent Properties (e.g., usability – hard to measure)
Quality Factors (reliability, flexibility – can be subjective or objective)
Merit Indices (subjective quality ratings)
What input does COQUAMO require?
Product attributes (e.g., quality requirements)
Process attributes (e.g., maturity)
Personnel attributes (e.g., experience)
Project attributes (e.g., expected quality norm)
Organizational attributes (e.g., quality management)
Why was the Squid Product Model developed?
After COQUAMO results showed that software product metrics were poor predictors of final product quality.
What is the purpose of Quality Function Deployment (QFD) in software?
To translate customer requirements into technical requirements at each development and production stage.
What must be identified before beginning a software project using QFD?
The desired characteristics and their importance as identified by stakeholders.
What are some criticisms of software quality models?
Quality is hard to compare across products.
There’s no consensus on definitions, criteria, or good measures.
Lack of models that rationalize multiple views.
What does Voas argue in defense of product-oriented models?
They are more focused on achieving quality than merely assessing it, making them crucial for research.
What dilemma do organizations face with software testing vs process measurement?
Testing measures the right things imprecisely; process measures the wrong things precisely.
Why is it hard to evaluate software using all views of quality?
Different views are hard to adopt simultaneously, and there’s a lack of frameworks justifying each view.
What model supports the evaluation of software quality from a cognitive perspective?
The means-end chain model, linking characteristics, consequences, and values.
What did the cognitive-based study reveal about evaluators?
Patterns between characteristics, consequences, and values help describe evaluator behavior and decision-making.
Why do requirements defects remain a significant issue in software-intensive system development?
Because individual function requirements represent fragments of behavior, but system design demands integrated behavior. Transitioning from fragmented to integrated behavior is complex, and most defects arise from mismatches, omissions, or inconsistencies in this process.
What is the role of behavior trees in addressing requirements defects?
Behavior trees allow a design to be constructed directly from its functional requirements by composing individual behavior trees into an integrated behavior design. This helps detect different defect types at each composition stage.
At which stages can defects be detected when using behavior trees?
Defects may occur:
During translation of individual requirements into behavior trees,
During integration into a full design behavior tree (DBT),
When projecting component behavior trees from the DBT,
Through inspection and model checking of the DBT.
What are the common problems with functional requirements?
They may be incomplete, inconsistent, or redundant.
They may not reflect stakeholder intentions.
Translation to design may distort the original meaning.
They may become outdated or inadequate as development progresses.
Their complexity can exceed human short-term memory.
The alignment between requirements, design, and implementation may be lost.
Why are existing requirements analysis and design methods insufficient for complex systems?
Because they often result in multiple, partial system views that overlap but don’t integrate well—making it hard to detect defects, especially those involving inter-requirement interactions.
