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