SUBJECTS
|
BROWSE
|
CAREER CENTER
|
POPULAR
|
JOIN
|
LOGIN
Business Skills
|
Soft Skills
|
Basic Literacy
|
Certifications
About
|
Help
|
Privacy
|
Terms
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. A document or collection of notes or diagrams used by the business analyst during the requirements development process.
Requirements Management Tool
Lessons Learned Process
Work Product
Relationship
2. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.
Interface
Objective
Functional Requirement(s)
Problem Statement
3. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.
Event
Functional Requirement(s)
Use Case
Relationship
4. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.
Gap Analysis
Requirement(s) Attribute
Monitoring
Change Control Board (CCB)
5. Information that is used to understand the context and validity of information recorded in a system.
Metadata
Desired Outcome
Business Event
Stakeholder Requirement
6. Influencing factors that are believed to be true but have not been confirmed to be accurate.
Assumption
Organization Modeling
Inspection
Secondary Actor
7. A unit of work performed as part of an initiative or process.
Requirements Workshop
Design Constraints
Activity
Inspection
8. 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.
Verification
Activity Diagram
Requirements Model
Decision Tables
9. 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
Requirements Management
Requirements Iteration
Optionality
Stakeholder Requirement
10. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.
Validated Requirements
Regulator
Requirements Management Tool
Elicitation
11. Work carried out or on behalf of others.
User Acceptance Test
Elicitation
Operational Support
Service
12. 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.
Event
Throw-away Prototype
Dialog Map
Association
13. Limitations on the design of a solution that derive from the technology used in its implementation.
Dialog Map
Technical Constraint(s)
Brainstorming
Stakeholder Requirement
14. 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.
Business Analysis Approach
Elicitation
Implementation Subject Matter Expert (SME)
Return on Investment
15. Any methodology that emphasizes planning and formal documentation of the processes used to accomplish a project and of the results of the project. Emphasize the reduction of risk and control over outcomes over the rapid delivery of a solution.
Secondary Actor
System
Plan-driven Methodology
Requirements Signoff
16. The systematic and objective assessment of a solution to determine its status and efficacy in meeting objectives over time and to identify ways to improve the solution to better meet objectives. See also metric indicator and monitoring.
End User
Use Case
Evaluation
Software/Systems Requirements Specification
17. A classification of requirements that describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to the desired future state but that will not be needed once that transition is complet
Transition Requirement(s)
Focus Group
Requirements Verification
Data Dictionary
18. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.
Service
Peer Review
Requirements Model
Metric
19. The work that must be performed to deliver a product service or result with the specified features and functions.
Organizational Process Asset
Project Scope
Interface
Relationship Map
20. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
Constraint
Business Process
Evolutionary Prototype
Requirements Package
21. An organizational unit organization or collection of organizations that share a set of common goals and collaborate to provide specific products or services to customers.
Business Rule(s)
Fishbone Diagram
Business Requirement
Enterprise
22. 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).
Requirements Iteration
Cardinality
Business Analysis Approach
Regulator
23. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.
Decision Tables
Requirements Validation
Business Goal
Change-driven Methodology
24. The set of processes templates and activities that will be used to perform business analysis in a specific context.
Dialog Hierarchy
Developer
Baseline
Business Analysis Approach
25. The number of employees a manger is directly (or indirectly) responsible for.
Walkthrough
Span of Control
Operative Rule(s)
Business Case
26. A group or person who has interests that may be affected by an initiative or influence over it.
Requirements Package
Assumption
Tester
Stakeholder
27. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.
Impact Analysis
Methodology
Requirements Iteration
Activity
28. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.
Requirements Risk Mitigation Strategy
Data Flow Diagram (DFD)
Metadata
Commercial-off-the-Shelf Software (COTS)
29. A stakeholder who will be responsible for designing developing and implementing the change described in the requirements and have specialized knowledge regarding the construction of one or more solution components.
Requirements Workshop
Implementation Subject Matter Expert (SME)
Exploratory Prototype
Business Analysis Approach
30. 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.
Use Case
SWOT Analysis
Sponsor
Association
31. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.
Business Rule(s)
Solution
Business Constraint(s)
Attribute
32. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.
Requirements Trace Matrix
Project Scope
Unified Modeling Language (UML)
Use Case
33. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.
Requirements Package
Business Domain Model
Optionality
Stakeholder Requirement
34. 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.
Product Backlog
Horizontal Prototype
Dialog Hierarchy
Entity-Relationship Diagram
35. An approach to software engineering where software is comprised of components that are encapsulated groups of data and functions which can inherit behavior and attributes from other components; and whose components communicate via messages with one a
Class
Functional Requirement(s)
Object Oriented Modeling
Repository
36. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.
Business Analysis
Scenario
Requirements Trace Matrix
Knowledge Area
37. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.
Requirements Model
Quality Assurance
Stated Requirements
Sponsor
38. An analysis model that illustrates product scope by showing the system in its environment with the external entities (people and systems) that give to and receive from the system.
Product Backlog
Context Diagram
Capability
Span of Control
39. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.
Business Goal
Class Model
Data Flow Diagram (DFD)
Prioritization
40. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.
Requirements Management
Decision Tables
Work Breakdown Structure (WBS)
Sponsor
41. Test cases that users employ to judge whether the delivered system is acceptable. Each acceptance test describes a set of system inputs and expected results.
Stakeholder Requirement
User Acceptance Test
Business Analysis Plan
Request For Proposal (RFP)
42. A measure of the profitability of a project or investment.
Stated Requirements
Event
Business Process
Return on Investment
43. The set of capabilities a solution must deliver in order to meet the business need.
Project Charter
User Requirements Document
Business Requirement
Solution Scope
44. A formal type of peer review that utilizes a predefined and documented process specific participant roles and the capture of defect and process metrics. See also structured walkthrough.
Deliverable
Inspection
Tester
Interface
45. The quality attributes design and implementation constraints and external interfaces that the product must have.
Subject Matter Expert (SME)
Quality
Non-functional Requirement(s)
Defect
46. An informal solicitation of proposals from vendors.
Request For Proposal (RFP)
Request For Quote (RFQ)
Use Case
Process Map
47. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.
Stated Requirements
Process Map
Fishbone Diagram
Class
48. A target or metric that a person or organization seeks to meet in order to progress towards a goal.
Objective
Survey
Data Model
Code
49. The area covered by a particular activity or topic of interest.
Scope
Exploratory Prototype
Business Process
Request For Quote (RFQ)
50. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.
Class Model
Data Entity
End User
Work Breakdown Structure (WBS)