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 data element with a specified data type that describes information associated with a concept or entity.
Metric
Requirements Validation
User Story
Attribute
2. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.
Metadata
Operative Rule(s)
Solution
Change Control Board (CCB)
3. A deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. It organizes and defines the total scope of the project.
Technique
Decision Tree
Work Breakdown Structure (WBS)
Requirements Management
4. 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.
Structured Walkthrough
Domain
Interview
Desired Outcome
5. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.
Business Analysis
Metadata
Requirements Trace Matrix
Structured Walkthrough
6. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.
Project
Requirements Management Tool
Objective
Subject Matter Expert (SME)
7. Any unique and verifiable work product or service that a party has agreed to deliver.
Deliverable
Cost Benefit Analysis
Competitive Analysis
Business Case
8. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.
Relationship
Actor(s)
Feasibility Study
Data Flow Diagram (DFD)
9. An actor who participates in but does not initiate a use case.
Solution
Secondary Actor
Enterprise Architecture
System
10. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.
Document Analysis
Business Case
Business Rule(s)
Business Requirement
11. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.
Repository
Vision Statement (product vision statement)
Exploratory Prototype
Activity
12. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.
Relationship Map
Regulator
Domain
Checklist
13. Formal approval of a set of requirements by a sponsor or other decision maker.
Business Policy
Requirements Signoff
Assumption
Business Process
14. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.
Activity Diagram
Included Use Cases
System
Black Box Tests
15. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.
Monitoring
Requirements Allocation
Developer
Benchmarking
16. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.
Problem Statement
Black Box Tests
Deliverable
Service
17. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.
User Requirements Document
Defect
Change Control Board (CCB)
Survey
18. 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
Decision Tables
Organization Modeling
Commercial-off-the-Shelf Software (COTS)
19. Any effort undertaken with a defined goal or objective.
Stakeholder Analysis
Context Diagram
Initiative
Technique
20. A prototype that is continuously modified and updated in response to feedback from users.
Process Map
Peer Review
Requirements Management
Evolutionary Prototype
21. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.
Risk
Observation
Business Need(s)
Actor(s)
22. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.
Incremental Delivery
User
Baseline
Requirements Management Tool
23. A cohesive bundle of externally visible functionality that should align with business goals and objectives. Each is a logically related grouping of functional requirements or non-functional requirements described in broad strokes.
Organization Modeling
Span of Control
Feature
Project Manager
24. The human and nonhuman roles that interact with the system.
Actor(s)
Requirements Validation
Operational Support
Product Backlog
25. A quality control technique. They may include a standard set of quality elements that reviewers use for requirements verification and requirements validation or be specifically developed to capture issues of concern to the project.
Data Flow Diagram (DFD)
Methodology
Functional Requirement(s)
Checklist
26. 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.
Enterprise
Competitive Analysis
Organization
Regulator
27. An approach to decision-making that examines and models the possible consequences of different decisions. Assists in making an optimal decision under conditions of uncertainty.
Impact Analysis
Business Goal
Decision Analysis
Focus Group
28. 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.
Evaluation
Business Architecture
Business Analysis Approach
Lessons Learned Process
29. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
Design Constraints
Requirements Package
Constraint
Dialog Map
30. 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.
Implementation Subject Matter Expert (SME)
Secondary Actor
Plan-driven Methodology
Use Case
31. 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.
Regulator
Business Analysis Communication Plan
Class
System
32. A type of data model that depicts information groups as classes.
Class Model
Relationship Map
Process Map
Organization
33. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.
Solution
Fishbone Diagram
Stakeholder List
Operative Rule(s)
34. A system trigger that is initiated by humans.
Business Event
Requirements Trace Matrix
Organizational Process Asset
Unified Modeling Language (UML)
35. A stakeholder who helps to keep the solution functioning either by providing support to end users (trainers help desk) or by keeping the solution operational on a day-to-day basis (network and other tech support).
Business Case
Operational Support
Sponsor
Business Process
36. A formal type of peer review that utilizes a predefined and documented process specific participant roles and the capture of defect and process metrics. See also structured walkthrough.
Inspection
Metric
Requirements Iteration
Requirement
37. 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.
Verification
Code
Business Analysis Plan
Stated Requirements
38. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
External Interfaces
Product Scope
Model(s)
Capability
39. An evaluation of proposed alternatives to determine if they are technically possible within the constraints of the organization and whether they will deliver the desired benefits to the organization.
Model(s)
Feasibility Study
User Requirements Document
Activity
40. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.
Organization Modeling
Request For Information (RFI)
Prototype
Repository
41. A subset of the enterprise architecture that defines an organization's current and future state including its strategy its goals and objectives the internal environment through a process or functional view the external environment in which the busine
Sequence Diagram
Temporal Event
Business Architecture
Stated Requirements
42. A group or person who has interests that may be affected by an initiative or influence over it.
Requirements Iteration
Requirements Traceability
Stakeholder
Gap Analysis
43. A system trigger that is initiated by time.
Force Field Analysis
Product
Cost Benefit Analysis
Temporal Event
44. A stakeholder responsible for assessing the quality of and identifying defects in a software application.
Sequence Diagram
Validation
Tester
Entity-Relationship Diagram
45. A group of related tasks that support a key function of business analysis.
Focus Group
Requirements Package
Requirement(s) Attribute
Knowledge Area
46. The set of processes templates and activities that will be used to perform business analysis in a specific context.
Business Analysis Approach
Prioritization
External Interfaces
Assumption
47. 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
Repository
Request For Information (RFI)
Organizational Readiness Assessment
Validated Requirements
48. 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).
Cardinality
Requirements Package
Throw-away Prototype
Product Backlog
49. 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
Organization
User
Business Process
Vision Statement (product vision statement)
50. 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
Analyst
Requirement(s) Defect
Requirement(s) Attribute