Behavior diagrams are used to represent the « HMI presentation » part of the application to generate.

Two UML diagrams are used to model presentation objects:

• Use case diagrams
• Activity diagrams

3.4.1Screen process and use case diagrams

Use case diagrams represent interactions between actors, functional bundles and screen processes of the target application.

Figure 1 : “Use case” modeling

Design items

Dependence

 Actor

Package

 Use case

Stereotypes list

• PK_WEB

Packages which contain use cases must be contained within packages directly or indirectly descending from « PK_WEB » stereotyped packages.

Rules

• A package directly descending from a PK_WEB package must have a dependency with at least one « Actor ».

• A « PK_WEB » package name must not be empty and must be unique.

• A « Use case » name must not be empty and must be unique. Every « Use Case » must contain at least one « Activity ».

• Use cases can only be contained inside packages themselves contained within PK_WEB stereotyped packages.

• An activity can contain only one activity diagram.

• An « Actor » name must not be empty and must be unique. Actors are modeled as a « PK_ROLES» stereotyped package.

• As of version 3.5.0, dependencies can be defined between actors and use cases.

• A package directly or indirectly descending from a « PK_WEB » stereotyped package must not be stereotyped, and can only contain use cases or other packages.