SM Project Report Reference Booklet
SM Project Report Reference Booklet
– Computer Science
Instructions:
6. All paragraphs will be 1.5 line spaced and a double space between each paragraph. Each paragraph will begin
with a five–space indentation.
7. Chapter titles should be bold with 14pt typed in all capital letters and should be aligned at the center of the page.
Section heading should be aligned at the left with 12pt and bold and capitalized. Section subheading should be
aligned at the left with title case (the first letter of each word is to be capitalized). Leave two spaces between
section headings and 1 space between two section subheadings.
8. Illustrations (Charts, drawings photographs, figures) are to be in the text. Use only illustrations really pertinent
to the text. Illustrations must be sharp, clear, black and white. Illustrations downloaded from internet are not
acceptable.
a. Illustrations should not be more than two per page. One could be ideal
b. Figure No. and title at bottom with 12pt.
c. Legends below the title in 10pt.
d. Proper margin in all sides.
e. Illustrations as far as possible should not be Xeroxed (photo copy) 9. Photographs if any should
be of glossy prints.
10. Please use SI system for units. If student would like to add the equivalent in inch-pound (IP) units, they must
be stated in parentheses after the SI units. In case the final result comes out in any other units (say due to
empirical formula etc.) convert the unit to SI unit.
11. Please number the pages on the front side, centrally below the footer.
12. References should be either in order as they appear in the paper or in alphabetical order by last name of first
author.
13. Symbols and notations if any should be included in nomenclature section only.
Reference books
Papers from Journal or transactions
Papers from conference proceedings
Reports Handbooks etc.
Patent
Patent no. Country (In parenthesis), date of application, title, year. If taken from “Abstract” give cross reference as CF,
CA…….
Internet
WWW.(Site)
2-Blank spaces
OF (12/upper case)
(Two blank spaces)
BACHELOR OF SCIENCE
IN
COMPUTER SCIENCE (16/bold/upper case)
(Two blank spaces)
BY(14/bold/upper case)
(Two blank spaces)
2023-24(12/bold/upper case)
(2 blank space)
CERTIFICATE(16/bold/upper case)
(Three blank space)
This is to certify that the project report entitled (12 /sentence case)
(Two blank space)
<<PROJECT TITLE>>
(12/bold/upper case)
(Two blank space)
Submitted by (one-line blank space)
Place:
Date:
We feel great pleasure in expressing our deepest sense of gratitude and sincere thanks to our guide <<name of
guide>> for their valuable guidance during the Project work, without which it would have been a difficult task. I
have no words to express my sincere thanks for valuable guidance, extreme assistance and cooperation extended to
all the Staff Members of our department.
This acknowledgement would be incomplete without expressing our special thanks to Hon. Sangeeta Yadav, Head
of the Department of B. Sc. (Computer Science) for her support during the work.
We would like also like to extend our heartfelt gratitude to our Principal, Dr. K. P. Kakde who provided a lot of
valuable support, mostly being behind the veils of college bureaucracy.
Last but not the least we would like to thank all the Teaching, Non-teaching staff members of our Department, our
Parents and our collegues those who helped us directly or indirectly for completion of this project successfully.
C) CONTENTS
(Four blank space)
CONTENTS (14/bold/upper case)
Introduction
Introduction should help to understand three key questions to the reader: Why is this important problem?
What has been done before? How does your topic (problem) bring significant new understanding to the
respective field? It should be written in present tense and should include the following points:
i. Outline the problem you are working on, why is it interesting, important and what are the challenges?
ii. List your aims and goals. An aim is something you intend to achieve (e.g., learn a new programming
language and apply it in solving the problem), while a goal is something specific you expect to deliver
(e.g., a working application with a particular set of features)
iii. Give an overview of how you have carried out the project (i.e. software development model) iv. A
brief overview of the rest of the chapters in the report (a guide tithe reader of the overall structure of
the report).
v. This chapter is relatively short (2-4 pages) and must give the reader very clear understanding of what the
project is about and what your goals are
Problem Definition: Define/formulate the problem clearly and concisely of your project work.
Provide details of the overall problem and then divide the problem into module(s).
ii. Requirements Specification: A structured list of requirements. The requirement specifications
determine specific feature expectations, resolution of conflict or ambiguity in requirements as
demanded by the various users or groups of users and documentation of all aspects of the project
development process from start to finish. Here you should define the requirements of the system,
independent of how these requirements will be accomplished and identify the operation and problems
of the existing system.
iii. Description of Use cases/documentation (list of use case titles, with the full use cases appearing in the
appendix).
iv. Software and Hardware Requirements: Define the details of all the software and hardware needed for
the development and implementation of your project.
Design
i. Start with the architecture of your project and describe all components that makes up the system
ii. You can use necessary DFDs and UML diagrams with proper explanation of your project design
iii. The structure and contents of this chapter will vary according to the nature of your project, hence
above mentioned list of requirements is only representative.
Implementation
This chapter is about the realization of the concepts and ideas developed earlier. You can describe the
methodology (problem formulation and processes used to solve the problem) you have identified for the
development of your system/application (Literature review will help you to identify/choose methodology).
It can also describe any problems that may have arisen during implementation and how you dealt with them.
It should include the details regarding all modules of the project and description of each module. It may be
better to use pseudo-code rather than actual code, when describing an algorithm. Describe how a particular
algorithm is implemented or how an interesting programming problem was solved.
Conclusion
Demonstrate that you solved the problem or made significant improvement in the existing system/application.
You can use illustrations such as tables, figures, graphs etc. to support the conclusions.
i. Summarize what your project has achieved. Address each objective decided in the introduction.
ii. A critical evaluation of the results of the project (e.g., how well were the objectives met, is the
application fit for purpose, has good design and implementation practice been followed, was the right
implementation technology chosen and so on).
iii. Results should be clear and concise.
iv. State why your solution offers a new/improved solution
v. Acknowledge any limitations
References
i. List of references.
ii. Bibliography: This lists all the sources of information that you made use of during the project but are
not referenced in the text. The items in the list must be relevant to your project, so don't just list
everything you may have looked at or read.
2-Blank spaces
COVER PAGE {to be
pasted on the front side A PROJECT REPORT ON(12/bold/upper case)
of report booklet} (Two blank spaces)
OF(12/upper case)
(Two blank spaces)
BACHELOR OF SCIENCE
IN
COMPUTER SCIENCE(16/bold/upper case)
(Two blank spaces)
BY(14/bold/upper case)
(Two blank spaces)