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 real or virtual facility where all information on a specific topic is stored and is available for retrieval.
Code
Work Breakdown Structure (WBS)
Repository
Request For Proposal (RFP)
2. 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.
Plan-driven Methodology
Change-driven Methodology
Stakeholder List
Impact Analysis
3. A model that defines the boundaries of a business domain or solution.
Glossary
Scope Model
Change Control Board (CCB)
Actor(s)
4. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.
Gap Analysis
Operational Support
Work Product
Quality Attributes
5. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.
Organizational Unit
Process Map
Organizational Readiness Assessment
Vision Statement (product vision statement)
6. A solution or component of a solution that is the result of a project.
Product
Data Flow Diagram (DFD)
Requirements Trace Matrix
Baseline
7. An error in requirements caused by incorrect incomplete missing or conflicting requirements.
Stakeholder
Requirement(s) Defect
Requirements Verification
State Diagram
8. A use case composed of a common set of steps used by multiple use cases.
Change Control Board (CCB)
Included Use Cases
Span of Control
Requirements Trace Matrix
9. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.
Evaluation
Document Analysis
Use Case Diagram
Capability
10. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.
Indicator
Iteration
Requirements Signoff
Verified Requirements
11. The process of examining new business opportunities to improve organizational performance.
Requirements Signoff
Opportunity Analysis
Brainstorming
Risk
12. All materials used by groups within an organization to define tailor implement and maintain their processes.
Vision Statement (product vision statement)
Change Control Board (CCB)
Organizational Readiness Assessment
Organizational Process Asset
13. An analysis model describing the data structures and attributes needed by the system.
Exploratory Prototype
Cardinality
Entity-Relationship Diagram
Data Dictionary
14. A description of the planned activities that the business analyst will execute in order to perform the business analysis work involved in a specific initiative.
Change Control Board (CCB)
Knowledge Area
Business Analysis Plan
Stakeholder List
15. Software requirements that limit the options available to the system designer.
Design Constraints
Competitive Analysis
Sponsor
Exploratory Prototype
16. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.
Organization Modeling
Work Product
Organization
Gap Analysis
17. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.
Sponsor
Requirements Package
Plan-driven Methodology
Event Response Table
18. A non-actionable directive that supports a business goal.
Business Policy
Requirements Management Plan
Validation
Stakeholder
19. An informal solicitation of proposals from vendors.
Request For Quote (RFQ)
Decision Analysis
Supplier
Swimlane
20. 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).
Validated Requirements
Event
Subject Matter Expert (SME)
Operational Support
21. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.
Solution Requirement
Exploratory Prototype
Dialog Hierarchy
Incremental Delivery
22. An analysis model that illustrates the architecture of the system's user interface.
Quality Assurance
Dialog Map
Change Control Board (CCB)
Business Policy
23. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.
Capability
Stakeholder List
Solution
SWOT Analysis
24. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.
Temporal Event
Functional Requirement(s)
Business Requirement
Commercial-off-the-Shelf Software (COTS)
25. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.
Interoperability
Organizational Unit
Monitoring
End User
26. 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.
Design Constraints
Request For Quote (RFQ)
Verification
Business Goal
27. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.
Prioritization
Requirements Management Tool
Change-driven Methodology
Decomposition
28. Test cases that users employ to judge whether the delivered system is acceptable. Each acceptance test describes a set of system inputs and expected results.
Business Case
Class
Object Oriented Modeling
User Acceptance Test
29. 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
Interview
Lessons Learned Process
Requirements Model
Requirements Iteration
30. 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.
Sponsor
Requirement
Use Case
Business Requirements Document
31. Statements of the needs of a particular stakeholder or class of stakeholders. They describe the needs that a given stakeholder has and how that stakeholder will interact with a solution. Serve as a bridge between business requirements and the various
Business Case
Stakeholder Requirement
Elicitation
Quality Assurance
32. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.
Structural Rule
Work Product
Analyst
System
33. 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.
Subject Matter Expert (SME)
Business Analysis Communication Plan
Scope
Event Response Table
34. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.
Solution
Incremental Delivery
Supplier
Entity-Relationship Diagram
35. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).
Business Requirements Document
Project Charter
State Diagram
Interoperability
36. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.
Stated Requirements
Baseline
Sponsor
Actor(s)
37. The problem area undergoing analysis.
Operative Rule(s)
Scope
Domain
Stakeholder List
38. Formal approval of a set of requirements by a sponsor or other decision maker.
Business Process
Monitoring
Requirements Signoff
Cardinality
39. Information that is used to understand the context and validity of information recorded in a system.
Solution Scope
State Diagram
Requirements Traceability
Metadata
40. An analysis model that shows user interface dialogs arranged as hierarchies.
Dialog Hierarchy
Plan-driven Methodology
Focus Group
Deliverable
41. A structured examination of an identified problem to understand the underlying causes.
Impact Analysis
Root Cause Analysis
Throw-away Prototype
Data Dictionary
42. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.
Business Requirements Document
Software/Systems Requirements Specification
Optionality
Scope Model
43. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.
Structured Walkthrough
Objective
Included Use Cases
Use Case Diagram
44. A temporary endeavor undertaken to create a unique product service or result.
Business Case
Project
Business Goal
Incremental Delivery
45. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.
Survey
Requirements Traceability
Relationship
Vision Statement (product vision statement)
46. The product capabilities or things the product must do for its users.
Structured Walkthrough
Secondary Actor
Functional Requirement(s)
Business Domain Model
47. A fixed period of time to accomplish a desired outcome.
Transition Requirement(s)
Structural Rule
Timebox
Opportunity Analysis
48. An activity within requirements development that identifies sources for requirements and then uses elicitation techniques (e.g. interviews prototypes facilitated workshops documentation studies) to gather requirements from those sources.
Scenario
Business Analyst
Initiative
Elicitation
49. A means to elicit ideas and attitudes about a specific product service or opportunity in an interactive group environment. The participants share their impressions preferences and needs guided by a moderator.
Throw-away Prototype
Temporal Event
Focus Group
Structural Rule
50. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.
Elicitation
User Story
Observation
Solution