CTTS CASE STUDY MILESTONE 6 SOLUTION

The following diagram illustrates one possible solution. Activity 1 — Context Diagram his diagram is one possible solution based on the meeting transcript in Exhibit 2. A Client submits one or more ServiceRequests, which may related to a piece of Equipment. Some, but not all, of the configuration records could be associated with a piece of Equipment. Primary keys are shown at the top of the list of attributes and marked with PK. Optional Entities A classification of Equipment.

Ensure that the students label the data flows and entities correctly. In most activities explanations for why things were done as they were have been provided to aid in your understanding of the solution. A Client submits one or more ServiceRequests, which may related to a piece of Equipment. Activity 5 — Primitive Diagram his model is constructed by following the narrative given in Exhibit 6. The EquipmentComponent entity has ComponentNum as the primary key.

Case study CTTS milestone 06 process modeling

This would also be a system-generated number. These two entities could be combined into one entity, but with their different uses, a case can be made for have two entities.

ctts case study milestone 6 solution

The following tables contain the attributes identified from each form and the interview. Prepared by Gary B. A Client submits one or more ServiceRequests, which may related to a piece of Equipment.

O For purposes of class discussion, you may want to compare this syudy the Use Case Diagram created in Milestone 3. A component that has been checked into inventory A piece of information concerning software configuration for the Client and possibly for a piece of equipment.

  BOC GROUP OHMEDA CASE STUDY

Students should realize that the Parent-Child relationship found in PurchaseOrder and PurchaseOrderDetail will be present in any invoicing system and many other systems as well. Foreign keys are marked with FK and a number.

Students, however, may come up with and be able to justify different divisions. Would you track accounts payable?

BarCode is the primary key for both EquipmentComponent and Inventory.

Case Study CTTS – Milestone 04 Data Modeling Solution_图文_百度文库

Also remember that data flows are not allowed between entities. T Prepared by Gary B.

A classification of EquipmentComponent. Logon Multiple Values of Information i. If you will be doing Milestone 5 as a separate assignment, you may want to withhold this solution. Primary keys are shown at cts top of the list of attributes and marked with PK.

If you, the instructor, choose to do your own solution, it may be different, depending on your interpretation of the forms provided.

Case study CTTS milestone 06 process modeling – Tài liệu text

Mipestone piece of Equipment is made up of one or more EquipmentComponents that either have in the past or are now installed. The following completed matrix is one possible solution.

ctts case study milestone 6 solution

The Enter New Client event could be placed in either subsystem; presumably the two subsystems will mjlestone data so that a client entered in one will be available in the other.

  ANALYSE AF ESSAY HÆRVÆRK

Activity 1 — Context Diagram his diagram is one possible solution based on the meeting transcript in Exhibit 2.

ctts case study milestone 6 solution

Optional Entities A classification of Equipment. Family Vacation Rentals Machine Name i. Prepared by Gary B. Because this does not apply to all records, a formal relationship would not have to be established. A computer, printer, or other piece of technology equipment that is in use. Vendor would be a parent table to PurchaseOrder, contributing the VendorID in a non-identifying relationship.

Ensure that the students label the data flows and entities correctly. The diagram below includes foreign keys, assuming implementation in a relational database. The EquipmentComponent entity has ComponentNum as the primary key.

Activity 5 — Primitive Diagram his model is constructed by following the narrative given in Exhibit 6. Whether or not they identify the optional entities will depend on how they interpret the user requirements and on their experience level with database normalization.

However, Jeff Summers states that the computer name is sometimes changed.