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 small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.
Validated Requirements
Object Oriented Modeling
Change Control Board (CCB)
Benchmarking
2. A measure of the profitability of a project or investment.
Interface
Return on Investment
Model(s)
Observation
3. 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.
Subject Matter Expert (SME)
Force Field Analysis
Iteration
Technique
4. 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.
Technical Constraint(s)
Requirement
Organization
Impact Analysis
5. A structured examination of an identified problem to understand the underlying causes.
Gap Analysis
Activity
Root Cause Analysis
Methodology
6. 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
Attribute
Project Charter
Knowledge Area
7. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.
Technique
Data Dictionary
Iteration
Requirements Trace Matrix
8. A type of peer review in which participants present discuss and step through a work product to find errors. Are used to verify the correctness of requirements.
Requirement
Organization
Walkthrough
Data Model
9. 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.
Enterprise Architecture
Analyst
Stated Requirements
Event Response Table
10. Software requirements that limit the options available to the system designer.
Structured Walkthrough
Regulator
Design Constraints
Non-functional Requirement(s)
11. The problem area undergoing analysis.
Requirements Verification
Actor(s)
Activity Diagram
Domain
12. Formal approval of a set of requirements by a sponsor or other decision maker.
Customer
Use Case
Desired Outcome
Requirements Signoff
13. A set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Are triggered by events and may have multiple possible outcomes. A successful outcome of a process will deliver value to one or more s
Supplier
Use Case Diagram
Business Process
Stakeholder List
14. A link between two elements or objects in a diagram.
Knowledge Area
System
Association
Metadata
15. 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
Commercial-off-the-Shelf Software (COTS)
Object Oriented Modeling
Problem Statement
Analyst
16. 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.
Relationship Map
Elicitation
Horizontal Prototype
User Requirements Document
17. Limitations on the design of a solution that derive from the technology used in its implementation.
Technical Constraint(s)
Requirements Validation
Use Case
Requirements Risk Mitigation Strategy
18. 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.
Checklist
Business Analysis
Business Rule(s)
Observation
19. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
Model(s)
Requirements Management Tool
Business Policy
Gap Analysis
20. Metadata related to a requirement used to assist with requirements development and management.
Requirement(s) Attribute
Business Analyst
Decision Analysis
Work Breakdown Structure (WBS)
21. 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.
Subject Matter Expert (SME)
Association
Use Case
Competitive Analysis
22. A unit of work performed as part of an initiative or process.
Interoperability
Iteration
Activity
Regulator
23. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.
Structural Rule
Fishbone Diagram
Business Analysis Plan
Change Control Board (CCB)
24. 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.
Cardinality
Interview
Capability
Walkthrough
25. A prototype that dives into the details of the interface functionality or both.
Event Response Table
Requirement
Fishbone Diagram
Vertical Prototype
26. Interfaces with other systems (hardware software and human) that a proposed system will interact with.
Quality Assurance
External Interfaces
Project Scope
Checklist
27. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.
Swimlane
Domain
Optionality
Observation
28. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.
Problem Statement
Transition Requirement(s)
Requirements Model
Process Model
29. 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.
User Acceptance Test
Iteration
Methodology
Evolutionary Prototype
30. An actor who participates in but does not initiate a use case.
User Requirements Document
Secondary Actor
Business Analysis Approach
Scope
31. Roles and Responsibility DesignationA listing of the stakeholders affected by a business need or proposed solution and a description of their participation in a project or other initiative.
Deliverable
Stakeholder List
Business Need(s)
Implementation Subject Matter Expert (SME)
32. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.
Defect
Use Case Diagram
Business Analyst
Requirements Allocation
33. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.
Quality Assurance
Document Analysis
Functional Requirement(s)
Change-driven Methodology
34. The features and functions that characterize a product service or result.
Product Scope
Stated Requirements
Requirements Workshop
Actor(s)
35. 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
Requirements Verification
Requirements Workshop
Requirement(s) Defect
Interface
36. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.
Deliverable
System
Interoperability
Prototype
37. The set of capabilities a solution must deliver in order to meet the business need.
Attribute
Business Domain Model
Requirement
Solution Scope
38. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.
Requirements Management
Opportunity Analysis
Context Diagram
Requirements Management Tool
39. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.
Enterprise Architecture
Organization
Desired Outcome
Repository
40. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.
Defect
Organizational Unit
End User
Survey
41. A stakeholder who uses products or services delivered by an organization.
Domain
Stated Requirements
Customer
Entity-Relationship Diagram
42. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.
Request For Information (RFI)
Business Case
User Acceptance Test
Decomposition
43. An informal solicitation of proposals from vendors.
Request For Quote (RFQ)
Opportunity Analysis
Business Architecture
Repository
44. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.
Walkthrough
Solution Requirement
Sponsor
Object Oriented Modeling
45. An analysis model that shows user interface dialogs arranged as hierarchies.
Dialog Hierarchy
Class Model
Data Dictionary
Requirements Verification
46. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.
Product
State Diagram
Risk
Decision Tree
47. A use case composed of a common set of steps used by multiple use cases.
Included Use Cases
Brainstorming
Data Entity
Verified Requirements
48. The degree to which a set of inherent characteristics fulfills requirements.
Requirements Signoff
Quality
Stakeholder
Interoperability
49. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.
Focus Group
Stakeholder List
Inspection
SWOT Analysis
50. A stakeholder with legal or governance authority over the solution or the process used to develop it.
Process Model
Functional Requirement(s)
Regulator
Interoperability