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 type of high-level business requirement that is a statement of a business objective or an impact the solution should have on its environment.
Structured Walkthrough
Service
Interface
Business Need(s)
2. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.
Business Case
Organization Modeling
Requirements Allocation
Requirements Model
3. 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
Survey
Business Domain Model
Functional Requirement(s)
Business Analysis Approach
4. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.
Iteration
System
Dialog Map
Brainstorming
5. Information that is used to understand the context and validity of information recorded in a system.
Metadata
Temporal Event
Requirements Model
Repository
6. Formal approval of a set of requirements by a sponsor or other decision maker.
Capability
Requirements Signoff
Enterprise Architecture
Indicator
7. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.
Actor(s)
Business Requirement
Knowledge Area
Requirement
8. The quality attributes design and implementation constraints and external interfaces that the product must have.
Non-functional Requirement(s)
Monitoring
SWOT Analysis
Indicator
9. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.
Organizational Process Asset
Observation
Inspection
Organization
10. 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.
Regulator
Benchmarking
Activity Diagram
Requirements Signoff
11. A means to elicit ideas and attitudes about a specific product service or opportunity in an interactive group environment. The participants share their impressions preferences and needs guided by a moderator.
Business Process
Verification
Focus Group
Process Model
12. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.
Incremental Delivery
Unified Modeling Language (UML)
Solution Requirement
Survey
13. 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
Unified Modeling Language (UML)
Class Model
Object Oriented Modeling
Initiative
14. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.
Business Analysis Communication Plan
Lessons Learned Process
Entity-Relationship Diagram
Code
15. 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)
Business Analyst
Unified Modeling Language (UML)
Brainstorming
16. 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.
Variance Analysis
User Acceptance Test
Requirements Management
Operational Support
17. A type of data model that depicts information groups as classes.
Solution Scope
Exploratory Prototype
Work Breakdown Structure (WBS)
Class Model
18. A partial or preliminary version of the system.
Prototype
Supplier
Vision Statement (product vision statement)
Code
19. 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
Quality Assurance
Business Analysis Communication Plan
Class
Requirements Allocation
20. A function of an organization that enables it to achieve a business goal or objective.
Activity Diagram
Stated Requirements
Solution Requirement
Capability
21. Influencing factors that are believed to be true but have not been confirmed to be accurate.
User Acceptance Test
Cost Benefit Analysis
Assumption
Throw-away Prototype
22. An analysis model that illustrates the architecture of the system's user interface.
Requirements Model
Dialog Map
Requirements Workshop
Brainstorming
23. 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.
Business Analysis Plan
Interoperability
Deliverable
Horizontal Prototype
24. An iteration that defines requirements for a subset of the solution scope. Would include identifying a part of the overall product scope to focus upon identifying requirements sources for that portion of the product analyzing stakeholders and plannin
SWOT Analysis
Data Model
Requirements Iteration
Fishbone Diagram
25. A data element with a specified data type that describes information associated with a concept or entity.
Scope Model
Attribute
Desired Outcome
Work Breakdown Structure (WBS)
26. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.
Business Rule(s)
Impact Analysis
Organizational Unit
Object Oriented Modeling
27. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.
Domain Subject Matter Expert (SME)
Plan-driven Methodology
Business Policy
Subject Matter Expert (SME)
28. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).
Technical Constraint(s)
Requirements Allocation
Swimlane
Quality Assurance
29. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
User
Requirements Management
Requirement
Model(s)
30. A unit of work performed as part of an initiative or process.
Objective
Risk
Activity
Entity-Relationship Diagram
31. 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
Product Backlog
Customer
Design Constraints
32. A group of related tasks that support a key function of business analysis.
Fishbone Diagram
Knowledge Area
Requirements Traceability
Validated Requirements
33. 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.
Walkthrough
Assumption
Force Field Analysis
Project Manager
34. An actor who participates in but does not initiate a use case.
Secondary Actor
Swimlane
Knowledge Area
Brainstorming
35. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.
Business Analysis
Solution
Impact Analysis
Design Constraints
36. 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.
Association
Business Analysis Communication Plan
Data Flow Diagram (DFD)
Business Requirement
37. A state or condition the business must satisfy to reach its vision.
Business Goal
Request For Information (RFI)
External Interfaces
Request For Quote (RFQ)
38. Metadata related to a requirement used to assist with requirements development and management.
Tester
Commercial-off-the-Shelf Software (COTS)
Requirement(s) Attribute
SWOT Analysis
39. A description of the requirements management process.
Requirements Management Plan
Enterprise Architecture
Iteration
Object Oriented Modeling
40. A type of diagram that shows objects participating in interactions and the messages exchanged between them.
Sequence Diagram
Validated Requirements
Variance Analysis
Return on Investment
41. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.
Business Analysis
Activity Diagram
Requirements Validation
Regulator
42. An analysis model showing the life cycle of a data entity or class.
Checklist
Code
State Diagram
Organizational Process Asset
43. 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.
Requirement
Event
Objective
Feasibility Study
44. 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.
Requirement
Use Case
Object Oriented Modeling
Metadata
45. A system trigger that is initiated by time.
Temporal Event
Organization Modeling
Use Case Diagram
Assumption
46. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Work Breakdown Structure (WBS)
Stakeholder Analysis
Requirements Iteration
Use Case Diagram
47. A practitioner of business analysis.
Optionality
Business Analyst
Process Model
Quality
48. 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.
Context Diagram
Included Use Cases
Requirements Management Plan
Feasibility Study
49. A system of programming statements symbols and rules used to represent instructions to a computer.
Software/Systems Requirements Specification
Deliverable
Code
Relationship
50. 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.
Requirements Management Plan
Transition Requirement(s)
Evaluation
Cost Benefit Analysis