Difference between revisions of "Main Page"

From OOEM
Jump to navigationJump to search
 
(68 intermediate revisions by the same user not shown)
Line 1: Line 1:
= This Wiki is Under Construction [http://www.ooem.org#OOBPM More Information Here] =
=== {{T|Einführung|Introduction}} ===


== Time to advance BPM ==
<div style="width:140px; float:right; border:thin solid #ccc; padding:4px 4px 4px 4px;">
{{T|Zur Einstimmung: '''[[10 Thesen|10 Thesen zur Inspiration]]'''|Appetizer: '''[[10 Thesen|10 Theses for Inspiration]]'''}}
</div>


{{T|
* Was ist UBPML?
* Was ist UBPML?
:: UBPML ist eine Modellierungssprache für Geschäftsprozesse, und zwar sowohl für fachliche als auch für IT-technische, die mit UBPML in '''einem''' integrierten Modell konsistent beschrieben werden können.
|
* What is UBPML?
:: UBPML is a modelling language for business processes - and that is for application domain ones as well as IT technical ones - and with UBPML both can be described in one and the same integrated model consistently.
}}
{{T|
* Ist UBPML schon wieder etwas neues?
:: Nein. UBPML ist eine Ergänzung der '''bewährten Standards''' UML und BPMN, um die Spannung zwischen fachlicher Ebene und technischen Details aufzulösen.
|
* Is UBPML yet another new thing?
:: No. UBPML is an extension to the '''proven standards''' UML and BPMN, to resolve the tension between application domain issues and technical details.
}}
{{T|
* Welche Probleme löst UBPML?
:: Mit UBPML ist es möglcih, ein '''Single Source Modell''' für Fachbereich und IT herzustellen, anstatt wie bisher separate Modelle, die in aller Regel auf Dauer nicht konsistent gehalten werden können. UBPML Modelle sind einerseits '''übersichtlich''' und kurz gefaßt genug für den Fachbereich, andererseits ausreichend '''präzise''' für die IT-technische Umsetzung. UBPML Teil-Modelle können '''lose verbunden''' sein, so daß kein übergroßes Top-Down-Design erfolgen muß (kein BigDesignUpFront). Darüber hinaus können UBPML Modelle sich selbst während des Betriebs selbsttätig vervollständigen ("late service binding").
|
* Which problems addresses UBPML?
:: UBPML allows to create a '''Single Source Model''' for both business users and IT people, instead of the usual sperated models, which typically can't be kept consistent in the long run. UBPML models are clear and comprehensbible enough for business users, while being at the same time suffieciently detailed and precise enough with respect to IT technical implementation.Due to loose coupling in UBPML, no oversized top-down design is necessary (no BigDesignUpFront). In addition, UBPML models are able to complete themselves during business operations ('late service binding').
}}
{{T|
* Wie funktioniert UBPML?
:: UBPML verknüpft die '''zweckbezogene Planungsebene''' mit der '''kontrollflußcodierten Ausführungebene'''. Das UBPML-Metamodell ist das Ergebnis einer objektorientierten Analyse der Domäne "Arbeit und Planung". Dadurch steht neben der Präzision der Modellbegriffe das gesamte Instrumentarium der Objektorientierung zur Handhabung komplexer Systeme zur Verfügung.
|
* How does UBPML work?
:: UBPML links the '''purposeful planing level''' to the '''control flow coded execution level'''. The UBPML metamodell is the result of an object oriented analysis of the domain "work and planing". Therefore, in addition to a crisp metamodel and basic terms the full power of object orientation is available to handle complex systems.
}}
{{T|
* Ist das nicht zu kompliziert für Fachanwender?
:: Nein. Das UBPML/light Konzept belegt, daß die UBPML Struktur auf '''ganz einfachen''' Prinzipien besteht, die von jedermann nachvollzogen werden können, soweit sein Arbeitsbereich betroffen ist. Natürlich steht es außer Frage, daß ein unternehmensweites Prozeßmodell insgesamt weiter gefaßte Expertise und Werkzeug-Unterstützung erfordert - der Vorteil von UBPML besteht jedoch darin, diese Facetten eines komplexen Modells stimmig zu vereinen und gleichzeitig natürlich voreinander abzugrenzen.
|
* Now that is far too complex for business users, isn't it?
:: Not at all. The UBPML/Light concept proofs, that the UBPML structure is based on '''totally simply''' principles, comprehensible by everybody, as far as their work is affected. Of course without doubt an enterprisewide process model requires elaborated skills and sound tooling - nevertheless the advantage of UBPML is the ability to integrate all those different facets of a complex model and at the same time shield them naturally from one another.
}}
=== {{T|Dokumentation|Documentation}} ===
{{T|
* [[UBPML Tutorial]]
* [[UBPML Referenz]]
* [[UBPML Prozess]]
* [[UBPML Prozessbegriffe]] (Glossar und Methodenvergleich BPMN, UML, EPC, UBPML, CEP, (A)CM, HIMS)
* [[Handlung als elementarer Prozeßbaustein]]
* [[UBPML Meta Modell]]
* [[UBPML/light Referenz]]
|
* [[UBPML Tutorial]]
* [[UBPML Referenz|UBPML Reference]]
* [[UBPML Prozess|UBPML Process]]
* [[UBPML Prozessbegriffe|UBPML Process Terms]] (Glossary and Comparison of Methods BPMN, UML, EPC, UBPML, CEP, (A)CM, HIMS)
* [[Handlung als elementarer Prozeßbaustein|Acttion as basic Process Element]]
* [[UBPML Meta Modell]]
* [[UBPML/light Referenz|UBPML/light Reference]]
}}
=== Tools ===
* [[DiaShapes|{{T|Shapes für|Shapes for}}]] [http://live.gnome.org/Dia Dia]


* Welche Probleme löst UBPML?
=== {{T|Publikationen|Publications}} ===
 
* [[Artikel|{{T|Artikel|Paper}}]]
 
=== Events ===


** Single Source Modell für Fachbereich und IT
* [[Vorträge|{{T|Vorträge|Speeches}}]]
** ''verständlich'' für Fachbereich - ''präzise'' für IT
** ''dezentrales'' Arbeiten möglich, kein Top-Down notwendig


* Wie funktioniert UBPML?
=== {{T|Über uns|About us}} ===


=== Mehr... ===
* [[Initiatoren|{{T|Initiatoren|initiators}}]]


* UBPML Referenz
__NOTOC__
* UBPML/light Referenz
* Vorträge
* Veranstaltungen
* Initiatoren

Latest revision as of 13:07, 2 March 2011

Introduction

  • What is UBPML?
UBPML is a modelling language for business processes - and that is for application domain ones as well as IT technical ones - and with UBPML both can be described in one and the same integrated model consistently.

  • Is UBPML yet another new thing?
No. UBPML is an extension to the proven standards UML and BPMN, to resolve the tension between application domain issues and technical details.

  • Which problems addresses UBPML?
UBPML allows to create a Single Source Model for both business users and IT people, instead of the usual sperated models, which typically can't be kept consistent in the long run. UBPML models are clear and comprehensbible enough for business users, while being at the same time suffieciently detailed and precise enough with respect to IT technical implementation.Due to loose coupling in UBPML, no oversized top-down design is necessary (no BigDesignUpFront). In addition, UBPML models are able to complete themselves during business operations ('late service binding').

  • How does UBPML work?
UBPML links the purposeful planing level to the control flow coded execution level. The UBPML metamodell is the result of an object oriented analysis of the domain "work and planing". Therefore, in addition to a crisp metamodel and basic terms the full power of object orientation is available to handle complex systems.

  • Now that is far too complex for business users, isn't it?
Not at all. The UBPML/Light concept proofs, that the UBPML structure is based on totally simply principles, comprehensible by everybody, as far as their work is affected. Of course without doubt an enterprisewide process model requires elaborated skills and sound tooling - nevertheless the advantage of UBPML is the ability to integrate all those different facets of a complex model and at the same time shield them naturally from one another.

Documentation

Tools

Publications

Events

About us


Retrieved from "https://wiki.ubpml.org/index.php?title=Main_Page&oldid=292"