Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
116 Cards in this Set
- Front
- Back
|
What is the description of the Requirements Management & Communication knowledge area? |
It is the activities and considerations for managing and expressing requirements to a broad and diverse audience.
|
|
|
The tasks in the Requirements Management & Communication knowledge area are performed to ensure what?
|
That all stakeholders have a shared understanding of the nature of a solution and to ensure that those stakeholders with approval authority are in agreement as to the reuqirements.
|
|
|
Management of requirements assists with understanding the effects of ___ and linking business ___ and ____ to the actual solution that is constructed and delivered.
|
Change, goals & objectives
|
|
|
All requirements management and communication activities are governed by which two outputs of the Requirements Planning & Monitoring knowledge area?
|
- Business Analysis Plans - Business Analysis Performance Metrics |
|
|
What are the inputs to the Requirements Management & Communication knowledge area?
|
- BA Communication Plan - Organizational Process Assets - Requirements - Requirements Management Plan - Requirements Structure - Solution Scope - Stakeholder List, Roles, and Responsibilities |
|
|
What are the outputs of the Requirements Management & Communication knowledge area?
|
- Requirements (approved) - Requirements (communicated) - Requirements (maintained & reusable) - Requirements (traced) - Requirements Package |
|
|
At what point during a project may requirements approval be sought?
|
At the end of a project phase or at a number of intermediate points in the business analysis process.
|
|
|
Requirements may be ___ following approval.
|
Baselined
|
|
|
If changes are permitted on a project, it would involve the use of a ___ ___ process and subsequent approval.
|
Change Control
|
|
|
If business needs change, the ____ ___ must also change.
|
Solution Scope
|
|
|
In a change-driven approach, there is not typically a formal ___ ___ process.
|
Change Control
|
|
|
How is the requirements management plan used as an input to Manage solution scope and requirements?
|
Defines the process to be followed in managing the solution scope and requirements
|
|
|
What are the inputs to the task "Manage Solution Scope and Requirements"?
|
- Requirements Management Plan - Solution Scope - Stakeholder List, Roles, and Responsibilities - Stakeholder, Solution, or Transition Requirements (Communicated or Traced) |
|
|
What is the output of the task "Manage Solution Scope and Requirements"?
|
Requirements (approved)
|
|
|
What tasks use the output of the task "Manage Solution Scope and Requirements", Requirements (approved)?
|
- Maintain Requirements for Re-use - Assess Proposed Solution - Allocate Requirements |
|
|
How is the Solution Scope used as an input to Manage solution scope and requirements?
|
- Requirements must support the solution scope in order to be approved - Solution scope can be managed in their own right |
|
|
How is the Stakeholder List, Roles, and Responsibilities used as an input to Manage solution scope and requirements?
|
Defines which stakeholders are involved in reviewing and approving requirements
|
|
|
How are the requirements used as an input to Manage solution scope and requirements?
|
- may be managed at any point in their lifecycle - requirements must be communicated to be managed - may be managed if they can be traced to requirements that have been approved |
|
|
What are the elements of "Manage Solution Scope and Requirements"?
|
- Solution Scope Management - Conflict and issue management - Presenting Requirements for Review - Approval |
|
|
All ___ and ___ requirements must be assed to ensure that they fall within the solution scope.
|
Stakeholder and Solution
|
|
|
If requirements are invalid, and fall outside of the solution scope, the BA must do what?
|
Act to resolve the conflict by amending the requirements or reachign agreement that the requirement does not fall within scope.
|
|
|
What are some reasons that conflict may arise when defining requirements?
|
- Stakeholders in different areas viewing requirements from different perspectives - Conflicting priorities |
|
|
What are the methods of resolving conflicts?
|
- Formal Meetings - Research - Third-party mediation - Other methods |
|
|
Conflicts affecting requirements must be ___ before ___ is given.
|
Resolved, Approval
|
|
|
How may requirements be presented for review?
|
Formal or informal
|
|
|
What should be assessed in order to determine the level or formality for presenting the requirements for review?
|
Requirements, audience, and organizational process assets.
|
|
|
If a less formal method of presenting requirements is chosen, it may result in what?
|
Key stakeholders missing information or increased ambiguity in requirements
|
|
|
True or false: Approval may be obtained from stakeholders either individually or as a group.
|
TRUE
|
|
|
What are the techniques used to "Manage Solution Scope and Requirements"?
|
- Problem Tracking - Baselining - Sign-off |
|
|
Which stakeholders are involved in the task "Manage Solution Scope and Requirements"?
|
- Domain SME - Implementation SME - Project Manager - Sponsor |
|
|
What is the purpose of the task "Manage Requirements Traceability"?
|
Create and maintain relationships between business objectives, requirements, other team deliverables, and solution components to support business analysis or other activities. |
|
|
What are the inputs to the task "Manage Requirements Traceability"?
|
- Requirements - Requirements Management Plan |
|
|
What are the outputs of the task "Manage Requirements Traceability"?
|
- Requirements (Traced)
|
|
|
What other tasks use traced requirements?
|
Manage Solution Scope and Requirements
|
|
|
What is the goal of traceability?
|
To ensure that requirements (and ultimately, solution components) are linked back to a business objective
|
|
|
What are the reasons for creating traceability relationships?
|
- Impact Analysis - Requirements coverage - Requirements allocation |
|
|
Requirements traceability identifies and documents the ___ of each requirement.
|
Lineage
|
|
|
What is the word for backward traceability?
|
Derivation
|
|
|
What is the word for forward traceability?
|
Allocation
|
|
|
At what level sould traceability be performed?
|
At any of the following levels, as appropriate: - individual requirement level - model or package level - feature level |
|
|
What is "Impact Analysis"?
|
To review all related requirements and software components in order to understand the "impact" of a change.
|
|
|
How are requirements used as an input to "Manage Requirements Traceability"?
|
All requirements may potentially be traced to other requirements, and all stakeholder and solution requirements must be traceable to a business requirement.
|
|
|
How is the "Requirements Management Plan" used to "Manage Requirements Traceability"?
|
Defines how and whether traceability is being performed, and what tools will be used to manage it
|
|
|
What are the elements of the task "Manage Requirements Traceability"?
|
- Relationships - Impact Analysis - Configuration Management System |
|
|
What are the possible traceability relationships?
|
- Necessity - Effort - Subset - Cover - Value |
|
|
What are the two themes of "Requirements Management & Communication"?
|
- Control Scope - Understand Stakeholders |
|
|
What is the mnemonic for the tasks of "Requirements Management & Communication"?
|
STRPC S - Scope Management T - Traceability R - Re-use P - Package Requirements C - Communicate Requirements |
|
|
What is the "Necessity" relationship in traceability?
|
When it only makes sense to implement a requirement if a related requirement is also implemented. |
|
|
What is the "Effort" relationship in traceability?
|
Exists when a requirement is easier to implement if a related requirement is also implemented.
|
|
|
What is the "Subset" relationship in traceability?
|
When the requirement is the decomposed outcome of another requirement.
|
|
|
What is the "Cover" relationship in traceability?
|
When the requirement fully includes another requirement.
|
|
|
What si the "Value" relationship in traceability?
|
When including a requirement affects the desirability of a related requirement
|
|
|
What is "Impact Analysis" used for in traceability?
|
To assess or evaluate the impact of a change.
|
|
|
What technique is used in "Manage Requirements for Traceability"?
|
Coverage Matrix
|
|
|
Which stakeholders are involved in the task "Manage Requirements for Traceability"?
|
- Implementation SME - Project Manager - Tester |
|
|
What is the output of the task "Manage Requirements for Traceability"?
|
Requirements (Traced)
|
|
|
What is the purpose of the task "Manage Requirements for Re-use"?
|
To manage knowledge of requirements following their implementation
|
|
|
What is a coverage matrix?
|
A table or spreadsheet for the recording and managing of tracing.
|
|
|
When is a coverage matrix used for traceability?
|
When there are relatively few requirements to trace
|
|
|
What are the inputs to the task "Manage Requirements for Re-use"?
|
- Organizational Process Assets - Requirements |
|
|
What are the outputs of the task "Manage Requirements for Re-use"?
|
Requirements (Maintained and Re-usable)
|
|
|
How are "Organizational Process Assets" used as an iput to "Manage Requirements for Re-use"?
|
These set standards regarding how and when requirements should be maintained for re-use
|
|
|
How are "Requirements" used as an iput to "Manage Requirements for Re-use"?
|
Requirements may be maintained for re-use as long as they describe information of use to the orgnization beyond the lifetime of an initiative.
|
|
|
In order for requirements to be re-used, the must be clearly ___ and ____ and ___ ___ to other analysts.
|
Name, Defined, and Easily Available
|
|
|
What are the benefits of maintaining requirements for re-use?
|
- Facilitate impact analysis of new, proposed changes to the business - Reduce analysis time and effort - Assist in maintenance of previously implemented solutions - Support other activities such as training, governance, and compliance |
|
|
What are the elements of the task "Manage Requirements for Re-use"?
|
- Ongoing Requirements - Satisfied Requirements |
|
|
What are "Ongoing Requirements"?
|
Requirements that an organizational unit is required to be able to meet on a continuous basis.
|
|
|
What are some examples of "Ongoing Requirements"?
|
- Contractual Obligations - Quality Standards - Service Level Agreements - Business Rules - Business Processes - Requirements describing the work products the group produces |
|
|
What are "Satisfied Requirements"?
|
Requirements that have been satisifed.
|
|
|
Maintainting "satisfied requirements" helps with what?
|
Product enhancements and future system changes may also be re-used on related business projects.
|
|
|
Which techniques are used in the task "Manage Requirements for Re-use"?
|
None
|
|
|
Which stakeholders are involved in the task "Manage Requirements for Re-use"?
|
- Business Analyst - Domain SME - Implementation SME |
|
|
What is the purpose of the task "Prepare Requirements Package"?
|
To select and structure a set of requirements in an appropriate fashion to ensure that hte requirements are effectively communicated to, understood by, and usable by a stakeholder group or groups.
|
|
|
Requirements documentation should be created to what extent?
|
To assure clear understanding by the team
|
|
|
Why are requirements packages created?
|
- Early assessment of quality and planning - Evaluation of possible alternatives - Formal reviews and approval - Inputs to solution design - Conformance to contractual and regulatory obligations - Maintenance for re-use |
|
|
What is the primary goal of creating a requirements package?
|
To convey information clearly and in an understandable fashion.
|
|
|
___ of requirements will adversely affect solution implmentation.
|
Misunderstanding
|
|
|
What might a misunderstanding of requirements cause?
|
Re-work and cost overruns, particularly if uncovered late in the process.
|
|
|
What are some forms that a requirements package might take?
|
- Formal Documentation - Presentation - Models |
|
|
What are the inputs to the task "Prepare Requirements Package"?
|
- Business Analysis Communication Plan - Organizational Process Assets - Requirements - Requirements Structure |
|
|
When can a requirements be created during a project?
|
At any point in their lifecycle
|
|
|
What are the elements of the task "Prepare Requirements Package"?
|
- Work products and deliverables - Format |
|
|
What is a "work product"?
|
A document or collection of notes or diagrams used by the business analyst during the requirements development process, which may or may not become a deliverable.
|
|
|
What is the output of the task "Prepare Requirements Package"?
|
Requirements Package
|
|
|
What other task used the "Requirements Package"?
|
Communicate Requirements
|
|
|
What are some examples of work products?
|
- Meeting agendas and minutes - Interview questions and notes - Facilitation session agendas and notes - Issues log - Work plan, status reports - Presentation slides used during the project - Traceability matrices |
|
|
What is a "deliverable"?
|
A specific output of the business analysis process that the business analyst has agreed to produce.
|
|
|
A deliverable is used as a basis for what?
|
Solution design and implementation
|
|
|
True or False: a requirements package will likely be a combination of many formats in one requirements package
|
TRUE
|
|
|
What is the best form for a requirements package?
|
The one that best communicates the specific content of the requirement.
|
|
|
Which techniques are used in the task "Prepare Requirements Package"?
|
- Requirements Documentation - Requirements for Vendor Selection |
|
|
What are some of hte most common types of requirements documents?
|
- Business requirements document - Product Roadmap - Software/System Requirements Specification - Supplementary Requirements Specification - Vision Document |
|
|
What are the three types of vendor selection documents?
|
RFI, RFP, RFQ
|
|
|
Which group(s) in an organization typicallys owns the vendor selection process?
|
Purchasing agent, legal department, or procurement organization
|
|
|
Under which circumstances would an RFI be issued?
|
When the issuing organization is open to a number of alternative solutions and is seeking information to evaluate possible options.
|
|
|
When would an RFP or RFQ be used?
|
When the issuing organization understands the nature of the solution options available, and is seeking vendors who can implement an option.
|
|
|
Which is less formal, and RFP or RFQ?
|
RFQ
|
|
|
Before looking at available products for a vendor selection, what must be first be created?
|
Evaluation criteria (based on the business requirements)
|
|
|
When developing RFP questions, avoid using __-___ questions.
|
Closed-ended
|
|
|
What is the goal of an RFP?
|
To stimulate the vendors to provide extensive information regarding their produce and service offerings.
|
|
|
Which stakeholders are involved in the task "Prepare Requirements Package"?
|
- Domain SMEs and End Users - Implementation SMEs - Project Managers - Regulators - Sponsors - Testers |
|
|
What do sponsors typically want to see in a requirements package?
|
- Summaries and high-level requirements - ROI |
|
|
What is the purpose of "Communicate Requirements"?
|
To bring stakeholders to a common understanding of the requirements.
|
|
|
What ways can requirements be communicated?
|
Conversations, notes, documents, presentations, and discussions
|
|
|
Busienss analysis must have a significant set of skills, both ___ and ___.
|
Soft and technical
|
|
|
What are the inputs to the task "Communicate Requirements"?
|
- BA Communication Plan - Requirements - Requirements Package |
|
|
What is the output of the task "Communicate Requirements"?
|
Requirements (communicated)
|
|
|
What task uses "Requirements (communicated)"?
|
Manage Solution Scope and Requirements
|
|
|
True or False: Requirements cannot be communicated without a requirements package
|
False. However, if a requirements package was created, it must be distributed, reviewed, and communicated to stakeholders.
|
|
|
What are the elements of the task "Communicate Requirements"?
|
- General Communication - Presentations |
|
|
When should requirements be communicated?
|
Iteratively and in conjuction with most of the tasks in the other knowledge areas.
|
|
|
True or False: All requirements communication can and should be planned
|
False. Informal communication is likely to be needed during performance of most BA tasks, and can lead to elicitation of additional requirements.
|
|
|
What must be decided before making any presentations of requirements?
|
The appropriate format for the presentation
|
|
|
Requirements presentations can be ___ or ___.
|
Formal or informal
|
|
|
Which techniques are used in the task "Communicate Requirements"? |
- Requirements Workshops - Structured Walkthrough |
|
|
Which Stakeholders are involved in the task "Communicate Requirements"?
|
All stakeholders
|
