As a recommended best practice in Module 06 for documenting verifiable software requirements, which of the following keywords should be avoided to prevent ambiguity?
A.Jargon words like 'must', 'shall', or 'etc.'
B.Functional design descriptors like 'button', 'login', or 'toggle'
C.Standard database parameters like 'index', 'key', or 'join'
D.CMMI process framework levels like 'managed', 'defined', or 'optimized'
According to Module 06 of the course handouts, what characteristics must a software requirement possess to satisfy the 'Traceable' quality attribute under CMMI and Software Quality Engineering guidelines?
A.It must be written using automated validation scripts and stored exclusively in a secure cloud database folder.
B.It should be linked to its source in the Requirement Specifications, have a unique identifier (like an ID number), and be linked with Use cases, design, and test cases.
C.It must be capable of running independently of SCM code branch integrations and require zero compiler warning checks.
D.It must be written using a single line of exactly 10 to 15 words and contain at least three subjective terms.
According to Module 06, Section CC of the handouts, what is 'Release Management', and what represents its most critical component before shipping a build?
A.It is a methodology to debug compiling errors on the local developer environment; the most critical component is testing unit coverage ratios.
B.It is another name for controlling a software build throughout different stages, involving planning, scheduling, and execution; the most critical component is seeking approvals on the schedule and features to be added.
C.It is a project cost control framework using EVM; the most critical component is adjusting the CPI and SPI budget lines.
D.It is an automated defect logging process in Mantis; the most critical component is verifying that zero defects are found.
According to Module 06 of the course handouts, what is the primary purpose of 'Requirement verification' as a structured and organized activity?
A.To confirm that the built software product fully addresses the documented and agreed-upon requirements.
B.To automate the creation of CMMI Level 5 software process assessment reports.
C.To lock the software configuration management branches during the design phase.
D.To calculate the final earned value of the project's completed tasks.
According to the course handouts, what is a major impediment in requirement engineering when dealing with non-technical clients?
A.Their insistence on writing complex object-oriented class definitions during scope kickoff.
B.They are difficult to handle and understand because of knowledge issues.
C.They frequently attempt to modify database indexes and network configurations on the live servers.
D.They demand that requirements must be written in formal mathematical specification languages.
What is the critical structural consequence of having 'Missing Requirements' that are not documented properly during the requirements engineering phase?
A.The developer's compiler will throw syntax errors, preventing any local execution or code generation.
B.The project team may skip requirements, making it nearly impossible to change the software design afterwards.
C.The CMMI appraisal rating of the organization is automatically downgraded to Capability Level 0.
D.The software release notes must be written exclusively by the customer support representative.
What are the Pre-Condition and Post-Condition specified in the 'Sign In' Use Case (Use Case ID 1) template in Module 06?
A.Pre-Condition: System must be in offline maintenance mode; Post-Condition: Database indexes are rebuilt.
B.Pre-Condition: Actor must be already registered and authorized; Post-Condition: Actor is logged in successfully if credentials are valid and active, otherwise the system state remains unchanged.
C.Pre-Condition: Actor must have an active social media session; Post-Condition: System syncs search history with external APIs.
D.Pre-Condition: SCM repository must be locked; Post-Condition: Release notes are compiled and displayed.
In software requirement engineering, how are 'Forward Integration' and 'Backward Integration' defined and differentiated in the context of traceability?
A.Forward integration maps a requirement to SCM database schemas, while backward integration maps it back to compilers.
B.Forward integration is used to identify where a requirement is used, while backward integration is used to determine where that feature originated.
C.Forward integration tracks compiler-level syntax errors, while backward integration checks for logical runtime faults.
D.Forward integration is a project management tool for checking SPI, while backward integration calculates CPI trends.
What error-handling exception is defined in the 'Register new patient' Use Case (Use Case ID 7) when a duplicate entry is detected?
A.The system will automatically overwrite the existing record with the new details.
B.The SCM team will lock the repository and log a defect in Mantis with an estimated fix time of 1 hour.
C.If the intended patient is already registered within the system, the system will prompt a message 'Patient Already Registered!' and won't allow registering them again.
D.The system will allow duplicate entries but assign them to different deactivated doctors.
According to Module 06, Section N of the course handouts, how is a software requirement determined to be 'Feasible'?
A.If it can be compiled without syntax errors or warnings by any standard object-oriented compiler.
B.If it is possible to implement or satisfy it within the scope, budget, and physical limitations of the project, preferably with technical input from developers.
C.If it takes up less than 10% of the total project budget allocated to the Software Configuration Management team.
D.If the customer agrees to sign a Service Level Agreement (SLA) without reviewing any first-cut prototypes.
