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 analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.
Object Oriented Modeling
Data Model
Process Map
Capability
2. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.
Enterprise Architecture
Tester
Work Breakdown Structure (WBS)
Requirements Package
3. 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.
Prototype
Context Diagram
Objective
Iteration
4. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.
Vision Statement (product vision statement)
Entity-Relationship Diagram
Developer
Actor(s)
5. 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.
Enterprise Architecture
End User
Requirements Management
Elicitation
6. 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
Class Model
Black Box Tests
Request For Proposal (RFP)
User Story
7. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.
Business Requirement
Structural Rule
Project Scope
Metric
8. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.
Design Constraints
User Requirements Document
Business Constraint(s)
Organization
9. A fixed period of time to accomplish a desired outcome.
Business Policy
Business Goal
Timebox
Object Oriented Modeling
10. A system trigger that is initiated by humans.
Business Event
Use Case Diagram
Requirement(s) Defect
Business Domain Model
11. A generic name for a role with the responsibilities of developing and managing requirements. Other names include business analyst business integrator requirements analyst requirements engineer and systems analyst.
Requirements Signoff
Decomposition
Analyst
Requirements Package
12. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.
Object Oriented Modeling
Stakeholder List
Entity-Relationship Diagram
Sponsor
13. A use case composed of a common set of steps used by multiple use cases.
Use Case Diagram
Included Use Cases
Feature
Scope
14. 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.
Process Map
Baseline
Activity
User Story
15. 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.
Request For Quote (RFQ)
Event Response Table
Project Charter
Non-functional Requirement(s)
16. The number of employees a manger is directly (or indirectly) responsible for.
Span of Control
Survey
Stakeholder Requirement
Business Analysis Approach
17. A type of data model that depicts information groups as classes.
Evaluation
Class Model
Work Product
Tester
18. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.
User
Black Box Tests
Work Breakdown Structure (WBS)
Competitive Analysis
19. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.
Process Map
Root Cause Analysis
Technique
Change Control Board (CCB)
20. 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.
Business Need(s)
Requirements Model
Repository
Impact Analysis
21. 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.
Enterprise Architecture
Methodology
Requirements Workshop
Dialog Map
22. A partial or preliminary version of the system.
Work Product
Project Manager
Prototype
Quality
23. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.
Prioritization
Problem Statement
Data Dictionary
Desired Outcome
24. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.
Object Oriented Modeling
Organization Modeling
Requirement(s) Defect
Return on Investment
25. Software developed and sold for a particular market.
Cost Benefit Analysis
Inspection
Indicator
Commercial-off-the-Shelf Software (COTS)
26. 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.
Non-functional Requirement(s)
Object Oriented Modeling
Business Analysis Plan
Code
27. 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.
Repository
Requirement
Change-driven Methodology
Implementation Subject Matter Expert (SME)
28. A stakeholder who uses products or services delivered by an organization.
Competitive Analysis
Customer
Cardinality
Technical Constraint(s)
29. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.
Initiative
Brainstorming
Constraint
Requirements Management
30. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.
Operative Rule(s)
Monitoring
Supplier
Optionality
31. A data element with a specified data type that describes information associated with a concept or entity.
Requirement(s) Attribute
Metadata
Competitive Analysis
Attribute
32. 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).
User
Requirements Signoff
Scope
Cardinality
33. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.
Scope
Solution
Return on Investment
External Interfaces
34. An analysis model describing the data structures and attributes needed by the system.
Inspection
Use Case Diagram
Data Dictionary
Business Process
35. 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.
Stated Requirements
Requirements Model
Developer
Iteration
36. 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.
Request For Proposal (RFP)
Use Case
Stated Requirements
Swimlane
37. A practitioner of business analysis.
Data Entity
Quality Attributes
Process Model
Business Analyst
38. Creating working software in multiple releases so the entire product is delivered in portions over time.
Incremental Delivery
Dialog Hierarchy
Customer
Change Control Board (CCB)
39. 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.
Optionality
Verified Requirements
Enterprise Architecture
Interview
40. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.
Survey
Product Backlog
Fishbone Diagram
Operational Support
41. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.
Variance Analysis
Brainstorming
Quality Assurance
Elicitation
42. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.
Plan-driven Methodology
Requirements Management Tool
Defect
Requirements Trace Matrix
43. A measure of the profitability of a project or investment.
Return on Investment
Entity-Relationship Diagram
Gap Analysis
Competitive Analysis
44. A stakeholder who provides products or services to an organization.
Deliverable
Use Case
Supplier
Interface
45. 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 Validation
Product Backlog
Requirements Traceability
Business Policy
46. Interfaces with other systems (hardware software and human) that a proposed system will interact with.
Objective
Operative Rule(s)
Checklist
External Interfaces
47. A function of an organization that enables it to achieve a business goal or objective.
Capability
Use Case Diagram
Requirements Allocation
Requirements Signoff
48. 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.
Requirements Model
Model(s)
Decomposition
End User
49. 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.
Project Charter
Prioritization
Requirement
Validated Requirements
50. The set of capabilities a solution must deliver in order to meet the business need.
Business Analysis
Initiative
Solution Scope
Requirements Verification