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. An evaluation of proposed alternatives to determine if they are technically possible within the constraints of the organization and whether they will deliver the desired benefits to the organization.
Feasibility Study
Lessons Learned Process
Data Dictionary
Variance Analysis
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.
Analyst
Unified Modeling Language (UML)
Organizational Process Asset
Operative Rule(s)
3. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.
Feasibility Study
Business Requirement
Scope Model
Black Box Tests
4. 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
Technique
Organizational Process Asset
Span of Control
5. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.
Requirement
Process Model
Domain
Monitoring
6. 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
Business Domain Model
Requirement(s) Attribute
Class Model
Domain Subject Matter Expert (SME)
7. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.
Entity-Relationship Diagram
Developer
Supplier
Stakeholder List
8. Limitations on the design of a solution that derive from the technology used in its implementation.
Technical Constraint(s)
Business Analyst
Plan-driven Methodology
Transition Requirement(s)
9. Analysis done to compare and quantify the financial and non-financial costs of making a change or implementing a solution compared to the benefits gained.
Entity-Relationship Diagram
Cost Benefit Analysis
Evaluation
Span of Control
10. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.
Transition Requirement(s)
Organization Modeling
Request For Quote (RFQ)
Domain
11. An analysis model showing the life cycle of a data entity or class.
State Diagram
Data Flow Diagram (DFD)
Solution Scope
Requirements Iteration
12. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.
Business Case
Peer Review
Opportunity Analysis
Service
13. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
Business Domain Model
Scenario
Constraint
Brainstorming
14. 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.
Domain
Domain Subject Matter Expert (SME)
Walkthrough
Knowledge Area
15. Ability of systems to communicate by exchanging data or services.
Objective
Interoperability
Implementation Subject Matter Expert (SME)
Requirements Traceability
16. Creating working software in multiple releases so the entire product is delivered in portions over time.
Secondary Actor
Model(s)
Incremental Delivery
Validated Requirements
17. A link between two elements or objects in a diagram.
Feasibility Study
Tester
Functional Requirement(s)
Association
18. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.
Decision Tree
Competitive Analysis
Brainstorming
Evolutionary Prototype
19. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).
Stated Requirements
Service
Opportunity Analysis
Quality Attributes
20. A structured examination of an identified problem to understand the underlying causes.
Business Process
Data Flow Diagram (DFD)
Product Backlog
Root Cause Analysis
21. A system trigger that is initiated by time.
Actor(s)
Technique
Requirements Management
Temporal Event
22. A unit of work performed as part of an initiative or process.
Regulator
Organizational Unit
Activity
Business Analysis
23. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.
Requirements Traceability
Observation
Solution Scope
Solution
24. 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.
Project Charter
Interface
Regulator
Organizational Process Asset
25. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.
Product Scope
Structural Rule
Business Analysis Approach
Baseline
26. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.
Attribute
Entity-Relationship Diagram
Requirements Signoff
Fishbone Diagram
27. 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
Organization Modeling
Exploratory Prototype
Requirements Allocation
Business Process
28. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.
Customer
Exploratory Prototype
Data Entity
Operational Support
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.
Capability
Work Breakdown Structure (WBS)
Validation
Sequence Diagram
30. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).
Commercial-off-the-Shelf Software (COTS)
Requirements Allocation
Cardinality
Domain
31. An actor who participates in but does not initiate a use case.
Secondary Actor
Activity Diagram
Included Use Cases
Business Analysis Plan
32. The features and functions that characterize a product service or result.
Focus Group
Product Scope
Scope Model
Use Case
33. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.
Methodology
Requirements Risk Mitigation Strategy
Business Analysis
Unified Modeling Language (UML)
34. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.
Feasibility Study
Vision Statement (product vision statement)
Quality
Optionality
35. The set of processes templates and activities that will be used to perform business analysis in a specific context.
Business Requirements Document
Scope
Black Box Tests
Business Analysis Approach
36. 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.
Knowledge Area
Requirements Allocation
Iteration
Business Constraint(s)
37. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.
Analyst
Impact Analysis
Subject Matter Expert (SME)
Incremental Delivery
38. A system of programming statements symbols and rules used to represent instructions to a computer.
Benchmarking
Code
Decision Tables
Scope
39. 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.
Dialog Hierarchy
Requirement
Evolutionary Prototype
Evaluation
40. A group of related tasks that support a key function of business analysis.
Knowledge Area
Survey
Relationship Map
Event Response Table
41. 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.
Product Backlog
Indicator
Event Response Table
Cardinality
42. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.
Optionality
Solution
Request For Information (RFI)
Gap Analysis
43. 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.
Business Analysis Approach
Solution
Benchmarking
Stakeholder List
44. 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
Interview
Requirements Traceability
Requirements Iteration
Requirements Package
45. The quality attributes design and implementation constraints and external interfaces that the product must have.
Capability
User
Non-functional Requirement(s)
Interview
46. The product capabilities or things the product must do for its users.
Functional Requirement(s)
Business Process
Data Entity
Requirement
47. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.
Business Analysis Plan
Business Goal
Stakeholder List
Swimlane
48. 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.
Throw-away Prototype
Included Use Cases
Activity
Cost Benefit Analysis
49. 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.
Relationship
End User
Requirements Verification
Stated Requirements
50. A set of requirements grouped together in a document or presentation for communication to stakeholders.
Requirements Package
Stakeholder List
Observation
Business Event