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