Will provide approved project proposal. This will be a single paper but two main parts, which will need to be clearly separated. Project Plan: The project plan will be drafted early in the course but further refined as the system design is developed. This way, the work breakdown structure and tasks identified in the design in need of development are added to the project plan. A. Work Breakdown Structure: Clearly communicate a logical work breakdown structure for stakeholders to ensure successful completion of the project. Identify all tasks and artifacts to be developed. B. Timeline: Illustrate the overall project timeline, identifying start and finish dates, major milestones, and any other relevant data points during the design and implementation of the project/solution. (Implementation will not happen at this time.) C. Dependencies: Clearly communicate any dependencies between tasks or resources for ensuring successful communication of needs. D. Use of Tools: Professionally document project plan using Microsoft Project or Excel. II. System Design Document: Although the project will be individually developed, the project design should contain enough detail to support another skilled information technology practitioner in implementing the solution. Determine a reasonable scope for the project so that it can be implemented within the timeframe eight weeks. The following sections should be included: A. Introduction: Articulate the overall purpose and scope of the system design in terms of addressing the problem or challenges identified in the proposal. B. Requirements: Determine all relevant and necessary system requirements based on analysis of the problem faced. The requirements should be written as “system shall” statements that are testable and include functional, design, security, safety, and performance requirements. C. Constraints: Determine the constraints of the system design and any assumptions made in terms of the problem being solved. D. Resources: Identify necessary resources—hardware, software, servers, virtual desktop resources, and so on—that are required to complete the project, based on analysis of the problem being solved. E. System Overview: Describe the overall design in terms of the integration of tools and technology for successfully constructing your solution. In this section, describe the high-level design and architecture, making sure that details are congruent with the type of project being worked on. For example, use of case and class diagrams would need to be included if the project focused on a software application, website wireframe, screen mock-ups for a web application, and so on. F. Documented Detailed Design: The detailed design should illustrate and annotate all important details to be developed of the system and its components, interfaces, subsystems, and more. It further breaks down the high-level design into small enough chunks to be properly implemented. The detailed design should align with the work breakdown structure in the product plan. The detailed design should inform the tasks identified and included in the project plan.
#Project #Plan #System #Design #Documentation
