PROJECT REPORT GUIDELINES

First, show the soft copy of the final report to guide and get approval.
After getting the suggestions and approval from guide, you can print the fair report.
One fair report is to be submitted per individual and in addition to that, one report per batch should
be submitted as reference copy in the library.
The final fair report is to be submitted before the guide.
Report may have pages printed on A4 size paper.
Binding Hard binding with golden letters printed in cover page. Cover page should be black in colour.
Cover page should be printed with the matter in the specified format.
The templates for cover page format, front page format and certificate format are attached in the
mail.
Minimum number of pages required for report (from Introduction to References) is 30.
Name all the figures with Figure No. and name (like Figure 2: System Architecture)
Body font: Times New Roman
Body font size: 12
Body line spacing: 1.5 lines
Leave one line before the between paragraphs.
Use different sized fonts for headings, sub-headings, sub-sub-headings etc
You can use color pages as and when necessary.
Use the hierarchical IEEE format for numbering sections and sub-setions.
Arrangement of contents is as shown below.

CS 16L2 MINIPROJECT

FORMAT OF FINAL REPORT

The following is the order of placing various pages inside the report.

Page No

BLANK PAGE i

FRONT PAGE iii

CERTIFICATE FROM COLLEGE v

CERTIFICATE FROM COMPANY (IF REQUIRED) vii

ACKNOWLEDGEMENT ix

ABSTRACT xi

TABLE OF CONTENTS xiii

LIST OF FIGURES xv

LIST OF ABBREVIATIONS (eg RFID, NFC, NAT, WAP,ID3,GPS,AES,RSA etc) xvii

1. Introduction 1
2. Problem Definition/ Objective
State the problem that is to be solved/objective to achieve. 2
3. Software Requirement Specification (SRS) 3
Specify the requirements as needed by the client. It can include Functional requirements,
performance requirements, behavioral requirements etc. Follow the IEEE structure of an SRS.
4. System Study/ Review of Literature
4.1 Existing System or a survey of literatures available, indicating the state of the art.
4.2 Organization Chart/Hierarchy Diagram, if necessary
4.3 ER Diagram
4.4 Proposed System (include the overall system architecture of the proposed system)
4.5 Feasibility Study
You can use any tool used in the System Analysis and Design in this section.
5. System Design
Identify the modules and processes coming under the system.
Draw a structure chart of different modules.
Identify the data structures/tables to be used in the system
Construct DFDs in as many levels as required
6. Use Case Design
Draw the UML diagrams for usecases identified in the system.
7. Detailed Design
Specify the internal logic of modules/processes using Algorithms, pseudo-codes, Flowchart,
Structured English, or any other tool.
Any other type of UML diagram to describe the system may be put in this section.
You are advised to use all types of UML diagrams for your project. It will be an added
advantage at the time of evaluation if you do so.

8. Database Design
Determine the tables, attributes and their data types.
9. Input /Output Design
Specify the input methods(specify how input is given to system, ie, by keyboard and forms, by
code/card readers, by mobile devices etc)
Specify the outputs of the system.( ie , if reports are outputs specify their format)
10. System Implementation
 9.1 System Requirements
(Specify the hardware and software requirements that are needed to run the system. (Mention
both the client side and server side requirements, if applicable. Additional special hardware
requirements or mobile device requirements are to be mentioned.)
9.2 Implementation Scenario ( about clinet and server configurations, network setup required.
UML Deployment diagram may be used)
9.3 Developing Environment. (Specify both hardware and software. The tools used for developing
the system. eg: Wndows 7 64bit/Ubuntu 12.04 32 bit, Netbeans 7.1 IDE/Eclipse/ MS Visual
Studio, MS SQL Server / MySQL/Oracle)
9.4 Familiarization with the tools/techniques/APIs used in implementation. Include only the
relevant items from below.
(eg: About ASP.NET, .NET Framework, SQL Server, My SQL
About Java Technologies, J2EE,
About J2ME, Bluetooth communication, AT Commands
About data mining techniques
About statistical measures of performance used in the evaluation
About cryptography and encryption.
About images, audio, language processing
About UNIX configuration files
About Web/Application Servers
About Android and Android programming
About Protocols and protocol stacks etc., whichever is /are applicable. )
10 Source Code of important sections may be included......
11 Results and findings
11.1 Experimental setup.
11.2 Output Screenshots.
11.3 Any type of Chart, Table or Comparison of results obtained.
11.4 Performance evaluation if required.
11.5 Discussion on the findings.
11.6 Limitations
11.7 Future Scope
12 Conclusion
13 References