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. An evaluation of proposed alternatives to determine if they are technically possible within the constraints of the organization and whether they will deliver the desired benefits to the organization.
Validated Requirements
Risk
Feasibility Study
Work Product
2. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.
Requirements Allocation
Variance Analysis
Observation
Software/Systems Requirements Specification
3. 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.
Fishbone Diagram
Activity Diagram
Context Diagram
Business Analysis Communication Plan
4. A prototype that dives into the details of the interface functionality or both.
Regulator
Vertical Prototype
Decomposition
Context Diagram
5. A solution or component of a solution that is the result of a project.
Product
Checklist
Inspection
Request For Proposal (RFP)
6. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.
Project Manager
Deliverable
Requirements Validation
Solution Requirement
7. An analysis model that illustrates the architecture of the system's user interface.
Dialog Map
Timebox
Business Analysis
Project Charter
8. The number of employees a manger is directly (or indirectly) responsible for.
Requirement
Business Need(s)
Span of Control
Requirements Trace Matrix
9. A descriptor for a set of system objects that share the same attributes operations relationships and behavior. Represents a concept in the system under design. When used as an analysis model a class will generally also correspond to a real-world enti
Class
Throw-away Prototype
Metric
Request For Proposal (RFP)
10. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.
Domain
Observation
Product Backlog
Cardinality
11. A measure of the profitability of a project or investment.
Business Architecture
Non-functional Requirement(s)
Developer
Return on Investment
12. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.
User Requirements Document
Deliverable
Business Architecture
Feature
13. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.
Scope
Unified Modeling Language (UML)
Included Use Cases
Organization Modeling
14. Ability of systems to communicate by exchanging data or services.
Peer Review
Interoperability
Interface
Root Cause Analysis
15. 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
Business Rule(s)
Organization
Association
Stated Requirements
16. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.
Optionality
Elicitation
Organizational Unit
Requirements Signoff
17. A systematic approach to elicit information from a person or group of people in an informal or formal setting by asking relevant questions and documenting the responses.
Stakeholder Analysis
Interview
System
User Acceptance Test
18. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.
Data Flow Diagram (DFD)
Unified Modeling Language (UML)
Business Case
Root Cause Analysis
19. A model that illustrates the flow of processes and/or complex use cases by showing each activity along with information flows and concurrent activities. Steps can be superimposed onto horizontal swimlanes for the roles that perform the steps.
Brainstorming
Product Scope
Business Event
Activity Diagram
20. A group of related tasks that support a key function of business analysis.
Problem Statement
Risk
Knowledge Area
Requirement
21. An activity within requirements development that identifies sources for requirements and then uses elicitation techniques (e.g. interviews prototypes facilitated workshops documentation studies) to gather requirements from those sources.
Optionality
Force Field Analysis
Elicitation
Stakeholder Requirement
22. The set of capabilities a solution must deliver in order to meet the business need.
Glossary
Decision Analysis
Solution Scope
Event
23. The process of checking that a deliverable produced at a given stage of development satisfies the conditions or specifications of the previous stage. Ensures that you built the solution correctly.
Business Policy
Technique
Verification
Developer
24. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).
Return on Investment
Requirements Allocation
Capability
Request For Quote (RFQ)
25. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.
Sequence Diagram
Project Scope
Requirement
Business Architecture
26. Formal approval of a set of requirements by a sponsor or other decision maker.
Requirements Workshop
Requirements Signoff
Dialog Map
Incremental Delivery
27. A conceptual view of all or part of an enterprise focusing on products deliverables and events that are important to the mission of the organization. Is useful to validate the solution scope with the business and technical stakeholders. See also mode
Prototype
Association
Business Domain Model
Requirements Risk Mitigation Strategy
28. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.
Solution Scope
Secondary Actor
Project Manager
Competitive Analysis
29. 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.
Technique
Monitoring
Horizontal Prototype
Requirements Management Tool
30. Metadata related to a requirement used to assist with requirements development and management.
Monitoring
Optionality
Requirements Management Tool
Requirement(s) Attribute
31. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.
Decision Tree
Requirements Risk Mitigation Strategy
Change Control Board (CCB)
Risk
32. The quality attributes design and implementation constraints and external interfaces that the product must have.
Non-functional Requirement(s)
Feature
Quality Assurance
Association
33. A fixed period of time to accomplish a desired outcome.
Code
Timebox
Change Control Board (CCB)
Quality Assurance
34. The number of occurrences of one entity in a data model that are linked to a second entity. Is shown on a data model with a special notation number (e.g. 1) or letter (e.g. M for many).
Lessons Learned Process
Relationship Map
Business Requirements Document
Cardinality
35. An analysis model in table format that defines the events (i.e. the input stimuli that trigger the system to carry out some function) and their responses.
Regulator
Business Goal
Plan-driven Methodology
Event Response Table
36. Information that is used to understand the context and validity of information recorded in a system.
Stakeholder Requirement
Product
Model(s)
Metadata
37. A prototype used to quickly uncover and clarify interface requirements using simple tools sometimes just paper and pencil. Usually discarded when the final system has been developed.
Relationship
Throw-away Prototype
Document Analysis
Operative Rule(s)
38. All materials used by groups within an organization to define tailor implement and maintain their processes.
Gap Analysis
Elicitation
Organizational Process Asset
Included Use Cases
39. A link between two elements or objects in a diagram.
Vision Statement (product vision statement)
Organization Modeling
Requirement
Association
40. A type of high-level business requirement that is a statement of a business objective or an impact the solution should have on its environment.
Use Case
Evolutionary Prototype
Request For Proposal (RFP)
Business Need(s)
41. An analysis model that describes the tasks that the system will perform for actors and the goals that the system achieves for those actors along the way.
Plan-driven Methodology
Decision Tree
Use Case
Throw-away Prototype
42. The business benefits that will result from meeting the business need and the end state desired by stakeholders.
Organizational Unit
Desired Outcome
Decomposition
User Requirements Document
43. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
Model(s)
Gap Analysis
Request For Proposal (RFP)
Knowledge Area
44. Roles and Responsibility DesignationA listing of the stakeholders affected by a business need or proposed solution and a description of their participation in a project or other initiative.
Requirements Iteration
Stakeholder List
Business Requirement
Survey
45. Influencing factors that are believed to be true but have not been confirmed to be accurate.
Assumption
Scope
Model(s)
Enterprise Architecture
46. A structured examination of an identified problem to understand the underlying causes.
Request For Proposal (RFP)
Requirements Model
Root Cause Analysis
Commercial-off-the-Shelf Software (COTS)
47. Any recognized association of people in the context of an organization or enterprise.
Organizational Unit
Organization Modeling
State Diagram
Business Rule(s)
48. A type of diagram that shows objects participating in interactions and the messages exchanged between them.
Work Breakdown Structure (WBS)
Decision Analysis
Constraint
Sequence Diagram
49. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
Constraint
Design Constraints
Defect
Baseline
50. The process of checking a product to ensure that it satisfies its intended use and conforms to its requirements. Ensures that you built the correct solution.
Technical Constraint(s)
Scenario
Validation
End User