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