Terms You Should Know Asa Business Analyst

Business analysis is the practice of enabling alter in the context of an enterprise by defining needs and recommending solutions that deliver value to stakeholders. Those that perform business organization assay are formally chosen business analysts only can as well be referred to every bit product owners, business systems analysts, production managers, system architects, process engineers, requirements engineers, projection managers or whatever other projection team member.

Developing stiff analytical skills is an effort that requires experience and training. Nonetheless, understanding the related linguistic communication, lingo and abbreviations doesn't have to be. Use this glossary every bit your comprehensive, go-to reference of terms that anyone performing business concern analysis should know.

A | B | C | D | E | F | G | H | I | J | K | Fifty | Grand | N | O | P | Q | R | S | T | U | Five | Due west | X | Y | Z

A

active listening

Listening is ane of the nearly important skills you can possess when performing interviews or other elicitation techniques. Active listening is a communication technique used in elicitation, team exercises, training, and conflict resolution. It requires that the listener fully concentrates, understands, responds, and then remembers what is being said. An active listener must be aware of listening filters and blockers, which are things that cause the listener not to receive the intended message.

activeness

Used interchangeably with the word "procedure".

histrion

Resource that actually interact with the system; a human, a device, or a system that plays some specified role in interacting with a solution; an actor is a UML component that represents a resource that interfaces with software. Actors are represented as stick figures in utilize-case diagrams.

adaptive approach

An approach where the solution evolves based on a bicycle of learning and discovery with feedback loops which encourage making decisions as late equally possible.

active

The ability of an organization to rapidly adapt to market and environmental changes in productive and cost-effective means; a style of project management wherein a tightly-knit, highly-skilled, collocated, and self-managed team of individuals follows a project from outset to finish and delivers the software quickly.

Agile Extension to the BABOK® Guide

A standard on the practise of business analysis in an Agile context. The Active Extension to the BABOK® Guide version 1 was published in 2013 by IIBA® in partnership with the Active Alliance.

agile manifesto

In 2001, 17 advocates of lightweight processes came together and drafted a certificate known as the Manifesto for Agile Software Development. According to the Manifesto, "Information technology emphasized the value of individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a programme."

ANSI (American National Standards Institute)

An organisation that has a set of standard workflow symbols. For a cheat sheet on the symbols used, come across our Unofficial Guide to Process Flow Chart Symbols.

architecture

The design, structure, and beliefs of the current and time to come states of a structure in terms of its components and the interaction betwixt those components. Besides meet: "business organization architecture", "enterprise architecture", and "requirements architecture".

artifact

Tangible production produced by the project. Examples: a model, a document, a source lawmaking, a requirement; whatsoever solution-relevant object, output, or representation that is created as role of business analysis efforts.

assumption

An influencing factor that is believed to exist true but has not been confirmed to be accurate; an influencing gene that could be true now just may not be true in the time to come.

attribute

A characteristic that further describes an entity; a data element.

automation purlieus

This is the limit of the solution to assist establish scope. A apply case diagram depicts the automation purlieus and defines the solution scope. See "employ case diagram".

B

behavioral business organization dominion

A business dominion that places an obligation (or prohibition) on conduct, action, do, or procedure; a concern dominion whose purpose is to shape (govern) twenty-four hours-to-day concern activity. Also known every bit an operative rule.

benchmarking

A comparing of a conclusion, a process, a service, or a organization'due south price, fourth dimension, quality, or other metrics to those of leading peers to identify opportunities for improvement; used to review products and/or services that are beingness delivered by your competitors. Also known every bit market analysis.

trunk of knowledge

The aggregated noesis and mostly accepted practices on a topic (i.e. BABOK, PMBOK^® Guide, SWEBOK).

BPM

Come across "concern process direction".

BPMN

See "business process modeling note".

brainstorming

A team activity that seeks to produce a broad or various set of options through the rapid and uncritical generation of ideas.

business organization (business world)

An economic system where any commercial, industrial, or professional activity is performed for turn a profit.

business analysis

The practice of enabling change in the context of an enterprise by defining needs and recommending solutions that deliver value to stakeholders.

business analysis arroyo

The set of processes, rules, guidelines, heuristics, and activities that are used to perform business analysis in a specific context.

business assay communication program

A clarification of the types of advice the concern analyst will perform during business organisation analysis, the recipients of those communications, and the form and frequency of those communications.

business analysis attempt

The scope of activities a concern analyst is engaged in during the life cycle of an initiative.

business analysis information

Any kind of information at any level of particular that is used as an input to concern analysis work or equally an output of business analysis work.

business analysis package

A document, presentation, or other collection of text, matrices, diagrams, and models representing business assay information.

business concern analysis program

A description of the planned activities the business organization analyst will execute in order to perform the business analysis piece of work involved in a specific initiative. As well encounter "requirements management plan".

