[keyword] !convention

[note] The «!render» stereotype on an operation or method indicates that it returns a Drupal render array portion for a page (or form).

Applies to

[note] The stereotype «!by» is just shorthand for «!encapsulated by»

Applies to

[note] Webel: «!logical» Components used for convenient "parasitic" graphical groupings may be shown "unwrapped" in diagrams that reveal the Component Realizations to the logically (and otherwise graphically) grouped participants.

Applies to

[note] The «!page» stereotype on an operation or method indicates that it returns a Drupal render array for a page.

Applies to

[note] A «!new» stereotype assigned to a Usage from a source Classifier (or a creation method) means an instance of the target Classifier is created directly (instead of fetching an Interface product via a factory) and assigned to a «!chosen» Interface var.

Applies to

[note] It is strongly recommended that implementation Classes use full private property vars with protected lazy creation/configuration methods (rather than just local variables) ! It has many advantages and is UML friendly ! (TIP: use code template expansion.)

Applies to

Please when working with OOE = Object Oriented Examples = One Of Each code like this, with explicit private Interface variables that are "lazily" (as needed) assigned implementations and configured in protected lazy creation/configuration methods. And please only then access the Interfaces via their matching lazy methods:

[note] The «!new» stereotype on a Usage from a Factory class (or a method of a Factory class, or both) to a concrete implementation Class for an Interface product indicates that the Factory (by default) uses that implementation Class as the product.

Applies to

If the factory is subclassed and a creation method is overridden to use a different implementation class, an additional «!new» Usage may be used from the subclass (or the overridden subclass method).


Usages from methods/operations indicate clearly exactly which implementation Class is used for which Interface product, however there are certain graphical disadvantages:

[note] The «!product» stereotype on a Property variable typed by an Interface indicates that a concrete implementation Class is supplied for it by a factory.

Applies to

From OoeBridge:

[note] The «!default» stereotype on a Usage from a composite structure compartment Property symbol to a Class indicates it is assigned as the default (usually in a lazy creator of the same name as the Property) by the managing class.

Applies to

From OoeBridge:

[note] The «!chosen» stereotype on a Property variable typed by an Interface indicates that a default concrete implementation Class is chosen for it by the managing Class (not via a factory), usually in a lazy creator method of the same name as the Property.

Applies to

From OoeBridge:

[note] An analysis @Interface class diagram may show a "circuit" formed by an analysis @Interface/@Component pair and a design Interface/Class pair with Generalizations on opposing sides, and the «!Trace» and the «!encapsulated by» on opposing sides.

Applies to

[note] Analysis «!local» variables usually represent variables within a method that hold a specific implementation Component, they do not correspond to Class property variables ($this->property) and do not appear in the reverse-engineered PHP design(ed) classes.

Applies to
Subscribe to RSS - !convention