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. Strengths Weaknesses Opportunities and Threats. It is a model used to understand influencing factors and how they may affect an initiative.
Defect
Requirements Management Plan
Span of Control
SWOT Analysis
2. The work to identify the stakeholders who may be impacted by a proposed initiative and assess their interests and likely participation.
Stakeholder Analysis
State Diagram
Object Oriented Modeling
Data Entity
3. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.
Decomposition
Lessons Learned Process
Validation
Requirements Management Plan
4. Alter the way a business analysis task is performed or describe a specific form the output of a task may take.
Technique
Operational Support
Constraint
Knowledge Area
5. A solution or component of a solution that is the result of a project.
Sequence Diagram
Domain Subject Matter Expert (SME)
Product
System
6. 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.
Structured Walkthrough
Quality Assurance
Event Response Table
User Requirements Document
7. The ability to identify and document the lineage of each requirement including its derivation (backward traceability) its allocation (forward traceability) and its relationship to other requirements.
Requirements Traceability
Survey
Process Map
Software/Systems Requirements Specification
8. The subset of nonfunctional requirements that describes properties of the software's operation development and deployment (e.g. performance security usability portability and testability).
Business Event
Class
Quality Attributes
User Requirements Document
9. A deliverable-oriented hierarchical decomposition of the work to be executed by the project team to accomplish the project objectives and create the required deliverables. It organizes and defines the total scope of the project.
Work Breakdown Structure (WBS)
Cardinality
Swimlane
State Diagram
10. 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.
Methodology
Vertical Prototype
Competitive Analysis
Business Process
11. 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.
Elicitation
Requirements Signoff
Use Case
Risk
12. 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.
Black Box Tests
Class Model
System
Feasibility Study
13. Work carried out or on behalf of others.
Project
Service
Event Response Table
Span of Control
14. The features and functions that characterize a product service or result.
Product Scope
Attribute
Vision Statement (product vision statement)
Constraint
15. A graphical representation of the entities relevant to a chosen problem domain the relationships between them and their attributes.
Entity-Relationship Diagram
Organization
Business Analysis Communication Plan
Sequence Diagram
16. A requirements document issued when an organization is seeking a formal proposal from vendors. Typically requires that the proposals be submitted following a specific process and using sealed bids which will be evaluated against a formal evaluation m
Assumption
Stakeholder Analysis
Request For Proposal (RFP)
Business Rule(s)
17. 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.
Customer
Black Box Tests
Organizational Process Asset
Walkthrough
18. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.
Solution Scope
Requirements Package
Iteration
Optionality
19. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.
Span of Control
Requirements Management
Cardinality
User Story
20. Requirements that have been demonstrated to deliver business value and to support the business goals and objectives.
Use Case Diagram
Validated Requirements
Change Control Board (CCB)
Class
21. A type of diagram defined by UML that captures all actors and use cases involved with a system or product.
Data Dictionary
Use Case Diagram
Iteration
Attribute
22. A list and definition of the business terms and concepts relevant to the solution being built or enhanced.
Business Requirements Document
Organizational Process Asset
User Story
Glossary
23. The set of processes templates and activities that will be used to perform business analysis in a specific context.
Business Domain Model
Data Model
Incremental Delivery
Business Analysis Approach
24. Influencing factors that are believed to be true but have not been confirmed to be accurate.
Business Architecture
Business Analysis Plan
Lessons Learned Process
Assumption
25. The work that must be performed to deliver a product service or result with the specified features and functions.
Commercial-off-the-Shelf Software (COTS)
Business Rule(s)
Project Scope
Interview
26. A function of an organization that enables it to achieve a business goal or objective.
Impact Analysis
Cardinality
Event Response Table
Capability
27. The number of employees a manger is directly (or indirectly) responsible for.
Business Requirement
Feasibility Study
Span of Control
Knowledge Area
28. An analysis model that provides a graphical alternative to decision tables by illustrating conditions and actions in sequence.
Attribute
Requirements Iteration
Use Case Diagram
Decision Tree
29. A quantifiable level of an indicator that an organization wants to accomplish at a specific point in time.
Metric
Change Control Board (CCB)
Checklist
Requirement(s) Defect
30. The human and nonhuman roles that interact with the system.
Model(s)
Organizational Process Asset
Stakeholder List
Actor(s)
31. 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.
Operational Support
Requirements Workshop
Business Event
Verified Requirements
32. A target or metric that a person or organization seeks to meet in order to progress towards a goal.
Objective
User
Change Control Board (CCB)
Cost Benefit Analysis
33. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.
Business Architecture
Regulator
Relationship
Repository
34. A stakeholder with legal or governance authority over the solution or the process used to develop it.
Benchmarking
Data Entity
Problem Statement
Regulator
35. A model that illustrates the flow of processes and/or complex use cases by showing each activity along with information flows and concurrent activities. Steps can be superimposed onto horizontal swimlanes for the roles that perform the steps.
Activity Diagram
Secondary Actor
Business Architecture
Quality Assurance
36. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).
Project Charter
Requirements Allocation
Object Oriented Modeling
Data Model
37. 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.
Data Entity
User Requirements Document
Force Field Analysis
Defect
38. The process of examining new business opportunities to improve organizational performance.
Desired Outcome
Business Analyst
Opportunity Analysis
System
39. Software developed and sold for a particular market.
Model(s)
Commercial-off-the-Shelf Software (COTS)
Metric
Force Field Analysis
40. A requirements document written primarily for Implementation SMEs describing functional and nonfunctional requirements.
Software/Systems Requirements Specification
Work Product
Requirements Iteration
Optionality
41. 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
Objective
Change-driven Methodology
Interface
42. A system trigger that is initiated by humans.
Process Map
Business Event
Requirements Validation
Functional Requirement(s)
43. A representation of requirements using text and diagrams. Can also be called user requirements models or analysis models and can supplement textual requirements specifications.
Inspection
Requirements Model
Requirements Iteration
Change Control Board (CCB)
44. An analysis of requirements-related risks that ranks risks and identifies actions to avoid or minimize those risks.
Business Constraint(s)
Requirements Workshop
Prototype
Requirements Risk Mitigation Strategy
45. The work done to evaluate requirements to ensure they are defined correctly and are at an acceptable level of quality. It ensures the requirements are sufficiently defined and structured so that the solution development team can use them in the desig
Plan-driven Methodology
Requirements Verification
Sponsor
Requirements Iteration
46. A measure of the profitability of a project or investment.
Root Cause Analysis
Functional Requirement(s)
Dialog Hierarchy
Return on Investment
47. A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract standard specification or other formally imposed documents.
Object Oriented Modeling
Organizational Readiness Assessment
Requirement
Requirements Management Tool
48. A stakeholder who uses products or services delivered by an organization.
Organizational Process Asset
Verification
Customer
Benchmarking
49. 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.
Requirements Model
End User
Horizontal Prototype
Product Backlog
50. The area covered by a particular activity or topic of interest.
Structural Rule
Enterprise Architecture
Document Analysis
Scope