FINAL YEAR PROJECT REPORT

Title

By

Name Registration # ProgramName Registration # ProgramName Registration # ProgramName Registration # Program

Supervised by

Supervisor name

Bahria University (Karachi Campus)

Year

Title of project

2 of 24

Title of project

Final Year Project Report (font size 16)

Title (font size 16-20)

By

Name Registration # ProgramName Registration # ProgramName Registration # ProgramName Registration # Program

Project Advisor XXXXXXXX

DeliverableReport 1 Volume Program 1 CD

Bahria University (Karachi Campus)

3 of 24

Title of project

Submission Performa

Name (1)………………. (Student’s Name)

(2)………………. (Student’s Name)

(3)………………. (Student’s Name)

Address (1)…………. … (Student’s address)

(2)…………. … (Student’s address)

(3)…………. … (Student’s address)

Title of Report

Project Supervisor’s Name

This report is submitted as required for the Project in accordance with the rules laid down by the Bahira University as part of the requirements for the award of the degree of Bachelor of Engineering. I declare that the work presented in this report is my own except where due reference or acknowledgement is given to the work of others.

Signatures of students Date

(1)…………………………….. ……………………..

(2)……………………………. …………………….

(3)…………………………….. …………………….

Signature of Supervisor Date

…………………………. ……………………….

4 of 24

Title of project

Acknowledgments

This page should consist of the acknowledgements to the people, companies and institutions that have been helpful to the author in compiling the reports. It is normal practice to thank the Head of Institute for the use of facilities with which the project was carried out, the supervisor for his/her suggestions and guidance and any other member of the academic and technical support staff who have made a significant contribution to the success of the project.

5 of 24

Title of project

Abstract

The abstract is a brief summary of your research. Typically, an abstract should be one page and/or less than 350 words. Your abstract should consist of concise precise to inform the reader of the content of the report, what the project was about, the main aim of the project, how the work was undertaken and major conclusions drawn from the work performed. It is important not to confuse an abstract with introduction. The first sentence should give the subject of the report and the last sentence should state the primary conclusion of the report. The abstract should be written in the present tense. It should not include illustrative material such as formula, diagrams, and charts. The abstract page numbered ii. It should conclude with short entry ‘Keywords’ …..Nominating several keywords by which a computerized library would find the project.

6 of 24

Title of project

Table of contents

The table of the contents is on a separate page and is numbered iii. The table of contents lists the sections of the report, a list of figures and a list of tables along with the page on which they begin.

1. INTRODUCTION.....................................................................................................9

2. BACKGROUND AND LITERATURE REVIEW...............................................10

3. AIM AND STATEMENT OF PROBLEM............................................................11

4. ANALYSIS AND DESIGN.....................................................................................12

5. IMPLEMENTATION.............................................................................................13

6. TESTING..................................................................................................................14

7. RESULTS.................................................................................................................15

8. DISCUSSION...........................................................................................................16

9. CONCLUSIONS......................................................................................................17

10. FUTURE WORK.................................................................................................18

11. APPENDICES......................................................................................................19

12. GENERAL GUIDELINES.................................................................................20

12.1 TYPING AND SIZE OF PAPER...............................................................................2012.2 PAGE NUMBER AND SECTION NUMBER..............................................................2012.3 MARGIN BOUNDARIES........................................................................................2112.4 DIAGRAMS AND FIGURES...................................................................................2112.5 PHOTOCOPYING..................................................................................................2212.6 FIXING OF PHOTOGRAPH....................................................................................2212.7 TABLES...............................................................................................................2212.8 EQUATIONS.........................................................................................................2212.9 UNITS.................................................................................................................2312.10 REFERENCES...................................................................................................23

12.10.1 List of References...................................................................................2312.10.2 Journal Articles.....................................................................................2312.10.3 Conference Paper..................................................................................2412.10.4 Books......................................................................................................2412.10.5 Manuals.................................................................................................2412.10.6 Unpublished Reports and Theses...........................................................2412.10.7 Web Based.............................................................................................24

7 of 24

Title of project

List of symbols and Units

A list of symbols and units should be included to assist the reader. This should include any Greek letters or other mathematical symbols together with the quantities to which they refer, and their appropriate units.

8 of 24

Title of project

1. Introduction

This should introduce the reader to the subject are described in the report, what the project was about and why it was undertaken. It should be written in a manner sufficient to allow a reader unfamiliar with the project to appreciate any background knowledge necessary to understand the report.

Describe the function, show the block diagram, and give the performance specifications as they appear in your final proposal. Show that you know what variables are important in your project’s performance, and what values they should take on. Describe briefly the subprojects into which the project has been divided. Introduce the structure of the report (what you will cover in which chapter).

