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 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 Requirements Document
Process Map
Commercial-off-the-Shelf Software (COTS)
Stakeholder Requirement
2. 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.
Scope
Decision Analysis
Analyst
Activity
3. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.
Business Architecture
Business Requirement
Black Box Tests
Business Policy
4. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.
Requirements Validation
Business Architecture
Validated Requirements
Event Response Table
5. 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
Use Case
Cost Benefit Analysis
Stakeholder
6. A document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.
Business Policy
Data Model
Project Charter
Business Analyst
7. Interfaces with other systems (hardware software and human) that a proposed system will interact with.
External Interfaces
Requirements Workshop
Commercial-off-the-Shelf Software (COTS)
Organization Modeling
8. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.
Business Constraint(s)
Organization Modeling
Optionality
Methodology
9. 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.
Decomposition
Sequence Diagram
Process Model
End User
10. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.
Business Policy
SWOT Analysis
End User
Swimlane
11. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.
Domain Subject Matter Expert (SME)
Supplier
Optionality
Data Entity
12. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.
Non-functional Requirement(s)
Repository
Plan-driven Methodology
Swimlane
13. An organizational unit organization or collection of organizations that share a set of common goals and collaborate to provide specific products or services to customers.
Enterprise
Tester
Sequence Diagram
Horizontal Prototype
14. Influencing factors that are believed to be true but have not been confirmed to be accurate.
Business Analysis Approach
Business Constraint(s)
Business Requirements Document
Assumption
15. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.
Benchmarking
Regulator
Data Flow Diagram (DFD)
Knowledge Area
16. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.
Business Requirements Document
Project Manager
Developer
Entity-Relationship Diagram
17. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.
Organization Modeling
Verification
Dialog Hierarchy
Business Policy
18. A high-level informal short description of a solution capability that provides value to a stakeholder. Is typically one or two sentences long and provides the minimum information necessary to allow a developer to estimate the work required to impleme
Structured Walkthrough
Organizational Unit
User Story
Request For Quote (RFQ)
19. 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
Root Cause Analysis
Requirements Validation
Interface
Lessons Learned Process
20. A prototype that dives into the details of the interface functionality or both.
Organizational Process Asset
Vertical Prototype
Business Analysis Approach
Defect
21. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Risk
Event
Dialog Hierarchy
Stakeholder Analysis
22. 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.
Optionality
Object Oriented Modeling
User Acceptance Test
Requirement
23. 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.
Functional Requirement(s)
Requirements Model
Business Need(s)
Solution
24. Requirements that have been shown to demonstrate the characteristics of requirements quality and as such are cohesive complete consistent correct feasible modifiable unambiguous and testable.
Tester
Verified Requirements
Gap Analysis
Metric
25. 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
Validated Requirements
Activity
Request For Proposal (RFP)
Decomposition
26. An informal solicitation of proposals from vendors.
User
Request For Quote (RFQ)
Structural Rule
Requirement(s) Defect
27. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
Product Backlog
Activity Diagram
Secondary Actor
Model(s)
28. A prototype developed to explore or verify requirements.
Request For Proposal (RFP)
Business Case
Indicator
Exploratory Prototype
29. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.
Change-driven Methodology
Functional Requirement(s)
Exploratory Prototype
Brainstorming
30. Any methodology that emphasizes planning and formal documentation of the processes used to accomplish a project and of the results of the project. Emphasize the reduction of risk and control over outcomes over the rapid delivery of a solution.
Plan-driven Methodology
Change-driven Methodology
Indicator
Metadata
31. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.
Vision Statement (product vision statement)
Model(s)
Project Manager
Initiative
32. 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).
Context Diagram
Cost Benefit Analysis
Requirements Workshop
Cardinality
33. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.
Requirements Risk Mitigation Strategy
Actor(s)
Service
Product Backlog
34. Limitations on the design of a solution that derive from the technology used in its implementation.
Technical Constraint(s)
Survey
Requirements Management Tool
Throw-away Prototype
35. A model that defines the boundaries of a business domain or solution.
Glossary
Business Domain Model
Requirements Management Plan
Scope Model
36. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.
Stakeholder Analysis
Initiative
Requirements Validation
Scope Model
37. An error in requirements caused by incorrect incomplete missing or conflicting requirements.
Requirements Trace Matrix
Methodology
Requirement(s) Defect
Project
38. 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.
Gap Analysis
Decision Analysis
Requirements Trace Matrix
Requirements Verification
39. The features and functions that characterize a product service or result.
Software/Systems Requirements Specification
Product Scope
Scope
Glossary
40. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.
Data Entity
Verification
Requirements Management Tool
Requirements Trace Matrix
41. The process of checking that a deliverable produced at a given stage of development satisfies the conditions or specifications of the previous stage. Ensures that you built the solution correctly.
Business Domain Model
Verification
Lessons Learned Process
Context Diagram
42. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.
Requirements Workshop
Process Model
Quality
Dialog Map
43. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.
Change Control Board (CCB)
Requirements Signoff
Quality
Impact Analysis
44. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.
Tester
Problem Statement
Vertical Prototype
Structural Rule
45. The set of capabilities a solution must deliver in order to meet the business need.
Solution Scope
Benchmarking
Organizational Readiness Assessment
Checklist
46. 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
Solution Requirement
Tester
Metric
Requirements Verification
47. 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
Requirement(s) Attribute
Requirements Iteration
Domain
Work Product
48. Work carried out or on behalf of others.
Quality Attributes
State Diagram
Design Constraints
Service
49. 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.
Enterprise Architecture
Evaluation
Document Analysis
Sponsor
50. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.
Request For Quote (RFQ)
Product Backlog
Problem Statement
Software/Systems Requirements Specification