business concern analyst

Any person who performs business analysis, no matter their job title or organizational role; a person who helps companies determine their objectives for meeting certain opportunities or addressing specific needs and then helps that company determine solutions and ways to run into those needs.

business organization architecture

The design, structure, and behavior of the current and future states of an enterprise to provide a common agreement of the arrangement. It is used to align the enterprise's strategic objectives and tactical demands.

business case

A justification for a class of activity based on the benefits to be realized by using the proposed solution, as compared to the cost, effort, and other considerations to acquire and live with that solution.

business organisation decision

A conclusion that can exist made based on strategy, executive judgment, consensus, and business concern rules, and that is generally fabricated in response to events or at divers points in a business concern process.

business concern drivers

The reasons a project is deemed important enough to fund, staff, and spend time on.

business goal

A state or condition that an system is seeking to constitute and maintain, usually expressed qualitatively rather than quantitatively.

business model

This describes a broad range of informal and formal models that are used by enterprises to represent various aspects of business organisation, including its purpose, offerings, strategies, infrastructure, organizational structures, and operational processes and policies.

business organization need

A problem or opportunity of strategic or tactical importance to exist addressed.

business objective

An objective, measurable outcome to indicate that a business goal has been achieved. SMART objectives are specific and measurable results the business wants delivered by the project; long-term operational or strategic goals of the project.

business concern policy

A non-practicable directive that controls and influences the actions of an enterprise.

business problem

An outcome of strategic or tactical importance preventing an enterprise or organization from achieving its goals.

business organisation process

An end-to-terminate set of activities which collectively responds to an event and transforms information, materials, and other resource into outputs that deliver value straight to the customers of the process. It may be internal to an arrangement, or information technology may span several organizations.

business organization process direction (BPM)

A management subject area that determines how manual and automated processes are created, modified, cancelled, and governed.

business procedure modeling notation (BPMN)

A graphical representation for specifying business processes in a workflow. For a cheat sheet on the symbols used, encounter our Unofficial Guide to Process Flow Chart Symbols.

business organisation process re-engineering

Rethinking and redesigning business organisation processes to generate improvements in performance measures.

business requirement

A representation of goals, objectives, and outcomes that describes why a change has been initiated and how success volition be assessed.

business risks

Potential problems that may impact the mission of the business area.

business concern dominion

A condition that governs the manner work is done; a specific, practicable, and testable directive that is under the command of the business and that serves as a criterion for guiding beliefs, shaping judgments, or making decisions.

concern use case

A primary purpose of the model of business use cases is to describe how the solution is or volition be used by its customers and users. It shows you how the thespian will interact with the system. A business utilise case may only indicate the "actor's actions" or it may include "the system responses". When the system responses are included, this is called a "systems utilize case".

business worker

A person who works within the concern area.

Dorsum to Superlative ↑

C

capability or capabilities

Activities that are in scope, describe core or essential work, and are independent of applied science; the fix of activities the enterprise performs, the knowledge it has, the products and services information technology provides, the functions it supports, and the methods it uses to make decisions.

crusade-and-effect diagram

Encounter "fishbone diagram".

change

The act of transformation in response to a need.

modify agent

One who is a catalyst for change.

alter control

Controlling changes to requirements and designs so that the impact of requested changes is understood and agreed upon before the changes are made.

change management

Planned activities, tools, and techniques to address the human side of alter during a change initiative, primarily addressing the needs of the people who will exist most afflicted by the alter.

modify strategy

A programme to movement from the electric current land to the futurity state to achieve the desired concern objectives.

change team

A cross-functional group of individuals who are mandated to implement a change. This group may be comprised of product owners, business analysts, developers, project managers, implementation subject thing experts, or any other individual with the relevant set of skills and competencies required to implement the change.

checklist (business organisation analysis)

A standard prepare of quality elements that reviewers employ for requirements verification.

kid procedure

A process that is a component of another process, its parent.

collaboration

The act of 2 or more people working together towards a common goal.

collaboration techniques

Brainstorming, requirements workshops, and collaborative games.

collaborative games

Structured techniques that are inspired by game-play to facilitate collaboration.

commercial off-the-shelf (COTS)

A prepackaged solution available in the market which addresses all or most of the common needs of a large group of buyers of those solutions. A commercial off-the-shelf solution may require some configuration to encounter the specific needs of the enterprise.

competitive analysis

A structured assessment which captures the key characteristics of an manufacture to predict the long-term profitability prospects and to determine the practices of the most meaning competitors.

component

A uniquely identifiable element of a larger whole that fulfills a articulate role. Encounter "context information catamenia diagram".

concept or conceptual model

An assay model that develops the meaning of core concepts for a problem domain, defines their collective structure, and specifies the appropriate vocabulary needed to communicate almost it consistently.

