Process modeling: Difference between revisions

Revision as of 20:10, 8 July 2016

Revision as of 18:01, 26 July 2016

Line 26:

The activity of [[business model|modeling a business]] process usually predicates a need to change processes or identify issues to be corrected. This transformation may or may not require IT involvement, although that is a common driver for the need to model a business process. [[Change management]] programmes are desired to put the processes into practice. With advances in technology from larger platform vendors, the vision of business process models (BPM) becoming fully executable (and capable of round-trip engineering) is coming closer to reality every day. Supporting technologies include [[Unified Modeling Language]] (UML), [[model-driven architecture]], and [[service-oriented architecture]].

Process modeling addresses the process aspects of an [[Enterprise Business Architecture]], leading to an all encompassing [[Enterprise Architecture]]. The relationships of a business processes in the context of the rest of the enterprise systems, data, organizational structure, strategies, etc. create greater capabilities in analyzing and planning a change. One real -world example is in corporate [[mergers and acquisitions]]; understanding the processes in both companies in detail, allowing management to identify redundancies resulting in a smoother merger.

Process modeling has always been a key aspect of [[business process reengineering]], and continuous improvement approaches seen in [[Six Sigma]].