0% found this document useful (0 votes)
6 views9 pages

Project Report Writing Guidelines

The document provides detailed guidelines for writing a project report, including formatting specifications such as font size, margins, and structure of chapters. It emphasizes uniformity in headings, proper referencing, and the inclusion of specific sections like abstract and synopsis. Additionally, it outlines the sequence of chapters and requirements for figures and tables, ensuring clarity and consistency throughout the report.
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
6 views9 pages

Project Report Writing Guidelines

The document provides detailed guidelines for writing a project report, including formatting specifications such as font size, margins, and structure of chapters. It emphasizes uniformity in headings, proper referencing, and the inclusion of specific sections like abstract and synopsis. Additionally, it outlines the sequence of chapters and requirements for figures and tables, ensuring clarity and consistency throughout the report.
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

‭Guidelines for Project Report Writing‬

‭Follow these guidelines strictly while writing Project Report:‬


‭1. Font size‬
‭➢ Chapter heading size : 16 (Bold) Uppercase‬
‭➢ Sub Heading e.g. 1.1 : 14 (Bold) Uppercase‬
‭➢ Subtitles e.g. 1.1.1 : 12 (Bold) titlecase‬
‭➢ Subtitles e.g. [Link] : 12 (Bold) titlecase‬
‭➢ Text (script) : 12‬
‭2. Font : Times New Roman‬ ‭Line Spacing : 1‬‭1/2‬
‭3. Margin:‬

‭1.‬ ‭Right margin - 2 cm from edge of paper.‬


‭2.‬ ‭Left margin - 3 1/2 cm from edge of paper.‬
‭3.‬ ‭Top margin - 3 1/2 cm from edge of paper.‬
‭4.‬ ‭Bottom margin - 2 cm from edge of paper.‬
‭4. There should be uniformity in writing headings and sub-headings in all chapters.‬
‭5. Avoid‬‭Underlines‬‭and colon (:) .‬
‭6. To indicate a figure, write below the figure and the format should be Fig. 1.5.‬
‭7. To indicate a Table, write above the Table and the format should be Table. 1.5.‬
‭8. All the figure caption and table caption should be 12 size, bold and title case.‬
‭9.‬ ‭All‬ ‭the‬ ‭figure‬ ‭and‬ ‭table‬ ‭should‬ ‭be‬ ‭mentioned/referred/explained‬ ‭in‬ ‭the‬ ‭adjoining‬
‭paragraphs.‬
‭10.‬ ‭Always‬ ‭number‬ ‭the‬ ‭equation,‬ ‭Tables‬ ‭and‬ ‭figures‬ ‭chapter‬ ‭wise,‬ ‭for‬ ‭e.g.‬ ‭4th‬ ‭figure‬ ‭in‬
‭chapter 5 will bear the number Fig. 5.4.‬
‭11. Never write report in first person i.e. “I will do this” instead of the author...........‬
‭12.‬ ‭In‬ ‭references‬‭and‬‭bibliography,‬‭the‬‭mention‬‭of‬‭paper‬‭should‬‭be‬‭Fanghua‬‭Ye,‬‭Jiahao‬‭Liu,‬
‭Chuan‬‭Chen,‬‭Guohui‬‭Ling,‬‭Zibin‬‭Zheng,‬‭and‬‭Yuren‬‭Zhou.‬‭Identifying‬‭influential‬‭individuals‬
‭on‬‭large-scale‬‭social‬‭networks:‬‭A‬‭community‬‭based‬‭approach.‬‭IEEE‬‭Access,‬‭6:47240–47257,‬
‭2018.‬
‭13.‬ ‭The‬ ‭references‬ ‭should‬ ‭be‬ ‭placed‬ ‭in‬ ‭the‬ ‭chapters‬ ‭in‬ ‭the‬ ‭forms‬ ‭as‬ ‭[1],‬ ‭in‬ ‭the‬ ‭order‬ ‭of‬
‭occurrence.‬
‭14. There should be uniformity in writing headings of chapters for e.g.‬

‭Department of Computer Science and Engineering‬ ‭BCS -753‬

