Chapter 3 Building a requirements model
The General page of a business rule property sheet displays the following properties:
| Property | Description |
|---|---|
| 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 of the rule |
| Stereotype | Sub-classification used to extend the semantics of an object without changing its structure. It can be predefined or user-defined |
| Type | Constraint, definition, fact, formula, requirement or validation |
You can define several types of business rules in a requirements model:
| Type | Description | Example |
|---|---|---|
| Constraint | Additional check constraint on a value | The start date should be inferior to the end date of a project |
| Definition | Properties of an object in the requirements model | A customer is a person identified by a name and an address |
| Fact | Certainty, existence in the requirements model | A client may place one or more orders |
| Formula | Calculation used in the requirements model | The total order is the sum of all the order line costs |
| Requirement | Functional specification for the requirements model | The model is designed so that total losses do not exceed 10% of total sales |
| Validation | Constraint on a value in the requirements model | The sum of all orders for a client must not be greater than the client's allowance |
| Copyright (C) 2005. Sybase Inc. All rights reserved. |
| |