REPORT STANDARD FORMAT

ABSTRACT
The Project Abstract shall include a statement of objectives, methods to be employed, and the
significance of the proposed activity. This information collection shall not be more than one page in length
and shall be written in the third person.
The information in the first PARAGRAPH
should state the main objective and rationale of your project,
should outline the methods you used to accomplish your objectives,
The information in the econd PARAGRAPH
it should list the project!s results or product "or projected or intended results or product, if project
is not yet complete#,
and it should draw conclusions about the implications of your project
Orderin in the Ac!no"ledement
$ Principal
% H&'
( )nternal Guide
* +,ternal Guide"if any#
- Parents ,friends..
#ist o$ Fiures
#ist o$ T%bles
Ch%pter &'le$t justi$ied( $ont si)e &*+
,NTROD-CT,ON'centered ( $ont si)e o$ ch%pter title &.+
&/& overview'section such %s &/& should be le$t justi$ied "ith $ont si)e &*( subsection such %s &/&/&
should be le$t justi$ied "ith $ont si)e &0+
'& t%b sp%ce %t beinnin o$ e%ch p%r%+A project overview is similar to an outline and should not
e,ceed one page. )n the project overview you must include many of the main ideas of the project. /ou do
not have to go into details since this is an overview and hence the main ideas should be included'$ont
si)e o$ inner te1t &2+.
&/2 Problem statement
0hat the problem is that you1re trying to find the answer to , why it1s a problem" should not e,ceed
one paragraph#.
&/3 The solution
how your project will help answer it. "should not e,ceed one paragraph#.
&/0 +,isting ystem
+,plain briefly about the e,isting system the algorithm or techni2ue it is using to solve the problem
and its drawbac3 "should not e,ceed % paragraphs#
&/4 Proposed ystem
+,plain briefly about the new algorithm or techni2ue you will use to solve the problem and its
advantage over +,isting system" should not e,ceed % paragraphs#
&/* &rgani4ation of project report
The report is organi4ed in the following manner
The chapter 1 gives the...
The chapter 2 specifies....
Ch%pter 2
#,TERAT-RE S-R5E6
%.$ urvey Papers
5or your literature survey review information $rom v%rious sources 7boo!s( journ%ls( con$erence
proceedins( "eb sites( product liter%ture( etc/8, and formulate a report about the topic. The goal is to
show that you have read the information about the system from various sources and understand the the
problems6issues of the system.
/our goal at this point is to 7present an overview of what your source offers its topic, problem.
)nclude the following content8
a# 0hat the topic is
b# 0hat problems and issues it addresses
c# 0hat are the different technical approaches "e,plain in detail in conte,t of +,isting ystem and proposed
ystem#, and a comparison of their specific benefits and issues.
%.% urvey 5indings
&utline the main findings of the documents you reviewed, &verall impression and assessment of the
system
Note: Survey info should be derived from books, journals, conference proceedings, web sites, product
literature, etc. Do not discuss about technologies you are using
Ch%pter 3
SOFT9ARE RE:-,REMENT SPEC,F,CAT,ONS
(.$ 5unctional Re2uirements
)n software engineering, a $unction%l re;uirement defines a function of a software system or its component.
A function is described as a set of inputs, the behavior, and outputs "see also software#. 5unctional re2uirements may
be calculations, technical details, data manipulation and processing and other specific functionality that define what a
system is supposed to accomplish. Function%l re;uirement should be e1pl%ined usin -M# di%r%ms such %s use
c%se( se;uence di%r%ms etc//
(.% 9onfunctional Re2uirements
non:functional re2uirements "also 3nown as quality requirements#, which impose constraints on the design or
implementation "such as performance re2uirements, security, or reliability#
Note: 3. and 3.! are compulsory.Depending on its applicability to your project you can also can e"plain
Architectural Requirements, Structural Requirements, and Behavioral Requirements, Domain
Requirements , Use requirements !!which can "e #!# , #!$ !
(.- ystem Re2uirements
/ou need to e,plain the Hardware and software re2uirements of your project.
Ch%pter 0
S6STEM ANA#6S,S AND DES,<N
*.$ ystem Analysis
Analysis done for planning the design should be e,plained
*.% High ;evel 'esign
0/2/& S=stem Architecture
ub systems , modules and their interactions should be e,plained
hould use conte,t diagram or structure diagram ,use case diagram,<omponent diagram "any one is
compulsory ,can use more than one diagrams to show the high level design #
0/2/2 DB Desin
=se data flow diagrams to e,plain the flow of data in sub systems and modules
0/2/3 DB t%ble structure
hould specify the tables with their various fields
*.( ;ow ;evel 'esign
'etailed description of each module should be given.hould use class diagram ,se2uence diagram ,Activity
diagram ,deployment diagram diagram "any one is compulsory ,can use more than one diagrams to show the
low level design #
*.* =ser )nterface 'esign
'esign of )nterfaces provided for the user to interact with the system should be specified "9o snapshots#
Ch%pter 4
,MP#EMENTAT,ON
-.$ <ontrol 5low
should be e,plained using flow charts
-.% Pseudo code or Algorithm
&f all the modules should be written and each pseudo code or algorithm should be e,plained
briefly.
Ch%pter *
TEST,N<
>.$ 'esign of Test <ases
'ifferent Testing approaches used 5or testing the project should be e,plained. Testing approaches should be
e,plained in the conte,t of the project.
>.% ample Test <ases
+,pected fields in the table and an e,ample has been given about how to write the test cases
T+T
<A+
)'
T+T
<A+
9A?+
T+T <A+
'+<R)PT)&
9
T+T T+P T+T
TAT=

P65
T+P )6P
G)@+9
+AP+<T+'
&6P
A<T=A;
&6P
;oginB$
"+,ample#
@alidate
=ser
logged in
as admin
To verify that
the user name
and password
is correct.
+nter user
name and
password
of admin
=n8admin
Pw8admin
;og in as
admin
;ogged in
as admin
P
Ch%pter >
SNAPS?OTS AND RES-#T D,SC-SS,ON
)mportant screenshots of the project should be shown, along with the e,planation of each screenshot "only one
snapshot in a page aligned at center of page and a brief e,planation below#
CONC#-S,ON AND F-T-RE 9OR@
<onclusion and future wor3 should not be a chapter.
5irst paragraph should conclude your project
Conclusion should brief ( birds eye view ) of what made you undertake the project , what has been
achieved. Give a brief summary of the procedures adapted .
Second paragraph should specify future work
!t should state the openings and possibilities it offers for further projects based on this
REFERENCES
APPEND,A
Which includes supplementary information which may be of interest or use to the reader of the report