Difference between revisions of "UBPML Referenz"

From OOEM
Jump to navigationJump to search
 
(12 intermediate revisions by the same user not shown)
Line 1: Line 1:
== UBPML Notation ==
== UBPML Notation ==
[[:image:ubpmloverview.pdf|Download UBPML Notation Overview in PDF format]]


{| class="dgmtable"
{| class="dgmtable"
!bgcolor="#F0F0FF"| Notation
!bgcolor="#F0F0FF"| {{T|Notation|Notation}}
!bgcolor="#F0F0FF"| Bedeutung
!bgcolor="#F0F0FF"| {{T|Bedeutung|Semantics}}
!bgcolor="#F0F0FF"| Konformität
!bgcolor="#F0F0FF"| {{T|Konformität|Conformity}}
|-
|-
| [[Image:UBPMLClass.png]]
| [[Image:UBPMLClass.png]]
| Eine Klasse
| {{T|Eine Klasse|A class}}
| [[UML]] standard
| [[UML]] standard
|-
|-
| [[Image:UBPMLObject.png]]
| [[Image:UBPMLObject.png]]
| Eine Instanz einer Klasse
| {{T|Eine Instanz einer Klasse|An instance of a class}}
| [[UML]] standard
| [[UML]] standard
|-
|-
| [[Image:UBPMLClassInState.png]]
| [[Image:UBPMLClassInState.png]]
| Eine Klasse in einem bestimmten Zustand
| {{T|Eine Klasse in einem bestimmten Zustand|A class in a certain state}}
| UBPML
| UBPML
|-
|-
| [[Image:UBPMLClassInStateWithDefinition.png]]
| [[Image:UBPMLClassInStateWithDefinition.png]]
| Eine Klasse in einem bestimmten Zustand. Dieser Zustand wird hier ebenfalls deklariert, und zwar in Form einer Bedingung, die dann und nur dann erfüllt ist, wenn der Zustand vorliegt.
| {{T|Eine Klasse in einem bestimmten Zustand. Dieser Zustand wird hier ebenfalls deklariert, und zwar in Form einer Bedingung, die dann und nur dann erfüllt ist, wenn der Zustand vorliegt.|A class in a certain state. The state itself is also declared here, and that by specifying a condition, which true and only true if that state is given.}}
| UBPML
| UBPML
|-
|-
| [[Image:UBPMLObjectInState.png]]
| [[Image:UBPMLObjectInState.png]]
| Eine Instanz einer Klasse in einem bestimmten Zustand.
| {{T|Eine Instanz einer Klasse in einem bestimmten Zustand.|An instance of a class in a certain state.}}
| [[UML]] standard (seit 2.0 in Aktivitätsdiagrammen)
| [[UML]] standard (seit 2.0 in Aktivitätsdiagrammen)
|-
|-
<!--
| [[Image:UBPMLConstellationStereotype.png]]
| [[Image:UBPMLConstellationStereotype.png]]
| UML stereotypes vs. new symbols (OOEM/BPM)
| UML stereotypes vs. new symbols UBPML
| suggested UML usage conforming to standard
| [[UML]] standard
|-
|-
-->
| [[Image:UBPMLConstellationClass.png]]
| [[Image:UBPMLConstellationClass.png]]
|
| {{T|Ein bestimmter Zustand des Systems, der durch eine Menge von Klassen (d.h. eine ''Konstellation'') in einem bestimmten Zustand beschrieben wird, sowie optional weiteren Bedingungen, die für diese Klassen sowie ihre Beziehungen untereinander gelten müssen. Eine ''Konstellation'' ist eine UML Klasse, also im Metamodell abgeleitet von ''Klasse''.|A certain system state, defined by a set of classes (i.e a ''Constellation'') in certain states, as well as optionally additional constraints that have to be met by that classes and their relationships. A ''Constellation'' is a UML class, i.e. dervied from ''Class'' in the metamodel.}}
| specific UML usage conforming to standard
| UBPML
|-
|-
| [[Image:UBPMLConstellationObject.png]]
| [[Image:UBPMLConstellationObject.png]]
|
| {{T|Eine Instanz einer Konstellation, also eine Menge von Instanzen in bestimmten Zuständen, die die Bedingungen der Konstellations-Klasse erfüllen.|An instance of a Constellation, i.e. a set of instances in certain states, which satisfy the constraints of the Constellation-class.}}
| specific UML usage conforming to standard
| UBPML
|-
|-
<!--
| [[Image:UBPMLStepStereotype.png]]
| [[Image:UBPMLStepStereotype.png]]
|
|
| UML usage
| [[UML]] standard
|-
|-
-->
| [[Image:UBPMLStepClass.png]]
| [[Image:UBPMLStepClass.png]]
|
| {{T|Ein Schritt (''Step'') beschreibt eine Veränderung (Transformation) des Systems von einer Konstellation in ein oder alternativ mehrere andere. Er stellt somit die elementare Einheit einer ''geplanten Veränderung'' dar. Ein ''Schritt'' ist eine UML Klasse, also im Metamodell abgeleitet von ''Klasse''.|A ''Step'' denotes a change (transformation) of the system from one constellation into possibly several alternative other ones. It is thereby the elementary unit of a ''planned change''. A ''Step'' is a UML class, i.e. dervied from ''Class'' in the metamodel.}}
| specific UML usage conforming to standard
| UBPML
|-
|-
| [[Image:UBPMLStepObject.png]]
| [[Image:UBPMLStepObject.png]]
|
| {{T|Eine Instanz eines Schrittes. Diagramme, die Instanzen von Schritten beinhalten können zur Beschreibung von ''Projekten'' verwendet werden. Auf diese Weise werden Projekte und Prozesse in einer einheitlichen Notation verknüpft.|An instance of a Step. Diagrams containing Step instances may serve to describe ''Projects''. Thereby it is possible to describe Projects and Processes within one uniform notation.}}
| specific UML usage conforming to standard
| UBPML
|-
| [[Image:UBPMLProcedure.png]]
| {{T|Ein Schritt besschreibt, ''was'' getan werden, welche Veränderung stattfinden soll. Er legt nicht fest, ''wie'' dies geschieht. Dies erfolgt durch Zuordnung einer ''Prozedur'' zu einem Schritt. Prozeduren können verschiedenes sein: eine Handlungsanweisung für einen Mitarbeiter, eine verfeinerte Vorgehensweise oder eine maschinelle Operation (Aufruf eines Dienstes). Verfeinerte Vorgehensweisen wiederum können entweder aus UBPML Schritten oder aber aus BPMN- bzw. UML-Aktivitäten bestehen.|A Step describes ''what'' shall be done, which change shall happen. It does not fix ''how'' this is achieved. The latter happens by assigning a ''Procedure'' to the Step. There are different types of Procedures: manual instructions, a refined proceeding or execution of machine operations (invocation of a service). Refined proceedings then may be described with UBPML Steps or BPMN- resp. UML-activities.}}
| [[UML]] standard
|-
| [[Image:UBPMLProcess.png]]
| {{T|Ein Prozess ist eine nach inhaltlichen Kriterien  zusammengestellte, im weiteren aber beliebige Menge von Schritten, die zu durchaus verschiedenen Schrittklassen gehören können. Ein Prozeß ist insbseondere nicht das gleiche wie eine Schrittklasse. Das Beispiel zeigt eine Prozeßinstanz, die sowohl auf einen Schritt verweist,als auch auf eine Schrittklasse. Der Verweis zur Schrittklasse bedeutet, daß alle Instanzen dieser Klasse (Klassen Extension) zum Prozeß gehören. |A Process is set of step classes assembled by criteria with regards to content. These steps may belong to quite different Step classes. Specifically, a Process is not the same as a Step class. The example shows a Process instance referring to both a Step instance as well as a Step class. The reference to Step class denotes that all instances of that class (class extent) belong to the Process.}}
| [[UML]] standard
|-
|-
| [[Image:UBPMLStepClassWithConstellations.png]]
| [[Image:UBPMLStepClassWithConstellations.png]]
| A step is the explicitly performed change between an initial and a final constellation
| {{T|Jedem Schritt ist genau eine ''initiale'' Konstellation zugeordnet, sowie eine oder mehrere finale, sich wechselseitig ausschließende Konstellationen. Die Verbindungspfeile sind notationell entlehnt aus Zustandiagrammen (Transitionen) und heißen hier ''Transformationen''.|Each Step is associated with exactly one ''initial'' Constellation, as well as at least one but possibly several ''final'', mutual exclusive ones. The relationship arrows are borrowed from state transition diagrams (transitions) and named ''Transformation'' here.}}
| specific UML usage conforming to standard
| UBPML
|-
|-
| [[Image:UBPMLStepObjectWithConstellations.png]]
| [[Image:UBPMLStepObjectWithConstellations.png]]
| Same as above, but with instances instead of classes
| {{T|Eine Instanz eines Schrittes verbunden mit Konstellations-Instanzen. Diese Notation ist bpsw. in Projekt-Diagrammen verwendbar.|An instance of a Step connected to Constellation instances. This notation is useful e.g. in project diagrams.}}
| specific UML usage conforming to standard
| UBPML
|-
|-
| [[Image:UBPMLConstellationClassAggregate.png]]
| [[Image:UBPMLConstellationClassAggregate.png]]
|
| {{T|Stellt die Details einer Konstellation als Aggregation dar: eine Konstellation besteht aus Klassen in einem bestimmten Zustand, diese Klassen werden dargestellt.|Shows the details of an constellation as an aggregation: a Constellation consistsof classes in a certain state, these classes are shown.}}
| extension to UML
| UBPML
|-
|-
| [[Image:UBPMLConstellationObjectAggregate.png]]
| [[Image:UBPMLConstellationObjectAggregate.png]]
| A constellation is an aggregation of certain objects within certain states
| {{T|Stellt die Details einer Konstellations-Instanz als Aggregation dar|Shows the details of a Constellation instance as an aggregation}}
| extension to UML
| UBPML
|-
|-
| [[Image:UBPMLConstellationClassPane.png]]
| [[Image:UBPMLConstellationClassPane.png]]
| An alternative notation for a constellation
| {{T|Alternative Darstellungsweise der Details einer Konstellation, entspricht der vorigen Darstellung als Aggregation.|Alternative way of showing the details of a Constellation, corresponds to the previous presentation as an aggregation.}}
| extension to UML
| UBPML
|-
|-
| [[Image:UBPMLConstellationObjectPane.png]]
| [[Image:UBPMLConstellationObjectPane.png]]
|
| {{T|Stellt die Details einer Konstellations-Instanz alternativ dar|Alternative way of showing the details of a Constellation instance}}
| extension to UML
| UBPML
|-
|-
| [[Image:UBPMLStepWithClassesInState.png]]
| [[Image:UBPMLStepWithClassesInState.png]]
| Constellations can be shown in detail
| {{T|Anstelle der Konstellationen können auch die konstituierenden Klassen in einem bestimmten Zustand direkt mit dem Schritt verknüpft werden. Dies ist nur eine Vereinfachung in der Darstellung, implizit werden hierdurch ebenfalls (anonyme) Konstellationen definiert. Wird eine Klasse in einem bestimmten Zustand hierbei mehrfach in unterschiedlicher Bedeutung referenziert, so sind Rollennamen zur Unterscheidung zu verwenden.|Instead of showing a Constellation the constituting classes in a certain state are directly connected to the Step. This is just a simpler way of presentation, there are implicitly (anonymous) Constellations defined, too. If a class in a certain state is referenced multiply in different roles, the rolenames are used to ditinguish this.}}
| UML standard
| UBPML
|-
|-
| [[Image:UBPMLStepWithClassesInStateAlternativeOutcome.png]]
| [[Image:UBPMLStepWithClassesInStateAlternativeOutcome.png]]
| Steps can have different (mutually exclusive) final constellations; individual classes/instances may be shared by these constellations
| {{T|Da Ergebnisklassen in mehreren Zielkonstellationen auftreten können, müssen diese im Falle der alternativen Darstellung zugeordnet werden können. Dies erfolgt in Form der Angabe der jeweiligen Zielkonstellation als Bedingung an der Relation.|Since one and the same resulting class might exist within several target Constellations, the respective Constellations can be declared as relationship conditions.}}
| UML standard
| UBPML
|-
|-
| [[Image:UBPMLStepAttributes.png]]
| [[Image:UBPMLStepAttributes.png]]
| All standard UML notation is valid, e.g. constraints
| {{T|Da Schritte auch Klassen sind, können sie wie diese natürlich auch Attribute aufweisen. Die Befüllung der Attribute zu Beginn und zum Ende kann an den Transformations-Relationen angegeben werden.|Since Steps are classes, of course they may contain attributes. The initial and final values of these attributes at the beginning and end of the transformation can be specified at the transformation relations.}}
| UML standard
| [[UML]] standard
|-
| [[Image:UBPMLStepWithTools.png]]
| {{T|Schritte können als Klassen auch auf weitere Klassen oder Objekte verweisen, die nicht verändert werden und mit denen kein primärer Informationsaustausch stattfindet. Solche Objekte sind typischerweise Werkzeuge und andere Hilfsmittel.|Steps as classes can refer to further classes or objects, which are not changed and no primary information flow takes place. Such objects are typically tools or further supporting material.}}
| [[UML]] standard
|-
|-
| [[Image:UBPMLInstantiation.png]]
| [[Image:UBPMLInstantiation.png]]
|  
| {{T|Durch Angabe einer Multiplizität von 1 am initialen Transformationspfeil auf Seite des Schrittes wird ausgesagt, daß zu jeder Instanz einer Startkonstellation genau ein Schritt existieren soll. Damit wird ausgedrückt, daß automatisch eine Verarbeitung initiiert wird. Alternativ kann durch Angabe einer Zeitfolge (bspw. "jeder 1 Montag im Monat") an einem Timersymbol eine Instantiierung spezifiziert werden, die zeitabhängig erfolgt. Sinnvoll ist dies etwa für Verarbeitungschritte, die eine Prüfung des Vorhandenseins des Rohmaterials beinhalten.|A multiplicity of 1 at the initial transformation arrow at the side of the Step says, that for each initial Constellation instance exactly one Step shall exist. In other words, the processing is initiated automatically. Alternatively, by declaring a sequence of points in time (e.g. "1st monday of each month" ) at a timer symbol, a automatically recurring instantiation is defined. E.g., this is useful if the existence of initial raw material is desired.}}
|  
| [[UML]] standard/UBPML
|-
|-
| [[Image:UBPMLProblemStateConditions.png]]
| [[Image:UBPMLProblemStateConditions.png]]
|  
| {{T|Dieses Symbol ordnet eine Fehlerzustands-Bestimmung einer beliebigen Klasse eines UML-Modells zu und stellt lediglich eine vereinfachte Notation von UML Bedingungen dar. Durch Zuordnung dieser Bedingungen zu Schritten können auch abgestuft problematische - und nicht bloß fatale - Verarbeitungszustände festgelegt und damit auswertbar gemacht werden.|This symbol associates an error state condition to an arbitrary class of a UML model, basically it is just a simplified notation of a UML condition. By associating such conditions to Steps also gradually problematic - and not just fatal - processing conditions can be expressed and made analyzable.}}
|  
| UBPML
|-
|-
| [[Image:UBPMLProblemStates.png]]
| [[Image:UBPMLProblemStates.png]]
|  
| {{T|Mögliche Problem-Zustände.|Possible problem states}}
|  
| UBPML
|-
|-
| [[Image:UBPMLResponsibilities.png]]
| [[Image:UBPMLResponsibilities.png]]
|  
| {{T|Durch Zuordnung eines ''Actors'' zu Verarbeitungsschritten wird dessen Verantwortung ausgedrückt. Es stehen unterschiedliche Verantwortungsarten zur Verfügung.|By attaching ''Actors'' to processing steps it's responsibility is expressed. There are different types of responsibility available.}}
|  
| UBPML
|-
|-
| [[Image:UBPMLResponsibilityTypes.png]]
| [[Image:UBPMLResponsibilityTypes.png]]
|  
| {{T|Mögliche Verantwortungsarten.|Possible responsibility types.}}
|  
| UBPML
|-
|-
<!--
| [[Image:UBPMLActorsAndSchedule.png]]
| [[Image:UBPMLActorsAndSchedule.png]]
| Of course actors and timing constraints can be placed here; optionally with nice symbols
| Of course actors and timing constraints can be placed here; optionally with nice symbols
Line 114: Line 133:
| UML standard
| UML standard
|-
|-
-->
| [[Image:UBPMLClassInStateInheritance.png]]
| [[Image:UBPMLClassInStateInheritance.png]]
|
| {{T|Auch Klassen in einem bestimmten Zustand können voneinander abgeleitet werden. Dies bedeutet die Festlegung eines Unter-Zustands.|Also classes in a certain state are derivable from each other.}}
| extension to UML
| [[UML]] standard
|-
|-
<!--
| [[Image:UBPMLObjectInStateInheritance.png]]
| [[Image:UBPMLObjectInStateInheritance.png]]
|
|  
| extension to UML
| UBPML
|-
|-
-->
| [[Image:UBPMLStepInheritance.png]]
| [[Image:UBPMLStepInheritance.png]]
| 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
| {{T|Als Klassen können auch Schritte voneinander abgeleitet werden.|As classes also Steps can be derived from each other.}}
| extension to UML
| UBPML
|-
|-
| [[Image:UBPMLFuzzyStates.png]]
| [[Image:UBPMLFuzzyStates.png]]
| Partially completed work can be shown in a natural way
| {{T|In Projekt-Diagrammen kann es hilfreich sein, die Erreichung eines Zustands partiell anzugeben.|It might be useful in project diagrams to express the completion of a state partially.}}
| extension to UML
| UBPML
|-
|-
| [[Image:UBPMLLocationAsState.png]]
| [[Image:UBPMLLocationAsState.png]]
|
| {{T|Auch "Orte" sind nur eine Sonderform eines Zustands, somit wird der Transfer eines Objekts völlig analog beschrieben.|Also "Locations" are just a special kind of States, therefore the transfer of an object is expressed in the same way.}}
| extension to UML
| UBPML
|-
|-
| [[Image:UBPMLLocationPane.png]]
| [[Image:UBPMLLocationPane.png]]
| A notation for location changes, as a special case of state changes
| {{T|Mit dieser Notationsform, die nur eine vereinfachende Darstellung ist, wird der Transfer von Objekten übersichtlich dargestellt. Die Darstellung ist bewußt ähnlich zu Swimlanes gehalten.|This notation, which is just a simplifying form, the transfer of objects is shown clearly. The presentation is intentionally similar to swimlanes.}}
| extension to UML
| UBPML
|}
|}
== Prozeß-Begriffe ==
[[Image:UBPMLProcessingTermsOverview.png|637px]]

Latest revision as of 20:15, 23 February 2011

UBPML Notation

Download UBPML Notation Overview in PDF format

Notation

Semantics

Conformity

UBPMLClass.png

A class

UML standard
UBPMLObject.png

An instance of a class

UML standard
UBPMLClassInState.png

A class in a certain state

UBPML
UBPMLClassInStateWithDefinition.png

A class in a certain state. The state itself is also declared here, and that by specifying a condition, which true and only true if that state is given.

UBPML
UBPMLObjectInState.png

An instance of a class in a certain state.

UML standard (seit 2.0 in Aktivitätsdiagrammen)
UBPMLConstellationClass.png

A certain system state, defined by a set of classes (i.e a Constellation) in certain states, as well as optionally additional constraints that have to be met by that classes and their relationships. A Constellation is a UML class, i.e. dervied from Class in the metamodel.

UBPML
UBPMLConstellationObject.png

An instance of a Constellation, i.e. a set of instances in certain states, which satisfy the constraints of the Constellation-class.

UBPML
UBPMLStepClass.png

A Step denotes a change (transformation) of the system from one constellation into possibly several alternative other ones. It is thereby the elementary unit of a planned change. A Step is a UML class, i.e. dervied from Class in the metamodel.

UBPML
UBPMLStepObject.png

An instance of a Step. Diagrams containing Step instances may serve to describe Projects. Thereby it is possible to describe Projects and Processes within one uniform notation.

UBPML
UBPMLProcedure.png

A Step describes what shall be done, which change shall happen. It does not fix how this is achieved. The latter happens by assigning a Procedure to the Step. There are different types of Procedures: manual instructions, a refined proceeding or execution of machine operations (invocation of a service). Refined proceedings then may be described with UBPML Steps or BPMN- resp. UML-activities.

UML standard
UBPMLProcess.png

A Process is set of step classes assembled by criteria with regards to content. These steps may belong to quite different Step classes. Specifically, a Process is not the same as a Step class. The example shows a Process instance referring to both a Step instance as well as a Step class. The reference to Step class denotes that all instances of that class (class extent) belong to the Process.

UML standard
UBPMLStepClassWithConstellations.png

Each Step is associated with exactly one initial Constellation, as well as at least one but possibly several final, mutual exclusive ones. The relationship arrows are borrowed from state transition diagrams (transitions) and named Transformation here.

UBPML
UBPMLStepObjectWithConstellations.png

An instance of a Step connected to Constellation instances. This notation is useful e.g. in project diagrams.

UBPML
UBPMLConstellationClassAggregate.png

Shows the details of an constellation as an aggregation: a Constellation consistsof classes in a certain state, these classes are shown.

UBPML
UBPMLConstellationObjectAggregate.png

Shows the details of a Constellation instance as an aggregation

UBPML
UBPMLConstellationClassPane.png

Alternative way of showing the details of a Constellation, corresponds to the previous presentation as an aggregation.

UBPML
UBPMLConstellationObjectPane.png

Alternative way of showing the details of a Constellation instance

UBPML
UBPMLStepWithClassesInState.png

Instead of showing a Constellation the constituting classes in a certain state are directly connected to the Step. This is just a simpler way of presentation, there are implicitly (anonymous) Constellations defined, too. If a class in a certain state is referenced multiply in different roles, the rolenames are used to ditinguish this.

UBPML
UBPMLStepWithClassesInStateAlternativeOutcome.png

Since one and the same resulting class might exist within several target Constellations, the respective Constellations can be declared as relationship conditions.

UBPML
UBPMLStepAttributes.png

Since Steps are classes, of course they may contain attributes. The initial and final values of these attributes at the beginning and end of the transformation can be specified at the transformation relations.

UML standard
UBPMLStepWithTools.png

Steps as classes can refer to further classes or objects, which are not changed and no primary information flow takes place. Such objects are typically tools or further supporting material.

UML standard
UBPMLInstantiation.png

A multiplicity of 1 at the initial transformation arrow at the side of the Step says, that for each initial Constellation instance exactly one Step shall exist. In other words, the processing is initiated automatically. Alternatively, by declaring a sequence of points in time (e.g. "1st monday of each month" ) at a timer symbol, a automatically recurring instantiation is defined. E.g., this is useful if the existence of initial raw material is desired.

UML standard/UBPML
UBPMLProblemStateConditions.png

This symbol associates an error state condition to an arbitrary class of a UML model, basically it is just a simplified notation of a UML condition. By associating such conditions to Steps also gradually problematic - and not just fatal - processing conditions can be expressed and made analyzable.

UBPML
UBPMLProblemStates.png

Possible problem states

UBPML
UBPMLResponsibilities.png

By attaching Actors to processing steps it's responsibility is expressed. There are different types of responsibility available.

UBPML
UBPMLResponsibilityTypes.png

Possible responsibility types.

UBPML
UBPMLClassInStateInheritance.png

Also classes in a certain state are derivable from each other.

UML standard
UBPMLStepInheritance.png

As classes also Steps can be derived from each other.

UBPML
UBPMLFuzzyStates.png

It might be useful in project diagrams to express the completion of a state partially.

UBPML
UBPMLLocationAsState.png

Also "Locations" are just a special kind of States, therefore the transfer of an object is expressed in the same way.

UBPML
UBPMLLocationPane.png

This notation, which is just a simplifying form, the transfer of objects is shown clearly. The presentation is intentionally similar to swimlanes.

UBPML
Retrieved from "https://wiki.ubpml.org/index.php?title=UBPML_Referenz&oldid=283"