constraint

A constraint describes something in the electric current or future state that cannot exist changed, even if a specific situation or solution would do good by doing so.

constraint (concern analysis)

An influencing factor that cannot be changed, and that places a limit or restriction on a possible solution or solution option.

context

The circumstances that influence, are influenced by, and provide agreement of the modify.

context information menses diagram

A scoping diagram used to define the area of study for analysis.

core concept (concern analysis)

One of half dozen ideas that are fundamental to the practise of business analysis: change, need, Solution, context, stakeholder, and value.

price-benefit assay

An analysis which compares and quantifies the financial and non-financial costs of making a alter or implementing a solution compared to the benefits gained.

COTS

See "commercial off-the-shelf".

CRUD (Create, Read, Update and Delete)

The four basic functions of persistent data storage.

Crud matrix

A two-dimensional matrix showing which user roles accept permission to admission specific information entities, to create new records in those entities, to view the data in existing records, to update or alter the data in existing records, or to delete existing records. An alternate use of the CRUD matrix can be used to prove which processes, instead of users, have the permission to create, read, update and delete rights.

customer

A stakeholder who uses or may employ products or services produced by the enterprise and may have contractual or moral rights that the enterprise is obliged to come across.

D

information flow

A pipeline through which information or information flows. Shows how parties and systems collaborate with each other; an pointer on a data period diagram that represents a pipeline or path through which data flows. Also encounter "context data flow diagram".

information mining

Uses statistical assay techniques to discover patterns and relationships in big volumes of information. Can be descriptive, diagnostic, and predictive. Predicting future actions using data analysis.

information model

See "ERD".

data stores

Data at residue; information that is of import to the business surface area and will be retained or stored for some period of time.

data warehouse

A large shop of data accumulated from a wide range of sources inside a visitor and used to guide management decisions. Typically, in organizations they are computerized key repositories of integrated data from one or more disparate sources.

debate

An activity for discussing predetermined options or ideas, peculiarly if at that place are opposing viewpoints in the overall group.

decision analysis

An arroyo to controlling that examines and models the possible consequences of different decisions, and assists in making an optimal decision under atmospheric condition of uncertainty.

decomposition

A technique that subdivides a problem into its component parts in order to facilitate analysis and understanding of those components. Meet "functional decomposition diagram".

defect

A deficiency in a product or service that reduces its quality or varies from a desired attribute, state, or functionality.

definitional business organisation rule

A rule that indicates something is necessarily true (or untrue); a rule that is intended as a definitional criterion for concepts, noesis, or information. Also known as a structural rule.

deliverable

Any unique and verifiable piece of work product or service that a party has agreed to deliver.

dependencies

Relationships between tasks or projects. Example: Projection A may need Project B to be completely or partially performed before Project A can be successfully completed.

design

A usable representation of a solution.

design thinking

Creative problem solving with a human being-centered lens through co-cosmos, collaboration and by experiencing the world instead of talking most experiencing the globe.

document assay

An examination of the documentation of an existing organization in order to arm-twist requirements. The process of reviewing existing documents or systems related to the project: reports, letters, screen layouts, brochures, etc.

domain

The sphere of cognition that defines a ready of common requirements, terminology, and functionality for any plan or initiative solving a problem.

domain subject matter good (SME)

A stakeholder with in-depth knowledge of a topic relevant to the business concern need or solution scope.

DSDM (dynamic systems development method)

A project commitment framework which focuses on fixing cost, quality, and time at the beginning while contingency is managed by varying the features to be delivered.

Back to Pinnacle ↑

E

elicitation

Iterative derivation and extraction of data from stakeholders or other sources. A more than intentional set of tasks than simple requirements gathering. Receiving of information from stakeholders or other resources. The main path to discovering requirements and design information.

elicitation plan

A plan for eliciting requirements to help determine what you need to know, where you tin go that information, and what elicitation technique will work best. Get more than on how to develop your plan.

end user

A stakeholder who directly interacts with the solution.

enterprise

A system of one or more organizations and the solutions they use to pursue a shared set of common goals.

enterprise compages

A clarification of the business processes, information technology, people, operations, information, and projects of an enterprise and the relationships between them.

enterprise readiness assessment

An assessment that describes if the enterprise is prepared to accept the alter associated with a solution and is able to use information technology effectively.

entity

A data modeling component that represents a course of things that the business concern surface area wants to continue information about. Run into "ERD (entity-relationship diagram)".

epic

A big user story; effectively a description of a product feature that cannot be delivered every bit defined within an iteration and is therefore too big to exist estimated.

ERD (entity-relationship diagram)

A graphical representation of the entities relevant to a chosen trouble domain and the relationships between them. A standard technique for documenting data requirements.

essential procedure

See "process, essential" and "capabilities".

estimate

