4. The Project Presentation and Demonstration The presentation should contain between 10 and 15 slides and should be structured as follows: • An overview of the context/background of the project • An overview of the analysis and design activities (high level model of the system, techniques used, key design decisions) • An overview of the testing (techniques, a summary results, conclusions) • A critique of the process (what went well, what didn't, what you have learned, what you would do differently next time) Don't forget to illustrate this by taking lot of pictures from the websites. More details for presentation mark scheme: Presentation Content - Appropriate level of technical details (10 marks) - Content clearly structured and relevant (10 marks) - Presentation shows a thorough grasp of project issues (10 marks) - Presentation identifies scope for further work (10 marks) - Presentation has effective introduction and conclusion (10 marks) Presentation Skills - Student introduces information confidently and effectively (10 marks) - Student engages audience with content and performance of presentation (e.g. eye contact, body language, clear speech) (10 marks) - Student delivers material with appropriate structure (10 marks) - Student displays effective time discipline (10 marks) - Student concludes material confidently and effectively (10 marks) 3- The Project Report Your project report is an account of the work done in terms of the development of the computing artefact. It is important that you plan for the report to communicate with the people reading it. This means producing a report that your supervisor will enjoy reading. The project report should be a well-structured word processed document that is easy to read. The project report should be 6000 (+/- 500) words in length. The precise structure of the project report is presented below: 3.1 Title Page This section should contain the following centred information: • The full title of the project • The full name of the author, followed by the student registration number in brackets • The centre at which the author is studying 3.2 Abstract This section should consist of a synopsis of the project (150-200 words) stating the nature and scope of the work undertaken, and a high level summary of the outcomes. 3.3 Contents Page This section should show the page numbers of chapters, sections and sub-sections, a list of figures and tables, and a list of appendices. 3.4 Acknowledgements This section is optional, but you may wish to pay tribute to particular people who have given you special assistance or support. 3.5 Introduction This chapter provides the context of your work in terms of: • The system developed • Justification for the method or framework used • The solution that emerged • The main aims and objectives of the project • A short overview of the remaining chapters Further guidance with respect to the content of this chapter is provided in Topic 5. 3.6 Analysis This chapter consists of the analysis specification of the proposed system in terms of: • Requirements • Use Cases • Architecture Further guidance with respect to the content of this chapter is provided in Topic 2 3.7 Design This chapter consists of the design specification for the proposed system in terms of: • Structural Model • Behavioural Model Further guidance with respect to the content of this chapter is provided in Topic 3. 3.8 Implementation This chapter describes your approach to implementation in terms of: • Choice of programming language • System cutover from the development architecture to the implementation architecture • Data migration from the development architecture and/or existing systems to the implementation architecture • Training Further guidance with respect to the content of this chapter is provided in Topic 5. 3.9 Other Project Issues This chapter provides an account of your approach to project management, risk management, configuration management and testing. You need to describe what particular techniques you have used, why you have used these rather than others, and present a summary of your main results. Further guidance with respect to project management, risk management and configuration managed is provided in Topic 1, whilst Topic 4 provides further guidance with respect to testing. 3.10 Conclusion This chapter evaluates the substantive aspects of your work, within the context you have established in the Introduction. It also comments on the extent to which the original aims and objectives have been met. In addition, you might wish to comment on any envisaged future development of the system. Further guidance with respect to the content of this chapter is provided in Topic 5. 3.11 References All references you cite within the body of your report should be fully referenced in this section, using the Harvard Style. No reference should appear here unless it has been cited in the body of the report. 3.12 Appendices Appendices may include any supporting material to which a reader might wish to refer, but which is not essential for the main body of the report. Appendices for the computing project may include some, or all, of the following: • Requirements Catalogue • Use Case Descriptions • Detailed Class Definitions • Test Scripts • User Guide • System Code • External Client Documents where applicable (see Section 4 below) Project Report more details for the content INTRODUCTION,ANALYSIS, DESIGN and CONCLUSION already mentioned above Documentation items: 1. Introduction - Abstract (5 marks) - Background to the system (5 marks) - Overview of design (5 marks) - Aims and objectives (5 marks) 2. Analysis - Identification of functional requirements (10 marks) - Identification of non-functional requirements (10 marks) for these I have already done it please check attached document - Provision of appropriate diagrams (10 marks) 3 Design - Outline of structural model (10 marks) - Outline of behavioral model (10 marks) - Justification of approach taken (10 marks) Conclusion - Conclusion (5 marks) - Evaluation of work (5 marks) - References and bibliography (10 marks) For the appendixes dont forget to make a good user guides and take lot of picture from the website in order to illustrate this final report very well.