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