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 stakeholder with legal or governance authority over the solution or the process used to develop it.
Data Model
Monitoring
Regulator
Metric
2. 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.
Change Control Board (CCB)
Walkthrough
Business Need(s)
Requirements Workshop
3. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.
Regulator
Customer
Requirements Management Tool
Requirements Model
4. The set of processes templates and activities that will be used to perform business analysis in a specific context.
Business Analyst
Dialog Map
Secondary Actor
Business Analysis Approach
5. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.
Observation
Organization Modeling
Timebox
Customer
6. 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
Business Process
Opportunity Analysis
Scenario
Data Model
7. A classification of requirements that describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to the desired future state but that will not be needed once that transition is complet
Implementation Subject Matter Expert (SME)
Structural Rule
Transition Requirement(s)
Dialog Hierarchy
8. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.
Validation
Risk
Quality Assurance
Business Analysis Approach
9. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.
Requirements Trace Matrix
Business Requirement
Transition Requirement(s)
Solution
10. 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.
Requirement
Fishbone Diagram
Iteration
Plan-driven Methodology
11. 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
Business Analyst
Business Event
Lessons Learned Process
Evolutionary Prototype
12. An approach to software engineering where software is comprised of components that are encapsulated groups of data and functions which can inherit behavior and attributes from other components; and whose components communicate via messages with one a
Commercial-off-the-Shelf Software (COTS)
Object Oriented Modeling
Software/Systems Requirements Specification
Requirements Trace Matrix
13. A practitioner of business analysis.
Tester
Requirements Workshop
Dialog Map
Business Analyst
14. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.
Entity-Relationship Diagram
Organizational Readiness Assessment
Focus Group
Organizational Process Asset
15. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.
Product Backlog
Knowledge Area
Return on Investment
Process Model
16. An analysis model showing the life cycle of a data entity or class.
Verified Requirements
Validated Requirements
Functional Requirement(s)
State Diagram
17. 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.
Exploratory Prototype
Business Analysis Communication Plan
Focus Group
Requirement(s) Defect
18. A temporary endeavor undertaken to create a unique product service or result.
Process Map
Stakeholder List
Requirements Verification
Project
19. 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.
Evolutionary Prototype
Problem Statement
Project Charter
Objective
20. An informal solicitation of proposals from vendors.
Defect
Request For Quote (RFQ)
Requirements Management
State Diagram
21. A system trigger that is initiated by humans.
Validated Requirements
Business Event
Requirements Management
Included Use Cases
22. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.
Data Model
Product
Association
Unified Modeling Language (UML)
23. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.
Verification
End User
Vision Statement (product vision statement)
Association
24. 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
Class
Business Analysis
Business Architecture
Structured Walkthrough
25. The degree to which a set of inherent characteristics fulfills requirements.
Quality
Business Process
Business Analysis Approach
Solution
26. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.
Data Flow Diagram (DFD)
Change Control Board (CCB)
Competitive Analysis
Repository
27. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.
Prototype
Impact Analysis
Data Flow Diagram (DFD)
Sequence Diagram
28. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.
Initiative
Impact Analysis
Product Backlog
Requirements Workshop
29. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).
Vision Statement (product vision statement)
Business Architecture
Requirements Allocation
Process Map
30. Software requirements that limit the options available to the system designer.
Enterprise
Requirements Workshop
Root Cause Analysis
Design Constraints
31. 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.
Scenario
Checklist
Incremental Delivery
Domain
32. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).
Checklist
Requirements Trace Matrix
Business Requirements Document
Indicator
33. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.
Monitoring
Context Diagram
User Acceptance Test
Stated Requirements
34. An activity within requirements development that identifies sources for requirements and then uses elicitation techniques (e.g. interviews prototypes facilitated workshops documentation studies) to gather requirements from those sources.
Verified Requirements
Elicitation
Evaluation
Quality Attributes
35. 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
Exploratory Prototype
Operative Rule(s)
Requirements Allocation
Business Policy
36. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.
Business Analysis Plan
Sponsor
Enterprise Architecture
Force Field Analysis
37. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.
Glossary
Observation
Technical Constraint(s)
Business Analysis Approach
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.
Decision Analysis
Regulator
Stakeholder
Requirements Iteration
39. A stakeholder responsible for assessing the quality of and identifying defects in a software application.
Business Constraint(s)
Business Analyst
Tester
Risk
40. A means to elicit ideas and attitudes about a specific product service or opportunity in an interactive group environment. The participants share their impressions preferences and needs guided by a moderator.
Impact Analysis
Focus Group
Solution Scope
Evolutionary Prototype
41. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.
Cost Benefit Analysis
Focus Group
Requirements Management
Solution
42. 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.
Requirements Management
Domain Subject Matter Expert (SME)
Dialog Map
Inspection
43. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Supplier
Capability
Stakeholder Analysis
Organizational Process Asset
44. The process of examining new business opportunities to improve organizational performance.
Project Manager
Opportunity Analysis
Supplier
Service
45. A shared boundary between any two persons and/or systems through which information is communicated.
Interface
Competitive Analysis
Initiative
Supplier
46. Creating working software in multiple releases so the entire product is delivered in portions over time.
Decision Tree
Baseline
Business Process
Incremental Delivery
47. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.
Feasibility Study
Business Goal
Technique
Subject Matter Expert (SME)
48. 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
Cost Benefit Analysis
Request For Information (RFI)
Business Domain Model
Requirement(s) Defect
49. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.
Requirements Package
Structured Walkthrough
Business Domain Model
Observation
50. A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract standard specification or other formally imposed documents.
Organization Modeling
Structured Walkthrough
Requirement
Temporal Event