Business Process Analysis is the most important aspect of Business Process Management (BPM) and the models and support specifications that result from analysis are crucial to an Enterprise Architecture.

The task of analysis has to be performed on any worthwhile project, be it buying a car, house, hardware or an information system. It will be performed even if it is disguised or combined within a solution or is passed off to a vendor or assumed to have been performed as part of a purchased package, and analysis is an activity that is independent of any particular development methodology or software tool.

We see problems today in Information System/Information Technology with hardware and software that can't talk to each other. We see the equivalent in manual system where departments have their own terminology and support methods. That may be expected with a young industry but not with an established profession or even an established organization. At least within an organization there should be the equivalent of the house blueprint – a model of the essential business, backed up with definitions of its data.

The inability to specify and communicate the correct Business Requirements can lead to a canceled development project or the wrong purchased package. This is regardless of good system design or implementation methods. Business Process Analysis draws heavily on graphical models, such as Flow Diagrams or Data Flow Diagrams, as well as textual documentation to assist in this critical requirements gathering activity. How these models are displayed (their structure and partitioning) is important as the design of future systems will probably be based on this display. This seminar describes Event and Event Partitioning as the best way to do this.

The seminar content is presented in an unambiguous, non-technical, jargon free manner. It also uses workshops and case studies to show the importance of deriving logical, implementation independent views of an organization (or a portion of an organization). This logical view will assist in defining the best design characteristics for future systems as an Event Partitioned model will flow naturally into systems design for development or packaged system selection.

This seminar is for Enterprise Architecture team members, Business Architects and Business Analysts, Project and Program managers, Users/Owners of business policy and others having responsibilities to purchase, build or implement systems support for business mission areas dealing with processes, activities and Events.

Seminar Outline

COPYRIGHT 2010, LOGICAL CONCLUSIONS, INC.