You are on page 1of 3

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

or any other tool. Database Design Determine the tables.4 Proposed System (include the overall system architecture of the proposed system) 4. System Design Identify the modules and processes coming under the system. Follow the IEEE structure of an SRS. by mobile devices etc) Specify the outputs of the system. if reports are outputs specify their format) 10.GPS.RSA etc) xvii 1. 4. 8.3 ER Diagram 4.1 Existing System or a survey of literatures available. It will be an added advantage at the time of evaluation if you do so. behavioral requirements etc.AES. 2 3. NAT. 7. Detailed Design Specify the internal logic of modules/processes using Algorithms. performance requirements. by keyboard and forms. NFC. Flowchart.( ie . Input /Output Design Specify the input methods(specify how input is given to system. by code/card readers. Any other type of UML diagram to describe the system may be put in this section. WAP. Structured English. attributes and their data types. Introduction 1 2.ID3. Problem Definition/ Objective State the problem that is to be solved/objective to achieve. 5. 4. System Implementation .5 Feasibility Study You can use any tool used in the System Analysis and Design in this section. Software Requirement Specification (SRS) 3 Specify the requirements as needed by the client.2 Organization Chart/Hierarchy Diagram. ie. 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. You are advised to use all types of UML diagrams for your project. pseudo-codes. indicating the state of the art. 9.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. It can include Functional requirements. if necessary 4. Use Case Design Draw the UML diagrams for usecases identified in the system. System Study/ Review of Literature 4.

) 10 Source Code of important sections may be included. network setup required.04 32 bit.6 Limitations 11. About J2ME. Additional special hardware requirements or mobile device requirements are to be mentioned. UML Deployment diagram may be used) 9. The tools used for developing the system. MS SQL Server / MySQL/Oracle) 9. AT Commands About data mining techniques About statistical measures of performance used in the evaluation About cryptography and encryption. 9.3 Any type of Chart.5 Discussion on the findings. My SQL About Java Technologies. 11 Results and findings 11.1 Experimental setup.7 Future Scope 12 Conclusion 13 References . . 11.3 Developing Environment.. if applicable..4 Familiarization with the tools/techniques/APIs used in implementation.2 Implementation Scenario ( about clinet and server configurations. Netbeans 7. (Specify both hardware and software. 11. Include only the relevant items from below. 11. About images. (Mention both the client side and server side requirements.2 Output Screenshots. 11.1 System Requirements (Specify the hardware and software requirements that are needed to run the system. whichever is /are applicable.NET Framework... Bluetooth communication.1 IDE/Eclipse/ MS Visual Studio.4 Performance evaluation if required. language processing About UNIX configuration files About Web/Application Servers About Android and Android programming About Protocols and protocol stacks etc..NET.) 9. audio. (eg: About ASP. J2EE. 11.. SQL Server. Table or Comparison of results obtained. eg: Wndows 7 64bit/Ubuntu 12.