Professional Documents
Culture Documents
The report structure relates to the scenario described and previously published; you are asked to plan (but not implement) a project for the FROSTIE and SCIMITAR systems for client Sam Dapper, MD of SMARTS Ltd. You should prepare a report, addressing all sections and maintaining the sequence given below. Guidelines (which should not be exceeded) for the maximum length of each section are specified; answers shorter than this that deal with the required issues are acceptable. The text should be in font size 12 (no smaller) and preferably Times Roman or Arial, although headings and sub-headings may be in a larger font. The final version you submit must be printed. Please print your final version on standard A4 paper; using a heavier weight paper will not earn a higher grade. Margins must be wide enough for the report to be read if presented in a folder (e.g. 1 inch or 2.5 cm all round) without removing the pages from the folder. The folder or binding must open flat within all text clearly visible, or the report may be stapled in the top left-hand corner. Reports submitted in a plastic pocket should be stapled in the top left-hand corner; please do not submit loose sheets. This work must be your own. Material from any other source must be clearly indicated where used and identified in the references section. You must not cut-and-paste material from other sources without indicating that it is a quotation. Guidance is available from the library The deadline for submission of your report to Undergraduate Office, North Campus Tower Block is WEEK 20 Friday 1st March 2013. You may submit your work earlier than this if you wish. Your assignment must be in the format and sequence specified in Parts A and B below, with a standard coursework cover sheet. Please do not include CDs/DVDs/disks in your submission, and do not submit your work by email.
Overall presentation (2 marks) The report should be word-processed. The main body of the report should start from page 1, and each heading and sub-heading shown in the table of contents. The Gantt chart does not need to have page numbers, but there should be a numbered page indicating the start of the Gantt chart. The Gantt chart should be in an easy-to-read format (e.g. joined so the entire chart on several A4 pages will fold out flat). Title page The report is for the management of the client organisation, and should have an appropriate title page, containing the report title, recipient, author and date. You may add your own logo if you wish. The title page should not have a page number. . The title page may contain a logo, but it must give the name of the client, the identity of the author (name and student id) and the date of submission. (Maximum 1 page) Management Summary The title page should be followed by a management summary, giving details of the context, timing, purpose and cost of the project. You should also identify any special features of your project. This page should not have a page number. (Maximum page) Table of Contents The table of contents must use the numbered headings and sub-headings specified below, and identify the corresponding page numbers in the text. The ToC facility in MS Word may be used to generate the table of contents. All subsequent pages must be numbered, and the page numbers must be printed, not handwritten. Page numbers should appear on every page except the title page, management summary and table of contents. The main body of the report must start at page 1 (Maximum 1 page)
Report Structure
Report Structure
Section 4: Installation
4.1. Deployment plan (5 marks) What is the overall approach to the installation of the FROSTIE and SCIMITAR systems, i.e. how will the systems be deployed (or "rolled-out")? Justify the selection and explain how this approach will be used in practice. How will training and data migration fit in to the overall plan? (Maximum 1 page)
4.2. Data migration (5 marks) What data is required in the new systems? Is there any existing data that is not required in the new systems? How will existing data be transferred into the new systems? Who will be involved in this process? When should data migration take place in relation to other installation activities? (Maximum 1 page) 4.3. Training (5 marks) What training is required by different end-user groups? Which end-user groups who will require training? When is training required? What training methods will be used? Where will training be carried out, how long training will last, and who should perform it? How does the training plan fit with the overall deployment strategy? (Maximum 1 page)
5. Support
5.1. Support needs (5 marks) Who will require support? Identify the different user groups who will have access to the support service. What are the specific needs of each group? How will it be possible to distinguish between different users and groups? What are the hours of service during which support is offered? What provision is made outside the normal hours of service? (Maximum 1 page) 5.2. The ISST Help Desk (5 marks) How will the SMARTS ISST support service operate? Provide a detailed description of the proposed ISST Help Desk, including: the intended support model under which it will operate where the Help Desk will be located, and how it will be staffed an explanation of the different roles and skills required of the support staff (Maximum 1 page) 5.4. Support service levels (5 marks) What are the service level targets for each category of support issue? Are there any other service level targets? Are there any exceptions? How will the Help Desk Manager monitor whether these service levels are achieved? What action should be taken as a result this analysis? (Maximum 1 page)
Report Structure
8. References (4 marks)
Specify any references that have been used in preparing the report, including textbooks and web sites. Indicate clearly in the main body of the report where references have been used. Do not use material from other sources without identifying the sources in this section. Use the Harvard style of referencing. There is no maximum length for the references section, but one or two pages should be sufficient.
Appendix (4 marks)
Include an appendix of material used in research for this report (e.g. search results relating to project staff recruitment or equipment). The appendix may contain printouts and/or commercial vendor literature. (Maximum 6 pages)
Section Title page and contents Management summary 1. Background 2. Risk 3. Costings and resources 4. Installation 4.1. Deployment 4.2. Data Migration 4.3. Training 5. Support 5.1. Support needs 5.2. The help desk 5.3. Support service levels 6. Work packages and activities 7. Gantt chart 8. References Appendix Overall presentation Total
Weightings 5 5 10 5 15 0 5 5 5 0 5 5 5 10 10 4 4 2 100
Report Structure