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. The set of capabilities a solution must deliver in order to meet the business need.
Data Flow Diagram (DFD)
Solution Scope
Commercial-off-the-Shelf Software (COTS)
Business Constraint(s)
2. A target or metric that a person or organization seeks to meet in order to progress towards a goal.
Business Architecture
Objective
Class Model
Variance Analysis
3. A system of programming statements symbols and rules used to represent instructions to a computer.
Business Rule(s)
Code
Dialog Hierarchy
Stakeholder Analysis
4. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.
Evaluation
Metric
Impact Analysis
Technical Constraint(s)
5. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.
Interoperability
Repository
Requirements Validation
Change Control Board (CCB)
6. 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.
Product
Interview
Verified Requirements
Cardinality
7. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.
State Diagram
Temporal Event
Prototype
SWOT Analysis
8. An analysis model that illustrates the architecture of the system's user interface.
Process Model
Quality Assurance
Dialog Map
Product
9. Influencing factors that are believed to be true but have not been confirmed to be accurate.
Assumption
Capability
Business Analysis Approach
Product Backlog
10. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.
Organizational Process Asset
Indicator
Initiative
Change Control Board (CCB)
11. A shared boundary between any two persons and/or systems through which information is communicated.
Organizational Unit
Entity-Relationship Diagram
Interface
Work Product
12. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.
Observation
Organization
Evaluation
Impact Analysis
13. 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).
Requirements Signoff
Functional Requirement(s)
Cardinality
Decision Tables
14. Something that occurs to which an organizational unit system or process must respond.
Event
Initiative
Project
Technical Constraint(s)
15. 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.
Throw-away Prototype
Capability
Walkthrough
Change-driven Methodology
16. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.
Product
Software/Systems Requirements Specification
Relationship Map
Capability
17. The degree to which a set of inherent characteristics fulfills requirements.
Technique
Quality
Checklist
SWOT Analysis
18. 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.
SWOT Analysis
Requirements Workshop
Requirement(s) Attribute
Regulator
19. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.
Data Entity
Requirements Signoff
Product Backlog
User Story
20. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.
Analyst
Activity Diagram
Relationship
Vision Statement (product vision statement)
21. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.
Peer Review
Monitoring
Metric
Metadata
22. 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.
Horizontal Prototype
Initiative
Structural Rule
Use Case
23. 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.
Throw-away Prototype
Requirements Traceability
Interface
Technique
24. A description of the requirements management process.
Service
Requirements Management Plan
Project Charter
Quality
25. The process of examining new business opportunities to improve organizational performance.
Included Use Cases
Timebox
Requirements Management Tool
Opportunity Analysis
26. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.
Work Breakdown Structure (WBS)
Change Control Board (CCB)
Competitive Analysis
Requirements Model
27. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.
Vision Statement (product vision statement)
Requirements Validation
Requirements Management Tool
Requirement
28. A state or condition the business must satisfy to reach its vision.
Cost Benefit Analysis
Business Goal
Force Field Analysis
Developer
29. A stakeholder who uses products or services delivered by an organization.
Request For Proposal (RFP)
Customer
Lessons Learned Process
Subject Matter Expert (SME)
30. 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.
Force Field Analysis
Walkthrough
User Acceptance Test
Work Product
31. A system trigger that is initiated by humans.
User Story
Business Event
Metric
Model(s)
32. A person with specific expertise in an area or domain under investigation.
Attribute
Cardinality
Structural Rule
Domain Subject Matter Expert (SME)
33. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Stakeholder Analysis
Decision Tree
Validation
Verification
34. 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.
Regulator
Business Need(s)
Work Breakdown Structure (WBS)
Problem Statement
35. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.
Feasibility Study
Business Process
Activity
Technique
36. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.
Data Flow Diagram (DFD)
Solution Requirement
Focus Group
Baseline
37. A fixed period of time to accomplish a desired outcome.
Structural Rule
Business Domain Model
Timebox
Validated Requirements
38. A type of data model that depicts information groups as classes.
Class Model
Business Rule(s)
Change Control Board (CCB)
Defect
39. An error in requirements caused by incorrect incomplete missing or conflicting requirements.
Scope
Requirement(s) Defect
Validated Requirements
Business Need(s)
40. Limitations on the design of a solution that derive from the technology used in its implementation.
Requirements Verification
Included Use Cases
Technical Constraint(s)
Verified Requirements
41. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.
Enterprise Architecture
Focus Group
Requirement(s) Defect
Requirements Management
42. Information that is used to understand the context and validity of information recorded in a system.
Metadata
Regulator
Force Field Analysis
Glossary
43. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.
Enterprise Architecture
Process Model
Exploratory Prototype
Business Analysis
44. 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
Requirements Verification
Scenario
Change-driven Methodology
Business Domain Model
45. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).
Actor(s)
Supplier
Quality Attributes
Repository
46. 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.
Verification
Methodology
Analyst
Request For Quote (RFQ)
47. Metadata related to a requirement used to assist with requirements development and management.
User Requirements Document
Organization
Requirement(s) Attribute
Peer Review
48. 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.
Requirements Validation
Code
Developer
Evaluation
49. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.
Data Entity
Analyst
Stakeholder
Cardinality
50. The number of employees a manger is directly (or indirectly) responsible for.
Inspection
Relationship Map
Capability
Span of Control