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. Information that is used to understand the context and validity of information recorded in a system.
Unified Modeling Language (UML)
Product
Metadata
Constraint
2. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.
Organization Modeling
Requirements Verification
Stakeholder Analysis
Code
3. An analysis model that illustrates the architecture of the system's user interface.
Requirements Risk Mitigation Strategy
Dialog Map
Use Case
Data Dictionary
4. The area covered by a particular activity or topic of interest.
Gap Analysis
Scope
Context Diagram
Vision Statement (product vision statement)
5. A solution or component of a solution that is the result of a project.
Timebox
Quality
Product
Non-functional Requirement(s)
6. 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.
Verified Requirements
Request For Quote (RFQ)
User Requirements Document
Dialog Map
7. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.
Business Analyst
Repository
Survey
Throw-away Prototype
8. A deficiency in a product or service that reduces its quality or varies from a desired attribute state or functionality.
Defect
Stakeholder
Project
Competitive Analysis
9. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.
Project
Prioritization
Change-driven Methodology
Structured Walkthrough
10. The business benefits that will result from meeting the business need and the end state desired by stakeholders.
Document Analysis
Opportunity Analysis
Desired Outcome
Optionality
11. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.
Organizational Readiness Assessment
Quality
User Requirements Document
Project Charter
12. The degree to which a set of inherent characteristics fulfills requirements.
Enterprise
Exploratory Prototype
Requirements Management
Quality
13. 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.
Requirements Verification
Enterprise
Opportunity Analysis
Incremental Delivery
14. Formal approval of a set of requirements by a sponsor or other decision maker.
Requirements Trace Matrix
Requirements Signoff
Functional Requirement(s)
Solution Requirement
15. 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.
Unified Modeling Language (UML)
Defect
Event Response Table
Quality
16. A practitioner of business analysis.
Sequence Diagram
Evolutionary Prototype
Risk
Business Analyst
17. A high-level informal short description of a solution capability that provides value to a stakeholder. Is typically one or two sentences long and provides the minimum information necessary to allow a developer to estimate the work required to impleme
Optionality
Solution Requirement
Class
User Story
18. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.
Product
Document Analysis
User Acceptance Test
Desired Outcome
19. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
Constraint
Requirements Traceability
Analyst
Organization
20. A methodology that focuses on rapid delivery of solution capabilities in an incremental fashion and direct involvement of stakeholders to gather feedback on the solution's performance.
Subject Matter Expert (SME)
Scope
Change-driven Methodology
Sequence Diagram
21. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.
Requirements Traceability
Requirements Validation
Observation
Secondary Actor
22. A link between two elements or objects in a diagram.
Requirements Package
Peer Review
Class Model
Association
23. An analysis model that illustrates product scope by showing the system in its environment with the external entities (people and systems) that give to and receive from the system.
Business Analysis Approach
Survey
Context Diagram
Model(s)
24. 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.
User Story
Checklist
Object Oriented Modeling
Evaluation
25. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.
Feasibility Study
Process Model
Baseline
Enterprise Architecture
26. A group of related tasks that support a key function of business analysis.
Business Constraint(s)
Organization Modeling
Knowledge Area
Non-functional Requirement(s)
27. The quality attributes design and implementation constraints and external interfaces that the product must have.
Requirements Trace Matrix
Requirements Allocation
Interface
Non-functional Requirement(s)
28. A unit of work performed as part of an initiative or process.
Interview
Activity
Use Case Diagram
Stakeholder List
29. 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
Vision Statement (product vision statement)
Object Oriented Modeling
User Story
Horizontal Prototype
30. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.
Requirements Management
Decision Tree
System
Elicitation
31. Interfaces with other systems (hardware software and human) that a proposed system will interact with.
External Interfaces
Elicitation
User
Feasibility Study
32. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
Incremental Delivery
Business Requirements Document
Model(s)
Fishbone Diagram
33. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.
Project Charter
Requirements Trace Matrix
Context Diagram
Project Manager
34. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.
Business Need(s)
Span of Control
Peer Review
Evaluation
35. An evaluation of proposed alternatives to determine if they are technically possible within the constraints of the organization and whether they will deliver the desired benefits to the organization.
Feasibility Study
Requirements Workshop
Requirements Signoff
Process Model
36. 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.
Root Cause Analysis
Transition Requirement(s)
Span of Control
Verification
37. A prototype developed to explore or verify requirements.
Prototype
Project Manager
Commercial-off-the-Shelf Software (COTS)
Exploratory Prototype
38. An informal solicitation of proposals from vendors.
User Story
Request For Quote (RFQ)
Class Model
Business Constraint(s)
39. A description of the requirements management process.
Unified Modeling Language (UML)
Verification
Requirements Management Plan
Brainstorming
40. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.
Fishbone Diagram
Software/Systems Requirements Specification
Class Model
Supplier
41. The features and functions that characterize a product service or result.
Product Scope
Transition Requirement(s)
Business Policy
Metadata
42. A shared boundary between any two persons and/or systems through which information is communicated.
Deliverable
Class Model
Interface
Observation
43. The process of examining new business opportunities to improve organizational performance.
Structural Rule
Opportunity Analysis
Scope Model
Quality Assurance
44. A structured examination of an identified problem to understand the underlying causes.
Optionality
End User
Root Cause Analysis
Work Product
45. Creating working software in multiple releases so the entire product is delivered in portions over time.
Vision Statement (product vision statement)
Incremental Delivery
Non-functional Requirement(s)
User Requirements Document
46. The work that must be performed to deliver a product service or result with the specified features and functions.
Glossary
Interview
Project Scope
Context Diagram
47. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.
Interview
Requirements Package
Project Charter
Requirement
48. A classification of requirements that describe capabilities that the solution must have in order to facilitate transition from the current state of the enterprise to the desired future state but that will not be needed once that transition is complet
Supplier
Data Flow Diagram (DFD)
User Acceptance Test
Transition Requirement(s)
49. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.
Solution Requirement
Business Analysis Communication Plan
Interview
Metadata
50. A stakeholder who uses products or services delivered by an organization.
Object Oriented Modeling
Customer
Solution
Impact Analysis