[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).

Type:

Applies to
[UML Element] IFlagBanner
UML element type: Interface
«!analysis»
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML diagram type:

UML modelling domain:

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

Type:

Applies to
[UML Element] IFlagBanner
UML element type: Interface
«!analysis»
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML diagram type:

UML modelling domain:

[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.

Type:

Applies to
[UML Element] BybundleAbstractBuilder: child hierarchy (and logical grouping wrapper Component example)
UML element type: Component
«!analysis»
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML diagram type:

UML modelling domain:

This "logical" analysis wrapper Component is for graphical organisation only. It does not (in this case) change the logical grouped elements' ownerships, but it does indicate a possible future packaging.

,
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML diagram type:

UML modelling domain:

The "unwrapped" diagram for the logical grouping component, showing Component Realization relationships to the logically (and otherwise graphically/visually) grouped participants.

The @Component is still (in this case) in fact contained (owned by) the Package 'flagplus', because how it was moved (dragged) as a graphical symbol into another graphical Component symbol, in MagicDraw UML ! By contrast, in MagicDraw UML, if you drag a Packageable model element in the project browser instead of in a diagraminto a Component it will change ownership ! Both of these modes yield fully compliant UML diagrams.

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

Type:

Applies to
[UML Element] DemoPageController
UML element type: Component
«!refactor», «!wrapper»
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML diagram type:

UML modelling domain:

[UML Element] DemoArgumentsHelper
UML element type: Component
«!wrapper»
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML diagram type:

UML modelling domain:

[UML Element] DemoOfPageArguments
UML element type: Component
«!wrapper»
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML diagram type:

UML modelling domain:

Typically an OOE controlled project has a controller for a main page and a matching page menu item.

A specific project may add additional menu items (possibly for page controllers) for separate pages. In this demonstration, in addition to the main controlled welcome page for the argument extraction demos, there are 4 different sub menu items for 4 demonstration cases:

1. Demo of automatic page path argument extraction, via a Drupal hook in the .module file. Uses a basic IMenuItem.

2. Demo of page path argument extraction with some forced arguments, via a Drupal hook in the .module file. Uses a basic IMenuItem.

3. Demo of page path argument extraction for an OOE controlled page. Uses an IPageMenuItem and a page controller.

4. Demo of page path argument extraction with C. Skene's original PageController. Uses a basic IMenuItem.

,
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML diagram type:

UML modelling domain:

The best UML tools like MagicDraw UML are able to show inherited properties in composite structure diagrams. Here they are grouped for illustration purposes.

,
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML diagram type:

UML modelling domain:

In the best UML tools like MagicDraw UML one can show the structure compartment of Classes and Components and their composite structure as Property symbols in "hybrid" class or implementation diagrams. Here the inheritance of all major properties is shown.

[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.

Type:

Applies to
[UML Element] DemoOfPageArguments
UML element type: Component
«!wrapper»
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML diagram type:

UML modelling domain:

Typically an OOE controlled project has a controller for a main page and a matching page menu item.

A specific project may add additional menu items (possibly for page controllers) for separate pages. In this demonstration, in addition to the main controlled welcome page for the argument extraction demos, there are 4 different sub menu items for 4 demonstration cases:

1. Demo of automatic page path argument extraction, via a Drupal hook in the .module file. Uses a basic IMenuItem.

2. Demo of page path argument extraction with some forced arguments, via a Drupal hook in the .module file. Uses a basic IMenuItem.

3. Demo of page path argument extraction for an OOE controlled page. Uses an IPageMenuItem and a page controller.

4. Demo of page path argument extraction with C. Skene's original PageController. Uses a basic IMenuItem.

,
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML diagram type:

UML modelling domain:

The best UML tools like MagicDraw UML are able to show inherited properties in composite structure diagrams. Here they are grouped for illustration purposes.

,
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML diagram type:

UML modelling domain:

In the best UML tools like MagicDraw UML one can show the structure compartment of Classes and Components and their composite structure as Property symbols in "hybrid" class or implementation diagrams. Here the inheritance of all major properties is shown.

[UML Element] Drupal\ooe\Demo\Project
UML element type: Package
«!analysis»
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML diagram type:

UML modelling domain:

[UML Element] Drupal\ooe\Demo\Module
UML element type: Package
«!analysis»
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML diagram type:

UML modelling domain:

Please note, normally one would not show so many Associations to Classes/Components external to the focus Package in such a Package overview diagram; that is usually the job of the focus implementation Component diagram for each Component (such as for @OoeModule).

[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.)

Type:

Applies to
[UML Element] OoeBridge
UML element type: Component
«!wrapper»
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML diagram type:

UML modelling domain:

I have tried above to show some of the landscape of OOE beyond the OOE Project classes to which the bridge delegates most of the work, such as menu items, page controllers, and blocks. Each OOE Interface and Class is otherwise presented in easy-to-understand UML diagrams that mostly only show each element's nearest neighbour relationships.

[UML Element] Drupal\ooe\Demo\Module
UML element type: Package
«!analysis»
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML diagram type:

UML modelling domain:

Please note, normally one would not show so many Associations to Classes/Components external to the focus Package in such a Package overview diagram; that is usually the job of the focus implementation Component diagram for each Component (such as for @OoeModule).

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.

Type:

Applies to
[UML Element] AbstractFactory
UML element type: Component
«!wrapper»
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML diagram type:

UML modelling domain:

[UML Element] DemoOfPageArguments
UML element type: Component
«!wrapper»
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML diagram type:

UML modelling domain:

Typically an OOE controlled project has a controller for a main page and a matching page menu item.

A specific project may add additional menu items (possibly for page controllers) for separate pages. In this demonstration, in addition to the main controlled welcome page for the argument extraction demos, there are 4 different sub menu items for 4 demonstration cases:

1. Demo of automatic page path argument extraction, via a Drupal hook in the .module file. Uses a basic IMenuItem.

2. Demo of page path argument extraction with some forced arguments, via a Drupal hook in the .module file. Uses a basic IMenuItem.

3. Demo of page path argument extraction for an OOE controlled page. Uses an IPageMenuItem and a page controller.

4. Demo of page path argument extraction with C. Skene's original PageController. Uses a basic IMenuItem.

,
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML diagram type:

UML modelling domain:

The best UML tools like MagicDraw UML are able to show inherited properties in composite structure diagrams. Here they are grouped for illustration purposes.

,
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML diagram type:

UML modelling domain:

In the best UML tools like MagicDraw UML one can show the structure compartment of Classes and Components and their composite structure as Property symbols in "hybrid" class or implementation diagrams. Here the inheritance of all major properties is shown.

[UML Element] Demo
UML element type: Component
«!wrapper»
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML diagram type:

UML modelling domain:

Only those methods of the extended Components relevant to
the implementation by the Demo project are shown !

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.

Type:

Applies to
[UML Element] DemoOfPageArguments
UML element type: Component
«!wrapper»
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML diagram type:

UML modelling domain:

Typically an OOE controlled project has a controller for a main page and a matching page menu item.

A specific project may add additional menu items (possibly for page controllers) for separate pages. In this demonstration, in addition to the main controlled welcome page for the argument extraction demos, there are 4 different sub menu items for 4 demonstration cases:

1. Demo of automatic page path argument extraction, via a Drupal hook in the .module file. Uses a basic IMenuItem.

2. Demo of page path argument extraction with some forced arguments, via a Drupal hook in the .module file. Uses a basic IMenuItem.

3. Demo of page path argument extraction for an OOE controlled page. Uses an IPageMenuItem and a page controller.

4. Demo of page path argument extraction with C. Skene's original PageController. Uses a basic IMenuItem.

,
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML diagram type:

UML modelling domain:

The best UML tools like MagicDraw UML are able to show inherited properties in composite structure diagrams. Here they are grouped for illustration purposes.

,
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML diagram type:

UML modelling domain:

In the best UML tools like MagicDraw UML one can show the structure compartment of Classes and Components and their composite structure as Property symbols in "hybrid" class or implementation diagrams. Here the inheritance of all major properties is shown.

[UML Element] AbstractProject
UML element type: Component
«!wrapper»
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML diagram type:

UML modelling domain:

[UML Element] OoeBridge
UML element type: Component
«!wrapper»
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML diagram type:

UML modelling domain:

I have tried above to show some of the landscape of OOE beyond the OOE Project classes to which the bridge delegates most of the work, such as menu items, page controllers, and blocks. Each OOE Interface and Class is otherwise presented in easy-to-understand UML diagrams that mostly only show each element's nearest neighbour relationships.

[UML Element] Drupal\ooe\Demo\Module
UML element type: Package
«!analysis»
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML diagram type:

UML modelling domain:

Please note, normally one would not show so many Associations to Classes/Components external to the focus Package in such a Package overview diagram; that is usually the job of the focus implementation Component diagram for each Component (such as for @OoeModule).

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.

Type:

Applies to
[UML Element] OoeBridge
UML element type: Component
«!wrapper»
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML diagram type:

UML modelling domain:

I have tried above to show some of the landscape of OOE beyond the OOE Project classes to which the bridge delegates most of the work, such as menu items, page controllers, and blocks. Each OOE Interface and Class is otherwise presented in easy-to-understand UML diagrams that mostly only show each element's nearest neighbour relationships.

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.

Type:

Applies to
[UML Element] DemoOfPageArguments
UML element type: Component
«!wrapper»
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML diagram type:

UML modelling domain:

Typically an OOE controlled project has a controller for a main page and a matching page menu item.

A specific project may add additional menu items (possibly for page controllers) for separate pages. In this demonstration, in addition to the main controlled welcome page for the argument extraction demos, there are 4 different sub menu items for 4 demonstration cases:

1. Demo of automatic page path argument extraction, via a Drupal hook in the .module file. Uses a basic IMenuItem.

2. Demo of page path argument extraction with some forced arguments, via a Drupal hook in the .module file. Uses a basic IMenuItem.

3. Demo of page path argument extraction for an OOE controlled page. Uses an IPageMenuItem and a page controller.

4. Demo of page path argument extraction with C. Skene's original PageController. Uses a basic IMenuItem.

,
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML diagram type:

UML modelling domain:

The best UML tools like MagicDraw UML are able to show inherited properties in composite structure diagrams. Here they are grouped for illustration purposes.

,
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML diagram type:

UML modelling domain:

In the best UML tools like MagicDraw UML one can show the structure compartment of Classes and Components and their composite structure as Property symbols in "hybrid" class or implementation diagrams. Here the inheritance of all major properties is shown.

[UML Element] Drupal\ooe\Demo\Project
UML element type: Package
«!analysis»
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML diagram type:

UML modelling domain:

[UML Element] OoeBridge
UML element type: Component
«!wrapper»
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML diagram type:

UML modelling domain:

I have tried above to show some of the landscape of OOE beyond the OOE Project classes to which the bridge delegates most of the work, such as menu items, page controllers, and blocks. Each OOE Interface and Class is otherwise presented in easy-to-understand UML diagrams that mostly only show each element's nearest neighbour relationships.

[UML Element] Drupal\ooe\Demo\Module
UML element type: Package
«!analysis»
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML diagram type:

UML modelling domain:

Please note, normally one would not show so many Associations to Classes/Components external to the focus Package in such a Package overview diagram; that is usually the job of the focus implementation Component diagram for each Component (such as for @OoeModule).

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.

Type:

Applies to
[UML Element] IFlagBanner
UML element type: Interface
«!analysis»
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML diagram type:

UML modelling domain:

[UML Element] IMenuItemSet
UML element type: Interface
«!analysis»
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML diagram type:

UML modelling domain:

[UML Element] IMenuTabs
UML element type: Interface
«!analysis»
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML diagram type:

UML modelling domain:

[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.

Type:

Applies to
[UML Element] OoeBridge
UML element type: Component
«!wrapper»
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML diagram type:

UML modelling domain:

I have tried above to show some of the landscape of OOE beyond the OOE Project classes to which the bridge delegates most of the work, such as menu items, page controllers, and blocks. Each OOE Interface and Class is otherwise presented in easy-to-understand UML diagrams that mostly only show each element's nearest neighbour relationships.

[UML Element] DemoOfMenuTabs
UML element type: Component
«!wrapper»
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML diagram type:

UML modelling domain:

[UML Element] Drupal\ooe\Demo\Module
UML element type: Package
«!analysis»
UML Diagram
Click on the UML diagram to view it in a lightbox image viewer. You may then zoom in (or just open the image in a new web browser tab using the Download Original link to view large diagrams).

UML diagram type:

UML modelling domain:

Please note, normally one would not show so many Associations to Classes/Components external to the focus Package in such a Package overview diagram; that is usually the job of the focus implementation Component diagram for each Component (such as for @OoeModule).

Subscribe to RSS - !convention