A quantitative cess of a planned event, resource requirements, and schedule where uncertainties and unknowns are systematically factored into the assessment.

evaluation

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. Also run into "indicator", "metric", and "monitoring".

result

An occurrence or incident to which an organizational unit, system, or process must respond. Requirements can be based on upshot-driven activities; an occurrence exterior the scope of the business expanse that requires a response from the concern expanse.

consequence response

A process that is washed past the business concern area in response to an event.

evolutionary prototype

A epitome that is continuously modified and updated in response to feedback from stakeholders.

experiment

Elicitation performed in a controlled manner to make a discovery, exam a hypothesis, or demonstrate a known fact.

external agent

An external agent is a person, organization, or organization with whom the business concern surface area interacts. See "context information flow diagram".

external interface

An interaction that is outside the proposed solution. It can be another hardware organization, software organisation, or a human interaction with which the proposed solution will interact.

F

facilitation

The art of leading and encouraging people through systematic efforts toward agreed-upon objectives in a fashion that enhances involvement, collaboration, productivity, and synergy.

feasibility study

An evaluation of proposed alternatives to make up one's mind if they are technically, organizationally, and economically possible within the constraints of the enterprise, and whether they will deliver the desired benefits to the enterprise.

feature

A distinguishing characteristic of a solution that implements a cohesive gear up of requirements and which delivers value for a gear up of stakeholders; a product capability that provides value to the customer.

fishbone diagram

A diagramming technique used in root cause analysis to identify underlying causes of an observed problem, and the relationships that exist between those causes. Also known as an Ishikawa or cause-and-effect diagram

menstruum chart

Used commonly with non-technical audiences and are skillful for gaining both alignment with what the process is and context for a solution. A catamenia chart tin be simple, displaying just the sequence of activities, or it can be more comprehensive, using "swimlanes".

focus group

A group formed to elicit ideas and attitudes nearly a specific product, service, or opportunity in an interactive group environment. The participants share their impressions, preferences, and needs; guided by a moderator.

force field analysis

A graphical method for depicting the forces that support and oppose a change.

functional decomposition diagram

Used to graphically depict decomposition.

functional requirement

A capability that a solution must have in terms of the behavior and information the solution will manage.

G

gap analysis

A comparison of the current state and desired future state of an enterprise in lodge to identify differences that demand to be addressed.

goal

See "business organization goal".

governance procedure (change)

A process by which appropriate conclusion makers use relevant data to make decisions regarding a change or solution, including the means for obtaining approvals and priorities.

guideline (business analysis)

An education or clarification on why or how to undertake a task.

Back to Tiptop ↑

H

loftier level processes

A high-level summary of key processes; frequently used to help analyze scope. Too see "capabilities".

horizontal paradigm

A prototype that is used to explore requirements and designs at ane level of a proposed solution, such as the customer-facing view or the interface to another organization.

I

IIBA

See "International Institute of Business organization Analysis".

impact analysis

An assessment of the effects a proposed change volition accept on a stakeholder or stakeholder group, project, or system.

implementation field of study matter expert (SME)

A stakeholder who has specialized cognition regarding the implementation of one or more solution components.

indicator

A specific numerical measurement that indicates progress toward achieving an touch, output, activity, or input. Also meet "metric".

initiative

A specific project, program, or action taken to solve some business organisation problem(s) or achieve some specific alter objective(south).

input (concern analysis)

Information consumed or transformed to produce an output. An input is the information necessary for a task to begin.

inspection

A formal review of a work product by qualified individuals that follows a predefined process and uses predefined criteria for defect identification and removal.

interface

A shared boundary betwixt whatever 2 persons and/or systems through which information is communicated.

International Institute of Business concern Analysis (IIBA)

An association for business analysts.

interoperability

Ability of systems to communicate by exchanging information or services.

interview

Eliciting information from a person or grouping of people in an informal or formal setting by request relevant questions and recording the responses; well-nigh appropriate for eliciting requirements with one or two individuals at a time.

IRACIS

Increase Revenue, Avoid Costs, Better Service. This is what the concern is trying to accomplish through the results of the initiative.

Ishikawa diagram

See "fishbone diagram".

iteration (business organization analysis)

A single instance of progressive cycles of analysis, development, testing, or execution.

iterative methodology

Iterative approaches plan and scope the projection at the outset and then iterate the assay, design, and structure phases until the system is ready for implementation.

J

Back to Superlative ↑

K

cognition area

An surface area of expertise that includes several specific business analysis tasks.

Back to Height ↑

L

lessons learned process

A technique used to learn about and improve on a process or project. A lessons learned session involves a special meeting in which the squad explores what worked, what didn't piece of work, what could be learned from the merely-completed iteration, and how to adapt processes and techniques before standing or starting anew.

life bicycle

