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. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).
Evaluation
Sponsor
Requirements Allocation
Business Analysis Communication Plan
2. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.
Relationship Map
Defect
Methodology
Requirements Management
3. The features and functions that characterize a product service or result.
Data Entity
Evaluation
Product Scope
Requirements Risk Mitigation Strategy
4. 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.
Sequence Diagram
Business Analysis
Dialog Hierarchy
Service
5. 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.
Work Breakdown Structure (WBS)
Benchmarking
Verification
Span of Control
6. Software developed and sold for a particular market.
Requirements Package
Requirements Allocation
Commercial-off-the-Shelf Software (COTS)
End User
7. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.
Dialog Map
Requirements Management Plan
Indicator
Requirements Allocation
8. The work that must be performed to deliver a product service or result with the specified features and functions.
Stated Requirements
Scope
Unified Modeling Language (UML)
Project Scope
9. A shared boundary between any two persons and/or systems through which information is communicated.
Requirements Validation
Walkthrough
Interface
Association
10. 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
Baseline
Activity
Implementation Subject Matter Expert (SME)
Class
11. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.
Fishbone Diagram
Organizational Readiness Assessment
Requirements Verification
Timebox
12. 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.
Survey
Peer Review
Business Requirements Document
Requirements Traceability
13. A description of the planned activities that the business analyst will execute in order to perform the business analysis work involved in a specific initiative.
Software/Systems Requirements Specification
Business Analysis Plan
Use Case Diagram
Survey
14. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).
Risk
Business Requirements Document
Dialog Map
Event Response Table
15. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.
Constraint
Technique
Relationship
Service
16. Analysis done to compare and quantify the financial and non-financial costs of making a change or implementing a solution compared to the benefits gained.
Capability
User Acceptance Test
Software/Systems Requirements Specification
Cost Benefit Analysis
17. A link between two elements or objects in a diagram.
Feasibility Study
Enterprise Architecture
Association
Request For Quote (RFQ)
18. 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
Product Backlog
Transition Requirement(s)
Swimlane
Model(s)
19. The quality attributes design and implementation constraints and external interfaces that the product must have.
Non-functional Requirement(s)
Decision Analysis
Feature
Secondary Actor
20. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.
Feasibility Study
Methodology
Unified Modeling Language (UML)
Return on Investment
21. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
Model(s)
Actor(s)
Horizontal Prototype
Analyst
22. Work carried out or on behalf of others.
Quality Attributes
Validated Requirements
Business Goal
Service
23. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.
Scope Model
Model(s)
Monitoring
Risk
24. 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.
Requirements Management Tool
Interview
Business Analysis Communication Plan
Data Entity
25. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.
Subject Matter Expert (SME)
Prioritization
Change Control Board (CCB)
Technique
26. A model that defines the boundaries of a business domain or solution.
User Story
Scope Model
Observation
Validation
27. A measure of the profitability of a project or investment.
Return on Investment
Survey
Prototype
Capability
28. 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).
Organization Modeling
Observation
Cardinality
User Acceptance Test
29. A type of data model that depicts information groups as classes.
Structural Rule
Class Model
Business Rule(s)
Black Box Tests
30. All materials used by groups within an organization to define tailor implement and maintain their processes.
Stakeholder Analysis
Requirements Traceability
Organizational Process Asset
Organization
31. A document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.
Project Charter
Requirements Signoff
Black Box Tests
Prioritization
32. A structured examination of an identified problem to understand the underlying causes.
Solution
Root Cause Analysis
Plan-driven Methodology
Requirements Signoff
33. 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.
Decision Analysis
Requirements Validation
Scope Model
Interview
34. 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.
Repository
Requirements Iteration
Requirements Workshop
Decision Tables
35. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.
User Requirements Document
Design Constraints
Data Entity
Methodology
36. 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.
Technical Constraint(s)
Supplier
Event Response Table
Business Case
37. A type of diagram that shows objects participating in interactions and the messages exchanged between them.
Variance Analysis
Process Map
Sequence Diagram
Activity Diagram
38. A use case composed of a common set of steps used by multiple use cases.
Code
Unified Modeling Language (UML)
Domain
Included Use Cases
39. Any effort undertaken with a defined goal or objective.
Initiative
Force Field Analysis
Business Constraint(s)
Stakeholder List
40. A graphical method for depicting the forces that support and oppose a change. Involves identifying the forces depicting them on opposite sides of a line (supporting and opposing forces) and then estimating the strength of each set of forces.
Exploratory Prototype
Subject Matter Expert (SME)
Force Field Analysis
Requirements Model
41. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.
Impact Analysis
Developer
User
Verified Requirements
42. A stakeholder who uses products or services delivered by an organization.
Customer
Force Field Analysis
Data Entity
Validated Requirements
43. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.
Business Event
Requirement(s) Attribute
Swimlane
Requirements Package
44. The work done to evaluate requirements to ensure they are defined correctly and are at an acceptable level of quality. It ensures the requirements are sufficiently defined and structured so that the solution development team can use them in the desig
Business Domain Model
Change Control Board (CCB)
Organization
Requirements Verification
45. Metadata related to a requirement used to assist with requirements development and management.
Organizational Unit
Enterprise
Requirement(s) Attribute
Event Response Table
46. Any unique and verifiable work product or service that a party has agreed to deliver.
Interface
Entity-Relationship Diagram
Elicitation
Deliverable
47. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.
Quality
Metric
Work Breakdown Structure (WBS)
Actor(s)
48. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
Elicitation
Solution
Quality Attributes
Constraint
49. A business model that shows a business process in terms of the steps and input and output flows across multiple functions organizations or job roles.
Feasibility Study
Decision Tables
Process Map
Sequence Diagram
50. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.
Work Product
User
Solution
Scope Model