SUBJECTS
|
BROWSE
|
CAREER CENTER
|
POPULAR
|
JOIN
|
LOGIN
Business Skills
|
Soft Skills
|
Basic Literacy
|
Certifications
About
|
Help
|
Privacy
|
Terms
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 group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.
Exploratory Prototype
Knowledge Area
Data Entity
Code
2. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.
SWOT Analysis
External Interfaces
Business Need(s)
Quality Assurance
3. A stakeholder person device or system that directly or indirectly accesses a system.
Project
Data Model
Relationship
User
4. Any recognized association of people in the context of an organization or enterprise.
Verified Requirements
Organizational Unit
Included Use Cases
Elicitation
5. A diagramming technique used in root cause analysis to identify underlying causes of an observed problem and the relationships that exist between those causes.
Stakeholder Analysis
Decision Tables
Technical Constraint(s)
Fishbone Diagram
6. A system of programming statements symbols and rules used to represent instructions to a computer.
Requirements Allocation
Interface
Elicitation
Code
7. The human and nonhuman roles that interact with the system.
Actor(s)
Scenario
Feasibility Study
End User
8. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.
Optionality
Entity-Relationship Diagram
User Story
Included Use Cases
9. Any effort undertaken with a defined goal or objective.
Initiative
Stated Requirements
Requirements Management
Change-driven Methodology
10. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.
Use Case Diagram
Checklist
Work Breakdown Structure (WBS)
Business Goal
11. A document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.
Risk
Project Charter
Organizational Readiness Assessment
Enterprise
12. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.
Requirements Management Tool
Verified Requirements
Transition Requirement(s)
Data Entity
13. A description of the requirements management process.
Deliverable
Solution Scope
Requirements Management Plan
Business Requirement
14. 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
Structured Walkthrough
Quality Attributes
Return on Investment
Request For Information (RFI)
15. A partial or preliminary version of the system.
Glossary
Quality Attributes
Prototype
Product Backlog
16. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.
Repository
Methodology
Business Process
Glossary
17. The degree to which a set of inherent characteristics fulfills requirements.
Organizational Readiness Assessment
Quality
Requirement
Transition Requirement(s)
18. 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
Model(s)
Baseline
Cost Benefit Analysis
Requirements Iteration
19. An actor who participates in but does not initiate a use case.
Secondary Actor
Focus Group
Requirement(s) Defect
Sequence Diagram
20. 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.
Product
Non-functional Requirement(s)
Design Constraints
Context Diagram
21. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.
System
Vertical Prototype
Regulator
Decomposition
22. 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
Defect
Business Analysis Communication Plan
Interoperability
Request For Proposal (RFP)
23. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.
Validated Requirements
Assumption
Requirements Iteration
Solution Requirement
24. The work done to evaluate requirements to ensure they are defined correctly and are at an acceptable level of quality. It ensures the requirements are sufficiently defined and structured so that the solution development team can use them in the desig
Business Analysis Approach
Requirements Verification
Operational Support
Enterprise Architecture
25. 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
Organization Modeling
Solution Scope
Entity-Relationship Diagram
Organization
26. 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.
Requirements Traceability
Solution Requirement
Class
Commercial-off-the-Shelf Software (COTS)
27. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
Temporal Event
Operational Support
Organization Modeling
Constraint
28. 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.
Enterprise
Requirements Iteration
Association
Technical Constraint(s)
29. A shared boundary between any two persons and/or systems through which information is communicated.
Project
Data Model
Interface
Solution
30. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.
Feature
Iteration
State Diagram
Organizational Readiness Assessment
31. 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.
Interview
Activity
Peer Review
Use Case Diagram
32. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.
Validated Requirements
Relationship Map
Relationship
Objective
33. Creating working software in multiple releases so the entire product is delivered in portions over time.
User Story
Incremental Delivery
Scope Model
Objective
34. The problem area undergoing analysis.
Evolutionary Prototype
Sponsor
Domain
Business Event
35. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.
End User
Product Backlog
Prototype
User Requirements Document
36. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.
Checklist
Requirement(s) Defect
Timebox
Requirements Management
37. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.
Sponsor
Requirements Management Tool
Business Rule(s)
Stated Requirements
38. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.
Developer
System
Technique
Subject Matter Expert (SME)
39. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.
Developer
Event
Enterprise Architecture
Requirement
40. 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.
Requirements Management
Iteration
Cost Benefit Analysis
Stated Requirements
41. The process of determining the relative importance of a set of items in order to determine the order in which they will be addressed.
Stakeholder Analysis
Developer
Subject Matter Expert (SME)
Prioritization
42. A group or person who has interests that may be affected by an initiative or influence over it.
Regulator
Survey
Activity Diagram
Stakeholder
43. An analysis model showing the life cycle of a data entity or class.
Work Breakdown Structure (WBS)
Focus Group
State Diagram
Decision Tree
44. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.
Data Dictionary
Product Backlog
Business Need(s)
Organizational Readiness Assessment
45. An analysis model that illustrates the architecture of the system's user interface.
Feasibility Study
Walkthrough
Dialog Map
Vision Statement (product vision statement)
46. A prototype that shows a shallow and possibly wide view of the system's functionality but which does not generally support any actual use or interaction.
Horizontal Prototype
Business Requirement
Class Model
Root Cause Analysis
47. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.
Entity-Relationship Diagram
Request For Proposal (RFP)
Monitoring
Dialog Hierarchy
48. A model that defines the boundaries of a business domain or solution.
Business Rule(s)
Metric
Scope Model
Transition Requirement(s)
49. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.
Span of Control
Data Flow Diagram (DFD)
State Diagram
Data Model
50. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.
Design Constraints
Project
Glossary
Data Model