Content deleted Content added
Reverted 1 edit by Wallace pinto oliveira (talk): Spam |
m clean up spacing around commas and other punctuation, replaced: ,and → , and |
||
| (4 intermediate revisions by 3 users not shown) | |||
Line 54:
In the field of [[software engineering]], the term ''business process modeling'' opposed the common [[software process]] modeling, aiming to focus more on the state of the practice during [[software development]].<ref>Brian C. Warboys (1994). ''Software Process Technology: Third European Workshop EWSPT'94'', Villard de Lans, France, February 7–9, 1994: Proceedings. p. 252.</ref> In that time (the early 1990s) all existing and new modeling techniques to illustrate business processes were consolidated as 'business process [[modeling language]]s'{{Citation needed|date = April 2014}}. In the [[Object Oriented]] approach, it was considered to be an essential step in the specification of business application systems. Business process modeling became the base of new methodologies, for instance, those that supported [[data collection]], data flow analysis, process flow diagrams, and reporting facilities. Around 1995, the first visually oriented tools for business process modeling and implementation were presented.
== Objectives
[[File:Influencing-factors-on-the-business-process-model.png|thumb|Influencing factors on the business process model]]
Line 106:
* Participation in competitions (such as [[European Foundation for Quality Management|EFQM]]).
== Applications
Since business process modeling in itself makes no direct contribution to the financial [[Profit (economics)|success]] of a company, there is no motivation for business process modeling from the most important goal of a company, the [[For-profit corporation|intention to make a profit]]. The motivation of a company to engage in business process modeling therefore always results from the respective purpose. ''Michael Rosemann, Ansgar Schwegmann und Patrick Delfmann'' lists a number of purposes as motivation for business process modeling:
* Organizational ''documentation'', with the "objective of increasing transparency about the processes in order to increase the efficiency of communication about the processes"<ref name="ROSEMANN"/> <sup>(Chapter 3.2.1 Relevant perspectives on process models) ← automatic translation from German, </sup><ref name="GADATSCH"/> <sup>(Chapter 2.5.4 Areas of application for process modeling in practice) ← automatic translation from German</sup> including the ability to create process templates to relocate or replicate business functions or the objective to create a complete company model
Line 181:
* To ensure suitable and available at the place and time as required;
* To ensure protection (e.g. against loss of confidentiality, improper use or loss of integrity);
* To consider distribution, access, retrieval, and use;
* To consider filing/storage and preservation (including preservation of readability);
* To perform monitoring of changes (e.g. version control); and
Line 651:
{{|bot=InternetArchiveBot |fix-attempted=yes}}
{{DEFAULTSORT:Business Process Modelling}}
[[Category:Business process modelling| ]]
| |||