JOSIF Main Page | JOSIF Guidebook | Modeling | Interface Design
| Table of Contents | ||||||||
|---|---|---|---|---|---|---|---|---|
|
...
The diagam below shows a simplified meta-model of a TIP interface package.
Interface
...
Interface Meta-Model Description of the TIP Interface Meta-Model
Interface Project vs Dependencies
The scope of an interface project is a set of ABEs (Aggregated Business Entities). For each ABE, the whole package has to be part of the interface project.
The numbers of ABEs associated with an Interface can be zero for pure task-centric interfaces, like an Inventory interace, 1 or more for entity-centric interfaces.
...
- A parent class for a class present in the interface project. Eg. BI for Trouble Ticket
- Relationships/ associations. If an object in the interface scope references other objects, then these objects would be part of the needed references.
- Composition. A class (entity or datatype) used by composition, for instance for an attribute.
- Parameters that will be used by the operational model. A class or datatype used as a parameter of an operation of this interface.
General Patterns
General Patterns Description of the general patterns applicable to TIP interface modeling. Only the patterns applicable to the current version of JOSIF are described in this section.
General Patterns - Future
General Patterns - Future Description of the general patterns applicable to TIP Interface modeling and planned for coming releases of JOSIF.
Shared Framework Model
Shared Framework Model Description of the Common and Internal Models of TIP Framework