CBAP - Requirements Analysis - 20 - Quiz, Flashcards & Trivia

1. What imposes limitations on your solution?

Attributes

Constraints

Assumptions

Priorities

Constraints impose limitations imposed on the solution that do not support the business or stakeholder needs.

Explanation

Constraints impose limitations imposed on the solution that do not support the business or stakeholder needs.

2. What is the purpose of nonfunctional requirements?

Addressing educational needs of users interacting with the solution

Defining quality attributes and design constraints of the solution

Protecting and preventing access to data that the solution uses or creates

Describing the likely growth of use of the deployed and maintained solution over time

Nonfunctional requirements define quality attributes, design, and implementation constraints and external interfaces the product must have. They are a type of solution requirement.

Explanation

Nonfunctional requirements define quality attributes, design, and implementation constraints and external interfaces the product must have. They are a type of solution requirement.

3. What is defined as a sequence of repeatable activities executed in an organization?

Rule

Event

Process

Object

A process is defined as a sequence of repeatable activities executed in an organization.

Explanation

A process is defined as a sequence of repeatable activities executed in an organization.

4. What requirements analysis task ensures that solution requirements align to the business requirements?

Validate requirements.

Verify requirements.

Prioritize requirements.

Specify requirements.

Requirements validation ensures that all requirements support the delivery of value to the business by ensuring that stakeholder, solution, and transition requirements align to the business requirements.

Explanation

Requirements validation ensures that all requirements support the delivery of value to the business by ensuring that stakeholder, solution, and transition requirements align to the business requirements.

5. Data flow diagrams show how __________ flows through a system.

Processes

Requirements

Decisions

Information

Data flow diagrams show how information flows through the system.

Explanation

Data flow diagrams show how information flows through the system.

6. When reviewing a set of related requirements, you discover that two of the requirements describe the same feature but produce different results. Based on your well-written requirements checklist, you would note that these requirements are not ____________.

Complete

Consistent

Cohesive

Correct

Consistent requirements do not contradict or conflict with one another.

Explanation

Consistent requirements do not contradict or conflict with one another.

7. What is the name for an abstraction representing some or all of a proposed solution?

Diagram

Concept

Matrix

Model

A model serves as an abstraction representing some or all of the proposed solution.

Explanation

A model serves as an abstraction representing some or all of the proposed solution.

8. Tasks performed as part of requirements analysis include:

Specify and model requirements.

Manage solution scope and approach.

Prepare requirements package.

Manage requirements traceability.

The six tasks of requirements analysis are prioritize requirements, organize requirements, specify and model requirements, define assumptions and constraints, verify requirements, and validate requirements.

Explanation

The six tasks of requirements analysis are prioritize requirements, organize requirements, specify and model requirements, define assumptions and constraints, verify requirements, and validate requirements.

9. What is the name for the individual pieces of information that describe an entity in an entity relationship diagram?

Identifier

Relationship

Attribute

Cardinality

The four main components of an entity relationship diagram are the entities, their attributes, unique identifiers for each occurrence of an entity, and relationships between the entities. Attributes are individual pieces of information that describe an entity.

Explanation

The four main components of an entity relationship diagram are the entities, their attributes, unique identifiers for each occurrence of an entity, and relationships between the entities. Attributes are individual pieces of information that describe an entity.

10. Process models show how the system behaves over the course of time through the:

Structures describing what is important to the enterprise

Execution of business processes or a series of events

Set of related set classes and associations between them

Business s policies, guidelines, standards, and regulations

Process models show how the system behaves over the course of time through executing business processes or resulting from events that occur inside the solution scope.

Explanation

Process models show how the system behaves over the course of time through executing business processes or resulting from events that occur inside the solution scope.

11. What component of an entity-relationship diagram is contained in the labeled rectangle and represents a source or destination of data?

Attribute

Relationship

Entity

Constraint

Entities in an entity-relationship diagram are the things about which data is needed. They are contained in the labeled rectangle of the diagram.