9 of 24

Title of project

2. Background and Literature Review

This section should describe the current state of knowledge concerning the subject involved in the project. It should review literature on the subject and highlight the information relevant to the immediate activity undertaken in the project. The survey should cover a sufficient amount of available literature to highlight the gaps in current knowledge and to support and allow predictions to be made regarding main work covered in the project. Try to include related work (if you know). Where literature source are quoted, these should be accompanied by the author/s surname and year of publication within parentheses referring to the “Reference” section of the report.

10 of 24

Title of project

3. Aim and Statement of Problem

The aim of the project should be clearly stated with sufficient explanation to make these easily understandable. Write succinct definition of the problem. Defines and limits the ‘Scope’ of the effort. Clearly describe how you tackled the problem. Provide enough information for knowledgeable person where difficulty or lack of time has caused a change in the aims of the project. The nature of any changes in aims and the reasons for these changes should be explicitly stated within this section.

11 of 24

Title of project

4. Analysis and Design

Requirement capture.

Comparison of different choices for algorithms and data structures.

Overall system structure.

Context diagram, Data flow, actor-usecase diagram, entity relation, and object diagrams as appropriate.

Use your project logbook (file) to remind you of what decisions you took, and why you thought at the time they were good. Later, in the evolution, you can criticize them.

12 of 24

Title of project

5. Implementation

Give code details (not a complete listing, but description of key parts). Discuss the most important/interesting aspects. It probably won’t be possible to discuss everything- give a rationale for what you do discuss. Code shall not be more than 3-5 pages.

13 of 24

Title of project

6. Testing

Test plan – how the program/system was verified. Put the actual test results in the Appendix.

14 of 24

Title of project

7. Results

This covers different areas to the ‘Testing’ chapter, and is appropriate for ‘research style’ projects. For such projects this chapter should detail the types of experiments/simulations that were carried out with the code written. Why were certain experiments in the simulation and how did they affect the results? (Refer to your logbook!) If there are very many graphs and tables associated with this Chapter they may be put in appendix.

15 of 24

Title of project

8. Discussion

This section should fully and logically discuss the progression of the project including the methods used and the results of experimentation, or the design; in such a way that examiner can evaluate the worth of the project. The discussion should be backed by detailed reference to material in the testing and result section of the report.

16 of 24

Title of project

9. Conclusions

This section should be a concise statement of the conclusions which may be drawn from the work attempted. The reader needs to be convinced that the design will work. If

Uncertainties remain, they should be pointed out, and alternatives, such as modifying performance specifications, should be spelled out to deal with foreseeable outcome.

17 of 24

Title of project

10. Future work

This section may be used to propose further work which may be carried out on the project in subsequent study projects. Suggestions of this type should be limited to proposals which involve significant amounts of work such as major modifications of equipment or development of student practical experiments. Any suggestion is to be given in sufficient detail to provide adequate information for a future student to be able to fully appraise the proposal.

18 of 24

Title of project

11. Appendices

These shall be used to give detailed results that shall be summarized in main text. The normal practice is “Annex A, B, C…” and, when required, “Appendix (to annex) 1, 2, 3…..” They should identify on every page by running header. Following items should be included in appendices

19 of 24

Title of project

12. General Guidelines

- Begin each chapter on new page.

- Each chapter should have small introduction at beginning of chapter. Introduction must link to previous chapter. It is a one or more than one paragraph but not more than one page that introduces the reader to the subject. The introduction presents basic background material, the history of the problem and contains the key sentence outlining the subjects to be discussed.

The total report length should under no circumstances exceed 150 pages; most projects somewhat shorter. There is no value in trying to artificially lengthen your project by ‘padding’ it. Each project is unique and has its own natural length, and you will probably know when you have said everything that you need to be said.

12.1 Typing and size of paper

I. The report is to be typewritten on one side of the paper on international size A4 paper (297mmX210mm). This paper must be good quality bond.

ii. Reports length should be 80-150 pages.

iii. Use Times New Roman, size 12 font throughout the reports.

Use 1.5 or double spacing.

12.2 Page number and Section number

- Use lower case Roman numerals for preliminary pages

I. Title page (not numbered on page)

ii. Abstract

Table of Contents

The text of the report begins with Arabic number 1. Number all pages. Page numbers can be inserted either at the bottom/top right or the bottom/top center.

20 of 24

Title of project

All appendices should number as A-1, A-2, etc. for pages under appendix A, and B-1, B-2, etc. for pages under appendix B (See Table of Contents.).

