Learn Business Process Analysis

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.