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