A hierarchical numbering scheme for chapter numbering shall be used. For instance, use 1 for chapter one, 2 for chapter 2, 1.1 for the subsection 1 of chapter 1, etc. (See the Table of Contents).

12.3 Margin boundaries

I. 1 -inch left margin.

ii. 0.5-inch margin on the other three sides.

12.4 Diagrams and figures

Figures and table should be inserted in the text in one of the three places

A full page diagram or illustration must be inserted on the left hand side facing the typescript which described it.

Small diagrams should be incorporated in the text with the legend appearing below (not recommended).

Each graph, diagram, etc., should have a figure number and title typed below it. The type style should be same as the text. Figures should be numbered consecutively (Fig.1, Fig. 2) or by chapters (Fig. 1.1, Fig 1.2, Fig. 2.1, etc). Whichever numbering system you use, make sure that you follow the same system for tables and equations.

Line drawings, graphs, and monograms should be in bold clear lines. Where graphs, diagrams and figures cannot be mounted vertically on the page these are to be mounted and labeled in such a way that they can be read from the right hand side(900 on the page) of the page .

All the axes of graphs are to be labeled with the parameter and its units. Information on illustrations and graphs such as labels, scales etc. must be typewritten.

21 of 24

Title of project

12.5 Photocopying

All the diagrams, etc. must be reproduced by an electronic or electrostatic or photographic method which is known not to fade.

12.6 Fixing of photograph

Full page photographs should be bound into the report. Small photographs must be firmly fixed to the paper. An alternative is to use color photocopying or digital processing.

12.7 Tables

Each table should be numbered consecutively (Table 1, Table 2) or by chapter (Table 1.1, Table 1.2, Table 2.1).Table number should be centred above the top of the table and be followed on the next line by a brief descriptive caption, preferably in cap. The type should be the same as the text. Refer to each table in text by number “In Table 1, one can clearly see………”The same rules for location of figures apply to tables.

TABLE 1. MEASURED RESISTOR VALUES AND THE METER ERROR

Nominal Value Marked Measured Value Error (%)

12.8 Equations

Centre each equation on separate line. Number equations consecutively in parentheses at the right margin. Equation may be referenced by number in the text, using parentheses around the number.

Y (t) = sin (x) dx (1)

22 of 24

Title of project

12.9 Units

The S.I. system of units is to be used throughout. Where difficulties are introduced by quotation of imperial units from reference source, these should be accompanied by the appropriate conversion to S.I. units in parentheses.

12.10 References

The references must list all published information sources that are directly quoted or used to support the technical discussion or equations. Reference to these sources must be made at the appropriate points within the report text. Use numbers enclosed in brackets in the text [1]. Each reference is preceded by a bracketed number in the list of reference. Reference number in the text should look as follows

[1] “User-friendly Support Environment for Requirement Analysis In User Interface Design”, Seongjun Yun, Minseok Pang, Hongjin Cho, Jongho Chae, Yoonjung Choi, Eun-Seok Lee

[1]

[3], [4]

[5]- [7]

These are all to be on the line and within punctuation marks. Example for textual referencing.

Maxwell [1] states that………

Reference should be cited as follows

12.10.1 List of References

References should be ordered alphabetically according to the surname of the first author (use the editor’s name or the organization’s name when the author’s name is absent). A list of references is the last section of each chapter.

23 of 24

Title of project

12.10.2 Journal Articles

R. A. Barry and P. A. Humblet, “Models of blocking probability in all-optical networks with and without wavelength changers,” IEEE JSAC/SAC/LT Special issue on Optical Networks, 14(5) pp 858-867, June 1996.

12.10.3 Conference Paper

Gouda, M.G. and Dayal, U. (1971). Optimal semi-join schedules for query processing in local

Distributed database systems. In Proceedings of ACM SIGMOD International Conference on

The Management of Data, (Ann Arbor, Michigan, April 29 – May 1, 1980.) ACM, New York, 1981, pp. 164 – 165.

12.10.4 Books

Papoulis, Probability, Random Variables, and Stochastic Processes. McGraw-Hill, New York, 1984

12.10.5 Manuals

IBM. (1984). Information Systems Planning Guide. Fourth Edition, July 1984. SPSS Inc. (1983). SPSS-X User’s Guide. McGraw Hill Book Company, New York, 1983.

12.10.6 Unpublished Reports and Theses

Thorpe, A. (1982). Stability tests on a tender-price prediction model. M.Sc. Thesis, Loughborough University of Technology, UK. 1982.

12.10.7 Web Based

http//www.westwords.com/guffey/apa.html, “introduction of information technology”, West world technologies , last visited on 12 November 2008.

24 of 24