Modeling Project Data
HOPEX Application Design provides the tools required to model logical data via class diagrams and data models.
Using data area and data views concepts, you can detail a logical data structure in a particular use context.
For more details on creating and updating a data model, see "The data model".Logical View Concepts
UML package
A package is used to represent the static structure of a system, particularly the types of objects handled in the system, their internal structure, and the relationships between them.
The package is an owner element. It provides a namespace for the elements that it consolidates.
The package allows you to classify elements referenced in a project. You can create sub-packages in a package to classify objects in finer detail, for example actors of a project.
Urgent purchase requests are provided to process purchase of spare parts and boat rental requests. In both of these cases, users are actors of the purchasing domain.
Class diagrams are used to graphically represent the elements of a package.
For more details on building a class diagram, see "The Class Diagram".
See also "Structure and Deployment Diagrams", page 65.
Data models
Like a package, a data model is used to represent the static structure of a system, particularly the types of objects handled in the system, their internal structure, and the relationships between them.
Data diagrams are used to graphically represent the elements from a data model.
For more details on creating and updating a data model, see "The data model", page 25.
Example
The data model of the "Purchase Request Automation" project is presented below.
The application manages purchase requests, orders and product stock levels in each of the representation offices.
A centralized catalog of products and suppliers is installed.
Contracts with referenced suppliers are also accessible from the application.
For more details on creating and updating a data model, see "Modeling data". Data areas
A Data Area represents a restricted data structure dedicated to the description of a software Data Store (see Using Data Stores). It is made of classes and/or data views and can be described in a Data Area Diagram.
A logical data area is used to define a logical data structure made up of classes and data views.
A logical data domain is owned by a package and can reference objects held in other packages.
You can define the access mode (creation, deletion, etc.) to the objects referenced by a data area by integrating them as components of the data area.
During integration with HOPEX Database Builder, a corresponding physical structure can be defined via a physical data area. It is made up of tables and table views.
Example
The following data area diagram represents a data structure relating to Orders; it describes classes and their relationships in a Whole/Part formalism.
To address these specific use cases, you can create Data Views in which you can see and modify the scope covered by the classes.
Logical data view
A data view represents the scope covered by an element of a data model or a data area. A data view is based on the selection of several classes connected in the specific context of the view.
Data store
A data store references, in a process or an application system, persistent data defined in a data area.
See Using Data Stores.