You are on page 1of 10

A MANUAL FOR PREPARATION OF PROJECT REPORT

1. GENERAL

The manual is intended to provide broad guidelines to B.C.A. candidates in the


preparation of the project report. In general, the project report shall report, in an
organized and scholarly fashion an account of original project work of the candidate.

2. NUMBER OF COPIES TO BE SUBMITTED

B.C.A. Students should submit three copies to the Head of the Department
concerned on or before the specified date. (i) One copy to the University Library (ii) one
copy to the student concerned and (iii) one soft copy of the report with PowerPoint
presentation and full content including full code should be given to department library

3. SIZE OF PROJECT REPORT

The size of project report should not exceed 100 pages of typed matter reckoned
from the first page of chapter 1 to the last page

4. ARRANGEMENT OF CONTENTS OF PROJECT REPORT

The sequence in which the project report material should be arranged and bound is as
follows.
1. Title Page
2. Bonafide Certificate
3. Acknowledgement
4. List of Figures
5. List of Tables
6. Abbreviations
7. Table of Contents.
5. PAGE DIMENSIONS AND MARGIN

The dimensions of the final bound copies of the project report should be 290 mm
X 205 mm. Standard A4 size (297mm X 210 mm) paper may be used for preparing the
copies.
The final copies of the project report (at the time of submission) should have the
following page margins.

Top Page 30 to 35 mm
Bottom Page 25 to 30 mm
Left Side 35 to 40 mm
Right Side 20 to 25 mm
The project report should be prepared on good quality white paper preferably not
lower than 80 Gms / sq meter.

Tables and figures should conform to the margin specifications large size figures
should be photographically or otherwise reduced to the appropriate size before
insertion.

6. Table of Content

The table of contents should list all material following it as well as any material which
precedes it. The title page, Bonafide certificate and acknowledgement will not find a
place among the items listed in the table of contents but the page numbers of which are in
lower case Roman letters. One and a half spacing should be adopted for typing the matter
under this head.

7. List of Tables

The list should use exactly the same captions as they appear above the tables in the text.
One and a half spacing should be adopted for typing the matter under this head
.

8. TYPING INSTRUCTIONS

General

The impression on the typed copies should be black in color. Uniformity in the
font of letters in the same project report shall be observed.

A sub-heading at the bottom of a page must have atleast two full lines below it or
else it should be carried over to the next page. For typing general text-one and half
spacing and (i) long tables (ii) long quotations (iii) foot notes (iv) multiline captions
(v) references to be use single spacing.

All quotation exceeding one line should be typed in an indented space-the


indentation being 15mm from either margins double spacing should be used for typing
the Bonafide certificate and acknowledgement.

9. Chapters

The format for typing chapter must be sub divided into headings, divisions headings sub
division headings Chapter without punctuation should be centered 50mm down from the
top of the page. Two spaces below, the title of the chapter should be typed centrally in
capital letters. The text should commence 4 spaces below this title, First letter of starting
20mm , inside from the left hand margin.

The division and sub division captions along with their numbering should be left-
justified and paragraphs should commence 3 spaces below the last line of the proceeding
paragraph.
10. NUMBERING INSTRUCTIONS

Page numbering

A page numbers to be (roman or Arabic numbers). Preliminary pages in project report


(such as title page, acknowledgement, table of contents etc.,) should be lower case roman
numerals, consecutively numbered using Arabic numerals.

Numbering of chapters, Divisions and sub-Divisions

Use only Arabic numerals and further decimal notations ex.(2.3.4) first chapter should be
serially numbered using Arabic numerals

11. BINDING SPECIFICATIONS

Project report submitted for M.C.A. should be bound using flexible cover of thick
sky blue art paper. The alpine for the bound volume should be of black calico of 20mm
width. The cover should be printed in black letters and the text for printing should be
identical to what has been prescribed for the title page.
[…Project Title with Upper Case and Font Size 14…,]
The Project Submitted In Partial Fulfillment of the
Requirements for the Award Of The degree of

