Business Process Improvement


Why you should choose

Business Process Improvement


The emphasis of this Business Process Improvement course is on the gathering, specifying and designing Business Processes, so that we do not create faster, bad processes.  Business Process Improvement (BPI), Business Process Re-engineering (BPR) and Business Process Management concepts are discussed; debated and practical applications of these disciplines are covered. Systematic, top-down techniquesare used to study and decompose a Business Area. The delegate is taken through the four stages possible for analysis i.e. as is design, as is analysis, new analysis and new design.  Various tools and techniques are introduced based on a business process engineering methodology.  Upon completion the delegate will be in position to choose the right tool for the right job.  This is a technical business course.


Business Analysts, Process Engineers, Product Developers or any information systems or business professionals actively involved in designing and developing business processes.  No Information Technology (IT) experience is required.


At least one year of working experience either from a business or systems development perspective.


Self Study


After completing this course the delegate will be able to:

  • Start analysing in a structured approach and know what deliverables are required i.e. Process models, process specifications, and the data dictionary.
  • Which models are the most appropriate to use, flow charts, data flow diagrams (DFD), entity relationship diagrams (ERD), functional decomposition, object orientation, narrative text etc.
  • How to identify a process from stimulus to response (Organisational Events)
  • How to separate design issues from business issues
  • How to apply Quality Assurance to each deliverable
  • Use a systematic top down approach to process modelling
  • Understand what a repository is and why it is important.
  • Identify the characteristics required from a case tool and understand the difference between a modelling tool and a case tool
  • Understand what is ‘analysis paralysis’ and how to ensure it doesn’t set in.
  • Develop a Business Process Design

In-house Training at a venue of your choice is available on request for a minimum of 6 delegates

Each delegate will receive:

  • Access to the online learning portal .
  • Certificate of Completion


Course Content

Process Analysis Fundamentals

A management overview of the concepts of Business Process Analysis, this will include the following:

  • Introduction to BPA
  • Advantages of Process Centric Approach
  • Risks and Benefits
  • Activities Required to implement a solution
  • Activities required to support a solution
  • Ensuring Business Benefit for a solution

This 1 day overview provides the foundation for the Process Analysis and the ‘to be’ process design.



  • Brief History of the Systems Development Life Cycle (SDLC)
  • Role Definitions
  • Deliverables of the standard SDLC
  • Personal Characteristics of an Analyst
  • Overview of the training
  • Overview of the training methods
  • SDLC Quality Requirements

Overall Objective: To provide the learners with a foundation to the subject matter.

The Essence of Every Organisation


How organizations are formed

  • Where Analysis fits in with the business

Overall Objective: To provide the learners with an understanding of how and where technology meets business and why it is important to understand the needs of the business before inventing a solution.

Dis-Covering the Real Business


How organizations have fragmented the end-to-end process

  • Understanding the difference between business policy and procedure and essential business requirements
  • Examples of non-essential business policy
  • Examples of non-essential business information

Overall Objective: To show the learner that lots of business policies are not challenged and are often instituted, then carried into the future with very little or no business benefit. This is their introduction to challenging existing paradigms

The Need for Models


Proof that models are better than narrative text

  • Model Categories
  • Choosing an appropriate model
  • State Transition Diagrams
  • Flow Charts
  • Swim Lane Diagrams
  • Use Case Diagrams
  • Data Flow Diagrams

Overall Objective: To show and describe various modelling techniques to the learner, so that they can choose the correct modelling techniques to depict the requirements.

Overview of Business Process Analysis


Definition of Business Process Analysis

  • The Context of Business  Process Analysis
  • Tools for the Process Analyst
  • Definition of a Data Flow Diagram
  • Flavours of Data flow Diagrams (DFD)
  • Event Context DFD & Business Event Memory
  • Using DFDs to Model Analysis and Design Issues
  • Sample of a Data Flow Diagram
  • Definition of a Data Dictionary
  • Sample of Data Dictionary
  • Definition of a Process Specification
  • Sample Process Specification
  • Sample Complete Business Process Analysis Specification
  • Separating Analysis/Design and As Is/To be Issues

Objective: To provide the learners with an understanding the concepts of Process Analysis, including where and why data definition is imperative.



Modelling Rules


Using DFDs to model Business Issues

  • Modelling External Interfaces
  • Modelling Data & Control Flows
  • Modelling Stimulating Flows
  • Modelling Response Flows
  • Modelling Converging and Diverging Data Flows
  • Modelling Processing
  • Modelling Stored Data
  • Additional Helpful Modelling Symbology
  • Behaviour Rules of Symbology
  • Correct Data Flow Naming
  • Correct Process Naming
  • Summary of Valid Analysis Constructs
  • A Sample Detailed DFD
  • The Best Way to Draw a Data Flow Diagram

Overall Objective: To provide the learners with the skills required to model a process



Organisational  Event Modelling


Organisational Event Definitions (the end-to-end process)

  • Classical Vs. Organisational Event Partitioning
  • What Constitutes a Total Organisational Event
  • Organisational Event Level Vs. Detailed Level Modelling
  • Separating Organisational Events
  • Types of Events
  • Definition of Strategic Events
  • Definition of System Events
  • Definition of Business Events
  • Definition of Regulatory Events
  • Definition of Dependent Events
  • Determining Event Types
  • Business Event Partitioning Vs. Human or Computer Partitioning
  • Understanding Event Primers (marketing)
  • Benefits of the Business Engineering

