Project Report Format
Project Report Format
Pls submit One hard copy in Spiral Binding of Project Report without error,
Signed by all group members and checked and approved by your respective Supervisor
and submit this hard copy to respective Project Coordinator.
Text :
The text should be typed in 12 font size Times New Roman style in 1.5 spacing on one side of
A4 size page (Executive Bond) only. The Captions for figures should be typed at the its bottom
for example 4th figure in Chapter 3 should be captioned as Figure. 3.4 Title of Figure. The
captions for tables should be typed at its top for example 7th table in Chapter 3 should be
captioned as Table. 3.7 Title of Table. The text format in the chapter will be
Main heading Size : 16 (Bold)
Sub heading 1.1: 14 (Bold)
Subtitle .1.1.1: 12 (Bold)
Text(script): 12
Equations appearing in each Chapter should be numbered serially, the numbering commencing
fresh for each Chapter or Appendix. For example, an equation appearing in Chapter 2, if it
happens to be the eighth equation in that Chapter 2 should be numbered (2.8). While referring
this equation in the body of the project it should be referred to as Equation (2.8).
List of References / Bibliography
Any work of other researchers, if used either directly or indirectly, the origin of the material thus
referred to at appropriate places in the report should be indicated. The citation may assume any
of the standard form (preferably ASCE, ASCE, IEEE, or other international Journal Publishers
such as Elsevier, Kluwer, Pergamon etc.). For more details the students may contact their
respective guides.
Internet Documents
[4] R. Hayes, G. Pisano, and S. Wheelwright, Operations, Strategy, and Technical Knowledge.
Hoboken, NJ: Wiley, 2007
Page Dimensions and Margin
The dimensions of the Spiral binding report should be Standard A4 size (297mm x 210mm)
paper, may be used for preparing the copies. The report should have the following page margins:
Top and Bottom edge : 25 mm (1 inch) Left and right side : 25 mm (1 inch)
Page Numbering
All pages numbers should be typed at the center of page bottom. The preliminary pages of the
Project (such as Title page, Table of Contents, List of tables and figures, Notations,
Abbreviations etc.) should be numbered in lower case Roman numerals.
Page Type:
The project report should print on white paper with Spiral binding.
Size of Report
The size of Project report should not exceed 80 Pages of typed matter reckoned from the First
page of Chapter 1 to the last page.
Sequence of Report:
1. Cover Page
2. Progress Report form
3. Synopsis(2-3 Pages)
4. Table of Contents along with page numbers
5. List of Tables
6. List of Figures
7. List of Symbols, Abbreviations
8. Chapter 1: Introduction
9. Chapter 2: Hardware and Software Requirement
10. Chapter 3: SDLC Methodologies
11.Chapter 4: Software Requirement Specification and Analysis
12. Chapter 5: Risk Assessment
13.Chapter 6: DFD /ER Diagram/ wireframe/Application Architecture
14.Chapter 7: Project Modules Design/ Database tables/ Software Features
15.Chapter 8: Project Snapshots
16. References
Chapter 1: Introduction : This chapter cover the Introduction of the Project,
objective, motivation, Problem definition etc. chapter 2 of PPR-1(back ground
and related work) will be now sub chapter of Introduction. ( minimum 8-12
Pages)
Chapter 2: Hardware and Software Requirement : Write down in brief about
the Hardware and Software requirements of your project. (Minimum 1-2 Pages).
Chapter 3: SDLC Methodologies: Students should write the various popular
SDLC methodology in brief and in details explain the methodology used in project
and how it works in your project. (Minimum 3-4 Pages).
Chapter 4: Software Requirement Specification and Analysis: Write Down the
complete specification and description of requirements of software that needs to be
fulfilled for successful development of software system. These requirements can be
functional, interface requirements, performance requirement, design constraint, as
well as non-functional as Security, Portability, Reliability, Reusability, Application
compatibility, Data integrity, Scalability capacity, etc. depending upon type of
requirement.
Chapter 5: Risk Assessment: Write down about risk ought to be rated to the
chance of a risk coming back and the consequence of the issues related to that risk.
Risks plans should be created to contain the foremost damaging and also the
possible risks. Also write setup of risk containment like avoid risk, transfer risk,
risk reduction.
2024-25
Under the Guidance of: Submitted By:
6. SUPERVISOR:
(Name of Supervisor)
…………………………………………………………………………………
……………………………………………………………………………………
…………………………………………………………………………………
Note: Role can be Team Leader, Requirement Analyzer, Designer, Coder, Tester, Report
Preparation, Manual Preparation etc. Choose selective role in your Project as per team
member contribution.
SYNOPSIS
TABLE OF CONTENTS
SYNOPSIS iii
LIST OF TABLES ix
LIST OF FIGURES x
1. INTRODUCTION 1
INTRODUCTION
Since the rise of the Internet, one of the most important factors of information
technology and communication has been the security of information. Cryptography was created
as a technique for securing the secrecy of communication and many different methods have been
developed to encrypt and decrypt data in order to keep the message secret. Unfortunately it is
sometimes not enough to keep the contents of a message secret, it may also be necessary to keep
the existence of the message secret. The technique used to implement this, is called
Steganography.
Steganography is the art and science of invisible communication. This is
accomplished through hiding information in other information, thus hiding the existence of the
communicated information. The word steganography is derived from the Greek words “stegos”
meaning “cover” and “grafia” meaning “writing” defining it as “covered writing”. In image
steganography the information is hidden exclusively in images. The idea and practice of hiding
information has a long history. In Histories the Greek historian Herodotus writes of a nobleman,
Histaeus, who needed to communicate with his son-in-law in Greece.
well-known channels greatly reduces the risk of information being leaked in transit. Hiding
information in a photograph of the company picnic is less suspicious than communicating an
encrypted file.