This introductory tutorial teaches you how to analyze the processing aspects of any business large or small. It is also an essential part of what’s known as Business Process Improvement.
This tutorial is intended to give you a good knowledge of Process Analysis concepts and a reading knowledge of the process analysis effort result, which is a Business Process Analysis Specification.
That specification captures the Essential Business Processing and Workflow in an organization or business area.
The goal of this course is to give you the knowledge to realize the importance of a good analysis effort and its benefit to any business. In this course you will learn how to separate Analysis from Design and implementation issues and be able to specify the essential requirements which will be used to create a successful business structure.
Even though this is an introductory Business Process Analysis course it contains a significant amount of information that should be helpful to your career and any business to which you apply the concepts.
The course contains approximately one hour of material structured into eight lectures.
As you will see Process Analysis is the most important technical task that should be conducted on every business.
This introduction identifies what you will learn in the tutorial. It shows the different Business models used to describe an organization as well as identifying the need to separate the existing design from analysis issues.
It lists the four main aspects we need to gather for a Process Analysis model.
This section simply sates the goals of Business Process Analysis and Identifies the context of where Analysis fits in to the development life cycle.
In this section we get right to the heart of business issues and how we should view an organization and its documentation.
We cover the different types of Events that every business responds to and focus on Business Events - the ones that will help us create an efficient, cost effective, unbeatable business.
This section teaches how we can and should use "Customer" Business Events to partition our Business Model and even use them for future design structures for a business.
I’ve included enough detail in this section for you to be able to create a decent Process Model for a business.
Now there are a number of different modeling techniques that have emerged in the Business Process Management subject area. Luckily most of them have a common theme that aims to produce a flow model of some kind for the organization.
In order to teach this section in Process Analysis I’m going to use a process model called a Data Flow Diagram and its supporting specifications. There are other types of models but I have found a model showing data flowing through its processing to be easy to understand and create.
I will recommend the use of Business Events to map the essential flow of each reaction to an Event and use Event-Driven concepts as a means of partitioning the analysis models.
This section covers one of the support specifications for our Analysis Process Model. It is where we define what we mean by the data items flowing on our Business Model via a Data Dictionary.
I identify a recommended Standard Naming Convention as well as a concise Data Dictionary Notation for non-ambiguous definitions.
This section covers another one of the support specifications for our analysis model. It is where we define the contents of the Stored Data on our Business Model.
This subject is part of analysis, but it’s not part of Process Analysis. It is typically the domain of Information Analysis. It is necessary to talk about this subject here though, as the process model shows stored data.
In this section we'll talk about Essential versus Non-Essential Stored Data and how we see through the Design of existing files.
I show a Data Model for Stored Data and then describe the Link between Process Models and Data Models.
This section covers another one of the detail support specifications for our Analysis Process Model.
It’s where we specify business policy via the contents of the detail Processes - in other words the actual step by step business rules.
In this section we discuss how we use the top-down Process Modeling technique to reach the detail processes and then use various methods of documentation for documenting the processing.
In this section we use the analysis Business Process Model to move into the beginnings of a new design for the business.
We cover the components of the complete Business Process Analysis Specification and use the Process Model to identify Functional Design Boundaries for the new systems.
We then identify the Automation Boundary and form Event-Driven Compartments and show how we should use each Event–Driven Compartment to form efficient human and/or computer teams.
In this summary section we discuss the Business Library containing the essential documentation that will help a business implement changes in the future and allow it to expand easily.
I also list the business benefits of Implementing an Event-Driven design advocated in this course.
I am the President and CEO of Logical Conclusions, Inc., a training and consulting company specializing in how to create a Customer Focused, Event-Driven organization. For over three decades I've assisted Business Process Management/Improvement and Re-engineering projects at many major corporations and government agencies.
I've created numerous videos and educational tutorials on how to create the definitive efficient business structure for any organization.
I've also taught thousands of attendees at live business user and technical workshop seminars.
Being a prolific guest speaker I've given talks at many Business Process/Information Resource conferences such as conducting keynote and featured speeches at:
Also presentations at:
I've published many books and articles on Business Improvement and Quality Systems Development. My latest e-book is titled “Strategic Planning using a Customer-Focused, Event-Driven model”.
I have been a proud participant in the US Citizen Ambassador Program representing the U.S.A. in China and Russia.I can be reached at: Brian@LogicalConclusionsInc.com