Describe the concept of functional requirements in software systems and analyze how they differ from the attributes that govern requirement quality (such as verifiability). Furthermore, explain how Use Cases act as the primary bridge to translate these functional requirements into structured, traceable steps for development and testing.
Ch 06: Support Process Area
Analysis of formal configuration baselines, change control boards (CCB), objective quality evaluations via PPQA, data measurement repositories, and structured decision evaluation matrices.
279 Questions279 MCQs0 Short Questions0 Long Questions
SEMESTER PASS
CS611 - Software Quality Engineering Examination Practice
Timed practice exam simulation for CS611 - Software Quality Engineering.
Showing 211 – 220 of 279 Questions
Page 22 of 28
Describe the lifecycle, authorship, and content structure of software Release Notes as detailed in the course material. Explain why this document is critical for deployment and how it builds client trust.
According to the Cavendish Software Chaos Report and the effort-wise distribution of SDLC, what percentage of the total project budget is ideally recommended for requirement gathering and documentation to avoid project failure, compared to what is typically spent?
Compare the typical and ideal budget allocations for requirement gathering and documentation in a software development life cycle (SDLC). What are the consequences of neglecting this phase?
Under what condition is the Release Notes document officially distributed to customers or clients?
Define the 'Traceable' quality attribute of software requirements, and explain the difference between 'forward integration' and 'backward integration' as described in the handouts.
Discuss the fundamental purpose and core functions of Software Quality Assurance (SQA) as described in the handouts and lecture. Detail the role of the SQA team as an 'internal customer,' and explain why the two primary functions of quality (defect minimization and alignment with customer needs) must be balanced throughout the Software Development Life Cycle (SDLC).
The handouts outline five major problem areas that commonly arise during requirement engineering. Identify and explain these five issues and how they negatively impact a software project.
A client provides the following software requirement: 'The Graphical User Interface (GUI) of the billing application should be extremely user-friendly.' Explain which requirement attribute is violated in this statement, identify the issue, and provide a professional suggestion to resolve it.
If a software requirement states, 'The product shall provide status messages at regular intervals not less than every 60 seconds,' which requirement quality attribute is primarily violated and why?