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. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.
Assumption
Data Entity
Black Box Tests
Quality Attributes
2. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.
Cost Benefit Analysis
Organizational Unit
Elicitation
Process Model
3. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.
Solution
Requirements Trace Matrix
Tester
Monitoring
4. The quality attributes design and implementation constraints and external interfaces that the product must have.
Non-functional Requirement(s)
Desired Outcome
Service
Project Manager
5. The process of examining new business opportunities to improve organizational performance.
Opportunity Analysis
Peer Review
Initiative
Iteration
6. 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
Enterprise Architecture
Product
Actor(s)
Business Constraint(s)
7. A subset of the enterprise architecture that defines an organization's current and future state including its strategy its goals and objectives the internal environment through a process or functional view the external environment in which the busine
Business Architecture
Glossary
Secondary Actor
Class
8. 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
Requirements Model
Vertical Prototype
Object Oriented Modeling
Project
9. The product capabilities or things the product must do for its users.
Force Field Analysis
Requirements Management Tool
User Requirements Document
Functional Requirement(s)
10. A function of an organization that enables it to achieve a business goal or objective.
User Story
Temporal Event
Cardinality
Capability
11. Any effort undertaken with a defined goal or objective.
Business Constraint(s)
Structured Walkthrough
Initiative
Walkthrough
12. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.
SWOT Analysis
Organizational Process Asset
Business Analyst
Technical Constraint(s)
13. 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.
Metric
Glossary
Relationship Map
Work Breakdown Structure (WBS)
14. 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.
Process Model
Requirements Validation
Use Case
Requirements Allocation
15. A prototype that dives into the details of the interface functionality or both.
Vertical Prototype
External Interfaces
User Acceptance Test
Vision Statement (product vision statement)
16. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.
Developer
Peer Review
Quality Assurance
Data Model
17. 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.
Business Process
Requirements Validation
Evaluation
Service
18. The process of checking a product to ensure that it satisfies its intended use and conforms to its requirements. Ensures that you built the correct solution.
Validation
Request For Proposal (RFP)
Validated Requirements
Object Oriented Modeling
19. 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
User Story
Customer
Supplier
Enterprise
20. Roles and Responsibility DesignationA listing of the stakeholders affected by a business need or proposed solution and a description of their participation in a project or other initiative.
Benchmarking
Product
Association
Stakeholder List
21. The human and nonhuman roles that interact with the system.
Cardinality
Organization Modeling
Business Analyst
Actor(s)
22. 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.
Included Use Cases
Iteration
Product Scope
Non-functional Requirement(s)
23. An actor who participates in but does not initiate a use case.
Desired Outcome
Glossary
Organizational Readiness Assessment
Secondary Actor
24. 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.
Cardinality
Assumption
Process Map
Association
25. 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.
Object Oriented Modeling
Benchmarking
Business Requirement
User Story
26. A stakeholder person device or system that directly or indirectly accesses a system.
User
Business Requirements Document
Event Response Table
Fishbone Diagram
27. A fixed period of time to accomplish a desired outcome.
Timebox
Scope Model
Subject Matter Expert (SME)
Requirement
28. A target or metric that a person or organization seeks to meet in order to progress towards a goal.
Business Requirements Document
Product
Objective
Project Scope
29. 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.
Project Manager
Evolutionary Prototype
Timebox
Walkthrough
30. A shared boundary between any two persons and/or systems through which information is communicated.
Secondary Actor
Interface
Span of Control
Glossary
31. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.
Use Case Diagram
Structural Rule
Data Flow Diagram (DFD)
Survey
32. 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.
Event Response Table
SWOT Analysis
Elicitation
Event
33. 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.
Request For Quote (RFQ)
Verified Requirements
Problem Statement
User Story
34. A system trigger that is initiated by humans.
Decision Tree
Dialog Map
Business Event
User Acceptance Test
35. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.
Problem Statement
Software/Systems Requirements Specification
Competitive Analysis
Survey
36. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.
Project Charter
Business Rule(s)
Functional Requirement(s)
Unified Modeling Language (UML)
37. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.
Relationship Map
Requirements Validation
Organization Modeling
Cardinality
38. A requirements workshop is a structured meeting in which a carefully selected group of stakeholders collaborate to define and or refine requirements under the guidance of a skilled neutral facilitator.
Functional Requirement(s)
Quality Assurance
Requirements Workshop
Enterprise Architecture
39. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.
Competitive Analysis
Process Model
Requirements Validation
Glossary
40. 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.
Requirements Signoff
Feasibility Study
Business Requirements Document
Cardinality
41. A stakeholder with legal or governance authority over the solution or the process used to develop it.
Focus Group
Regulator
Operative Rule(s)
Analyst
42. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.
Horizontal Prototype
Use Case
Peer Review
Initiative
43. A prototype that is continuously modified and updated in response to feedback from users.
Requirements Traceability
Evolutionary Prototype
Validated Requirements
Design Constraints
44. A systematic approach to elicit information from a person or group of people in an informal or formal setting by asking relevant questions and documenting the responses.
Survey
Interview
Validation
Stakeholder
45. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.
Repository
Project Manager
Data Model
Code
46. All materials used by groups within an organization to define tailor implement and maintain their processes.
Stakeholder
Organizational Process Asset
Requirements Management Tool
Activity Diagram
47. A state or condition the business must satisfy to reach its vision.
Unified Modeling Language (UML)
Product Backlog
Business Analysis Communication Plan
Business Goal
48. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.
Interface
Glossary
Attribute
Developer
49. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.
Decision Analysis
Scenario
Decomposition
Functional Requirement(s)
50. A practitioner of business analysis.
Quality
Functional Requirement(s)
Solution
Business Analyst