CTTS CASE STUDY MILESTONE 5 SOLUTION

The following completed matrix is one possible solution. Would you also have payments? Suggest us how to improve StudyLib For complaints, use another form. 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. In the present system, the computer name acts as a primary identifier. As a number it would also consume less disk space as a foreign key in related tables and would provide for faster joins.

A system-generated large integer numeric value unique to each work record. All of the cardinalities of the major entities can be determined from the interview or the forms. A date field representing the date a component was purchased. Make sure students specify primary keys that uniquely identify the entities as well as use proper names for the keys. Would you also have payments? Primary keys are shown at the top of the list of attributes and marked with PK.

A character alphanumeric field holding the identifying name for the piece of equipment A system-generated numeric value unique to each piece of equipment.

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

But a long text field such as the client name would solutio a poor primary key for Client, consuming extra storage space, slowing down database operations, and probably requiring extra typing. Data analysis – Chapter 8 2. Primary keys are shown at the top of the list of attributes and marked with PK. Data Model Normalization Page: This would also be a system-generated number.

  RGUHS DISSERTATION TOPICS IN PAEDIATRIC NURSING

A character alphanumeric barcode ID that is either pre-printed on each component package or dtudy via a label at Coastline Consulting. The EquipmentComponent entity has ComponentNum as the primary key. In most activities explanations for why things were done as they were have been provided to aid in your understanding of the solution. Specify all data types your instructor will specify the target database or allowable set of data types. A system-generated large integer numeric value unique to each work record.

ctts case study milestone 5 solution

Optional Entities A classification of Equipment. Would you track accounts payable? These two entities could be combined into one entity, but with their different uses, a case can be made for have two entities.

Case Study CTTS – Milestone 05 Data Model

This could be the primary key. A character alphanumeric field consisting of last name of the client contact person. As a number it would also consume less disk space as a foreign key in related tables and would provide for faster joins.

ctts case study milestone 5 solution

But make sure each non-key attribute exists in only one entity. Some, but not all, of the configuration records could be associated with a piece of Equipment.

  CCEA LLW COURSEWORK

Case Study CTTS – Milestone 05 Data Model

The following completed matrix is one possible solution. A character description of the component. If you will be doing Milestone 5 as a separate assignment, you may milestohe to withhold this solution. Suggest us how to improve StudyLib For complaints, use another form.

A character alphanumeric field identifying the equipment as PC, Printer, Scanner, etc.

ctts case study milestone 5 solution

Logical Data Model in 3rd Normal Form: Your e-mail Input it if you want to receive answer. This makes a one-to-one relationship. Why do we use different scales. A character alphanumeric postal code of a client. The following tables contain the attributes identified from each form and the interview. Work done to resolve a SeviceRequest. Each EquipmentComponent is a particular ComponentType.

If you, the instructor, choose to do your own solution, it may be different, depending on your interpretation of the forms provided. This is always a whole number. Date field consisting of the date a component was installed into a piece of equipment. A character alphanumeric description of the piece of equipment, if any, for a software configuration record.