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 problem area undergoing analysis.
Risk
Observation
Data Flow Diagram (DFD)
Domain
2. A set of requirements grouped together in a document or presentation for communication to stakeholders.
Requirements Package
Plan-driven Methodology
Defect
Business Analysis Communication Plan
3. 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)
Project Scope
Event
Optionality
4. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.
Quality Assurance
Product Scope
Validation
Elicitation
5. 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.
Enterprise Architecture
Stated Requirements
Interoperability
Use Case Diagram
6. Limitations on the design of a solution that derive from the technology used in its implementation.
Dialog Hierarchy
Scope
Requirement(s) Attribute
Technical Constraint(s)
7. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
Relationship
Model(s)
Commercial-off-the-Shelf Software (COTS)
Walkthrough
8. The set of capabilities a solution must deliver in order to meet the business need.
Solution Scope
Business Process
Baseline
Scope Model
9. An analysis model that shows user interface dialogs arranged as hierarchies.
Dialog Hierarchy
Request For Proposal (RFP)
Product Scope
Variance Analysis
10. 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
Sequence Diagram
Association
Walkthrough
User Story
11. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.
Impact Analysis
External Interfaces
Quality Assurance
Requirement
12. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.
Enterprise
Focus Group
Root Cause Analysis
Defect
13. 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.
Interview
Requirements Management Tool
Attribute
Metadata
14. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.
Decision Tables
Stakeholder Analysis
Problem Statement
Actor(s)
15. 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.
SWOT Analysis
Enterprise
Focus Group
Lessons Learned Process
16. The product capabilities or things the product must do for its users.
Customer
Enterprise Architecture
Functional Requirement(s)
Business Requirements Document
17. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Stakeholder Analysis
Root Cause Analysis
Unified Modeling Language (UML)
Quality Attributes
18. An analysis model that illustrates product scope by showing the system in its environment with the external entities (people and systems) that give to and receive from the system.
Context Diagram
Exploratory Prototype
Stakeholder Requirement
External Interfaces
19. An analysis model describing the data structures and attributes needed by the system.
Project Charter
Defect
Event
Data Dictionary
20. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.
Business Requirement
Organizational Process Asset
Context Diagram
Risk
21. Software developed and sold for a particular market.
Business Policy
Business Case
Domain Subject Matter Expert (SME)
Commercial-off-the-Shelf Software (COTS)
22. A structured examination of an identified problem to understand the underlying causes.
Root Cause Analysis
Requirement
Request For Information (RFI)
Analyst
23. 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
Organization
Domain Subject Matter Expert (SME)
Relationship
Process Model
24. Ability of systems to communicate by exchanging data or services.
Business Requirements Document
Deliverable
Interoperability
Solution
25. A comparison of a process or system's cost time quality or other metrics to those of leading peer organizations to identify opportunities for improvement.
Event Response Table
Process Map
Solution Scope
Benchmarking
26. 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.
Domain
Requirements Traceability
Evolutionary Prototype
Service
27. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.
Requirements Model
Domain
Requirements Trace Matrix
Product Scope
28. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.
Requirements Management Plan
Vision Statement (product vision statement)
Competitive Analysis
Service
29. 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.
Requirements Management Tool
Constraint
Benchmarking
Work Breakdown Structure (WBS)
30. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.
Requirements Management Tool
Event
Survey
Interview
31. 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.
Work Product
Relationship Map
Feasibility Study
Throw-away Prototype
32. 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
Evaluation
Lessons Learned Process
Secondary Actor
Requirements Trace Matrix
33. A prototype developed to explore or verify requirements.
Exploratory Prototype
Requirements Management Tool
Interview
Requirements Allocation
34. 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.
Span of Control
Business Policy
Force Field Analysis
Iteration
35. Any recognized association of people in the context of an organization or enterprise.
User Acceptance Test
Organizational Unit
Scope
Requirements Signoff
36. 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.
Business Policy
Business Analyst
Process Map
Event Response Table
37. A prototype that is continuously modified and updated in response to feedback from users.
Vision Statement (product vision statement)
Evolutionary Prototype
Scope
Peer Review
38. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.
Repository
Problem Statement
Quality Attributes
Enterprise Architecture
39. 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.
Business Analysis
Business Requirement
Glossary
Transition Requirement(s)
40. The business rules an organization chooses to enforce as a matter of policy. They are intended to guide the actions of people working within the business. They may oblige people to take certain actions prevent people from taking actions or prescribe
Data Model
Operative Rule(s)
Requirements Validation
Observation
41. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.
Actor(s)
Structured Walkthrough
Project
Vision Statement (product vision statement)
42. 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).
Solution Requirement
Change Control Board (CCB)
Decomposition
Cardinality
43. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.
Entity-Relationship Diagram
Cost Benefit Analysis
Attribute
SWOT Analysis
44. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.
Requirements Management
Context Diagram
Association
Supplier
45. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.
User Acceptance Test
Attribute
Project Manager
Opportunity Analysis
46. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.
Organization Modeling
Secondary Actor
Requirements Trace Matrix
Root Cause Analysis
47. 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
Cardinality
Business Process
Requirements Verification
Business Domain Model
48. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.
Problem Statement
Model(s)
Sponsor
Scope
49. A stakeholder who provides products or services to an organization.
Interface
Event
Iteration
Supplier
50. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.
Decision Tree
Object Oriented Modeling
Fishbone Diagram
Horizontal Prototype