According to Module 06, Section E of the course handouts, how is a 'Requirement' formally defined in the context of software systems?
A.A requirement can be defined as a feature of the system or a description of something the system is capable of doing in order to fulfill the system's purpose.
B.A requirement is defined as a line-by-line compilable block of source code written in a high-level language.
C.A requirement is defined as an automated build script executed inside a software configuration management repository.
D.A requirement is defined as a financial invoice deadline shared with the organization's finance department.
According to Module 06, Section B of the course handouts (Page 43-44), what is the direct consequence of a client not being mindful of requirements and putting requirement documentation on low priority?
A.It leads to ambiguity and uncertainty throughout the project, and the chances of failure become high because the development team is not completely sure about what is to be done.
B.It reduces development costs significantly and accelerates the release of the first demo-able version of the software.
C.It allows the SQA team to bypass unit testing and move directly to system-level stress testing.
D.It forces SCM teams to automate build releases without performing sanity testing on merged code bases.
According to the Cavendish Software Chaos Report discussed in Module 06, Section A of the course handouts, which process area is identified as the leading cause of software and IT project failures, accounting for up to 87% of failure chances if executed inaccurately?
A.Software Configuration Management (SCM)
B.Requirement Engineering
C.Automated Statement-Level Unit Testing
D.Heterogeneous Product Integration
According to Module 06, Section E of the course handouts, why are non-technical clients considered a major impediment or difficult to handle in requirement engineering?
A.Because they demand the use of obsolete programming languages like PHP 4.
B.Because they refuse to participate in Skype introduction calls or sign formal contracts.
C.Because they are difficult to handle because of knowledge issues.
D.Because they demand that all software products have zero bugs before the first release.
According to Module 06, Section C of the course handouts (Page 44), which of the following is NOT one of the five specific problems that can occur during requirement engineering?
A.Missing Requirements and Client Lack of Involvement.
B.Inadequate Unit Test Coverage and SCM Branch Merge Conflicts.
C.Wrong Requirements and Changing Requirements.
D.Out of Scope Requirements.
Based on Module 06, Section C of the course handouts (Page 44), why is requirement engineering considered the most important area of the entire software life cycle?
A.Because compiler technologies can automatically translate requirements into error-free executable binary code.
B.Because errors produced in this phase cost a lot in later stages, and the customer will not get the required product in the required time.
C.Because it completely replaces the need for software validation and verification in subsequent stages.
D.Because requirement development represents 80% of the total budget allocation in a standard SDLC.
According to Module 06, Section I of the course handouts, what specific action is suggested to resolve the ambiguity of subjective client requirements such as 'GUI should be user friendly'?
A.Developers should implement their own preferred color scheme and skip the client validation phase.
B.Ask the client for reference or show him some reference material or a sample website to get started, and avoid subjective terms.
C.Log the requirement as 'NotAFix' and defer it to the post-deployment maintenance phase.
D.Rewrite the requirement using formal mathematical pseudocode and compile it inside an SCM repository.
According to the 'Example of Coherent' in Module 06, Section K of the course handouts, what issue arises when one requirement references 'ISO-ITIL 3.0' compliance and another references 'ISO-90 – ITIL 3.0' compliance, and how is it resolved?
A.The requirements are in conflict regarding the correct version or standard of ISO, and the resolution is that only one consistent standard should be used.
B.The requirements represent a standard Level B critical risk, which is resolved by updating the schedule baselines.
C.The conflict indicates a database schema mismatch, which is resolved by running an SQL merge script.
D.The requirements are both correct because ISO and ITIL allow multiple parallel standards in Level 5 CMMI organizations.
According to Module 06, Section J of the course handouts, what does the 'Coherent' attribute require when documenting software requirements?
A.Requirements must be logical, consistent, add value to the project, and not come in conflict with other requirements or the project scope.
B.Requirements must be written using object-oriented C++ classes with at least 80% line-level test coverage.
C.Requirements must define the database index structure and exclude any reference to third-party APIs.
D.Requirements must be documented on exactly three lines of text with a mandatory CMMI Level 5 quantitative rating.
Based on Module 06, Section I of the course handouts, why is the requirement statement 'GUI should be user friendly' considered problematic from an SQA correctness standpoint?
A.Because user friendliness cannot be implemented in modern web browsers due to cross-origin resource sharing limitations.
B.Because it is an open-ended, subjective term that is highly difficult to correct in the first cut and introduces ambiguity.
C.Because CMMI guidelines restrict the use of graphical interfaces in Level 3 certified software applications.
D.Because the database configuration is not capable of validating the layout of user interfaces.
