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 stakeholder responsible for assessing the quality of and identifying defects in a software application.
Deliverable
Business Analysis Plan
Tester
Methodology
2. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.
Objective
Model(s)
Interface
Document Analysis
3. 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.
Process Model
Implementation Subject Matter Expert (SME)
Vertical Prototype
Business Requirements Document
4. 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).
Evaluation
Cardinality
Event Response Table
Competitive Analysis
5. 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).
Walkthrough
Operational Support
Product
Benchmarking
6. 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.
Feasibility Study
Relationship
Object Oriented Modeling
Business Analysis Communication Plan
7. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.
Business Domain Model
Monitoring
Data Model
Dialog Hierarchy
8. A stakeholder who uses products or services delivered by an organization.
Customer
User
Methodology
Dialog Hierarchy
9. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.
Repository
Use Case
Decomposition
Requirement(s) Defect
10. The degree to which a set of inherent characteristics fulfills requirements.
Requirements Risk Mitigation Strategy
Change-driven Methodology
Objective
Quality
11. 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.
Operative Rule(s)
Focus Group
Scope
Data Entity
12. 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.
Opportunity Analysis
Scope
Requirement
Verification
13. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.
Validated Requirements
Variance Analysis
Requirements Risk Mitigation Strategy
Requirement
14. All materials used by groups within an organization to define tailor implement and maintain their processes.
Organizational Process Asset
Solution Scope
Organization
Root Cause Analysis
15. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.
Enterprise Architecture
Business Need(s)
Desired Outcome
Requirements Allocation
16. A prototype that dives into the details of the interface functionality or both.
Vertical Prototype
Context Diagram
Business Analysis Approach
Requirements Verification
17. 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.
Work Product
Work Breakdown Structure (WBS)
Object Oriented Modeling
Analyst
18. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.
Process Model
Subject Matter Expert (SME)
Metadata
Organization Modeling
19. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.
Repository
Requirements Management
Business Goal
Transition Requirement(s)
20. 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.
Benchmarking
Methodology
Requirements Iteration
Stakeholder Analysis
21. An actor who participates in but does not initiate a use case.
Secondary Actor
Requirements Signoff
Inspection
Requirement
22. A measure of the profitability of a project or investment.
Organization Modeling
Verification
Return on Investment
Project Manager
23. A graphical method for depicting the forces that support and oppose a change. Involves identifying the forces depicting them on opposite sides of a line (supporting and opposing forces) and then estimating the strength of each set of forces.
Force Field Analysis
Decision Tables
Requirements Risk Mitigation Strategy
Constraint
24. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.
Walkthrough
Black Box Tests
Work Breakdown Structure (WBS)
Indicator
25. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.
Product
Requirement(s) Attribute
Inspection
Validated Requirements
26. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.
System
Stakeholder Requirement
Commercial-off-the-Shelf Software (COTS)
Competitive Analysis
27. An error in requirements caused by incorrect incomplete missing or conflicting requirements.
Prototype
Requirement(s) Defect
Stakeholder List
Scope
28. 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
Included Use Cases
Data Dictionary
Event Response Table
Organization
29. Any effort undertaken with a defined goal or objective.
Quality
Initiative
Deliverable
Stakeholder List
30. 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.
Feasibility Study
Methodology
End User
Process Map
31. A type of diagram that shows objects participating in interactions and the messages exchanged between them.
Scenario
Requirements Trace Matrix
Walkthrough
Sequence Diagram
32. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.
Prioritization
Requirements Trace Matrix
Unified Modeling Language (UML)
Developer
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.
Walkthrough
Implementation Subject Matter Expert (SME)
Business Domain Model
Enterprise
34. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.
Product Backlog
Secondary Actor
Walkthrough
Observation
35. The human and nonhuman roles that interact with the system.
Requirements Model
Requirements Management Tool
Actor(s)
Sequence Diagram
36. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.
Interview
Peer Review
Change Control Board (CCB)
Decomposition
37. The process of examining new business opportunities to improve organizational performance.
Data Flow Diagram (DFD)
User
Entity-Relationship Diagram
Opportunity Analysis
38. A temporary endeavor undertaken to create a unique product service or result.
Methodology
Project
Sequence Diagram
Organizational Process Asset
39. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.
Vision Statement (product vision statement)
Evolutionary Prototype
Scenario
Initiative
40. A prototype developed to explore or verify requirements.
Interview
Solution Scope
Exploratory Prototype
Feasibility Study
41. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.
System
Quality Assurance
Requirements Management
Variance Analysis
42. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.
Organization Modeling
Organizational Readiness Assessment
Root Cause Analysis
Brainstorming
43. 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.
Optionality
Relationship Map
Feature
Sequence Diagram
44. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.
Optionality
Validation
Prioritization
Data Entity
45. A structured examination of an identified problem to understand the underlying causes.
Root Cause Analysis
Sequence Diagram
Walkthrough
Secondary Actor
46. 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.
State Diagram
Product
Walkthrough
Optionality
47. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.
Entity-Relationship Diagram
Technical Constraint(s)
Problem Statement
Requirements Signoff
48. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
Model(s)
Technique
Project
Requirements Management Tool
49. The number of employees a manger is directly (or indirectly) responsible for.
Request For Quote (RFQ)
Span of Control
Technical Constraint(s)
Business Goal
50. 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
Requirements Iteration
Lessons Learned Process
Requirements Management Plan
Indicator