Process Model
Jump to navigation
Jump to search
A Process Model is a model that represents a process.
- Context:
- It can range from being a Descriptive Process Model to being a Prescriptive Process Model to being an Explanatory Process Model.
- It can be created by a Process Modeling Task.
- It can be represented using various modeling techniques and tools, such as BPMN (Business Process Model and Notation), UML (Unified Modeling Language), or Petri Nets.
- …
- Example(s):
- a Lifecycle Model, such as:
- a Software Development Process Model, such as Agile Software Development.
- ...
- an Organizational Process Model, such as:
- a Workflow Process Model.
- …
- a Lifecycle Model, such as:
- Counter-Example(s):
- See: Organizational Workflow, Model Instance, Process Redesign.
References
2021
- (Wikipedia, 2021) ⇒ https://en.wikipedia.org/wiki/Process_modeling Retrieved:2021-11-28.
- The term process model is used in various contexts. For example, in business process modeling the enterprise process model is often referred to as the business process model. ...
- The term process model is used in various contexts. For example, in business process modeling the enterprise process model is often referred to as the business process model. ...
2013
- http://en.wikipedia.org/wiki/Process_modeling#Overview
- Process models are processes of the same nature that are classified together into a model. Thus, a process model is a description of a process at the type level. Since the process model is at the type level, a process is an instantiation of it. The same process model is used repeatedly for the development of many applications and thus, has many instantiations. One possible use of a process model is to prescribe how things must/should/could be done in contrast to the process itself which is really what happens. A process model is roughly an anticipation of what the process will look like. What the process shall be will be determined during actual system development.[1]
The goals of a process model are to be:
- Descriptive
- Track what actually happens during a process.
- Take the point of view of an external observer who looks at the way a process has been performed and determines the improvements that must be made to make it perform more effectively or efficiently.
- Prescriptive
- Define the desired processes and how they should/could/might be performed.
- Establish rules, guidelines, and behavior patterns which, if followed, would lead to the desired process performance. They can range from strict enforcement to flexible guidance.
- Explanatory
- Provide explanations about the rationale of processes.
- Explore and evaluate the several possible courses of action based on rational arguments.
- Establish an explicit link between processes and the requirements that the model needs to fulfill.
- Pre-defines points at which data can be extracted for reporting purposes.
- Descriptive
- Process models are processes of the same nature that are classified together into a model. Thus, a process model is a description of a process at the type level. Since the process model is at the type level, a process is an instantiation of it. The same process model is used repeatedly for the development of many applications and thus, has many instantiations. One possible use of a process model is to prescribe how things must/should/could be done in contrast to the process itself which is really what happens. A process model is roughly an anticipation of what the process will look like. What the process shall be will be determined during actual system development.[1]
- ↑ Colette Rolland and Pernici, C. Thanos (1998). A Comprehensive View of Process Engineering. Proceedings of the 10th International Conference CAiSE'98. B. Lecture Notes in Computer Science 1413. Springer.