pg project format2014

8/10/2019 Pg Project Format2014

1/28

h t t p : / / c s . a n n a u n i v . e d u

Project GuidelinesD ep a r t m e n t o f C o m p u t e r S c i e n c e & E n g i n e er i n g

(Post Graduate)

A NNA UNIVERSITY

PROGRESS THROUGH KNOWLEDGE


2/28

Preamble

These guidelines are intended to give both students and faculty members at the Department of Computer

Science and Engineering a set of procedures and expectations that will make the project evaluation process

easier, more predictable, and more successful. These guidelines should also be interpreted as the minimum

requirements of the degree awarded by Anna University Chennai. The Project Committee assigned forvarious programmes offered under Department of Computer Science & Engineering may add requirements

or guidelines as they see fit as long as there are no less demanding than the guidelines set forth in this

document.

Eligibility

The Eligibility criteria for PG student are to be followed as per the regulations given by Anna University

during admission. The project work for M.E. / M.Tech. consists of Phase I and Phase II. Phase I is to

be under taken during III semester and Phase II, which is a continuation of Phase I is to be undertaken

during IV semester.

MINIMUM CREDIT REQUIREMENTS TO DO THE PROJECT

Minimum credits shall be as follows:

PROGRAMME MINIMUM NO. OF CREDITS TO BE EARNED

M.E. / M.Tech 24 (for Phase I)

If the candidate has not earned the requisite minimum credits, he / she has to complete the arrears

(at least to the extent of earning the minimum credits specified) and then enroll for the project

(Phase - I) work in the subsequent semester.

In case of candidates of M.E. / M.Tech. not completing Phase - I of project work successfully, the

candidates can undertake Phase - I again in the subsequent semester. In such cases the

candidates can enroll for Phase-II, only after successful completion of Phase I.

Project work shall be carried out under the supervision of a qualified teacher in the Department

concerned. In this context qualified teacher means the faculty member possessing Ph.D degree

or PG degree with a minimum of 3 years experience in teaching PG courses.

A candidate may, however, in certain cases, be permitted to work on projects in an

Industrial/Research Organization, on the recommendations of the Head of his/her Department. In

such cases, the Project work shall be jointly guided by a guide of the department and an expert-as a


3/28

joint guide from the organization and the student shall be instructed to meet the guide periodically

and to attend the review committee meetings for evaluating the progress.

The Project work (Phase II in the case of M.E/M.Tech) shall be pursued for a minimum of 16 weeks

during the final semester.

The deadline for submission of final Project Report is 60 calendar days from the last working day ofthe semester in which project / thesis / dissertation is done. However, the Phase-I of the Project

work in the case M.E. / M.Tech. shall be submitted within a maximum period of 30 calendar days

from the last working day of the semester as per the academic calendar published by the University.

Evaluation of the Project

The evaluation of Project Work for Phase I & Phase II shall be done independently in the respective

semesters and marks shall be allotted as per the weight ages.

There shall be three assessments (each 100 marks), by a review committee, during each of the

project semesters for M.E. / M.Tech. programmes. The student shall make presentation on the

progress made before the committee.

The project work shall be evaluated for a maximum of 100 marks of which

20 marks will be through internal assessment. The Project Report prepared according to approved

guidelines and duly signed by the guide(s) and the Head of the Department shall be submitted tothe Head of the Institution.

The evaluation of the Project work Phase - I & Phase - II (M.E. / M.Tech.) will be based on the

project report submitted in each of the Phase I & Phase - II semesters and a Viva-Voce

Examination by a team consisting of the Guide, a Internal examiner (other than the guide) and a

External Examiner for each programme. The internal examiner and the external examiner shall be

appointed by the for Phase I and Phase II evaluation.

If the candidate fails to obtain 50% of the internal assessment marks in the PhaseI and PhaseII

and the Final Project he/she will not be permitted to submit the report for that particular semester

and has to re-enroll for the same in the subsequent semester. If a candidate fails to submit the

project report on or before the specified deadline, he/she is deemed to have failed in the Project

Work and shall re-enroll for the same in a subsequent semester. This applies to both PhaseI and

PhaseII in the case of M.E. / M.Tech.

