Vehicle Security Management system for provision of security to cabs operators and their clients

Project Report structure

The project must include the following items in the sequence shown:

(a) Title Page (see 1.8 formatting details )

(b) Abstract – This is part of the title page (see 1.8 formatting details). The abstract is a summary of the report. Be precise: the abstract should not exceed 250 words.

(c) Project Topic outline – Include the original project topic outline that you chose for your project. This is helpful for the second marking understanding what your project is about.

(d) Table of contents (with page numbers),

Use the automatic Table of Contents (TOC) function in Microsoft Word to generate the TOC. Ask your Supervisor, Unit Coordinator or Google if you are unable to use this

(e) Lists of Symbols; Tables; Figures; Abbreviations (where applicable):

(f) Body: the actual report consists of sections arranged to suit the individual needs of each project, and should include the following:

1. Introduction including any relevant background information.

3. A description of the aim of the project.

2. Background research/literature review/requirements analysis. This should be based on the work you completed in the interim report and the heading used needs to reflect the project type undertaken.

4. A description of the methods/approach used to implement your project (including justification of the choices made where appropriate).

5. Results /Implementation, discuss the outcomes of the method used. For other types of project reports, it is expected that some tabular data that shows the results of your project activities/methodological approach will be included.

6. Analysis and discussion of the project outcomes. From the work you have completed, extract the important issues from the information you have accumulated and choose suitable information (diagrams, images, graphs etc), to aid the comprehension of the text. Explain the significance of the project outcomes in relation to other relevant published work.

7. Conclusions: A critical statement of what has been achieved or demonstrated with this project, based on the analysis and discussion of the results. The conclusion should sum up the main points of the report and should clearly relate to the objectives of your report.

Don’t include any new information in the conclusions.

8. Recommendations (where applicable): A statement of further work or action you consider to be necessary, e.g. during the investigation/project it may have become apparent that it would be desirable to carry the study beyond the planned objective or that some problems encountered should be explored in greater depth than was possible or necessary in the current project.

(g) Lessons Learned: this section enables students to step back from the project and more objectively analyse what they have learned from the project. This section should address the following issues:

· Did the project meet scope, time, and cost goals?

· Were the IT practices used in your project conducted ethically (use the ACS Code of Ethics to respond)

· In terms of managing the project, what were the main lessons you learned?

· Describe one example of what went right on this project.

· Describe one example of what went wrong on this project.

· Outline what will you do differently on the next project based on your experience working on this project?

(h) References: Please note that incorrect referencing may constitute plagiarism. Students should use Harvard Style. (See formatting guidelines)

(i) Appendices: Appendices should contain material which is too detailed, technical, or complex to include in the body of the report. All appendices must be referenced in the main text. Appendices may include:

1. Detailed theoretical analyses.

2. Tabulated records of results, with reference to instruments or sources as appropriate.

3. Graphs, drawings, diagrams etc, not included in the main sections.

4. Software details and program listings.

5. Only selected, concise examples of code and other developed products (for example requirements design specifications are to be included in the body of the report.)

6. Examples of software /code

Appendices are NOT COUNTED as part of the word limit.