Reference no: EM132176419 , Length: word count:4000

Case Background

Three-Body Consulting is a provider of computer networks and web serviceslocated in Cork, Ireland. The staff of seven IT technicians, web designers, and systems integrators provides a range of networking, computer hardware, and software solutions to area businesses. Three-body works with clients to analyze their business needs. They then provide a packaged solution that often combines web services, networking and computer hardware, purchased software, and custom programming. In addition to the seven technicians, Three-body has one receptionist/bookkeeper.

As a small organization, Three-body is an informal, "shirt-sleeve" environment. Everyone is on a first-name basis, even with Peter Charles, the president.

The Problem

As Three-body's client base and the complexity of installations have grown, keeping track of the clients' hardware and software configurations has become a nightmare. Each client PC contains various components, such as video cards, NICs, and keyboards which are replaced at different times and so have differing warranty periods that must be tracked. Every client has multiple PCs and network devices, whose passwords and configurations must be accessible by technicians in the Three-body office and in the field. One technician is "on-call" every weekend, meaning the data must be accessible from home as well. This must be organized in a way that is easily accessible by any technician at any time or place but secure from unauthorized users.

In addition to tracking components and passwords, clients call and e-mail the Three-Body office whenever they have any kind of hardware or software problem. These requests and the work done to resolve them need to be organized and documented.

The president, Peter Charles, wants to develop a system that is both responsive to clients and helpful to technicians. He would like to see a system that allows technicians to access and update client equipment hardware and software configurations. He wants an easy way for technicians to track the installation of new hardware components, possibly using barcode scanning. He wants the system to allow clients to directly enter their service requests, allow technicians to document the work done on those requests, and for everyone to be able to see the history and status of each request. Mr. Charles also wants the system to be able to generate statistics and reports, so he can pursue continuous improvement in this area.

Assignment
You are an analyst/programmer who has been working for Three-body Systems Consulting for one year since your college graduation. So far youhave handled designing small web applications for clients. You recently got an idea of how to improve Three-body's efficiency and customer service. After thinking about it a few days, you have decided to share it with the president, Peter Charles.

Deliverables - Part 1
1. To complete the Request for System Services form, use information from the case background. Make assumptions where necessary.
2. To complete the Problem Statement Matrix, use the interview with Peter Charles and the case background for the basis of your information. Make assumptions where necessary. Place yourself in the shoes of Peter Charles. Which problems do you believe have the highest visibility, and how should they be ranked? Try to determine the annual benefits. State assumptions and be prepared to justify your answers! Finally, what would be your proposed solution based on the facts you know now?

The following is a copy of the transcript of an interview between Mr. Peter Charles, President, and You. This was the initial discussion concerning the proposed client configuration tracking system.

Assignment

Now that we have completed the survey of the system and gained approval to proceed, we can attempt to gain a better understanding of the current system and to evaluate whether the proposed system is worth developing.

Deliverables - Part 2
1. To complete the Problems, Opportunities, Objectives, and Constraints Matrix, use the interview presented in this milestone. Use the PIECES framework as a model to classify the problems, opportunities, and directives.
2. Create a tentative list of requirements for the proposed system, classifying each as a functional or non-functional requirement.
3. Create a zero level DFD (Context) for the entire system.

Assignment
Now that we have studied the current system and analyzed some of its problems and opportunities, plus gained approval to proceed, we can now start to identify the business requirements for the system and model them. In this assignment we will use our results of the previous milestones and transcripts of an interview with president Peter Charles, IT consultant Jeff Summers, and web server administrator Dane Wagner of Three-body Systems Consulting. The results of this activity will identify the system requirements for the proposed system.
Exhibit 3.1 is a copy of the transcript of the interview. Refer to the transcript, sample forms, and results from Milestones 1 and 2 for the information necessary to complete the activities.

Deliverables - Part 3
1. Complete a Use-Case Glossary. Make assumptions where necessary.
2. Prepare a Use-Case Model Diagram.

The following is a copy of the transcript of an interview conducted by You Kelly with president Peter Charles, IT consultant Jeff Summers, and web server administrator Dane Wagner of Three-body Systems Consulting. The goal of this interview was to determine requirements for the proposed system.

Assignment
In this assignment we will use our results of the previous milestones and transcripts of an interview with IT consultant Jeff Summers and receptionist/bookkeeper Kathy Grey, both of Three-body Systems Consulting. The results of this activity will identify the business data requirements for the proposed system.
Exhibit 4.1 is a copy of the transcript of the interview. Refer to the transcript, sample forms, and results from Milestones 1-3 for the information necessary to complete the activities.

Deliverables - Part 4
1. Complete an Entity/Definition Matrix. Analyze each of the forms referenced by the user interview plus any comments made by Jeff Summers. Make assumptions where necessary.
2. Entity relationship diagram
3. Prepare a UML Class Diagram
4. Candidate systems matrix

Attachment:- project.rar