Data models define how data or information is represented, as well as the dependencies and relationships between them.
There are two types of data models: classes and enumerations.
Enumerations are used to define lists of possible choices in a given context. For example, when a customer wants to get a refund, the system can offer them to choose between a cash refund and a check refund: these two options can be recorded in the Refund Type data model as an enumeration.
Classes are used to describe data models with one or more distinct attributes. For example, it is in the User class that we indicate which attributes a user is made of: an Identifier, a Password, a First Name, a Last Name, and a Role. ReqBuilder allows you to define relationships between different data models according to UML modeling principles.
In the example below, two relationships are defined for the « Service » data model:
- Multiple services (multiplicity *) for one company (multiplicity 1), which means that there can be multiple services for the same company.
- One dispute (multiplicity 1) for one service (multiplicity 1), which means that a dispute can be associated with one service. This relationship is not modifiable at the « Service » data model level, but at the « Litigation » level.
Reminder: ReqBuilder is designed for analysts with knowledge of functional analysis based on the UML description language.
Diagram #
The graphical representation of all data models is available at the top of the data model list: it visually presents the content of each class and enumeration as well as the relationships that exist between them.
Data Model List #
The data model list provides information on any Inheritances, the number of Attributes, and the Relationships corresponding to each one.
