• Shuffle
    Toggle On
    Toggle Off
  • Alphabetize
    Toggle On
    Toggle Off
  • Front First
    Toggle On
    Toggle Off
  • Both Sides
    Toggle On
    Toggle Off
  • Read
    Toggle On
    Toggle Off
Reading...
Front

How to study your flashcards.

Right/Left arrow keys: Navigate between flashcards.right arrow keyleft arrow key

Up/Down arrow keys: Flip the card between the front and back.down keyup key

H key: Show hint (3rd side).h key

A key: Read text to speech.a key

image

Play button

image

Play button

image

Progress

1/43

Click to flip

43 Cards in this Set

  • Front
  • Back
  • 3rd side (hint)
By maintaining requirements that are candidates for other projects in the organization, reduced
time for future analysis and easier maintenance is enabled. When a BA does this, which task is
he or she performing?
a. Determine organizational readiness.
b. Maintain requirements traceability.
c. Maintain requirements for re-use.
d. Allocate requirements.
c. Maintain requirements for re-use.
"The output of this task are requirements
that are expressed in a form that makes
them suitable for long-term usage ...""
BABOK 4.3.2 and 4.3. 7."
Which is an output from Requirements Management and Communication?
a. Requirements (approved).
b. Requirements (specified).
c. Requirements (documented).
d. Requirements (elicited).
a. Requirements (approved).
Figure 4.1.
Communicating requirements helps to:
a. Specify requirements.
b. Bring stakeholders to a common understanding.
c. Prioritize and progressively elaborate requirements.
d. Helps stakeholders defme their real business need.
b. Bring stakeholders to a common
understanding.
Intro to Chapter Four.
Which of the following does NOT describe a traceability relationship?
a. Effort.
b. Value.
c. Necessity.
d. Hierarchy.
d. Hierarchy.
BABOK 4.2.4.1.
In managing requirements traceability, the cover relationship describes:
a. When the requirement is a decomposed outcome of another requirement.
b. When the requirement is met by a test case.
c. When the requirement fully includes the other requirement.
d. When the requirements links to a lower-level requirement.
c. When the requirement fully includes the other requirement.
BABOK 4.2,4.1.
Which technique are you least likely to use when packaging requirements?
a. Agile.
b. Requirements documentation.
c. Request for information (RFI).
d. Request for proposal (RFP).
a. Agile.
Agile emphasizes informal documentation.
A coverage matrix is:
a. A traceability relationship.
b. A test plan describing the amount of testing that will be done to ensure a requirement
is met.
c. The approach taken to ensure requirements are verified and validated.
d. A table or spreadsheet used to manage tracing.
d. A table or spreadsheet used to manage
tracing.
Commonly referred to as a traceability
matrix. BABOK 4.2.5.
The purpose of maintaining requirements for re-use is to:
a. Manage identification and documentation of requirements during business analysis
and the development effort.
b. Manage requirements as they are being shared by other teams doing business analysis
concurrently.
c. Manage knowledge of requirements following their implementation.
d. Allow many teams to test the requirements concurrently.
c. Manage knowledge of requirements
following their implementation.
BABOK 4.3.1.
Requirements are related to other requirements. This is called:
a. Requirements linkage.
b. Requirements traceability.
c. Requirements specificity.
d. Requirements coverage.
b. Requirements traceability.
BABOK 4.2.2.
A technique that is used to communicate requirements is:
a. Structured walkthrough.
b. Request for proposal (RFP).
c. Requirements documentation.
d. Signoff.
3. Structured walkthrough.
BABOK 4.5.5.
Requirements Managementand Communication Tasks
Manage Requirements Traceability
Maintain Requirements for Re-use
Prepare requirements Package
Communicate Requirements
Manage Solution Scope & Requirements
"TRPCS
Manage Requirements Traceability
Maintain Requirements for Re-use
Prepare requirements Package
Communicate Requirements
Manage Solution Scope & Requirements"
List the items in a typical Requirements Review
Purpose of the reviewed deliverable
Objectives of the review
Introduce participants
Background of project
Agreement - on actions or changes
Review- walkthrough the deliverable
Status - review status of deliverable
"POI BARS
Purpose of the reviewed deliverable
Objectives of the review
Introduce participants
Background of project
Agreement - on actions or changes
Review- walkthrough the deliverable
Status - review status of deliverable"
Prerequisites for a Structured Walkthrough
a) A complete requirements package.
b) A list of appropriate reviewers.
c) A meeting vehicle.
Often a fact-fmding document, used early in a selection process, when the requester is open to a number of possible options. It requests information
from vendors about potential solutions to a given need.
Request for Information
RFI
Used to request bids on a specific solution from a
number of potential vendors. An RFQ is less
formal than an RFP, and may be a subset of an
RFP.
Request for Quotation
RFQ
Used to request proposals to solve a specified business need, typically from a small number of potential vendors. The solutions could vary and are part of the proposal.
Request for Proposal
RFP
A plan for matching short- and long-term goals with how a solution will help reach those goals.
Product Roadmap
Also referred to as a "technology roadmap"
______ describes the desired functionality of software. These documents can be used to describe the business requirements, and the primary audience is business customers/users.
Business Requirements Document (BRD)
"BABOK 4.4.5 & Glossary
A Business Requirements Document is a requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business, rather than documenting business requirements)."
Like the BRD, an ______ describes solution functionality, Requirements but the intended audience is the development team. Typically more detailed than a BRD.
Software/System Requirements Specification (SRS)
BABOK 4.4.5
A document that describes non-functional requirements and/or supporting information, such as meta-data or "volumetrics" for data.
Supplementary Requirements Specification
BABOK 4.4.5
Often used in Enterprise Analysis or in project charters to document a high-level understanding of why and how a solution is needed. Often used when a solution is being developed iteratively.
Vision Document
BABOK 4.4.5
Documents or diagrams specified by a process, that show the output of a project or project phase.
Deliverable
"BABOK 4.4.4
A deliverable is a specific output of the business analysis process that the business analyst has agreed to produce. A requirement deliverable is used as a basis for solution design and implementation."
Documents, notes, diagrams, etc. that are byproducts of a project, used to record and organize information, and help in analyzing requirements.
Work Product
"BABOK 4.4.4
Examples of work products might be:
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"
Which of the following best describes what should be included in a requirements package?
a. Implementation transport strategy, requirements communications, methodology selection
b. Formal documentation such as a vision document or software requirements specification, presentation of high level functionality of the solution, requirements presented in a form of a model
c. Requirements modeling, SOW, organizational templates
d. Storyboards of key process for agile development, technical requirements for software development and environmental impact requirements
b. Formal documentation such as a vision document or software requirements specification, presentation of high level functionality of the solution, requirements presented in a form of a model
"BABOK 4.4.2
Possible forms for requirements packages may include:
Formal Documentation: Formal documentation is usually based on a template used by the organization, such as a Vision Document or Software Requirements Specification.
Presentation: Delivers a high-level overview of the functionality delivered by the solution.
Models: The requirements may be presented only in the form of a model, such as a process map, or captured on a whiteboard."
The ______ technique helps the BA manage any issues identified with requirements by stakeholders and ensures that those issues are resolved
Problem Tracking
BABOK 4.1.5.1 p 66
According to the BABOK, what is the purpose of managing requirements traceability?
To create and maintain relationships between business objectives, requirements, other team deliverables and solution components
BABOK 4.2.1 p 67
What is another term for forward traceability?
Allocation
BABOK 4.2.1 p 68
Traceability helps in requirements management such as risk, time, change and scope management. What is it also used to detect?
Missing Functionality
BABOK 4.2.2 p68
Requirements coverage is a term to define what aspect of traceability?
When business objectives are traced to detail requirements such as business rules, data elements, and Use Caes. If the business objective is not tied to a solution component(s) then the requirements are identified as missing.
BABOK 4.2.2 p 69
Requirements have dependancies and relationships. These help when determining the sequence in which requirements are to be addresses. What does the "necessity relationship describe?
This relationship exists when it only makes sense to implement a particular requirement if a related requirement is also implemented.
BABOK 4.2.4 p69
This matrix is used when there are relatively few requirements or when tracing is limited to high-level requirements
Coverage Matrix
BABOK 4.2.5.1 p 70
Communications and management of requirements assists in the understanding of changes. True or False
TRUE
Requirements traceability is the task associated with assigning resources to the project. True or False
FALSE
CCB stands for Change Control Board. True or False
TRUE
Organizational process assets are inputs to the Requirements Management and Communication KA. True or False
TRUE
List the Outputs for RMC KA
1. Requirements (Approved)
2. Requirements (Traced)
3. Requirements (Maintained and Reusable)
4. Requirements Package
5. Requirements (Communicated)
ATMRPC
All The Managers Require Proper Constraint
What are the elements for Manage Solution Scope & Requirements?
1. Solution Scope Management
2. Conflict and Issue Management
3. Presenting Requirements for Review
4. Approval.
BABOK 4.1.4
Which is NOT an example of Ongoing Requirements?
a. Contractual obligations
b. Implimented requirements
c. Service level agreements
d. Business processes
b. Implimented requireemtns
Satisfied requirements are those requirements that have been implemented in a solution. They are still requirements as long as the organization has the need. The purpose of this task is to acknowledge the desirability of maintaining satisfied requirements to assist future system enhancements and facilitate re-use of requirements on other projects.
An established checkpoint, against which requirements changes are compared. Each time requirements are approved, they are ______.
Baselined
BABOK 4.1.2
Requirements may be baselined following approval. Any changes to requirements after baselining, if changes are permitted, involves use of a change control process
and subsequent approval.
Identifies the "lineage" of a requirement by tracing back to the business need.
Derivation
BABOK 4.2.2
Requirements traceability identifies and documents the lineage of each requirement, including its backward traceability (derivation), its forward traceability (allocation), and its relationship to other requirements.
Traces a requirement through development, testing, and implementation.
Allocation
BABOK 4.2.2
Requirements traceability identifies and documents the lineage of each requirement, including its backward traceability (derivation), its forward traceability (allocation), and its relationship to other requirements.
What are the three types of Requirements Packages/Package Components
Formal Documentation
Presentation
Models
BABOK 4.4.2
Possible forms for requirements packages may include:
Formal Documentation: Formal documentation is usually based on a template used by the organization, such as a Vision Document or Software Requirements Specification.
Presentation: Delivers a high-level overview of the functionality delivered by the solution.
Models: The requirements may be presented only in the form of a model, such as a process map, or captured on a whiteboard.
The purpose of this task is to obtain approval from authorized stakeholders of the overall solution scope and requirements to be implemented.
4.1 Manage Solution Scope & Requirements
4.2 Manage Requirements Traceability
4.3 Maintain Requirements for Re-use
4.4 Prepare requirements Package
4.5 Communicate Requirements
4.1 Manage Solution Scope & Requirements
This task involves securing approval of requirements from those stakeholders who have the appropriate authority, and managing issues that emerge during elicitation and analysis. Approval of requirements may be sought at the end of a project phase or at a number of intermediate points in the business analysis process.