Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Category:Object Teams Examples"
Line 10: | Line 10: | ||
* [[OTExample FlightBonus|FlightBonus]] - advanced, shows separation of use cases (flight booking vs. bonus) plus view-model separation on top of an OT/J implementation (simple UI) | * [[OTExample FlightBonus|FlightBonus]] - advanced, shows separation of use cases (flight booking vs. bonus) plus view-model separation on top of an OT/J implementation (simple UI) | ||
* [[OTExample OrderSystem|OrderSystem]] - advanced, shows three-layered domain logic (Stock, Reservations, Order) plus view-model separation on top of an OT/J implementation (complex UI) | * [[OTExample OrderSystem|OrderSystem]] - advanced, shows three-layered domain logic (Stock, Reservations, Order) plus view-model separation on top of an OT/J implementation (complex UI) | ||
+ | |||
+ | ===External examples=== | ||
+ | ''These examples are not part of the distribution and not hosted at Eclipse.org''. | ||
+ | |||
+ | * '''Company Hierarchy''' - technically ambitious example featuring two connected visualizations of a company hierarchy. The example exhibits a design where almost everything in the application is modeled using teams. The eaxmple show cases the following design features | ||
+ | :* using team inheritance for refining a complex structure | ||
+ | :* using the [[OTPattern/Connector|Connector]] pattern for binding a complex structure to the application | ||
+ | :* using roles from a library team as externalized roles | ||
+ | :* using teams for implementing dynamically switchable variants of the application (the adapted base classes being roles themselves). | ||
+ | Download: http://www.objectteams.org/examples/CompanyHierarchy.zip | ||
+ | |||
[[Category:Object Teams]] | [[Category:Object Teams]] |
Latest revision as of 15:22, 13 January 2013
Collection of some examples for Object Teams
The following examples are also shipped with the OTDT:
- Stopwatch - simplest, straight-forward view-model separation
- Observer - mostly simple, re-usable implementation of the Observer pattern, yet comprehensive coverage of many Object Teams concepts.
- ATM - simple, demonstrates the use of guard predicates (OTJLD §5.4)
- FlightBonus - advanced, shows separation of use cases (flight booking vs. bonus) plus view-model separation on top of an OT/J implementation (simple UI)
- OrderSystem - advanced, shows three-layered domain logic (Stock, Reservations, Order) plus view-model separation on top of an OT/J implementation (complex UI)
External examples
These examples are not part of the distribution and not hosted at Eclipse.org.
- Company Hierarchy - technically ambitious example featuring two connected visualizations of a company hierarchy. The example exhibits a design where almost everything in the application is modeled using teams. The eaxmple show cases the following design features
- using team inheritance for refining a complex structure
- using the Connector pattern for binding a complex structure to the application
- using roles from a library team as externalized roles
- using teams for implementing dynamically switchable variants of the application (the adapted base classes being roles themselves).
Download: http://www.objectteams.org/examples/CompanyHierarchy.zip
Pages in category "Object Teams Examples"
The following 3 pages are in this category, out of 3 total.