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