ReportTitle

A PROJECT REPORT

Submitted by

Student
Reg. No. nnMCAnnnn

in partial fulfillment for the award of the degree of

Master of Computer Applications

School of Computing Science and Engineering

VIT University
Vandalur - Kelambakkam Road, Chennai - 600 127

May - 2015
 School of Computing Science and Engineering

DECLARATION

I hereby declare that the project entitled ReportTitle submitted by me to the

School of Computing Science and Engineering, VIT Chennai, 600 127 in partial
fulfillment of the requirements of the award of the degree of Master of Computer
Applications is a bona-fide record of the work carried out by me under the super-
vision of Guide. I further declare that the work reported in this project, has not
been submitted and will not be submitted, either in part or in full, for the award of
any other degree or diploma of this institute or of any other institute or University.

Place: Chennai Signature of Candidate

Date: (Student)
 School of Computing Science and Engineering

CERTIFICATE

This is to certify that the report entitled ReportTitle is prepared and submit-
ted by Student (Reg. No. nnMCAnnnn) to VIT Chennai, in partial fulfullment
of the requirement for the award of the degree of Master of Computer Appli-
cations is a bona-fide record carried out under my guidance. The project fulfills
the requirements as per the regulations of this University and in my opinion meets
the necessary standards for submission. The contents of this report have not been
submitted and will not be submitted either in part or in full, for the award of any
other degree or diploma and the same is certified.

Guide/Supervisor Program Chair

Name: Guide Name: Program Manager

Date: Date:

Examiner Examiner

Name: Name:
Date: Date:

(Seal of SCSE)
ReportTitle iv

Acknowledgement

Give your acknowledgement in the following hierarchy: Guide Program Chair

Dean and Others.

Student
Reg. No. nnMCAnnnn

School of Computing Science and Engineering, VIT University, Chennai

ReportTitle v

Abstract

Abstract to your work.

School of Computing Science and Engineering, VIT University, Chennai

ReportTitle vi

Contents

Declaration i

Certificate i

Acknowledgement iv

Abstract v

1 Introduction 1

2 Overview / Literature Review 2

3 System Design 3

4 Implementation of System/ Methodology 4

5 Results and Discussions 5

6 Conclusion and Future Work 6

School of Computing Science and Engineering, VIT University, Chennai

ReportTitle vii

List of Tables

School of Computing Science and Engineering, VIT University, Chennai

ReportTitle viii

List of Figures

School of Computing Science and Engineering, VIT University, Chennai

ReportTitle 1

Chapter 1

Introduction

The introduction is a shorter version of the rest of the report, and in many cases
the rest of the report can also have the same flow that summarizes the major con-
tributions of the project. The chapter should provide a critical and concise outline
of the subject to be covered by the dissertation and indicate how this study will
contribute to the subject. This chapter should include the descriptions such as:
(not necessarily in that order, but what is given below is a logical order).
• Background [The setting of the scene of the problem].
• Statement [Exact problem you are trying to solve].
• Motivation [Importance of the problem].
• Post/Related work [Existing methods including pros and cons of the meth-
ods should be cited wherever possible].
• Challenges [Difficulty in the problem solving].
• Essence of your approach [Your method of problem solving].
• Statement of assumptions [The conditions under which your solution is ap-
plicable].
• Organization of the report.
• Aim(s) and Objective(s)
• Avoid routine background e.g. the C programming language.
• Dont cite endless sources that are irrelevant or that you havent read.

School of Computing Science and Engineering, VIT University, Chennai

ReportTitle 2

Chapter 2

Overview / Literature Review

This chapter should include the brief description of the whole-proposed software
system that is to be developed, system preliminary design, system planning and
the details of the hardware & software used. System analysis & design vis--vis
user requirements (Preliminary design) should also be represented as a block di-
agram. System planning is represented as either as PERT chart or as Gantt chart.
A thorough review of the literature with respect to the chosen field should be pro-
jected. Should include earlier and current reports along with author citation and
year. In other words it should be a collection and a record of past land recent
work. Summarize major contributions of significant studies and articles related
to your field under review, maintaining the focus established in the introduction.
Evaluate current state of art. Point out major gaps, inconsistencies in theory and
findings. Conclude by providing some insight into the relationship between the
central topic of the literature review and the areas / issues pertinent to future study.

