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 description of the requirements management process.
Code
Requirements Management Plan
Data Model
Observation
2. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.
Decision Tree
Analyst
Business Constraint(s)
Technical Constraint(s)
3. An analysis model showing the life cycle of a data entity or class.
State Diagram
Software/Systems Requirements Specification
Impact Analysis
Transition Requirement(s)
4. The horizontal or vertical section of a process model that show which activities are performed by a particular actor or role.
Business Event
Requirements Management Tool
Customer
Swimlane
5. 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.
Event Response Table
Deliverable
Event
Model(s)
6. An analysis model that illustrates the architecture of the system's user interface.
Data Entity
Scenario
Stakeholder Analysis
Dialog Map
7. A model that defines the boundaries of a business domain or solution.
Scope Model
Business Goal
Requirement(s) Attribute
Incremental Delivery
8. The business rules an organization chooses to enforce as a matter of policy. They are intended to guide the actions of people working within the business. They may oblige people to take certain actions prevent people from taking actions or prescribe
Business Analyst
Dialog Hierarchy
Operative Rule(s)
Inspection
9. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.
Business Rule(s)
Business Architecture
Organization Modeling
Change-driven Methodology
10. A continuous process of collecting data to determine how well a solution is implemented compared to expected results. See also metric and indicator.
Developer
Business Analysis Approach
Stakeholder Requirement
Monitoring
11. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.
Solution Requirement
Relationship Map
Organizational Process Asset
Defect
12. The business benefits that will result from meeting the business need and the end state desired by stakeholders.
Cardinality
Structured Walkthrough
Requirements Signoff
Desired Outcome
13. A document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.
User Acceptance Test
Fishbone Diagram
Relationship
Project Charter
14. A requirement articulated by a stakeholder that has not been analyzed verified or validated. Frequently reflect the desires of a stakeholder rather than the actual need.
Indicator
Stated Requirements
Data Model
Gap Analysis
15. A non-proprietary modeling and specification language used to specify visualize and document deliverables for object-oriented software-intensive systems.
Data Dictionary
Cardinality
Unified Modeling Language (UML)
Association
16. A partial or preliminary version of the system.
Checklist
Interface
Prototype
Dialog Hierarchy
17. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.
Decision Tree
Requirement
SWOT Analysis
Class
18. A target or metric that a person or organization seeks to meet in order to progress towards a goal.
Code
Objective
Capability
Use Case
19. A higher level business rationale that when addressed will permit the organization to increase revenue avoid costs improve service or meet regulatory requirements.
Business Requirement
Regulator
Lessons Learned Process
Quality Assurance
20. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.
Problem Statement
Requirement
Decision Tree
Peer Review
21. The process of checking a product to ensure that it satisfies its intended use and conforms to its requirements. Ensures that you built the correct solution.
Business Constraint(s)
SWOT Analysis
Validation
Desired Outcome
22. The process of examining new business opportunities to improve organizational performance.
Opportunity Analysis
Business Rule(s)
Defect
Validation
23. A prototype that is continuously modified and updated in response to feedback from users.
Stated Requirements
Requirements Validation
Evolutionary Prototype
Activity Diagram
24. A type of data model that depicts information groups as classes.
Class Model
Design Constraints
Organizational Process Asset
Repository
25. An uncertain event or condition that if it occurs will affect the goals or objectives of a proposed change.
Risk
Verification
Timebox
Decision Analysis
26. Interfaces with other systems (hardware software and human) that a proposed system will interact with.
End User
External Interfaces
Activity
Requirements Validation
27. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).
Tester
Commercial-off-the-Shelf Software (COTS)
Request For Quote (RFQ)
Quality Attributes
28. The work that must be performed to deliver a product service or result with the specified features and functions.
Project Scope
Solution
Relationship
Requirement(s) Defect
29. A requirements package that describes business requirements and stakeholder requirements (it documents requirements of interest to the business rather than documenting business requirements).
Business Analysis
Stated Requirements
Association
Business Requirements Document
30. The number of occurrences of one entity in a data model that are linked to a second entity. Is shown on a data model with a special notation number (e.g. 1) or letter (e.g. M for many).
Cardinality
Requirements Validation
Sponsor
External Interfaces
31. The systematic and objective assessment of a solution to determine its status and efficacy in meeting objectives over time and to identify ways to improve the solution to better meet objectives. See also metric indicator and monitoring.
Evaluation
Requirements Management Plan
Change-driven Methodology
Decision Analysis
32. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.
Vision Statement (product vision statement)
Solution
Repository
Quality Attributes
33. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.
Technique
Requirement
Code
Organization Modeling
34. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.
Impact Analysis
Metric
Product Scope
External Interfaces
35. 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.
Code
Use Case Diagram
Process Map
Use Case
36. 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.
Project Scope
Black Box Tests
Interoperability
Business Need(s)
37. Influencing factors that are believed to be true but have not been confirmed to be accurate.
Assumption
Business Constraint(s)
Domain
Verified Requirements
38. A system of programming statements symbols and rules used to represent instructions to a computer.
Event
Code
Process Map
Attribute
39. 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.
Business Requirement
Customer
Association
Verification
40. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.
Solution
Checklist
Impact Analysis
Competitive Analysis
41. Software developed and sold for a particular market.
Developer
Commercial-off-the-Shelf Software (COTS)
Use Case
Activity Diagram
42. 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.
Data Model
Throw-away Prototype
Elicitation
Data Dictionary
43. A document or collection of notes or diagrams used by the business analyst during the requirements development process.
Work Product
Document Analysis
Business Analysis Approach
Organizational Readiness Assessment
44. A state or condition the business must satisfy to reach its vision.
Business Goal
Business Rule(s)
Secondary Actor
Change-driven Methodology
45. 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
Project
Structural Rule
Lessons Learned Process
Requirements Risk Mitigation Strategy
46. 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.
Stakeholder
User Acceptance Test
Context Diagram
Process Map
47. 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
Business Constraint(s)
Stakeholder Analysis
Incremental Delivery
48. Formal approval of a set of requirements by a sponsor or other decision maker.
Business Constraint(s)
Incremental Delivery
Requirements Signoff
Deliverable
49. 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.
Stated Requirements
Variance Analysis
Benchmarking
Defect
50. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Stakeholder Analysis
Return on Investment
Attribute
Commercial-off-the-Shelf Software (COTS)