A series of changes an item or object undergoes from inception to retirement.

Dorsum to Top ↑

M

manifesto

A public proclamation of principles, policies, or intentions, specially of a political nature. It comes from the Latin wordmanifestus, which means "articulate or evident".

matrix

A textual form of modelling used to represent information that can exist categorized, cross-referenced, and represented in a table format.

metadata

A description of data to help understand how to use that information, either in terms of the construction and specification of the data, or the description of a specific instance of an object.

methodology

A body of methods, techniques, procedures, working concepts, and rules used to solve a problem. The major methodologies include "waterfall", "iterative", object oriented ("UML"), and "agile".

metric

A quantifiable level of an indicator measured at a specified bespeak in time.

mission argument

A formal proclamation of values and goals that expresses the core purpose of the enterprise.

listen mapping

A artistic ways of recording and organizing thoughts that literally "maps out" an idea in a non-linear diagram.

model

A representation and simplification of reality developed to convey information to a specific audition to support analysis, communication, and understanding.

modeling

Circuitous software designs that would be hard to describe textually can readily exist conveyed through multi-dimensional diagrams, known as models. Modeling provides three central benefits: visualization, complication direction, and clear communication.

monitoring

Collecting data on a continuous basis from a solution in social club to decide how well a solution is implemented compared to expected results. Also run into "metric" and "indicator".

Dorsum to Pinnacle ↑

Due north

need

A problem or opportunity to exist addressed.

non-functional requirement

A type of requirement that describes the performance or quality attributes a solution must meet. Not-functional requirements are usually measurable and human activity as constraints on the design of a solution every bit a whole. Example: "99% of users will be able to log in and view their account rest without requiring aid."

Dorsum to Acme ↑

O

objective

See "business objective".

ascertainment

Studying and analyzing i or more stakeholders in their piece of work surround in order to elicit requirements; using sight or experience to review an activity or system. There are two means to find: active/noticeable and passive/unnoticeable.

OLAP (online analytical processing)

A business intelligence approach that allows users to analyze large amounts of data from different points of view.

operational support

A stakeholder who is responsible for the solar day-to-day management and maintenance of a organisation or product.

operative rule

Encounter "behavioral business rule".

organization

An autonomous grouping of people, under the management of a unmarried private or board, that works toward mutual goals and objectives.

organizational capability

A office inside the enterprise, made up of components such as processes, technologies, and information, used by organizations to accomplish their goals.

organizational change management

See "alter management".

organizational unit

Any recognized association of people within an organization or enterprise.

organization modelling

The analysis technique used to depict roles, responsibilities, and reporting structures that exist within an enterprise.

P

paraphrasing

Involves restating to the speaker, in your own words, what you believe is the essence of what has just been said.

parent process

A process that is decomposed into two or more child processes. See "functional decomposition diagram".

peer review

A formal or informal review of a work product to identify errors or opportunities for improvement. Also see "inspection".

plan

A detailed scheme for doing or achieving something; commonly comprised of a set of events, dependencies, an expected sequence, a schedule, results or outcomes, materials and resources needed, and how stakeholders need to exist involved. A piece of work breakdown structure is typically used.

policy

See "business concern policy".

postconditions

What happens after the process completes (both successful and unsuccessful completions).

preconditions

What needs to exist in identify earlier the process tin start.

predictive approach

An approach where planning and baselines are established early in the life bike of the initiative in order to maximize control and minimize risk.

prioritization

Determining the relative importance of a set of items in order to determine the order in which they will exist addressed.

trouble argument

A clear, curtailed clarification of the issue(s) that need(s) to be addressed by a problem-solving team. Information technology is used to eye and focus the squad at the beginning, keep the squad on runway during the effort, and is used to validate that the endeavour delivered an outcome that solves the problem argument.

procedure

A detailed, step-by-step clarification of how a procedure is accomplished; procedures commonly contain a transmission (non automated) component.

process

A business activity that transforms information; information technology has a distinct beginning and end; a process may exist loftier-level or detailed; an activity performed by the business organisation that transforms information (information); a set up of activities designed to reach a specific objective by taking 1 or more defined inputs and turning them into defined outputs.

process, essential

A process that is performed within the scope of the project; describes the core or essential work being done by the business area; essential processes are described independently of current or future applied science. Also referred to every bit "capability".

procedure model

A fix of diagrams and supporting information about a process and factors that could influence the process. Some process models are used to simulate the performance of the procedure.

product (concern analysis)

A solution or component of a solution that is the result of an initiative.

product backlog

A gear up of user stories, requirements, or features that accept been identified every bit candidates for potential implementation and have been prioritized and estimated.

production scope

Run into "solution scope".

product vision statement

A brief statement or paragraph that describes the goals of the solution and how it supports the strategy of the organization or enterprise. Can be defined using a vision box or text.

