Based on Module 06, Section D of the course handouts, what are the negative consequences of neglecting the requirement gathering and documentation phase in the SDLC?
A.It only impacts the unit testing phase, leaving development timelines and SCM activities unaffected.
B.It negatively affects the entire project in terms of quality, cost/budget, deliverables, meeting customer requirements, and revenue.
C.It forces the configuration management team to use third-party repositories like Mantis for all build releases.
D.It leads to a mandatory 25% variation in development efforts that must be formally cleared by Sales.
According to Module 06, Section L of the course handouts, what is famously considered to be 'the mother of all failures' in software requirement engineering, and how should completeness be ensured?
A.Detailed architectural documentation, which should be minimized to encourage developer autonomy.
B.An assumption, and requirements must be complete so all stakeholders completely understand them without guessing.
C.Line-by-line code reviews, which must be replaced by automated compilers to prevent human error.
D.Deploying multiple microservices simultaneously, which should be deferred until Maturity Level 5 is achieved.
Based on Module 06, Sections L and M of the course handouts, which of the following is a primary issue identified in the requirement statement: 'The product shall provide status messages at regular intervals not less than every 60 seconds'?
A.The requirement is technically unfeasible because computers cannot measure intervals of exactly 60 seconds.
B.The requirement violates CMMI Level 4 guidelines by specifying a precise numeric interval instead of a statistical range.
C.The requirement is incomplete because it leaves open questions regarding what the status messages are and where they are supposed to be displayed.
D.The requirement violates configuration management guidelines because it does not define SCM branching rules.
According to Module 06, Section H of the course handouts, which of the following represents a recommended best practice for ensuring a software requirement is 'Correct'?
A.It should be documented as an open-ended statement containing terms like 'etc.' or 'assumed' to allow developer flexibility.
B.It should be stated in a single line and must not exceed 30 to 50 words in length, avoiding open-ended and subjective terms.
C.It must be written in low-level pseudocode so that SQA resources can verify it without executing the program.
D.It must exceed 100 words to ensure all possible technical and hardware limitations are captured in a single statement.
Based on Module 06, Section A of the course handouts, why does requirement engineering pose such a significant challenge for the software industry today?
A.Because compiler technologies fail to translate requirements into binary execution instructions.
B.Because doing it properly is a strenuous task in today's dynamic and turbulent environment.
C.Because CMMI guidelines prohibit developers from communicating directly with SQA engineers.
D.Because requirements are inherently static and never change after the contract is signed.
According to Module 06, Section F of the course handouts, how do software requirements differ from requirements in other traditional domains (such as construction)?
A.Software requirements are completely static and remain exactly the same throughout the SDLC.
B.Software requirements are fully physical, tangible assets from the very beginning of the project.
C.Software requirements come with a lot of variation and changes in all stages of the SDLC, whereas traditional requirements are defined at the beginning and remain fixed.
D.Software requirements cannot be modified or updated after the first internal kickoff meeting.
Based on Module 06, Section J of the course handouts, why is consistent vocabulary and defined technical terms critical during requirements documentation?
A.To ensure that all stakeholders are on the same page and to avoid ambiguities or conflicts in meaning.
B.To automatically generate compilable UML state diagrams in the software configuration repository.
C.To minimize the lines of code that developers need to write during the implementation phase.
D.To replace the requirement for manual black box sanity testing on the final merged codebase.
Based on Module 06, Section F of the course handouts, why does a software product trigger significant requirement changes specifically after its first demo?
A.Because a software product is not tangible until the first demo, and requirements change after stakeholders finally see and interact with it.
B.Because SQA processes mandate that the first demo must fail to initiate a Change Request.
C.Because the database schema is automatically wiped after any demo, requiring a new SRS.
D.Because the cost of software quality increases when requirements are kept stable.
According to Module 06, Section D of the course handouts, what percentage of the entire project budget does requirements documentation typically take in a standard SDLC, and what is the ideal percentage that should be allocated?
A.It takes only 10% of the project budget; ideally, there should be 20% allocated for requirement gathering and documentation.
B.It takes 20% of the project budget; ideally, there should be 10% allocated.
C.It takes only 5% of the project budget; ideally, there should be 50% allocated.
D.It takes 40% of the project budget; ideally, there should be 5% allocated.
Based on Module 06, Section E of the course handouts, what is a key conceptual point worth understanding about the nature of Requirement Engineering?
A.Requirement engineering is purely a technical activity concerned with database normalization.
B.Requirement engineering is not a technical activity rather it is purely a communicational activity.
C.Requirement engineering is a sub-activity of statement-level white-box unit testing.
D.Requirement engineering is a static, one-time task that cannot be updated once a project begins.
