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