The principal features of the elementary processes and process interactions with entity types, attribute types, and relationship types are examined and documented by the JAD workshop participants.
¤ Entity Type Life Cycle Analysis
Entity type life cycle analysis is performed for those entity types that have complicated structures, such as many subtypes, or that are involved with many processes. For each of these entity types, the user design team determines the entity states that apply to it. Next, the elementary processes that cause each state change are identified. This may reveal missing elementary processes, inaccurate process definitions and entity types that are not well defined.
To complete the analysis, all elementary processes are reviewed to determine whether they involve the selected entity type. Also determined are those attribute types and relationship types whose values can identify the entity state. If none exist, then a status attribute type is defined.
ð Updates deliverable D3.4.2 Process/Entity Type Matrix.
ð Updates deliverable D3.4.7 Entity State Diagram.
» Creates deliverable D3.4.8 Entity State Matrix.
ð Updates deliverable D3.2.1 Entity Type Definition.
ð Updates deliverable D3.3.1 Process Definition.
¤ Process Logic Diagram Development
For each elementary process the user design team identifies the entity types to be created/modified/terminated by the process, the relationship types that are associated/disassociated by the process, the selection criteria for the entities, and existence checks for entity modification/termination or disassociation. As the actions are identified, they are numbered to indicate the logical sequence in which they may occur. The action number will show a feasible sequence of actions, though it is not necessarily the only possible sequence. The process logic diagram is drawn on top of (over) a subset of the entity relationship diagram.
» Creates deliverable D3.4.4 Process Logic Diagram.
¤ Process Action Diagram Development
The logic of each elementary process is then expressed in the form of a process action diagram. This is built by including all actions shown on the process logic diagram in the specified sequence. In addition, control statements are inserted in the action diagram to control the execution of conditional groups or repeating groups of actions,
» Creates deliverable D3.4.9 Process Action Diagram.
¤ Attribute Action Identification
Attribute actions are identified and added to the process action diagram. Business algorithms are defined in the form of process action blocks. The information repository should be checked for definitions of business algorithms that can be used and reused in the proposed system.
» Creates deliverable D3.2.4 Business Algorithm.
¤ Exception Situation Consideration
Exception situations and their subsequent activities are considered and documented in the process action diagram.
ð Updates deliverable D3.4.9 Process Action Diagram.
¤ Action Diagram Review
The user design team reviews the action diagrams to ensure that the process logic conforms with the process definition and other aspects of the process models and that all entity types, relationship types and attribute types appearing within the process logic diagram and process action diagrams are incorporated in the entity relationship model.
ð Updates deliverable D3.2.3 Entity Relationship Diagram.
ð Updates deliverable D3.2.1 Entity Type Definition.
Next : A11.1.4
Previous : A11.1.2
Activity Overview : A11.1
Stage Overview : Rad User Design Stage
Overview : Table of Contents