Book a Demo
SPARX SYSTEMS

The Custom Model

The custom model provides extensions to the basic UML objects through stereotypes to handle screen design, entities and requirements gathering.

Custom Model Overview

Custom model overview

Figure 1 : Overview

Example Custom Elements

Custom models provide a few extensions to the UML model and allow for some exploratory and non-rigorous experimentation with model elements and diagrams.

The following UML diagram presents an example of some of the common custom elements that Enterprise Architect supplies.

Example Custom Elements

Figure 2 : Example Custom Elements

Example Custom Elements

OM01-A: Screens
Screen design is supported through a stereotyped screen object and UI Controls. Use this model to design high level system prototypes.

Figure 3 : Screen Design

New Screen
Screen:

UI Control
GUIElement:

UI Control
GUIElement:

OM01-B: Requirements
System requirements may be modeled using stereotyped UML objects designed to capture requirements. These may then be linked back to use cases and components in the system to illustrate how a particular system requirement is met.

Figure 4 : Requirements

Ability to manage customers
Requirement:

Ability to receive an order
Requirement:

Connections
Realises link from usecase Use Case

System must be available 24 hours a day
Requirement:

Trash


Figure 5 : Trash

Entity

Entity: Possibly unwanted items