SUBJECTS
|
BROWSE
|
CAREER CENTER
|
POPULAR
|
JOIN
|
LOGIN
Business Skills
|
Soft Skills
|
Basic Literacy
|
Certifications
About
|
Help
|
Privacy
|
Terms
|
Email
Search
Test your basic knowledge |
BABOK Techniques
Start Test
Study First
Subjects
:
certifications
,
it-skills
Instructions:
Answer 43 questions in 15 minutes.
If you are not ready to take this test, you can
study here
.
Match each statement with the correct term.
Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.
This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.
1. To understand the scope of work and to break the solution scope into smaller work products or deliverables
MoSCoW Analysis
Scenarios and Use Cases
Organization Modeling
Functional Decomposition
2. Identify solution approaches that have proven effective in other organizations
Business Rule Analysis
Benchmarking
Coverage Matrix
Scope Modeling
3. Rank and select possible solution approaches
Metrics & Key Performance Indicators
Process Modeling
Problem Tracking
Decision Analysis
4. Useful method of comparing possible approaches
Structured Walkthrough
Document Analysis
Coverage Matrix
SWOT Analysis
5. Identify appropriate boundaries for the solution scope
Scope Modeling
Voting
Requirements Workshop
Functional Decomposition
6. Describe the stakeholder objectives that the solution will support
Metrics & Key Performance Indicators
Problem Tracking
Brainstorming
User Stories
7. Requirements may be presentated as part of a requirements workshop to familiarize all parties with the existing solution scope and current requirements
Requirements Workshop
SWOT Analysis
Signoff
Risk Analysis
8. Requirements that are considered risky may need to be investigaged or iplemented first - so that if risks cause the project to fail - the organization has invested as little as possible at that point.
Data Modeling
Structured Walkthrough
Problem Tracking
Risk Analysis
9. MoSCoW analysis divides requirements into four categories: Must - Should - Could - and Won't
MoSCoW Analysis
Timeboxing/Budgeting
Estimation
Coverage Matrix
10. If purchase or outsourcing to a thrid party is in consideration - an assessment of the vendor may be performed as part of the business case
Benchmarking
Voting
User Stories
Vendor Assessment
11. Useful to understand the current state of the enterprise - in as much as that current state is documented
Requirements Documentation
Decision Analysis
Document Analysis
Vendor Assessment
12. May be used to ensure that any problems identified during verification are resolved
Problem Tracking
Estimation
Risk Analysis
Functional Decomposition
13. Develop initial cost comparison of possible solution approaches
Estimation
Scope Modeling
Vendor Assessment
Acceptance and Evaluation Criteria Definition
14. Requirements may be organized around relevant processes
Problem Tracking
Voting
SWOT Analysis
Process Modeling
15. Allows the business analyst to manage any issues identified with requirements by stakeholders and ensure that those issues are resolved
Problem Tracking
Estimation
Structured Walkthrough
SWOT Analysis
16. Cost-Benefit analysis compares the costs of implementing a solution against the benefits to be gained. Financial analysis includes the use of financial models that estimate the market value of an organizational asset.
Functional Decomposition
User Stories
Decision Analysis
Coverage Matrix
17. Assess the risk (both positive and negative) if an assumption proves invalid - or a constraint is removed
Timeboxing/Budgeting
Problem Tracking
Risk Analysis
User Stories
18. Timeboxing or budgeting prioritizes requirements for investiation and implementation based on allication of a fixed resource.
Baselining
Timeboxing/Budgeting
MoSCoW Analysis
Structured Walkthrough
19. Requirements signoff formalizes agreement by stakeholders that the content and presentation of documented requirements is accurate and complete. A formal sign off of requirements documentation may be required by organizational standards or regulatory
Organization Modeling
Signoff
Voting
Requirements Workshop
20. Used to assess potential risks that may impact the solution and the costs and benefits associated with it
Functional Decomposition
Risk Analysis
Data Modeling
Document Analysis
21. Breaks down an organizational unit - product scope - or similar into its component parts. Each part can have its own set of requirements.
Decision Analysis
Estimation
Benchmarking
Functional Decomposition
22. Both assumptions and constraints are often identified - reviewed and managed using the ongoing planning - monitoring - and issue/risk management activities of the project team.
Structured Walkthrough
Coverage Matrix
Problem Tracking
Benchmarking
23. Once requirements are approved - they may be baselined - meaning that all future changes are recorded and tracked - and the current state may be compared to the baselined state. Subsequent chagnes to the requirement must follow the change control pro
Problem Tracking
Baselining
Organization Modeling
Decision Analysis
24. Used as a method of generating alternatives
Estimation
Brainstorming
SWOT Analysis
Structured Walkthrough
25. Used to inspect requirements documentation to identify ambiguous or unclear requirements
Scenarios and Use Cases
Benchmarking
Structured Walkthrough
Decision Analysis
26. Decision analsis may be used to identify high-value requirements
Requirements Workshop
Problem Tracking
MoSCoW Analysis
Decision Analysis
27. Business Rules may be separtated from other requirements for implememtnation and management in a business rules engine or similar
User Stories
Signoff
Business Rule Analysis
SWOT Analysis
28. Forecast the size of the investment required to deploy and operate the proposed solution
Estimation
Risk Analysis
Signoff
SWOT Analysis
29. Requirements may be organized based on the solution components they are related to
Voting
Scope Modeling
Data Modeling
Organization Modeling
30. Ensure that requirements are stated clearly enough to devise a set of tests that can prove that the requirement has been met.
Timeboxing/Budgeting
Acceptance and Evaluation Criteria Definition
Structured Walkthrough
Estimation
31. Show how information flows through a system. Each funciton that modifies the data should be decomposed into lower levels until the system is sufficiently described
Data Flow Diagrams
Business Rule Analysis
Acceptance and Evaluation Criteria Definition
Timeboxing/Budgeting
32. Identify how current capabilities and limitations match up against the influencing factors
Scope Modeling
SWOT Analysis
Benchmarking
Risk Analysis
33. Describe the requirements that support the individual goals of each actor - or the response to the triggering event.
Scenarios and Use Cases
Risk Analysis
Structured Walkthrough
Business Rule Analysis
34. Depict the scope of work required to integrate the new solution into the business and technical environments
User Stories
Interface Analysis
MoSCoW Analysis
Requirements Documentation
35. Describes the various organizational units - stakeholders - and their relationships. Requirements can be structured around the needs of each stakeholder or group
Risk Analysis
Requirements Workshop
Organization Modeling
User Stories
36. Voting method allocate a fixed amount of resources to each participant for them to distribute among proposed features or requirements
Voting
SWOT Analysis
Estimation
Coverage Matrix
37. Assessed to support benefit management - measurement and reporting - including where alignment of internal measures or systems is needed to ensure that the behaviors we are seeking canb e seen - evaluated - and realized
Structured Walkthrough
Metrics & Key Performance Indicators
Requirements Workshop
Benchmarking
38. A coverage matrix is a table or spreadsheet used to manage tracing. It is typically used when there are relatively few requirements or when tracing is limited to high-level requirements
Structured Walkthrough
Requirements Workshop
Coverage Matrix
Document Analysis
39. Describe stakeholders and the guals the system supports and as such can also be used to define the solution scope
Scope Modeling
Scope Modeling
User Stories
Business Rule Analysis
40. A structured walkthrough often begins with a review of the requirements to be discussed
User Stories
Organization Modeling
Problem Tracking
Structured Walkthrough
41. Describes the concepts and relationships relevant to the solution or business domain
Acceptance and Evaluation Criteria Definition
Decision Analysis
Data Modeling
User Stories
42. Requirements are frequently captured in a formal document. Many tempaltes for requirements document exist and are in common use
Decision Analysis
Requirements Documentation
Functional Decomposition
Problem Tracking
43. Demonstrate how the solution will help the organization mazimize strengths and minimize weaknesses
Risk Analysis
SWOT Analysis
MoSCoW Analysis
Document Analysis