If a candidate fails in the viva-voce examinations of PhaseI he/she has to redo the PhaseI in thesubsequent semester. If he / she fails in the viva-voce examination of PhaseII of Project work of

I

I

I

I

I


4/28

M.E. / M.Tech., he/she shall resubmit the Project report within 60 days from the date of viva-voce.

The resubmitted project will be evaluated during the subsequent academic session.

Every candidate doing M.E. / M.Tech., shall send a paper / patent for publication in a journal or a

conference. An acknowledgement from the Guide for having communicated to the journal or

conference shall be attached to the report of the project work. Such acknowledgements shall be

sent to the Additional Controller of Examination along with the evaluation marks by the team of

examiners without which the thesis shall not be accepted.

A copy of the approved project report after the successful completion of viva examinations shall be

kept in the library of the department.

General Suggestions and Expectations

The project is by far the most important single piece of work in the degree programme. It provides the

opportunity for you to demonstrate independence and originality, to plan and organise a large project over a

long period, and to put into practice some of the techniques you have been taught throughout the course.

The students are advised to choose a project that involves a combination of sound background research, a

solid implementation, or piece of theoretical work, and a thorough evaluation of the project's output in both

absolute and relative terms. Interdisciplinary project proposals and innovative projects are encouraged and

more appreciable.

A good tip is to try to think of the project as deliverable at reviews rather than an effort to deliver a fully-

functioning "product". The very best projects invariably cover some new ground, e.g. by developing a

complex application which does not already exist, or by enhancing some existing application or method to

improve its functionality, performance etc.

A straightforward implementation project is acceptable, but you must appreciate that it is unlikely to gain

high marks, regardless of how well it is done and its usage. Likewise, projects which are predominantly

survey reports, unless they are backed up with experimentation, implementation, or theoretical analysis,

e.g. for performing an objective comparison of surveyed methods, techniques etc. Pure survey reports, with

no supporting implementation or theory, are not acceptable.

PG Students are to decide on the Phase I & Phase II project with their proposal & project guide

during the month of April / November with a brief abstract.

In case of re-reviews, any number of re-reviews can happen depending on the discretion of the

committee and it should happen within the prescribed time.


5/28

If the student fails to attend the review or the guide refuses to endorse the students work. The

committee can invite HOD and HOD is empowered to resolve among further matters.

If the work of the candidate is found to be insufficient and plagiarism, the committee and HOD will

decide the further process.

HOD can initiate further steps to ensure the smooth implementation as deems appropriate of

guidelines.

Marks split-up

Committee - 30 Marks (Each 10 marks)

Guide - 20 Marks

Total - 50 Marks

Attendance register will be maintained separately in each lab. Attendance mark (5 marks) will be

awarded based on the interaction with guide (3 marks) and attendance (2 marks).

Choosing an Project

The idea for your project may be a proposal from a member of staff or your own, or perhaps a combination

of the two.

Staff Proposals

For projects proposed by members of staff you should discuss the project with the proposer as soon as

possible so that you have plenty of time to think about the best choices for you. Note that not every project

is suitable for every student: some may be specifically tailored to a particular degree and some may only

suit students with a very specific set of interests. Each proposal will indicate these constraints in order to

help you to make an informed choice.

Own Proposals

If you have your own idea for an individual project it is your responsibility to find a member of staff who both

approves of the proposed programme of work and is willing to guide it. You should first get the permission

of Project Committee, and may proceed with the same with the consistent consent of the guide.

I

I

I

I

I


6/28

Choosing the right project

The projects offered by staff may vary substantially in breadth, depth and degree of difficulty. The most

important thing is to shortlist a set of projects that are right for you. Some students are better suited to well-

defined and relatively safe projects that provide scope for demonstrating proficiency with a low risk of

failure. Other students are better advised to tackle harder, riskier projects that require a high degree of

original input and/or technical problem solving.

If you are in are hope to win one of the illustrious project prizes, or achieve "Distinguished Project" status,

you should choose your shortlist with particular care. The potential guides will be happy to offer advice on

the suitability of a project, given your individual background, strengths and ambitions. Remember that it is

important to balance ambition and realism when making a choice. For better help of projects you can

search from websites like (IEEE, ACM, Elsevier, Springer, etc...)

Meeting Your Guide

You must make sure that you arrange regular meetings with your guide. The meetings may be brief once

