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 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.
Requirements Workshop
SWOT Analysis
Quality Assurance
Actor(s)
2. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.
Throw-away Prototype
Fishbone Diagram
Black Box Tests
Model(s)
3. 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.
Checklist
Change-driven Methodology
Commercial-off-the-Shelf Software (COTS)
Temporal Event
4. The number of employees a manger is directly (or indirectly) responsible for.
Timebox
Span of Control
Metric
Stakeholder Analysis
5. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.
Validated Requirements
Solution
Risk
Business Policy
6. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.
System
Business Process
Business Rule(s)
Swimlane
7. A characteristic of a solution that meets the business and stakeholder requirements. May be subdivided into functional and non-functional requirements.
Constraint
Root Cause Analysis
Scope Model
Solution Requirement
8. 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.
Project Scope
Requirement(s) Defect
Inspection
Knowledge Area
9. A model that defines the boundaries of a business domain or solution.
Scope
Structural Rule
Scope Model
Benchmarking
10. Work carried out or on behalf of others.
Software/Systems Requirements Specification
Service
Business Requirements Document
Span of Control
11. Formal approval of a set of requirements by a sponsor or other decision maker.
Root Cause Analysis
Regulator
Requirements Signoff
Glossary
12. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.
Span of Control
Risk
Request For Quote (RFQ)
Walkthrough
13. 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 Analysis
Metadata
Objective
Inspection
14. A link between two elements or objects in a diagram.
Monitoring
Association
Requirement(s) Defect
Business Requirement
15. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.
Analyst
Developer
Entity-Relationship Diagram
Knowledge Area
16. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).
Activity
Business Analysis Plan
Requirements Verification
Business Requirements Document
17. An evaluation of proposed alternatives to determine if they are technically possible within the constraints of the organization and whether they will deliver the desired benefits to the organization.
Stakeholder Requirement
Feasibility Study
Scope Model
Variance Analysis
18. 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.
Requirement
Swimlane
Change-driven Methodology
Quality Assurance
19. The stakeholder assigned by the performing organization to manage the work required to achieve the project objectives.
Project Manager
Business Process
User Requirements Document
Non-functional Requirement(s)
20. A system trigger that is initiated by time.
Monitoring
Business Analysis Plan
Temporal Event
Business Constraint(s)
21. A prototype that dives into the details of the interface functionality or both.
Stakeholder
Vertical Prototype
User Story
Requirements Iteration
22. A stakeholder who authorizes or legitimizes the product development effort by contracting for or paying for the project.
Relationship Map
Sponsor
Exploratory Prototype
Operational Support
23. A set of processes rules templates and working methods that prescribe how business analysis solution development and implementation is performed in a particular context.
Methodology
Interface
Technique
Design Constraints
24. The process of examining new business opportunities to improve organizational performance.
Methodology
Analyst
Opportunity Analysis
Technique
25. Software developed and sold for a particular market.
Initiative
Defect
State Diagram
Commercial-off-the-Shelf Software (COTS)
26. A person with specific expertise in an area or domain under investigation.
Requirements Allocation
Dialog Hierarchy
Domain Subject Matter Expert (SME)
Project Scope
27. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.
Unified Modeling Language (UML)
Objective
Change Control Board (CCB)
Use Case
28. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.
User Story
Metric
Business Domain Model
Methodology
29. A non-actionable directive that supports a business goal.
Focus Group
Stakeholder List
Business Policy
Observation
30. An analysis model that depicts the logical structure of data independent of the data design or data storage mechanisms.
Organizational Readiness Assessment
Data Model
Assumption
Prototype
31. 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.
Customer
Subject Matter Expert (SME)
Solution
Benchmarking
32. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.
Relationship
Span of Control
Observation
Indicator
33. A visual model or representation of the sequential flow and control logic of a set of related activities or actions.
Objective
Functional Requirement(s)
Process Model
Document Analysis
34. Creating working software in multiple releases so the entire product is delivered in portions over time.
Stated Requirements
Incremental Delivery
Requirements Signoff
Business Goal
35. A data element with a specified data type that describes information associated with a concept or entity.
Implementation Subject Matter Expert (SME)
Object Oriented Modeling
Business Process
Attribute
36. A specific actionable testable directive that is under the control of the business and supports a business policy.
Business Rule(s)
Business Constraint(s)
Organization Modeling
Deliverable
37. 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.
System
Analyst
Data Dictionary
Non-functional Requirement(s)
38. Limitations on the design of a solution that derive from the technology used in its implementation.
Technical Constraint(s)
Requirements Trace Matrix
Product Scope
Enterprise
39. A set of user stories requirements or features that have been identified as candidates for potential implementation prioritized and estimated.
Objective
Product Backlog
Design Constraints
Quality
40. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.
Focus Group
Assumption
Competitive Analysis
Unified Modeling Language (UML)
41. Interfaces with other systems (hardware software and human) that a proposed system will interact with.
Deliverable
Throw-away Prototype
End User
External Interfaces
42. 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
Stated Requirements
User Story
Quality Attributes
43. 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.
Process Model
Solution Scope
Plan-driven Methodology
Temporal Event
44. Ability of systems to communicate by exchanging data or services.
Object Oriented Modeling
Interoperability
Defect
Non-functional Requirement(s)
45. 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.
Requirements Risk Mitigation Strategy
Requirements Iteration
Feasibility Study
Process Map
46. Are responsible for the construction of software applications. Areas of expertise include development languages development practices and application components.
Project Manager
Monitoring
Business Policy
Developer
47. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.
Requirements Model
Requirements Workshop
Stakeholder
Focus Group
48. A partial or preliminary version of the system.
User
Requirements Signoff
Requirement(s) Defect
Prototype
49. 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.
Evaluation
Competitive Analysis
Stakeholder List
Inspection
50. The quality attributes design and implementation constraints and external interfaces that the product must have.
Business Constraint(s)
Evaluation
Evolutionary Prototype
Non-functional Requirement(s)