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 uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.
Brainstorming
Risk
Requirements Allocation
Metric
2. 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.
Business Rule(s)
User Story
Stated Requirements
Activity Diagram
3. A unit of work performed as part of an initiative or process.
Focus Group
Constraint
Activity
Entity-Relationship Diagram
4. Software requirements that limit the options available to the system designer.
Black Box Tests
Request For Proposal (RFP)
Design Constraints
Requirements Traceability
5. A system trigger that is initiated by time.
Temporal Event
Sequence Diagram
Feature
Business Rule(s)
6. An autonomous unit within an enterprise under the management of a single individual or board with a clearly defined boundary that works towards common goals and objectives. Operate on a continuous basis as opposed to an organizational unit or project
Requirements Validation
Force Field Analysis
Walkthrough
Organization
7. A prototype developed to explore or verify requirements.
Business Analysis
Data Flow Diagram (DFD)
Verification
Exploratory Prototype
8. 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.
Project Manager
Requirements Model
Subject Matter Expert (SME)
Requirements Workshop
9. 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.
Use Case
Decomposition
Request For Quote (RFQ)
Throw-away Prototype
10. An assessment of the costs and benefits associated with a proposed initiative.
Project Manager
Business Policy
Business Case
Evolutionary Prototype
11. A structured process which captures the key characteristics of an industry to predict the long-term profitability prospects and to determine the practices of the most significant competitors.
Requirements Traceability
Technical Constraint(s)
Competitive Analysis
Software/Systems Requirements Specification
12. A non-actionable directive that supports a business goal.
Scenario
Requirements Workshop
Solution Scope
Business Policy
13. The work that must be performed to deliver a product service or result with the specified features and functions.
Project Scope
Requirements Risk Mitigation Strategy
Supplier
Stakeholder Analysis
14. 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
Requirements Iteration
Temporal Event
Lessons Learned Process
Customer
15. 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
Verification
Iteration
16. 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 Validation
Repository
SWOT Analysis
End User
17. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).
Quality Attributes
Use Case Diagram
Project
Cost Benefit Analysis
18. A fixed period of time to accomplish a desired outcome.
Customer
Solution Scope
Timebox
Gap Analysis
19. The systematic and objective assessment of a solution to determine its status and efficacy in meeting objectives over time and to identify ways to improve the solution to better meet objectives. See also metric indicator and monitoring.
Scenario
Document Analysis
Evaluation
Enterprise Architecture
20. 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
Business Constraint(s)
Sponsor
Return on Investment
User Requirements Document
21. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.
User Story
Business Requirement
Metric
Elicitation
22. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.
Requirements Iteration
Decomposition
Requirements Allocation
Organization Modeling
23. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.
Quality Assurance
Vision Statement (product vision statement)
Dialog Hierarchy
Requirements Workshop
24. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.
Technique
Business Requirement
Data Flow Diagram (DFD)
Brainstorming
25. 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.
Horizontal Prototype
Requirements Management
Exploratory Prototype
Impact Analysis
26. A use case composed of a common set of steps used by multiple use cases.
User
Project Manager
Data Entity
Included Use Cases
27. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.
Transition Requirement(s)
Sponsor
State Diagram
Swimlane
28. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.
Requirements Trace Matrix
Organizational Readiness Assessment
Organization
Baseline
29. A requirements document issued to solicit vendor input on a proposed process or product. Is used when the issuing organization seeks to compare different alternatives or is uncertain regarding the available options
Vertical Prototype
Enterprise Architecture
Request For Information (RFI)
Change Control Board (CCB)
30. A prototype that dives into the details of the interface functionality or both.
Vertical Prototype
Validated Requirements
Project Charter
Model(s)
31. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.
Design Constraints
Requirements Trace Matrix
Vertical Prototype
Requirements Management Tool
32. A set of requirements grouped together in a document or presentation for communication to stakeholders.
Business Goal
Problem Statement
Requirements Package
Risk
33. Information that is used to understand the context and validity of information recorded in a system.
Metadata
Model(s)
Event
User
34. A partial or preliminary version of the system.
Business Rule(s)
Prototype
Business Event
Constraint
35. A practitioner of business analysis.
Business Analyst
Prioritization
Business Requirement
User Requirements Document
36. 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.
Walkthrough
Implementation Subject Matter Expert (SME)
Throw-away Prototype
Domain Subject Matter Expert (SME)
37. An analysis model that shows user interface dialogs arranged as hierarchies.
Knowledge Area
Dialog Hierarchy
Black Box Tests
Prototype
38. A target or metric that a person or organization seeks to meet in order to progress towards a goal.
Span of Control
Work Product
Analyst
Objective
39. A process improvement technique used to learn about and improve on a process or project. Involves a special meeting in which the team explores what worked what didn't work what could be learned from the just-completed iteration and how to adapt proce
Activity
Activity Diagram
Structural Rule
Lessons Learned Process
40. A prototype used to quickly uncover and clarify interface requirements using simple tools sometimes just paper and pencil. Usually discarded when the final system has been developed.
Vision Statement (product vision statement)
Scenario
Throw-away Prototype
Peer Review
41. A prototype that is continuously modified and updated in response to feedback from users.
Checklist
Validation
Stakeholder Requirement
Evolutionary Prototype
42. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.
Root Cause Analysis
Monitoring
Product
Entity-Relationship Diagram
43. 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.
Business Constraint(s)
Product
Lessons Learned Process
Process Map
44. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.
Enterprise Architecture
Organization Modeling
Competitive Analysis
Opportunity Analysis
45. Any recognized association of people in the context of an organization or enterprise.
Organizational Unit
Stakeholder Requirement
Problem Statement
Feasibility Study
46. An analysis model that illustrates the architecture of the system's user interface.
Business Process
Requirements Validation
Scope
Dialog Map
47. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.
SWOT Analysis
Actor(s)
Interview
Black Box Tests
48. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.
Evaluation
Subject Matter Expert (SME)
Scope
Software/Systems Requirements Specification
49. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.
Event
Quality Assurance
Sponsor
Transition Requirement(s)
50. A group of related tasks that support a key function of business analysis.
Technical Constraint(s)
Knowledge Area
Solution
User Requirements Document