Bachelor of Technology
Computer Science & Engineering
Project Guidelines
for
8 Semester
th
Year 2022
by,
Department of Computer Science & Engineering
Global Nature Care Sangathan’s Group of
Institutions, Jabalpur (M.P.)
GUIDELINES FOR THE PROJECT REPORT
1. The Project Report must be as per given format and cover all the topics, but
according to project requirement student can omit some topic.
2. The Project Documentation may be about 75 to 100 pages (excluding
coding). The project documentation details should not be too generic in nature.
3. Every chapter start with one title page that includes chapter number and
chapter name. see page 21
4. n+2 (n - no. of students) hard binded copies of project report as per given
format. A CD consisting of the executable file(s) and source code of the
complete project should be attached on the last page of the project report. The
student needs to retain the identical copy of the CD that should be carried
while appearing for the viva-voce along with the project report.
5. After the table of contents every page should have footer, as following
Dept. of CSE Global Nature Care Sangathan’s Group of Institutions
Page<no>
6. Front page of hard binded file same as your project front page, having Navy
Blue with Silver fore color.
Project Report Format
The project report documentation should contain 80 to 100 pages for analysis,
design, and testing phases, however, the size of complete report may vary depending
upon the size of coding/ implantation and appendices. The project documentation
details should not be too generic in nature. To be more specific, whatever theory in
respect of these topics is available in reface books should be avoided as far as
possible. The project documentation should be in respect of your project only. You
should make sensible use of appendices. For example, soft ware user instructions,
detailed code listing, correspondence may be relegated to appendices. Note that
spiral bindings are not suitable for handing in the project report.
And figures should have titles. Detailed information about the layout for the project
proposal and report are also listed below:
Font size and margin
1. The report is to be bound with a clear front cover having navy blue
background and silver fore color.
2. The chapters are in 12-point Times new roman font.
3. Line spacing is in 1.25 point.
4. The pages are of A4 size, with margins as given below, except for the front
cover, which has a specific format given in unit 1. Margins of pages should
follow the following specifications.
a. Left margin-1.5 inch. From edge of paper.
b. Right margin-1 inch. From edge of paper.
c. Top margin-1 inch. From edge of paper.
d. Bottom margin-1 inch. From edge of paper.
5. The above margins shall be observed on charts, graphs, tables, and drawings.
Folded paper or large size paper will not be
accepted unless there is absolutely no other way for the material to be
presented.
Heading
1. Headings used in the project report should follow the following convention:
2. Main Headings or chapter Headings
a. Times roman, 16 font size (1,2,3 etc.) numerals.
b. Capital and bold.
c. Must begin a new page and be centered.
d. Main headings are to be tilted names that reflect content of the that
follows. Main headings are not to be identified as chapters.
e. The number of the headings shall be followed by a period and two
spaces.
f. Must precede the following text material by second heading by three
spaces.
3. Second Headings
a. Times roman, 14 font size, bold,2.1,2.2,2.3, etc
b. Must be centered and be typed in capital and lower case (sentence case)
letters; i.e., the first letter of each word except conjunctions,
prepositions, and articles must be a capital letter. Omit period at the end
of the heading.
c. The letter designation of the heading of the heading shall be followed by
a period and two spaces.
d. Must be four spaces below preceding preceding text and three spaces
ahead of succeeding text.
4. First Sub-Headings
a. Times roman, 13 font size, bold, 2.2.1,2.2.2, etc
b. Must be typed on separate lines beginning at the left margin line of the
text, but need not begin on a new page.
c. Must be typed in capitals and lower case letters except conjunctions,
prepositition, and articles.
d. The number designation of the heading shall be followed by a period and
two spaces. Omit period at the end of the heading.
e. Must be separated from the succeeding text by three spaces.
5. Second sub-headings (second sub-headings should be avoided if possible).
a. Times roman, 13 font size, bold.
b. Must be typed on the same line as the text it introduces beginning at the
left margin line of the text.
c. Must be typed in sentence case.
d. Must be followed by a period at the end of the heading and must be
underscored by a line.
e. The letter designation shall be followed by a period and two spaces.
Appendices re-start the section numbering, using capital letter as section
labels and Arabic numerals as sub-section labels (i.e.,A.1,A.2,); appendix
headers are in decreasing-sized fonts.
If a section is divided into sub-sections, it has at least two subsections.
Similarly for subsections divided into sub-sections, and so on.
The font matter, conclusions, recommendations, Glossary,
Acknowledgements, and reference sections are not divided into sub-sections.
(Include in main heading or chapter heading).
6. Project should have footer having department name, college name and page
no, and footer start after table of index.
Table of Contents
1. Title Page
2. Certificate of HOD & Guide
3. Certificate of Internal & External Examiner
4. Abstract
5. Declaration
6. Acknowledgment
7. Table of Contents
8. Table of Figures
1. Chapter 1 : Introduction
1.1. Background......................................................................................................Page No
1.2. Objective..........................................................................................................Page No
1.3. Purpose, Scope and Applicability................................................................” - -”- -
1.3.1. Purpose
1.3.2. Scope
1.3.3. Applicability
1.4. Achievements
2. Chapter 2: Survey of Technologies
3. Chapter 3: Requirement and Analysis
3.1. Problem Definition
3.2. Identification of Need
3.3. Feasibility Study
3.4. Project Planning & Scheduling using PERT CHART, Gantt Chart
3.5. Software Requirement Specification ( SRS)
3.6. Software Engineering Paradigm applied.
4. Chapter 4 : System Design
4.1. Basic Modules
4.2. Data Design
4.2.1. Database Design
4.2.2. Data Integrity and Constraints
4.3. Diagrams ( Depending upon your project requirement)
4.3.1. Control Flow Diagram
4.3.2. Data Flow Diagram
4.3.3. Entity Relationship Diagram
4.3.4. State Diagram
4.3.5. Class Diagram
4.3.6. Collaboration Diagram
4.3.7. Use Case Diagram
4.4. Object Oriented Design
4.5. Use Interface Design
5. Chapter 5 : Implementation
5.1. Implementation Approaches
5.2. Coding Details and Code Efficiency
5.2.1. Code Efficiency
5.2.2. Comments and Description
5.2.3. Error Handling
5.2.4. Validation & Checks
6. Chapter 6 :Testing Approach
6.1. Testing techniques and testing strategies
6.1.1. Unit Testing
6.1.2. Integrated Testing
6.2. Test Reports / Test Cases
6.3. Modifications and Improvement
7. Chapter 7 :Security Issues
7.1. Database Security
7.2. User Level Security & Access Rights
8. Chapter 8 : Results and Discussion
8.1. Cost Estimation of the Project
8.2. User Documentation
8.3. Report Generation
9. Chapter 9 : SWOT Analysis
9.1. Strength
9.2. Weakness
9.3. Opportunity
9.4. Threads
10. Chapter 10 : Conclusions
10.1. Limitations of the System
10.2. Future Scope and Further Enhancement of the Project
REFERENCES
GLOSSARY
APPENDIX
DESCRIPTION OF THE CONTENTS
1. Title page
Sample format of Title Page is given in page 16. Students should follow the given format.
2. Certificate of HOD & Project Guide
Sample format of Certificate is given in page 17. Students should follow the given format.
3. Certificate of Internal & External Examiner
Sample format of Certificate is given in page 18. Students should follow the given format.
4. Abstract
This should be one/two short paragraphs (100-150 words total), summarizing the project
work. It is important that this is not just a re-statement of the original project outline. A
suggested flow is background. Project aims and main achievements. From the abstract, a
reader should be able to ascertain if the project is of interest to them and, it should presents
results of which they may wish to know more details.
5. Declaration
Sample format of Declaration as per given in page 19. Students should follow the given
format.
6. Acknowledgements
This should express your gratitude to those who have helped you in the preparation of your
project. Sample see in page 20.
Table of contents: the table of contents given the readers a view of the detailed structure of
the report. You would need to provide section and subsection headings with associated
pages. The formatting details of these sections and subsections you will find in unit 2 of this
block.
Table of figures: list of all figures. Table, Graphs, Charts etc, along with their page numbers
in a table of figures.
Chapter 1: Introduction
The introduction has several parts as given below.
Background: A description of the background and context of the project and its relation to
work already done in the area. Summarise existing work in the area concerned with your
project work.
Objectives: Concise statement of the aims and objectives of the project. Define exactly what
you are going to do in the project; the objectives should be about 100 words.
Purpose, scope and applicability: the description of purpose, scope, and applicability are
given below:
Purpose: description of the topic of your project that answers questions on why you
are doing this project. How your project could improve the system its significance
and theoretical framework.
Scope: A brief overview of the methodology, assumption and limitations. You should
answer the question: what are the main issues you are covering in your project? What
are the main functions of your project?
Applicability: you should explain the direct and indirect applications of your work.
briefly discuss how this project will serve the computer world and people.
Achievements: Explain what knowledge you achieved after the completion of your work.
What contributions has your project made to the chosen area? Goals achieved-describes the
degree to which the findings support the original objectives laid out by the project. The goals
may be partially or fully achieved, or exceeded.
Chapter 2: Survey of Technologies
In this chapter survey of technologies you should demonstrate your awareness and
understanding of available technologies related to the topic of your project. You should give
the detail of all the related technologies that are necessary to complete your project. you
should describe the technologies available in your chosen area and present a comparative
study of all those available technologies. Explain why you selected the one technology for
the completion of the objectives of your project.
Chapter 3: Requirements and Analysis
Problem Definition: Define the problem on which you are working in the project. Provide
details of the overall problem and then divide the problem in to sub-problems. Define each
sub-problem clearly.
Identification of Need: Initiation is where there is an identified need for a new system
Feasibility Study: The feasibility study is used to determine if the project should get the
go-ahead. If the project is to proceed, the feasibility study will produce a project plan and
budget estimates for the future stages of development.
Planning and Scheduling: planning and scheduling is a complicated part of software
development. Planning, for our purposes, can be thought of as determining all the small
tasks that must be carried out in order to accomplish the goal. Planning also takes into
account, rules, known as constraints, which, control when certain tasks can or cannot
happen. Scheduling can be thought of as determining whether adequate resources are
available to carry out the plan. you should show the GANTT chart and program evaluation
review technique (PERT).
Software Requirements Specification: In this phase you should define the requirements of
the system, independent of how these requirements will be accomplished. The requirements
specification describes the things in the system and the actions that can be done on these
things. Identify the operation and problems of the existing system. See Details in page 13
Software Engineering Paradigm applied : In this project, which software engineering
model you are used and why. Explain your project according to this model.
Chapter 4: System Design
Describes desired features and operations in detail, including screen layouts, business rules,
process diagrams, pseudo code and other documentation.
Basic Modules: you should follow the divide and conquer theory, so divide the overall
problem into more manageable parts and develop each part or module separately. When all
modules are ready. You should integrate all the modules into one system. In this phase, you
should briefly describe all the modules and the functionality of these modules.
Data Design: data design will consist of how you organize, managing and manipulate the
data.
Database Design: define the structure and explanation of schemas used in your
project.
Data Integrity and Constraints: define and explain all the validity checks and
constraints you are providing to maintain data integrity.
Diagrams: Student draws the diagrams, Depending upon your project requirement).
Object Oriented Design: Give the detail of Object Oriented Approach used in your project.
Define how many classes used in your project; also write which OOP’s features you are used
in your project, like Inheritance, Overloading, Polymorphism, etc.
User Interface Design: define user, task, environment analysis and how you intend to map
those requirements in order to develop a “user interface”. Describe the external and internal
components and the architecture of your user interface. Show some rough pictorial views of
the user interface and its components.
Chapter 5: Implementation and Testing
Implementation Approaches: define the plan of implementation, and the standards you
have used in the implementation.
Coding Details and Code Efficiency: students not need include full source code, instead,
include only the important codes (algorithms, applets code, forms code etc). the program
code should contain comments needed for explaining the work a piece of code does.
Comments may be needed to explain why it does it, or, why it does a particular way.
Code Efficiency: you should explain how your code is efficient and how you have handled
code optimization.
Comments and Description : Should have comments with functional description which
include the input, output, total function calls to/from other functions, function parameters,
description of main variable, data types, logic description etc.
Error Handling : Explain exceptions handling and conditional checking.
Validations & Checks: Write the detail of all validations, like date, range, number-
alphabet & expression validations and also mentions the check for input data.
Chapter 6: Testing Approach
Testing approach: testing should be according to the scheme presented in the system
design chapter and should follow some suitable model-e.g., category partition state
machine-based. Both functional testing and user-acceptance testing are appropriate. Explain
your approach of testing.
Unit Testing: unit testing deals with testing a unit or module as a whole. This would
test the interaction of many functions but, do confine the test within one module.
Integrated Testing: brings all the modules together into a special testing
environment, then checks for errors, dugs and interoperability. It deals with tests for
the entire application. Application limits and features are tested here.
Test Reports: explain the test results and reports based on your test cases, which should
show that your soft ware is capable of facing any problematic situation and that it works
fine in different conditions. Take the different sample and show the outputs.
Modifications and Improvements: once you finish the testing you are bound to be faced
with dugs, errors and you will need to modify your source code to improve the system.
Define what modification you implemented in the system and how it improved your system.
Chapter 7 : Security Issues: Discuss real-time considerations and security issues related to
your project and explain how you intend avoiding those security problems. What are your
security policy plans and architecture?
Database Security: The student should mention the how your data is secure. Write the
deferent security levels provided by you and your selected database software.
User Level Security & Access Rights: The student should clearly emphasize the various
levels of security measures implemented in the project.
Chapter 8: Results and Discussion
Cost Estimation of the Project: The student need to incorporate the estimated cost of the
project using the suitable mechanism/model given in the Software Engineering, such as
COCOMO.
User Documentation: Define the working of the soft ware; explain its different functions,
components with screen shots. The user document should provide all the details of your
product in such a way that any user reading the manual. Is able to understand the working
and functionality of the document.
Report Generation : The project report should include the various sample report for ready
reference.
Chapter 9 : SWOT Analysis
Explain the Strength, Weakness, Opportunity and Threads of your project, 50-80 words for
each.
Chapter 10: Conclusions The conclusions can be summarized in a fairly short chapter (1
to 3 pages). This chapter brings. Together many of the points that you would have made in
the other chapter.
Limitation of the System: Explain the limitations you encountered during the testing of
your soft ware that you ware not able to modify. List the criticisms you accepted during the
demonstrations of your software.
Future scope and further enhancement of the project: Firstly, new areas of investigation
prompted by developments in this project, and secondly, parts of the current works that
were not completed due to time constraints and/or problems encountered.
REFERENCES
It is very important that you acknowledge the work of others that you have used or adapted
in your own work, or that provides the essential background or context to your project. The
use of reference is the standard way to do this. Please follow the given standard for the
reference for books. Journals, and online material.
GLOSSARY
If you use any acronyms, abbreviations, symbols, or uncommon terms in the project reports
then their meaning should be explained where they first occur. If you go on to muse any of
them extensively then it is helpful to list them in this section and define the meaning.
APPENDICES
These may be provided to include further details of results of results, mathematical
derivations, certain illustrative parts of the program code (e.g.-class interfaces), user
documentation etc.
In particular, if there are technical details of the work done that might be useful to others
who wish to build on this work, but that are not sufficiently important to the project as a
whole to justify being discussed in the main body of the project, then they should be
included appendices.
Software Requirement Specification
1 INTRODUCTION
1.1 Product Overview
1.2 Purpose
1.3 Scope
1.4 Reference
1.5 Definition And Abbreviation
2 OVERALL DESCRIPTION
2.1 Product Perspective
2.2 Product Functions
2.3 User Characteristics
2.4 General Constraints
2.5 Assumptions and Dependencies
3 SPECIFIC REQUIREMENTS
3.1 External Interface Requirements
3.1.1 User Interfaces
3.1.2 Hardware Interfaces
3.1.3 Software Interfaces
3.1.4 Communications Protocols
3.1.5 Memory Constraints
3.1.6 Operation
3.1.7 Product function
3.1.8 Assumption and Dependency
3.2 Software Product Features
3.3 Software System Attributes
3.3.1 Reliability
3.3.2 Availability
3.3.3 Security
3.3.4 Maintainability
3.3.5 Portability
3.3.6 Performance
3.4 Database Requirements
3.5 Other Requirements
4 ADDITIONAL MATERIALS
SRS for UMS (University Management System):
1. GENERAL DESCRIPTION – UMS is University Management System for managing the
records of the alumni’s of the university as well as staff, faculty and higher authorities.
1.1 Purpose – The purpose for developing this type of software or introducing this UMS is
to facilitate everyone who is concerned with the university.
1.2 Scope – The scope of UMS is global i.e. it should be able to be accessed from anywhere
through internet i.e. registered users must be able to login to their accounts by directly
accessing the university’s website and then signing in with their username and password
anytime and anywhere.
1.3 Abbreviation – UMS University Management System
1.4 Overview – As the ums is able to have a user interface. It should have a drop down boxes
and if we drag mouse on any control at our welcome screen information regarding that the
control should be displayed. Help menu should be there. As a teacher it should provide them
to upload the various assignments and the attendance of the students. As a developer it
should make a user interface which is user friendly. He should make the UMS as simple as
he can. Backup at the main server should be made.
2. OVERALL DESCRIPTION
2.1 Product Perspective – product i.e. UMS should be able to provide a basic and easy
interchange of information i.e. it should be able to remove the communication gaps between
a teacher and the student. It should have chat facilities for all the users that are online. It
should be compatible with all the operating systems.
2.2 Product Functions - The following are the product functions of the UMS:
The UMS login box should on the official website of the university.
The password field should be secured.
After signing in all updates and new announcements for users should be displayed.
By clicking on the dropdown box of the options the user should be able to view
progress reports, assignments, notes, attendance, placement services and results.
User should be able to change the passwords.
Web pages should support pdf, ppt, doc and similar supported formats so that they
can be easily downloadable and unloadable.
2.3 User Characteristics – A user can only have his/her registration number as username so
if he joins the university then only he can then only he can login. This prevents misuse,
unauthorized access and hacking of the product.
2.4 General Constraints – Server capacity is how many users can access or can be online at
once. More is the number of users more will be the network traffic and hence the server
comes in a down state. Personal firewall and updating is a tough task, it should be such that it
should not block the network traffic, making the system slower. Firewall of the UMS should
not collide with the firewall of the user system.
2.5 Assumptions and Dependencies – UMS should work even at when the network traffic is
high. Server should have a power backup as well as a database backup. The UMS should be
compatible with most of the operating systems i.e. previous and latest ones.
3. SPECIFIC REQUIREMENTS
3.1 External Interface Required
3.1.1 User Interfaces – The external users are the students and the teachers of the university.
The students can have an access to their accounts for their attendance, assignments etc. The
teachers have also an account to access their account for uploading of the students’
attendance and the assignments to be submitted by them.
3.1.2 Hardware Interfaces – The external hardware interface used for accessing the UMS is
the personal computers of the teachers and the students. The PCs may be laptops with
wireless LAN as the internet connections provided will be wireless.
3.1.3 Software Interfaces – The Operating Systems can be any version of Windows, Linux,
Unix or Mac which supports TCP/IP protocols.
3.1.4 Communication Interfaces – The communication interface is a local area network
through wireless network routers.
3.2 Performance Requirements – The PCs used must be at least Pentium 4 machines so that
they can give optimum performance of the product.
3.3 Design Constraints – The constraints at the designing time are that the needs of the
university students and the teachers may keep on changing so the designers must keep this in
view and design the product in this way that it is easily updatable.
3.4 Attributes – The following are the attributes of the product UMS:
It should be equipped with current and archive database.
All records can easily be updated.
It should have its personal firewall.
It should facilitate student with updating his/her account, downloading or uploading
of assignments from anywhere.
It should also do the same for teachers they can also have their pay checks online i.e.
UMS should be capable of online transaction.
3.5 Other Requirements – The software is such that as the time goes by the need of the
university management, students and teachers may keep on changing thus it is made to
change from time to time.
4 ADDITIONAL MATERIALS
Data Flow Diagram for UMS:
<<PROJECT TITLE>>
A Major Project
Submitted in partial fulfillment of the requirements
for the degree of
BACHELOR OF TECHNOLOGY
(Computer Science & Engineering)
by
<<Student Name>>
<<Enrollment No>>
Under the guidance of
<< Guide name >>
Department of Computer Science & Engineering
Global Nature Care Sangathan’s Group of
Institutions, Jabalpur (M.P.)
under
RAJIV GANDHI PRODYOGIKI VISHWAVIDYALAYA, BHOPAL
(M.P.)
APR-2022
Global Nature Care Sangathan’s Group
of Institutions, Jabalpur (M.P.)
Department of Computer Science & Engineering
Certificate
This is to certify that the Major Project report entitled <<project_title>>
submitted by <student name>> has been carried out under my guidance &
supervision. The project report is approved for submission towards partial
fulfillment of the requirement for the award of degree of Bachelor of
Engineering in Computer Science & Engineering from “Rajiv Gandhi
Proudyogiki Vishwavidyalaya, Bhopal (M.P).
<<guide_Incharge>> <<HOD_name>>
Project Incharge HOD
Dept of CSE
Global Nature Care Sangathan’s Group
of Institutions, Jabalpur (M.P.)
Department of Computer Science & Engineering
Certificate
This is to certify that the Major Project report entitled
“<<project_title>>” is submitted by <<student_name>> for the partial
fulfillment of the requirement for the award of degree of Bachelor of
Engineering in Computer Science & Engineering from Rajiv Gandhi
Proudyogiki Vishwavidyalaya, Bhopal (M.P).
Internal Examiner External Examiner
Date : Date :
Declaration
I / We hereby declare that the project entitled “<<project_title>>”
which is being submitted in partial fulfillment of the requirement for award of
the Degree of Bachelor of Engineering in Computer Science and Engineering to
“RAJIV GANDHI PROUDYOGIKI VISHWAVIDYALAYA, BHOPAL
(M.P.)” is an authentic record of our own work done under the guidance of
<<project guide name>>, Department Computer Science & Engineering,
GLOBAL ENGINEERING COLLEGE, JABALPUR..
The matter reported in this Project has not been submitted earlier
for the award of any other degree.
Dated : <<student(s)_name>>
Place : <<Ernollment_no>>
Acknowledgment
We sincerely express indebtedness to esteemed and revered guide
“<<guidename>>”, in department of CSE for his invaluable guidance,
supervision and encouragement throughout the work. Without his kind
patronage and guidance the project would not have taken shape.
We take this opportunity to express deep sense of gratitude to
“<<HOD Name>>”, Head of “Department of Computer Science &
Engineering” for his encouragement and kind approval. Also we thank him in
providing the computer lab facility. We would like to express our sincere
regards to him for advice and counseling from time to time.
We owe sincere thanks to all the lecturers in “Department of
Computer Science & Engineering” for their advice and counseling time to time.
Dated : <<student_name>>
Place : <<enrollment_no>>
Chapter 1
Introduction