Overall Objective: To provide the learners with the foundation knowledge of how to identify and contain project scope. This section provides the basis of the User Centred Design Session



Decomposing & Levelling


Handling Complex Events

  • Naming Levels of Data and Processing
  • The Lowest Level Process Model
  • Unnecessary Process Detail
  • Design Levelling
  • Analysis Levelling
  • The Detailed Business Event Level
  • Input/ Process/ Output
  • Handling Complex Stores
  • Data Cohesion and Data Conservation of business Events

Overall Objective: The learners need to understand how much detail to capture about a process, in order to produce the most effective solution.



Data Dictionary


Defining the Data

  • Design Vs. Analysis Data Definitions
  •  Potential Complexity of the Data Dictionary
  • Data Dictionary Notation
  • Complex Definitions
  • Clarifying Notation
  • Defining Data Elements
  • Reusable Data Element Groups
  • Data Element Specification
  • Design/Analysis Issues of Data
  • Beware of Pre-Printed Forms
  • Consistent Data Element Naming
  • Sample Standard Naming Convention

Overall Objective: Data is a vital aspect of processes, because by definition a process is the transformation of data, it is equally important that we understand and document in a concise, unambiguous manner, the data that enters the process and data that exits the process.



Specifying Business Logic – Process Specifications


Specifying Data Transformations in Process Specifications

  • Methods Specification
  • Recording Business Policy
  • Overcoming
  • Complex Logic
  • Decision Tables
  • Sample Decision Table Results
  • Structured English
  • Structured English Examples

Overall Objective: The step-by-step instructions of transforming an input data flow into an output data flow are absolutely essential to the success of any project. We make use of various methods in which to document the business rules and controls, in a detailed, concise and unambiguous manner.



Basic Communication Skills

Interaction with other people is continual; therefore every analyst needs the ability to ask constructive, meaningful questions. More importantly they must have the ability to assimilate the responses received. All interactions should be constructive and purposeful.



  • Types of interviews and interactions
  • Suggested questions for requirements elicitation
  • Setting SMART objectives

Overall Outcomes: To place the “soft skills” into context for the learner. Some basic questions for extracting information are provided. The purpose and benefits of SMART (Specific, Measurable, Accurate, Realistic, Timed) objectives or agendas are discussed to ensure every interaction is constructive and beneficial to reduce time wastage.



History of Joint Application Design (JAD)

  • Participants of a Facilitated Session and their roles
  • Guidelines for Success
  • Facilitated Sessions Benefits
  • Ensuring Quality via Reviews and Walkthroughs

Overall Objective: To provide the learners with an overview of group sessions. TQM is of vital importance of the development of a Detailed Business Requirement, it is essential that each deliverable has a review. The structure, participants and outcomes of reviews will be discussed.

Communication Skills


  • The Role of the Analyst
  • Challenging the Thought Process
  • Documenting the Thought Process
  • Essential Communication Skills
  • Questioning Techniques
  • Listening Skills
  • Attentive Listening
  • Encouraging Listening
  • Reflecting Listening
  • Active Listening
  • Dealing with Interruptions
  • Dealing with Negativity
  • Barriers to Listening

Overall Objective: To provide the learners with the ability to ask meaningful, constructive questions and to assimilate and capture the responses.



User Centred Design

User-Centred design requires the inclusion of a product’s end-users throughout the design process.

The primary benefit of user-centred design is that, it ensures that the solution is useful, usable, and meaningful to the end-user. Also, many of the low-fidelity methods developed to accomplish user-centred design allow for shortened development cycles.



Definition of Key Terms

  • Project Deliverables
  • The Focus of User Centred Design
  • Definition of User Centred  Design
  • Aims of User Centred Design

Overall Objective: To provide the learners with the foundations of User Centred Design

Overview of Design


  • The Automation Boundary
  • Pre-Packaged DFD
  • Swim Lanes
  • As is analysis DFD example
  • Partial Data Dictionary example
  • Design Swim Lane Example 1
  • Design Swim Example 2
  • Screen Design
  • Story Board
  • Review

Overall Objective: To provide the learners with an overview of what will be covered from a Design perspective.

Pre-Packaging – the beginnings of design


  • The Automation Boundary
  • Obvious Design Packaging
  • Who will use the new system?
  • Where is the Processes performed?
  • What is the Relationship between the User and Data?
  • What Other Tools Does the User Have?
  • How do Users Communicate with one another?
  • What are the Time Constraints on the processes
  • Bounded Model Example
  • Review

Overall Objective: To provide the learners with a starting point in the design process. They will learn how to document and design of interfaces to the system.





What is Prototyping

  • Fidelity in Prototyping
  • Why use Low-Fi prototypes?
  • Hi-Fi Prototypes Warp
  • The Basic Materials
  • Constructing the model
  • Evaluation Preparation
  • Post Evaluation Activities
  • Informal User for Early Stage UI Design
  • Widgets
  • Developing a Low-Fi Prototype
  • Summary

Overall Objective: Because it is too expensive to build a solution without a review, a method is required to present the emerging solution; the conceptual design needs to be put into a tangible form.



Story Boarding



  • Using the Pre-Packaging and Work Flows
  • Initial Screen Design
  • Storyboard
  • Summary

Overall Objective: To provide the learners into some insights on how screens should flow and to think about the navigation from the user’s perspective.