‭Page |‬‭1‬
‭CHAPTER 1‬
‭TITLE‬
‭15. The sequence of chapters should be like this‬
‭1. Chapter 1 Introduction‬
‭2. Chapter 2 Problem Formulation and proposed work‬
‭➢ Problem Definition‬
‭➢ Objectives‬
‭➢ Proposed work‬
‭3. Chapter 3 Methodology‬
‭➢ Implementation Strategy (Flowchart, Algorithms etc.)‬
‭➢ Tools/Hardwares/Softwares to be used‬
‭➢ Expected outcome (Performance Metrics with detail)‬
‭4.‬ ‭References‬ ‭and‬ ‭Bibliography‬ ‭(It‬ ‭should‬ ‭not‬ ‭be‬ ‭chapter‬ ‭and‬ ‭should‬‭be‬‭included‬‭at‬
‭the end)‬
‭16.‬‭There‬‭should‬‭be‬‭a‬‭concluding‬‭paragraph‬‭at‬‭the‬‭end‬‭of‬‭each‬‭chapter,‬‭this‬‭paragraph‬‭should‬
‭be the conclusion of that chapter and an introduction to the next chapter.‬
‭17. Check the spelling mistakes.‬
‭18.‬‭A‬‭sample‬‭of‬‭content‬‭writing‬‭in‬‭the‬‭table‬‭of‬‭contents‬‭is‬‭given‬‭below.‬‭This‬‭should‬‭be‬‭strictly‬
‭followed in every Chapter.‬
‭19. The sequence in the file should be like this:‬

‭1.‬ ‭Title page‬


‭2.‬ ‭Declaration / Supervisor certificate / HOD’s Approval‬
‭3.‬ ‭Table of contents with page numbers‬
‭4.‬ ‭List of fig & tables with page numbers‬
‭5.‬ ‭Abstract‬
‭6.‬ ‭Introduction‬
‭7.‬ ‭Literature Review‬
‭8.‬ ‭Real world Application‬
‭9.‬ ‭Inferences drawn from literature‬
‭10.‬ ‭Problem Statement and Solution approach‬
‭11.‬ ‭Proposed time bound progress of project‬
‭12.‬ ‭Bibliography or list of references‬

‭Department of Computer Science and Engineering‬ ‭BCS -753‬

‭Page |‬‭2‬
‭Size:‬‭Standard paper size A4 should be used.‬

‭Page‬ ‭number:‬ ‭Page‬ ‭should‬ ‭be‬ ‭numbered‬ ‭consecutively‬ ‭and‬ ‭clearly.‬ ‭No‬ ‭page‬ ‭number‬
‭should‬ ‭be‬ ‭indicated‬ ‭on‬ ‭the‬ ‭title‬ ‭page,‬ ‭supervisors‬ ‭certificates,‬ ‭declaration‬ ‭and‬
‭acknowledgement,‬‭however‬‭pages‬‭are‬‭to‬‭be‬‭counted‬‭from‬‭the‬‭title‬‭page.‬‭From‬‭title‬‭page‬‭to‬
‭abstract‬ ‭page‬ ‭Greek‬ ‭numbers‬ ‭should‬ ‭be‬ ‭used.‬ ‭From‬ ‭main‬ ‭text‬ ‭to‬ ‭end‬ ‭of‬ ‭report‬ ‭Indian‬
‭numerals should be used. All typing should be on right hand pages only.‬
‭20. The report should be printed single sided.‬
‭21. Starting pages should be Roman numbered without number on Title Page.‬
‭22.‬ ‭The‬ ‭project‬ ‭should‬ ‭be‬ ‭hard‬ ‭bound‬ ‭with‬ ‭Navy‬ ‭Blue‬ ‭color‬ ‭and‬ ‭Black‬ ‭print(engrossed).‬
‭Abstract:‬‭An abstract should be a maximum of 250 words‬‭in English.‬

‭Synopsis:‬

‭Preferably, should be of about 15-20 pages.‬

‭The content should be as brief as is sufficient enough to explain‬

‭●‬ ‭Name/Title of the Project‬


‭●‬ ‭Statement about the Problem‬
‭●‬ ‭Why is the particular topic chosen?‬
‭●‬ ‭Objective and scope of the Project‬
‭●‬ ‭Methodology (including a summary of the project)‬
‭●‬ ‭Hardware & Software to be used‬
‭●‬ ‭Testing Technologies to be used‬
‭●‬ ‭What contribution would the project make?‬

‭Department of Computer Science and Engineering‬ ‭BCS -753‬

‭Page |‬‭3‬
‭Title of the Project‬
‭Report submitted in partial fulfillment of the requirement for‬
‭the degree of‬

‭B. Tech.‬
‭In‬
‭Computer Science and Engineering‬
‭Under the Supervision of‬
‭Supervisor Name‬
‭Designation‬
‭Submitted By‬
‭Candidate's Name ([Link].)‬
‭...‬
‭...‬
‭Candidate's Name ([Link].)‬

‭Department of Computer Science & Engineering‬


‭Maharana Pratap Engineering College, Kanpur‬

‭A.P.J. Abdul Kalam Technical University, Lucknow‬


‭Session:- 2025-26‬
‭Department of Computer Science and Engineering‬ ‭BCS -753‬

‭Page |‬‭4‬
‭Sample Declaration Page‬

