//Artefact:SoftwareBundle/com/sphenon/products/EMOS (5.1) - Usage/Development


Open URL 'http://www.sphenon.de' in browser


EM/OS Solution Modelling Guide
OOEM Models
OOEM Models (Object Oriented Enterprise Models) are a complete, fully functional specification of a quality business software solution.
They consist of:
  • Canvases (BSC, CJC, BMC and alike)

  • Components (UML)

  • Classes and State Machines (OOEM), defining a multitude of structural aspects of the solution, like business domain objects, database schema, programming and service interfaces, exchange formats, user interface dialogs and fields, plus behaviour like user interface micro transactions, class state transitions and protocols

  • Business Processes (UBPML)

  • Business Spaces and Landscapes

  • Definitions (Facts and Rules)

  • Properties and Stereotypes (XModel)

  • Integrated Multipurpose Documentation (Doclets)

  • User Interface Styling

  • Test Specifications

  • Technical Models (UML) and Construction Plans (OCP)

  • Target Language Code (Java)

The Modelling Guide
Visibility and Changability
Whether an item is visible or not is influenced by a variety of factors.
State Dependent Visibility
State Dependent Changability
Display Context Dependent Visibility
Presentation contexts Importance Tightness Attribute Stereotypes
Presentation of a Class contained in another Class
Importance, Tightness, Relationship canEdit, canDelete, canCreate, canSelect Samples: - contained class is always only editable within attributes @Class: Dependent and StrictlyOwned - contained class is sometimes editable within certain attributes, sometimes selectable within others @Class: EditableInplace @Attribute: XMVUI/EnableDefaultSelector == false then, an InplaceEditor is shown, which can be tuned via @Attribute: XMVUI/DisableCreate XMVUI/DisableSelect XMVUI/DisableEdit XMVUI/DisableDelete
Tree Views
Hierarchically organised data often shall be visualised in tree form.
Preview Texts