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. 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.
Brainstorming
Software/Systems Requirements Specification
Cost Benefit Analysis
Operational Support
2. A representation and simplification of reality developed to convey information to a specific audience to support analysis communication and understanding.
Elicitation
Decision Analysis
Requirements Risk Mitigation Strategy
Model(s)
3. An analysis model that illustrates processes that occur along with the flows of data to and from those processes.
Data Entity
Requirements Traceability
Data Flow Diagram (DFD)
Lessons Learned Process
4. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.
Requirements Risk Mitigation Strategy
Verification
Document Analysis
Request For Quote (RFQ)
5. A non-actionable directive that supports a business goal.
Business Policy
Evaluation
Solution Scope
Business Architecture
6. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.
Observation
Vision Statement (product vision statement)
Quality Attributes
Model(s)
7. A validation technique in which a small group of stakeholders evaluates a portion of a work product to find errors to improve its quality.
Regulator
Peer Review
Requirements Allocation
Assumption
8. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.
Change-driven Methodology
Decision Tree
Deliverable
Requirements Management
9. Limitations placed on the solution design by the organization that needs the solution. Describe limitations on available solutions or an aspect of the current state that cannot be changed by the deployment of the new solution. See also technical cons
Requirements Management Tool
Business Constraint(s)
Requirements Traceability
Relationship
10. 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.
Swimlane
Glossary
Vision Statement (product vision statement)
Checklist
11. An analysis model that illustrates the architecture of the system's user interface.
Peer Review
Solution Scope
Dialog Map
Context Diagram
12. 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
Organization Modeling
Class Model
Metric
13. 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.
Transition Requirement(s)
Sponsor
Black Box Tests
Throw-away Prototype
14. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.
Indicator
Objective
Supplier
Organizational Process Asset
15. Tests written without regard to how the software is implemented. These tests show only what the expected input and outputs will be.
Checklist
Black Box Tests
Variance Analysis
Monitoring
16. A description of the planned activities that the business analyst will execute in order to perform the business analysis work involved in a specific initiative.
Process Model
Decision Tree
Scope Model
Business Analysis Plan
17. The process of examining new business opportunities to improve organizational performance.
Event Response Table
Business Need(s)
Span of Control
Opportunity Analysis
18. An approach to decision-making that examines and models the possible consequences of different decisions. Assists in making an optimal decision under conditions of uncertainty.
Requirements Risk Mitigation Strategy
Data Dictionary
Solution
Decision Analysis
19. A requirements document written for a user audience describing user requirements and the impact of the anticipated changes on the users.
Activity
Project Charter
Regulator
User Requirements Document
20. An informal solicitation of proposals from vendors.
Activity Diagram
Customer
Organizational Unit
Request For Quote (RFQ)
21. 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.
Methodology
Iteration
Technical Constraint(s)
Requirements Workshop
22. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).
Product Backlog
Initiative
Quality Attributes
Design Constraints
23. A graphical method for depicting the forces that support and oppose a change. Involves identifying the forces depicting them on opposite sides of a line (supporting and opposing forces) and then estimating the strength of each set of forces.
Operational Support
Scope Model
Quality Assurance
Force Field Analysis
24. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.
Root Cause Analysis
Document Analysis
Variance Analysis
Scope
25. Ability of systems to communicate by exchanging data or services.
Interoperability
Code
Root Cause Analysis
Competitive Analysis
26. A prototype that shows a shallow and possibly wide view of the system's functionality but which does not generally support any actual use or interaction.
Horizontal Prototype
Business Analysis Plan
Walkthrough
Peer Review
27. An assessment that describes whether stakeholders are prepared to accept the change associated with a solution and are able to use it effectively.
Requirements Allocation
Organizational Readiness Assessment
Functional Requirement(s)
Throw-away Prototype
28. Meets a business need by resolving a problem or allowing an organization to take advantage of an opportunity.
Use Case Diagram
Solution
Process Map
Fishbone Diagram
29. 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.
Verification
Business Analysis Communication Plan
Process Model
Regulator
30. A small group of stakeholders who will make decisions regarding the disposition and treatment of changing requirements.
Business Analysis
Verification
Change Control Board (CCB)
Iteration
31. 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.
Organizational Unit
Use Case
Plan-driven Methodology
Optionality
32. The work done to ensure that the stated requirements support and are aligned with the goals and objectives of the business.
Business Process
Requirements Validation
Organizational Readiness Assessment
Iteration
33. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.
Solution Scope
Project Scope
Exploratory Prototype
Technique
34. 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
End User
Organizational Process Asset
Brainstorming
Class
35. A brief statement or paragraph that describes the problems in the current state and clarifies what a successful solution will look like.
Problem Statement
Enterprise Architecture
Verification
Deliverable
36. 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.
Assumption
Process Map
Software/Systems Requirements Specification
Business Analysis
37. A prototype that is continuously modified and updated in response to feedback from users.
Business Requirements Document
Checklist
Evolutionary Prototype
Quality Assurance
38. 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
Defect
Analyst
Product
39. 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
User Requirements Document
Organization
Peer Review
Business Case
40. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.
Organization
Fishbone Diagram
Implementation Subject Matter Expert (SME)
Metric
41. A temporary endeavor undertaken to create a unique product service or result.
Project
Scope Model
Business Event
Monitoring
42. Assesses the effects that a proposed change will have on a stakeholder or stakeholder group project or system.
Inspection
Process Model
Impact Analysis
Enterprise
43. 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
Data Dictionary
Context Diagram
Scope
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.
Sponsor
Competitive Analysis
Business Policy
Operative Rule(s)
45. An error in requirements caused by incorrect incomplete missing or conflicting requirements.
Requirement(s) Defect
User Requirements Document
Scope
Iteration
46. A business model that shows the organizational context in terms of the relationships that exist among the organization external customers and providers.
Validation
Lessons Learned Process
Plan-driven Methodology
Relationship Map
47. A fixed period of time to accomplish a desired outcome.
Requirements Model
Dialog Hierarchy
Glossary
Timebox
48. A defined association between concepts classes or entities. Usually named and include the cardinality of the association.
Relationship
Vertical Prototype
Metric
User Acceptance Test
49. A brief statement or paragraph that describes the why what and who of the desired software product from a business point of view.
Focus Group
Vision Statement (product vision statement)
Benchmarking
Operational Support
50. A partial or preliminary version of the system.
Prototype
Requirements Package
Business Constraint(s)
Project Scope