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. A person or system that directly interacts with the solution. Can be humans who interface with the system or systems that send or receive data files to or from the system.
End User
Included Use Cases
Interoperability
Business Analysis Plan
2. A state or condition the business must satisfy to reach its vision.
Design Constraints
Business Goal
Request For Information (RFI)
Black Box Tests
3. 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
Organizational Unit
Stakeholder Requirement
Constraint
Software/Systems Requirements Specification
4. 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.
Feasibility Study
Organization
Requirements Signoff
Event Response Table
5. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).
Model(s)
Business Requirements Document
Business Analysis Plan
Lessons Learned Process
6. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.
Business Goal
Scope
Change Control Board (CCB)
Quality Attributes
7. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.
Scenario
Enterprise Architecture
Supplier
Subject Matter Expert (SME)
8. The product capabilities or things the product must do for its users.
Business Case
Requirements Validation
Stakeholder Analysis
Functional Requirement(s)
9. A non-actionable directive that supports a business goal.
Prototype
Unified Modeling Language (UML)
Business Policy
Attribute
10. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.
Analyst
Tester
Design Constraints
Requirements Management
11. A solution or component of a solution that is the result of a project.
Product
Functional Requirement(s)
Prototype
Requirements Package
12. 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.
Service
User Acceptance Test
Competitive Analysis
Feature
13. 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.
Project
Implementation Subject Matter Expert (SME)
Metadata
Prototype
14. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.
Requirements Model
Developer
Requirements Allocation
Risk
15. 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.
Root Cause Analysis
Business Policy
Requirements Traceability
Quality Attributes
16. Interfaces with other systems (hardware software and human) that a proposed system will interact with.
Organizational Unit
Benchmarking
External Interfaces
Competitive Analysis
17. A stakeholder with legal or governance authority over the solution or the process used to develop it.
Elicitation
Regulator
Product Backlog
Objective
18. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.
Quality Assurance
Business Analysis Communication Plan
Feasibility Study
Peer Review
19. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.
Competitive Analysis
Business Process
Optionality
Developer
20. A link between two elements or objects in a diagram.
Use Case
Association
Business Goal
Verified Requirements
21. An assessment of the costs and benefits associated with a proposed initiative.
Business Case
Requirement
Methodology
Lessons Learned Process
22. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.
Technical Constraint(s)
Glossary
Sponsor
Requirements Management Plan
23. An analysis model describing the data structures and attributes needed by the system.
Constraint
User Requirements Document
Methodology
Data Dictionary
24. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.
Requirements Validation
Swimlane
Evolutionary Prototype
Monitoring
25. The human and nonhuman roles that interact with the system.
Attribute
Object Oriented Modeling
Actor(s)
Temporal Event
26. 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.
Checklist
Process Map
Risk
Work Breakdown Structure (WBS)
27. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).
Quality Attributes
Requirements Allocation
Walkthrough
Knowledge Area
28. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
State Diagram
Requirement(s) Defect
Constraint
Business Analyst
29. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.
Solution
Tester
Business Policy
Optionality
30. A set of requirements grouped together in a document or presentation for communication to stakeholders.
Stakeholder List
Request For Information (RFI)
Requirements Package
Vertical Prototype
31. 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
Decision Tables
Class
Black Box Tests
Technique
32. A process in which a deliverable (or the solution overall) is progressively elaborated upon. Will result in a self-contained "mini-project" in which a set of activities are undertaken resulting in the development of a subset of project deliverables.
Service
Iteration
Optionality
Functional Requirement(s)
33. A requirements document issued when an organization is seeking a formal proposal from vendors. Typically requires that the proposals be submitted following a specific process and using sealed bids which will be evaluated against a formal evaluation m
Request For Proposal (RFP)
Black Box Tests
Scope Model
Sponsor
34. Work carried out or on behalf of others.
Baseline
Service
Design Constraints
Data Flow Diagram (DFD)
35. Creating working software in multiple releases so the entire product is delivered in portions over time.
Business Analysis Approach
Incremental Delivery
Deliverable
Secondary Actor
36. A group of related tasks that support a key function of business analysis.
Business Constraint(s)
Knowledge Area
Scenario
Operational Support
37. 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.
Elicitation
Scope
Use Case
Peer Review
38. An error in requirements caused by incorrect incomplete missing or conflicting requirements.
Operative Rule(s)
Throw-away Prototype
Requirement(s) Defect
Optionality
39. A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract standard specification or other formally imposed documents.
Glossary
Product Backlog
Requirement
Model(s)
40. Limitations placed on the solution design by the organization that needs the solution. Describe limitations on available solutions or an aspect of the current state that cannot be changed by the deployment of the new solution. See also technical cons
Stakeholder
Gap Analysis
Business Constraint(s)
Model(s)
41. The degree to which a set of inherent characteristics fulfills requirements.
Exploratory Prototype
Variance Analysis
Operational Support
Quality
42. A partial or preliminary version of the system.
Requirements Package
SWOT Analysis
Prototype
Decision Tables
43. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.
Impact Analysis
Data Flow Diagram (DFD)
Data Model
Analyst
44. A practitioner of business analysis.
Business Analyst
Business Domain Model
Document Analysis
Data Dictionary
45. An analysis model showing the life cycle of a data entity or class.
Return on Investment
State Diagram
Stakeholder Analysis
Exploratory Prototype
46. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.
Use Case Diagram
Glossary
Timebox
Developer
47. Any unique and verifiable work product or service that a party has agreed to deliver.
Deliverable
Throw-away Prototype
Organizational Process Asset
Elicitation
48. Any effort undertaken with a defined goal or objective.
Stakeholder List
Initiative
Requirements Iteration
Domain
49. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.
Evolutionary Prototype
Solution
Class
Requirements Model
50. The business rules an organization chooses to enforce as a matter of policy. They are intended to guide the actions of people working within the business. They may oblige people to take certain actions prevent people from taking actions or prescribe
Deliverable
Knowledge Area
Operative Rule(s)
Return on Investment