Business Processes Mapping
Business Processes Mapping
Business Processes Mapping
Arun Chalise
Assessment Criteria Targeted
LO 1
Evaluate the interrelationship between the different processes and
functions of the organization.
Justify the methodology to be used to map processes to the
organizations goals and objectives.
Evaluate the output of the process and the quality gateways.
Process management
Process outputs
Quality gateways
Process measures
What is a Process?
A business process
has a goal
Has specific inputs and outputs
Use resources
Has number of activities performed in a order
May affect one or more functional unit
Creates value for the customer.
A business process
is a collection of linked tasks which find their end in the delivery of a
service or product to a client.
a set of activities and tasks that, once completed, will accomplish an
organizational goal.
The process must involve clearly defined inputs and a single output.
These inputs are made up of all of the factors which contribute (either
directly or indirectly) to the added value of a service or product.
These factors can be categorized into management processes,
operational processes and supporting business processes.
Business process
orientation
Output
Inputs Process step What gets
derived?
Where does it go?
Process mapping
is a workflow
diagram to bring
forth a clearer
understanding of a
process or series of
parallel processes.
Activity
Design a process map in a
work flow diagram for the
process you have defined
in the previous Class
Activity.
Processes
Example:
Sales Order Processing
Demand forecasting
Sales Operation Planning
Sales Invoice processing
New product Development
Raw Material Purchasing
A clear name
A description of what is requested
A purpose, giving the reasons why this is requested
A fit criterion, detailing how the requirement can be tested from a
customer point of view
A source, stating where this requirement comes from
A statement, from marketing, of the importance of the requirement
A project version, also from marketing
Quality Gateways in the Requirements
Process
Quality Gateways is not quality control
The steps to achieve good quality in
requirements definition include:
Elicitation-identifying the customer and user needs
Analysis- establishing an agreed set of requirements
and discovering conflicts, omissions, ambiguity,
overlapping and unrealistic requirements.
Representation-documenting individual
requirements. Specifications.
Validation- checking requirements for omissions,
conflicts and insuring that requirements follow
quality standards.
Figure: Quality Gateway Diagram 2.
Requirements document
(the output to the process)
Functional Requirements
Non-functional Requirements
Constraints
Process Outcomes
Customer satisfaction
Cost of process outcome per unit measure
Quantity of output
Reliability of quality of output
Manner of delivery output
Reliability of delivery of process outcome to define programme
Delivery of process outcome within the defined timescale
Success or failure of process
Quantity of rejects, cost of rework
Quantity of waste
Extent of containment of risk
Requirement
Must contain
Specifications Quality Gateways
-name
-description
-purpose
-criteria Gateway Process
-source Rejections
Checklist of
Returned to
quality attributes
source
Elicitation
Validation
Business Goals
Input to the
process
Requirement Documents
-Functional requirement define what the (Output to the process)
system will do Functional requirements
-Non functional requirements describe Non functional
system qualities like performance, security, requirements
political and legal requirement etc. Constraint
-Constraints are conditions that limit the
choices available like system constrain- eg.
window based.