Reading...
Play button
Play button
Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
197 Cards in this Set
- Front
- Back
|
Accuracy
|
Assessment of correctness
|
|
|
Agile
|
An adaptive approach that focuses on small pieces of a solution for analysis, design, development, and testing that allows for frequent, small releases of solution functionality based on feature priority
|
|
|
Analogous Estimating
|
A technique using past projects that are similar to forecast hours and/or costs. It is typically used in the early stages of a project when there may not be a great deal of information available
|
|
|
Assessment
|
A generic term to describe evaluating, analyzing, or estimating the quality or ability of someone or something
|
|
|
Three-point estimations
|
PERT or a simplement average of three estimates (optimistic, most likely, pessimistic), used to provide an estimate that reveals the range of uncertainty about activity duration or cost
|
|
|
Baseline
|
An established boundary of approved requirements against which requirements changes are compared. EAch time requirements are approved, they are baselined
|
|
|
Benchmarking (aka Research)
|
To compare organizational practices against the best-in-class practices that exists within competitor enterprises in government or industry
|
|
|
Bottom-up Estimating
|
Method of estimating duration or cost for the lowest-level components of the WBS and then aggregating or "rolling up" the individual estimates into higher levels
|
|
|
Business Analysis
|
The evaluation of an organization's needs - followed by the identification and management of requirements - to realize a solution.
|
|
|
What is discipline of working with stakeholders to define an organization's requirements in order to shape the output of projects and ensure that expected business benefits are realized?
|
Business Analysis
|
|
|
Research is another word for what technique?
|
Benchmarking
|
|
|
Benchmarking focuses on what?
|
Strategies, Operations, and Processes
|
|
|
Business Analyst
|
A person who conducts business analysis activities regardless of the job title or role
|
|
|
Business Case
|
A document that describes the necessary information from a business standpoint to determine whether or not the project is worth the investment
|
|
|
Business Opportunity
|
Describes an opportunity that will add value to the business
|
|
|
Business Problem
|
Describes a situation that is hindering a business from achieving maximum value
|
|
|
Business Requirement
|
Describes the higher-level needs of an organization and provides the rationale for a new project
|
|
|
Business Requirements including the following business items:
|
Goals and objectives, problems to be solved, opportunities to be exploited
|
|
|
Business Rule Catalog
|
A document containing a complete list of business rules and related attributes. The catalog can be used as reference for related requirements
|
|
|
Cause and Effect Diagram
|
A type of flowchart that helps organize thinking about a problem and diagnose cause and effect to discover root cause
|
|
|
What are some other terms for a Cause and Effect Diagram
|
Fishbone or Ishikawa Diagram
|
|
|
True or False: the Fishbone diagram can be used in conjunction with the Five Whys technique
|
True. It is often used in combination with this technique
|
|
|
Checksheet
|
Used to collect sampling results information about defects which then may be further analyzed using a Pareto diagram
|
|
|
Communication Plan
|
A component of the project, program, or portfolio management plan that describes how, when, and by whom information about the project will be administered and disseminated
|
|
|
Consensus Building
|
A general term for a group to generally agree. Many specific techniques may help lead to group consensus
|
|
|
Context Diagram
|
A diagram that shows the boundary of a system, the users, and the high-level data provided by the system and to the system
|
|
|
Users in a context diagram may be __ or __
|
Human or Other Systems
|
|
|
True or False: Context-diagrams only show a high-level view
|
True, but when supported by detailed data definition, it's an excellent tool for communicating part of the project scope to stakeholders
|
|
|
Contingency Planning
|
The outcome of analyzing the risks to a product and the planned response if the risk becomes a reality.
|
|
|
Contingency Planning may results in schedule and budget ___ by determining the likelihood and impact of a risk occurring
|
Reserves
|
|
|
How is reserve in contingency planning calculated?
|
Likelihood (%) * impact ($)
|
|
|
Control Chart
|
A chart used to determine whether or not a process is stable or has predictable performance (typically) over time by measuring output variables representing repetitive activities.
|
|
|
Control Charts can be used for both __ and __ life cycle processes.
|
Project and Product
|
|
|
Cost-benefit Analysis
|
The study of the cost versus the benefits that an organization will receive for a particular solution.
|
|
|
When is cost-benefit analysis useful?
|
When selecting projects for investment that will yield the greatest financial benefits for the organization
|
|
|
CRUD Matrix
|
A matrix used to cross check the data and processes to ensure a process is in place to create, read, update, and delete every entity.
|
|
|
A CRUD matrix can be used to help spot __
|
Gaps
|
|
|
What tool is useful for documenting user permissions in a system?
|
CRUD Matrix
|
|
|
Data Dictionary & Glossary
|
A document containing key items that are formally recorded to identify terminology and corresponding definitions used by the organization
|
|
|
What tool helps define data used or needed by an organization, including both high-level and more complex data definitions?
|
Data Dictionary & Glossary
|
|
|
Data Modeling
|
A model representing data structures, relationships between structures, and the detailed data attributes or facts within the structures.
|
|
|
What technique is used to document and communicate data requirements, either using an ERD or UML Class Diagram
|
Data Modeling
|
|
|
Day-in-the-Life (DITL) Testing
|
Testing conducted by someone knowledgeable in the business that focuses on specific scenarios in order to verify that the expected results are realized
|
|
|
Decision Table
|
A tool used to document business rules in a tabular format with a series of decisions and the outcomes. The table provides an easy way to document all factors that may impact the processing of a decision
|
|
|
What is DITL an acronym for?
|
Day-in-the-Life Testing
|
|
|
A decision table helps to __ the processing of business rules
|
Simplify
|
|
|
Decision Tree
|
Used to document complex business rules graphically in a hierarchical structure
|
|
|
True or False: Decision Trees may be used in combination with other models
|
True. Combined with a decision table, they enable analysis and documentation of complex business rules
|
|
|
Decomposition
|
Breaking down something that is higher-level, such as functional areas, their processes, or project deliverables - into simpler subsets for the purpose of studying or analyzing it
|
|
|
Decomposition is often depicted used __ models
|
Graphics
|
|
|
WBS is an example of what technique?
|
Decomposition
|
|
|
Delphi Technique
|
A way to gain consensus using expert opinion. Experts are asked to provide their opinions independently through a facilitator, who coordinates anonymous feedback through a questionnaire for responses until agreement is reached.
|
|
|
What is the Delphi Technique commonly used for?
|
Creating estimates or getting a recommendation on a decision to be made
|
|
|
Dependency Analysis
|
A techniques used to identify and clearly articulate dependences between two or more objects (e.g. requirements)
|
|
|
Dependency Graph
|
A graph that visually depicts dependencies in system requirements, functions, or components.
|
|
|
True or False: there is a single method for developing dependency graphs
|
False, there is no single method or process
|
|
|
Design of Experiments
|
Using statistical "What-if" scenarios to determine which combination of variables produces the best or desired quality outcome
|
|
|
What is unique about "Design of Experiments"?
|
It provides a tool for modifying multiple factors at the same time, rather than just one.
|
|
|
Design of Experiments it more typically used on the __ versus the __
|
Product, Project
|
|
|
Desk Checking
|
This is where the person who creates the deliverable reviews their own work prior to presenting it for formal quality control review
|
|
|
Document Analysis
|
To elicit requirements by studying available documentation on existing and comparable solutions and identifying relevant information
|
|
|
Estimation Poker (aka Planning Poker)
|
A technique primarily used by agile teams to estimate the effort for each user story
|
|
|
What are some methods of conducting estimation poker?
|
T-shirt sizing or Fibonacci sequence
|
|
|
Planning Poker estimates stories __ to one another
|
Relative
|
|
|
0,1,2,3,5,8,13 represents what sequence?
|
Fibonacci
|
|
|
Evaluation Criteria
|
Defined criteria that will be used for determining when a requirements, feature, or solution is acceptable for use
|
|
|
What is another term for evaluation criteria?
|
Acceptance Criteria
|
|
|
Events
|
The process of analyzing business events in order to determine organizational responses needed to support the business
|
|
|
External, Internal, and Time-based are examples of what?
|
Events
|
|
|
What are the types of "Events" in a business?
|
Internal, External, Time-based
|
|
|
Exploratory testing
|
TEsting conducted by someone knowledgeable of the business without a script.
|
|
|
What does exploratory testing provide?
|
Out-of-the-box testing for expanded test coverage
|
|
|
True or False: Exploratory testing is alternative to formal testing methods
|
False. Exploratory testing supplements formal testing, but should be done instead
|
|
|
Feasibility Analysis
|
An initial study to develop a recommendation on if a solution is viable to accomplish a desired outcome, whether it's to solve a problem or seize an opportunity
|
|
|
Feasibility Analysis may be used to compare multiple options to determine the most __
|
Feasible
|
|
|
Facilitated Workshop
|
A structured way to capture requirements. a workshop may be used to scope, discover, define, prioritize, and reach closure on requirements for the target system
|
|
|
Five Whys
|
A technique where the analyst asks "why is the problem occurring" up to five times to get to the root cause
|
|
|
Flowcharts
|
Graphical depiction of how the process flows from beginning to end to illustrate how components of the system are related
|
|
|
What do flowcharts help to analyze?
|
How problems occur and also to identify and highlight inefficiencies
|
|
|
Force Field Analysis
|
Analyzes the forces for and against a change, to help form a decision and communicate the reasoning behind the decision
|
|
|
Gap Analysis
|
A technique that businesses use to determine what steps need to be taken in order to move from its current state to desired future state.
|
|
|
What is another term for Gap Analysis?
|
Needs-gap Analysis, Needs analysis, and Needs Assessment are all alternative terms for Gap Analysis
|
|
|
Given-when-then
|
A tool used to articulate acceptance criteria
|
|
|
Goal
|
An observable and measurable end result having one or more objectives to be achieved within a more or less fixed timeline
|
|
|
Grade
|
In quality, category or rank used to distingue items that have the same functional use but do not share the same quality requirements
|
|
|
Histograms
|
Bar charts showing how often something occurs
|
|
|
Impact Analysis
|
Analysis of potential requirements or changes to determine impacts to other requirements, the product, or the project
|
|
|
Incremental
|
A hybrid of predictive and adaptive project approaches where a solution is developed and features released in increments or phases
|
|
|
Inspection
|
Examination or measurement of a deliverable in order to verify it meets requirements specifications
|
|
|
Integration Testing
|
Testing, conducted to ensure that requirements for the complete business processes have been satisfied
|
|
|
Integration testing focuses on _-__-_ business and includes all of the systems and interaction points within scope of the solution
|
End-to-End
|
|
|
Interoperability
|
Analysis to understand how applications communicate and collaborate with each other to complete a workflow or process
|
|
|
Interview
|
A systematic approach designed to elicit information from a person or group of people in an informal or formal setting by talking to an interviewee, asking relevant questions, and documenting the responses
|
|
|
Iterative
|
A common agile approach where release cycles are time-boxed in small time frame. Each iteration may introduce new features, rework of previously released features, or a combination of both.
|
|
|
Job Analysis
|
Review of job information for potential stakeholders in order to understand how the stakeholder roles and responsibilities fit within the organization in order to develop stakeholder management plans
|
|
|
Key Performance Indicators
|
Metrics that are defined to be used in evaluating progress towards meeting objectives or goals.
|
|
|
A metric is a __ level of indicate that an organization uses to measure progress at a specific point in time
|
Quantifiable
|
|
|
An indicator with a specific measurement that represents a degree of progress toward achieve a goal is called what?
|
KPI
|
|
|
Lean
|
A project approach that seseks to optimize efficiency by eliminating waste from activities and operations
|
|
|
Lessons Learned
|
Documenting knowledge gained during a project by facilitating team discussion of project successes, opportunities for improvement, failures, and recommendations for improving the performance of future projects or phases
|
|
|
Maslow's Hierarchy of Needs
|
"A Theory of Human Motivation" describes Maslow's ideas on human motivation as a hierarchy of needs.
|
|
|
We are motivated to seek the next level of __ once each level of the hierarchy has been met
|
Satisfaction
|
|
|
MoSCoW
|
A prioritization technique used to rate requirements or features using ratings of "Must Have", "Should Have", " Could Have", and "Won't Have" as it relates to project or release scope
|
|
|
Multi-voting
|
A prioritization technique where participants are given multiple votes for a variety of options on a specific issues. Participants may vote per option or multiple votes for a single item for added weight
|
|
|
Nominal Group Technique
|
A process that includes brainstorming to generate ideas. Voting or multi-voting is then used to rank the ideas in order to identify the most desirable options
|
|
|
Non-functional Requirements
|
Describe the required qualities of a system, such as its usability and performance characteristics. Important to use and development community.
|
|
|
Non-functional Requirements are important to who?
|
User and Development communities
|
|
|
Objective
|
Something to which work is to be directed in order for a strategic position to be attained, a purpose to be achieved, a result to be obtained, a product to be produced, or a service to be performed
|
|
|
Observation
|
A means of eliciting requirements by observing stakeholders completing activities within their work environment
|
|
|
Opportunity Analysis
|
Analysis of a potential opportunity to fully understand the feasibility and potential benefits
|
|
|
Options Analysis
|
Analyzing various options to understand the benefits, risks, and consequences of each in order to make a selection that will bring the greatest value to the project.
|
|
|
What technique relates to multi-criteria decision analysis?
|
Options Analysis
|
|
|
Organizational Chart
|
Describes the roles, responsibilities and reporting structures that exist within an organization and to align those structures with the organization's goals
|
|
|
Organizational Readiness
|
Analyzing the organization's readiness to accept and use a new solution. This goes beyond the technical implementation to the acceptance of the solution and organization preparedness to use it effectively
|
|
|
Parametric Estimating
|
The use of historical data in formulas or algorithms to extrapolate an estimate for a small amount of work to a large amount of work
|
|
|
What describes a mathematical model that predicts time or cost?
|
Parametric Estimating
|
|
|
Pareto Chart
|
Shows how many results were generated by type or category of identified cause. It identifies the "vital few" causes of most quality problems.
|
|
|
For the "vital few" identified in a Pareto Chart, solving those problems will do what?
|
Eliminate about 75-80 percent of the problems
|
|
|
Peer Review
|
A review process involving peers of the author or creation of the work being inspected in order to verify and improve upon quality
|
|
|
Personas
|
A tool used to understand the different user groups of a potential solution by assigning each role a "Persona".
|
|
|
How is a Persona used?
|
To tell a story about the users of that class, including information such as goals, behaviours, motivations, environment, demographics, and skills
|
|
|
Planguage
|
A set of closely defined identifiers (tags) to describe and quantify specific elements of the requirements
|
|
|
Precedence Diagramming Method
|
A technique used to construct a schedule model in which activities are represented by nodes and graphically linked by one or more logical relationships to show the sequence in which the activities are to be performed
|
|
|
Precision
|
A measure of exactness. May not be accurate, but can still be precise
|
|
|
Process Modeling
|
A technique for visually documenting work performed in an organization, including who does it and how they collaborate.
|
|
|
What are the types of models used to do process modeling?
|
- Process map- Swim Lane- Activity Diagram
|
|
|
Product Backlog
|
A stack-ranked prioritized list of user stories used to allocate work to iterations in agile projects
|
|
|
Progressive Elaboration
|
The process of analyzing a high-level requirement, feature, or estimate to decompose and document additional detail
|
|
|
Project Requirement
|
Describes actions, processes, or other condition the project needs to meet
|
|
|
Prototyping
|
A diagram detailing using interface requirements and integrates them with other requirements such as use cases, scenarios, and data and business rules
|
|
|
Purpose Alignment Model
|
A method for aligning business decisions, processes, and feature designs around purpose
|
|
|
Quadrant Analysis
|
A generic analysis tool where factors are measured on two axis to determine a "quadrant" for classification
|
|
|
What are some examples of "Quadrant Analysis"?
|
Power/Interest grid (in stakeholder management), or Likelihood/Penalty of defects when determining if a solution is "fit for use"
|
|
|
Quality
|
The degree to which a set of inherent characteristic fulfil requirements
|
|
|
Quality Requirement
|
Conditions or criteria needed to validate the successful completion of a project deliverable
|
|
|
Reporting Tools & Techniques
|
Tools and techniques used to trck and report project or activity status and progress
|
|
|
Requirement
|
"A condition or capability that is required to be present in a product, service, or result to satisfy a contract or other formally imposed condition."
|
|
|
Requirements Baseline
|
The list of requirements that have been formally aproved for continued work. Any changes to the requirements baseline will require formal approval throug hthe change congtrol process
|
|
|
Requirements Management Plan
|
A component of the project or program maangement plan that describes how requirements will be analyzed, documented, and managed
|
|
|
Requirements Management System
|
A tool that support collecting, analyzing, managing, and communicating requirements through a relational database
|
|
|
Requirements Traceability Matrix
|
A matrix used to trace requirements up to the supporting project and business goals of the organizzation and then down to the work product of the project team needed to satisfy the requirements
|
|
|
The requirements traceability matrix includes additional __ useful to tracking and manageing each requirement
|
Attributes
|
|
|
Retrospectives
|
A review process typically used in agile projects to review each iteration. Team members meet to identify and discuss the results of the latest iteration, what is working well, and identify opportunities and actions for improvement
|
|
|
Risk Analysis
|
The process of examining a program, project, or process for risk.
|
|
|
True or False: Risks are always negative
|
False. Risks may be either positive or negative
|
|
|
Scatter Diagram
|
Shows relationship or correlation between indpendent (X axis) and dependent (Y axis) variables.
|
|
|
Independent variables on scatter diagrams are also know as what?n
|
Inputs or Potential Causes
|
|
|
Depdent variables on scatter diagrams are also known as what?
|
Outputs or Effects
|
|
|
Scenario Analysis
|
Anaysis of how the system will be used, and thew interactions between users andt he system for various sitruations.
|
|
|
Scenario analysis works to capture when __ to the most common situation occur in order to better understand requirements for all scenarious
|
Variations
|
|
|
Service Level Agreement
|
An agreement detailing the nature, quality, and scope of service to be provided
|
|
|
Skills Assessment
|
A study of the skills and competencies of project stakeholders to allow for stakeholder management plans that leverage strengths and can accommodate wqeaknesses
|
|
|
Solution Requirement
|
Requirements that the solution must satisfy, including functional (behaviors of the producct) and non-fucntional (environment conditions) requirements
|
|
|
Environmental conditions needed are also known as what?
|
Non-functional Requirements
|
|
|
Behaviors of the product are known as what?
|
Functional
|
|
|
Solution Scope
|
Describes major features and functions included in the solution and the interactions it will have with people and systems outside its scope
|
|
|
Solution Scope Statement
|
A description of the solution scope, major deliverables, assumptions, and constraints
|
|
|
Stakeholer Register
|
A document containing information on all identified stakeholders in order
|
|
|
The stakeholder register includes information that is helpful in determining what?
|
Stakeholder Mangement Strategy
|
|
|
Stakeholder Requirement
|
States needs of stakeholders, specifically how stakeholders or classes of stakeholders will interact with a solution
|
|
|
State Diagrams and Tables
|
Either a tabular or visual specification of a sequence of states that an object goes through during its lifetime.
|
|
|
Statement of Work
|
Narrative description of products, services, or results to be delivered.
|
|
|
What elements should be included in a SOW?
|
Business Need, Product Scope Description, Strategic Plan
|
|
|
Statistical Sampling
|
A technique fwhere a small number of items representing a sample of the entire quantity are chosen for inspection.
|
|
|
Statistical Sampleing is used to do what?
|
Reduce the cost of quality rather than inspecting every item
|
|
|
Storyboarding
|
A prototyping technique using images and illustrations to show the sequence or navigation through a series of events.
|
|
|
In software development, how are storyboards often used?
|
To show navigation paths through web pages, screens, or interfaces
|
|
|
Storyboards are typically __-__ and __
|
Low-tech and Disposable
|
|
|
True or False: Storyboards are intended to illustrate the look and feel of the system
|
False. Storyboards should not include look and feel, but rather should focus on illustrating the experience
|
|
|
Strategic
|
Used durign planning to describe long-term plans or goals of what the organization or project strives to accomplish
|
|
|
Survey/Questionnaire
|
A means of eliciting informationi from many people, sometimes anonymously, in a relatively short period of tiem by preparing an dsending a set list of questions for response
|
|
|
SWOT Analysis
|
An analysis of the strengths, weakneeses, opportunitioes, and threats relating to a specific organization, project, or solution option
|
|
|
Tactical
|
Used in planning to describe the short-term plans or gaols that support organization or project strategy.
|
|
|
What tends to demonstrate the "how" of how strategies will be achieved?
|
Tactics
|
|
|
Test
|
The examination of a work product or deliverable in order to determine the level of quality
|
|
|
Time-boxing
|
A prioritization method where stakeholders are provided estimates for implementing requirements and the time available. Stakeholders select which requirements to include in teh "time-box"
|
|
|
Transition Requirement
|
Temporary capabilities, such as data conversion and training requirements, needed to transition from the "as-is" to the "to-be" state
|
|
|
Tuckman Model
|
A model of the stages of team development created by Bruce Tuckman. Stages are form, norm, perform, adjourn (mourn)
|
|
|
What is another name for the Tuckman Model?
|
Stages of Team Development
|
|
|
Use Case Diagram
|
A diagram used to summarize the scope of a solution by illustarting which use cases are in scope and which are out of scope for the system. It identifies the use cases and the actors who directly interact with the solution
|
|
|
Use Cases
|
Textual model detailing the interactions between system users (actors) and the solution undergoing development
|
|
|
Each use case focuses on a single user __
|
Goal (process)
|
|
|
How are boundaries stated in a use case?
|
By pre- and post-conditions
|
|
|
How are Use Cases usefl?
|
For uncovering solution functional requirements
|
|
|
User Acceptance Testing
|
Testing conducted by future end users of a solution at the direction of the BA and QA professionals in order to gain user acceptance that the solution is ready for implementation
|
|
|
In which type of testing is it usually scripted and observed by the BA/QA teams to ensure full coverage?
|
User Acceptance Testing (UAT)
|
|
|
User Journey Map
|
Documents the customer experience from the users' perspective to understand not only how users interact with teh solution, but can also identify improvement opportunities
|
|
|
User Story
|
A brief description of functionality that the users need from a solution to meet a business objective.
|
|
|
User stories serve as what type of requirements on adaptive projects?
|
Stakeholder Requirements
|
|
|
Value Engineering
|
An approach used to optimize project life cycle costs, save time, increase profits, improve quality, expand market share, solve problems, and/or use resources more effectively
|
|
|
Value Proposition
|
An anslysis of the value an organiation can expect to achieve as a result of the recommened solution.
|
|
|
From whose perspective are value propositions typically made?
|
Customer Perspective
|
|
|
Value Stream Mapping
|
A lean management method for analyzing the current state and designing a fture state for the series of events which take a product or service from its beginning through to the customer.
|
|
|
Waterfall
|
A predictive development/project appraoch where full planning and analysis is conducted early in the project life cycle, prior to any develoment
|
|
|
Weighted Criteria
|
An objective method of ranking or prioritizing options. Once options are defined then criteria for evaluating them are defined and weighted for relative importance; options are scored against each criterion and the score is multiplied by the weight of the criterion. Scores for each option are totaled, resulting in weighted criteria
|
|
|
Work Breakdown Structure
|
A hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables.
|
|
|
The WBS provides a __ view of work that has been __
|
Graphical, Decomposed
|
