Project Title 1

PROJECT REPORT GUIDELINES-2020-21

PAPER SIZE, BINDING, MARGINS, FONTS AND LINE SPACINGS
Instructions:
Font: Times New Roman
Font Size:
Chapter Title: 16 Bold (In Capital letters, Centered)
Side Headings: 12 Bold (In Capital letters)
All other text 12 (Normal text)
Line Spacing: 1.5
Paper Size: A4 [One side printing]
Hard binding: All Final Semester PG Major Projects
Color: White
Margins:
Left margin: 1.5 inch
Right margin: 1 inch
Top: 1 inch
Bottom: 1 inch
Number of Copies: One Copy per Student
Number of Pages:
Final Semester PG : Minimum – 60 ; Maximum – 100

Header: Project Name (Left) and Page number (Right)

Footer: Department of Computer Science, Christ University
[with font size 10 for both header and footer; Include border line for
header and footer]

PAGE NUMBERING
1. Lower-case Roman numerals (e.g., iii, iv, v) for the front matter/preliminary
material from acknowledgements. No page numbering for TOC.
2. Arabic numbers (e.g., 1, 2, 3, etc.) starts from chapter 1. (This can be achieved by
giving a section break)
3. No Header and footer for TOC, Certificate and Title Page.
4. Chapters, Sections, Subsections are numbered as per the following meaning:
example
1.3.2 stands for Chapter 1, section 3, Subsection 2.

IMPORTANT INSTRUCTIONS
1. Do not end a page with a title. Shift the title to the next page.
2. Do not end a page with a single line of a new paragraph, Start the new paragraph
in the next page.
3. Do not include Thumb index, transparency sheets etc., within the report.
4. Use a drawing canvas to start drawing the image.
5. Strictly follow the given format for bibliography.
6. Follow the guidelines for Screen shots/Diagrams.

Department of Computer Science, Christ University

Project Title 2

7. Use automatic table of content option available in documentation tools (MS-

Word, Open Office, etc.)
8. In Title page and Certificate page, M.Sc. course is to be mentioned as M.Sc.
(Computer Science).

FIGURES AND TABLES

1. Position Figures and Tables as close as possible to the text where they are
referred.
2. Figures and Tables should be numbered in ascending order for each chapter.
Example second image in chapter 3 will be Fig 3.2.
3. The number of the figure, and its caption should be typed immediately below it in
Times New Roman Size 10.
4. The number of the table and its caption should be typed immediately above it in
Times New Roman Size 10.

ACKNOWLEDGEMENTS
1. Guide
2. All those who helped to complete the project

ABSTRACT

The abstract should condense the report to 200 words or less in single-space
format. Do not include any sub-title or bullets in abstract. The abstract should
contain:

a. the most essential background information

b. the purpose and scope of the project
c. major outcomes and recommendations

CONCLUSION

Rewrite the aim and objective of the project with a brief note on the major modules.
Summarize the available features, results and limitations. Conclude with your future
enhancements.

REFERENCES PAGE INSTRUCTIONS

1. In the body of your text refer to the source of your information by inserting
consecutive numbers in brackets at the end of each segment of cited information—like
this [1]. These reference numbers can also be inserted within a sentence [2], without
changing the sentence’s punctuation. You may also cite your reference in your text as
follows: “As Smithsky [3] points out,..

Department of Computer Science, Christ University

Project Title 3

2. Unless you are referring to a complete book or article, you will also need to identify
the page number(s) of your source of information. Indicate exact page numbers of a
source within your brackets after a comma [4, pp. 3-6], or by a simple rhetorical device in
your text such as “However, on page 79 of [5] the author seems to contradict himself
when he states. . .“ If you must refer to more than one separate page or source in the same
reference, use semicolons for separation: [6, p. 46; 7, pp. 29-31; 9, pp. 8-12].

3. Once you have numbered a source use the same number for all subsequent references
to that source. References at the end of quotation marks “are punctuated with the period
after the reference” [8, p. 23].

4. Always use square brackets around reference numbers [10, pp. 78-85] to distinguish
from equation numbers, which are given in parentheses (6).

5. Single space individual references, with no indentation for a second or third line.
Double space between separate references.

6. Use a common abbreviation for a journal title if there is one, e.g. IEEE Electron
Device Lett. Otherwise give the full name of the journal.

7. End each entry with a period.

8. List each source only once on your reference page.

Books Format:
Author's last name, first name. Book title. Edition and other additional information. City of
publication: Publisher, year.

[1] Allen, Thomas B. Vanishing Wildlife of North America. Washington, D.C.: National
Geographic Society, 1974.