your project is under way but your guide needs to know that your work is progressing. If you need to talk to

your guide between meetings and cannot locate them in their office, contact him/her and asking him/her to

suggest a time when they will be available. When you go to see your guide (or second marker) you should

have prepared a written list of points you wish to discuss. Take notes during the meeting so that you do not

forget the advice you were given or the conclusions that were reached.

Guides

The Guides are advised to give projects and suggest project titles focussing more on the current field of

research and ensure the level of innovation. Also guides are advised to check for the formatting of thepresentation and project report. Staff member cannot guide more than three candidates on the academic

schedule.

The Project Presentation and Demonstration

One of the most important skills which the project aims to assess is your ability to communicate your ideas

and work. As part of the assessment you will be required to give a presentation and demonstration of your

project to your Project Committee.


7/28

Each presentation will be for 10 and 20 minutes (to be decided by the project committee at the initial stages

and 30 to 40 minutes for the final stages including a demonstration. Guides will help you to structure your

talk and will be willing to go through it with you beforehand. The presentation is also a compulsory

component of the project. The project committee will not allocate a mark for a project unless there had been

a formal presentation. The objective of the presentation is to find out exactly what you/ your team have

done and to ensure that you get an accurate mark that is consistent with other projects.

Schedule for Project Reviews

ODD SEMESTER (July November) - M.E (Phase I)

Review Tentative Date

Zeroth Review Within 2 Weeks

First Review Within 6 Weeks but within schedule of 1stAssessment

Second Review Within 12 Weeks but within schedule of 2ndAssessment

Third Review Within 18 Weeks but within schedule of 3rdAssessment

Viva voce Mid of November

EVEN SEMESTER (December Apri l) M.E - (Phase II)

Review Tentative Date

Zeroth Review Within 2 Weeks

First Review Within 6 Weeks but within schedule of 1stAssessment

Second Review Within 12 Weeks but within schedule of 2ndAssessment

Third Review Within 18 Weeks but within schedule of 3rdAssessment

Viva voce End of April

The project committee is advised to conduct the project reviews for the students of various programmes

within the stipulated period and the review marks to be sent to the head of the department at the month

end. The project committee is also advised to make necessary arrangements required (Seminar hall

availability and Projector, etc...) for the smooth conduct of reviews.

I

I

I

I

I


8/28

Project Requirements: M.E (CSE / KECL / SW) Phase 1

Expectations from Students ( in the Presentation)

Zeroth Review First Review Second Review Third Review

Title

Abstract

Introduction

Literature Survey

Proposed System

Modules Split-up and Gantt Chart

References

Title

Abstract

Architectural Design for Proposed System (Phase 1)

ER Diagram, DFD, Use case diagram ( if necessary)

Algorithms / Techniques used

Expected outcomes

References

30% of code implementation

Title

Abstract

Detailed Design (if any deviation)

Contribution of the candidate

Results obtained (intermediate)

References

80% of code Implementation

Tile

Abstract

Overall Design (Phase 1)

Experimental Results

Performance Evaluation

Comparison with Existing system

References, Draft of paper

100% of code implementation Demo

Note:

The presentation should have maximum of 12 15 slides

Presentation will be for 15 minutes

A draft copy of the conference paper to be prepared at the end of the phase 1 based on the project work.

System to be tested using testing softwares.

For the Project Committe

The committee is advised to find the enough complexity in the project.

All the three panel members must be presented during the review.

The reviews to be conducted in the seminar hall and the available class rooms(in the department).

Guides to check

Advised to check for the formatting of the presentation and the documentation.

Check for the attendance of the students (Regular meeting for the discussion).

Advise the students to contribute some new techniques and advise them to publish a paper at the end of the project


9/28

Project Requir ements: M.E (CSE / KECL / SW) Phase 2

Expectations from Students ( in the Presentation)

First Review Second Review Third Review

Title

Abstract

Work completed for Phase 1

Architectural Design for Proposed System (Phase 2)

ER Diagram, DFD, Use case diagram ( if necessary)

Algorithms / Techniques used

Expected outcomes

References & 40% of code of implementation

Title

Abstract

Detailed Design (if any deviation)

Contribution of the candidate

Results obtained (intermediate)

References

80% code of Implementation

Draft copy of a paper

Tile

Abstract

Overall Design (Phase 1 & 2)

Integration & Experimental Results

Performance Evaluation

Comparison with Existing system

References, 100% code of implementation Demo

Copy of Published paper

App roval Guidel ines of Zeroth Review

Comparison with the existing systems and Complexity Metric (FP, Etc...)

Deliverables to be mentioned clearly for each review.

Work distribution among team members. Evaluation based on the complexity of the work.

Note:

The presentation should have maximum of 12 15 slides and Presentation will be for 15 minutes

Acceptance of conference paper at the end of the project work. * Mandatory

For the Project Committe

The committee is advised to find the enough complexity in the project.

The reviews to be conducted in the seminar hall and the available class rooms (in the department).

Guides to check

Advised to check for the formatting of the presentation and the documentation.

Check for the attendance of the students (Regular meeting for the discussion).


10/28

1

A MANUAL FOR PREPARATION OF PROJECT REPORT

CONTENTS

1. GENERAL

2. NUMBER OF COPIES TO BE SUBMITTED

3. SIZE OF PROJECT REPORT

4. ARRANGEMENT OF CONTENTS OF PROJECT REPORT

5. PAGE DIMENSIONS AND MARGIN

6. MANUSCRIPT PREPARATION

7.

TYPING INSTRUCTIONS

8. NUMBERING INSTRUCTIONS

9. BINDING SPECIFICATIONS

Appendix 1 : M.E. / M.Tech. / M.Sc. / MBA / MCA Title Page


11/28

2

A MANUAL FOR PREPARATION OF PROJECT REPORT

1. GENERAL :

The manual is intended to provide broad guidelines to the M.E. / M.Sc. / M.Tech.

/ M.C.A. / M.B.A. candidates in the preparation of the project report. In general,

the project report shall report, in an organised and scholarly fashion an account oforiginal research work of the candidate leading to the discovery of new facts or

techniques or correlation of facts already known (analytical, experiments,hardware oriented etc.)

2. NUMBER OF COPIES TO BE SUBMITTED :

M.E. / M.Tech. / M.Sc. / M.B.A. / M.C.A. : Students should submit five

copies to the Head of the Department concerned on or before the specified date.

The Head of the Department should send (i) One copy to the Zonal Coordinatorfor onward transmission to the University. (ii) One copy to the Department

library (iii) One copy to the internal examiner (iv) one copy to central library and(v) One copy to the student concened.

3. SIZE OF PROJECT REPORT :

The size of project report should not exceed 60 pages of typed matter reckoned

from the first page of Chapter 1 to the last page.

4. ARRANGEMENT OF CONTENTS OF PROJECT REPORT :

The sequence in which the project report material should be arranged and boundshould be as follows :

1. Title page

2. Bonafide Certificate

3. Abstract

4. Acknowledgement

5. Table of Contents

6. List of Tables

7. List of Figures

8.

List of Symbols, Abbreviations or Nomenclature (Optional)

9. Chapters

10. Appendices

11. References


12/28

3

The Tables and Figures shall be introduced in the appropriate places.

5. PAGE DIMENSIONS AND MARGIN :

The dimensions of the final bound copies of the project report should be 290mm x

205mm. Standard A4 size (297mm x 210mm) paper may be used for preparing

the copies.

The final five copies of the project report (at the time of submission) should havethe following page margins :

Top edge : 30 to 35 mm

Bottom edge : 25 to 30 mm

Left side : 35 to 40 mm

Right side : 20 to 25 mm

The project report should be prepared on good quality white paper preferably not

lower than 80 gms /Sq. Meter.

Tables and figures should conform to the margin specifications. Large size figures

should be photographically or otherwise reduced to the appropriate size beforeinsertion.

6. MANUSCRIPT PREPARATION :

The candidates shall supply a typed copy of the manuscript to the guide for the

purpose of approval. In the preparation of the manuscript, care should be taken toensure that all textual matter is typed to the extent possible in the same format as

may be required for the final project report.

Hence, some of the information required for the final typing of the project report

is included also in this section.

The headings of all items 2 to 11 listed section 4 should be typed in capital letters

without punctuation and centred 50mm below the top of the page. The text

should commence 4 spaces below this heading. The page numbering for all items

1 to 8 should be done using lower case Roman numerals and the pages thereaftershould be numbered using Arabic numerals.

6.1 Title page A specimen copy of the title page for M.E. /

M.Tech./M.B.A./ M.C.A. / M.Sc. project report are given in Appendix 1.

6.2 Bonafide Certificate Using double spacing for typing the Bonafide

Certificate should be in this format :


13/28

4

Certified that this project report titledis

the bonafide work of Mr./ Ms..who carried

out the research under my supervision. Certified further, that to the best ofmy knowledge the work reported herein does not form part of any other

project report or dissertation on the basis of which a degree or award was

conferred on an earlier occasion on this or any other candidate.

(Certificate to be countersigned by the HOD.)

6.3. AbstractAbstract should be an essay type of narrative not exceeding600 words, outlining the problem, the methodology used for tackling it

and a summary of the findings.

6.4. Acknowledgement It should be brief and should not exceed one pagewhen typed double spacing.

6.5. Table of contents The table of contents should list all materialfollowing it as well as any material which precedes it. The title page,

bonafide Certificate and acknowledgement will not find a place among the

items listed in the table of contents but the page numbers of which are in

lower case Roman letters. One and a half spacing should be adopted fortyping the matter under this head.

6.6. List of Tables The list should use exactly the same captions as theyappear above the tables in the text. One and a half spacing should be

adopted for typing the matter under this head.

6.7. List of FiguresThe list should use exactly the same captions as theyappear below the figures in the text. One and a half spacing should be

adopted for typing the matter under this head.

6.8. List of Symbols, Abbreviations and Nomanclature One and a half

spacing should be adopted for typing the matter under this head. Standard

symbols, abbreviations etc. should be used.

6.9. Chapters The chapters may be broadly divided into 3 parts (i)

Introductory chapter, (ii) Chapters developing the main theme of the

project report, (iii) Results, Discussion and Conclusion.

The main text will be divided into several chapters and each chapter may

be further divided into several divisions and sub-division.

Each chapter should be given an appropriate title.

Tables and figures in a chapter should be placed in the immediate

vicinity of the reference where they are cited.


14/28

5

Footnotes should be used sparingly. They should be typed single space

and placed directly underneath in the very same page which refers to

the material they annotate.

6.10. Appendices Appendices are provided to give supplementary

information, which if included in the main text may serve as a distractionand cloud the central theme under discussion.

Appendices should be numbered using Arabic numerals, e.g.

Appendix 1, Appendix 2, etc.

Appendices, Tables and References appearing in appendices should be

numbered and referred to at appropriate places just as in the case of

chapters.

6.11. List of ReferencesAny work of other researcher is used either directly

or indirectly the origin of the material thus referred to at appropriate placesin the project report should be indicated. A paper, a monograph or a book

may be designated by the name of the first author followed by the year of

publication, placed inside brackets at the appropriate places in the project

report should be indicated. A paper, a monograph or a book may bedesignated by the name of the first author followed by the year of

publication, placed inside brackets at the appropriate place of reference.

The citation may assume any one of the following forms.

Examples of citation

(i) An improved algorithm has been adopted in literature (Tsychiya

1980)

(ii) Jankins and Walts (1968) have dealt at length this principle.

(iii) The problems of mechanical manupulators has been studied by

Shin et al (1984) and certain limitations of the method used, hasbeen pointed out by Shin et al (1984 a).

The listed should be typed 4 space below the heading

REFERENCES in alphabetical order in single spacing left-justified. Thereference material should be listed in the alphabetical order of the first

author. The name of the author/authors should be immediately followed

by the year and other details. A typical illustrative list given below relatesto the citation examples quoted above.

REFERENCES

1. Ariponnammal S. and Natarajan S. (1994) Transport Phonomena

of Sm Se 1-x Asx Pramana Journal of Physics Vol. 42 No.5pp.421-425


15/28

6

2. Barnard R.W. and Kellogg C. (1980) Applications of Convolution

operators to Problems in univalent function theory. Michigan

Mach. J., Vol 27, pp 81-94

3. Jankins G.M. and Walts D.G. (1968), Spectral Analysis and its

Applications Holder Day, Sanfrancisco.

4. Shin K.G. and Mckay N.D. (1984) Open loop minimum time

control of mechanical manupulations and its applications, Proc.

Amer. Contr. Conf., San Diego, CA, pp. 1231-1236.

6.12. Tables and FiguresBy the word Table, is meant tabulated data in the

body of the project report as well as in the appendices. All other material

used in the body of the project report and appendices such as charts,graphs, maps, photographs and diagrams may be designated as figures.

A table or figure including caption should be accommodated withinthe prescribed margin limits and appear on the page following the page

where their first reference is made.

Tables and figures on half page or less in length may appear on the

same page along with the text. However, they should be separated

from the text both above and below by triple spacing.

All tables and figures should be prepared on the same paper or

material used for the preparation of the rest of the project report.

For preparing captions, numerals, symbols or characters in the case of

tables or figures, the Computer should be used.

Two or more small tables or figures may be grouped if necessary in a

single page.

Whenever possible, the entire photograph(s) may be reproduced on a

full sheet of photographic paper.

Photographs, if any, should be included in the colour xerox form only.

More than one photograph can be included in a page.

Samples of Fabric, Leather, etc., if absolutely necessary may be

attached evenly in a page and fixed/pasted suitably and should be

treated as figures.


16/28

7

7. TYPING INSTRUCTIONS

7.1 General

This section includes additional information for final typing of the project

report. Some information given earlier under Manuscript preparation

shall also be referred.

The impressions on the typed copies should be black in colour.

Uniformity in the font of letters in the same project report shall beobserved.

A sub-heading at the bottom of a page must have atleast two full lines

below it or else it should be carried over to the next page.

The last word of any page should not be split using a hyphen.

One and a half spacing should be used for typing the general text.

Single spacing should be used for typing:

(i) Long Tables

(ii) Long quotations

(iii) Foot notes(iv) Multiline captions

(v) References

All quotations exceeding one line should be typed in an indented space the indentation being 15mm from either margins.

Double spacing should be used for typing the Bonafide Certificate andAcknowledgement.

7.2. Chapters

The format for typing chapter headings, divisions headings and sub

division headings are explained through the following illustrativeexamples.

Chapter heading : CHAPTER 1

Division heading INTRODUCTION

Division heading : 1.1 OUTLINE OF PROJECT REPORT

Sub-division heading : 1.1.2. Literature review.


17/28

8

The word CHAPTER without punctuation should be centered 50mm down

from the top of the page. Two spaces below, the title of the chapter should

be typed centrally in capital letters. The text should commence 4 spacesbelow this title, the first letter of the text starting 20mm, inside from the

left hand margin.

The division and sub-division captions along with their numberings shouldbe left-justified. The typed material directly below division or sub-division

heading should commence 2 spaces below it and should be offset 20mm

from the left hand margin. Within a division or sub-division, paragraphsare permitted. Even paragraph should commence 3 spaces below the last

line of the preceding paragraph, the first letter in the paragraph being

offset from the left hand margin by 20mm.

8. NUMBERING INSTRUCTIONS

8.1. Page Numbering

All pages numbers (whether it be in Roman or Arabic numbers) should be

typed without punctuation on the upper right hand corner 20mm from top

with the last digit in line with the right hand margin. The preliminary

pages of the project report (such as Title page, Acknowledgement, Tableof Contents etc.) should be numbered in lower case Roman numerals. The

title page will be numbered as (i) but this should not be typed. The page

immediately following the title page shall be numbered (ii) and it shouldappear at the top right hand corner as already specified. Pages of main

text, starting with Chapter 1 should be consecutively numbered using

Arabic numerals.

8.2

Numbering of Chapters, Divisions and Sub-Divisions

The numbering of chapters, divisions and sub-divisions should be done,

using Arabic numerals only and further decimal notation should be used

for numbering the divisions and sub-divisions within a chapter. Forexample, sub-division 4 under division 3 belonging to chapter 2 should be

numbered as 2.3.4. The caption for the sub-division should immediately

follow the number assigned to it.

Every chapter beginning with the first chapter should be serially numbered

using Arabic numerals. Appendices included should also be numbered in

an identical manner starting with Appendix 1.

8.2. Numbering of Tables and Figures

Tables and Figures appearing anywhere in the project report should bear

appropriate numbers. The rule for assigning such numbers is illustrated

through an example. Thus if as figure in Chapter 3, happens to be thefourth then assign 3.4 to that figure. Identical rules apply for tables except


18/28

9

that the word Figures is replaced by the word Table. If figures (or tables)

appear in appendices then figure 3 in Appendix 2 will be designated as

Figure A 2.3. If a table to be continued into the next page this may bedone, but no line should be drawn underneath an unfinished table. The top

line of the table continued into the next page should, for example read

Table 2.1 (continued) placed centrally and underlined.

8.3. Numbering of Equations

Equations appearing in each Chapter or Appendix should be numbered

serially, the numbering commencing a fresh for each Chapter or

Appendix. Thus for example, an equation appearing in Chapter 2, if ithappens to be the eighth equation in that Chapter should be numbered

(2.8) thus:

C(s) G1G2----- = ----------------- (2.8)

R(s) 1 + G1 G2 H

While referring to this equation in the body of the project report it shouldbe referred to as Equation (2.8).

9. BINDING SPECIFICATIONS

Project report submitted for M.E. / M.Tech. / M.Sc./ M.C.A. / M.B.A.should be bound using flexible cover of thick white art paper. The spine

for the bound volume should be of black Calico of 20mm width. The

cover should be printed in black letters and the text for printing should be

identical to what has been prescribed for the title page.


19/28

Submi tted by

for the faculty of

INFORMATION AND COMMUNICATION ENGINEERING

in partial ful fi llment for the award of the degree of

MASTER OF ENGINEERING

in

COMPUTER SCIENCE AND ENGINEERING

KONGUNADU COLLEGE OF ENGINEERING AND

TECHNOLOGY, TRICHY 621 215

ANNA UNIVERSITY::CHENNAI 600 025

XXXXXXXX(62131XXXXX)

A PROJECT REPORTPHASE I

TITLE OF THE PROJECT

December 2014


20/28

ii

BONAFIDE CERTIFICATE

SIGNATURE SIGNATURE

Engineering, Engineering,

Kongunadu College of Engineering and Kongunadu College of Engineering and

Technology, Thottiam, Trichy Technology, Thottiam, Trichy.

INTERNAL EXAMINER EXTERNAL EXAMINER

Certified that this report titled Title of the project, forphase-I of the project, is a

bonafide work of XXXXXXXYYYY(62131XYXYXY),who carried out the work under my

supervision, for the partial fulfillment of the requirements for the award of the degree of

Master of Engineeringin ComputerScience and Engineering.

Mr.XYZM.E. Mr.C.SARAVANABHAVAN M.Tech.,(Ph.D)

SUPERVISOR, HEAD OF THE DEPARTMENT,

Assistant Professor, Associate Professor,

Department of Computer Science and Department of Computer Science and

Submitted to the Project Phase-IViva Voce Examination held on ______________________


21/28

iii

DECLARATION

Signature of the Student,

I certify that the declaration made above by the candidate is true.

Signature of the Supervisor,

I hereby declare that the work entitled Title of the Project

is submitted inpartialfulfillment ofthe requirement for theaward of the M.E.,degree

in Anna University, Chennai is a record of our own work carried out by us during

the academic year of 20142015 under the supervision and guidance of

Mr.XYZ M.E., Assistant Professor, Department of Computer Science and

Engineering, Kongunadu College of Engineering and Technology, Trichy. The extent and

source of information are derived from the existing literature and have been indicated

through the dissertation at the appropriate places. The matter embodied in this work

is original and has not been submitted for the award of any other degree or diploma,

either in this or any other University.

XXYYY(62131xyz)

Mr.xyz ,M.E.,Ph.D.

Assistant Professor,

Department of Computer Science

and Engineering.


22/28

iv

ACKNOWLEDEGMENT

I wish to express my sincere thanks to our beloved respectful and honourable chairman

Dr.PSK.R.PERIASWAMY for providing immense facilities in our institution.

I proudly render my thanks to our Principal Dr.R.ASOKAN, for the facilities and the

encouragement given by him to the progress and completion of our project.

I proudly render my immense gratitude to our Head of the Department of Computer

Science and Engineering Mr.C.SARAVANABHAVAN M.Tech.,(Ph.D). for his effective

leadership, encouragement and guidance in the project.

I highly indebted to provide my heart full thanks to my respectful supervisor

guidance throughout the project

I highly indebted to provide my heart full thank our respectful project coordinator

Mr.V.SARAVANAKUMAR M.E., for his supportive guidance throughout the project.

I wish to extend my sincere thanks to all teaching and non teaching staff of Computer

Science and Engineeering department for their valuable suggestions, cooperation and

encouragement on successful completion of this project.

I wish to acknowledge the help received from various departments and various

individuals during the preparation and editing stages of the manuscript.

Mr.XYZ, M.E., Ph.D for his valuable ideas constant encouragement andsupportive


23/28

v

ABSTRACT

Keywords:

Not more than 600 words


24/28

vi

TABLE OF CONTENT

CHAPTER NO TITLE PAGE NO

ABSTRACT v

LIST OF FIGURES viii

LIST OF ABBREVATIONS x

1 INTRODUCTION 1

1.1Literature Survey 1

1.2

Overview 5

1.3

VANET 6

1.3.1 Communications through Cellular Network 6

1.3.2 Vehicle To Roadside Infrastructure

Communications

7

1.3.3 Vehicle To Vehicle (AD HOC)

Communications

7

1.3.4 Characteristics of VANET 8

1.3.5 VANET Routing Challenges 8

2 SYSTEM DESCRIPTION 10

2.1 System Specification 10

2.2 Software Description 10

3 WORK DONE IN PHASE I 15

3.1 System Architecture 15

3.1.1 Adversary Model 19

3.1.2 Security Requirement 19

3.2 Trust Extended Authentication 20

3.3 Secure Communication 25

3.4 Key Revocation 26


25/28

vii

3.5 Key Updation 26

3.6 Data Flow Diagram 27

4 IMPLEMENTATION AND RESULTS 30

4.1 AES Algorithm 30

4.1.1 The AES Cipher 30

4.1.2 Inner Working of a Round 32

4.1.3 Substitute Bytes 32

4.1.4 Shift Row Transformation 34

4.1.5 Mix Column Transformation 35

4.2 SHA Algorithm 36

4.3 Results 39

4.3.1 Trust Extended communication for Varied

Transmission Range from 100m to 300 m

39

4.3.2 Trust Extended communication for Varied

Transmission Range from 5m to 15m

40

5 CONCLUSION AND FUTURE ENHACEMENT 45

SOURCE CODE 46

SCREEN SHOTS 47

PUBLICATION 48

REFERENCES 49


26/28

LIST OF TABLES

TABLE NO. TITLE PAGE NO.

2.1 Type of Defect and their population from theTILDA Database. 10

5.1 Classification accuracies for the TILDA Database 31

5.2 Canberra Distance between the query image andResults 33

5.3 CPU Times and Feature Vector Length for Gabor

Features Computed in MATLAB 33


27/28

LIST OF FIGURES

FIGURE NO. TITLE PAGE NO.

2.1 Architecture of the Defect Classification System 6

2.2 External Interface Diagram of the System 6

2.3 Image Database 10

3.1 Architecture for Image Defect Classification System 13

3.2 Architecture for Image Defect Retrieval System 13

3.3 Architecture for Video Defect Detection System 14

4.1 Detector masks for the Sobel Edge Detector 23

5.1 Query Image: Test12.bmp 29

5.2 Application window for Image Defect Classification

System with Input 30

5.3 Application window for Image Defect Classification

System with output 30

5.4 Query Image: T163.bmp 31

5.5 Application window for Image Defect Retrieval

System with Input 32

5.6 Retrieval Results of Image Defect Retrieval System 32

5.7 Application window for Video Defect Detection System 34

5.8 Input Video: Defect1.avi 34

5.9 Set of frames from Defect1.avi 35

5.10 Application window for the Video Defect Detection

System with output 36


28/28

LIST OF ABBREVIATIONS

AVI Audio Video Interlace

BMP Bitmap

CPU Central Processing Unit

GB Giga Bytes

GUI Graphical User Interface

LDA Linear Discriminant Analysis

ML Machine Learning

PCA Principal Component Analysis

RAM Read Only Memory

SPCA Shift invariant Principal Component Analysis

pg project format2014

Documents