CBAP 1 to 500 Flashcards
cbap (500 cards)
1
Q
What is the definition of business analysis?
A
The set of tasks and techniques used to work as a liaison among stakeholders in order to understand the structure, policies and operations of an organization, and to recommend end solutions that enable the organization to achieve its goals.
2
Q
What is the definition of a business analyst?
A
Any person who performs business analysis activities no matter what their job title or organizational role may be.
3
Q
A business analyst performs business analysis in order to do what?
A
Align the needs of the business units with the capabilities delivered by information technology.
4
Q
What is the definition of a solution?
A
A set of changes to the current state of an organization that are made in order to enable that organization to meet a business need, solve a problem, or take advantage of an opportunity.
5
Q
What is the definition of a requirement?
A
A condition or capability needed by a stakeholder to solve a problem or achieve an objective OR A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract, standard, specification or other formally imposed documents OR A documented representation of a condition or capability
6
Q
According to the BABOK 2.0, what type of analysis generates BUSINESS requirements?
A
Enterprise Analysis
7
Q
What is a BUSINESS requirement, according to the BABOK 2.0?
A
A high level statement of the goals or objectives or needs of the enterprise
8
Q
What is a STAKEHOLDER requirement, according to the BABOK 2.0?
A
A statement of the needs of a particular stakeholder or class of stakeholders
9
Q
According to the BABOK 2.0, what type of analysis generates STAKEHOLDER requirements?
A
Requirements Analysis
10
Q
What is a SOLUTION requirement, according to the BABOK 2.0?
A
A characteristic of the solution that meets the business requirements and stakeholder requirements.
11
Q
SOLUTION Requirements are comprised of what two types of requirements?
A
Functional and Non-functional requirements
12
Q
According to the BABOK 2.0, when are SOLUTION requirements gathered?
A
Requirements Analysis
13
Q
What is a TRANSITION requirement, according to the BABOK 2.0?
A
A requirement that describes the capabilities the solution must have to facilitate the transition from current to future state of the enterprise, but will not be needed after the transition
14
Q
According to the BABOK 2.0, when are TRANSITION requirements gathered?
A
Solution Assessment and Validation
15
Q
What is the definition of a knowledge area?
A
They define what a practitioner of business analysis needs to understand and the tasks that a practitioner must be able to perform
16
Q
How many Knowledge Areas are identified in the BABOK 2.0 and what are they?
A
There are 7: Business Analysis Planning and Monitoring Elicitation Enterprise Analysis Solution Assessment and Validation Requirements Analysis Requirements Management and Communication Underlying Competencies
17
Q
What is the objective of the Business Analysis Planning and Monitoring knowledge area?
A
To show how the BA determines which activities are necessary in order to complete a business analysis effort
18
Q
What is the objective of the Elicitation knowledge area?
A
To show how the BA works with stakeholders to identify and understand their needs and concerns, and understand the environment in which they work
19
Q
What is the purpose of elicitation?
A
To ensure that the stakeholders_ underlying needs are understood, rather than their stated or superficial desires
20
Q
What is the objective of the Requirements Management and Communication knowledge area?
A
To define how a BA manages conflict, issues and changes in order to ensure the stakeholders and the project team remain in agreement on the solution scope
21
Q
What is the objective of the Enterprise Analysis knowledge area?
A
To define how a BA identifies a business need, refines and clarifies the need and defines the solution scope that can be feasibly implemented
22
Q
What is the objective of the Requirements Analysis knowledge area?
A
To define how a BA prioritizes and progressively elaborates stakeholder and solution requirements in order to enable the project team to implement a solution
23
Q
What is the objective of the Solution Assessment and Validation knowledge area?
A
To define how the BA assesses proposed solutions to determine which solution fits best the business need, indentifies gaps in solutions, determines necessary workarounds or changes to the solution
24
Q
What is the objective of the Underlying Competencies knowledge area?
A
To describe the behaviors, knowledge and other characteristics that support the effective performance of business analysis
25
What are the characteristics of a task?
Accomplishes a result that creates value Is complete Is a necessary part of the purpose of the knowledge area
26
True or False The BA is a stakeholder in all business analysis activities?
TRUE
27
What is the definition of a Domain Subject Matter Expert (SME)
Any individual with in-depth knowledge of a topic relevant to the business need or solution scope
28
What is the definition of a customer?
A stakeholder outside the boundary of a given organization/unit who makes use of products/services delivered by the organization
29
What is the definition of an end user?
A stakeholder who interacts directly with the solution
30
What is an Implementation Subject Matter Expert (SME)
Individuals responsible for designing and implementing potential solutions and of providing expertise in design and construction of the solution
31
What do Organizational Change Professionals do, according to the BABOK 2.0?
They are responsible for facilitating acceptance and adoption of new solutions and overcoming resistance to change
32
What's a usability professional do?
A usability professional is responsible for external interaction design of technological solutions and for making the design as simple to use as feasible
33
An output is the necessary result of the work described in a WHAT?
Task
34
What is a technique?
It provides additional information on different ways that a task may be performed or forms the output of the task may take
35
How many underlying competencies are there and what are they?
There are 6 Analytical Thinking and Problem Solving Behavioral Characteristics Business Knowledge Communication Skills Interaction Skills Software Applications
36
What are the tasks associated with the Business Analysis Planning and Monitoring knowledge area?
There are 6 Conduct Stakeholder Analysis Plan BA Approach Plan BA Activities Plan BA Communication Plan Requirements Mgmt Process Manage BA Performance
37
What are the inputs to the Business Analysis Planning and Monitoring knowledge area tasks?
There are 5 Analysis performance metrics Business Needs Enterprise Architecture Expert Judgment Organizational process assets
38
What are the inputs to plan the Business Analysis Approach?
Business Need Organizational Process Assets Expert Judgment
39
The understanding of the business need in planning the Business Analysis approach helps to determine which approach to take. What are the two types of approaches?
Plan-driven Change-driven
40
What are the differences between plan and change-driven analysis approaches?
Plan-driven focuses on minimizing up-front uncertainty (risk reduction), fully defined requirements, fully detailed documentation and controlled change. Change-driven focuses rapid delivery of functionality in iterations, higher risk, prioritized high-level requirements that reside in a backlog, detailed documentation only as necessary and later in the process usually after implementation, enhanced collaboration
41
What are some factors that impact project complexity?
Number of stakeholders Number of business areas affected Amount and type of risk Uniqueness of requirements Number of tech resources required
42
What are the recommended techniques to assist in planning the business analysis approach?
There are 3 Decision Analysis Process Modeling Structured Walk-thrus
43
What is the definition of the business analysis approach?
A definition of the approach that will be taken for business analysis in a given initiative.
44
A business analysis approach specifies what?
Roles, deliverables, analysis techniques, timing/frequency of stakeholder interaction
45
Stakeholder Analysis is part of what knowledge area?
Business Analysis Planning and Monitoring
46
What does enterprise architecture do?
Describes the organizational units that exist and their interactions with other organizational units
47
What are organizational process assets?
Policies and procedures, suggested methodologies, templates and guidelines
48
Can change-driven analysis approaches eliminate risk? Why?
No, because late identification of stakeholders or needs can alter the previous outcomes
49
What are the elements of stakeholder analysis?
There are 4 Identification Complexity Attitude and Influence Authority Levels for BA Work
50
What are the complexity factors regarding stakeholder groups?
Number and variety of stakeholder groups Number of interfacing business processes and automated systems
51
What are the factors of stakeholder attitude directed at?
There are 5 Business goals approach Business Analysis Collaboration Sponsor Team members
52
What are the factors of influence by stakeholders on a project?
Influence on the project, organizational, project health and other stakeholders
53
Stakeholder authority over business analysis takes what forms?
Approval of deliverables Inspection/Approval of requirements Approval of requirements process Traceability Veto of proposed requirements or solutions
54
What is a RACI matrix?
It describes the roles of individuals involved in business analysis activities
55
What do the initials RACI stand for?
Responsible Accountable Consulted Informed
56
What is a stakeholder map?
A visual diagram that depicts the relationships of stakeholders to solutions
57
What are the two forms of stakeholder maps?
Matrix and Onion Diagram
58
What does an onion diagram depict?
The level of stakeholder involvement with the solution
59
What is the purpose of planning analysis activities?
Determining activities to be performed Estimation Identify Management tools to measure progress
60
What are the inputs to planning the business analysis activities?
There are 4 Business Analysis Approach Business Analysis Performance Assessment Organizational process assets Stakeholder List
61
What does a Business Analysis Performance Assessment define?
Prior analysis experience is used to determine effort for analysis activities
62
What are the elements of planning business analysis activities?
There are 3 Geographic Distribution of Stakeholders Type of Project Analysis Deliverables
63
What are the two types of geographic distribution of stakeholders?
Collocated Dispersed
64
Name 2 of the 7 project/initiative types
Feasibility studies Process improvement Organizational change: New software dev Outsourced new software dev Software Maintenance or enhancement Software package selection
65
What are the methods for identifying analysis deliverables?
There are 3 Interviews/facilitated session with stakeholders Review of project docs Review of organizational assets
66
What 3 tasks consume the Define Business Analysis Plan task?
Planning the BA Communication Planning Requirement Management Process Manage BA Performance
67
What 5 knowledge areas consume the Business Analysis Plan?
Elicitation Enterprise Analysis Requirement Management and Communication Requirement Analysis Solution Assessment and Validation
68
What is the definition of a milestone?
A significant event that measures the progress of a project and compares actual progress to earlier estimates
69
Decomposition of the project tasks often using a WBS is the definition of what?
Functional Decomposition
70
What is the purpose of Planning Business Analysis Communication?
To describe the proposed structure and schedule for Communications re: business analysis activities
71
Appropriate audience, appropriate delivery method, approach and physical location are all considerations of what?
Planning the BA Communication
72
The BA Communication Plan is consumed by what 2 tasks?
Prepare Requirements Package Communicate Requirements
73
What are the elements of planning the Business Analysis Communication Plan?
Time Task Completion Contracts Formal/Informal Authority
74
What are the factors that can increase or decrease the need for formal Communications on a project?
Project Size Domain Complexity Inclusion of new technologies Delivery to external vendors/suppliers Regulatory Concerns Stakeholder Request
75
One of the most recommended on approaches to requirements Communication is what?
Structured Walk-thru
76
What describes how, when and why the business analyst will work with stakeholders?
The Business Analysis Communication Plan
77
What is the purpose of planning the Requirements Management Process?
To describe the approach that will be used to approve requirements for implementation and manage changes to the solution scope
78
The Requirements Management Process includes what factors?
Approving stakeholders Requirements traceability Change process Requirement Attributes
79
What are the inputs to planning the Requirements Management Process?
There are 3 Business Analysis Approach Business Analysis Plan Organizational Process Assets
80
What tasks consume the Requirements Management Plan?
There are 5: Manage BA Performance Manage Requirements Traceability Conduct Elicitation Manage Solution Scope and Requirements Prioritize Requirements
81
A method of storing requirements that are approved, under development, and under review describes what term?
Repository
82
What provides information about requirements?
An attribute
83
What focuses on what requirements should be investigated first?
Requirements Prioritization
84
Requirements prioritization assesses priority based on what?
Risk
85
Is a component Communication on, cardinal, optional or an attribute?
An Entity Relationship Diagram has four main components: Entities: an entity represents a group of uniquely identifiable people, places, things or concepts about which a business area needs information. (e.g., Customers, Products, Employees, Invoices, etc.). Attributes: an attribute is one of the individual pieces of information that describes an entity (e.g., Customer Name, Product Price, Employee Number, and Invoice Date). Unique Identifiers: a unique identifier is an attribute, or a combination of attributes, that will uniquely identify each separate occurrence of an entity (e.g., Customer Number, Invoice Number, and Social Insurance Number). Relationships: a relationship is a significant business association between two entities. It reflects how data from one entity needs to be used in conjunction with data from another entity. It also reflects a business rule of the enterprise. At each end of a relationship line, a notation indicates the minimum and maximum number of occurrences of one entity that may be associated with the other entity. This notation is known as the cardinality of the relationship. A variety of notations are in popular use, all expressing the same general concept. The possible permutations of minimum and maximum cardinality are: Zero or one Zero or more One and only one One or more
86
Regarding quality assurance, should the BA find defects in the system or provide input into how to test the system?
The Quality Assurance process includes development of a test plan/strategy for the solution, execution of the test plan, and incident (defect) tracking of problems. The Business Analyst will assist these activities by providing detailed business knowledge and helping to find the cause of any problems
87
What is the Final task in requirements Communication? A. answer questions from requirements final review, B. make a requirements final review C. present the requirements to senior management D. obtain requirements signoff
D. obtain requirements signoff
88
What is the benefit of feature list decomposition?
A feature is a service that the solution provides to fulfill one or more stakeholder needs. Features are high-level abstractions of the solution that must later be expanded into fully described functional and supplemental requirements. They allow for early priority and scope management and for validating the stakeholders\_ view of the solution.
89
Functional decomposition identifies what?
Functional decomposition identifies the high-level functions of an organization or proposed solution and then breaks down those processes into sub-processes and activities. This can be done as part of a systems development or business process analysis project. The goal is to break functions down into smaller pieces to allow for analysis of the detail processes and to ensure coverage of all significant processes
90
In the Business Architecture planning endeavor the BA should determine what?
Appropriate framework and approach
91
Who are the primary consumers of requirements?
The project team, who will use them in the design and development of the system
92
Functional requirements can be expressed in what forms?
Use cases and text
93
The business domain can be described with what types of diagrams?
Activity Diagrams, Data Flow Diagrams, Flowcharts, Sequences Diagrams, State Machine Diagrams
94
The Component Business Model describes what?
Component Business Model identifies a basic building block of the business, and includes the people, processes and technology needed by the component to deliver value to the customer.
95
Enterprise architecture encompasses what 3 elements?
People, processes, technology
96
What do the letters of the CRUD Matrix stand for?
Create read, update delete rights to users and groups. Good in software system development. Not applicable to business process analysis.
97
When a conflict arises between stakeholders on one or more documented requirements, the first thing that needs to take place is what?
....to record the conflict in the Requirements Issues Log.
98
What are the Components of an ERD?
An Entity Relationship Diagram (ERD) is a visual representation of a data structure. Because they describe things that are significant to the enterprise (e.g., Customers, Products, Employees, Invoices, etc.), ERDs are useful in describing the structure of the business itself, and many of the rules by which it is governed.
99
What is described in the Enterprise Architecture people processes?
Each model identifies a basic building block of the business, and includes the people, processes and technology needed by the component to deliver value to the customer.
100
What are the measures on a balanced scorecard?
The balanced scorecard (Robert Kaplan and David Norton 1996) provides an effective technique to frame strategic goals. In this model, goals are partitioned into four dimensions: financial, customer, internal operations, and learning and innovation.
101
What does the abbreviation PLC stand for?
Project Life Cycle
102
What is the minimum structural set of requirements of a presentation whether it is formal or informal?
Introduction of parties attending presentation Statement of presentation objectives Project background Presentation/review of deliverable Agreement of actions/changes required Review of deliverable status (e.g., signed off, not signed off, etc.)
103
What is the ISO 9241-11 definition of usability?
The extent to which a product can be used by specified users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context of use.
104
What does a logical model represent?
Entities that are in the problem domain and the relationships between them
105
When are logical models used by BAs?
To represent requirements of a business area
106
What is the difference between a view and a model decomposition?
A view is not exclusive and its requirements may be referenced in all views that are relevant
107
What is a view with regard to modeling?
The capture of requirements from a specific perspective
108
Modeling benefits are?
Simplification of reality to allow focus Comprehension of complexity Explanation from varying perspectives Ensures all aspects are considered Translate easily into solution design
109
Modeling is often used when?
When the problem domain is well known When the solution is easy to construct When there is little collaboration needed When there is little need for ongoing maintenance When the scope is unlikely to grow
110
What is the definition of a model?
A template for expressing requirements that may combine textual elements, matrices, and diagrams
111
Authorization resources, process identification, impact assessment and correct wording are all aspects of what?
Change Management
112
What does a Change Control Board do?
Considers requested changes and decides on the merits of the request prior to approving or declining it.
113
What are the aspects to a change request that are important?
Cost and time to implement Benefits and Risk Course of action and alternate solutions Coordinated prioritization
114
What major methodology utilizes a project/product backlog?
Agile or Scrum
115
Organizational culture, Stakeholder preference, complexity, organizational maturity and availability of resources are all factors used to do what?
Perform tailoring exercises
116
What are the techniques used in planning requirements management?
There are 3 Decision analysis Problem tracking Risk analysis
117
What is the output of planning requirements management activities?
The Requirements Management Plan
118
What does the Requirements Management Plan describe?
Traceability approach Definition of requirement attributes Requirement prioritization process Requirement change process
119
Metrics are used to do what?
Measure business analysis performance throughout the lifecycle.
120
There are 4 inputs to the Manage BA Performance activity. What are they?
Business Analysis Performance Metrics Business Analysis Plan Organizational Performance Standards Requirements Management Plan
121
The Manage BA Performance activity is part of what knowledge area?
Business Analysis Planning and Monitoring
122
What are the 6 activities that occur within the Business Analysis Planning and Monitoring knowledge area?
Plan Business Analysis Approach Conduct Stakeholder Analysis Plan Business Analysis Communication Plan Requirements Management Process Manage Business Analysis Performance
123
What are the 4 activities that occur within the Elicitation knowledge area?
Prepare for Elicitation Conduct Elicitation Document Elicitation Results Confirm Elicitation Results
124
What are the activities that occur within the Requirements Management & Communication knowledge area?
There are 5 Manage Solution Scope and Requirements Manage Requirements Traceability Maintain Requirements for Re-use Prepare Requirements Package Communication of Requirements
125
What are the activities that are part of the Enterprise Analysis knowledge area?
There are 5 Define the Business Need Assess Capability Gaps Determine Solution Approach Define Solution Scope Define Business Case
126
What are the activities contained within the Requirements Analysis knowledge area?
There are 6 Prioritize Requirements Organize Requirements Specify and Model Requirements Define Assumptions and Constraints Verify Requirements Validate Requirements
127
What are the activities that are part of the Solutions Assessment and Validation knowledge area?
There are 6 Assess Proposed Solution Allocate Requirements Assess Organizational Readiness Define Transition Requirements Validate Solution Evaluate Solution Performance
128
What are the Underlying Competencies described in the BABOK?
There are 6 Analytical Thinking and Problem Solving Behavioral Characteristics Business Knowledge Communication Skills Interaction Skills Software Applications
129
How many different techniques does the BABOK 2.0 describe?
34
130
The BA Performance Assessment is used by what downstream task as an input?
Plan BA Activities
131
The BA Process Assets are children of what?
Organizational Process Assets
132
What does the Plan BA Activities task consume as an input?
BA Performance Assessment
133
There are several elements of the Manage BA Performance activity. What are they?
Performance Measures Performance Reporting Preventive and Correction Action
134
What are performance measures used for?
To set expectations regarding what constitutes effective business analysis work in the context of an organization or project
135
What are some performance measures?
Deliverable due date deliverables Frequency of change Number of review cycles
136
The business analyst should assess the performance measures to determine what?
Where problems in execution of business analysis activities are occurring or opportunities for improvement exist
137
There are several techniques defined for use in the Manage Business Analysis Performance activity. What are they?
There are 7 Interviews Lessons Learned Metrics and KPIs Problem Tracking Process Modeling Root Cause Analysis Survey/Questionnaire
138
What is root cause analysis?
An investigation into the underlying cause of a failure or problem
139
What is Variance Analysis?
A technique used to analyze discrepancies between planned and actual performance and to determine the magnitude of the differences
140
What knowledge are is Variance Analysis used in and why?
Business Analysis Planning and Monitoring. It is used as part of the Manage Business Analysis Performance activity to manage performance in an ongoing project
141
What is a KPI?
Key Performance Indicator These are metrics used to help an organization define and evaluate how successful it is, typically in terms of making progress towards its long-term organizational goals
142
Define elicit.
To draw forth, call forth or bring out
143
What phases of the SDLC are requirements elicited in?
Throughout the SDLC
144
Name 3 of the 9 elicitation techniques.
3 of the following: Brainstorming Document Analysis Focus Groups Interface analysis Interviews Observations Prototyping Requirements Workshop Survey/Questionnaire
145
What are the tasks described in the Elicitation knowledge area?
There are 4 Prepare for Elicitation Conduct Elicitation Activity Document Elicitation Results Confirm Elicitation Results
146
What are the inputs to Elicitation?
Business Case Business Need Organizational process assets Requirements Management Plan Solution Scope Stakeholder List
147
What are the outputs of Elicitation?
There are 4 Elicitation Results Scheduled Resources Stakeholder Concerns Supporting Materials
148
What is the purpose of preparing for elicitation?
To ensure that all resources are organized and scheduled for conducting the elicitation exercise
149
What are two things used to capture elicitation knowledge?
Data Dictionary & Glossary
150
What does a glossary typically contain?
Key Domain terminology and business definitions
151
What is metadata?
Data about data
152
What are the three elements of elicitation discussed in the BABOK?
Tracing requirements Capturing Requirements Attributes Metrics
153
What is the input to the Document Elicitation Results activity?
The elicited requirements
154
According to the BABOK 2.0, elicited requirements may undergo analysis directly with prototyping, without documentation. True or False
True. Prototyping may be used to perform analysis on requirements without the need to document
155
What tasks consume the documented elicited requirements?
There are 5 Confirm Elicitation Results Prioritize Requirements Define the Business Need Specify and Model Requirements Define Transition Requirements
156
What else does elicitation produce?
Stakeholder concerns
157
What tasks consume stakeholder concerns?
Confirm Elicitation Results Define Business Case Define Assumptions and Constraints Assess Org Readiness
158
What are some examples of stakeholder concerns?
Risk, assumptions, constraints, etc.
159
What is the purpose of confirming elicitation results?
To validate that the stated concerns that are expressed by the stakeholder match the stakeholders' understanding of the problem and needs
160
What are the inputs to the Confirm Elicitation Results task?
Requirements and Stakeholder Concerns, both unconfirmed
161
What are two techniques that are used to confirm elicitation results?
Interviews and Observation
162
What are the outputs of the Confirm Elicitation Results task?
Requirements and Stakeholder Concerns, both confirmed
163
What tasks consume CONFIRMED requirements?
There are 4 Define Business Need Prioritize Requirements Specify and Model Requirements Define Transition Requirements
164
What tasks consume CONFIRMED stakeholder concerns?
There are 3 Define Business Case Define Assumptions and Constraints Assess Organizational Readiness
165
What does the Requirements Management and Communication knowledge area describe?
The activities and considerations for managing and expressing requirements to a broad audience
166
Communication of requirements does what for stakeholders?
Brings them to a Communication on understanding
167
Performance of all Requirements Management and Communication activities is governed by what?
Business Analysis plan
168
What are the tasks/activities of the Requirements Management and Communication knowledge area?
There are 5 Manage Solution Scope Manage Requirements traceability Manage Requirements for Re-Use Prepare Requirements Package Communication Requirements
169
What are the inputs into the Requirements Management and Communication knowledge area tasks/activities?
There are 6 BA Communication Plan Organizational process assets Requirements Requirements Management Plan Solution Scope Stakeholder List/Responsibilities
170
What are the outputs from the tasks/activities in the Requirements Management and Communication knowledge area?
There are 5 Approved Requirements Traced Requirements Communicated Requirements Maintained and Reusable Requirements Requirements Package
171
What is the purpose of the Manage Solution Scope and Requirements task/activity?
To obtain consensus among stakeholders on overall solutions scope
172
What occurs during the Manage Solution Scope and Requirements task/activity?
Securing approval of requirements Management of issues from elicitation
173
What is base lining?
In essence, the approval of a set of requirements (in this context) that allows no change to occur to the set without a way to control change
174
What should the requirements do in order to be approved?
Support the solution scope
175
Why is the solution scope carried forward into the Requirement Management and Communication knowledge area?
To ensure that the requirements conform to the approved solution scope
176
How is the solution scope used to manage change in the Requirements Management and Communication knowledge area?
All requested changes to requirements are assessed against the solution scope to ensure of alignment
177
The Requirements Management Plan is an input to the Requirements Management and Communication knowledge area. Why?
It is used to define the process to be followed in managing the solution scope and the requirements
178
What are the elements of the Manage Solution Scope & Requirements task/activity?
Solution Scope Management Conflict and Issue Management Presenting Requirements for Review Approval
179
What's the difference between a formal and informal requirements presentation to stakeholders?
One is formal written specification with possible walk-thru and the other is possibly verbal or email Communication
180
What are the techniques used to Manage Solution Scope and requirements?
Base lining and Signoff
181
What is the purpose of managing requirements traceability?
To create and maintain relationships between business objectives, requirements, other deliverables
182
What does requirements traceability define?
Lineage of requirements, including backwards and forwards traceability.
183
What is derivation?
Backwards traceability
184
What is allocation?
Forward traceability
185
What is the value of traceability?
It helps ensure conformation to the overall solution for each individual requirements and assists is scope and change Management
186
What is used to potentially find missing functionality or identify unrequested functionality?
Requirements traceability
187
What is the overall goal of requirements traceability?
To requirements, solution components are linked directly or indirectly back to the original business objectives
188
What are the inputs to the Manage Requirements Traceability task/activity?
Requirements and the Requirements Management Plan
189
What task/activity consumes traced requirements?
Manage Solution Scope and Requirements
190
Why are relationships an element of Manage Requirements Traceability?
Knowing dependent relationships between requirements can help determine the sequence of when each will be addressed
191
What are the 5 type of relationships between requirements?
Necessity Effort Subset Cover Value
192
What is the Cover type of requirement relationship?
When a requirement completely includes another requirement. It is a subset in which the top-level requirement is the sum of the sub-requirements
193
What is the Value type of requirement relationship?
When including a requirement affects the desirability of a related requirement (increase or decrease)
194
Why is traceability useful in performing impact analysis?
Because when requirements change and they are linked to other requirements, the related items are identified as a result of the link, as well as potential changes in the relationship
195
What is a Configuration Management System
A specialized tools that is generally used to trace large volumes of requirements
196
What is a coverage matrix?
A table or spreadsheet used to manage tracing. Also called a trace matrix. Used when there are few requirements.
197
What is the purpose of the Maintain requirements for Re-Use task/activity?
To manage the knowledge of requirements following their implementation
198
What occurs in the Maintain Requirements for Re-Use task/activity?
To identify requirements that are good candidates for long-term usage
199
What are the two inputs to Maintain Requirements for Re-Use task/activity?
Organizational process assets and Requirements
200
Reusable requirements are consumable where?
Enterprise Architecture and Future Initiatives
201
How are reusable requirements used by Enterprise Architecture and Future Initiatives
Enterprise Architecture would typically include term requirement types into a data dictionary. Other requirement types can be used across projects in future initiatives to replicate portions of functionality that is Communication on to multiple areas
202
What are ongoing requirements?
Those requirements that an organizational unit is required to be able to meet on a continuous basis
203
What is an example of an ongoing requirement?
Contractual obligations (SLAs) Quality standards Business rules/standards
204
What is the purpose of Prepare Requirements Package?
To select and structure a set of requirements in an appropriate fashion to ensure that the requirements are effectively communicated to, understood by, and usable by a stakeholder group or groups
205
What is the proper level of detail to present for requirements in a requirements package
That which is needed for the team to understand the content, and no more
206
What are some reasons for creating a requirements package?
early assessment of quality and planning evaluation of possible alternatives formal reviews and approvals inputs to solution design conformance to contractual and regulatory obligations maintenance for re-use
207
The Prepare Requirements Package task is part of what knowledge area?
Requirements Management & Communication
208
Misunderstanding of requirements will adversely affect what?
Solution Implementation
209
What are the forms of requirements packages?
There are 3: Formal Documentation Presentation Models
210
What are the inputs to the Prepare Requirements Package task?
There are 4: Business Analysis Communication Plan Org Process Assets Requirements Requirements Structure
211
What is the value of the Business Analysis Communication Plan as an input to Prepare Requirements Package?
It will describe the stakeholder groups, their communication needs, and define whether a single requirements package or multiple requirements packages are required.
212
What task consumes the requirements package?
Communicate Requirements
213
What are the elements of Prepare Requirements Package?
There are 2: Work Products and Deliverables Format
214
What is the definition of a work product?
A document or collection of notes or diagrams used by the business analyst during the requirements development process
215
What are 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
216
What is the definition of a deliverable?
A deliverable is a specific output of the business analysis process that the business analyst has agreed to produce
217
What is the usage for a requirements deliverable?
As a basis for solution design and implementation
218
What must the analyst understand when deciding whether to use a deliverable or requirements deliverable?
Needs of the audience Level of detail that needs to be communicated Which deliverables to include in each presentation package
219
Format considerations in the requirements package are for what purpose?
Delivery of a cohesive, effective message to one or more audiences who will participate in the requirements review process
220
What are the techniques of the Prepare Requirements Package task?
There are 2: Requirements Documentation Requirements for Vendor Selection
221
What are some common forms of requirements documentation?
BRD Product Roadmap SRS Supplementary Requirements Spec Vision Document
222
What are the typical forms of documentation when presenting requirements to vendors?
There are 2: Request for Information (RFI) Request for Quote (RFQ) / Request for Proposal (RFP).
223
What is an RFI?
Generally used when the issuing organization is open to a number of alternative solutions and is seeking information to evaluate possible options
224
What is an RFQ/RFP?
Used when the issuing organization understands the nature of the solution options available to it and is seeking vendors who can implement an option. An RFQ generally follows a less formal review and selection process than an RFP.
225
Business analysts must develop what based on the business requirements before looking at available products?
Evaluation Criteria
226
What is the purpose of the Communicate Requirements task?
Communicating requirements is essential for bringing stakeholders to a common un\_derstanding of requirements.
227
Does the analyst utilize soft, technical or both types of communication skills when communicating requirements?
Both
228
What are the inputs to the Communicate Requirements task?
There are 3: BA Communication Plan Requirements Requirements Package
229
The Requirements Package is the output of what task?
Prepare Requirements Package
230
What is the output of the Communicate Requirements task?
Requirements - Communicated
231
Which task or tasks consume communicated requirements?
Manage Solution Scope and Requirements
232
With regards to communicating the requirements, what does the BA Communication Plan provide?
What requirements should be communicated Which stakeholders should receive the communication When communication should occur What the form of the communication should be
233
What are the elements of the Communicate Requirements task?
There are 2: General Communication Presentations
234
What knowledge area does the Communicate Requirements task reside in?
Requirements Mgmt and Communication
235
When does requirements communication typically occur?
It occurs throughout the project on an iterative basis
236
Must all project requirements communication be formal?
No, informal communication is also valuable and may lead to the creation of additional requirements
237
What are so common areas that lead to the creation of additional requirements as a result of communication?
Enterprise analysis Elicitation Requirements Analysis Solution Assessment and Validation
238
The formality of presentations used to communicate requirements is driven by what factors?
Stakeholder needs and objectives of the communication
239
A presentation may be used:
to ensure that internal project quality standards have been adhered to
240
What are the techniques of the Communicate Requirements?
There are 2: Requirements Workshops Structured Walkthrough
241
What is the difference between a structured walk through and a requirements workshop?
A requirements workshop is a structured meeting in which a carefully selected group of stakeholders collaborate to define and or refine requirements under the guidance of a skilled neutral facilitator A structured walkthrough is an organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance
242
Communicated Requirements mean what to stakeholders?
That they understand them and the current state the requirements are in
243
What does the Enterprise Analysis Knowledge Area describe?
The business analysis activities necessary to identify a business need, problem, or opportunity, define the nature of a solution that meets that need, and justify the investment necessary to deliver that solution
244
Enterprise Analysis outputs provide context to what?
Requirements analysis and solution identification
245
Is enterprise the starting point or a result of creating a new project?
The starting point?
246
What is the difference between a requirements defined during enterprise analysis and requirements analysis?
The requirements that are outputs of enterprise analysis are higher level requirements that must be in place to achieve the business goals and objectives.
247
The Enterprise Analysis knowledge area describes what types of activities for organizations?
To analyze the business situation in order to fully understand business problems and opportunities. To assess the capabilities of the enterprise in order to understand the change needed to meet business needs and achieve strategic goals. To determine the most feasible business solution approach. To define the solution scope and develop the business case for a proposed solution. To define and document business requirements (including the business need, required capabilities, solution scope, and business case).
248
There are 7 inputs to the Enterprise Analysis Knowledge Area. What are they?
Assumptions and Constraints Business Goals and Objectives Enterprise Architecture Org Process Assets Requirements [Stated] Solution Performance Assessment Stakeholder Concerns
249
How many tasks are part of the Enterprise Analysis knowledge area?
There are 5. They are: Define Business Need Assess Capability Gaps Determine Solution Approach Define Solution Scope Define Business Case
250
What are the outputs of the Enterprise Analysis knowledge area?
There are 5: Business Case Business Need Required Capabilities Solution Approach Solution Scope
251
What is the purpose of the Define Business Need task?
Identify and define why a change to organizational systems or capabilities is required
252
Why is the definition of the business need so critical?
It defines the problem that the business analyst is trying to find a solution for. The way the business need is defined determines which alternative solutions will be considered, which stakeholders will be consulted, and which solution approaches will be evaluated
253
What are the inputs needed to define the business need?
Business Goals and Objectives Requirements [Stated]
254
The business need is consumed by what task or tasks?
Plan Business Analysis Approach Conduct Stakeholder Analysis Prepare for Elicitation Conduct Elicitation Assess Capability Gaps Determine Solution Approach Define Solution Scope Define Business Case Prioritize Requirements Verify Requirements Requirements Mgmt and Communication Knowledge Area
255
What are the four ways to generate a business need during Enterprise Analysis?
From Top Down From Bottom Up From Middle Mgmt From External Drivers
256
Business goals and objectives describe what?
The ends that the organization is seeking to achieve. Goals and objectives can relate to changes that the organization wants to accomplish, or current conditions that it wants to maintain
257
Goals are defined as what?
Longer-term, ongoing, and qualitative statements of a state or condition that the organization is seeking to establish and maintain
258
High-level goals can be decomposed to break down what?
General strategy into distinct focus areas that may lead to desired results, such as increased customer satisfaction, operational excellence and/or business growth
259
A common test for assessing objectives is to ensure that they are SMART. What do the letters in this acronym stand for?
Specific _ describing something that has an observable outcome Measurable _ tracking and measuring the outcome Achievable _ testing the feasibility of the effort Relevant _ in alignment with the organization\_s key vision, mission, goals Time-bounded \_the objective has a defined timeframe that is consistent with the business need
260
In order to define a business need, what must occur?
An issue must be investigated to ensure that there is in fact an opportunity for improvement if the issue is resolved
261
When investigating the business, the analyst should consider what?
Adverse impacts the problem is causing Expected benefits from any potential solution How quickly the problem could potentially be resolved The underlying source of the problem
262
As a possible solution, what should always be considered?
Doing nothing
263
What is a desired outcome?
It describes the business benefits that will result from meeting the business need and the end state desired by stakeholders. Proposed solutions must be evaluated against desired outcomes to ensure that they can deliver those outcomes
264
What are the techniques of the Define Business Need task?
Benchmarking Brainstorming Business Rules Analysis Focus Groups Functional Decomposition Root Cause Analysis
265
What is Benchmarking?
Understanding what competing organizations and peers are doing allows the organization to remain at a comparable level of service or identify opportunities to increase efficiency
266
What is the purpose of the Assess Capability Gaps task?
To identify new capabilities required by the enterprise to meet the business need
267
Why should capability gaps be identified?
They that prevent it from meeting business needs and achieving desired outcomes
268
What are the inputs of the Assess Capability Gaps task?
Business Needs Enterprise Assessment Solution Performance Assessment
269
The Assess Capability Gaps task is part of what knowledge area?
Enterprise Analysis
270
What is the output of the Assess Capability Gaps task?
Required Capabilities
271
What are the tasks that consume Required Capabilities?
Determine Solution Approach Define Solution Scope Prioritize Requirements Verify Requirements Requirements Mgmt and Communication knowledge area
272
What does a Solution Performance Assessment define?
Shortcomings, problems or limitations of an existing solution
273
What are the elements of the Assess Capability Gaps task?
There are 3: Current Capability Analysis Assessment of New Capability Requirements Assumptions
274
What is the goal of the Current Capability analysis exercise?
To understand the organization\_s business and how the business and technology architecture are supporting that business
275
What must be done if current capability data is not available?
The analyst must model and other descriptive information about the area of the enterprise that is under review.
276
What must the current capabilities be assessed against in order to identify gaps?
The desired objectives of the stakeholders
277
If current capabilities are insufficient to meet the business need, the business analyst must identify what?
The capabilities that the organization must add
278
A comparison of the current and desired future states will identify what?
Gaps in organizational capabilities that need to be filled to support the business vision, strategy, goals and objectives.
279
Why is it important to identify assumptions during the Assess Capability Gaps task?
So that appropriate decisions can be made if the assumption later proves invalid
280
What are the techniques used in the Assess Capability Gaps task?
Document Analysis SWOT Analysis
281
What is SWOT Analysis?
Identify how current capabilities and limitations (Strengths and Weaknesses) match up against the influencing factors (Opportunities and Threats)
282
What is the definition of Required Capabilities?
An understanding of the current capabilities of the organization and the new capabilities (processes, staff, features in an application, etc.) that may be required to meet the business need
283
What is the purpose of the Determine Solution Approach task in Enterprise Analysis?
To determine the most viable solution approach to meet the business need in enough detail to allow for definition of solution scope and prepare the business case
284
The solution approach describes what?
The general approach that will be taken to create or acquire the new capabilities required to meet the business need
285
What must occur for the solution approach to be defined?
identify possible approaches determine the means by which the solution may be delivered (including the methodology and lifecycle to be used) assess whether the organization is capable of implementing and effectively using a solution of that nature
286
What are the inputs to the Define Solution Approach task?
There are 3 Business Organization Process Assets Required Capabilities
287
The Solution Approach is consumed by what task or tasks?
Define Solution Scope
288
What are the elements of the Define Solution Approach task?
There are 3 Alternative Generation Assumptions and Constraints Ranking Selection of Approaches
289
What is involved in the generation of alternatives?
Identify as many potential options as possible to meet the business objectives and fill identified gaps in capabilities
290
In relation to a solution, what is the impact of an assumption or constraint?
Either might impact whether the solution is a viable option
291
What are the techniques of the Define Solution Approach task?
There are 2 General Techniques (includes benchmarking, brainstorming, decision analysis, estimation, SWOT analysis) Feasibility Analysis
292
What is a feasibility study?
A preliminary analysis of solution alternatives or options to determine whether and how each option can provide an expected business benefit
293
What is the definition of a solution approach?
A description of the approach that will be taken to implement a new set of capabilities. Solution approaches describe the types of solution components that will be delivered (new processes, a new software application, etc.) and may also describe the methodology that will be used to deliver those components
294
What is the purpose of the Define Solution Scope task?
To define which new capabilities a project or iteration will deliver in order to conceptualize the recommended solution in enough detail to enable stakeholders to understand which new business capabilities an initiative will deliver
295
What does the solution scope include?
The scope of analysis (the organizational unit or process for which requirements are being developed) which provides the context in which the solution is implemented capabilities supported by solution components capabilities to be supported by individual releases or iterations enabling capabilities that are required in order for the organization to develop the capabilities required to meet the business need
296
What are the inputs to the Define Solution Scope task?
There are 4 Assumptions and Constraints Business Needs Required Capabilities Solution Approach
297
The Define Solution Scope task produces what output?
Solution Scope
298
The Solution Scope is consumed by what task or tasks?
Prepare for Elicitation Conduct Elicitation Define Business Case Prioritize Requirements Organize Requirements Verify Requirements Allocate Requirements Assess Org Readiness Requirements Mgmt and Communication knowledge area
299
What are the elements of the Define Solution Scope task?
There are 3 Solution Scope Definition Implementation Approach Dependencies
300
What is included in the Solution Scope Definition?
Major features and functions that are to be included, and the interactions that the solution will have with people and systems outside of its scope . Differentiation of the in-scope and out-of-scope components of the solution
301
What does the Implementation Approach define?
How the chosen solution approach will deliver the solution scope. The implementation approach may break delivery down into specific releases or provide a roadmap that indicates the timeframe in which a capability can be expected
302
What are the techniques for the Define Solution Scope task?
There are 2 General Techniques (includes Functional Decomposition, Interface Analysis, Scope Modeling, User Stories) Problem or Vision Statement
303
The Solution Approach is defined in what knowledge area?
Enterprise Analysis
304
The Solution Scope defines what?
What must be delivered in order to meet the business need, and the effect of the proposed change initiative on the business and technology operations and infrastructure
305
The business case describes what?
The justification for the project in terms of the value to be added to the business as a result of the deployed solution, as compared to the cost to develop and operate the solution
306
What are the inputs to the Define Business Case task?
There are 4 Assumptions and Constraints Business Needs Solution Scope Stakeholder Concerns
307
The business case is consumed by what tasks?
Prepare for Elicitation Conduct Elicitation Prioritize Requirements Verify Requirements Validate Requirements Requirements Mgmt and Communication knowledge area
308
With regard to the business, typically what do the assumptions refer to that are identified?
Assumptions about the revenue generated or retained by the solution or non-financial improvements it will deliver
309
What are the elements of the Define Business Case task?
There are 4 Benefits Costs
310
What are the two types of benefits collected in the Define Business Case task?
Qualitative and Quantitative
311
Benefits collected in the Define Business Case task should relate back to what?
Strategic objectives and goals of the organization
312
In estimating the total net cost of a proposed solution, what is included in the calculation?
capital expenditures for the new investment costs of developing and implementing the change opportunity costs of not investing in other options, costs related to changing the work and practices of the organization total cost of ownership to support the new solution and consequential costs borne by others
313
The initial risk assessment focuses on what?
Solution feasibility risks that the organization is willing to or able to bear
314
Initial risk assessment includes what factors?
technical risks (whether the chosen technology and suppliers can deliver the required functionality) financial risks (whether costs may exceed levels that make the solution viable or potential benefits may disappear) business change and organizational risks (whether the organization will make the changes necessary to benefit from the new solution).
315
What types of results are articulated in the business case?
Cost and Benefits to be realized and how each will be measured
316
What are the techniques used in the Define Business Case task?
There are 6 Decision Analysis Estimation Metrics and KPIs Risk Analysis SWOT Analysis Vendor Assessment
317
Why is vendor assessment a technique in the Define Business Case task?
In the case in which a purchase or outsourcing to a third party is in consideration, the organization must know whether the vendor is capable of delivering the solution
318
Who is the primary stakeholder in the Define Business Case task?
The Sponsor
319
The business case presents data in order to support what?
A go/no-go decision on whether to fund the effort
320
The Requirements Analysis knowledge area describes what?
The tasks and techniques used by a business analyst to analyze stated requirements in order to define the required capabilities of a potential solution that will fulfill stakeholder needs.
321
What are stakeholder requirements?
They describe what a solution must be capable of doing to meet the needs of one or more stakeholder groups
322
What are solution requirements?
They describe the behavior of solution components in enough detail to allow them to be constructed
323
The performance of all requirements analysis activities is governed by what?
Business Analysis Plan
324
What are the inputs to the Requirements Analysis knowledge area?
There are 8 Business Case Business Need Requirements Organizational Process Assets Requirements Mgmt Plan Stakeholder Concerns Stakeholder List Solution Scope
325
What are the tasks of the Requirements Analysis knowledge area?
There are 6 Prioritize Requirements Organize Requirements Specify and Model Requirements Define Assumptions and Constraints Verify Requirements Validate Requirements
326
What are the outputs of the Requirements Analysis knowledge area?
There are 6 Assumptions and Constraints Requirements Structure Requirements [prioritized] Requirements [validated] Requirements [verified] Stakeholder Concerns
327
What is the purpose of the Prioritize Requirements task?
Prioritization of requirements ensures that analysis and implementation efforts focus on the most critical requirements.
328
What is Requirement prioritization?
It is a decision process used to determine the relative importance of requirements, based on value, risk, difficulty of implementation, or on other criteria
329
Prioritization determines what?
Which requirements should be targets for further analysis and to determine which requirements should be implemented first
330
What are the inputs to the Prioritize Requirements task?
There are 5 Business Case Business Need Requirements Requirements Mgmt Plan Stakeholder List
331
Prioritized requirements are consumed by what tasks?
Assess Proposed Solution
332
What does the business case, as an input, provide to the prioritization of requirements process?
It provides key goals and measures of success for a project or organization, and priorities should be aligned with those goals and objectives.
333
Why is a business need and business case needed?
It\_s not. The business need serves as an alternative if the business case has not been provided
334
What are the elements for the Prioritize Requirements task?
There are 2 Basis of Prioritization Challenges
335
What are the factors considered as part as the basis for prioritization?
Business Value Business or Technical Risk Implementation Difficulty Likelihood of Success Regulatory or Policy Compliance Relationship to Other Requirements Stakeholder Agreements
336
How does business value impact prioritization of requirements?
It prioritizes requirements based on cost-benefit analysis of their relative value to the organization. The most valuable requirements will be targeted for development first.
337
Why is the relationship to other requirements a factor for the basis of prioritization?
A requirement may not be high value in and of itself, but may support other high-priority requirements and as such may be a candidate for early implementation.
338
What are two types of challenges with regard to requirements prioritization?
Non-negotiable demands from stakeholders and Unrealistic tradeoffs
339
What is considered an unrealistic tradeoff?
The solution development team may intentionally or uninten\_tionally try to influence the result of the prioritization process by overestimating the difficulty or complexity of implementing certain requirements
340
What are the techniques used in the Prioritize Requirements task?
There are 4 General techniques (Risk and Decision analysis) Moscow Analysis (Must, Should, Could, and Won\_t) Timeboxing/Budgeting Voting
341
What is Timeboxing/Budgeting?
Prioritization of requirements for investigation and implementation based on allocation of a fixed resource.
342
What must be determined in order to use Timeboxing/Budgeting?
The solution approach
343
Timeboxing prioritizes requirements based on what?
The amount of work that the project team is capable of delivering in a set period of time
344
Budgeting is used when?
When the project team has been allocated a fixed amount of money.
345
What are the three approaches to Timeboxing/budgeting?
All In - Begin with all the eligible requirements with assigned Duration or Cost. Remove the requirements in order to meet the calendar dates or budget limit. All Out - Begin with adding the requirement(s) with assigned duration or cost to the calendar or budget. Stop when the calendar dates are met or budget limit is reached. Selective - Begin by identifying high priority requirements added to the calendar or budget. Add or remove requirements in order to meet the calendar date or budget limit.
346
What is voting in relation to requirement prioritization?
Voting methods allocate a fixed amount of resources (votes, play money, or other tokens) to each participant for them to distribute among proposed features or requirements. The requirements that receive the most resources are the ones that will be investigated or developed first
347
A prioritized requirement has an attribute that describes what?
Its relative importance to stakeholders and the organization
348
What is the purpose of the Organize Requirements task?
To create a set of views of the requirements for the new business solution that are comprehensive, complete, consistent, and understood from all stakeholder perspectives
349
What are the two key objectives when organizing requirements?
Understand which models are appropriate for the business domain and solution scope Identify model interrelationships and dependencies
350
What are the inputs to the Organize Requirements task?
There are 3: Organizational Process Assets Requirements [Stated] Solution Scope
351
Why is it important to understand model interdependencies when organizing requirements?
Because it is the relationships and interdependencies among requirements that adds the element of complexity
352
What task or tasks consume the Requirements Structure?
Prepare Requirements Package and Specify and Model Requirements
353
What are the elements of the Organize Requirements task?
There are two Levels of Abstraction
354
According to the BABOK 2.0, which of the following describes LESSENING abstraction of requirements?
business requirements, stakeholder requirements, and solution requirements
355
What is the objective of creating a model of requirements?
To simplify reality in a way that is useful
356
Must modeling be performed in a specific order with a specific hierarchy?
No. There is not hierarchy when using models
357
What are the common concepts when using models?
User Classes, profiles, Roles Concepts and Relationships Events Processes Rules
358
User Classes, Profiles, or Roles are categorizations that are often found in what models?
organization models process models use cases
359
Organization models, process models and use cases are generally created in what task
Conduct Stakeholder Analysis
360
What corresponds to something in the real world; a place, a person, a thing, an organization
A concept
361
What do concepts define?
They define the objects, entities or facts that are relevant to the business domain and what relationships they have with other concepts
362
The attributes of a concept are found in what type of model
Data Model
363
A request to a business system or organization to do something, such as a customer placing an order, or a manager requesting a report, can be described as what?
An Event
364
Events can serve as the basis for what type of model?
Scope Model
365
Events serve as the basis for scope models but can be described in what other types of models?
Process Models State Diagrams Use Cases/Models
366
A sequence of repeatable activities executed within an organization is known as a what?
Process
367
Processes describe what?
Who and what has to be involved in fully responding to an event, or how people in the enterprise collaborate to achieve a goal
368
Process information can be found in what types of models?
Process Models Org Models State Diagrams Use Cases/Models
369
What are used by the enterprise to enforce goals and guide decision-making?
Rules
370
What do rules determine?
When information associated with an entity may change, what values of information are valid, how decisions are made in a process, and what the organization\_s priorities are
371
What types of models might contain rule information?
Process Models State Diagrams Use Cases/Models
372
What are the techniques used in the Organize Requirements task?
There are 9 Business Rules Analysis Data Flow Diagrams Data Modeling Functional Decomposition Organizational Modeling Process Modeling Scenarios and Use Cases Scope Modeling User Stories
373
Who are the primary stakeholders in the Organize Requirements task?
Domain SME, End User, Implementation SME, and Sponsor: They Affected by analysis techniques used to organize requirements since they need to verify and validate the requirements.
374
What is the purpose of the Specify and Model Requirements task?
To analyze expressed stakeholder desires and/or the current state of the organization using a combination of textual statements, matrices, diagrams and formal models
375
Specifications and models are created to do what?
Analyze the functioning of an organization and provide insight into opportunities for improvement
376
Specifications and models also support what?
Development and implementation of solutions, facilitating communication among stakeholders, supporting training activities and knowledge management, and ensuring compliance with contracts and regulations
377
What are the inputs to the Specify and Model Requirements task?
There are 2 Requirements [stated] Requirements Structure
378
What is the output of the Specify and Model Requirements task?
Stakeholder or Solution Requirements
379
What tasks consume the Stakeholder or Solution Requirements?
There are 3 Prioritize Requirements Verify Requirements Requirements Mgmt and Communication knowledge area
380
What are the elements of the Specify and Model Requirements task?
Text Matrix Documentation Models Capture Requirements Attributes Improvement Opportunities
381
The Text element must describe what?
Te capabilities of the solution, any conditions that must exist for the requirement to operate, and any constraints that may prevent the solution from fulfilling the requirement
382
A table or matrix is used to document requirements when?
When business analyst is looking to convey a set of requirements that have a complex but uniform structure which can be broken down into elements that apply to every entry in the table
383
What aspects of requirements are often expressed in tabular form?
Attributes Data Dictionaries Traceability Prioritization data
384
A WHAT is any simplified representation of a complex reality that is useful for understanding that reality and making decisions regarding it?
A model
385
What are two things that help determine which type of model to use?
The people that make up the receiving audience and the type of information being communicated
386
What is the difference between an informal model and a formal model?
An informal model does not have a formal semantic definition and instead connects elements in ways that are meaningful for the analyst and the audience A formal model follows semantics and iconography that are defined in a standard to indicate the meaning of each model element
387
What are some potential improvement opportunities that might be identified and captured during the Specify and Model Requirements task?
Automate Or Simplify The Work People Perform Improve Access To Information Reduce Complexity Of Interfaces Increase Consistency Of Behavior Eliminate Redundancy
388
What are the techniques used in the Specify and Model Requirements task?
There are several techniques that are part of the general techniques category: Acceptance and Evaluation Criteria Definition Business Rules Analysis Data Dictionary and Glossary Data Flow Diagrams Data Modeling Functional Decomposition Interface Analysis Metrics and Key Performance Indicators Non-functional Requirements Analysis Organization Modeling Process Modeling Prototyping Scenarios and Use Cases Sequence Diagrams State Diagrams User Stories
389
What is the purpose of the Define Assumptions and Constraints task?
Identify factors other than requirements that may affect which solutions are viable.
390
Assumptions are defined as what?
Assumptions are factors that are believed to be true, but have not been confirmed
391
What is associated with assumptions that must be validated by the analyst?
Risk
392
Constraints are defined as what?
Constraints are defined as restrictions or limitations on possible solutions.
393
Solution constraints describe what?
Aspects of the current state, or planned future state that may not be changed
394
What are the inputs to the Define Assumptions and Constraints task?
Stakeholder Concerns
395
What are the elements used in the Define Assumptions and Constraints task?
There are 3 Assumptions Business Constraints Technical Constraints
396
Business Constraints can reflect what type of information?
budgetary restrictions time restrictions limits on the number of resources available restrictions based on the skills of the project team and the stakeholders a requirement that certain stakeholders not be affected by the implementation of the solution or any other organizational restriction
397
Technical constraints include what?
Any architecture decisions that are made that may impact the design of the solution
398
Technical constraints may also describe restrictions such as what?
resource utilization message size timing software size maximum number of and size of files records and data elements
399
What is the output of the Define Assumptions and Constraints task?
Assumptions and Constraints
400
What tasks consume Assumptions and Constraints?
There are 4 Define Solution Scope Define Business Case Assess Proposed Solution Requirements Mgmt and Communication knowledge area
401
What is the purpose of the Verify Requirements task?
Requirements verification ensures that requirements specifications and models meet the necessary standard of quality to allow them to be used effectively to guide further work
402
Verifying requirements ensures what?
The requirements have been defined correctly and are of acceptable quality
403
Requirements verification constitutes a final check by the business analyst and key stakeholders to determine that the requirements are what?
Ready for formal review and validation by the customers and users and provide all the information needed for further work based on the requirements to be performed
404
What are the inputs to the Verify Requirements task?
Requirements [Any Except Stated]
405
The Verify Requirements task produces what output?
Requirements [Verified]
406
What tasks consume verified requirements?
Validate Requirements Requirements Mgmt and Communication knowledge area
407
What are the elements used in the Verify Requirements task?
There are 2: Characteristics of Requirements Quality Verification Activities
408
A high quality requirement exhibits what characteristics?
Cohesive Complete Consistent Correct Feasible Modifiable Unambiguous Testable
409
The feasibility of a requirement is concerned with what?
That the requirement must be implementable within the existing infrastructure, with the existing budget, timeline and resources available to the team or the project must develop the capability to implement the requirement
410
Are verification activities of requirements performed in a singular fashion or iteratively?
Iteratively throughout the requirements analysis process
411
Verification activities include what?
Check for completeness within each requirements model Compare each prepared requirements model (textual or graphical) against all other prepared requirements models Variations to the documented processes have been identified and documented All triggers and outcomes have been accounted for in all variations Terminology used in expressing the requirement is understandable to stakeholders and consistent Examples are added where appropriate for clarification
412
What are the techniques used in the Verify Requirements task?
There are 2: General techniques (includes Acceptance and Evaluation Criteria Definition, Problem Tracking, Structured Walkthrough) Checklists
413
What is the purpose of a checklist?
The purpose of a checklist is to ensure that items that the organization or project team has determined are important are included in the final requirements deliverable(s)
414
What is the purpose of the Validate Requirements task?
To ensure that all requir+B16ements support the delivery of value to the business, fulfill its goals and objectives, and meet a stakeholder need.
415
Does Requirements Validation once or throughout the life of the project?
Throughout in an ongoing basis
416
To be a valid requirement, it must do what?
Contribute directly or indirectly to the business case
417
What are the inputs to the Validate Requirements task?
There are 2 Business Case Stakeholder Solution or Transition Requirements [verified]
418
Validated requirements are consumed by what tasks?
Validate Solution Requirements Mgmt and Communication knowledge area
419
What are the elements of the Validate Requirements task?
There are 5 identify Assumptions Define Measurable Criteria Determine Business Value Determine Dependencies for Benefit Realization Evaluate Alignment with Business Case and Opportunity Cost
420
Assumptions must be identified to manage what?
Risk
421
Evaluation Criteria are used to do what during Validate Requirements?
They are create and used to measure the solution following deployment against the forecasted benefits from the start of the project
422
True or False: Besides the Business Case, it is possible to assess individual requirements or features to determine business value
TRUE
423
A requirement that does not deliver direct or indirect value to a stakeholder is a strong candidate for what?
Elimination
424
True or False: Business value can be delivered through requirements that support compliance with regulatory or other standards, alignment with internal standards or policies of the organization, or increased satisfaction for stakeholders, even if those things do not have a direct measurable financial benefit.
TRUE
425
True or False: All requirements contribute directly to the end result desired by the organization and described in the business case
FALSE
426
Can a requirement hold value for a stakeholder yet not be part of a delivered solution.
Yes, but if it is not aligned with the business case should be defined and approved in a separate business case, or considered for removal from the solution scope
427
Each requirement must be traceable to what?
The objectives in the business case
428
At the project level, opportunity cost refers to what?
The benefits that could have been achieved with an alternative investment rather than this one.
429
The opportunity cost of any decision is equal to what?
The value of the best alternative use of those resources
430
What are the techniques in the Validate Requirements task?
There are 5: Acceptance and Evaluation Criteria Definition Metrics and Key Performance Indicators Prototyping Risk Analysis Structured Walkthrough
431
The Solution Assessment and Validation Knowledge Area describes what?
The tasks that are performed in order to ensure that solutions meet the business need and to facilitate their successful implementation
432
What is the responsibility of the business analyst during Solution Assessment and Validation?
Ensuring that stakeholders fully understand the solution requirements and that implementation decisions are aligned with the relevant requirements
433
What are the tasks in the Solution Assessment and Validation knowledge area?
There are 6 Assess Proposed Solution Allocate Requirements Assess Organizational Readiness Define Transition Requirements Validate Solution Evaluate Solution Performance
434
What is the purpose of the Assess Proposed Solution task?
To assess proposed solutions in order to determine how closely they meet stakeholder and solution requirements
435
Is Solution Assessment performed on a single or multiple solutions?
Both. It may be used to compare multiple solutions or to assess a single solution
436
What are the inputs to the Assess Proposed Solution task?
There are 3 Assumptions and Constraints Requirements [prioritized and approved] Solution Option(s)
437
What is the output of the Assess Proposed Solution task?
Assessment of Proposed Solution
438
What tasks consume the Assessment of Proposed Solution?
Solution Selection or Design
439
What are the elements of the Assess Proposed Solution task?
Ranking of Solution Options Identification of Additional Potential Capabilities
440
What are the techniques of the Assess Proposed Solution task?
There are 3 Acceptance and Evaluation Criteria Definition Decision Analysis Vendor Assessment
441
Why is vendor assessment a technique as part of the Assess Proposed Solution task?
To ensure that all parties will be able to develop and maintain a healthy working relationship
442
What is a potential suggestion as part of the Solution Assessment if no solution delivers appropriate value?
To terminate the initiative or do nothing.
443
What is the purpose of the Allocate Requirements task?
Allocate stakeholder and solution requirements among solution components and releases in order to maximize the possible business value given the options and alterna\_tives generated by the design team.
444
Requirements allocation is defined as what?
Te process of assigning stakeholder and solution requirements to solution components and to releases
445
Allocation is performed after assessing what?
Assessment tradeoffs between alternatives in order to maximize benefits and minimize costs
446
What are the inputs of the Allocate Requirements task?
There are 3: Requirements [prioritized and approved] Solution [designed] Solution Scope
447
Allocated Requirements are consumed by what tasks?
Requirements Mgt. and Communication Solution Selection or Design
448
Requirements may be allocated between or over what?
Organizational units between job functions between people and software software application components releases of a solution.
449
To prevent scope revision, what must the allocation of requirements match?
The associated stakeholder and solution requirements
450
What are the elements of the Allocate Requirements task?
There are 2 Solution Components Release Planning
451
What are some examples of solution components?
Business policies and business rules Business processes to be performed and managed People who operate and maintain the solution, including their job functions and responsibilities Software applications and application components used in the solution. Structure of the organization, including interactions between the organization, its customers, and its suppliers
452
The allocation of requirements to solution components will be a primary driver of what?
The cost to implement the solution and the benefits delivered by it.
453
During solution design, why might it become necessary to revisit the initial allocation of functionality between components as defined in the solution scope?
The cost to implement each component becomes better understood, and to determine which allocations have the best cost/benefit ratio.
454
Analyst assessment of whether the allocation represents the most effective tradeoffs between delivery options involves what considerations?
Available resources Constraints on the Solution Dependencies Between Requirements
455
What types of factors are considerations of release planning?
overall project budget the need to implement a solution or parts of the solution by a certain date resource constraints training schedule ability for the business to absorb changes within a defined timeframe.
456
What are the techniques used in the Allocate Requirements task?
There are 6 Acceptance and Evaluation Criteria Definition Business Rules Analysis Decision Analysis Functional Decomposition Process Modeling Scenarios and Use Cases
457
Why would process modeling be a part of allocation of requirements?
Activities in the process model may be allocated to different roles, or outsourced to a supplier. A solution can be developed that incrementally supports some sub-processes or activities
458
What is the involvement of the Implementation SME during the Allocate Requirements task?
The role is responsible for the design and construction of some or all solution components and the estimation of the work required. It will also make recommendations regarding the allocation of requirement
459
Allocated requirements are associated with what?
A solution component that will implement them.
460
What is the purpose of the Assess Organizational Readiness task?
Assess whether the organization is ready to make effective use of a new solution.
461
An organizational readiness assessment describes what?
The effect a new solution will have on an organization and whether the organization is prepared for the organizational change that the solution implementation will cause
462
What should the business analyst understand to assess organizational readiness?
what changes will occur in the business area technical infrastructure or processes how these affect other business units or operations
463
What are the inputs to the Assess Organizational Readiness task?
There are 4 Enterprise Architecture Solution [designed] Solution Scope Stakeholder Concerns
464
What is the output of the Organizational Readiness Assessment?
Duh! The organizational readiness assessment
465
What tasks consume the Organizational Readiness Assessment?
Define Transition Requirements
466
Why is the Enterprise Architecture an important input into the Assess Organizational Readiness task?
It describes the current state of the enterprise, including the organizational structure, business processes, systems, information, etc.
467
What are the elements used in the Assess Organizational Readiness task?
There are 3 Cultural Assessment Operational or Technical Assessment Stakeholder Impact Analysis
468
What occurs in a cultural assessment?
A determination is made of the stakeholders\_ attitudes, beliefs, willingness to change and other factors that could pose potential obstacles to solution implementation.
469
What occurs in a Operational or Technical Assessment?
A determination of whether the organization is able to take advantage of the capabilities provided by the new solution is made. There is also an evaluation of whether stakeholders are prepared to make use of the new solution and whether there must be training/policy/process changes to accompany the new solution
470
What are some of the considerations of stakeholder impact analysis?
:Stakeholder Group functions Geographic Location of Stakeholder Groups Tasks performed by specific stakeholders Concerns about the stakeholder group\_s usability requirements, preferences, and their proficiency level regarding interaction with computer systems
471
What are the techniques used in the Assess Organizational Readiness task?
General Techniques (including Acceptance and Evaluation Criteria Definition, Data Flow Diagrams, Process Models, Focus Groups, Interviews, Survey/Questionnaire, Organization Modeling, Problem Tracking, Risk Analysis, SWOT Analysis) Force Field Analysis
472
What is Force Field Analysis?
A graphical method for depicting the forces that support and oppose a change by identifying the forces that support and oppose a change, depicting them on opposite sides of a line, and then estimating the strength of each force in order to assess which set of forces are stronger
473
What does the Organizational Change Management SME do during the Assess Organizational Readiness task?
Assists organizations with communicating change to their stakeholders and creating support among those stakeholders for the change.
474
In general, the Organizational Readiness Assessment describes what?
Whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively. May lead to revisions in solution or project scope
475
What is the purpose of the Define Transition Requirements task?
To define requirements for capabilities needed to transition from an existing solution to a new solution
476
Why couldn\_t the project just utilize the normal requirement set, instead of developing transition requirements?
During the transition period (the time when both the old and new solutions are operational), the enterprise may need to operate both solutions in parallel, move information between the new and old solution, conduct training to enable stakeholders to effectively operate the new solution, and so forth.
477
Transition requirements cannot be defined until what occurs?
The solution has been designed
478
Transition requirements remain relevant for how long?
Only during the transition period between the existing and new solutions. They are then discarded
479
Are transition requirements developed using other methods that normal requirements are not?
No Transition requirements are elicited, analyzed, managed, and communicated by performing the same tasks as for other requirements.
480
What are the inputs to the Define Transition Requirements task?
There are 4: Organizational Readiness Assessment Requirements [stated] Solution [deployed] Solution [designed]
481
Transition Requirements are consumed by what tasks?
Prioritize Requirements Verify Requirements Requirements Mgmt and Communication knowledge area
482
Why is the deployed solution an input to defining transition requirements?
The deployed (or existing) solution will be investigated to understand what needs to be transitioned to the new solution
483
What are the elements used in the Define Transition Requirements task?
There are 3 Data Ongoing Work Organizational Change
484
Why must the data element be evaluated during creation of transition requirements?
There must be a determination of whether the data must be migrated and/or converted for the new solution to function
485
Organizational change management generally refers to what?
To a process and set of tools for managing change at an organizational level.
486
Why is the analysis of organizational change necessary when creating transition requirements?
Organizational units may be significantly impacted by the new solution and will need to have processes changed to be able to take advantage of the new solution
487
What are the techniques used in the Define Transition Requirements task?
There are 3 Business Rules Analysis Data Flow Diagrams, Process Modeling, Organizational Modeling Data Modeling
488
What stakeholder receives noticeable negative impact if information is incorrectly transferred from the old to new solution?
The customer
489
Transition requirements describe what?
Capabilities that must be developed in order for an organization to successfully transition between solutions.
490
What is the purpose of the Validate Solution task?
Validate that a solution meets the business need and determine the most appropriate response to identified defects
491
Solution validation is required to do what?
Ensure that a delivered solution meets the business needs on an ongoing basis
492
What are the outputs of the Validate Solution task?
There are 3 Identified Defects Mitigating Actions Solution Validation Assessment
493
Identified defects that are an output of the Validate Solution task are consumed by what task?
Evaluate Solution Performance
494
Mitigating Actions and Solution Performance Assessments that are outputs of the Validate Solution tasks are consumed by what task?
Solution Implementation
495
What are the elements of the Validate Solution task?
There are 2 Investigate Defective Solution Outputs Assess Defects and Issues
496
When it can be determined that the solution is consistently producing defective outputs, it\_s time to utilize what technique?
Root Cause Analysis
497
When performing root cause analysis as part of the Validate Solution task, what stakeholder may be involved?
Implementation SME
498
Defects are reviewed with what considerations in mind?
determining the severity of the defect, the probability of the occurrence of the defect the severity of the business impact the capacity of the business to absorb the impact of the defects
499
What are the techniques used in the Validate Solution task?
There are 3 Acceptance and Evaluation Criteria Definition Root Cause Analysis Problem Tracking
500
What is the definition of a mitigating action?
Steps that can be taken, or processes that can be followed, to reduce or eliminate the effect an identified defect has on a stakeholder or stakeholder group.