project

A temporary endeavor undertaken to create a unique product, service, or upshot.

projection direction

The application of cognition, skills, tools, and techniques to project activities to meet the project requirements. The bodily handling of the project which is resultant from the BA'south work of elicitation and clarification of scope. Projection management handles the programme, the scope, and the deliverables; the discipline of initiating, planning, executing, decision-making, and endmost the work of a squad to attain specific goals and run into specific success criteria.

projection manager

A stakeholder who is responsible for managing the work required to evangelize a solution that meets a business need. He or she is also responsible for ensuring that the project's objectives are met while balancing the project constraints including scope, budget, schedule, resources, quality, and take a chance.

project risks

An uncertain event or status that, if information technology occurs, has a positive or negative effect on ane or more projection objectives.

project scope

The work that must exist performed to evangelize a product, service, or issue with the specified features and functions.

proof of concept

A model created to validate the design of a solution without modelling the appearance, materials used in the creation of work, or processes and workflows ultimately used by the stakeholders.

prototype

A partial or simulated approximation of the solution for the purpose of eliciting or verifying requirements with stakeholders.

Back to Elevation ↑

Q

quality

The caste to which a set of inherent characteristics fulfills needs.

quality balls

A set of activities performed to ensure that a procedure will deliver products that encounter an appropriate level of quality.

quality attributes

A set of measures used to judge the overall quality of a organization. Also see "not-functional requirements".

questionnaire

A set of divers questions with a choice of answers used to collect information from respondents; the use of questions to gather data verbally, on paper, or electronically; often used in "surveys".

Dorsum to Height ↑

R

RACI (responsible, accountable, consulted, and informed) matrix

A tool used to identify the responsibilities of roles or squad members and the activities or deliverables in which they will participate by being responsible (doing the work), accountable (approving the results), consulted (providing input), or informed of the completed item after information technology has been completed.

regulator

A stakeholder from outside the organization who is responsible for the definition and enforcement of standards.

relationship

Every bit related to utilise cases, information technology shows which actors are involved with each utilise case; shows an association from i entity to another; represents a business rule.

repository

A real or virtual facility where all information on a specific topic is stored and is available for retrieval.

asking for data (RFI)

A formal elicitation method intended to collect data regarding a vendor's capabilities or whatever other information relevant to a potential upcoming procurement.

request for proposal (RFP)

A requirements document issued when an organization is seeking a formal proposal from vendors. An RFP typically requires that the proposals be submitted post-obit a specific process and using sealed bids which will be evaluated against a formal evaluation methodology.

asking for quote (RFQ)

A procurement method of soliciting price and solution options from vendors.

request for tender (RFT)

An open invitation to vendors to submit a proposal for goods or services.

requirement

A usable representation of a need; could exist in the form of text, a diagram, a nautical chart, a table, a model or a paradigm; a condition or capability needed by a stakeholder to solve a problem or accomplish an objective.

requirements allocation

The process of assigning requirements to be implemented by specific solution components.

requirements architecture

The requirements of an initiative and the interrelationships between these requirements.

requirements artifact

A business analysis antiquity containing information about requirements such as a diagram, a matrix, a document or a model.

requirements attribute

A characteristic or holding of a requirement used to help with requirements management.

requirements defect

A problem or error in a requirement. Defects may occur because a requirement is of poor quality (run into "requirements verification") or because it does not describe a need that, if met, would provide value to stakeholders (meet "requirements validation").

requirements certificate

Run into "requirements packet".

requirements life cycle

The stages through which a requirement progresses from inception to retirement.

requirements management

Planning, executing, monitoring, and controlling whatever or all of the work associated with requirements elicitation and collaboration, requirements analysis and design, and requirements life cycle management.

requirements direction programme

A subset of the business assay plan for a specific change initiative describing specific tools, activities, roles, and responsibilities that will exist used on the initiative to manage the requirements. Meet "business concern assay program".

requirements management tool

Special-purpose software that provides support for whatsoever combination of the following capabilities: elicitation and collaboration, requirements modelling and/or specification, requirements traceability, versioning and baselining, attribute definition for tracking and monitoring, document generation, and requirements change command.

requirements model

An abstract (ordinarily graphical) representation of some aspect of the current or future state.

requirements package

A specialized form of a concern analysis package primarily concerned with requirements. A requirements package may represent a baseline of a collection of requirements.

requirements traceability

The power for tracking the relationships between sets of requirements and designs from the original stakeholder demand to the actual implemented solution. Traceability supports change control by ensuring that the source of a requirement or pattern can exist identified and that other related requirements and designs potentially affected by a modify are known.

requirements validation

Piece of work done to evaluate requirements to ensure they back up the commitment of the expected benefits and are within the solution scope.

requirements verification

Work done to evaluate requirements to ensure that 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 tin utilize them in the design, development, and implementation of the solution.

