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 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.
User Acceptance Test
Baseline
Repository
Change-driven Methodology
2. A team activity that seeks to produce a broad or diverse set of options through the rapid and uncritical generation of ideas.
Business Architecture
Product
Force Field Analysis
Brainstorming
3. A deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. It organizes and defines the total scope of the project.
Interoperability
Vision Statement (product vision statement)
Association
Work Breakdown Structure (WBS)
4. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.
Design Constraints
Metric
Product Backlog
Walkthrough
5. 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.
Requirement
Structured Walkthrough
Design Constraints
Monitoring
6. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.
Structural Rule
Assumption
Service
Validation
7. 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).
Design Constraints
Developer
Operational Support
Requirements Management Plan
8. A type of diagram that shows objects participating in interactions and the messages exchanged between them.
Included Use Cases
Project Charter
Evolutionary Prototype
Sequence Diagram
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.
Software/Systems Requirements Specification
Stakeholder
Prioritization
Black Box Tests
10. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.
Organization
Scenario
Repository
Lessons Learned Process
11. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.
Verified Requirements
Swimlane
Business Analyst
Object Oriented Modeling
12. 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.
Iteration
Technique
Solution
Cost Benefit Analysis
13. A prototype developed to explore or verify requirements.
Objective
Exploratory Prototype
Structured Walkthrough
Project Charter
14. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.
Request For Proposal (RFP)
Sponsor
Plan-driven Methodology
Impact Analysis
15. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.
Monitoring
Black Box Tests
Product
User Acceptance Test
16. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.
Sponsor
Fishbone Diagram
Enterprise Architecture
Validation
17. A system trigger that is initiated by humans.
Business Event
Return on Investment
Business Case
Customer
18. A type of data model that depicts information groups as classes.
Scope
Supplier
Class Model
Software/Systems Requirements Specification
19. Interfaces with other systems (hardware software and human) that a proposed system will interact with.
Business Analysis Approach
Plan-driven Methodology
External Interfaces
Impact Analysis
20. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.
Baseline
User Requirements Document
Change Control Board (CCB)
Requirements Validation
21. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.
Impact Analysis
Code
Dialog Hierarchy
Transition Requirement(s)
22. 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.
Data Dictionary
Requirements Model
Enterprise
Data Entity
23. 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.
Brainstorming
Initiative
Developer
Stated Requirements
24. Information that is used to understand the context and validity of information recorded in a system.
Metadata
Solution Scope
Dialog Map
Metric
25. An analysis model describing the data structures and attributes needed by the system.
Entity-Relationship Diagram
Cardinality
Sequence Diagram
Data Dictionary
26. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.
Product
System
Technique
Checklist
27. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.
Dialog Map
Project Manager
Requirements Workshop
Throw-away Prototype
28. 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.
Requirements Management Plan
Iteration
Solution
Cardinality
29. Formal approval of a set of requirements by a sponsor or other decision maker.
Gap Analysis
Stated Requirements
Requirements Signoff
Solution
30. An analysis model that illustrates the architecture of the system's user interface.
Temporal Event
Dialog Map
Verification
Document Analysis
31. 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
Business Constraint(s)
Data Dictionary
Product
Request For Information (RFI)
32. A function of an organization that enables it to achieve a business goal or objective.
Business Event
Benchmarking
Domain Subject Matter Expert (SME)
Capability
33. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
Model(s)
User Acceptance Test
Solution
Data Entity
34. Any recognized association of people in the context of an organization or enterprise.
Organizational Unit
Defect
Competitive Analysis
Activity
35. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.
Project Scope
User
Optionality
Black Box Tests
36. An assessment of the costs and benefits associated with a proposed initiative.
Stated Requirements
Horizontal Prototype
Solution Requirement
Business Case
37. 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
Requirement(s) Defect
Non-functional Requirement(s)
Request For Information (RFI)
Focus Group
38. Ability of systems to communicate by exchanging data or services.
Decision Analysis
Interoperability
Implementation Subject Matter Expert (SME)
Process Map
39. Software requirements that limit the options available to the system designer.
Domain
Design Constraints
Domain Subject Matter Expert (SME)
Business Event
40. A prototype used to quickly uncover and clarify interface requirements using simple tools sometimes just paper and pencil. Usually discarded when the final system has been developed.
Throw-away Prototype
Use Case Diagram
Defect
Technical Constraint(s)
41. 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.
Business Analysis Plan
Requirements Iteration
Document Analysis
Checklist
42. A stakeholder person device or system that directly or indirectly accesses a system.
Force Field Analysis
Opportunity Analysis
Requirements Allocation
User
43. A set of requirements grouped together in a document or presentation for communication to stakeholders.
Requirements Package
Interview
Focus Group
Activity Diagram
44. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
Incremental Delivery
Non-functional Requirement(s)
Verification
Constraint
45. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.
Business Domain Model
Relationship Map
Project
Requirements Validation
46. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.
Verified Requirements
Organizational Readiness Assessment
Stakeholder Analysis
Requirements Validation
47. A system of programming statements symbols and rules used to represent instructions to a computer.
Customer
Dialog Hierarchy
Verified Requirements
Code
48. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.
Methodology
Event Response Table
Stakeholder List
Requirements Management
49. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.
Lessons Learned Process
Business Requirements Document
Domain Subject Matter Expert (SME)
Change Control Board (CCB)
50. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).
Developer
Business Need(s)
Business Requirements Document
Walkthrough