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.
Regulator
Span of Control
Unified Modeling Language (UML)
Focus Group
2. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.
Scenario
Interface
Enterprise Architecture
Dialog Hierarchy
3. 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
Organizational Process Asset
Object Oriented Modeling
Functional Requirement(s)
Class Model
4. 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.
Requirement(s) Defect
Organizational Process Asset
Stated Requirements
Requirements Workshop
5. A process in which a deliverable (or the solution overall) is progressively elaborated upon. Will result in a self-contained "mini-project" in which a set of activities are undertaken resulting in the development of a subset of project deliverables.
Event
Domain
Iteration
Organization
6. A temporary endeavor undertaken to create a unique product service or result.
Constraint
Project
User Acceptance Test
Peer Review
7. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.
Object Oriented Modeling
Interface
Evaluation
Swimlane
8. A structured examination of an identified problem to understand the underlying causes.
Root Cause Analysis
Exploratory Prototype
Throw-away Prototype
Data Entity
9. A practitioner of business analysis.
Competitive Analysis
Event Response Table
Objective
Business Analyst
10. 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
Requirements Package
Request For Information (RFI)
Baseline
Organization
11. A group or person who has interests that may be affected by an initiative or influence over it.
Tester
Stakeholder
Functional Requirement(s)
Included Use Cases
12. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.
Decision Tree
Black Box Tests
Interview
Baseline
13. The quality attributes design and implementation constraints and external interfaces that the product must have.
Benchmarking
Constraint
Swimlane
Non-functional Requirement(s)
14. Any unique and verifiable work product or service that a party has agreed to deliver.
Deliverable
Organizational Readiness Assessment
Business Analysis Approach
Validation
15. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.
Organization Modeling
Swimlane
Opportunity Analysis
Change-driven Methodology
16. 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.
Plan-driven Methodology
Enterprise
Quality Attributes
Solution
17. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.
Baseline
Business Analyst
SWOT Analysis
Service
18. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.
User
Solution
Business Event
Problem Statement
19. The product capabilities or things the product must do for its users.
Project
Functional Requirement(s)
Quality Assurance
End User
20. Software developed and sold for a particular market.
Actor(s)
Commercial-off-the-Shelf Software (COTS)
Business Analyst
Elicitation
21. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.
Solution Scope
Stakeholder Analysis
Brainstorming
Exploratory Prototype
22. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.
Prototype
Stated Requirements
Timebox
Requirements Trace Matrix
23. Work carried out or on behalf of others.
Impact Analysis
Swimlane
Developer
Service
24. 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.
Monitoring
Interface
Elicitation
Opportunity Analysis
25. 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.
Monitoring
Business Need(s)
Enterprise
Product Scope
26. A unit of work performed as part of an initiative or process.
Risk
Requirements Management Plan
Activity
Cost Benefit Analysis
27. 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
Verification
Return on Investment
Requirements Iteration
28. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).
Black Box Tests
Business Requirements Document
Risk
Sequence Diagram
29. A stakeholder who provides products or services to an organization.
Feasibility Study
Supplier
Requirement(s) Attribute
Problem Statement
30. A stakeholder person device or system that directly or indirectly accesses a system.
Solution Scope
Risk
Requirements Signoff
User
31. 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
Force Field Analysis
Impact Analysis
Technical Constraint(s)
Business Architecture
32. 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.
Dialog Map
Project Charter
Relationship Map
Business Analysis Approach
33. Creating working software in multiple releases so the entire product is delivered in portions over time.
Stakeholder Analysis
Incremental Delivery
Benchmarking
Desired Outcome
34. 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
Requirements Allocation
Interview
Project Scope
35. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.
Metric
State Diagram
Vertical Prototype
Business Event
36. An analysis model that specifies complex business rules or logic concisely in an easy-to-read tabular format specifying all of the possible conditions and actions that need to be accounted for in business rules.
Decision Tables
Interface
Walkthrough
Evaluation
37. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.
Software/Systems Requirements Specification
Exploratory Prototype
Document Analysis
Requirements Allocation
38. 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
Operational Support
Quality Attributes
Organization
Project
39. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.
Requirements Traceability
System
Entity-Relationship Diagram
Quality Assurance
40. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.
Assumption
Return on Investment
Project Manager
Enterprise Architecture
41. 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
Relationship Map
Stakeholder Requirement
Stakeholder
42. An informal solicitation of proposals from vendors.
Document Analysis
Span of Control
Request For Quote (RFQ)
Business Analysis Communication Plan
43. 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.
Requirement
User
Decision Tree
User Acceptance Test
44. The number of employees a manger is directly (or indirectly) responsible for.
Span of Control
Inspection
Feasibility Study
Enterprise
45. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.
Document Analysis
Business Analysis Approach
Organizational Readiness Assessment
Risk
46. Any effort undertaken with a defined goal or objective.
Relationship
Initiative
Methodology
Project Manager
47. The process of examining new business opportunities to improve organizational performance.
Business Case
Constraint
Black Box Tests
Opportunity Analysis
48. The work that must be performed to deliver a product service or result with the specified features and functions.
Business Analysis Approach
Capability
Project Scope
Association
49. A prototype that is continuously modified and updated in response to feedback from users.
Domain Subject Matter Expert (SME)
Evolutionary Prototype
Timebox
Non-functional Requirement(s)
50. An actor who participates in but does not initiate a use case.
Business Goal
Timebox
User
Secondary Actor