All of the cardinalities of the major entities can be determined from the interview or the forms. A numeric ClientID serves better. Optional Entities A classification of Equipment. This would also be a system-generated number. A computer, printer, or other piece of technology equipment that is in use. Would you track accounts payable?
Work done to resolve a SeviceRequest. The following diagram illustrates one possible solution. This could be the primary key. Ensure that the students label the data flows and entities correctly. In the present system, the computer name acts as a primary identifier.
Activity 5 — Primitive Diagram his model is constructed by following the narrative given in Exhibit 6.
Logon Multiple Values of Information i. None of the forms hint at a ClientID. Students, however, may come up with and be able to justify different divisions.
A piece of Equipment is made up of one or more EquipmentComponents that either have in the past or are now installed. The Enter New Client event could be placed in either subsystem; presumably the two subsystems will share data so that a client entered in one will be available in the other.
Case study CTTS milestone 06 process modeling
These two entities could be combined into one entity, but with their different uses, a case can be made for have two entities. The real problem with adding purchase orders to CTTS is that it opens the door on accounting functions. If you, the instructor, choose to do your own solution, it may be different, depending on your interpretation of the forms provided. Family Vacation Rentals Machine Name i.
As a number it would also consume less disk space as a foreign key casd related tables and would provide for faster joins. The following diagram illustrates one possible solution.
Case study CTTS milestone 06 process modeling – Tài liệu text
The diagram below includes foreign keys, assuming implementation in a relational database. The following stkdy matrix is one possible solution. Primary keys are shown at the top of the list of attributes and marked with PK. Studg 3 — Event Diagrams hese diagrams represent one possible implementation of the ten events in the EventResponse List Exhibit 6.
An EquipNum is a number that could be generated by the system and stays unchanged forever.
Each Configuration is associated with a particular Client. In the present system, the computer name acts as a primary identifier. Make sure students specify primary keys that uniquely identify the entities as well as use proper names for the keys.
This would also be a system-generated number. BarCode is the primary key for both EquipmentComponent and Inventory. A request for service on Equipment. But a long text field such as the client name would make a poor primary key for Client, consuming extra storage space, slowing down database operations, and probably requiring extra typing.
Would you track accounts payable? A component that has been checked into inventory A piece of information concerning software configuration for 66 Client and possibly for a piece of equipment.
Foreign keys are marked with FK and a number. Ensure that the students label the data flows and entities correctly. Because this does not apply to all records, a formal relationship would not have to be established. Work done to resolve a SeviceRequest. In most activities explanations for why things were done as they were have been provided to aid in your understanding of the solution. Would you also have payments? This could be the primary key. Vendor would be a parent table to PurchaseOrder, contributing the VendorID in a non-identifying relationship.
Each EquipmentComponent is a particular ComponentType.