School of Computing Science and Engineering, VIT University, Chennai

ReportTitle 3

Chapter 3

System Design

This chapter should describe the engineering specifications and targets critically
evaluating the existing benchmarks and specifically identifying the gaps which
the project is intended to fill; It should show how the concepts evolved and were
evaluated also should describe and justify the formation of the final product which
may include possibly a number of subsections such as:

• Details of the development. System architecture indicating various modules

/ components and their interaction.

• Feasibility assessment report.

• Entity relationship diagram / analysis / DFD / State Transition Diagram.

If you adopt an object-oriented method, you will include the following in this
chapter:

• Sequence diagrams for each module and entire system.

• Class diagrams or any other UML diagram for each module and entire sys-
tem.

School of Computing Science and Engineering, VIT University, Chennai

ReportTitle 4

Chapter 4

Implementation of System/
Methodology

This chapter should reflect development of the project such as: implementation,
experimentation, optimization, evaluation etc. and unit integration testing should
be discussed in detail. The unit test cases and system test cases should describe the
input, expected output and output obtained. It can also include the details of the
tools used for implementation, justification for the selected tool and the detailed
description of implemented modules. Screen shots, Pseudocode etc. In case of
simulation, modeling, programming techniques, programming steps, flow-charts,
simulation results, verification of the approach followed and the like depending
on the nature of the project. The materials required, techniques followed, sam-
ple preparations, research design and methods should be clearly mentioned. The
experimental procedure should be clearly defined.

School of Computing Science and Engineering, VIT University, Chennai

ReportTitle 5

Chapter 5

Results and Discussions

This is part of the set of technical sections, and is usually a separate section for
experimental/design papers. This chapter should include:

• Performance metrics.

• Parameters under study

• Comparison of cases/ studies with respect to existing and proposed work /

algorithm/ designcomparison/ with the published data and deviations / im-
provements if any as expected in the aims and objectives

• Expected and obtained results- Analysis of the results- statistical analysis,

plots, simulated results, synthesis of process, interpretation of the results

• Detailed results for each logical component of the project with an accom-
panying discussion section [Can include screen shots, graphs etc.].

• The results can be tabulated, graphically presented and photographs to be

displayed if any.

• Discuss the results which should include an interpretation of the results and
their relationship to the aims and objectives.

School of Computing Science and Engineering, VIT University, Chennai

ReportTitle 6

Chapter 6

Conclusion and Future Work

This chapter should summarize the key aspects of your project (failures as well
as successes) and should state the conclusions you have been able to draw. Out-
line what you would do if given more time (future work). Try to pinpoint any
insights your project uncovered that might not have been obvious at the outset.
Discuss the success of the approach you adopted and the academic objectives you
achieved. Avoid meaningless conclusions, [e.g. NOT “ I learnt a lot about C++
programming ”]. Be realistic about potential future work. Avoid the dreaded:
“All the objectives have been met and the project has been a complete success”.
You have to crisply state the main take-away points from your work. Describe
how your project is performed against planned outputs and performance targets.
Identify the benefits from the project. Be careful to distinguish what you have
done from what was there already. It is also a good idea to point out how much
more is waiting to be done in relation to a specific problem, or give suggestions
for improvement or extensions to what you have done. Future scope of the work
for improvement may also be included

School of Computing Science and Engineering, VIT University, Chennai

ReportTitle 7

Appendices

Appendices are provided to give supplementary information, which is not in-

cluded in the main text may serve as a separate part contributing to main theme.

School of Computing Science and Engineering, VIT University, Chennai

ReportTitle 8

Bibliography

[1] R. M. Star. Foo Bar Baz. MIT Press, Cambridge, MA, 1989.

School of Computing Science and Engineering, VIT University, Chennai