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