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 means to elicit requirements by conducting an assessment of the stakeholder's work environment.
Verification
Observation
Organizational Unit
Included Use Cases
2. 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.
Business Goal
Checklist
Enterprise
Quality Attributes
3. 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.
Stakeholder Analysis
Feasibility Study
Scenario
Verification
4. A generic name for a role with the responsibilities of developing and managing requirements. Other names include business analyst business integrator requirements analyst requirements engineer and systems analyst.
Analyst
Gap Analysis
Survey
Implementation Subject Matter Expert (SME)
5. 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.
Elicitation
Prioritization
Tester
Organization Modeling
6. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.
Entity-Relationship Diagram
SWOT Analysis
Business Analysis Communication Plan
Process Model
7. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
Model(s)
Attribute
Temporal Event
Decision Analysis
8. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.
Glossary
Horizontal Prototype
Impact Analysis
Interview
9. A target or metric that a person or organization seeks to meet in order to progress towards a goal.
Customer
Gap Analysis
Request For Quote (RFQ)
Objective
10. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.
Sequence Diagram
Survey
Organizational Readiness Assessment
Requirements Verification
11. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.
Quality
Subject Matter Expert (SME)
Requirements Management
Code
12. A set of written questions to stakeholders in order to collect responses from a large group in a relatively short period of time.
Interoperability
Survey
Requirements Package
Non-functional Requirement(s)
13. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.
Request For Information (RFI)
Requirements Signoff
Project Manager
Scope Model
14. 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
Change Control Board (CCB)
Activity Diagram
Decomposition
Organization
15. 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
Sequence Diagram
Iteration
Request For Quote (RFQ)
Request For Information (RFI)
16. 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.
Product Backlog
Verified Requirements
Quality Attributes
Quality
17. A prototype used to quickly uncover and clarify interface requirements using simple tools sometimes just paper and pencil. Usually discarded when the final system has been developed.
Change Control Board (CCB)
Decomposition
Regulator
Throw-away Prototype
18. 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.
Product Backlog
Requirements Allocation
Activity Diagram
Plan-driven Methodology
19. A type of diagram that shows objects participating in interactions and the messages exchanged between them.
Business Need(s)
User Requirements Document
Sequence Diagram
Enterprise Architecture
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.
Return on Investment
Stakeholder List
User Acceptance Test
Business Analysis
21. 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
Data Entity
Feasibility Study
Business Architecture
Plan-driven Methodology
22. 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.
End User
Evaluation
Event Response Table
Work Product
23. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.
Decomposition
User
Business Architecture
Desired Outcome
24. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Competitive Analysis
Methodology
Stakeholder Analysis
Peer Review
25. The area covered by a particular activity or topic of interest.
Tester
Change Control Board (CCB)
Scope
Process Map
26. The human and nonhuman roles that interact with the system.
Actor(s)
Span of Control
Business Analysis
Business Domain Model
27. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.
Requirement(s) Defect
Change-driven Methodology
Vision Statement (product vision statement)
Objective
28. A practitioner of business analysis.
Stakeholder Analysis
Business Analyst
Observation
Span of Control
29. An error in requirements caused by incorrect incomplete missing or conflicting requirements.
Product Scope
Requirements Management Plan
Requirement(s) Defect
Request For Quote (RFQ)
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.
Developer
Use Case
Business Analysis Approach
Data Flow Diagram (DFD)
31. 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.
Benchmarking
Actor(s)
Business Analysis Communication Plan
Organization Modeling
32. An assessment of the costs and benefits associated with a proposed initiative.
Business Case
Sponsor
Relationship Map
Brainstorming
33. 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
Fishbone Diagram
Requirements Risk Mitigation Strategy
Unified Modeling Language (UML)
34. 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.
Change-driven Methodology
Enterprise Architecture
Requirement(s) Attribute
Activity Diagram
35. 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
Constraint
Repository
Business Event
Stakeholder Requirement
36. 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.
Vertical Prototype
Benchmarking
Span of Control
Domain
37. The set of tasks and techniques used to work as a liaison among stakeholders in order to understand the structure policies and operations of an organization and recommend solutions that enable the organization to achieve its goals.
Business Policy
Interface
Focus Group
Business Analysis
38. Software developed and sold for a particular market.
Commercial-off-the-Shelf Software (COTS)
Quality Attributes
Timebox
Business Requirement
39. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.
Technique
Enterprise Architecture
Document Analysis
Deliverable
40. 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
Requirements Trace Matrix
Class
Project
Prototype
41. A stakeholder who will be responsible for designing developing and implementing the change described in the requirements and have specialized knowledge regarding the construction of one or more solution components.
User Story
Implementation Subject Matter Expert (SME)
Cardinality
Requirements Workshop
42. 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 Analysis Communication Plan
Indicator
Secondary Actor
User Acceptance Test
43. A shared boundary between any two persons and/or systems through which information is communicated.
Operational Support
Event
Solution Scope
Interface
44. A structured process which captures the key characteristics of an industry to predict the long-term profitability prospects and to determine the practices of the most significant competitors.
Objective
Competitive Analysis
Span of Control
Requirements Risk Mitigation Strategy
45. An analysis model describing the data structures and attributes needed by the system.
Software/Systems Requirements Specification
Business Constraint(s)
Knowledge Area
Data Dictionary
46. All materials used by groups within an organization to define tailor implement and maintain their processes.
Product
Organizational Process Asset
Activity
Variance Analysis
47. A prototype that dives into the details of the interface functionality or both.
Structural Rule
Scope Model
Vertical Prototype
Prototype
48. Any effort undertaken with a defined goal or objective.
Initiative
Requirement
Requirements Allocation
Optionality
49. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.
Actor(s)
Business Requirement
Developer
Evaluation
50. Interfaces with other systems (hardware software and human) that a proposed system will interact with.
Transition Requirement(s)
Domain
External Interfaces
Analyst