In the context of the Requirement Development process area, requirements gathering is primarily defined as which type of activity?
A.communication activity
B.design activity
C.technical activity
D.procurement activity
Which of the following groups represents the correct quality attributes of software requirements as defined in the course handouts?
A.Complex, Customized, Codified, Fixed, and Closed.
B.Correct, Coherent, Complete, Feasible, Necessary, Verifiable, and Traceable.
C.Redundant, Implicit, Unverifiable, General, and Non-traceable.
D.Variable, Functional, Structural, Auditable, and Certified.
In the absence of properly documented software requirements, what is the ultimate consequence for the development team and the software project according to Module 06?
A.The development team faces compiler configuration conflicts, and database sharding becomes completely impossible.
B.The team is not completely sure about what is to be done, and the actual purpose of software development is lost.
C.The software configuration management (SCM) repository branch is permanently locked to prevent code commits.
D.The project automatically falls back to CMMI Maturity Level 1 with no option for independent SQA auditing.
In Module 06, Section C of the course handouts, which of the following is NOT listed as a common problem that occurs during requirement engineering when the team fails to focus on requirements?
A.Missing Requirements and Client Non-Involvement.
B.Wrong Requirements and Out of Scope Requirements.
C.Changing Requirements during later stages.
D.Compilation syntax errors and database index fragmentation.
According to the Cavendish Software Chaos Report and the motivation for software requirements discussed in Module 06, why does requirement engineering become a significantly harder task for software development teams?
A.Because clients are often not mindful of requirements and put requirement documentation on low priority, leading to ambiguity.
B.Because developers prefer writing code in low-level languages rather than documenting high-level requirement models.
C.Because software quality assurance teams refuse to review requirement specification documents during the initial stages.
D.Because automated compilers are unable to parse requirement documents to generate executable test cases.
According to the Cavendish Software Chaos Report discussed in Module 06, what is identified as the top reason behind software/IT project failures, and what percentage of failure chances does it carry if not done accurately?
A.Software Configuration Management (SCM) issues, carrying a 45% chance of project failure.
B.Lack of automated Software Quality Assurance (SQA) testing tools, carrying a 60% chance of project failure.
C.Requirement engineering, carrying an 87% chance of project failure if not done accurately.
D.Inappropriate selection of programming languages, carrying a 30% chance of project failure.
According to Module 06 of the course handouts, why is an 'assumption' described as 'the mother of all failures' in software requirement engineering, and how should completeness be achieved to prevent this?
A.Because assumptions lead to compiler-level memory leaks that SQA is unable to debug.
B.Because requirements must be complete so that all stakeholders completely understand them, leaving no room for guessing or assuming things, expressing the entire need along with all conditions and constraints.
C.Because assumptions force the software configuration team to lock the baseline code repository during planning.
D.Because CMMI Capability Level 5 prohibits the use of any object-oriented class assumptions during unit testing.
According to Module 06, Section J, what is required for software requirements to satisfy the 'Coherent' attribute?
A.They must be consistent, must not conflict with other requirements or the project scope, and must use consistent and defined technical terms.
B.They must be compiled into executable binary unit tests before the architectural design is finalized.
C.They must be written in a single line of exactly 15 words and contain at least three open-ended terms.
D.They must be approved solely by the Software Management (SCM) lead to prevent repository merge conflicts.
Based on the 'Effort-wise Distribution of SDLC' discussed in Module 06, what is the typical budget percentage currently allocated to requirements documentation, and what is the ideal percentage recommended to prevent project issues?
A.Typical: 5%, Ideal: 15%
B.Typical: 10%, Ideal: 20%
C.Typical: 15%, Ideal: 25%
D.Typical: 20%, Ideal: 40%
Why is a 'Use Case ID' considered essential when documenting functional requirements using the standard template in Module 06?
A.It is used to make the functional requirements traceable across the design, code, and testing phases of the SDLC.
B.It is required by compiler tools to generate binary execution streams.
C.It calculates the team's weekly budget and resource allocations automatically.
D.It represents the total number of actors who are authorized to run sanity test cases.