requirements workshop

A highly structured, intensive workshop to achieve a goal; a coming together in which a advisedly selected grouping of stakeholders collaborates to define and/or refine requirements nether the guidance of a skilled neutral facilitator. Also called a "facilitated session".

research-based techniques

Benchmarking and market analysis, information mining, document analysis, and survey/questionnaire

residual risk

The run a risk remaining later action has been taken or plans have been put in place to bargain with the original risk.

response cards

Tin be used to encourage all participants to provide input. Useful in situations where there is a disagreement or conflict in a group.

retrospective (agile)

A meeting that is held at the stop of an iteration in an Active Scrum approach. During the retrospective, the team reflects on what happened in the iteration and how well the squad members worked together, and they place deportment for improvement going forward.

return on investment (ROI) (business concern assay)

A measure of the profitability of a project or investment.

opposite brainstorming

Reverse brainstorming takes an opposite viewpoint.

gamble (business analysis)

The effect of uncertainty on the value of a change, a solution, or the enterprise. Also run into "remainder risk".

run a risk assay

Factors of concern with risk: probability, likelihood the upshot will occur, impact or consequence, and blazon and extent of 'pain' acquired.

chance cess

Identifying, analyzing, and evaluating risks.

ROI

See "return on investment".

root cause

The cause of a problem having no deeper cause, usually one of several possible causes.

root cause assay

A structured examination of an identified problem to understand the underlying causes.

S

scope

The boundaries of command, alter, a solution, or a need.

secondary actor

An actor external to the system nether design that supports the execution of a use case.

sequence diagram

A type of diagram that shows objects participating in interactions and the messages exchanged between them.

service

The performance of any duties or work for a stakeholder, from the perspective of the stakeholder.

silence

Refraining from speaking or making noise. Tin be a powerful communication tool used for facilitating a group of people. Silence can be used when someone has shared a large amount of information or there is a lot of tension or emotions in a facilitated session.

SIPOC (suppliers, inputs, procedure, outputs, and customers)

A tool used to describe relevant high-level elements of a procedure. May be used in conjunction with process mapping and "in/out of scope" tools to provide boosted detail.

SMART objectives

Objectives that areSpecific,Measurable,Achievable,Relevant, andTime-bound.

SME

Bailiwick affair skilful. Run into "domain subject matter adept" and "implementation subject matter expert".

solution

A specific manner of satisfying one or more needs in a context.

solution component

A sub-function of a solution that can be people, infrastructure, hardware, software, equipment, facilities, and process assets or whatever combination of these sub-parts.

solution life cycle

The stages through which a solution progresses from inception to retirement.

solution option

One possible manner to satisfy one or more needs in a context.

solution requirement

A capability or quality of a solution that meets the stakeholder requirements. Solution requirements can be divided into two parts: functional requirements and not-functional or quality of service requirements.

solution scope

The set of capabilities a solution must deliver in order to meet the business need.

SOW

Meet "argument of piece of work".

sponsor

A stakeholder who is responsible for initiating the effort to define a business demand and develop a solution that meets that need. Sponsors qualify the work to be performed and control the upkeep and scope for the initiative.

stakeholder

A group or individual with a relationship to the change, the demand, or the solution.

stakeholder analysis

Identifying and analyzing the stakeholders who may exist impacted by the alter, and assessing their bear upon, participation, and needs throughout the business analysis activities.

stakeholder list

A catalogue of the stakeholders affected by a change, a business need, or a proposed solution, and a description of their attributes and characteristics related to their involvement in the initiative.

stakeholder proxy (business analyst)

The role a business concern annotator takes when representing the needs of a stakeholder or stakeholder group.

stakeholder requirement

A description of the needs of a detail stakeholder or course of stakeholders that must be met in order to accomplish the business organization requirements. They may serve as a bridge between business requirements and the various categories of solution requirements.

state diagram

A state diagram is an analysis model showing the life cycle of a information entity or class.

stated requirement

A requirement articulated by a stakeholder that has non been analyzed, verified, or validated. Stated requirements frequently reflect the desires of a stakeholder rather than the bodily demand.

argument of work (SOW)

A written description of the services or tasks that are required to exist performed.

strategy

A description of the chosen arroyo to apply the capabilities of an enterprise in lodge to reach a desired set of goals or objectives.

strategy analysis

Provides a context for the project. May also provide an initial description of the project, which is necessary for developing telescopic.

structural rule

See "definitional business organization dominion".

subject matter proficient (SME)

See "domain subject thing practiced" and "implementation subject matter expert".

supplier

A stakeholder outside the boundary of a given organization or organizational unit of measurement who provides products or services to the organization and may have contractual or moral rights and obligations that must be considered.

survey

