The Relationship Name phrases must not overlap and must be sized to view the entire phrase. Entity Formatting Entities must be formatted and colored for ease of readability. Entity Type Fill Data An entity that will become a data table. A data entity – contains the application’s core attributes. The resulting pale yellow transactional table will be one to which the users input and/or retrieve data from on a regular basis. The entity Code An entity that will become a code table. – will contain repeatedly used data values that fall within the management of the application administrative team. A code entity often populates the List of Value (LOV) fields in the light blue application and is used for data validation. A code entity must be named using the Entity Class Word, for example “CODE” CODE”. “PAY Processing An entity that will become an audit, report, or – temporary table. The entity will contain data stored for audit light peach purposes or that is reloaded daily, weekly, or on demand for some business function. Table 6 Entity Colors – Logical Model Diagram Entity Relationship Placement For diagrams to be legible the entity relationship lines should be placed as cleanly as possible. The preferred line placement is top to bottom (crow’s feet pointing down). If this is not possible in all cases then an optional placement is with lines from left to right (crow’s feet pointing to the right). A simple example of a Logical Model Diagram is displayed on the next page. The following recommendations are offered in order of precedence. Readability is the goal. Whenever possible, place entities so that the relationship lines do not cross an entity box. Place entities to avoid crowding relationship names so that the name is in white space. Place related entities near each other to avoid relationship lines crossing the entire diagram. It is better for a line to cross an entity than to use bent lines over a lot of space. Avoid crossing relationship lines if possible. Point crow’s feet to the right (East) and/or down (South). In other words, the point “three prongs” point to the right and/or down. Minimize the use of bent relationship lines. Straight lines are preferred but bent lines are acceptable to avoid crossing entities and relationship lines. Bent lines are not acceptable if they travel from one side of the diagram to the other.
The Relationship Name phrases must not overlap and must be sized to view the entire phrase. Entity Formatting Entities must be formatted and colored for ease of readability. Entity Type Fill Data – An entity that will become a data table. A data entity contains the application’s core attributes. The resulting transactional table will be one to which the users input and/or retrieve data from on a regular basis. pale yellow Code – An entity that will become a code table. The entity will contain repeatedly used data values that fall within the management of the application administrative team. A code entity often populates the List of Value (LOV) fields in the application and is used for data validation. A code entity must be named using the “CODE” Entity Class Word, for example “PAY CODE”. light blue Processing – An entity that will become an audit, report, or temporary table. The entity will contain data stored for audit purposes or that is reloaded daily, weekly, or on demand for some business function. light peach Table 6 – Entity Colors Logical Model Diagram Entity Relationship Placement For diagrams to be legible the entity relationship lines should be placed as cleanly as possible. The preferred line placement is top to bottom (crow’s feet pointing down). If this is not possible in all cases then an optional placement is with lines from left to right (crow’s feet pointing to the right). A simple example of a Logical Model Diagram is displayed on the next page. The following recommendations are offered in order of precedence. Readability is the goal. Whenever possible, place entities so that the relationship lines do not cross an entity box. Place entities to avoid crowding relationship names so that the name is in white space. Place related entities near each other to avoid relationship lines crossing the entire diagram. It is better for a line to cross an entity than to use bent lines over a lot of space. Avoid crossing relationship lines if possible. Point crow’s feet to the right (East) and/or down (South). In other words, the “three point prongs” point to the right and/or down. Minimize the use of bent relationship lines. Straight lines are preferred but bent lines are acceptable to avoid crossing entities and relationship lines. Bent lines are not acceptable if they travel from one side of the diagram to the other.
STD-07092501.4.0.docx