The final project for this course is the creation of a proposal, project plan, and system design document. The project is divided into two milestones, which will be submitted at various points through

IT 420 Milestone One Guidelines and Rubric (Draft of Introduction and Verification Plan) In this milestone, you will submit a draft of Section I (introduction) and Section II (verification plan) to include all crit ical elements. The introduction provides an overview of the IT problem you are addressing. When completed, it should provide suffic ient context to facilitate quality feedback from the reviewing audience. Your draft Introduction will largely consist of the information from the system proposal and should continue to be updated as required. The verification plan (Section II) will descr ibe how to verify that the system meets original design specifications, for example, by performing various tests that demonstrate functionality and performance. It should include a detailed feedback plan and comment adjudication guidelines. Prompt: Specif ically, the following critical elements must be addressed: I. Introduction : Present an overview of the problem that the project addressed, the significance this project has, and objectives that the p roject should have met. Much of this can be taken from the project proposal submitted in IT 415 but including any necessary alterations or adjustments you made during this course. The aim of this section is to provide context to the rest of the project closure document so that the aud ience can critically evaluate the completed project and provide feedback. II. Verification Plan : A verification plan will provide an organized way to conduct verification of the system, which can be done through executio n of formal test cases that exercise the functionality and performanc e of the system. It can also include obtaining verbal feedback through focus groups, usability testing of prototypes, and other means. The following sections should be included: a) Feedback Plan : Construct a comprehensive plan for showcasing your system and c ollecting feedback from stakeholders. Explain what you will present as regular artifacts of the system to your stakeholders so you can obtain feedback. The stakeholders from whom you mu st collect feedback will vary depending on your IT issues. b) Criteria : Es tablish the criteria you will use to determine whether or not the feedback received is relevant and actionable. c) Test Cases : In this section, you will describe how you will (or would) test the implemented project to ensure it fulfilled all requirem ents and that the promised objectives/functionality were met. You will be required to fully test your system and supply the test results as part of the appendix of your project closure document, if implementation of your project is possible. Rubric Guidelines for Submission: Submit assignment as a Word document with double spacing, 12 -point T imes New Roman font, and one -inch margins. Critical Elements Proficient (100%) Needs Improvement (75%) Not Evident (0%) Value Introduction Creates an introduction that provides a clear and comprehensive overview of the issue, the significance of the solution, and the objectives of the project Creates an introduction that provides an overview of the issue, the significance of the solution, and the objectives of the projec t but with gaps in detail or clarity Does not create an introduction that provides an overview of the issue, the significance of the solution, or the objectives of the project 20 Verification Plan: Feedback Constructs a comprehensive, logical plan for showcasing the system and collecting feedback from stakeholders Constructs a plan for showcasing the system and collecting feedback from stakeholders but with gaps in detail or logic Does not construct a plan for showcasing the system and collecting feedba ck from stakeholders 20 Verification Plan: Criteria Establishes reasonable and relevant criteria for determining whether or not feedback received is relevant and actionable Establishes criteria for determining whether or not feedback received is relevant and actionable, but criteria is not reasonable or relevant Does not establish criteria for determining whether or not feedback received is relevant and actionable 20 Verification Plan: Test Cases Articulates a sound process for testing the implemented project to ensure requirements fulfillment Articulates a process for testing the implemented project to ensure requirements fulfillment but with gaps in logic or reason Does not articulate a process for testing the implemented project to ensure requirement s fulfillment 20 Articulation of Response Submission has no major errors related to citations, grammar, spelling, or syntax Submission has major errors related to citations, grammar, spelling, or syntax that negatively impact readability and articulation of main ideas Submission has critical errors related to citations, grammar, spelling, or syntax that prevent understanding of ideas 20 Earned Total 100%