Collecting data on a certain topic, typically the opinions or experiences of a group of people. This can exist done through multiple information collection methods, including questionnaires, observation, and inquiry. Likewise see "questionnaire".

swimlane

A horizontal or vertical section of a procedure diagram that shows which activities are performed past a detail actor or function.

SWOT (strengths, weaknesses, opportunities, and threats) analysis

An assay model used to understand influencing factors and how they may affect an initiative.

system

A prepare of interdependent components that interact in various ways to produce a set of desired outcomes.

systems development life bicycle (SDLC)

Encounter "lifecycle".

Back to Acme ↑

T

task (business analysis)

A discrete piece of work that may be performed formally or informally every bit role of business organisation analysis.

technique

A style, method, or style for conducting a business analysis job or for shaping its output.

temporal event

An event based on time that can trigger the initiation of a procedure, evaluation of business organization rules, or some other response.

tester

An individual responsible for determining how to verify that the solution meets the requirements defined by the business annotator and for conducting the verification process.

theme

An aggregation of user stories to show business value delivered, to help with prioritization, and to show planned product commitment at a high level.

throw-abroad prototype

A prototype used to quickly uncover and clarify requirements or designs using simple tools (sometimes only paper and pencil). Information technology is intended to be discarded when the terminal system has been developed.

time-box

An agreed-upon catamenia of time in which an activity is conducted or a defined deliverable is intended to be produced.

traceability

See "requirements traceability".

transition requirement

A requirement that describes the capabilities that the solution must accept and the conditions that the solution must meet to facilitate transition from the current state to the hereafter state, but which are non needed one time the change is complete. They are different from other requirements types considering they are of a temporary nature.

Dorsum to Top ↑

U

UML® (unified modelling linguistic communication™)

A notation specified by the Object Direction Group for describing software application construction, beliefs, and compages. It can also exist used for describing business organisation processes and data structures. The about common UML® diagrams used by business analysts are utilize example diagrams, activity diagrams, state machine diagrams (as well known every bit "state diagrams"), and class diagrams. For a crook sail on the symbols used, see our Unofficial Guide to Process Flow Chart Symbols.

use case

A description of the observable interaction between an actor (or actors) and a solution that occurs when the actor uses the system to accomplish a specific goal. See "use case diagram".

utilise case description

Describes in detail the expected software functionality; footstep-by-step description of how a utilize example will be accomplished in the automated system.

apply case diagram

A type of diagram defined past UML® that captures all actors and employ cases involved with a organization or production; shows those actors that play a part in the system and what activities they may do.

use example model

Consists of a diagram and a narrative to explain user/software interactions.

user

Run across "terminate user".

user credence test (UAT)

Assessing whether the delivered solution meets the needs of the stakeholder group that will be using the solution. The cess is validated against identified credence criteria.

user interface (UI)

Visual part of computer application or operating organization through which a use interacts with a computer or software.

user requirement

See "stakeholder requirement".

user story

A description of a product feature used for planning and scoping purposes. User stories will exist decomposed to a level that can exist delivered in a unmarried iteration and tin can provide value; a quick way to sympathise the desired functionality of a user feel; a modest, concise statement of functionality or quality needed to deliver value to a specific stakeholder.

Back to Pinnacle ↑

V

validated requirement

A requirement that has been reviewed, has been adamant to support the delivery of the expected benefits, and is within the solution scope.

validation (business analysis)

The process of checking that a deliverable is suitable for its intended use. Also run into "requirements validation".

value (business concern analysis)

The worth, importance, or usefulness of something to a stakeholder in a context.

value stream mapping

A complete, fact-based, fourth dimension-serial representation of the stream of activities required to evangelize a production or service.

verification (business organization analysis)

The process of determining that a deliverable or artifact meets an adequate standard of quality. Besides see "requirements verification".

Dorsum to Top ↑

Due west

waterfall methodology

Waterfall is a evolution methodology that is also referred to as the traditional approach. It is a linear approach to software development. Work is washed in phases, where one stage doesn't start until the previous phase is completed.

walkthrough

A review in which participants stride through an artifact or gear up of artifacts with the intention of validating the requirements or designs, as well as to identify requirements or blueprint errors, inconsistencies, omissions, inaccuracies, or conflicts.

wireframe

Run across "prototype".

piece of work breakdown structure (WBS)

A deliverable-oriented hierarchical decomposition of the piece of work to be executed to accomplish objectives and to create the required deliverables. It organizes and defines the total scope of the projection; a structured presentation of the tasks and deliverables required to complete a project.

work product (business analysis)

A certificate or collection of notes or diagrams used by the business concern analyst during the requirements development process.

workflow

Run into "flow nautical chart".

Back to Height ↑

X

Y

Z

[dcb id=41240]

malleymottee.blogspot.com

Source: https://netmind.net/en/business-analysis-glossary/