OOEM is a comprehensive Enterprise Modelling Language.

Participate in OOEM research:

Open repository for OOEM models
and much more:

Enterprise Model Operation Services

OOEM is the result of Sphenon's development and research efforts in creating our powerful model execution engine EMOS.

This engine provides enterprise solutions, ready for prodcution, which are controlled immediately by business domain models (i.e., OOEM).

Slides

Discuss OOEM/BPM on oomodels:

OOEM Models describe the business domain, it's structure and logic, as well as business processes.

They are precise enough to to allow the automated creation of appropriate IT applications while being abstract enough to be manageable by business domain experts.

OOEM is based on a subset of UML 2.0, augmented by OO-BPM Notation and a rich set of Extended Model Properties (XModel).

OOEM Models are comprehensive (dynamic and static enterprise structure), maintainable (single source), executable (as far as feasible by machines), modular and non-redundant (thereby flexible), aspect oriented (distinct concerns are expressed separately), artefact-focused (people are not regarded as mere "actors"), and open (everyone can use it).

For more information, you're welcome to contact Andreas Leue or Sphenon GmbH.

Special thanks to GWK GmbH for free web hosting and continuous excellent support.

OOEM Business Process Notation (OOEM/BPM)

OOEM/BPM is based on UML class and object diagrams. It is related to, but not the same as activity diagrams - due to the OO nature of our modelling approach (no control flow!).

For details, please refer to the slides you can download on the right side. We are happy to provide more information and coaching in case you are interested in using the notation.

It is not our intention to compete with UML, in the contrary, we'd be happy if UML would be developing in such a direction. There are chances this might happen, considering the evolution in UML process modelling over the last decade.

It is important to note that is already possible to use UML to build OOEM/BPM models as we suggest, since these models are strictly speaking just class/instance diagrams.

Just as well it is clear, that this plain UML notation is not usable by non-IT people, therefore a notational and semantically extension of UML with OOEM/BPM symbols is very much desirable.

Terms and Diagram Types

A Process is a collection of a certain set of Step instances of a certain set of Step classes
A Process Schema is a certain set of Step classes
A Workflow is a sequence of connected Step classes
A Workflow Instance is a sequence of connected Step instances matching some Workflow
A Project is a sequence of connected Step instances
A Process Stage Schema is a collection of Step classes, comprising Workflows and Process Schemas
A Progression Plan is a collection of Step instances, comprising Projects and Workflow Instances

Notationsübersicht

Basic symbols - note the distinction between classes (no underline) and instances (underline)

UML stereotypes vs. new symbols (OOEM/BPM)

A constellation is an aggregation of certain objects within certain states

A step is the explicitly performed change between an initial and a final constellation.

Same as above, but with instances instead of classes

Steps can be derived from as is true for any normal class; derivation of classes and instances within a certain state expresses a substate relationship