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 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.
Non-functional Requirement(s)
Sponsor
Verification
Use Case
2. The process of examining new business opportunities to improve organizational performance.
Opportunity Analysis
Force Field Analysis
State Diagram
Project Scope
3. A prototype that is continuously modified and updated in response to feedback from users.
Data Entity
Evolutionary Prototype
End User
Event
4. A data element with a specified data type that describes information associated with a concept or entity.
Attribute
Requirements Allocation
Enterprise
SWOT Analysis
5. Work carried out or on behalf of others.
Sponsor
Business Requirement
Walkthrough
Service
6. 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.
Quality
Feasibility Study
Process Map
Peer Review
7. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.
Decomposition
Class
Enterprise Architecture
Design Constraints
8. A stakeholder person device or system that directly or indirectly accesses a system.
Iteration
User
Operational Support
Stated Requirements
9. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.
Data Model
Stakeholder Requirement
Evaluation
Cardinality
10. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Stakeholder Analysis
Checklist
Prototype
Decision Tables
11. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.
Business Event
Project Scope
Data Model
Repository
12. A system trigger that is initiated by time.
Temporal Event
Force Field Analysis
Organization
Change-driven Methodology
13. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.
Black Box Tests
Requirements Traceability
Data Flow Diagram (DFD)
Competitive Analysis
14. A structured examination of an identified problem to understand the underlying causes.
Vision Statement (product vision statement)
Root Cause Analysis
Request For Quote (RFQ)
Requirement
15. 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.
Request For Proposal (RFP)
Cardinality
Decision Analysis
Organizational Unit
16. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.
Brainstorming
Business Analysis Plan
Use Case Diagram
Business Case
17. The problem area undergoing analysis.
Objective
Tester
Context Diagram
Domain
18. A model that defines the boundaries of a business domain or solution.
Scope Model
Subject Matter Expert (SME)
Deliverable
Monitoring
19. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.
Context Diagram
Interview
User Acceptance Test
Relationship Map
20. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.
Prioritization
Requirements Trace Matrix
Data Entity
Lessons Learned Process
21. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.
Horizontal Prototype
Document Analysis
Use Case Diagram
Business Case
22. 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.
Requirements Model
Optionality
Monitoring
Plan-driven Methodology
23. The area covered by a particular activity or topic of interest.
Regulator
Model(s)
Requirements Management
Scope
24. 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
Observation
Business Analysis Communication Plan
Requirements Iteration
Stakeholder
25. An informal solicitation of proposals from vendors.
Dialog Map
Stakeholder Analysis
Request For Quote (RFQ)
Product Scope
26. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.
Evaluation
Prioritization
Product
Decision Analysis
27. Formal approval of a set of requirements by a sponsor or other decision maker.
Requirements Verification
Requirements Signoff
Change Control Board (CCB)
Solution
28. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.
User Acceptance Test
Implementation Subject Matter Expert (SME)
Secondary Actor
Unified Modeling Language (UML)
29. A stakeholder responsible for assessing the quality of and identifying defects in a software application.
Brainstorming
Opportunity Analysis
Objective
Tester
30. 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.
Secondary Actor
Business Analysis Communication Plan
Stakeholder
Service
31. Something that occurs to which an organizational unit system or process must respond.
Unified Modeling Language (UML)
Requirement(s) Defect
Monitoring
Event
32. 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
Object Oriented Modeling
Requirements Allocation
Business Case
Structured Walkthrough
33. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.
Structured Walkthrough
Change-driven Methodology
Operative Rule(s)
Activity
34. A type of diagram that shows objects participating in interactions and the messages exchanged between them.
Business Analysis Communication Plan
Verified Requirements
Sequence Diagram
Unified Modeling Language (UML)
35. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.
Requirements Management Plan
Fishbone Diagram
Service
Observation
36. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.
Developer
Business Requirement
Code
Decomposition
37. A prototype that dives into the details of the interface functionality or both.
End User
Requirements Validation
Functional Requirement(s)
Vertical Prototype
38. A shared boundary between any two persons and/or systems through which information is communicated.
Solution
User Requirements Document
Horizontal Prototype
Interface
39. 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.
Cost Benefit Analysis
Product Scope
Requirements Traceability
Enterprise
40. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.
Stakeholder Analysis
Feasibility Study
Operational Support
Impact Analysis
41. A stakeholder who provides products or services to an organization.
Validation
Quality Attributes
Initiative
Supplier
42. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.
Throw-away Prototype
Request For Proposal (RFP)
Validated Requirements
Business Domain Model
43. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.
Verified Requirements
Methodology
Attribute
Walkthrough
44. The degree to which a set of inherent characteristics fulfills requirements.
Verified Requirements
Quality
Impact Analysis
Event
45. The quality attributes design and implementation constraints and external interfaces that the product must have.
Non-functional Requirement(s)
Enterprise Architecture
Change Control Board (CCB)
Class Model
46. A target or metric that a person or organization seeks to meet in order to progress towards a goal.
End User
User Story
Software/Systems Requirements Specification
Objective
47. 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.
User Requirements Document
Requirements Package
Business Domain Model
Decision Tables
48. An analysis model that illustrates the architecture of the system's user interface.
Object Oriented Modeling
Dialog Map
Supplier
Work Breakdown Structure (WBS)
49. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.
Stated Requirements
Non-functional Requirement(s)
Opportunity Analysis
Sponsor
50. Any effort undertaken with a defined goal or objective.
Code
Business Analysis Approach
Span of Control
Initiative