BACHELOR OF COMPUTER SCIENCE

SUBMITTED BY

[..Student Name with Upper Case and Font Size 14…,]]


[..Student Register number:__________]

GUIDED BY

GUIDENAME
DESIGNATION

DEPARTMENT OF COMPUTER SCIENCE AND APPLICATIONS

SRI CHANDRASEKHARENDRA SARASWATHI VISWA MAHAVIDYALAYA


(SCSVMV)
(Deemed to be University U/S 3 of the UGC Act 1956)
Accredited with “A” Grade by NAAC
Enathur, Kanchipuram – 631 561

April 2019
Sri Chandrasekharendra Saraswathi Viswa Mahavidyalaya
(SCSVMV)
(Deemed to be University U/S 3 of the UGC Act 1956)
Accredited with “A” Grade by NAAC
Enathur, Kanchipuram – 631 561

BONAFIDE CERTIFICATE

Certified that this project work entitled [………project title……….] is the

bonafide work carried out by Mr./Ms. …………………. Reg.No [………………..] in the

Project Lab of B.Sc. (Computer Science) during the VI th Semester of the academic year

Dec 2018 to April 2019.

Project Lab In- charge Head of the Department


Department of Computer Science & Department of Computer Science &
Applications Applications
SCSVMV SCSVMV.

Submitted for the project work viva-voce examination held on _________________

Internal Examiner External Examiner


Certificate by the Guide

This to certify that the project entitled “________________________________________

Submitted for the Degree of B.Sc (Computer Science) by Mr./ Ms. ______________

[Reg.No.________________ ] is a record of project work carried out by him/her during

the period from December 2018 to April 2019 under my guidance.

Signature of the Guide

Name of the Guide with


Designation

Date:
CONTENTS
1. Acknowledgement
2. List of Figures
3. List of Tables
4. Abbreviations

Chapter 1- Introduction

1.1 Abstract
1.2 Existing system
1.3 Drawbacks of the existing system
1.4 Proposed system

Chapter 2 -System Requirements

2.1 Selection of software and language


2.2 Selection of hardware

Chapter 3 - System Design

3.1 Overall System Design structure


3.2 Data Flow diagram
3.3 Database design

Chapter 4- System Implementation

4.1 Methodology used for Testing


4.2 System implementation

Chapter 5 - User Manual

5.1 Screen Shots


5.2 Reports

Chapter 6 - Conclusion

6.1 Scope for further development


6.2 Conclusion

Chapter 7

7.1 Bibliography

Appendix
Sample Coding

1. Introduction

1.1 Abstract

Abstract should be an essay type of narrative not exceeding 500 words, outlining
the problem, the methodology used for tacking it and a summary of the findings.

1.2 Existing system and Drawbacks of the existing system

Write up of the existing system which is being automated or upgraded and the
drawbacks of the existing system due to which the new system is proposed.

1.3 Proposed system

Problem to be solved through software.

2. System Requirements

2.1 Selection of software and language

To decide which language or application is suitable for solving the proposed


system.

2.2 Selection of hardware

To decide which system configuration is suitable for solving the proposed system.

3. System Design

3.1 Overall System Design structure

To draw a pictorial representation of the proposed system.

3.2 Data Flow diagram

To draw Multiple DFD to show data flow details to an extends.

3.3 Database design

Detailed Description of Table structure


4. System Implementation

4.1 Methodology used for Testing

Detailed description of testing done on the proposed system.

4.2 System implementation

Describe the various methods of implementing the proposed system.

5. User Manual

5.1 Input / Output screen

To attach the screen Printout of input and output.

5.2 Reports

To attach the various reports generated by the proposed system.

6. Conclusion

6.1 Conclude the Report by justifying your developed system.

6.2 Describe the future enhancement of the proposed system.

7. Bibliography

List out the references made for the development of the proposed system.

Appendix

Sample coding

To attach sample coding