MILESTONE 10 IT510

  

  

Using your previous work (your Business Case Proposal and Introduction, Project Plan, System Requirements, and System Design (SEE OTHER ATTACHMENTS)) you will submit a systems proposal document. It should be a complete, polished artifact containing all the critical elements of the final product.

Your final submission will include an introduction, systems requirements, systems design specifications, and an implementation plan. All the components listed below should be submitted as a single, organized systems proposal document and include screenshots of all relevant diagrams, charts, and tables.

I. Introduction: Provide an overview of your selected case. Be sure to provide appropriate citations and reference to the case study you have selected.

a) Background: Establish a context for understanding your systems proposal. Specifically, explain any essential paradigms, processes, and activities of the existing information technology systems.

b) Problem Statement: What is the problem that needs to be solved? Why is it a problem? What are the impacts to the enterprise?

c) Audience: Who are your audiences for this systems proposal? How will you effectively communicate the information of your proposal to these diverse groups?

II. Systems Requirements: Detail the specific requirements of your case. Be sure to include screenshots of all relevant diagrams, charts, and tables.

a) Requirements Modeling: Assess the current system to identify the requirements for the new system. Be sure to address each of the following aspects: outputs, inputs, processes, performance, and controls (i.e., security).

b) Data Process Model: Create a visual representation of all relevant data processes that represents a logical model of the requirements of the system based on the systems development life cycle.

c) Data Flow Diagrams: Create a visual representation of the data flow based on the systems development life cycle.

d) Data Dictionary: Create a data dictionary that annotates your system requirements to build clarity in communicating with the relevant audiences.

e) Object Modeling: Use appropriate object modeling techniques and tools to describe the system requirements.

f) Use Case Diagrams: Create (a) use case diagram(s) that outline the system requirements based on the systems development life cycle.

III. Systems Design: Propose a solution that addresses the identified problem in your case. Be sure to include screenshots of all relevant diagrams, charts, and tables.

a) Specifications: Provide a physical design that will meet the specifications outlined in the systems requirement document.

b) Data Design: Create entity relationship diagrams that accurately describe the proposed solution, including 3NF table designs.

c) User Interface Design: Illustrate the user interface design. Specifically, be sure to address your proposed human computer interactions (HCIs) and graphical user interfaces (GUIs). Your proposals should follow user-centered design principles and address all design requirements.

d) System Architecture: Describe the system architecture. Specifically, be sure to address the corporate organization and culture, enterprise resource planning, total cost of ownership, scalability, integration and interface requirements, and security.

e) Feasibility Analysis: Provide supporting details that justify why your proposed solution is appropriate for solving the problem. In your defense, be sure to address operational, technical, economic, and scheduling feasibility. Be sure that you frame your response for communicating effectively to your target audiences.

IV. Project Plan: Illustrate your recommended implementation and management strategies. Be sure to include screenshots of all relevant diagrams, charts, and tables.

a) Work Breakdown Structure: Describe all the essential roles and functions required for implementing the solution. Who will be doing the work and what, specifically, will they need to do?

b) Project Monitoring and Control Plan: How are you going to ensure that the project is going smoothly? What is your plan of attack to ensure that all controls are adhered to? What is the defined critical path? Be sure that you frame your response for communicating effectively to your target audiences.

c) Timeline: What is the estimated amount of time for implementation? Create a visual representation that captures your timeline (e.g., Ganttchart) based on the systems development life cycle.