[2] Hyde, Margaret, and Elizabeth Forsythe. Suicide: The Hidden Epidemic. New York: Watts,
1986.

[3] Baron, Alvin. Bud’s Easy Research Paper Computer Manual For IBM PC’s. 3rd ed. New
York: Lawrence House Publishers, 2000.

Magazine & Newspaper Articles Format:

Author's last name, first name. "Article title." Periodical title Volume # Date: inclusive
pages.

[1] Kanfer, Stefan. "Heard Any Good Books Lately?" Time 113 21 July 1986: 71-72.

Department of Computer Science, Christ University

Project Title 4

Website or Webpage Format:

Author's last name, first name (if available). "Title of work within a project or
database." Title of site, project, or database. Editor (if available). Electronic publication
information (Date of publication or of the latest update, and name of any sponsoring
institution or organization). Date of access and <full URL>.

Note: If you cannot find some of this information, cite what is available.

[1] Devitt, Terry. "Lightning injures four at music festival." The Why? Files. 2 Aug. 2001. 23 Jan.
2002 <http://whyfiles.org/137lightning/index.html>.

[2] Dove, Rita. "Lady Freedom among Us." The Electronic Text Center. Ed. David Seaman.
1998. Alderman Lib., U of Virginia. 19 June 1998
<http://etext.lib.virginia.edu/subjects/afam.html>.

Sample reference page:

[1] Allen, Thomas B. Vanishing Wildlife of North America. Washington, D.C.: National
Geographic Society, 1974.

[2] Boorstin, Daniel J. The Creators: A History of the Heroes of the Imagination. New York:
Random, 1992.

[3] Hall, Donald, ed. The Oxford Book of American Literacy Anecdotes. New York: Oxford UP,
1981.

[4] Kanfer, Stefan. "Heard Any Good Books Lately?" Time 113 21 July 1986: 71-72.

[5] Devitt, Terry. "Lightning injures four at music festival." The Why? Files. 2 Aug. 2001. 23 Jan.
2002 <http://whyfiles.org/137lightning/index.html>.

Appendix
Use the appendices to avoid interrupting the body of the report with excessive detail,
thereby improving readability. Number the appendices with a structure like: A, A.1, B,
etc. The appendices might include, but are not limited to:

a. A "Users Manual" or instructions for operating and maintaining the

system you've designed.
b. Additional charts, graphs and tables.
c. Mathematical derivations, proofs, etc.
d. Detailed calculations (theoretical developments, error and sensitivity
analyses, etc.)
e. Budget status.
f. Gantt chart and/or other planning information.
g. Division of labor within the group: what did each member accomplish for
the project and for the report?

Department of Computer Science, Christ University

Project Title 5

h. An analysis of the "design concepts" topics (e.g. health and safety) given
separately. Indicate how your design is affected by each topic.

List of Figures
Fig. No. Figure Name Page No.

List of Tables
Table No. Table Name Page No.

List of Abbreviations
Example:
UNICEF United Nations Children’s Fund
Strictly follow the Order of Pages given below
Title Page (Refer the template)

Certificate page (Refer the template)

Company Certificate [ company seal, signature etc is a must]

Acknowledgments

Abstract

Table of Contents

List of Tables

List of Figures

Abbreviations (optional)

All Chapters …. (Refer the sample TOC given below)

Appendices

References

Department of Computer Science, Christ University

Project Title 6

TABLE OF CONTENTS

Acknowledgments iv
Abstract v
List of Tables
List of Figures
Abbreviations (optional)
1. Introduction 1
1.1. Problem Description 3
1.2. Existing System
1.3. Project Scope
1.4. …...
1.5. …..
2. System Analysis
2.1. Functional Specifications
2.1.1. …..
2.1.2. …..
2.2. Block Diagram
2.3. System Requirements
2.3.1. .......
2.3.2. …...
3. System Design
3.1. System Architecture
3.2. Module Design
3.3. Database Design
3.3.1. Table Structure
3.3.2. Data Flow Diagram
3.3.3. ER Diagram
3.4. System Configuration (optional)
3.5. Interface Design
3.5.1. User Interface Screen Design

Department of Computer Science, Christ University

Project Title 7

3.5.2. Application flow/Class Diagram

3.6. Reports Design
3.7. …....
3.8.
4. Implementation
4.1. Coding Standard
4.2. Screen Shots
5. Testing
5.1. Test Cases
5.2. Test Reports
6. Conclusions
6.1. Design and Implementation Issues
6.2. Advantages and Limitations
6.3. Future Enhancements
Appendices
A …….
A.1 ……
A.2…….
A.3…….
B…….
B.1…….
B.2…….
B.3…….
References

Department of Computer Science, Christ University