If you, the instructor, choose to do your own solution, it may be different, depending on your interpretation of the forms provided. The real problem with adding purchase orders to CTTS is that it opens the door on accounting functions. Vendor would be a parent table to PurchaseOrder, contributing the VendorID in a non-identifying relationship. Some students may have given more specific descriptions such as those found in the first column of the problem statement matrix. 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. Each piece of Equipment is owned by a particular Client. Techs should be able to mark a service request as resolved The system should be able to mark as service request as resolved if nothing more is heard from the client after the passage of a set amount of time Classification Functional Functional Non-functional Non-functional Functional Non-functional Non-functional Non-functional Functional Functional Non-functional Functional Non-functional Functional Functional Prepared by Gary B.

In your class discussion you might point out that functional requirements show up in the context model, while generally non-functional requirements do not show up in the context model other than to specify the actors that can do send or receive certain information. Prepared by Gary B. However, some users have very specific ideas or expectations of what software and technologies will be used. Causes and Effects Receptionist takes calls and route to technicians with phone transfer or e-mail. A Client submits one or more ServiceRequests, which may related to a piece of Equipment. Make sure students identify a cause and not restate the problem.

Three-ring binder is difficult to keep up-to-date because word processing documents cannot be updated in the field. Problem Statement Matrix Students should try to identify problems and also opportunities that were mentioned in the narrative.


Each piece of Equipment is owned by a particular Client. BarCode is the primary key for both EquipmentComponent and Inventory. If not online, then need to replicate data between master and copy.

case study ctts - milestone 09

Each piece of Equipment is ccase particular EquipmentType. This makes a one-to-one relationship. There is also a need for an Internet application that would allow clients to submit service requests and technicians to enter notes of their work on those requests.

case study ctts - milestone 09

Vendor would be a parent table to PurchaseOrder, contributing the VendorID in a non-identifying relationship. Clients, technicians, and management should be able to view unresolved service requests and the history of studdy performed on them. An Internet-based portion of the system will allow clients to submit service requests and consultants to enter work notes to provide a history for each client.

In sgudy activities explanations for why things were done as they were have been provided to aid in your understanding of the solution. As a number it would also consume less disk space as a foreign key in related tables and would provide for faster joins.

case study ctts - milestone 09

Optional Entities A classification of Equipment. Stuudy form that follows illustrates one possible solution. Family Vacation Rentals Machine Name i. You will have a multitude of different answers.

Work done to resolve a SeviceRequest. 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.

Case Study CTTS – Milestone 02 Problem Analysis Solution_图文_百度文库

The following matrix illustrates one possible solution. The system must make it easy atudy technicians to update the component and configuration information. If you will be doing Milestone 5 as a separate assignment, you may want to withhold this solution. Foreign keys are marked with FK and a number. The service request part of the system should have adequate security.


Case study CTTS milestone 09 application architecture

Students should be able to defend their answers with specific statements from the case study exhibits. System Constraint Internet application must have adequate security. Visio cannot easily produce a Context Diagram exactly like the one shown in chapter 5.

Requirement The system should allow technicians to view and edit hardware component information in the field. Causes and Effects Three-ring binder that holds information is disorganized and incomplete. The students cths try to identify the causes and effects of the problems identified in Milestone 1.

Another alternative is to start with this data model for Milestone 5 but add additional requirements, such as the Milestone 4 Advanced Option and require that students revise the data mildstone accordingly. Each ServiceRequest will be worked on with zero or more WorkRecords initially zero but eventually at least one.

System Constraint Configuration information should not be accessible from the Internet for security reasons. Logon Multiple Values of Information i. Techs should be able to enter work performed on a service request Only techs should be able to enter work performed on a service request Techs should be able to enter new equipment to the system. Also, make sure they specify proper objectives to correct the problems.

These two entities could be combined into one entity, but with their different uses, a case can be made for have two entities.