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. Any recognized association of people in the context of an organization or enterprise.
Organizational Unit
Evolutionary Prototype
Technique
Process Model
2. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.
Business Requirement
Methodology
Data Entity
Business Analysis Approach
3. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.
Dialog Hierarchy
Focus Group
SWOT Analysis
Requirements Management Tool
4. A group or person who has interests that may be affected by an initiative or influence over it.
Force Field Analysis
Temporal Event
Stakeholder
Survey
5. An analysis model that illustrates the architecture of the system's user interface.
Evolutionary Prototype
Dialog Map
Requirements Traceability
Organizational Readiness Assessment
6. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.
Throw-away Prototype
Data Flow Diagram (DFD)
User
Change-driven Methodology
7. A structured examination of an identified problem to understand the underlying causes.
Root Cause Analysis
Business Constraint(s)
Use Case
Technique
8. A business model that shows a business process in terms of the steps and input and output flows across multiple functions organizations or job roles.
Feature
Tester
Requirements Traceability
Process Map
9. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).
Activity Diagram
Quality Attributes
Business Constraint(s)
Requirements Signoff
10. 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.
Span of Control
Requirements Management Tool
Requirement
Transition Requirement(s)
11. 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)
Process Model
Iteration
Vertical Prototype
12. 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.
User
Business Need(s)
Impact Analysis
Root Cause Analysis
13. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.
Software/Systems Requirements Specification
Evolutionary Prototype
Activity Diagram
Defect
14. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.
Variance Analysis
Model(s)
Domain
Inspection
15. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.
Code
Product
Problem Statement
Quality Attributes
16. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Survey
Stakeholder Analysis
Business Analysis Approach
Solution Requirement
17. 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.
Business Analysis Communication Plan
Interface
End User
Commercial-off-the-Shelf Software (COTS)
18. Something that occurs to which an organizational unit system or process must respond.
Sequence Diagram
Event
Stakeholder
Business Rule(s)
19. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.
Fishbone Diagram
Initiative
Data Entity
Association
20. The number of employees a manger is directly (or indirectly) responsible for.
Tester
Developer
Decomposition
Span of Control
21. A type of data model that depicts information groups as classes.
Data Flow Diagram (DFD)
Technique
Class Model
Organizational Process Asset
22. An analysis model describing the data structures and attributes needed by the system.
Vision Statement (product vision statement)
Object Oriented Modeling
Data Dictionary
Technique
23. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.
Peer Review
Class Model
Model(s)
Solution Requirement
24. A systematic approach to elicit information from a person or group of people in an informal or formal setting by asking relevant questions and documenting the responses.
Iteration
Sponsor
Work Product
Interview
25. A temporary endeavor undertaken to create a unique product service or result.
Incremental Delivery
Business Requirements Document
Request For Information (RFI)
Project
26. The work done to evaluate requirements to ensure they are defined correctly and are at an acceptable level of quality. It ensures the requirements are sufficiently defined and structured so that the solution development team can use them in the desig
Decomposition
Requirements Verification
Dialog Hierarchy
Use Case Diagram
27. 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
Organization
Walkthrough
Change Control Board (CCB)
Data Flow Diagram (DFD)
28. The process of checking a product to ensure that it satisfies its intended use and conforms to its requirements. Ensures that you built the correct solution.
Class Model
Dialog Map
Validation
End User
29. Any effort undertaken with a defined goal or objective.
Monitoring
Requirement
Return on Investment
Initiative
30. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.
Regulator
Requirement(s) Attribute
SWOT Analysis
System
31. An informal solicitation of proposals from vendors.
Vertical Prototype
Business Analysis Communication Plan
Constraint
Request For Quote (RFQ)
32. The area covered by a particular activity or topic of interest.
Plan-driven Methodology
Scope
System
Risk
33. The number of occurrences of one entity in a data model that are linked to a second entity. Is shown on a data model with a special notation number (e.g. 1) or letter (e.g. M for many).
Requirement(s) Defect
Cardinality
Temporal Event
Checklist
34. The degree to which a set of inherent characteristics fulfills requirements.
Data Flow Diagram (DFD)
Stakeholder Requirement
Quality
Requirements Trace Matrix
35. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.
Problem Statement
Requirements Risk Mitigation Strategy
Requirements Validation
Code
36. 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.
Scope Model
Tester
Stated Requirements
Cost Benefit Analysis
37. A non-actionable directive that supports a business goal.
Requirements Workshop
Gap Analysis
Throw-away Prototype
Business Policy
38. An analysis model that describes the tasks that the system will perform for actors and the goals that the system achieves for those actors along the way.
Requirements Risk Mitigation Strategy
Stated Requirements
Use Case
Knowledge Area
39. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.
Analyst
Software/Systems Requirements Specification
Dialog Map
Initiative
40. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.
Constraint
User Acceptance Test
Implementation Subject Matter Expert (SME)
Document Analysis
41. 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.
User Acceptance Test
Change Control Board (CCB)
Activity
Capability
42. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.
Work Breakdown Structure (WBS)
Code
Scenario
Process Model
43. The set of tasks and techniques used to work as a liaison among stakeholders in order to understand the structure policies and operations of an organization and recommend solutions that enable the organization to achieve its goals.
Validation
Business Analysis
Data Dictionary
Requirement(s) Attribute
44. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.
Business Requirement
Walkthrough
Project Scope
Cardinality
45. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.
Exploratory Prototype
Project Manager
Throw-away Prototype
Event
46. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
Interface
Activity Diagram
Glossary
Model(s)
47. 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.
Requirements Verification
Benchmarking
Elicitation
Vision Statement (product vision statement)
48. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.
State Diagram
Glossary
Requirement
Dialog Hierarchy
49. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.
Model(s)
Optionality
Unified Modeling Language (UML)
Process Model
50. A shared boundary between any two persons and/or systems through which information is communicated.
Exploratory Prototype
Interface
Capability
Focus Group