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 state or condition the business must satisfy to reach its vision.
Dialog Map
Business Goal
Business Case
Software/Systems Requirements Specification
2. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.
Competitive Analysis
Organizational Readiness Assessment
Dialog Map
Request For Proposal (RFP)
3. 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.
User Acceptance Test
Requirements Signoff
Project Charter
Force Field Analysis
4. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.
Change Control Board (CCB)
Business Process
Evaluation
Subject Matter Expert (SME)
5. 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.
Iteration
Metadata
Interoperability
Evolutionary Prototype
6. 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.
Gap Analysis
Indicator
Requirements Traceability
Exploratory Prototype
7. A cohesive bundle of externally visible functionality that should align with business goals and objectives. Each is a logically related grouping of functional requirements or non-functional requirements described in broad strokes.
Initiative
Feature
Unified Modeling Language (UML)
Request For Proposal (RFP)
8. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.
Metadata
Lessons Learned Process
Black Box Tests
Elicitation
9. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.
Tester
Desired Outcome
Gap Analysis
Validated Requirements
10. The area covered by a particular activity or topic of interest.
Technical Constraint(s)
Decision Analysis
Scope
Methodology
11. A practitioner of business analysis.
End User
Business Analyst
Sequence Diagram
Desired Outcome
12. 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
Implementation Subject Matter Expert (SME)
Organization Modeling
Horizontal Prototype
Request For Information (RFI)
13. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.
Tester
Repository
Scenario
Sponsor
14. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.
Service
Optionality
Attribute
Developer
15. 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.
Organizational Unit
Business Analysis
Domain
Business Analysis Communication Plan
16. A system trigger that is initiated by time.
Constraint
Data Dictionary
Temporal Event
User
17. 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.
Data Model
Plan-driven Methodology
External Interfaces
Walkthrough
18. Work carried out or on behalf of others.
Service
Business Event
Indicator
End User
19. A solution or component of a solution that is the result of a project.
Product
Vertical Prototype
Repository
Work Breakdown Structure (WBS)
20. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.
Walkthrough
Knowledge Area
Product Backlog
Competitive Analysis
21. 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
Scope Model
Cardinality
Validation
22. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.
Inspection
Requirements Management
Data Flow Diagram (DFD)
Solution Requirement
23. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.
Requirements Verification
Operational Support
Software/Systems Requirements Specification
Interoperability
24. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.
User Story
User Acceptance Test
State Diagram
Glossary
25. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.
Project Charter
Evolutionary Prototype
Developer
Entity-Relationship Diagram
26. Determine when something is or is not true or when things fall into a certain category. They describe categorizations that may change over time.
Brainstorming
SWOT Analysis
Exploratory Prototype
Structural Rule
27. The set of capabilities a solution must deliver in order to meet the business need.
Feasibility Study
Organizational Readiness Assessment
Solution Scope
Request For Proposal (RFP)
28. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.
Use Case Diagram
Data Flow Diagram (DFD)
Problem Statement
Business Analysis Approach
29. A person with specific expertise in an area or domain under investigation.
Software/Systems Requirements Specification
Fishbone Diagram
Gap Analysis
Domain Subject Matter Expert (SME)
30. An error in requirements caused by incorrect incomplete missing or conflicting requirements.
Sequence Diagram
Requirements Signoff
Requirement(s) Attribute
Requirement(s) Defect
31. A formal type of peer review that utilizes a predefined and documented process specific participant roles and the capture of defect and process metrics. See also structured walkthrough.
Checklist
Competitive Analysis
Inspection
Optionality
32. A type of high-level business requirement that is a statement of a business objective or an impact the solution should have on its environment.
Requirements Allocation
Domain
Business Need(s)
Scope
33. Limitations on the design of a solution that derive from the technology used in its implementation.
Cardinality
Stated Requirements
Technical Constraint(s)
Business Domain Model
34. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.
Organizational Readiness Assessment
Unified Modeling Language (UML)
Business Analysis
Use Case
35. 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.
Product Scope
Business Analysis Plan
Process Map
Business Requirements Document
36. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.
Domain
Stakeholder Requirement
Secondary Actor
System
37. 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
Gap Analysis
Inspection
Observation
38. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.
Baseline
Model(s)
Capability
Gap Analysis
39. The human and nonhuman roles that interact with the system.
Methodology
Actor(s)
Indicator
Tester
40. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.
Developer
Use Case
Commercial-off-the-Shelf Software (COTS)
Business Case
41. 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
Use Case Diagram
Design Constraints
Requirements Verification
Focus Group
42. The quality attributes design and implementation constraints and external interfaces that the product must have.
State Diagram
Non-functional Requirement(s)
Metric
Deliverable
43. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.
Relationship
Decision Analysis
Return on Investment
Metric
44. Information that is used to understand the context and validity of information recorded in a system.
Metadata
Stakeholder List
Iteration
Solution Requirement
45. 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.
Verification
Organization Modeling
Stakeholder Requirement
Checklist
46. The set of processes templates and activities that will be used to perform business analysis in a specific context.
Business Process
Subject Matter Expert (SME)
Requirements Management Tool
Business Analysis Approach
47. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.
Indicator
Solution Scope
Assumption
Throw-away Prototype
48. 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
Requirements Iteration
Deliverable
Validated Requirements
Domain Subject Matter Expert (SME)
49. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.
Objective
Validated Requirements
Requirements Model
Customer
50. All materials used by groups within an organization to define tailor implement and maintain their processes.
Glossary
Verified Requirements
Organizational Process Asset
Observation