CIS 317 Chapter 5 Quiz Review

For construction projects today, the real choice of project approach today is between: Agile vs. plan-driven. Agile vs. hybrid. Plan-driven vs. hybrid. There is no significant choice: agile has won for both requirements and construction. There is no significant choice: hybrid has won for both requirements and construction.

Agile vs. hybrid.

Comparing the agile approach vs. the plan-driven approach in today's environment, which of the following is NOT true: Agile is best suited to small, simple projects with small teams and uncertain and/or rapidly changing requirements. Plan-driven is best suited to large, complex projects with large teams and highly certain and stable requirements. Agile works best in projects focused on the configuration of commercial-off-the-shelf (COTS) software. Agile and plan-driven are frequently combined into a hybrid approach. All of the above are true.

Agile works best in projects focused on the configuration of commercial-off-the-shelf (COTS) software.

In terms of interpreting the plot of a project characteristics radar chart, which of the following is NOT TRUE: Projects plotting near the center align to the Agile Home Ground. Projects plotting near the outer edge align to the Hybrid Home Ground. High levels of BRUF suggest high levels of team characteristics. High levels of BDUF suggest high levels of team characteristics. All of the above are true.

All of the above are true.

Regarding the value of big requirements up front (BRUF) during software construction: Plan-driven assumes that requirements are stable, changing little. Agile assumes that requirements change rapidly. Plan-driven assumes requirements value remains high. Agile assumes requirements value declines rapidly. All of the above are true.

All of the above are true.

The "Yes, but" syndrome occurs when customers see the software end product and realize "that's not what I really need"—it can be caused by: The IT team misinterpreting the customer's request. The customer asking for the wrong requirements. The requirements changing during the project. Utilizing non-iterative construction that may last months or even years. All of the above are true.

All of the above are true.

With respect to detailed requirements for each user story, which of the following is NOT true of the agile approach: Agile tends to create detailed requirements right before each user story is constructed in a sprint. Agile tends to do less formal, detailed requirements overall than does plan-driven. Agile tends to view creating formal, detailed requirements as a waste of time. Agile utilizes minimal requirements documentation, often called "barely sufficient requirements." All of the above statements are true of the agile approach.

All of the above statements are true of the agile approach.

Compared to creating detailed, up-front requirements, agile tends to view creating traditional detailed, up-front project plans as: A good way to compensate for the risk of doing fewer up-front, detailed requirements. Only useful for specific programming languages. Most important during construction sprints. Also a waste of time. None of the above are true.

Also a waste of time.

Comparing the agile approach vs. the plan-driven approach in today's environment: Agile has largely replaced plan-driven. Plan-driven has largely replaced agile. Either can be used equally well in any software construction project, so long as the team uses the chosen approach effectively. Both are used, but each is best suited for certain, specific types of projects. None of the above are true.

Both are used, but each is best suited for certain, specific types of projects.

Comparing iterative vs. non-iterative software construction: Iterative construction is always superior to non-iterative construction. Non-iterative construction is always superior to iterative construction. Iterative construction is superior to non-iterative construction for agile projects only. Non-iterative construction helps avoid the "Yes, but" syndrome. None of the above are true.

Iterative construction is always superior to non-iterative construction.

Regarding the costs of changing requirements during a project, agile assumes: High change costs at both the beginning and end of a project. Low change costs at the beginning that stay mostly unchanged over time. Low change costs at the beginning that rapidly increase throughout the project. High change costs at the beginning that slowly decrease through the project. None of the above are true.

Low change costs at the beginning that stay mostly unchanged over time.

Which of the following is not a non-functional requirement: Average response time. Security to protect confidential customer data. Number of simultaneous users supported. Ability to communicate with other systems using web services. Domain model.

Domain model.

Regarding the value of big requirements up front (BRUF), plan-driven assumes: High value initially because BRUF can completely and accurately capture requirements early on Low value initially because BRUF will be incomplete and inaccurate, even at the beginning A high degree of requirements clarity is generally impossible Software, as an intangible product, is fundamentally more difficult to envision than tangible items None of the above are true.

High value initially because BRUF can completely and accurately capture requirements early on

The Home Grounds Model defines different sets of major project characteristics indicating the type of project approach that is most appropriate and likely to succeed—which of the following is NOT one of the major categories of project characteristics: Functional requirements characteristics Non-functional requirements characteristics Hybrid project characteristics Team characteristics All of the above are major categories of Home Grounds Model project characteristics

Hybrid project characteristics

The hybrid approach fundamentally consists of: BRUF and BDUF delivered via non-iterative construction. BRUF and BDUF delivered via iterative construction. Emergent requirements delivered via non-iterative construction. Emergent requirements delivered via iterative construction. A highly repeatable series of steps for configuring commercial-off-the-shelf (COTS) software.

BRUF and BDUF delivered via iterative construction.

Comparing big requirements up front (BRUF) and big design up front (BDUF): BRUF pertains to functional requirements and BDUF to non-functional requirements. BRUF pertains to non-functional requirements and BDUF to functional requirements. BRUF is used in plan-driven projects and BDUF is used in agile projects. BRUF and BDUF are synonyms. BRUF is used in agile projects and BDUF is used in plan-driven projects.

BRUF pertains to functional requirements and BDUF to non-functional requirements.

Which of the following is correct? -Emergent requirements is associated with the plan-driven project approach and big requirements up-front is associated with the agile project approach. -Emergent requirements is associated with the agile project approach and big requirements up front (BRUF) is associated with plan-driven project approach. -Configuration projects typically use emergent requirements, while construction projects typically use big-requirements up front. -Big requirements up front are needed when team members work in a face-to-face environment. -The is no significant relationship between requirements approach and project approach.

Emergent requirements is associated with the agile project approach and big requirements up front (BRUF) is associated with plan-driven project approach.

In a project characteristics radar chart, which of the following is NOT a Big Design Up Front factor: Performance Stability Criticality Integration Technology

Stability

In a project characteristics radar chart, which of the following is NOT a Big Requirements Up Front factor: Number Complexity Interdependence Supportability Clarity

Supportability

Which of the following is NOT an important source of the non-functional requirement of criticality: System impacts on human safety. System facing the public Internet. System includes sensitive and confidential data. System needs to be highly maintainable and extensible over time. System is subject to regulation or audit.

System needs to be highly maintainable and extensible over time.

In terms of finding the "right answer" to the question of using big requirements up front (BRUF) vs. emergent requirements, the chapter argues that: BRUF is still generally the best approach. Emergent requirements have largely replaced BRUF. The best choice for each project depends on that project's characteristics. Either can work about equally well in most projects. The BA should use whichever approach she feels most comfortable with.

The best choice for each project depends on that project's characteristics.