I need help with this

1. Project Plan: The project plan will be drafted early in the course but further refined as you develop the system design. This way, the workbreakdown structure and tasks identified in the design in need of development are added to the project plan.
   1. 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.
   2. 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 should happen in IT 420, the implementation course.)
   3. Dependencies: Clearly communicate any dependencies between tasks or resources for ensuring successful communication of needs.
   4. Use of Tools: Professionally document project plan using Microsoft Project or Excel.
2. System Design Document: Although you will individually develop your recommended information technology project, the project design should contain enough detail to support another skilled information technology practitioner in implementing the solution. Determine a reasonable scope for your project so that it can be implemented within the timeframe of the IT 420 course. 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 your proposal.

1. 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.
2. Constraints: Determine the constraints of the system design and any assumptions made in terms of the problem being solved.
3. Resources: Identify necessary resources—hardware, software, servers, virtual desktop resources, and so on—that are required tocomplete the project, based on analysis of the problem being solved.
4. System Overview: Describe the overall design in terms of the integration of tools and technology for successfully constructing yoursolution. In this section, you should describe the high-level design and architecture, making sure that details are congruent with the type of project you are working on. For example, use of case and class diagrams would need to be included if your project focused on a software application, website wireframe, screen mock-ups for a web application, and so on.
5. Documented Detailed Design: Your detailed design should illustrate and annotate all important details to be developed of the system and its components, interfaces, subsystems. 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.