Final Report

1
Final Report
2
Project Deadline

• Project submission date To be notified on
  websiteend of teaching week 12 in the second
  semester

3
Report Structure

• Introduction
• This should be a short chapter.
• Revisit the problem and describe the motivation
  (Initial report helps here)
• Aims and Objectives should be identified here
• provide the reader with some details as to what
  they should expect in the remainder of the
  report. (3 pages)
• Problem investigation and background reading
• Descriptions of other similar systems or
  technologies addressing the same problem domain.
• Again, the initial report helps here but the
  context/background to your project is described
  in more detail now in the final report
• Probably a more significant chapter for
  investigative projects

4
Report Structure

• Requirements Specification
• Detailed description of the analysis procedures
  of fact finding
• Consider requirements management
• Produce the Requirements specification (VOLERE
  maybe)
• Investigative projects need to define the
  parameters and scope of the problem.
• Remember, solutions solve problemsproblems arise
  from needrequirements define need
• If using an IDEAL model then this would be
  equivalent to Diagnosing the nature of the
  problem in order to define what needs to be
  addressed

5
Report Structure

• Detailed Design
• Should give an in-depth view of how the problem
  will be solved
• Describe the architecture
• Depending on project nature should address
  detailed design of
• User experience (Use Cases and UX modeling)
• Database (ER modelling)
• Behaviourswhich manipulate the DB and change the
  User Experience (Activity Diagrams)
• Investigative projects have an approach to
  solving the problem. This will vary depending on
  the nature of an investigation. If using IDEAL
  model, this chapter might be equivalent to
  Establishing a plan/course of action which when
  implemented will deliver a solution to the problem

6
Report Structure

• Implementation
• This chapter should focus on the aspects of
  implementation of the project.
• Should include (for example)
• Details of technologies used to develop the
  system
• Platforms used e.g. Windows NT, 128MB RAM etc.
• The implementation strategy used
• The implementation itself
• Details of key aspects of your project
• algorithm development
• web access
• main system functionality
• DB management/access
• Security issues
• Difficulties and decisions incurred during
  implementation.

7
Report Structure

• For an investigative project using the IDEAL
  model this chapter would be equivalent to Acting
  execution of the plan to solve the problem
• This might reasonably be a smaller chapter in an
  investigative project and would deal with the
  success or otherwise of executing the Established
  plan for solving the problem
• Note that it is possible that your Established
  plan might involve creating a new structure or
  set of processes for an organisation. If so these
  must be engineered and consequently this chapter
  might be a mini-engineering chapter and be quite
  large as a result

8
Report Structure

• Testing
• Details of testing of the system both during and
  after the implementation stage.
• Details of the test strategy employed
• e.g. unit testing, integration testing, black
  box, white box
• Description of the tests carried out
• A summary of the test results should be
  presented.
• It is not a bad thing to report any bugs your
  program may have!!

9
Report Structure

• For an investigative project, this chapter would
  be concerned with Validation of the implemented
  solution. For example, if you have designed a new
  structure or process for an organisation, you
  would concern yourself with the success of this
  new process in its working environment.

10
Report Structure

• Evaluation
• Reflect on the requirements. To what extent have
  the requirements been met by your solution? You
  may have specified measures to be used to judge
  the success of meeting a requirement. Now is the
  time to perform the measures and judge the
  success
• Reflect on the aims and objectives. For each
  objective in the project describe how your work
  meets the objective or otherwise. Reflect on how
  your work meets the project aims.
• Reflect on how the project/system could be
  improved with more time/effortfuture work
• For investigative projects the same format
  applies

11
Report Structure

• Conclusion
• Summarise main achievements
• Identify what you have learned from the
  experiencewhat has helped, what has hindered
• Try to emphasise the positive

12
Report Structure

• The semester 2 final report should be structured
  as follows
• Title page.
• Project title, student name, course, date (e.g.
  May 2011)
• Abstract.
• A summary of the overall project (1 page).
• Acknowledgments.
• It is customary to acknowledge help and advice
  given by staff, fellow students and others (where
  appropriate).
• Contents.
• Table giving chapters and sections with page
  numbers.

13
Report Structure

• Chapters as described.
• References and Appendices.
• Complete listing of all articles, books, manuals,
  web sites, etc. referenced in body of report.
• Software, screen shots, questionnaires, design
  material..

14
Report Guidelines

• Should contain in the region of 60 pages plus
  appendices.
• Three copies of the report should be presented,
  typed on A4 size white paper using an inkjet or
  laser quality printer.
• Type Font Times Roman
• Font size 12 point 1.5 spacing
• Margins at least 1 inch top and bottom of
  pages. 1.5 inches at the binding margin
• Page numbering in bottom centre of each page
• Front title page type title to show through
  window in front cover. This should include
  project title, student name, module code (COM618)
  and course.
• Bindinguse white front and back project covers.
  These may be purchased from the Print Room (Block
  7). USE WHITE PLASTIC COMB BINDERS.

15
Report Guidelines

• Give some consideration for the time to print and
  bind.
• THREE identical bound copies of the final report
  are required
• Each copy of your project should include a cd
  with an electronic executable version of any
  software where appropriate.
• Submit an additional cd to the project
  coordinator containing an electronic copy of your
  project in Word format
• Appendix must include source code as appropriate

16
What Next?
Email, or call in, if any issues arise.