|
Name
|
The name of the item which should be clear and meaningful, and should convey the item's purpose to non-technical users
|
|
Code
|
The technical name of the item used for generating code or scripts, which may be abbreviated, and should not generally include spaces
|
|
Comment
|
Descriptive label for the rule
|
|
Stereotype
|
Sub-classification used to extend the semantics of an object.
|
|
Type
|
Specifies the nature of the business rule. You can choose between:
-
Constraint – a check constraint on a value. For example, "The start date should be inferior to the end date of a project." In a PDM, constraint rules attached to tables or columns are generated. If the DBMS supports multiple constraints, constraint rules are generated as separate constraint statements with the name of the rule.
-
Definition – a property of the element in the system. For example; "A customer is a person identified by a name and an address".
-
Fact – a certainty in the system. For example, "A client may place one or more orders".
-
Formula – a calculation. For example, "The total order is the sum of all the order line costs".
-
Requirement – a functional specification. For example, "The model is designed so that total losses do not exceed 10% of total sales".
-
Validation – a constraint on a value. For example, "The sum of all orders for a client must not be greater than that client's allowance". In a PDM, validation rules attached to tables or columns are generated as part of the primary constraint for the table or column.
|