Document extension Maintenance: Preventative/Periodic based Maintenance 17% Incomplete Incomplete Prives a minimum of maintenance items that require periodic maintenance Defines the period of each maintenance interval for each periodic maintenance item Includes maintenance of risky or long-lead items Creative investigation of the system that exposes deep understanding on whole system interactions. Includes maintenance of relationships between components. Maintenance: Ad-hoc/Repair based Maintenance 17% Incomplete Incomplete Describes maintenance actions on multiple items Also includes a flow chart for multiple repair maintenance actions for multiple items Also provides a causes and effects relationship for multiple ad-hoc maintenance items Indicates deep understanding on the failure modes of the entire sub-system that is covered by the group. Maintenance: Requirements based Maintenance 17% Incomplete Incomplete Very generic maintenance details described Minimally describes the maintenance of each requirement.

Requirements + testing sections 7% Incomplete Incomplete Regurgitation Citation/interpretation Risk or long-lead items Creative investigation Project Plan (Gantt charts and project stages) 3% Poor/Missing Poor/Missing Schedule/Gantt Previous plus WBS, project stages All previous plus quantified All previous and risk/contingency Introductions of steps/procedures 3% Incomplete Incomplete Regurgitation of provided material Concise rephrasing Insight Extended understanding Top down approach / Systematic EDP 3% Incomplete Incomplete Complete process demonstrated Exceptional depth/breathe in 1 area Exceptional depth/breathe in multiple areas Consistent/metered depth/breath at a professional level

Document content Executive Summary 5% Incomplete or missing Incomplete or missing Regurgitation of provided material Summarizes Summarizes and reviews Abstracts Improvement on Text and document body structure 3% No structure or organisation of content No structure or organisation of content Minimal use of bullets All ideas conveyed with prose and proper sub-headings Prose and sub-headings used to convey structure of actual process or project management Professional balance between brevity and depth/breathe or similar communication skill demonstrated

/10 0 3 5 7 8 10 Assessible % contribution Fail Fail Pass Credit Distinction High Distinction Inclusion of the previous GRADED report 5% Missing Missing N/a N/a N/a Included in appendix Improvement of previous report Professionalism Layout 5% Poor Poor Template implemented, professional appearance Goes beyond use of template Develops structure to extend & support overall document Thesis or publication quality document Figures and table (incl captions) 5% Poor/Missing Poor/Missing Appropriate with good aesthetics Previous and integrated with text All previous and insightful demonstration All previous and used as focus/summary of effort

The document one member will submit, on behalf of the group, will be constructed by starting with the testing document and then adding the section on Support and Maintenance. Note that at each of these submissions are contributing to your final report and therefore you need to take the feedback from each stage and improve on your existing report to maximise your mark for the final document. You will be expected to deliver the entire document each time. Different sections of the final document will be checked at each of these milestones. Each document must also include a table at the front detailing each member's contribution within the entire group.

As a part of the documentation for the ENGG200 cohort, you will be required to write and then submit a version of the requirements document. This document will cover requirements, testing and support/maintenance. You will be expected to follow the given template and make the required modifications. The general marking rubrics is provided on iLearn. Up until now the ENGG300 students have been showing the ENGG200 students how it's done. Now it's time for the ENGG200 students to step up and take the lead. Building on what you've learnt, and with the help of your ENGG300/600 leaders the ENGG200 students will revise the requirements document and add the section on Support/Maintenance.