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