sqa 2 Flashcards
(5 cards)
Scenario:
A hospital is developing a life-critical patient monitoring system. As part of the Software Quality Assurance (SQA) team, you are asked to ensure the software is reliable, meets user expectations, and aligns with contractual obligations.
a. Define the terms: error, defect, and failure. Illustrate how each may appear in the hospital monitoring system. (6 marks)
b. Using the 4-level model of client needs (true, expressed, specified, achieved), evaluate a mismatch that could arise in the hospital’s request for “instant alerts.” (5 marks)
c. Why is it important that the SQA function remains organizationally independent from the project team? (4 marks)
a.
Error: Human mistake – e.g., developer misinterprets heart rate threshold logic.
Defect (fault): Bug in code – e.g., alert triggers at 150 bpm instead of 120 bpm.
Failure: System does not alert when a patient’s vitals cross critical levels.
b.
True Need: Doctors need instant alerts to save lives.
Expressed Need: “We want alerts quickly.”
Specified Need: “Alerts must be triggered in under 2 seconds.”
Achieved Need: System delivers alerts in 5 seconds → gap between expectation and delivery.
c.
To maintain objectivity in assessment, free from political, financial, or delivery pressure. Prevents bias in quality decisions.
a. Define Software Engineering and Quality Assurance. How do they interact to ensure successful project outcomes? (5 marks)
b. SQA activities are said to “instill confidence” in users. Identify 2 techniques that demonstrate this confidence and briefly explain how they work. (5 marks)
a.
Software Engineering: Systematic application of methods to build software.
Quality Assurance: Planned/systematic actions to ensure conformance to requirements.
They interact by embedding QA checks throughout the software lifecycle (planning, testing, validation) using SE processes.
b.
Quality Audits: Check whether the process is being followed.
Verification and Validation (V&V): Ensures product is built right and is the right product.
Scenario:
A QA engineer claims: “As long as our software meets the specifications, the quality is guaranteed.”
a. Critically evaluate this statement using the concept of stakeholder expectations in software quality.
(4 marks)
b. From a client vs user perspective, describe two different quality priorities they might have when evaluating software.
(4 marks)
c. List and explain any three factors that positively influence software quality, and two that negatively influence it.
(4 marks)
a.
Meeting specifications does not guarantee quality unless those specs truly reflect stakeholder needs. Quality also includes implied expectations and how well the product works in practice.
b.
Client: Cost-efficiency, deadline compliance
User: Reliability, usability, performance
c.
Positive:
Clear requirements
Skilled team
Automated testing tools
Negative:
Poor communication
Unrealistic deadlines
a. Define Software Engineering and explain how it relates to the practice of Software Quality Assurance.
(4 marks)
b. Explain three planned actions or techniques an SQA team can use to demonstrate that quality requirements are being met.
(6 marks)
a.
Software Engineering is the application of scientific principles for software design, testing, and documentation.
SQA ensures the engineering process follows quality standards and delivers suitable products.
b.
Use of checklists during code reviews
Process audits to ensure procedure compliance
Defect tracking to measure and reduce failure risks
a. Discuss why the SQA function is ideally structured to be organizationally independent from the development team.
(4 marks)
b. Describe the purpose of a quality policy and how it ties into the SQA system and continuous improvement.
(3 marks)
c. Differentiate between a critical software and a critical system, giving one example of each.
(3 marks)
a.
To avoid bias and pressure from project management. Independence ensures objective evaluation and prevents compromise on quality.
b.
A quality policy defines the organization’s stance on quality goals. It guides the SQA team’s activities and fosters continuous improvement practices.
c.
Critical software: A program where failure has serious consequences (e.g., aircraft autopilot code)
Critical system: A whole system where the entire solution must function reliably (e.g., hospital patient monitoring system)
