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 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
Temporal Event
Requirements Risk Mitigation Strategy
Plan-driven Methodology
2. 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
Requirements Verification
Requirements Risk Mitigation Strategy
Prioritization
Decision Tables
3. The process of apportioning requirements to subsystems and components (i.e. people hardware and software).
Request For Quote (RFQ)
Timebox
User Story
Requirements Allocation
4. The process of examining new business opportunities to improve organizational performance.
Repository
Business Analysis Approach
Context Diagram
Opportunity Analysis
5. The set of capabilities a solution must deliver in order to meet the business need.
Elicitation
Stakeholder Requirement
Solution Scope
State Diagram
6. The product capabilities or things the product must do for its users.
Functional Requirement(s)
Vertical Prototype
Methodology
User Acceptance Test
7. The activities that control requirements development including requirements change control requirements attributes definition and requirements traceability.
Project Manager
Activity
Exploratory Prototype
Requirements Management
8. Something that occurs to which an organizational unit system or process must respond.
Attribute
Prioritization
Event
Request For Proposal (RFP)
9. A data element with a specified data type that describes information associated with a concept or entity.
Stakeholder
Requirements Model
Attribute
System
10. An error in requirements caused by incorrect incomplete missing or conflicting requirements.
Business Architecture
Requirements Signoff
Decision Tree
Requirement(s) Defect
11. The analysis technique used to describe roles responsibilities and reporting structures that exist within an organization.
Prototype
Quality
Organization Modeling
Scope Model
12. 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.
Domain
Verified Requirements
Analyst
Technical Constraint(s)
13. A condition or capability needed by a stakeholder to solve a problem or achieve an objective.
Swimlane
Product
Requirement
Customer
14. A measure of the profitability of a project or investment.
Operative Rule(s)
Change-driven Methodology
Return on Investment
Domain Subject Matter Expert (SME)
15. Influencing factors that are believed to be true but have not been confirmed to be accurate.
Assumption
Monitoring
Focus Group
Regulator
16. Identifies a specific numerical measurement that indicates progress toward achieving an impact output activity or input. See also metric.
Initiative
Indicator
Benchmarking
Interoperability
17. 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.
Throw-away Prototype
Product Backlog
Vertical Prototype
Evaluation
18. Ability of systems to communicate by exchanging data or services.
Decision Analysis
Interoperability
Root Cause Analysis
Peer Review
19. A description of an organization's business processes IT software and hardware people operations and projects and the relationships between them.
Enterprise Architecture
Requirements Verification
Requirements Package
Data Model
20. A state or condition the business must satisfy to reach its vision.
Product Backlog
Project
Business Goal
Work Breakdown Structure (WBS)
21. A real or virtual facility where all information on a specific topic is stored and is available for retrieval.
Product
Repository
Black Box Tests
Data Model
22. A target or metric that a person or organization seeks to meet in order to progress towards a goal.
Objective
Requirements Iteration
Requirements Management
Object Oriented Modeling
23. A means to elicit requirements by conducting an assessment of the stakeholder's work environment.
Code
Observation
Quality Attributes
End User
24. A document or collection of notes or diagrams used by the business analyst during the requirements development process.
Business Analysis Plan
Solution Scope
Decision Analysis
Work Product
25. A partial or preliminary version of the system.
Stakeholder List
Stakeholder
Validated Requirements
Prototype
26. A set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization. Are triggered by events and may have multiple possible outcomes. A successful outcome of a process will deliver value to one or more s
Business Requirements Document
Requirements Traceability
Business Process
Solution
27. A function of an organization that enables it to achieve a business goal or objective.
Tester
Return on Investment
User Story
Capability
28. A stakeholder with legal or governance authority over the solution or the process used to develop it.
Service
Span of Control
Regulator
Vision Statement (product vision statement)
29. A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components.
Requirements Allocation
Methodology
Decomposition
Non-functional Requirement(s)
30. 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.
Stakeholder Analysis
User
Regulator
Use Case
31. A type of data model that depicts information groups as classes.
Class Model
Glossary
Business Analysis
Stakeholder List
32. Any effort undertaken with a defined goal or objective.
Optionality
Decision Tables
Initiative
Non-functional Requirement(s)
33. A stakeholder with specific expertise in an aspect of the problem domain or potential solution alternatives or components.
Secondary Actor
Structural Rule
Stakeholder Requirement
Subject Matter Expert (SME)
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
Class
Design Constraints
Organization Modeling
Prioritization
35. A software tool that stores requirements information in a database captures requirements attributes and associations and facilitates requirements reporting.
Requirements Trace Matrix
Customer
Requirements Management Tool
Gap Analysis
36. A prototype that dives into the details of the interface functionality or both.
Vertical Prototype
Dialog Map
Organizational Process Asset
Implementation Subject Matter Expert (SME)
37. A group of related information to be stored by the system. Can be people roles places things organizations occurrences in time concepts or documents.
Service
Product Scope
Solution Scope
Data Entity
38. A means to elicit requirements of an existing system by studying available documentation and identifying relevant information.
Vertical Prototype
Business Analysis
Document Analysis
Activity
39. 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
Repository
Capability
Operative Rule(s)
40. An analysis model that describes a series of actions or tasks that respond to an event. Each is an instance of a use case.
Cardinality
Scenario
Elicitation
Organization
41. A system trigger that is initiated by time.
Business Domain Model
Temporal Event
Impact Analysis
Business Requirement
42. A group of related tasks that support a key function of business analysis.
Defect
Knowledge Area
Swimlane
Project Charter
43. A collection of interrelated elements that interact to achieve an objective. Elements can include hardware software and people.
Business Architecture
System
Event Response Table
Metric
44. 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.
Business Need(s)
Focus Group
Survey
Included Use Cases
45. A cohesive bundle of externally visible functionality that should align with business goals and objectives. Each is a logically related grouping of functional requirements or non-functional requirements described in broad strokes.
Feature
Enterprise Architecture
Object Oriented Modeling
Deliverable
46. An analysis model that shows user interface dialogs arranged as hierarchies.
Dialog Hierarchy
Business Policy
Transition Requirement(s)
Stakeholder List
47. Defining whether or not a relationship between entities in a data model is mandatory. Is shown on a data model with a special notation.
Objective
Optionality
Project Manager
Requirements Package
48. 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 Management Tool
Stakeholder Analysis
Requirements Traceability
Swimlane
49. 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.
Assumption
Product Scope
Requirement
Technical Constraint(s)
50. A non-actionable directive that supports a business goal.
Metric
Business Policy
User Story
Business Need(s)
Sorry!:) No result found.
Can you answer 50 questions in 15 minutes?
Let me suggest you:
Browse all subjects
Browse all tests
Most popular tests
Major Subjects
Tests & Exams
AP
CLEP
DSST
GRE
SAT
GMAT
Certifications
CISSP go to https://www.isc2.org/
PMP
ITIL
RHCE
MCTS
More...
IT Skills
Android Programming
Data Modeling
Objective C Programming
Basic Python Programming
Adobe Illustrator
More...
Business Skills
Advertising Techniques
Business Accounting Basics
Business Strategy
Human Resource Management
Marketing Basics
More...
Soft Skills
Body Language
People Skills
Public Speaking
Persuasion
Job Hunting And Resumes
More...
Vocabulary
GRE Vocab
SAT Vocab
TOEFL Essential Vocab
Basic English Words For All
Global Words You Should Know
Business English
More...
Languages
AP German Vocab
AP Latin Vocab
SAT Subject Test: French
Italian Survival
Norwegian Survival
More...
Engineering
Audio Engineering
Computer Science Engineering
Aerospace Engineering
Chemical Engineering
Structural Engineering
More...
Health Sciences
Basic Nursing Skills
Health Science Language Fundamentals
Veterinary Technology Medical Language
Cardiology
Clinical Surgery
More...
English
Grammar Fundamentals
Literary And Rhetorical Vocab
Elements Of Style Vocab
Introduction To English Major
Complete Advanced Sentences
Literature
Homonyms
More...
Math
Algebra Formulas
Basic Arithmetic: Measurements
Metric Conversions
Geometric Properties
Important Math Facts
Number Sense Vocab
Business Math
More...
Other Major Subjects
Science
Economics
History
Law
Performing-arts
Cooking
Logic & Reasoning
Trivia
Browse all subjects
Browse all tests
Most popular tests