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 examining new business opportunities to improve organizational performance.
Stated Requirements
Business Analyst
Evolutionary Prototype
Opportunity Analysis
2. A use case composed of a common set of steps used by multiple use cases.
Business Analysis
Developer
Validation
Included Use Cases
3. A stakeholder with legal or governance authority over the solution or the process used to develop it.
Developer
Regulator
Implementation Subject Matter Expert (SME)
Entity-Relationship Diagram
4. The features and functions that characterize a product service or result.
Product Scope
Business Analyst
Lessons Learned Process
Scope
5. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.
Use Case
Product
Structural Rule
Use Case Diagram
6. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.
Requirements Trace Matrix
Verified Requirements
Decision Analysis
Variance Analysis
7. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.
Deliverable
Scenario
Use Case Diagram
Stakeholder Analysis
8. A model that illustrates the flow of processes and/or complex use cases by showing each activity along with information flows and concurrent activities. Steps can be superimposed onto horizontal swimlanes for the roles that perform the steps.
Non-functional Requirement(s)
Validation
Activity Diagram
Secondary Actor
9. 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).
Cardinality
Service
Regulator
Decision Tables
10. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.
Prototype
Temporal Event
Quality Assurance
Deliverable
11. 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
Commercial-off-the-Shelf Software (COTS)
Attribute
Organization
Scenario
12. The business benefits that will result from meeting the business need and the end state desired by stakeholders.
Data Flow Diagram (DFD)
Business Process
Desired Outcome
Secondary Actor
13. An actor who participates in but does not initiate a use case.
Class
Secondary Actor
Organization Modeling
Requirements Allocation
14. An informal solicitation of proposals from vendors.
Business Constraint(s)
Variance Analysis
Requirements Management Plan
Request For Quote (RFQ)
15. The area covered by a particular activity or topic of interest.
Horizontal Prototype
Scope
Unified Modeling Language (UML)
Benchmarking
16. Metadata related to a requirement used to assist with requirements development and management.
Root Cause Analysis
Requirement(s) Attribute
Project Charter
Methodology
17. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.
Secondary Actor
Knowledge Area
Swimlane
Stakeholder List
18. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.
Business Analysis
Included Use Cases
Relationship
Code
19. A target or metric that a person or organization seeks to meet in order to progress towards a goal.
Transition Requirement(s)
Requirements Verification
Scope Model
Objective
20. A stakeholder who uses products or services delivered by an organization.
Customer
Requirement
Requirements Management
Operational Support
21. Any recognized association of people in the context of an organization or enterprise.
Use Case Diagram
Quality
Organizational Unit
Solution
22. A stakeholder responsible for assessing the quality of and identifying defects in a software application.
Tester
Data Entity
Requirement(s) Attribute
Requirements Management Tool
23. A type of diagram that shows objects participating in interactions and the messages exchanged between them.
Organization Modeling
Sequence Diagram
Business Process
Included Use Cases
24. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.
Requirements Verification
Horizontal Prototype
Solution
Requirements Traceability
25. 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.
Sequence Diagram
Organization
Capability
Event Response Table
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.
Requirements Management Tool
Association
Prioritization
Plan-driven Methodology
27. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.
Included Use Cases
Swimlane
Product Scope
Structured Walkthrough
28. Software requirements that limit the options available to the system designer.
Design Constraints
Activity Diagram
Work Product
Project Scope
29. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.
Software/Systems Requirements Specification
Project Scope
Unified Modeling Language (UML)
Competitive Analysis
30. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.
Operational Support
Cardinality
Gap Analysis
Product Scope
31. The systematic and objective assessment of a solution to determine its status and efficacy in meeting objectives over time and to identify ways to improve the solution to better meet objectives. See also metric indicator and monitoring.
Operative Rule(s)
Developer
Horizontal Prototype
Evaluation
32. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Business Analysis Communication Plan
Walkthrough
Stakeholder Analysis
Actor(s)
33. A set of requirements grouped together in a document or presentation for communication to stakeholders.
Requirements Package
Requirements Trace Matrix
Non-functional Requirement(s)
Business Requirements Document
34. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.
Brainstorming
Model(s)
Requirements Iteration
Entity-Relationship Diagram
35. 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.
Organization Modeling
Business Need(s)
Benchmarking
Structural Rule
36. An error in requirements caused by incorrect incomplete missing or conflicting requirements.
Requirement(s) Defect
Validation
Monitoring
Root Cause Analysis
37. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.
Data Flow Diagram (DFD)
Feature
Stakeholder List
Requirements Model
38. Something that occurs to which an organizational unit system or process must respond.
Stakeholder Analysis
Event
Developer
Business Architecture
39. A stakeholder person device or system that directly or indirectly accesses a system.
Requirements Iteration
Business Rule(s)
Organization
User
40. A partial or preliminary version of the system.
Competitive Analysis
State Diagram
Quality
Prototype
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.
Brainstorming
Requirements Package
Survey
User Acceptance Test
42. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.
Product
Stated Requirements
Process Model
Project
43. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
Brainstorming
Model(s)
Requirements Model
Association
44. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.
External Interfaces
Entity-Relationship Diagram
Requirements Signoff
Stakeholder Analysis
45. The problem area undergoing analysis.
Stakeholder Analysis
Operational Support
Event
Domain
46. The degree to which a set of inherent characteristics fulfills requirements.
Quality
Checklist
Defect
Horizontal Prototype
47. Any unique and verifiable work product or service that a party has agreed to deliver.
Elicitation
Gap Analysis
Deliverable
Stated Requirements
48. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.
Methodology
System
Monitoring
Fishbone Diagram
49. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.
Technique
Model(s)
Organization
Problem Statement
50. 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.
Business Analysis
Requirements Iteration
Indicator
Iteration