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 critical elements. The introduction provides an
overview of the IT problem you are addressing. When completed, it should provide sufficient 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 describe 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: Specifically, 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 project 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 audience 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 execution of formal
test cases that exercise the functionality and performance 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 collecting 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 must collect
feedback will vary depending on your IT issues.
b) Criteria: Establish 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 requirements 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 Times New Roman font, and one-inch margins.
Critical Elements
Introduction
Verification Plan:
Feedback
Verification Plan: Criteria
Verification Plan: Test
Cases
Articulation of Response
Proficient (100%)
Creates an introduction that provides a
clear and comprehensive overview of
the issue, the significance of the
solution, and the objectives of the
project
Constructs a comprehensive, logical
plan for showcasing the system and
collecting feedback from stakeholders
Establishes reasonable and relevant
criteria for determining whether or not
feedback received is relevant and
actionable
Articulates a sound process for testing
the implemented project to ensure
requirements fulfillment
Submission has no major errors related
to citations, grammar, spelling, or syntax
Needs Improvement (75%)
Creates an introduction that provides an
overview of the issue, the significance of
the solution, and the objectives of the
project but with gaps in detail or clarity
Not Evident (0%)
Does not create an introduction that
provides an overview of the issue, the
significance of the solution, or the
objectives of the project
Value
20
Constructs a plan for showcasing the
system and collecting feedback from
stakeholders but with gaps in detail or
logic
Establishes criteria for determining
whether or not feedback received is
relevant and actionable, but criteria is
not reasonable or relevant
Articulates a process for testing the
implemented project to ensure
requirements fulfillment but with gaps
in logic or reason
Submission has major errors related to
citations, grammar, spelling, or syntax
that negatively impact readability and
articulation of main ideas
Does not construct a plan for
showcasing the system and collecting
feedback from stakeholders
20
Does not establish criteria for
determining whether or not feedback
received is relevant and actionable
20
Does not articulate a process for testing
the implemented project to ensure
requirements fulfillment
20
Submission has critical errors related to
citations, grammar, spelling, or syntax
that prevent understanding of ideas
20
Earned Total
100%
Purchase answer to see full
attachment