Archives: Templates

Templates and model types in the QualiWare platform.

Table Scema

Description of this template will be available soon.

Table

A Table is a basic component in a Relational Diagram that represents a collection of related data organized in rows and columns. Tables are the fundamental building blocks of a relational database, and they provide a structured way of storing and organizing data, making it easy to access, query, and manipulate.

Tables can be related to each other through foreign key constraints, creating a relational schema that models the interrelationships between different entities in the system being represented.

Example: In a Relational Diagram for a system that manages a university, you might have a table called “Students” that stores information about all the students enrolled in the university. The table might have columns such as “id”, “name”, “major”, “email”, and “enrollment_date”, among others. Each row in the “Students” table represents a single student record, with values for each of the corresponding attributes. The “id” column serves as the primary key for the table, uniquely identifying each student record. Other tables in the database, such as “Courses” and “Enrollments”, can be related to the “Students” table through foreign key constraints, creating a relational schema that models the interrelationships between different entities in the university system.

Substitution

Description of this template will be available soon.

Subscription

Description of this template will be available soon.

Strategic Alignment

The template is used to model a connection from a strategic object to another object on a diagram, e.g. from a goal to a process.

 

Stereotype

A Stereotype is a template in a Class Diagram that serves as an extension mechanism for adding domain-specific or custom semantics to model elements. Stereotypes allow you to classify or categorize elements in the model according to specific roles, characteristics, or behaviors relevant to your domain or context. They are typically used in combination with profiles, which define a collection of stereotypes, tagged values, and constraints tailored for a specific domain or application.

Example: In a Class Diagram for a system that manages an e-commerce platform, you might create a profile called “ECommerceDomain” that includes stereotypes such as “Product”, “Customer”, “Order”, and “PaymentMethod”. You can then apply these stereotypes to the corresponding classes in your model to provide domain-specific context and semantics. For instance, you could apply the “Product” stereotype to a class called “Item” to indicate that the class represents a product in the e-commerce domain. This additional context helps clarify the role and purpose of the “Item” class in your system.