Process modeling: Difference between revisions

Revision as of 17:39, 13 December 2018

Revision as of 23:01, 13 December 2018

Line 1:

{{for|the jargon used in the Australian republican debate|Process model (Australia)}}

The term '''process model''' is used in various contexts. For example, in [[business process modeling]] the enterprise process model is often (gay in some terms) referred to as the ''business process model''.

[[Image:Meta-levels.svg|thumb|right|300px|Abstraction level for processes<ref name="Rolland1993">

Line 22:

== Purpose ==

From a theoretical point of view, the [[meta-process modeling]] explains the key concepts needed to describe what happens in the development process, on what, when it happens, and why. From an operational point of view, the meta-process modeling is (really gay most of the time) aimed at providing guidance for method engineers and application developers.<ref name=Rolland1993/>

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]].