CASE STUDY CTTS – MILESTONE 09

CASE STUDY CTTS – MILESTONE 09

The system must make it easy for technicians to update the component and configuration information. This makes a one-to-one relationship. The diagram below includes foreign keys, assuming implementation in a relational database. This, of course, is DFD style. This could be the primary key. The proposed system could allow clients to enter service requests online, saving receptionist time plus providing more efficiency.

An EquipNum is a number that could be generated by the system and stays unchanged forever. Foreign keys are marked with FK and a number. A computer, printer, or other piece of technology equipment that is in use. 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. 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. Clients, technicians, and management should be able to view unresolved service requests and the history of work performed on them. But make sure each non-key attribute exists in only one entity.

case study ctts - milestone 09

Some students may have given more specific descriptions such as those found in the first column of the problem statement matrix. The diagram below includes foreign keys, assuming implementation in a relational database. The proposed system could provide a customer history that would allow for better service.

An Internet-based portion stud the system will allow clients to submit service requests and consultants to enter work notes to provide a history for each client. 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.

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

Configuration information will be very flexible to handle all the kinds of information that needs to be tracked. The system must make it easy for technicians to update the component and configuration information. Causes and Effects Receptionist takes calls and route to technicians with phone transfer or e-mail.

  CURRICULUM VITAE AC STUDIORUM ESEMPIO

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.

Students may combine some requirements; evaluate their thought processes in building the list. However, Jeff Summers states that the computer name is sometimes changed. Causes and Effects Three-ring binder that holds information is disorganized and incomplete.

case study ctts - milestone 09

Each EquipmentComponent is a particular ComponentType. Prepared by Gary B. There is also more than one wrong answer. In the present system, the computer name acts as a primary identifier.

Each piece of Equipment is owned by a particular Client. But make sure each non-key attribute exists in only one casse.

If use barcode scanning, would have to change inventory check-in process. Clients, technicians, and management should be able to view unresolved service requests and the history of work performed on them. Some, but not all, of the configuration records could be associated with a piece of Equipment. A component anything from a stick of RAM to an entire turn-key system that is or has been installed in Equipment. The following matrix illustrates one possible solution.

Case study CTTS milestone 09 application architecture

Because this does not apply to all records, a formal relationship would not have to be established. 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.

  DISSERTATION DIN A5 SCHRIFTGRÖßE

case study ctts - milestone 09

None of the forms hint at a ClientID. System Constraint Internet application must have adequate security. 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 cths requiring extra typing.

Case Study CTTS – Milestone 01 Scope Definition Solution_图文_百度文库

A request for service on Equipment. In this milestone enough information was provided to be able to quantify some but not all annual benefits. The proposal has an opportunity to provide better service to users along with reduced costs and better information to both IT personnel and management.

Three-ring binder is difficult to keep up-to-date because word processing documents cannot be updated in the field. As a number it would also consume less disk space as a foreign key in related tables and would provide for faster joins. The Data Flow Model template found in the Software category can produce one that is like the sample except that the square Interface symbol must be used instead of the Actor symbol. System should be easy to update in the field. Would allow technicians to see what other technicians had done.

Vendor would be a parent table to PurchaseOrder, contributing the VendorID in a non-identifying relationship.