Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
159 Cards in this Set
- Front
- Back
|
What knowledge area describes the tasks and techniques used by a BA to analyze stated requirements in order to define the required capabilities of a potential solution that will fulfill stakeholder needs? |
Requirements Analysis
|
|
|
Requirements Analysis covers the definition of which types of requirements?
|
Stakeholder and Solution
|
|
|
At what level of detail should requirements be described at?
|
In enough detail to allow them to be constructed
|
|
|
In Requirements Analysis, modeling current states may help to identify what?
|
Opportunities for improvement, or for assisting stakeholders in understanding their current state.
|
|
|
All requirements analysis activities are governed by which two tasks?
|
- Business Analysis Plan(s) - BA Performance Metrics |
|
|
What are all of the inputs into the Requirements Analysis knowledge area?
|
- Business Case - Business Need - Requirements - Operational Process Assets - Requirements Management Plan - Stakeholder Concerns - Stakeholder List, Roles, and Responsibilities - Solution Scope |
|
|
What is the purpose of the "Prioritize Requirements" task?
|
To ensure that analysis and implementation efforts focus on the most critical requirements
|
|
|
Determining requirements prioritization may be based on what?
|
- Relative Value - Risk - Difficulty of implementation - Other Criteria |
|
|
The priority of requirements should be used to target what?
|
Which requirement should be further analyzed and which requirements should be implemented first |
|
|
What are the inputs to the task "Prioritize Requirements"?
|
- Business Case - Business Need - Requirements - Requirements Management Plan - Stakeholder List, Roles, and Responsibilities |
|
|
What is the output of the task "Prioritize Requirements"?
|
Requirements (prioritized)
|
|
|
What other tasks use prioritized requirements?
|
- Assess Proposed Solution - Allocate Requirements - Validate Solution - Requirements Management & Communication |
|
|
How is the business case used as an input to "Prioritize Requirements"?
|
States the key goals and measures of success, and priorities should be aligned with those goals and objectives.
|
|
|
How is the business need used as an input to "Prioritize Requirements"?
|
Serves as an alternative to the business case if no business case has been defined.
|
|
|
How are requirements used as an input to "Prioritize Requirements"?
|
Any requirement may be prioritized, at any point in its lifecycle.
|
|
|
True or False: Requirements may be prioritized before they are fully analyzed and in their final form.
|
TRUE
|
|
|
How is the Requirements Management Plan used as an input to "Prioritize Requirements"?
|
Defines the process that will be used to prioritize requirements.
|
|
|
How is the Stakeholder List, Roles, and Responsibilities used as an input to "Prioritize Requirements"?
|
To determine which stakeholders need to participate in prioritization.
|
|
|
What are the elements of the task "Prioritize Requirements"?
|
- Basis for Prioritization - Challenges |
|
|
What are the criteria for prioritizing requirements?
|
- Business Value - Business or Technical Risk - Implementation Difficulty - Likelihood of Success - Regulatory or Policy Compliance - Relationship to Other Requirements - Stakeholder Agreement - Urgency |
|
|
What is the "Business Value" prioritization approach?
|
It's based on cost-benefit analysis; the most valuable requirements will be targeted for development first. |
|
|
When is it common to choose "Business Value" as the prioritization method?
|
When enhancing an existing solution that already meets specified minimal requirements, or when delivering the solution incrementally.
|
|
|
What is the "Business or Technical Risk" prioritization method?
|
Selects requirements that present the highest risk of project failure
|
|
|
What is the "Implementation Difficulty" prioritization method?
|
Chooses the easiest requirement |
|
|
When would it make sense to choose the "Business or Technical Risk" prioritization method?
|
This ensures if the project fails it does so after as little expenditure as possible
|
|
|
When would the "Implementation Difficulty" prioritization method be used?
|
During a pilot of a new development process or tools, or when rolling out a packaged solution |
|
|
What is the "Likelihood of Success" prioritization method?
|
Focuses on the requirements that are likely to produce quick and relatively certain successes
|
|
|
When is the "Likelihood of Success" prioritization method often selected?
|
When a project is controversial and early signs of progress are needed to gain support for the initiative
|
|
|
What is the "Regulatory or Policy Compliance" prioritization method?
|
Prioritizes requirements that must be implemented in order to meet regulatory or policy demands
|
|
|
What is the "Relationship to Other Requirements" prioritization method?
|
Requirements that are not high-value in themselves, but may support other high-priority requirements
|
|
|
What is the "Stakeholder Agreement" prioritization method?
|
Requires the stakeholders to reach consensus on which requirements are most useful or valuable. May be combined with other prioritization approaches.
|
|
|
What is the "Urgency" prioritization method?
|
Prioritizes requirements based on time sensitivity.
|
|
|
What types of challenges might be encountered when prioritizing requirements?
|
- Non-negotiable demands - Unrealistic Tradeoffs |
|
|
What is a "non-negotiable demand" when prioritizing requirements?
|
Stakeholders attempt to avoid difficult choices, failing to recognize the necessity for making tradeoffs, or desire to rank all requirements as high priority.
|
|
|
What is an "Unrealistic Tradeoff" when prioritizing requirements?
|
The solution development team may try to influence the prioritization process by overestimating difficulty or complexity of requirements
|
|
|
What are the techniques used to "Prioritize Requirements"?
|
- General Techniques Decision Analysis Risk Analysis - MoSCoW Analysis - Timeboxing/Budgeting - Voting |
|
|
How is the "Decision Analysis" technique used to prioritize requirements?
|
May be used to identify high-value priorities |
|
|
How is the "Risk Analysis" technique used to prioritize requirements?
|
High-risk requirements may be investigated or implemented first so if the project fails, the loss is minimized.
|
|
|
What is MoSCoW Analysis?
|
A technique to prioritize requirements into Must, Should, Could or Won't-do
|
|
|
What is the "Timeboxing/Budgeting" technique?
|
Prioritizes requirements based on allocation of a fixed resource
|
|
|
When is the "Timeboxing/Budgeting" technique used?
|
When the solution approach has been determined
|
|
|
What is "Timeboxing"?
|
Prioritizes requirements based on the amount of work that the project team is capable of delivering in a set period of time.
|
|
|
What is "Budgeting"?
|
Prioritizes requirements based on a fixed amount of money.
|
|
|
When are the "Timeboxing/Budgeting" techniques most often used?
|
- When there's a fixed deadline - When there are enhancements on a frequent or regular basis |
|
|
In "Timeboxing/Budgeting", which are the approaches that can be used?
|
- All-in - All Out - Selective |
|
|
What does "All-in" mean?
|
That all requirements are in, but are removed in order to meet the time or budget requirements
|
|
|
What does "All Out" mean?
|
Add the requirements with assigned duration or cost until the limit is reached
|
|
|
What does "Selective" mean?
|
Begin with high-priority requirements and add until the calendar or budget is reached
|
|
|
What is the "Voting" technique?
|
Allocates a fixed amount of resources to each participant to distribute among proposed features or requirements; those with the most resources are first. |
|
|
What can be used to represent a "vote" in the "Voting" technique?
|
Votes, play money, or other tokens
|
|
|
Which stakeholders are involved in the task "Prioritize Requirements"?
|
- Domain SME - Implementation SME - Project Manager - Sponsor |
|
|
What is the purpose of "Organize Requirements"?
|
To create a set or views of the requirements for the new business solution that are comprehensive, complete, consistent, and understood from all stakeholder perspectives.
|
|
|
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 |
|
|
What are the inputs to "Organize Requirements"?
|
- Organizational Process Assets - Requirements (stated) - Solution Scope |
|
|
What is the output of "Organize Requirements"?
|
Requirements Structure
|
|
|
What other tasks use Requirements Structure as an input?
|
- Prepare Requirements Package - Specify and Model Requirements |
|
|
How are Organizational Process Assets used as an input to "Organize Requirements"?
|
Describe the structures and types of requirements information that stakeholders expect |
|
|
How are Requirements (stated) used as an input to "Organize Requirements"?
|
They are the expressed desires of stakeholders, which must be analyzed to ensure that they reflect a genuine need.
|
|
|
How is the Solution Scope used as an input to "Organize Requirements"?
|
The selected models must be sufficient to fully describe the solution scope from all needed perspectives.
|
|
|
What are the elements of the "Organize Requirements" task?
|
- Levels of Abstraction - Model Selection |
|
|
What guidelines does the BABOK recommend to promote consistency, repeatability and high quality when organizing requirements?
|
- Follow organizational standards - Use simple, consistent definitions - Document dependencies and interrelationships - Produce a consistent set of models and templates |
|
|
True or False: any given requirement should only appear in one model in order to avoid confusion and contradictions
|
TRUE
|
|
|
What is a "Level of Abstraction"?
|
It's based on the level of detail included, typically moving from high to low as analysis moves from business to solution requirements.
|
|
|
Any category of requirement can be expressed at whatever level of ___ is appropriate for the audience.
|
Abstraction
|
|
|
What is a "model" meant to do?
|
Abstract and simplify reality.
|
|
|
True or False: Models can be a complete description of reality
|
FALSE
|
|
|
True or False: It is usually necessary to develop multiple models with different techniques to fully analyze and document requirements.
|
TRUE
|
|
|
Models do not have any inherent ___.
|
Hierarchy
|
|
|
What are the general modeling concepts that are relevant to business analysis?
|
- User Classes, Profiles, or Roles - Concepts and Relationships (Entities) - Events - Processes - Rules |
|
|
What is the mnemonic for the modeling concepts?
|
PUREE (Processes, User Classes, Rules, Events, Entities
|
|
|
What is "Requirements Structure"?
|
An organized structure for requirements, including any relationships between them.
|
|
|
What are the types of "Process" modeling that may be selected when organizing/structuring requirements?
|
- Process Models - Organization Models - State Diagrams - Use Cases |
|
|
What are the types of "User class, profile, or roles" modeling that may be selected when organizing/structuring requirements?
|
- Organization Models - Process Models - Use Cases |
|
|
What are the types of "Rules" modeling that may be selected when organizing/structuring requirements?
|
- Process Models - State Diagrams - Data Models - Use Cases |
|
|
What are the types of "Concepts and Relationships" modeling that may be selected when organizing/structuring requirements?
|
- Data Models
|
|
|
What are the types of "Events" modeling that may be selected when organizing/structuring requirements?
|
- Scope Models - Process Models - State Diagrams - Use Cases |
|
|
What is the "Processes" modeling concept?
|
Steps performed to accomplish a goal or achieve a result; they transform inputs to outputs and should be repeatable
|
|
|
What is the "User Classes, Profiles, or Roles" modeling concept?
|
These categorize and describe the people who directly interact with a solution; roles group together people with similar needs, expectations and goals.
|
|
|
What is the "Events" modeling concept?
|
A trigger or other request to do something, such as a customer making a withdrawal from a bank account.
|
|
|
Events can come from __ or ___ or at scheduled times.
|
outside or within
|
|
|
What is the "Concepts and Relationships" (entities) modeling concept?
|
Entities or other related things in an organization (people, places, things, etc.). They are the source of facts and other data, and have relationships with other concepts.
|
|
|
What is the "Rules" modeling concept?
|
Used by the organization to enforce goals and guide decision-making
|
|
|
How should a BA choose which models to include when organizing/structuring requirements?
|
Choose those that meet the informational needs of stakeholders and allow description of all five modeling concepts to ensure full coverage.
|
|
|
What techniques are used in the task "Organize Requirements"?
|
- Business Rules Analysis - Data Flow Diagrams - Data Modeling - Functional Decomposition - Organization Modeling - Process Modeling - Scenarios and Use Cases - Scope Modeling - User Stories |
|
|
Which stakeholders are involved in the task "Organize Requirements"?
|
- Domain SME, End User, Implementation SME, Sponsor - Project Manager |
|
|
True or False: Requirements Structure and Traceability are the same thing
|
False. Structure is distinct from tracing.
|
|
|
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.
|
|
|
What does specifying and modeling requirements provide insight into?
|
Opportunities for improvement
|
|
|
What are the other objectives of specifying and modeling requirements?
|
- Development and implementation of solutions - Facilitating communication among stakeholders - Supporting training activities - Knowledge management - Ensuring compliance with contracts and regulations |
|
|
What are the inputs into the "Specify and Model Requirements" task?
|
- Requirements (stated) - Requirements structure |
|
|
What is the output of the "Specify and Model Requirements" task?
|
Requirements (analyzed) - could be either Stakeholder or Solution Requirements |
|
|
Which tasks use "Stakeholder or Solution Requirements" as inputs?
|
- Prioritize Requirements - Verify Requirements - Requirements Management and Communication |
|
|
What are the elements of the "Specify and Model Requirements" task?
|
- Text - Matrix Documentation - Models - Capture Requirements Attributes - Improvement Opportunities |
|
|
What guidelines should be followed when writing text requirements?
|
- Express only one requirement at a time - Avoid complex conditional logic - Do not assume your reader has domain knowledge - Use terminology that is consistent - Express requirements as a verb or verb phrase - Write in active voice - Use terminology the reviewing stakeholder is familiar with |
|
|
What must a text requirement describe?
|
- capabilities of the solution - any conditions that must exist for the requirement to operate - any constraints that may prevent the solution from fulfilling the requirement |
|
|
When would a matrix be the best way to model requirements?
|
when the BA wants to convey requirements with complex, but uniform structure
|
|
|
What other common ways are matrices used to model requirements?
|
- Requirements attributes - Data dictionaries - Traceability - Requirements to test cases - Gap Analysis - Prioritizing requirements by mapping against objectives |
|
|
Models may be either ___ or ___, or some combination of both.
|
Textual or Graphical
|
|
|
Graphical models are also known as what?
|
Diagrams
|
|
|
What are the different things that models can do?
|
- Describe a situation or define a problem - Defined boundaries - Describe thought processes and action flows - Categorize and create hierarchies of items - Show components and their relationships - Show business logic |
|
|
True or False: Models may be used not only to document requirements in their final form, but also as a tool while performing elicitation activities.
|
TRUE
|
|
|
Notations in modeling are also know as what?
|
Keys
|
|
|
What is the difference between a formal and informal model?
|
Formal models follow semantics and iconography based on a defined standard, whereas informal models do not. |
|
|
What are some types of improvements BA should be looking for as they modely requirements?
|
- Automate or simplify the way people work - Improve access to information - Reduce complexity of interfaces - Increase consistency of behavior - Eliminate redundancy |
|
|
What techniques are used in the task "Specify and Model Requirements"?
|
BUD3 PUNS3
|
|
|
Which stakeholders are involved in the "Specify and Model Requirements" task?
|
Any stakeholder
|
|
|
What is the purpose of the task "Define Assumptions & Constraints"?
|
To identify factors other than requirements that may affect which solutions are viable.
|
|
|
What is an assumption?
|
Factors that are believed to be true, but have not been confirmed.
|
|
|
What is a constraint?
|
A restriction or limitation on possible solutions
|
|
|
What do constraints describe?
|
Aspects of the current or future state that may not be changed.
|
|
|
BAs must do what with assumptions?
|
Confirm whether or not they are true and manage related risks.
|
|
|
What are the inputs into the "Define Assumptions & Constraints" task?
|
Stakeholder Concerns
|
|
|
What are the elements of the task "Define Assumptions & Constraints"?
|
- Assumptions - Business Constraints - Technical Constraints |
|
|
What are some examples of Business type constraints?
|
Budget, time, number of resources available, skillsets, or any other restriction
|
|
|
Constraints need to be carefully examined to ensure that they are ___ and ___.
|
Accurate and Justified
|
|
|
What are some examples of Technical type constraints?
|
- Development languages - Hardware and software platforms - Application software that must be used - Resource utilization - Message size and timing - Software size - Maximum number of size and files - Records and data elements |
|
|
What is the output of the "Define Assumptions & Constraints" task?
|
Assumptions & Constraints
|
|
|
Which other tasks use "Assumptions & Constraints" as an input?
|
- Define Solution Scope - Define Business Case - Assess Proposed Solution - Requirements Management & Communication |
|
|
Which techniques are used in the task "Define Assumptions & Constraints"?
|
- Problem Tracking - Risk Analysis |
|
|
Which stakeholders are involved in the "Define Assumptions & Constraints" task?
|
- Implementation SME - Project Manager - All Stakeholders |
|
|
True or False: Assumptions & Constraints are not technically requirements.
|
True. However, they can be managed and communicated in the same way.
|
|
|
What is the purpose of the task "Verify Requirements"?
|
Ensures that requirements have been correctly defined and that they are of acceptable quality.
|
|
|
Requirements verification constitutes a __ __ by the BA and stakeholders.
|
Final check
|
|
|
By verifying requirements, the BA and stakeholders are determining that they:
|
- are ready for formal review and validation by the customers and end users - provide all the information needed for further work |
|
|
What are the inputs into the task "Verify Requirements"?
|
Requirements (any except stated)
|
|
|
What is the output of the task "Verify Requirements"?
|
Requirements (verified)
|
|
|
What other tasks use verified requirements as an input?
|
- Requirements Management & Communication - Validate Requirements |
|
|
What are the elements of the task "Verify Requirements"?
|
- Characteristics of Requirements Quality - Verification Activities |
|
|
What are the minimum quality characteristics of high-quality requirements?
|
- Cohesive - Complete - Consistent - Correct - Feasible - Modifiable - Unambiguous - Testable |
|
|
What is the mnemonic for requirements quality characteristics?
|
CCCC MUFT
|
|
|
What are "cohesive" qualities in requirements?
|
They relate to only one thing.
|
|
|
What does it mean to have "consistent" requirements?
|
Ensures that individual requirements do not contradict each other or describe the same requirement using different wording. |
|
|
What activities are used to verify requirements?
|
- Check for completeness - Compare models against each other - Make sure all variations to document processes are identified - Assure all triggers and outcomes are accounted for in all variations - Make sure the terminology is consistent with use in the organization - Add examples where appropriate |
|
|
Which techniques are used in the task "Verify Requirements"?
|
General techniques: - Acceptance and Evaluation Criteria Definition - Problem Tracking - Structured Walkthrough Checklists |
|
|
How are checklists use in requirements verification?
|
As a quality control technique for requirements documentation.
|
|
|
Which stakeholders are involved in the task "Verify Requirements"?
|
All stakeholders
|
|
|
What is the output of the task "Verify Requirements"?
|
Requirements (verified)
|
|
|
What are synonyms of "cohesive"?
|
Unified, interconnected
|
|
|
What is a synonym of "complete"?
|
Comprehensive
|
|
|
What is a synonym of "consistent"?
|
Coherent
|
|
|
What is a synonym of "correct"?
|
Traceable (back to the business need)
|
|
|
What is a synonym of "modifiable"?
|
Changeable
|
|
|
What is a synonym of "unambiguous"?
|
Clear
|
|
|
What is a synonym of "feasible"?
|
Realistic, Possible
|
|
|
What is a synonym of "testable"?
|
Measurable
|
|
|
What is the purpose of the "Validate Requirements" task?
|
To ensure that all requirements support the delivery of value to the business, fulfill its goals and objectives, and meet a stakeholder need.
|
|
|
Requirements validation is an ___ process to ensure that stakeholder, solution, and transition requirements align to the business requirements.
|
Ongoing
|
|
|
What are the inputs into the task "Validate Requirements"?
|
- Business Case - Stakeholder, Solution or Transition Requirements |
|
|
What is the output of the task "Validate Requirements" ?
|
Requirements (validated)
|
|
|
What other tasks use validated requirements as an input?
|
- Requirements Management & Communication - Validate Solution |
|
|
What are the elements of the task "Validate Requirements" ?
|
- Identify Assumptions - Define Measurable Evaluation Criteria - Determine Business Value - Determine Dependencies for Benefits Realization - Evaluate Alignment with Business Case & Opportunity Cost |
|
|
How are evaluation criteria used in validating requirements?
|
To measure how successful the resulting change has been after the solution has been deployed.
|
|
|
Requirements that do not deliver business value may be candidates for what?
|
Elimination
|
|
|
True or false: Business value needs to be monetary
|
False. Can also be derived through requirements that support compliance, align with internal standards or policies, or increased satisfaction for stakeholders.
|
|
|
What is "opportunity cost"? |
The benefits that could have been achieved with an alternative investment rather than this one.
|
|
|
Each requirement must be ___ to the objectives in the business case. |
Traceable
|
|
|
The opportunity cost of any decision is equal to what? |
The value of the best alternative use of those resources.
|
|
|
What techniques are used in the "Validate Requirements" task? |
- Acceptance and Evaluation Criteria Definition - Metrics and KPIs - Prototyping - Risk Analysis - Structured Walkthrough |
|
|
Which stakeholders are involved in the task "Validate Requirements" ? |
All stakeholders
|
