Review the introductory information about theCoastline Systems Consulting company presented in week 3 and read theCase Study CTTS - Milestone 01 Scope Definition.We will accomplish the requirements of...


Review the introductory information about theCoastline Systems Consulting company presented in week 3 and read theCase Study CTTS - Milestone 01 Scope Definition.We will accomplish the requirements of the Scope Definition in several stages.
For this week complete:



  • Request for System Services (RSS)

  • Problem Statement Matrix (PSM)










Below is the instructions from my professor. I believe (could be wrong) it is filling out two forms. Attached are the templates, Case Study of Coastline, and example pictures from my book. Please let me know if there are any questions or missing information. Thank you


Use for guidelines the following examples from chapter 5 of your textbook:



  • Requestfor Systems Services (Fig. 5-7, page 170)

  • Problem Statements (Fig. 5-8, page 171)




INTRODUCTION SADM 7/ed – CTTS CASE STUDY - Introduction Page: I-3 Client Technology Tracking System INTRODUCTION I n this section you will learn background information that will prepare you to understand and complete each of the milestones of this case study. This information includes a history of the business, a description of the business’s current facilities, and the descriptions of the problems that triggered the project. · Case Background Coastline Systems Consulting is a provider of managed computer networks and web services located in Destin, Florida. The staff of seven IT technicians, web designers, and systems integrators provides a range of networking, computer hardware, and software solutions to area businesses. Coastline 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, Coastline has one receptionist/bookkeeper. As a small organization, Coastline is an informal, "shirt-sleeve" environment. Everyone is on a first-name basis, even with Peter Charles, the president. · Organization Structure Coastline Systems Consulting · Information Systems Facilities PCs · Each technician works uses a Dell notebook: · Pentium M class machines with 512 MB RAM, 30-50 GB hard drives · The bookkeeper/receptionist has a Dell Optiplex desktop running a Pentium 4, 256 MB RAM, and an 80 GB hard drive: · Operating systems - MS Windows Windows XP Professional · Tools - MS Office 2003 suite plus other software depending on use · Internet Browser – IE 6 and Mozilla FireFox · E-mail Client - Mozilla Thunderbird · Various inkjet and laser printers Servers · Dell PowerEdge 2800 Server · 1 GB of RAM, 80 GB RAID-5 hard drive storage · Operating system - MS Windows Server 2003 · Providing DHCP, Security, and Internet Access, and Database Management (SQL Server 2000) · Dell PowerEdge 1850 Server · Providing Web hosting · Operating system – Windows Server 2003 with IIS Networking · The company headquarters is equipped with wireless networking so notebooks can roam throughout the building. Notebooks also have integrated Ethernet NICs and modems so they can connect to the Internet at home and at clients' places of business. · The Problem As Coastline'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 Coastline office and in the field. One technician is "on-call" every weekend, meaning the data has to be accessible from home as well. This has to 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 Coastline 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. Prepared by Gary B. Randolph for Systems Analysis & Design Methods 7ed by J. L. Whitten, L. D. Bentley, & K. C. Dittman Copyright Irwin/McGraw-Hill 2007 INTRODUCTION SADM 7/ed – CTTS CASE STUDY - Milestone 1: Scope Definition Page: 1-6 MILESTONE 1 – SCOPE DEFINITION · Synopsis T he purpose of the preliminary investigation phase is threefold. First, it answers the question, “Is this project worth looking at?” To answer this question, this phase must define the scope of the project and the perceived problems, opportunities, and directives that triggered the project. In this milestone you will prepare a Request for System Services, which is the trigger for the Preliminary Investigation Phase. Also, you will use fact-finding techniques to extract and analyze information from an interview to determine project scope, level of management commitment, and project feasibility for the Client Technology Tracking System. With these facts and facts obtained from the Case Background, you will have the necessary information to complete the Problem Statement Matrix and, if assigned, construct the Project Feasibility Assessment Report. · Objectives After completing this milestone, you should be able to: · Complete a Request for System Services form, which triggers the preliminary investigation phase. · Analyze a user interview and extract pertinent facts that can be used to assess project feasibility. · Complete a Problem Statement Matrix documenting the problems, opportunities, or directives of the project. · Prepare and understand the structure and content, of the Project Feasibility Assessment Report. · Prerequisites Before starting this milestone the following topics should be covered: 1. The scope definition phase - Chapters 3 and 5 2. Optional – project management - Chapter 4 · Assignment Anna Kelly is an analyst/programmer who has been working for Coastline Systems Consulting for one year since her college graduation. So far she has handled small web applications for clients, designing and writing the XHTML, JavaScript, and .NET code. Anna recently got an idea of how to improve Coastline's efficiency and customer service. After thinking about it a few days, she has decided to share it with the president, Peter Charles. Refer to the Case Background found in the Introduction and the interview transcript in Exhibit 1.1for the information necessary to complete the following activities. · Activities 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? Deliverable format and software to be used are according to your instructor’s specifications. Deliverables should be neatly packaged in a binder, separated with a tab divider labeled “Milestone 1” and accompanied with a Milestone Evaluation Sheet. References and Templates: Case Background Workbook Introduction Transcript of Interview with Peter Charles Exhibit 1.1 Templates See on-line learning center website for the textbook. Deliverables: Request for System Services: Due: __/__/__ Time:_______ Problem Statement Matrix: Due: __/__/__ Time:_______ ADVANCED OPTION For the advanced option, prepare a Project Feasibility Assessment Report. A template for this report can be downloaded from the textbook website. Use the information provided by the case background, the user interview, and the completed problem statement matrix. Be sure to include a Statement of Work and Gantt charts for the project schedules. Information on the Statement of Work and Gantt charts can be found in Chapter 4 of the SADM 7th ed. textbook. Project Feasibility Assessment Report: Due: __/__/__ Time:_______ Milestone’s Point Value: _______ The following is a copy of the transcript of an interview between Mr. Peter Charles, President, and Anna Kelly, Web Programmer. This was the initial discussion concerning the proposed client technology tracking system. Exhibit 1.1 Scene: The office of Peter Charles, president of Coastline Systems Consulting. Peter is working at his desk. Anna Kelly knocks on the open door. Anna: Hey, Boss, do you have a few minutes? Peter: The door is always open, Anna. Have a seat. What's on your mind? Anna: I have an idea I'd like to bounce off you. I was talking to Ben the other day. He told me about going out to Fox Motors to check out a problem with their router. When he got there he discovered that the router password he had in his files wasn't right. He had to call back to our office to see if anyone knew what was going on. Turns out Jeff had replaced the router three months ago. Jeff had a record of its configuration, but Ben essentially wasted most of an hour learning what Jeff already knew. Peter: Ouch. Sad to say, that isn't the first time something like that has happened. Anna: Well, it got me thinking. Peter: How so? Anna: I've heard the other consultants tell similar stories. Someone goes out on a job and doesn't know what another consultant has already done. What if we build a company-wide database for storing that information? Peter: I like that idea. Anna: It would be really simple. It would need to keep all configuration information for every piece of equipment for every client. But that shouldn't be so hard. Peter: Except that all those pieces of configuration information are different. Some are usernames and passwords. Some are IP addresses with or without port numbers. Some are web addresses where we go to setup databases or e-mail addresses or whatever else. Anna: That just means we need to design the data carefully. I do databases for our web programming clients all the time. Peter: There are a couple other pieces of the puzzle that maybe you haven't thought of since you don't often make field calls. Anna: Like what? Peter: Like hardware components. We sell and service computers. Sometimes the servicing gets confusing. Speaking as someone who has been known to crack open a case at a client's office, we need keep track of each piece of equipment (computers, printers, scanners, etc.) that we have in service. We need to know how each computer is configured in terms of RAM, hard drive, video card, etc. And we need to know when each component was purchased, because each has a different warranty period that we have to honor. Anna: I thought we were keeping that information already. Peter: We keep notes on that information for each client. But I can tell you that it doesn’t work very well. As a result, Jeff and Ben sometimes get out on site and don’t have the right equipment or drivers. Then they have to make a trip back here to get
Oct 07, 2021
SOLUTION.PDF

Get Answer To This Question

Related Questions & Answers

More Questions »

Submit New Assignment

Copy and Paste Your Assignment Here