Guidelines for preparation of PROJECT REPORT

All BE (Computer) students are required to meet their guides and submit the project report
draft in the prescribed format on or before 11/04/2011 as well you have to show 100%
implementation, Project demo .After submitting the report only your journals will be
Certified. Those who are not reporting to guide are not allowed to appear for Examination.
All groups should be present on Monday 11/04/2011 at 8.00 AM. in class room No.12.

The contents of the report should be as follows:

1. Front page-Outer cover-Hardbound-black background, title & name, in golden ink.

Print academic year 2008-2009.(as shown in format)
2. First page should be well designed and should have the contents as per the format.
3. Certificate to be signed by guide & HOD.(as shown in format)
4. Acknowledgement.(as shown in format)
5. Abstract
6. Contents(refer sample format)
7. List of figures (if applicable)
8. List of tables (if applicable)

Note:
• The page numbers should begin from chapter 1.The pages prior to this can be
represented in small Romans in the contents but should not be printed on the page.
• The Header (consisting of name of Project Right justified) and Footer (consisting of
Name of Department, page no and College) should be applied from chapter one.
• The font of the text of the report should be Times New Roman-12 justified.
• The font for chapter name has to be 16 bold capitals.
• The headings font should be 14 bold capitals and the sub headings can be of 12 bold.
• All the diagrams should be numbered with respect to the chapter no.e.g. Fig.1.1.
 GROUP NO:
A PROJECT REPORT
ON

…………(Name of the project)………..

Towards the partial fulfillment of B.E. (Computer Engineering) degree of

University of Pune during the academic year (2010-2011).

SUBMITTED BY

[Name, Exam seat No. Roll No.]

[Name, Exam seat No. Roll No.]

[Name, Exam seat No. Roll No.]

[Name, Exam seat No. Roll No.]

UNDER THE GUIDANCE OF

PROF.____________

DEPARTMENT OF COMPUTER ENGINEERING

D. Y. PATIL COLLEGE OF ENGINEERING
SECTOR NO.-29, AKURDI, PUNE – 411 044, INDIA

UNIVERSITY OF PUNE
(2010-2011)
 D. Y. PATIL COLLEGE OF ENGINEERING
AKURDI, PUNE – 411 044.

CERTIFICATE
This is to certify that Ms. _____________________has satisfactorily
completed the project work entitled

“(Name of the project)”

in partial fulfillment of “Bachelor Engineering Degree in Computer as
prescribed by the University of Pune. in the academic year 2010-2011.

(Name of the Guide) (Prof. A. J Patankar)

Guide H.O.D. Computer Engineering (UG) Examiner

Place: Pune
Date:
 ACKNOWLEDGEMENT

With immense pleasure, we present the project report as part of the curriculum of the
B.E. Computer Engineering .We wish to thank all the people who gave us an unending
support right from when the idea was conceived.
We express our sincere and profound thanks to Pof.________________,our project
Guide, who always stood by us as the helping and guiding support and all those who have
directly or indirectly guided and helped us in the development of the project.

At last we thank LedTech Systems who sponsored this project and had immense faith
in us.(if sponsored)

Name Exam Seat No. Signature

 Project Report Format for Semester-II

1. Title Page
2. Certificate
3. Acknowledgement
4. Abstract
5. Format for Chapter Organization
Sr.No. Chapters Page No.
01
Introduction

1.1 Overview

1.2 Brief Description

1.3 Problem Definition

1.4 Applying software engineering

approach
02
Literature Survey (additional than sem I)
03
Software Requirements Specification
3. Introduction
1
3.1. Purpose
1
3.1. Intended audience and reading suggestion
2
3.1. Project Scope
3
3.1. Design and Implementation Constraints
4
3.1. Assumptions and Dependencies
5
3.
2 System Features
3.2. System Feature 1(Functional Requirement)
1
3.2. System Feature2 (Functional Requirement)
2
……
……
3.
3 External Interface Requirements
3.3. User Interfaces
1
 3.3. Hardware Interfaces
2
3.3. Software Interfaces
3
3.3. Communication Interfaces
4
3.
4 Nonfunctional Requirements
3.4. Performance Requirements
1
3.4. Safety Requirements
2
3.4. Security Requirements
3
3.4. Software Quality Attributes
4
3. Other Requirements (If Applicable)
5
3.5. Database Requirements
1
3.5. Internalization Requirements
2
3.5. Legal Requirements
3
3.5. Reuse Objectives for the Project
4
3.
6 Analysis Models
3.6. Data Flow Diagrams
1
3.6. Class Diagrams
2
3.6. State-transition Diagrams or Entity Relationship Diagrams
3
3.
7 System Implementation Plan
04
System Design
4. System Architecture
1
4. UML Diagrams
2
05
Technical Specification
5.1 Technology details used in the project
5.2 References to Technology
06 Project estimate, Schedule and team structure
07 Software implementation
7.1 Introduction
7.2 databases
7.3 important module and algorithms
7.4 Business logic and Architecture
08 Software testing
8.1 Introduction
8.2 Test cases
8.3 snap shots of the test cases and Test plans
09 Results (Snap shots of the results)
10 Deployment and Maintenance
10.1 Installation and un-installation
10.2 user help
11 Conclusion and future scope
12 References

Appendix A: Glossary [Define terms,

acronyms, and abbreviations used in
the FRD]

Appendix B: Glossary [Define terms,

acronyms, and abbreviations used in
the FRD]