This week, you will complete your proof of concept and submit the report. This is the final report to management before the actual cloud deployment process begins. Use the Proof–of–Concept Report Template to prepare a report that shows the steps and results for the proof of concept. In the template, you will see specific instructions. Delete the instruction text before you submit the project. Your report should:
When you are finished, click “add a file” to upload your work, then click the Submit button. |
||
Rubric Name: Project 3: Proof of Concept Report
This table lists criteria and criteria group name in the first column. The first row lists level names and includes scores if the rubric uses a numeric scoring method.Criteria
Presents a logical flow of ideas that is easily identifiable and completely appropriate to the task.
Presents ideas in a clear, logical order appropriate to the task.
Attempts to present ideas, but the logic is not clear and/or not appropriate to the task.
Does not present ideas in a clear, logical order appropriate to the task.
Explains the relationship between the ideas presented in a thorough manner to enhance clarity and comprehension.
Explains the relationship between the ideas presented to enhance clarity and comprehension.
Attempts to explain the relationship between the ideas presented, but there may be gaps in clarity and comprehension.
Does not explains the relationship between the ideas presented to enhance clarity and comprehension.
Identifies the issue or problem under consideration in a clear and thorough manner.
Identifies the issue or problem under consideration.
Attempts to Identify the issue or problem under consideration, but there is a lack of clarity or thoroughness.
Does not identify the issue or problem under consideration.
Describes the context surrounding the issue or problem clearly and accurately.
Describes the context surrounding the issue or problem.
Attempts to describe the context surrounding the issue or problem.
Does not describe the context surrounding the issue or problem.
Explains the assumptions underlying viewpoints, solutions, or conclusions in a comprehensive and accurate manner.
Explains the assumptions underlying viewpoints, solutions or conclusions.
Attempts to explain the assumptions underlying viewpoints, solutions or conclusions, but the explanation lacks clarity.
Does not explain the assumptions underlying viewpoints, solutions, or conclusions.
Addresses alternative viewpoints, perspectives, and methods accurately and appropriately.
Addresses alternative viewpoints, perspectives, and methods.
Attempts to address alternative viewpoints, perspectives, and methods, but there are issues with the accuracy and/or appropriateness.
Does not address alternative viewpoints, perspectives, and methods.
Installs software that is fully functional and appropriate for the given requirements.
Installs software that is appropriate for the given requirements.
Installs software that may not be fully functional and/or appropriate for the given requirements.
Does not install software.
Configures technology accurately and thoroughly to meet stakeholder specifications and requirements.
Configures technology that meets stakeholder specifications and requirements.
Attempts to configure technology according to stakeholder specifications and requirements.
Does not configure technology that meets stakeholder specifications and requirements.
Creates thorough and accurate IT documentation that exceeds requirements.
Creates IT documentation that meets requirements.
Creates IT documentation that lacks detail and/or does not fully meet requirements.
Does not create appropriate IT documentation.