Details of this Paper

Part 1 of 6: Milestones 1 & 2 (80 pts.) - Due Week...

Description

Solution


Question

Part 1 of 6: Milestones 1 & 2 (80 pts.) - Due Week 2 Be sure to read the Project area of each Assignment section, as they talk directly to the milestone tasks. Also, for review purposes, note that typical milestone solutions will be posted on Wednesday morning of the following week. This is necessary as it is important. Deliverables: Request for System Services form Problem Statement Matrix Context Diagram Problems, Opportunities, Objectives, and Constraints Matrix Tentative List of Functional and Non-Functional Requirements Review all of the Milestone project steps below. Post questions in the CTTS Milestone discussion area. Milestone 1 The 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 (CTTS). With these facts and facts obtained from the Case Background, you will have the necessary information to complete the Problem Statement Matrix. Milestone 1 Instructions For this milestone, you will be using the following templates/resources: Click here for Template A Click here for Template B Note: Please be sure to submit BOTH milestone assignments to the Dropbox using ONE Word document. (You may paste created diagrams and illustrations from other software as needed.) Milestone 2 There?s an old saying that suggests, ?Don't try to fix it unless you understand it.? With those words of wisdom, the next milestone of our project is to study and analyze the existing system. There is always an existing business system, regardless of whether it currently uses a computer. The problem analysis phase provides the project team with a more thorough understanding of the problems, opportunities, and/or directives that triggered the project. Indeed, the analyst frequently uncovers new problems and opportunities. The problem analysis phase may answer the questions, ?Are the problems worth solving?'' and ?Is a new system worth building?'' The purpose of the problem analysis phase is threefold. First and foremost, the project team must gain an appropriate understanding of the business problem domain. Second, we need to answer the question, ?Are these problems (opportunities and directives) worth solving?? Finally, we need to determine if the system is worth developing. The problem analysis phase provides the systems analyst and project team with a more thorough understanding of the problems, opportunities, and/or directives that triggered the project. In the process, they frequently uncover new problems and opportunities. In this milestone you will perform a cause-effect analysis on the Client Technology Tracking System (CTTS) and document your findings using the Problems, Opportunities, Objectives, and Constraints Matrix. The PIECES framework, originally developed by James Wetherbe and then adapted by the authors, can serve as a useful tool to classify the various problems, opportunities, and directives identified in Milestone 1. Milestone 2 Instructions For this milestone, you will be using the following templates/resources: Click here for Template C Note: Please be sure to submit BOTH milestone assignments to the Dropbox using ONE Word document. (You may paste created diagrams and illustrations from other software as needed.) Category Points % Description Milestone 1 40 50% Milestone 2 40 50% Part 1 Total 80 100% A quality report will meet or exceed all of the above requirements.

 

Paper#10953 | Written in 18-Jul-2015

Price : $25
SiteLock