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. 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.
Decision Analysis
Risk Analysis
Vendor Assessment
Acceptance and Evaluation Criteria Definition
2. Assess the risk (both positive and negative) if an assumption proves invalid - or a constraint is removed
User Stories
Risk Analysis
User Stories
Data Modeling
3. Depict the scope of work required to integrate the new solution into the business and technical environments
Data Flow Diagrams
Interface Analysis
Estimation
Metrics & Key Performance Indicators
4. Describes the concepts and relationships relevant to the solution or business domain
Data Modeling
Benchmarking
Signoff
Estimation
5. Breaks down an organizational unit - product scope - or similar into its component parts. Each part can have its own set of requirements.
Timeboxing/Budgeting
Functional Decomposition
Scenarios and Use Cases
Scope Modeling
6. 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
Decision Analysis
Process Modeling
Data Flow Diagrams
Requirements Workshop
7. 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.
SWOT Analysis
Vendor Assessment
Structured Walkthrough
Risk Analysis
8. Develop initial cost comparison of possible solution approaches
Signoff
Structured Walkthrough
Requirements Workshop
Estimation
9. Describe the requirements that support the individual goals of each actor - or the response to the triggering event.
Baselining
SWOT Analysis
MoSCoW Analysis
Scenarios and Use Cases
10. Used as a method of generating alternatives
Voting
Brainstorming
User Stories
Structured Walkthrough
11. Useful method of comparing possible approaches
SWOT Analysis
Interface Analysis
Metrics & Key Performance Indicators
Requirements Documentation
12. Business Rules may be separtated from other requirements for implememtnation and management in a business rules engine or similar
Business Rule Analysis
Organization Modeling
Risk Analysis
Acceptance and Evaluation Criteria Definition
13. Allows the business analyst to manage any issues identified with requirements by stakeholders and ensure that those issues are resolved
Interface Analysis
Estimation
Problem Tracking
Decision Analysis
14. Identify how current capabilities and limitations match up against the influencing factors
SWOT Analysis
Vendor Assessment
Business Rule Analysis
Data Flow Diagrams
15. Describes the various organizational units - stakeholders - and their relationships. Requirements can be structured around the needs of each stakeholder or group
Organization Modeling
Structured Walkthrough
Estimation
SWOT Analysis
16. Both assumptions and constraints are often identified - reviewed and managed using the ongoing planning - monitoring - and issue/risk management activities of the project team.
Scope Modeling
Data Modeling
MoSCoW Analysis
Problem Tracking
17. Decision analsis may be used to identify high-value requirements
Process Modeling
Decision Analysis
Metrics & Key Performance Indicators
Baselining
18. Describe stakeholders and the guals the system supports and as such can also be used to define the solution scope
User Stories
Baselining
Brainstorming
Decision Analysis
19. Identify solution approaches that have proven effective in other organizations
Data Flow Diagrams
Benchmarking
Coverage Matrix
Business Rule Analysis
20. Useful to understand the current state of the enterprise - in as much as that current state is documented
Acceptance and Evaluation Criteria Definition
Document Analysis
Process Modeling
Benchmarking
21. Requirements may be organized around relevant processes
Document Analysis
Decision Analysis
Risk Analysis
Process Modeling
22. May be used to ensure that any problems identified during verification are resolved
Brainstorming
Coverage Matrix
Problem Tracking
Estimation
23. Requirements may be presentated as part of a requirements workshop to familiarize all parties with the existing solution scope and current requirements
Scenarios and Use Cases
SWOT Analysis
Problem Tracking
Requirements Workshop
24. MoSCoW analysis divides requirements into four categories: Must - Should - Could - and Won't
Timeboxing/Budgeting
Coverage Matrix
MoSCoW Analysis
User Stories
25. 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
Coverage Matrix
Estimation
Timeboxing/Budgeting
Scenarios and Use Cases
26. Requirements may be organized based on the solution components they are related to
Decision Analysis
Scope Modeling
Requirements Documentation
Structured Walkthrough
27. To understand the scope of work and to break the solution scope into smaller work products or deliverables
Functional Decomposition
Data Modeling
MoSCoW Analysis
Coverage Matrix
28. Rank and select possible solution approaches
Signoff
SWOT Analysis
Decision Analysis
Problem Tracking
29. 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
Scope Modeling
Metrics & Key Performance Indicators
Structured Walkthrough
Risk Analysis
30. Used to inspect requirements documentation to identify ambiguous or unclear requirements
Benchmarking
Structured Walkthrough
Problem Tracking
Process Modeling
31. 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
Metrics & Key Performance Indicators
SWOT Analysis
Requirements Workshop
Vendor Assessment
32. Forecast the size of the investment required to deploy and operate the proposed solution
Organization Modeling
Risk Analysis
Estimation
Scope Modeling
33. Identify appropriate boundaries for the solution scope
Metrics & Key Performance Indicators
Decision Analysis
Scope Modeling
Decision Analysis
34. Used to assess potential risks that may impact the solution and the costs and benefits associated with it
Voting
Problem Tracking
Risk Analysis
Signoff
35. Requirements are frequently captured in a formal document. Many tempaltes for requirements document exist and are in common use
Decision Analysis
Structured Walkthrough
Decision Analysis
Requirements Documentation
36. Timeboxing or budgeting prioritizes requirements for investiation and implementation based on allication of a fixed resource.
Timeboxing/Budgeting
Organization Modeling
Estimation
SWOT Analysis
37. 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
Scenarios and Use Cases
Signoff
Estimation
Interface Analysis
38. Ensure that requirements are stated clearly enough to devise a set of tests that can prove that the requirement has been met.
Acceptance and Evaluation Criteria Definition
Functional Decomposition
Metrics & Key Performance Indicators
Problem Tracking
39. Voting method allocate a fixed amount of resources to each participant for them to distribute among proposed features or requirements
Benchmarking
Voting
Coverage Matrix
Timeboxing/Budgeting
40. A structured walkthrough often begins with a review of the requirements to be discussed
Interface Analysis
User Stories
Document Analysis
Structured Walkthrough
41. Describe the stakeholder objectives that the solution will support
Decision Analysis
User Stories
Decision Analysis
Estimation
42. Demonstrate how the solution will help the organization mazimize strengths and minimize weaknesses
User Stories
Structured Walkthrough
Process Modeling
SWOT Analysis
43. 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
SWOT Analysis
Risk Analysis