‭DECLARATION‬
‭This is to certify that Synopsis Report Entitled “………………………………..‬
‭…………………………………………………………..”‬‭which‬‭is‬‭submitted‬‭in‬‭partial‬
‭fulfillment‬ ‭of‬ ‭the‬ ‭requirement‬ ‭for‬ ‭the‬ ‭award‬‭of‬‭degree‬‭[Link].‬‭in‬‭Computer‬‭Science‬
‭and‬ ‭Engineering‬ ‭to‬ ‭MPEC‬ ‭Kanpur,‬ ‭Dr.‬ ‭A.P.J.‬ ‭Abdul‬ ‭Kalam‬ ‭Technical‬ ‭University,‬
‭Lucknow‬ ‭comprises‬ ‭only‬ ‭original‬ ‭work‬ ‭and‬ ‭studies‬ ‭carried‬ ‭out‬ ‭by‬‭students‬‭himself.‬
‭The‬ ‭matter‬ ‭embodied‬ ‭in‬ ‭this‬ ‭synopsis‬ ‭has‬ ‭not‬ ‭been‬ ‭submitted‬ ‭for‬ ‭the‬ ‭award‬ ‭of‬ ‭any‬
‭other degree.‬

‭Date:‬ ‭Name of Student (Roll No.)‬

‭Approved By :‬

‭ ignature‬
S ‭ ignature‬
S
‭(Name of Project Guide)‬ ‭(Name of HOD)‬
‭Project Guide‬ ‭HOD‬
‭CSE Department‬ ‭CSE Department‬
‭MPEC, KANPUR‬ ‭MPEC,‬
‭KANPUR‬

‭Department of Computer Science and Engineering‬ ‭BCS -753‬

‭Page |‬‭5‬
Sample Table of content Page

TABLE OF CONTENTS

Title…………………………………….………… i

Declaration………………………………............... ii

Abstract…………………………………………... iii

List of Acronyms……………………………….... vi
List of Figures…………………………………..... viii
List of Tables.…………………………………..... ix

Chapter 1 INTRODUCTION

1.1 Fundamentals of …………………. 1-2

1.2 …………………………………… 2-3

1.2.1 ……………………… 2

1.2.2 ……………………… 2

1.2.3 ……………………… 2

Chapter 2 LITERATURE SURVEY

2.1 Introduction 4

2.2 Literature Review 4

2.2.1 Technique 1……………………… 5


2.2.2 Technique 2……………………… 7

2.2.3 Technique 1……………………… 8

Chapter 3 INFERENCES FROM LITERATURE

3.1 Inferences Drawn out of Literature Survey 12

Chapter 4 PROBLEM STATEMENT AND SOLUTION APPROACH

4.1 Proposed work 13

4.2 Methodology 14

4.3 Performance Metrics 15

REFERENCES 17
Sample of Individual Chapters

CHAPTER -1

INTRODUCTION

………………………………………………………………………………………………
………………………………………………………………………………………………
………………………………………………………………………………………………
…………………………….………………………………………………………………
………………………………………………………………………………………………
………………………………………………………………………………………………
………………………………………………….…………………………………………
………………………………………………………………………………………………
………………………………………………………………………………………………
……………………………………………………………………….……………………
………………………………………………………………………………………………
………………………………………………………………………………………………
…………………………………………………………………………………………….

CHAPTER -2

LITERATURE SURVEY
………………………………………………………………………………………………
………………………………………………………………………………………………
………………………………………………………………………………………………
…………………………….………………………………………………………………
………………………………………………………………………………………………
………………………………………………………………………………………………
………………………………………………….…………………………………………
………………………………………………………………………………………………
………………………………………………………………………………………………
……………………………………………………………………….……………………
………………………………………………………………………………………………
………………………………………………………………………………………………
………………………………………………………………………………………………
………………………………………………………………………………………………
………………………………………………………………………………………………
………………………………………………………………………………………………
………………………………………………………………………………………………

Sample for Proposed time bound progress of project

Proposed Project Activity Chart

[Link]. Activity to be Done Date(From) Date( to)


DD-MM-YYYY DD-MM-YYYY
1. Project title selection
2. feasibility study
3. Literature survey
4. problem statement
5. requirement elicitation
6. Solution approach
7. Designing solution
8. Hardware/tool implementation

Abstract: An abstract should be maximum of 250 words in English.

Synopsis:
Preferably, should be of about 15-20 pages.
The content should be as brief as is sufficient enough to explain

• Name/Title of the Project


• Statement about the Problem
• Why is the particular topic chosen?
• Objective and scope of the Project
• Methodology (including a summary of the project)
• Hardware & Software to be used
• Testing Technologies to be used
• What contribution would the project make?

You might also like