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
Start Test
Study First
Subjects
:
certifications
,
it-skills
Instructions:
Answer 50 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. Limitations on the design of a solution that derive from the technology used in its implementation.
Technical Constraint(s)
Objective
Work Product
Solution Scope
2. A methodology that focuses on rapid delivery of solution capabilities in an incremental fashion and direct involvement of stakeholders to gather feedback on the solution's performance.
SWOT Analysis
Change-driven Methodology
Requirement(s) Attribute
Regulator
3. A system trigger that is initiated by time.
Actor(s)
Functional Requirement(s)
Temporal Event
Prioritization
4. Statements of the needs of a particular stakeholder or class of stakeholders. They describe the needs that a given stakeholder has and how that stakeholder will interact with a solution. Serve as a bridge between business requirements and the various
Model(s)
Commercial-off-the-Shelf Software (COTS)
Stakeholder Requirement
Business Case
5. A model that defines the boundaries of a business domain or solution.
Stakeholder Requirement
Analyst
Vertical Prototype
Scope Model
6. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.
Relationship
Relationship Map
Change Control Board (CCB)
Business Policy
7. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.
Quality Assurance
Stakeholder
Brainstorming
Data Model
8. A prototype that shows a shallow and possibly wide view of the system's functionality but which does not generally support any actual use or interaction.
Focus Group
Horizontal Prototype
Root Cause Analysis
Business Analysis Plan
9. The set of tasks and techniques used to work as a liaison among stakeholders in order to understand the structure policies and operations of an organization and recommend solutions that enable the organization to achieve its goals.
Customer
Software/Systems Requirements Specification
Desired Outcome
Business Analysis
10. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.
Project Scope
Objective
Project Manager
Decision Tree
11. Any effort undertaken with a defined goal or objective.
Organization
Product
Analyst
Initiative
12. A use case composed of a common set of steps used by multiple use cases.
Capability
Organizational Readiness Assessment
Included Use Cases
Solution Requirement
13. A description of the types of communication the business analyst will perform during business analysis the recipients of those communications and the form in which communication should occur.
Decision Analysis
Prototype
Baseline
Business Analysis Communication Plan
14. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.
Validated Requirements
Swimlane
Process Model
Solution Requirement
15. A structured process which captures the key characteristics of an industry to predict the long-term profitability prospects and to determine the practices of the most significant competitors.
Request For Proposal (RFP)
Requirements Management Tool
Code
Competitive Analysis
16. A type of diagram that shows objects participating in interactions and the messages exchanged between them.
Organization Modeling
Sequence Diagram
Root Cause Analysis
Monitoring
17. Software developed and sold for a particular market.
Project Manager
Organization
Commercial-off-the-Shelf Software (COTS)
Problem Statement
18. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.
Vision Statement (product vision statement)
Requirements Management
Solution Scope
Activity
19. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.
Business Constraint(s)
Stakeholder List
Product Backlog
Non-functional Requirement(s)
20. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Class Model
Gap Analysis
Commercial-off-the-Shelf Software (COTS)
Stakeholder Analysis
21. A non-actionable directive that supports a business goal.
Optionality
Business Policy
Requirements Traceability
Requirements Verification
22. The number of employees a manger is directly (or indirectly) responsible for.
Span of Control
Requirements Management Tool
Validated Requirements
Included Use Cases
23. The ability to identify and document the lineage of each requirement including its derivation (backward traceability) its allocation (forward traceability) and its relationship to other requirements.
Requirements Traceability
Class
Evaluation
Focus Group
24. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.
Stakeholder List
Evaluation
Glossary
Business Requirements Document
25. Any unique and verifiable work product or service that a party has agreed to deliver.
Indicator
User
Sponsor
Deliverable
26. A prototype that is continuously modified and updated in response to feedback from users.
Gap Analysis
Evolutionary Prototype
Supplier
Dialog Map
27. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.
Data Entity
Capability
User Requirements Document
Subject Matter Expert (SME)
28. A system of programming statements symbols and rules used to represent instructions to a computer.
Product
Actor(s)
Code
Context Diagram
29. A requirements workshop is a structured meeting in which a carefully selected group of stakeholders collaborate to define and or refine requirements under the guidance of a skilled neutral facilitator.
Force Field Analysis
Process Model
Requirements Workshop
Developer
30. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.
Methodology
Organizational Readiness Assessment
Span of Control
Decomposition
31. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
Checklist
Business Requirement
Constraint
Request For Proposal (RFP)
32. A unit of work performed as part of an initiative or process.
Stakeholder List
Cardinality
Activity
Peer Review
33. The problem area undergoing analysis.
Organizational Readiness Assessment
Domain
Quality Attributes
Use Case
34. An iteration that defines requirements for a subset of the solution scope. Would include identifying a part of the overall product scope to focus upon identifying requirements sources for that portion of the product analyzing stakeholders and plannin
Requirement
Requirements Iteration
Requirements Signoff
Timebox
35. A requirement articulated by a stakeholder that has not been analyzed verified or validated. Frequently reflect the desires of a stakeholder rather than the actual need.
Focus Group
Dialog Map
Stated Requirements
Code
36. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.
Indicator
Class
Implementation Subject Matter Expert (SME)
Variance Analysis
37. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.
Data Entity
Opportunity Analysis
State Diagram
Methodology
38. A comparison of a process or system's cost time quality or other metrics to those of leading peer organizations to identify opportunities for improvement.
Object Oriented Modeling
Benchmarking
Requirements Iteration
Business Event
39. An autonomous unit within an enterprise under the management of a single individual or board with a clearly defined boundary that works towards common goals and objectives. Operate on a continuous basis as opposed to an organizational unit or project
Organization
Business Analysis Plan
Change Control Board (CCB)
Plan-driven Methodology
40. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.
Entity-Relationship Diagram
Requirements Management
Business Policy
Walkthrough
41. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.
Class
Validated Requirements
Solution
Vision Statement (product vision statement)
42. A document or collection of notes or diagrams used by the business analyst during the requirements development process.
Work Product
Activity Diagram
Elicitation
Lessons Learned Process
43. An analysis model that shows user interface dialogs arranged as hierarchies.
Horizontal Prototype
Dialog Hierarchy
Prototype
Cost Benefit Analysis
44. Work carried out or on behalf of others.
Business Rule(s)
Initiative
User Acceptance Test
Service
45. Requirements that have been shown to demonstrate the characteristics of requirements quality and as such are cohesive complete consistent correct feasible modifiable unambiguous and testable.
Requirements Signoff
Verified Requirements
User Acceptance Test
Business Constraint(s)
46. Software requirements that limit the options available to the system designer.
Solution Requirement
Stated Requirements
Design Constraints
Business Need(s)
47. A requirements document issued to solicit vendor input on a proposed process or product. Is used when the issuing organization seeks to compare different alternatives or is uncertain regarding the available options
Request For Information (RFI)
Stakeholder
Plan-driven Methodology
User Acceptance Test
48. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.
Request For Information (RFI)
Capability
Project Scope
Vision Statement (product vision statement)
49. Something that occurs to which an organizational unit system or process must respond.
Event
Organizational Process Asset
Context Diagram
Data Entity
50. Creating working software in multiple releases so the entire product is delivered in portions over time.
Benchmarking
Incremental Delivery
Inspection
Quality Attributes