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 structured examination of an identified problem to understand the underlying causes.
Elicitation
Cost Benefit Analysis
Root Cause Analysis
Fishbone Diagram
2. 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
Glossary
Sponsor
State Diagram
3. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.
Evolutionary Prototype
Activity
Business Requirement
Product
4. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.
Requirements Risk Mitigation Strategy
Evolutionary Prototype
Requirement(s) Attribute
Survey
5. A cohesive bundle of externally visible functionality that should align with business goals and objectives. Each is a logically related grouping of functional requirements or non-functional requirements described in broad strokes.
Data Entity
Walkthrough
Feature
Data Dictionary
6. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.
Product
System
Decision Tables
Data Model
7. 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.
Observation
Relationship
Document Analysis
Iteration
8. Metadata related to a requirement used to assist with requirements development and management.
Code
Verified Requirements
Cost Benefit Analysis
Requirement(s) Attribute
9. A solution or component of a solution that is the result of a project.
Service
Product
Business Constraint(s)
Interoperability
10. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.
Product
Variance Analysis
Interoperability
Analyst
11. The business benefits that will result from meeting the business need and the end state desired by stakeholders.
Desired Outcome
Optionality
Throw-away Prototype
Unified Modeling Language (UML)
12. 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.
Cardinality
Event Response Table
Subject Matter Expert (SME)
Prioritization
13. A group or person who has interests that may be affected by an initiative or influence over it.
Evaluation
Domain
Stakeholder
Included Use Cases
14. 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.
Business Need(s)
Verification
Organizational Readiness Assessment
Data Flow Diagram (DFD)
15. Limitations placed on the solution design by the organization that needs the solution. Describe limitations on available solutions or an aspect of the current state that cannot be changed by the deployment of the new solution. See also technical cons
Vision Statement (product vision statement)
Non-functional Requirement(s)
Business Constraint(s)
Technical Constraint(s)
16. A shared boundary between any two persons and/or systems through which information is communicated.
Organizational Readiness Assessment
Organization
Interface
Return on Investment
17. Any unique and verifiable work product or service that a party has agreed to deliver.
Stated Requirements
Relationship Map
Glossary
Deliverable
18. A system trigger that is initiated by humans.
Validated Requirements
Business Event
Regulator
Plan-driven Methodology
19. 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.
Objective
Enterprise Architecture
Checklist
Project Manager
20. Software developed and sold for a particular market.
Feature
Supplier
Cost Benefit Analysis
Commercial-off-the-Shelf Software (COTS)
21. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.
Methodology
Subject Matter Expert (SME)
Evolutionary Prototype
Product Scope
22. 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.
Business Policy
Code
Benchmarking
Implementation Subject Matter Expert (SME)
23. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.
Data Flow Diagram (DFD)
System
Project Manager
Relationship Map
24. A description of the requirements management process.
Organizational Readiness Assessment
Requirements Management Plan
Organization Modeling
Solution
25. 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 Package
Business Event
Requirements Model
Assumption
26. Work carried out or on behalf of others.
Software/Systems Requirements Specification
Quality
Service
Business Process
27. Information that is used to understand the context and validity of information recorded in a system.
Metadata
Requirements Signoff
Operative Rule(s)
Scope
28. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.
Scenario
Requirements Validation
Event
Business Analysis
29. 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.
Relationship Map
Domain Subject Matter Expert (SME)
Enterprise Architecture
Stated Requirements
30. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.
Repository
Vision Statement (product vision statement)
Competitive Analysis
External Interfaces
31. 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.
Use Case
Problem Statement
Data Flow Diagram (DFD)
Methodology
32. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.
Assumption
Project Charter
Requirements Trace Matrix
Relationship Map
33. 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
Enterprise Architecture
Evolutionary Prototype
Change Control Board (CCB)
34. A non-actionable directive that supports a business goal.
Class
Event
Use Case
Business Policy
35. A practitioner of business analysis.
Event Response Table
Business Constraint(s)
Business Analyst
Decision Tree
36. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.
Technique
Entity-Relationship Diagram
Scenario
Return on Investment
37. A stakeholder who helps to keep the solution functioning either by providing support to end users (trainers help desk) or by keeping the solution operational on a day-to-day basis (network and other tech support).
Competitive Analysis
Operational Support
Benchmarking
Organizational Unit
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.
User Acceptance Test
System
Requirements Trace Matrix
Methodology
39. A person with specific expertise in an area or domain under investigation.
Attribute
Business Analyst
Domain Subject Matter Expert (SME)
Association
40. A prototype developed to explore or verify requirements.
Exploratory Prototype
Solution
Validated Requirements
Domain Subject Matter Expert (SME)
41. A system of programming statements symbols and rules used to represent instructions to a computer.
Span of Control
Regulator
Code
Analyst
42. The degree to which a set of inherent characteristics fulfills requirements.
Problem Statement
Quality
Objective
Solution Requirement
43. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
Objective
Focus Group
Model(s)
Enterprise
44. A function of an organization that enables it to achieve a business goal or objective.
Operational Support
Capability
Stakeholder
Domain Subject Matter Expert (SME)
45. 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.
Interface
Force Field Analysis
Requirements Risk Mitigation Strategy
Verified Requirements
46. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.
Incremental Delivery
Use Case
Decomposition
Feature
47. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.
Business Analysis Communication Plan
Software/Systems Requirements Specification
Impact Analysis
Change Control Board (CCB)
48. Limitations on the design of a solution that derive from the technology used in its implementation.
Throw-away Prototype
Developer
Data Model
Technical Constraint(s)
49. A means to elicit ideas and attitudes about a specific product service or opportunity in an interactive group environment. The participants share their impressions preferences and needs guided by a moderator.
Business Case
State Diagram
Constraint
Focus Group
50. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.
Business Domain Model
Fishbone Diagram
Evaluation
Risk