Roles

Stereotype*

Classes that store data about a known identity
User, Account, Product, ShoppingCartItem, CreditCard, etc.
May contain simple, related methods
Created and managed by Regimes

*Entity

Roles

Culture*

Governs the UI
Exhibits a set of predefined behaviors
As dummy and ignorant as possible, no memory or state
Interprets user input and sends to a Representative
Can contain subcultures that exhibit different behaviors
List, ListItem, etc.
Can contain immigrant subcultures temporarily

*View

Roles

Representative*

Keeps Culture's state
If a Culture has a Stereotype instance, keeps that, too
Represents a Culture to the Regime
Every Culture breeds their own Representatives

*ViewModel

Roles

Regime*

Keeps and manages application's state in application layer
Breeds, manages, and operates on Stereotypes
May communicate with other Regimes through Diplomats
Delegates persistence to Undertakers
Lives as a Singleton
More complex apps can use two layers of Regimes


*Domain Model / Service

Roles

Undertaker*

Works at the infrastructure layer, persists state
Doesn't keep state, takes orders from the Regime
May include technology-specific code (e.g. WebSQL, LocalStorage, AJAX, WebSockets)
May utilize Satellites for keeping state in multiple technologies
Lives as a Singleton


*Repository

Roles

Diplomat*

Coordinates communication between Regimes.
Quasi-autonomous
Lives as a Singleton
On rare occasions, may coordinate communication between Representatives

 

*Event Manager

Roles

Satellite*

Abstracts a certain persistence technology
Persists serialized data
Mostly redundant

*Event Manager

Roles

Union*

Brings together contextually-similar roles that work together under an umbrella
Eases to see the big picture
Provides a clear file structure

*Package

The Team is important!

Armağan Amcalar 

Fatih Kadir Akın

Tarık Akyol

Murat Çorlu

WE WANT YOU!