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 target or metric that a person or organization seeks to meet in order to progress towards a goal.
Interoperability
Object Oriented Modeling
Objective
Enterprise Architecture
2. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.
User Acceptance Test
Vision Statement (product vision statement)
Variance Analysis
Organizational Process Asset
3. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.
Activity
Observation
Indicator
Developer
4. A set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Are triggered by events and may have multiple possible outcomes. A successful outcome of a process will deliver value to one or more s
Business Process
State Diagram
Prototype
Verification
5. A process improvement technique used to learn about and improve on a process or project. Involves a special meeting in which the team explores what worked what didn't work what could be learned from the just-completed iteration and how to adapt proce
Lessons Learned Process
Requirements Model
Feature
Desired Outcome
6. A description of the requirements management process.
Requirements Traceability
Knowledge Area
Requirements Management Plan
Constraint
7. Analysis of discrepancies between planned and actual performance to determine the magnitude of those discrepancies and recommend corrective and preventative action as required.
Variance Analysis
Scenario
Incremental Delivery
Design Constraints
8. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.
Organization Modeling
Customer
Product
Cardinality
9. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.
Inspection
Organization
User Story
Relationship
10. A prototype that dives into the details of the interface functionality or both.
Vertical Prototype
Data Model
Project Scope
Dialog Map
11. Work carried out or on behalf of others.
Indicator
Change Control Board (CCB)
Sequence Diagram
Service
12. A requirements document issued when an organization is seeking a formal proposal from vendors. Typically requires that the proposals be submitted following a specific process and using sealed bids which will be evaluated against a formal evaluation m
Decision Tables
Request For Proposal (RFP)
Object Oriented Modeling
Quality Attributes
13. 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.
Vision Statement (product vision statement)
Solution Scope
Verified Requirements
Process Model
14. The ability to identify and document the lineage of each requirement including its derivation (backward traceability) its allocation (forward traceability) and its relationship to other requirements.
Horizontal Prototype
Change-driven Methodology
Validation
Requirements Traceability
15. A specific actionable testable directive that is under the control of the business and supports a business policy.
Plan-driven Methodology
Requirements Management
Business Rule(s)
Business Architecture
16. 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.
Checklist
Enterprise
Swimlane
Feasibility Study
17. 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
Dialog Hierarchy
Capability
Requirements Signoff
Request For Information (RFI)
18. 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.
Methodology
Customer
Force Field Analysis
Gap Analysis
19. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.
Operative Rule(s)
Variance Analysis
Dialog Map
Problem Statement
20. A system of programming statements symbols and rules used to represent instructions to a computer.
Business Analysis
Code
Object Oriented Modeling
Requirements Traceability
21. Any methodology that emphasizes planning and formal documentation of the processes used to accomplish a project and of the results of the project. Emphasize the reduction of risk and control over outcomes over the rapid delivery of a solution.
Organization Modeling
Class
Plan-driven Methodology
Requirements Traceability
22. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.
Fishbone Diagram
Gap Analysis
Project Charter
Change-driven Methodology
23. An informal solicitation of proposals from vendors.
Request For Quote (RFQ)
Transition Requirement(s)
Desired Outcome
Optionality
24. A data element with a specified data type that describes information associated with a concept or entity.
Stated Requirements
Attribute
Validation
Business Need(s)
25. A stakeholder person device or system that directly or indirectly accesses a system.
User
Requirements Management Plan
Solution Scope
Solution
26. The business benefits that will result from meeting the business need and the end state desired by stakeholders.
Desired Outcome
Included Use Cases
State Diagram
Requirement(s) Attribute
27. Ability of systems to communicate by exchanging data or services.
Organization Modeling
Enterprise Architecture
External Interfaces
Interoperability
28. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.
Entity-Relationship Diagram
Return on Investment
User Acceptance Test
Evolutionary Prototype
29. A person or system that directly interacts with the solution. Can be humans who interface with the system or systems that send or receive data files to or from the system.
Work Breakdown Structure (WBS)
End User
Unified Modeling Language (UML)
Requirements Package
30. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.
Activity
Supplier
Software/Systems Requirements Specification
Business Analyst
31. The degree to which a set of inherent characteristics fulfills requirements.
Requirement
Defect
Quality
Stakeholder Analysis
32. A unit of work performed as part of an initiative or process.
Activity
Change-driven Methodology
Entity-Relationship Diagram
Interoperability
33. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.
Observation
Requirements Workshop
Functional Requirement(s)
Stated Requirements
34. A partial or preliminary version of the system.
Project Charter
Structural Rule
Project
Prototype
35. 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.
Stakeholder List
Cardinality
Iteration
Sequence Diagram
36. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.
Feature
Unified Modeling Language (UML)
Survey
Operative Rule(s)
37. 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.
Change-driven Methodology
Capability
Business Analysis Communication Plan
Prototype
38. 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.
Business Rule(s)
Class
Requirement
Survey
39. 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
Business Analyst
Elicitation
Included Use Cases
Requirements Iteration
40. A use case composed of a common set of steps used by multiple use cases.
Included Use Cases
Class
Risk
Focus Group
41. An analysis model that specifies complex business rules or logic concisely in an easy-to-read tabular format specifying all of the possible conditions and actions that need to be accounted for in business rules.
Decision Tables
Project Scope
Quality Attributes
Included Use Cases
42. A prototype that is continuously modified and updated in response to feedback from users.
Stated Requirements
Evolutionary Prototype
Event Response Table
Feasibility Study
43. An error in requirements caused by incorrect incomplete missing or conflicting requirements.
Data Dictionary
Transition Requirement(s)
Constraint
Requirement(s) Defect
44. An organized peer review of a deliverable with the objective of finding errors and omissions. It is considered a form of quality assurance.
Gap Analysis
Business Analyst
Structured Walkthrough
Inspection
45. Interfaces with other systems (hardware software and human) that a proposed system will interact with.
External Interfaces
Technique
Inspection
Activity Diagram
46. Software requirements that limit the options available to the system designer.
Stakeholder
Business Event
Design Constraints
Scope Model
47. A descriptor for a set of system objects that share the same attributes operations relationships and behavior. Represents a concept in the system under design. When used as an analysis model a class will generally also correspond to a real-world enti
Impact Analysis
Requirements Iteration
Quality
Class
48. 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.
Constraint
Document Analysis
Cost Benefit Analysis
Dialog Hierarchy
49. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.
Structural Rule
Force Field Analysis
User Requirements Document
Data Flow Diagram (DFD)
50. 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 Allocation
Actor(s)
Iteration
Business Analysis