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