Explanation

Entities in an entity-relationship diagram are the things about which data is needed. They are contained in the labeled rectangle of the diagram.

12. What is another name for the quality check performed following analysis of a requirement?

Verification

Validation

Approval

Clarification

Verification is a quality check performed after a requirement is analyzed. Verification activities are typically performed iteratively throughout the requirements analysis process.

Explanation

Verification is a quality check performed after a requirement is analyzed. Verification activities are typically performed iteratively throughout the requirements analysis process.

13. Which technique organizes your requirements based on the solution components to which they are related?

Data dictionary

Business rules

Scope modeling

Class diagram

Scope modeling organizes requirements based on the solution components to which they are related.

Explanation

Scope modeling organizes requirements based on the solution components to which they are related.

14. Which deliverable defines your process for prioritizing solution requirements?

Solution approach

Business analysis approach

Requirements management plan

Business analysis plan

The requirements management plan built as part of the Business Analysis Planning and Monitoring knowledge area defines the process used to prioritize requirements during requirements analysis.

Explanation

The requirements management plan built as part of the Business Analysis Planning and Monitoring knowledge area defines the process used to prioritize requirements during requirements analysis.

15. You are currently reviewing a specific requirement to see if it is modifiable. What is a modifiable requirement?

Operationally feasible and fits within budget and schedule constraints

Logically structured in a related group and able to be changed

Technically feasible with a wide range of implementation options

Testable and representing all relevant requirements as a set

Modifiable requirements are logically structured in a related group and able to be changed.

Explanation

Modifiable requirements are logically structured in a related group and able to be changed.

16. To determine which requirements can be delivered by the project team in a fixed amount of time, you begin with all eligible requirements and remove them in order to meet the calendar date. Which timeboxing approach are you applying?

All-in

Time- riven

All-out

Iterative

All-in timeboxing determines which requirements can be delivered by the project team in a fixed amount of time by beginning with all eligible requirements and removing them in order to meet the calendar date.

Explanation

All-in timeboxing determines which requirements can be delivered by the project team in a fixed amount of time by beginning with all eligible requirements and removing them in order to meet the calendar date.

17. The tasks and techniques in the Requirements Analysis knowledge area are used to define what types of requirements?

Business and stakeholder

Stakeholder and transition

Solution and stakeholder

Transition and solution

Requirements analysis tools and techniques are used to develop the stakeholder and solution requirements.

Explanation

Requirements analysis tools and techniques are used to develop the stakeholder and solution requirements.

18. When facilitating a requirements prioritization session, you encounter a stakeholder who wants to rank all of their requirements as high-priority requirements for the project. What type of challenge is this?

Nonnegotiable demand

Unrealistic tradeoff

Stakeholder avoidance

Unrealistic expectations

Challenges in facilitating requirements prioritization sessions include nonnegotiable demands such as avoiding difficult choices, not making tradeoffs, or ranking all requirements as a high priority.

Explanation

Challenges in facilitating requirements prioritization sessions include nonnegotiable demands such as avoiding difficult choices, not making tradeoffs, or ranking all requirements as a high priority.

19. The two inputs to specifying and modeling requirements are:

Business rules and the requirements management plan

Solution scope and stakeholder list, roles, and responsibilities

Stakeholder concerns and a documented business need

Stated requirements and a requirements structure

The two inputs to specifying and modeling requirements are the stated requirements and the requirements structure.

Explanation

The two inputs to specifying and modeling requirements are the stated requirements and the requirements structure.

20. Assumptions and constraints are defined and clarified as requirements are understood and documented with their associated:

Limitations

Attributes

Restrictions

Requirements

Assumptions and constraints are defined and clarified as requirements are understood and documented with their associated attributes such as date identified, owner, impact, and any associated risks.

Explanation

Assumptions and constraints are defined and clarified as requirements are understood and documented with their associated attributes such as date identified, owner, impact, and any associated risks.