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