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 temporary endeavor undertaken to create a unique product service or result.
Project
Stakeholder List
Incremental Delivery
Supplier
2. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.
Developer
Requirements Traceability
Checklist
Requirements Management Tool
3. A solution or component of a solution that is the result of a project.
Analyst
Relationship
Data Entity
Product
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.
Stated Requirements
Analyst
Organization Modeling
Business Case
5. A partial or preliminary version of the system.
Requirement
Prototype
Opportunity Analysis
Supplier
6. 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
System
Problem Statement
Assumption
7. 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 Policy
Structured Walkthrough
Enterprise
Software/Systems Requirements Specification
8. 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
Data Dictionary
Software/Systems Requirements Specification
Benchmarking
9. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.
Quality Attributes
Glossary
User Story
Subject Matter Expert (SME)
10. 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.
Plan-driven Methodology
Business Requirement
Focus Group
Initiative
11. Describes any limitations imposed on the solution that do not support the business or stakeholder needs.
Work Breakdown Structure (WBS)
Problem Statement
Constraint
State Diagram
12. 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.
Service
Incremental Delivery
Verification
Analyst
13. Any recognized association of people in the context of an organization or enterprise.
Regulator
Metric
Organizational Unit
Incremental Delivery
14. 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.
Defect
Focus Group
Knowledge Area
Plan-driven Methodology
15. A unit of work performed as part of an initiative or process.
Request For Proposal (RFP)
Activity
Requirements Package
End User
16. A high-level informal short description of a solution capability that provides value to a stakeholder. Is typically one or two sentences long and provides the minimum information necessary to allow a developer to estimate the work required to impleme
User Story
Enterprise Architecture
Implementation Subject Matter Expert (SME)
Temporal Event
17. Any unique and verifiable work product or service that a party has agreed to deliver.
Business Requirement
Deliverable
Product
Constraint
18. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.
Subject Matter Expert (SME)
Brainstorming
Use Case Diagram
Dialog Map
19. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.
Data Entity
Monitoring
Vertical Prototype
Operative Rule(s)
20. 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.
Quality Assurance
Monitoring
Business Process
Event Response Table
21. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.
Evaluation
Horizontal Prototype
Metadata
Relationship
22. Activities performed to ensure that a process will deliver products that meet an appropriate level of quality.
Quality Assurance
Business Analysis Communication Plan
Functional Requirement(s)
Competitive Analysis
23. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.
Quality Assurance
Stakeholder Analysis
Requirements Validation
Requirements Traceability
24. 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.
Span of Control
Interface
Competitive Analysis
Requirements Iteration
25. A requirements workshop is a structured meeting in which a carefully selected group of stakeholders collaborate to define and or refine requirements under the guidance of a skilled neutral facilitator.
Regulator
Requirements Workshop
Optionality
Interface
26. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Quality Assurance
Indicator
Technical Constraint(s)
Stakeholder Analysis
27. A fixed period of time to accomplish a desired outcome.
Requirements Signoff
Stated Requirements
Requirements Allocation
Timebox
28. A point-in-time view of requirements that have been reviewed and agreed upon to serve as a basis for further development.
Baseline
Competitive Analysis
Requirements Management Plan
Technique
29. A stakeholder with legal or governance authority over the solution or the process used to develop it.
Cardinality
Sponsor
Included Use Cases
Regulator
30. A function of an organization that enables it to achieve a business goal or objective.
Capability
State Diagram
Document Analysis
Business Process
31. Interfaces with other systems (hardware software and human) that a proposed system will interact with.
Organizational Process Asset
External Interfaces
Subject Matter Expert (SME)
Requirements Package
32. A system of programming statements symbols and rules used to represent instructions to a computer.
Domain Subject Matter Expert (SME)
Code
Business Analyst
System
33. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.
Problem Statement
Capability
Data Model
Scope Model
34. A group of related tasks that support a key function of business analysis.
Transition Requirement(s)
Objective
Knowledge Area
Optionality
35. The set of capabilities a solution must deliver in order to meet the business need.
Capability
Product Backlog
Solution Scope
Variance Analysis
36. 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.
Regulator
Non-functional Requirement(s)
Requirements Model
Interview
37. 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
Interview
State Diagram
Peer Review
38. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.
Initiative
Software/Systems Requirements Specification
Commercial-off-the-Shelf Software (COTS)
Organizational Readiness Assessment
39. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).
Technique
Requirements Allocation
Impact Analysis
Force Field Analysis
40. Creating working software in multiple releases so the entire product is delivered in portions over time.
Incremental Delivery
Requirements Signoff
Structured Walkthrough
Gap Analysis
41. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.
Deliverable
Stakeholder Analysis
Walkthrough
Developer
42. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.
Vision Statement (product vision statement)
Organizational Readiness Assessment
Operational Support
Supplier
43. 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.
User Requirements Document
Risk
Operational Support
Cost Benefit Analysis
44. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.
Structural Rule
SWOT Analysis
Horizontal Prototype
Decision Tree
45. 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.
Quality
Enterprise
Stakeholder List
Force Field Analysis
46. A comparison of the current state and desired future state of an organization in order to identify differences that need to be addressed.
Requirements Management Plan
Gap Analysis
Enterprise
Objective
47. A matrix used to track requirements' relationships. Each column in the matrix provides requirements information and associated project or software development components.
Requirements Trace Matrix
Swimlane
System
Quality Assurance
48. 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.
Walkthrough
Inspection
Business Analysis Plan
Evolutionary Prototype
49. 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).
Elicitation
Operational Support
Functional Requirement(s)
Requirements Model
50. A stakeholder who provides products or services to an organization.
Supplier
Dialog Map
Project Manager
Business Case