School Work

Interim Report Template

Description
this is basic template on how to an interim report for a project..
Categories
Published
of 4
All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.
Related Documents
Share
Transcript
  WH/CAT300/Sem1[2011/2012]/Interim Report 1 SCHOOL OF COMPUTER SCIENCES SEMESTER I, ACADEMIC SESSION 2011/2012 CAT 300  –  GROUP INNOVATION PROJECT REPORT WRITING GUIDELINES EXPECTED CONTENT Title Page This should contain the following information: Course Code and Course Title Project Title Full name of authors, metric numbers, specialization Full name of supervisor Full name of course coordinator Month and year of submission. Note that the title page should not show a page number.  Abstract This should be not more than one page in length. The abstract should allow the reader who is unfamiliar with the work to gain a swift and accurate impression of what the project is about, how it arose and what has been achieved. Tables of Contents This should give a complete list of what the report contains starting with the abstract (the title page is not included in the table of contents). List of Tables/Figures If the report contains figures or tables a list of these should be provided. The list should give the table or figure number, the title of the table or figure and the page number. If only a few tables and figures are present, they may be treated on one page. Remember that all figures and tables used must be referred to in the text. For example “The class diagram shown in Figure 2.1 ....”    Acknowledgements It is normal to thank those who have given help and support (typically your supervisor). Keep acknowledgements short and business-like.  WH/CAT300/Sem1[2011/2012]/Interim Report 2 Introduction This section introduces the reader to the subject area in the project. It may include such things as: how the need for the system was identified the nature of the system motivation and objectives proposed solution and expected result Background A brief outline of the project work should also be included. Some evidence of reading around the area is expected. This reading could be outlined in a References Section. A plan of organization for the project should be stated in the introduction section. Methodology (Main Body of the Report) This section should/could be divided into a number of chapters and sub-chapters. Each of these should contain a reasonably separate topic of discussion and be arranged in a logical sequence. The linkage between chapters should be stated clearly at the beginning and/or the end of each chapter to show the relationships between chapters. Conclusion The conclusion chapter should state briefly the achievements of the project, the conclusions and suggestions for further work.  Appendices These should be used for reference material, such as selected pieces of research data and other information which is too bulky, or would detract from the flow of the text, if included in the main body of the document. Try to make reference material that will be consulted from many different places in the document and appendix. Otherwise, put the information into a figure or table and keep it close to the text that refers to it. References  There should always be a list of all books, articles and technical resources consulted. The use of all source material should be explicit in the report. This means that normally ever item in the reference list will be referred to in the report and every item mentioned in the report will have an entry in the reference list. The reference in the text could appear as “…  the best system [23].. .” and the Reference S ection would have: [23] “ … is Linux the best “ , Linux World, John Waters, Dec 02 , pp 23 – 45.  WH/CAT300/Sem1[2011/2012]/Interim Report 3 EXAMPLE LAYOUT FOR INTERIM REPORT (max 20 pages) Abstract (page i) The whole project in miniature  - Problem statement   - Key Requirements - State main objectives  –  What did you investigate and why? - Describe methods  –  What did you do? - Summarize important results  –  What did you find out? - State main conclusions  –  what do your results mean? - Recommendation for future development Table of Contents (page ii) List of Tables and Figures (page iii) Acknowledgement (page iv) Chapter 1: Introduction (Start with Page 1) - Research background - Motivation - Problem description - Describe the problem investigated - Objectives of the work - System scope - Proposed solution - Organization of the report Note : Move from general to specific  –  relate problems in the real world to your research. Make clear links between the problem and the solution. Chapter 2: Background Study - Review relevant past research to provide rational for your work. - Summarize relevant research to provide context, key terms, and concept so the reader can understand the study. - Details of relevant theory/model - Briefly describe your research  – research questions, hypothesis, etc. - Brief introduction of the proposed work/solution  WH/CAT300/Sem1[2011/2012]/Interim Report 4 Methodology    Chapter 3  –  Project Management Plan - Identify project scope, system capabilities and system limitation - Project management : (a) work breakdown structure- WBS (b) work schedule- GANTT chart and milestone timeline (c) SWOT analysis and Risk Management - Feasibility Assessment (NPV and ROI)  –  if applicable Chapter 4: System Analysis - General description of the current system (problems, weaknesses, opportunities) - Detail requirements of new system (information gathering, requirements modeling  –  functional and non-functional requirements) - Analysis of the new system using appropriate UML diagrams (use case diagram, use case descriptions, class diagram, system sequence diagram and state chart diagrams) Chapter 5: System Design - Requirements specification- Requirement chosen as basis of design - Design Strategy (Choice of hardware and software and justification of choice  – why and comparison with others) - Proposed System Architecture Chapter 6: Discussion and Conclusion - Discussion on the group achievements. - Plan for Completing  –  Detailed schedule of tasks that still must be done (with deadline, names of who is responsible for each task and to what extent). Note: Different type of projects (other than Information System) may require different approach of report writing. Please consult your supervisor on the report writing requirement.   Content Advice
We Need Your Support
Thank you for visiting our website and your interest in our free products and services. We are nonprofit website to share and download documents. To the running of this website, we need your help to support us.

Thanks to everyone for your continued support.

No, Thanks