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 prototype that shows a shallow and possibly wide view of the system's functionality but which does not generally support any actual use or interaction.
Stakeholder Analysis
Horizontal Prototype
Work Breakdown Structure (WBS)
Requirement
2. 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.
Requirements Signoff
Requirements Workshop
Business Rule(s)
Throw-away Prototype
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
Change Control Board (CCB)
End User
Object Oriented Modeling
Problem Statement
4. 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.
Elicitation
Product Backlog
Request For Information (RFI)
Business Analysis Communication Plan
5. 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.
Knowledge Area
Root Cause Analysis
Activity Diagram
Checklist
6. A temporary endeavor undertaken to create a unique product service or result.
Project
Class Model
Change Control Board (CCB)
Requirements Package
7. A stakeholder who uses products or services delivered by an organization.
Swimlane
Customer
Feature
Fishbone Diagram
8. 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.
Design Constraints
Benchmarking
Requirements Iteration
Prioritization
9. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.
Initiative
System
User Story
Decision Tables
10. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.
Activity Diagram
Business Analyst
Requirements Model
Entity-Relationship Diagram
11. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.
Class
Solution
Requirements Traceability
Business Rule(s)
12. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.
Business Event
Activity
Stakeholder List
Document Analysis
13. An actor who participates in but does not initiate a use case.
Secondary Actor
Observation
Association
Request For Proposal (RFP)
14. 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.
Enterprise
Analyst
Product Backlog
Technique
15. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.
Structured Walkthrough
Requirement(s) Defect
Glossary
Supplier
16. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.
Requirements Workshop
Structural Rule
Organization Modeling
Methodology
17. 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.
Domain
Cost Benefit Analysis
Capability
Incremental Delivery
18. 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
Operative Rule(s)
Analyst
Requirement(s) Defect
Glossary
19. 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
Stakeholder List
Solution Scope
Evaluation
Organization
20. 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.
Request For Quote (RFQ)
Data Dictionary
Verification
Analyst
21. An assessment of the costs and benefits associated with a proposed initiative.
Request For Information (RFI)
Quality Attributes
Brainstorming
Business Case
22. 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.
Focus Group
Scenario
Validated Requirements
Stated Requirements
23. 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
Temporal Event
Business Domain Model
Fishbone Diagram
Use Case Diagram
24. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.
Requirements Model
Implementation Subject Matter Expert (SME)
Business Architecture
Business Requirements Document
25. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.
Change Control Board (CCB)
Request For Information (RFI)
Business Architecture
Interview
26. Something that occurs to which an organizational unit system or process must respond.
User
Event
Business Goal
Root Cause Analysis
27. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.
User
Decomposition
Service
Vision Statement (product vision statement)
28. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.
Requirements Management
Feature
Baseline
Risk
29. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.
Entity-Relationship Diagram
State Diagram
Process Model
Organization Modeling
30. 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
Quality
Requirements Iteration
Requirements Management Plan
Decision Tree
31. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.
Business Analysis Approach
Change-driven Methodology
Business Analysis Plan
Observation
32. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.
Cardinality
Implementation Subject Matter Expert (SME)
Knowledge Area
Solution Requirement
33. Work carried out or on behalf of others.
Implementation Subject Matter Expert (SME)
Optionality
Service
Requirements Iteration
34. 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.
Horizontal Prototype
Elicitation
Project Scope
Business Analysis Communication Plan
35. A shared boundary between any two persons and/or systems through which information is communicated.
Quality
Survey
Interface
Project Scope
36. A stakeholder who will be responsible for designing developing and implementing the change described in the requirements and have specialized knowledge regarding the construction of one or more solution components.
Gap Analysis
Prioritization
Implementation Subject Matter Expert (SME)
Decision Tree
37. A description of the planned activities that the business analyst will execute in order to perform the business analysis work involved in a specific initiative.
Project Scope
Fishbone Diagram
Business Analysis Plan
Use Case
38. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.
Organizational Unit
Benchmarking
External Interfaces
Methodology
39. Ability of systems to communicate by exchanging data or services.
Unified Modeling Language (UML)
Data Flow Diagram (DFD)
Requirements Package
Interoperability
40. A structured examination of an identified problem to understand the underlying causes.
Peer Review
State Diagram
Root Cause Analysis
Use Case
41. 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.
Business Event
Decision Tables
Business Need(s)
Survey
42. A document or collection of notes or diagrams used by the business analyst during the requirements development process.
Work Product
Interoperability
Business Architecture
Project Manager
43. A partial or preliminary version of the system.
Prototype
SWOT Analysis
Monitoring
Subject Matter Expert (SME)
44. A practitioner of business analysis.
Organization Modeling
Project Charter
Prototype
Business Analyst
45. 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
Request For Information (RFI)
Business Event
Requirements Trace Matrix
Lessons Learned Process
46. Requirements that have been shown to demonstrate the characteristics of requirements quality and as such are cohesive complete consistent correct feasible modifiable unambiguous and testable.
Stakeholder List
Requirements Validation
Verified Requirements
Observation
47. Software requirements that limit the options available to the system designer.
Design Constraints
Business Process
Organization Modeling
Business Analysis Communication Plan
48. A set of requirements grouped together in a document or presentation for communication to stakeholders.
Data Model
Verification
Tester
Requirements Package
49. The human and nonhuman roles that interact with the system.
Use Case
Quality
Survey
Actor(s)
50. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.
Functional Requirement(s)
Baseline
Class Model
Data Flow Diagram (DFD)