Software Quality Management Flashcards
what problems occur when talking about quality?
Problems:
- quality requirements can be open to multiple interpretations (ambiguous)
- often incomplete
- change over time
Shortly describe each Software Quality management activity.
- Quality assurance
- setup organisational processes for quality management
- decide on software development standards
- provide insight into quality of the products and alert the management if there are any quality problems - Quality planning
- define the quality attributes - output of the project
- Assignment of nonfunctional requirements
- Address stuff about market - Quality Control
- review Software artifacts to ensure quality requirements are met
- Test software before release + documentation
- Include feedback loop -> minimise # errors
- take measures if requirements are not met
Define Quality (QM) and describe the two types.
Quality refers to internally and externally measurable characteristics that we can compare to known standards.
Quality of Design
- characteristics that designers specify for the system
- includes requirements, specifications, and the design of the system
Quality of implementation
- how much does it follow the design specifications
Quality also can be described as user satisfaction
Describe which costs can arise in terms of Quality?
- Costs for Quality management itself, e.g. planning, testing, equipment etc.
Failure costs:
- Internal Failure: prior to shipment ad includes rework of the failure
- External Failure: after shipment, can lead to return and warranty claims etc.
What is the purpose of reviews?
- fault avoidance
- discovering errors
- saves a lot of money in the end
Shortly name the types of reviews and levels of formality?
Types of reviews:
- Analysis review
- Architecture review
- Code review
- Client review
- Sprint review
Levels of Formality:
- Informal
- Walkthrough
- – Peer Review
- — Inspection
What is the Objective of the Analysis review?
The objective is to make sure that the requirements specification is
- correct
- complete
- consistent
- clear/ explicit
- realistic
- and verifiable
What is the Objective of the Design review?
Objectives:
• Review the design goals that were identified during system design
• Ensure that the system design model is correct, complete, consistent, realistic, and readable
Shortly describe the objective of code review and name 3 advantages and disadvantages.
Objective: Improve the code quality (clean code)
Advantages:
+ Improved code quality
+ Knowledge transfer
+ Improved developer communication and culture
• Disadvantages:
– Higher costs
– Slower development
– Repetitive tasks
Shortly describe the two types of Quality metrics.
-Dynamic metrics- help assess efficiency and reliability: collected by measurements
made of a program during its execution
-Static metrics- help assess complexity, understandability and maintainability: collected by measurements made of the system representations (e.g. source code)
