Document Revision

This template is used to store references to files containing a revision of an ExternalDocument.

Document

Small to medium block of text – eg. a chapter.

Definition

A definition is used to give a long precise definition of a specific subject.

Decision:DMN

In Decision Model and Notation (DMN), the “Decision” symbol is used to represent a point in the decision-making process where a choice is made based on the available data and knowledge. A Decision element represents a logical outcome of the decision-making process.

The Decision Template is used in the Decision Requirements Diagram and is a part of the Decision Model Notation (DMN) from OMG.

 

 

 

Decision

A branching mechanism that determine the possible paths of execution based on user specified conditions.

Data Type

In the context of a Class Diagram, a datatype is a specialized kind of classifier that represents a simple, non-composite type of data. It is used to define the types of attributes, parameters, and return values for classes and their operations. Unlike classes, datatypes typically don’t have operations or behaviors associated with them, focusing primarily on the structure of the data.

When creating a Class Diagram, you can use predefined datatypes (provided by the modeling tool or the underlying modeling language, such as UML) or define your own custom datatypes to represent specific data structures needed for your system. These custom datatypes can then be used as templates for defining the types of attributes or operation parameters and return values in your classes.

For example, consider a Class Diagram for a software system that manages books in a library. You might define a custom datatype called “ISBN” to represent the International Standard Book Number format. In this case, the “ISBN” datatype can be used as a template for the “isbn” attribute in the “Book” class. This helps ensure consistent representation and interpretation of ISBN data across the system.

Data Relation

A DataRelation shows the relation between two data entities.

At each end of a DataRelation there is a DataEntity, which automatically appears in the ‘From’ and ‘To’ fields in the DataRelation dialog. The roles of the DataEntities can be described and the cardinality. If a one-to-many DataRelation is created, QualiWare Lifecycle Manager will automatically update the relevant DataEntity with a foreign key.