Minor Project Report Format

INSTITUTE OF INFORMATION TECHNOLOGY & MANAGEMENT
Accredited ‘A’ Grade by NAAC & Recognised U/s 2(f) of UGC act
Rated Category `A+’ by SFRC & `A’ by JAC Govt. of NCT of Delhi
Approved by AICTE & Affiliated to GGS Indraprastha University, New Delhi
INSTITUTE OF INFORMATION TECHNOLOGY & MANAGEMENT, NEW DELHI
Date: September 25, 2024
Minor Project Guidelines for BCA-V semester

Objective
All the students enrolled for BCA Programme, are to carry out a software project as part of
curriculum. At the end of the semester the students are to submit a written project report to be
forwarded to GGSIP University. The aim of the project is to give the students an integrated
experience in solving a real-life problem by applying knowledge and skills gained on completion
of theory papers and in-house practical papers during BCA course. It provides an occasion for
students to realize the importance of resource and time management, ownership of task towards
deliverables, innovation and efficiency in the task management. It also provides a good opportunity
for students to build, enhance and sustain high levels of professional conduct and performance and
evolves a problem solver frame of mind in students at early stage. It also prepares students for
taking up responsible assignments in the corporate establishment.
CO # Detailed Statement of the CO BT Level Mapping to PO #
CO1 An ability to understand the principles and BTL2 PO1,PO3,PO4,PO5,

Working of system software/hardware.
CO2 An ability to apply mathematical methodologies BTL3 PO1,PO3,PO4,PO5,PO8
to solve computation task, model real world
problem using appropriate data structure,
Software Engineering and suitable algorithms
CO3 An ability to understand the structure and BTL5 PO3,PO4,PO5,PO6
Development methodologies of software systems.
CO4 Familiarity and practical competence with a broad BTL6 PO3,PO4,PO5,PO11
range of programming language and open source
platforms.
University Scheme for Summer Training & Project
As per the syllabi of BCA (Paper Code: BCA-307), students of Semester V are to write a project
report comprising of 4 credits. The project report has two components, viz.
(a) External : Project (60 Marks), where a written report is to be submitted. It

involves external viva and presentation.
(b) Internal : Project (40 Marks), it includes continuous evaluation from idea
generation to final presentation.
Scope of Project
The SRS worked out during the summer training are to be converted into an application using
front& back-end tools during the V semester as a software project independently by each student .It
is partly the responsibility of the student to find a relevant topic for his/her project and decide it in
consultation with the guide allocated to him/her. The project work shall be an application
development in a language/platform that the student has learnt during the previous semesters. It
shall be an in-house development. Each student is required to carry out the independent work
and submit the report individually.
NOTE: ANY PREVIOUS WORK OR BORROWED REPORT WILL BE SUMMARILY

REJECTED AND IN ALL CASES OF REJECTION THE WORK IS TO BE REPEATED
AFRESH. STUDENT MUST ENCLOSE PLAGIARISM REPORT OF THEIR PROJECT
TO AVOID DUPLICACY OF WORK.
Methodology
General Guidelines that are to be performed to conduct the summer training project are given in
details in Appendix-A.
Format & Final Report
The student will submit his/her project report/thesis in the prescribed format, as given
hereunder, after the second presentation. The project report/thesis should include:
a) ONE hard copy (Maroon color with golden print) of the project report / thesis.
b) Soft copy of project on CD including all resource code/ compiled binary code and the
manuscript in MS-Word document format.
The Guidelines for the format to be used for compilation of the project report are given in
Appendix-B. All students are to adhere to these guidelines.
Appendices
The appendices are to be attached at the end of the report and to be numbered as Appendix-A,
Appendix-B etc right justified at the top of the page. An appendix may have annexure (s). If there
are annexure, these are to be attached immediately after the said appendix. The annexure are to be
numbered as Annexure-I, Annexure-II, Annexure-III and Annexure-IV etc.
Appendix ‘A’
GENERAL GUIDELINES FOR THE PROJECT WORK
1. The project should be original, of real-life value, and not copied from existing material
from any source. A student should ensure that he understands what is expected by
preparing a requirement document of his understanding and get it reviewed by the guide.
2. Design document should also be reviewed and code should also be peer reviewed.
3. A user manual has to be prepared and reviewed.
4. Testing has to be thorough and at various levels, followed by an acceptance test based on
the requirement document and user manual.
5. Students should follow the steps as discussed in Software Development Life Cycle while
writing dissertation and use Software Engineering Methodologies for development of
deliverables, mere programming will not be sufficient. Students must note that
interviewers for job are often more interested in the problem solved, alternatives that could
have been tried and the benefits derived from the developed application, rather than just
implementation details.
6. One Project will be submitted only by one student. However, if the nature of the project is
very big & large enough to be divided in different independent big modules having an
estimated required effort of minimum 06 weeks to be developed by one person, can be
taken up and designed in such a way that every student will be responsible for one module
and will submit only that specific module as it were a complete software project.
7. Every student has to get his / her synopsis approved from the guide.
8. The synopsis must be brief i.e., not more that 4-6 pages. It must address details like
(however, students may follow the SRS format of IEEE for writing Synopsis)
a. Name / title of the project,
b. Statement about the problem,
c. Why the Particular topic is chosen? It must address Present State of the Art.
d. Objective and scope of the project,
e. Analysis, Design, Development & Testing Methodology,
f. H/W& S/W to be used,
g. Testing Technologies to be used,
h. What contribution / value addition would the project make?
i. Limitations / constraints of the project,
j. Conclusion, Future Scope for Modification,
k. References and Bibliography.
9. After approval of the Synopsis, Students will need to give Two Presentations /
Demonstration, as per the schedule fixed by their respective Institutions or University.
First Presentation will ideally be given after Design Phase is over. Second should be given
when System Testing is over. First Presentation should be given in the first month. Second
Presentation (Projects) is in second month. Final Project reports should be given latest by
the end of the third month of the semester.
Appendix-B
FORMAT OF THE PROJECT REPORT
Note the following guidelines with respect to Preparation of the Documentation. Please note that
documentation is meant for other people, and hence it must be self-explanatory, in all respect. The
sequence of the Pages in the Project Report will be as follows:
FORMAT OF THE STUDENT PROJECT REPORT ON COMPLETION OF THE PROJECT
Synopsis
1. Title of Project
2. Problems with the Existing System(Note: Consider the previously existing project as
Manual)
3. Description of the Proposed System(Note: The proposed (new project that you are
making) system will be web based, online system)
4. Description and identification of the Functional Modules(Here, mention the name of the
modules and the users of the system)
5. Tools/Platforms
5.1. Hardware specification (RAM, HDD, Processor etc.)
5.2. Software specifications (OS, Front End, Back End, Any other additional s/w
interface reqd.)
6. Methodology
6.1. SDLC Model to be used
6.2. Justification for the Selection of Model
7. Future Scope
FORMAT OF PROJECT REPORT
I. Cover Page as per format

II. Acknowledgement
III. Certificate of the project guide
IV. Synopsis of the Project
Main Report
Chapter-1 –INTRODUCTION
1.1 Objective & Scope of the Project

1.2 Theoretical Background Definition of Problem
1.3 System Analysis & Design vis-a-vis User Requirements
1.4 System Planning (PERT Chart)
Chapter-2 - METHODOLOGY
2.1 Methodology adopted
2.2 System Implementation
2.3 Details of Hardware & Software
2.4 System Maintenance & Evaluation
Chapter-3 SYSTEM DESIGN

3.1 ERD, DFD
3.2 Input and Output Screen Design
3.3 Process involved
Chapter-4 Coding and Screenshots of the project
Chapter-5 Conclusion, Future Scope and References
Title Page
The format of the title page is attached as Annexure-I.
Certificate
The format of the certificate is attached as Annexure-II. A certificate by the student, guide and
duly authenticated by the Directors to be attached.
Acknowledgement
In the “Acknowledgement” page, the writer recognizes his indebtedness for guidance and
assistance by the guide and other members of the faculty. Courtesy demands that he/she also
recognizes specific contributions by other persons or institutions such as libraries and research
foundations. Acknowledgements should be expressed simply, tastefully, and tactfully duly signed
above the name.
TEMPLATE FOR CHAPTER SCHEME

The format of Chapter Scheme is attached as Annexure-III.
FORMAT OF LIST OF TABLES AND FIGURES
The format of list of Tables/Figures/Abbreviation and References/Bibliography is attached as

Annexure-IV.
BODY OF THE PROJECT REPORT: GUIDELINES FOR PROJECT REPORT WRITING
The pages coming under the preview of the CONTENTS will only be numbered in the BOTTOM
of the Page Centrally Aligned.
1. ONE Hardbound Copies (One Original and Two Xerox) will be submitted with the Institute
out of which one will be given back to the candidate. All the students are required to follow
the same binding format in maroon color with back quote mentioning title of the project,
name of the student and year.
2. At the end of the Project Report Two White blank sheets must be attached.
3. At the beginning of each chapter one blank page (Strictly as per the sample supplied) must
be attached. These pages will neither be numbered nor counted in total numbering of pages.
They will only indicate the beginning of a New Chapter with its learning objectives.
4. Font size of the documentation will be 12 Times New Roman and the pages will be one and
half line spaced.
5. Good quality white A4 size paper should be used for typing and duplication. Care should be
taken to avoid smudging while duplicating the copies.
6. Page Specification: (Written paper and source code)

 Left margin - 3.0 cms
 Right margin- 2.0 cms
 Top margin 2.54 cms
 Bottom margin 2.54 cms
 Page numbers - All text pages as well as Program source code listing should be
numbered at the bottom center of the pages.
7. Normal Body Text: Font Size: 12, Times New Roman, Double Spacing, Justified. 6 point
above and below para spacing
8. Paragraph Heading Font Size: 14, Times New Roman, Underlined, Left Aligned. 12 point
above & below spacing.
9. Chapter Heading Font Size: 20, Times New Roman, Centre Aligned, 30 point above and
below spacing. Coding Font size : 10, Courier New, Normal
10. Submission of Project Report to the University: The student will submit his/her project
report in the prescribed format. The Project Report should include:
1. One copy of the summary/abstract.
2. One hard Copy of the Project Report.
3. The Project Report may be about 75 pages (excluding coding).
11. Kindly note that all-methodological details and theoretical aspects must be written in
students‟ own words. Copying from books or other students will not be accepted, in any
case.
****All students are informed not to write definition of various concepts in index,
mention the topics w. r. t. to your project (i.e., how various concepts have been
implemented in the project) * No detailed theories required. ****
Annexure-I
Title of the Project Report

(Times New Roman, Italic, Font size = 24)
Submitted in partial fulfillment of the requirements
for the award of the degree of
Bachelor of Computer Applications
To
Guru Gobind Singh Indraprastha University, Delhi
Guide: Submitted by:

(Guide Name) (Student_name)
(Designation) (Enroll No)
Institute of Information Technology & Management,

New Delhi – 110058
Batch (2022-2025)
Annexure-II
Certificate
This is to certify that this project entitled “ xxxxxx xxxxx xxxxx xxxx xxxx xxx”
submitted in partial fulfillment of the degree of Bachelor of Computer Applications
to the “xxxxxxxxxxxxxxxxxxxxxxxxxx” through xxxxxx xxxxx done by Mr./Ms.
,RollNo. is an is an authentic work carried out by him/her at under my guidance. The
matter embodied in this project work has not been submitted earlier for award of any
degree to the best of my knowledge and belief..
Signature of the Student 1
Signature of the Guide:

Date:
Name of the Guide:
Designation:
Countersign HOD Countersign Director

SELF CERTIFICATE
This is to certify that the dissertation/project report entitled “…………………………………” is

done by me is an authentic work carried out for the partial fulfilment of the requirements for the
award of the degree of Bachelor of Computer Applications under the guidance of……………...
The matter embodied in this project work has not been submitted earlier for award of any degree or
diploma to the best of my knowledge and belief.
Signature of the student

Name of the Student
Roll No.
Annexure-III
TEMPLATE FOR CHAPTER SCHEME
CONTENTS
(Font size -18)
Certificate i
Acknowledgements ii
List of Tables/Figures/Symbols iii
Synopsis iv
Chapter 1: Introduction
1.1 Introduction -Existing System
1.2 Description of proposed information system – A
brief description of all processes & sub processes in
narrative form
1.3 Software Requirement Specifications
Note: Texts in black are the headings and subheadings they are to be written as it is.
Texts in green are the descriptions are also to be written as it is. Texts in red are to be
written according to your system.
1.3.1 Introduction – A single paragraph about SRS
The following subsections of Software Requirement Specifications Document should

facilitate in providing the entire overview of the Information system “Title of your
Project” under development.
This document aims at defining the overall software requirements for your end users.
Efforts have been made to define the requirements of the Information system
exhaustively and accurately.
1.3.2 Purpose
The main purpose of Software Requirement Specifications Document is to describe in a
precise manner all the capabilities that will be provided by the Software Application
“Your Title”. Italso states the various constraints which the system will be abide to. This
document further leads to clear vision of the software requirements, specifications and
capabilities. These are to be exposed to the development, testing team and end users of
the software
1.3.3 Scope – scope of your proposed system

1.3.4 Definition, acronyms, abbreviations
1.3.5 References
1.3.6 Overview
The rest of this SRS document describes the various system requirements,
interfaces, features and functionality in detail. Overall description of
proposed system
1.3.7Product Perspective
The application will be windows-based, self contained and independent
software product.
Front End Client

Application (with data
entry / update
Backend
/delete /view and Database
reporting facility)
Interaction of Product with the

environment
Assumptions and Dependencies – The application is developed on the following assumptions.

(List the assumptions specific to your project)
1.3.8 System Interfaces None
1.3.9 User Interfaces

The application will have a user friendly and menu based interface. Following
screens will be provided
.
(i) A Login Screen for entering username, password and role
(Administrator, operator) will be provided. Access to different
screens will be based upon the role of the user. And so on. The
following reports will be generated:
(i) And so on
1.3.9.1 Hardware
Interfaces None
1.3.9.2 Software Interfaces
<Describe the connections between this product and other specific
software components (name and version), including databases,
operating systems (Windows? Linux?Etc…), tools, libraries, and
integrated commercial components.
1.3.9.3 Communication Interfaces
None
1.3.10 Memory Constraints
1.3.11 Operations
This product will not cover any automated housekeeping aspects
ofdatabase. The DBA at client site will be manually deleting old/
nonrequired data. Database backup and recovery will also have to
be handled by DBA.
1.3.12 Specific Requirements

This section contains the software requirements to a level of
detail sufficient to enable designers to design the system, and
testers to test the system.
1.3.13 User Characteristics
1. Educational Level: At least graduate and should be comfortable
with English language.
2. Technical Expertise: Should be a high or middle level employee
of the organization comfortable with using general purpose
applications on a computer
1.3.14 Product functions
The system will allow access only to authorized users with specific
roles (Administrator, Operator). Depending upon the user‟s role,
he/she will be able to access only specific modules of the system.
A summary of the major functions that the software will perform:
(i) A Login facility for enabling only authorized access to the
system.
(ii) Users (with role operator) will add/update/delete the stored
information and so on
1.3.15 System Features
1.3.15.1 Module name
Description
One paragraph in brief about module
Validity Checks
Sequencing Information
Error Handling / Response to abnormal situations
1.3.16 Performance Requirement
None
1.3.17 Logical Database Requirements
The proposed information system contains the following data

tables in its database collection.
Table name
1.3.18 Design Constraints
Standard Compliance
None
1.3.19 Software System Attributes
1.3.19.1 Reliability
This application is a reliable product that produces fast and
verified output of all its processes.
1.3.19.2 Availability
This application will be available to use for your end users
and help them to carry out their operations conveniently.
1.3.19.3 Security
The application will be password protected. User will
haveto enter correct username, password and role in order
to access the application.
1.3.19.4 Maintainability
The application will be designed in a maintainable manner.
It will be easy to incorporate new requirements in the
individual modules.
1.3.19.5 Portability
The application will be easily portable on any windows-
based system that has oracle installed.
1.3.20 Other Requirement
None
1.4 System Planning (PERT Chart)
Chapter 2: System Design

2.1 Physical Design- about your system
2.1.1 Block Diagram- about block diagram followed by properly
labeleddiagram
2.1.2 Processes- All the processes along with their subprocessess
2.1.3 Input and Output of processes
No. Process Input Output
2.1.4 Use case diagram

2.1.5 Data Flow Diagrams
2.1.6 Entity Relationship Diagram
2.2 Database Design
The information system of “your title” performs its function with
the help of the data store in certain repositories called Databases
of the system. Detailed descriptions of the various databases
included in the information systems are tabulated as follows:
Accredited
ed ‘A’ Grade by NAAC & Recognised U/s 2(f) of UGC act
2.2.1 Login database

2.2.2 Schema of each table properly labeled
2.3 Data Dictionary
2.3.1 A data dictionary is metadata repository or a centralized
ce
repository of information about data such as meaning,
relationships to other data, origin, usage and format. The
term may have one of several closely related meaning
pertaining to databases and database management
systems (DBMS):A document describing bing a database or
collection of databases. An integral component of
DBMS that is required to determine itsstructure. A piece
of middleware that extends or supplants the native data
dictionary of a DBMS.
TABLE NAME
COLUMN FIELD SIZE PRIMARY NULL DESCRIPTION
NAME TYPE KEY
2.4 Interface Design

The interface design consists of the input and output source layouts.
i.e. the input forms and screens and the report layouts that form as a
source of outcome and income in the design and implementation of the
information
rmation system under study
2.4.1 Input Design
The input specifications of the existing information
system includethe illustration of the detailed
characteristics of contents included in each Input
Screen and documents. The description for each
graphical user interface
erface has been mentioned.
EXISTING SYSTEM DESIGN (Graphical
User Interface) 1. Main Form Snap shot of
your main screenDescription and so on
2.4.2 Output Design
The output specifications of the existing
information system include the detailed
characteristics of contents included in each Report.
The description for each Visual Basic Output
Report hasbeen mentioned.
2.4.2.1 Report 1
Snap shot of your
report properly
labelled Description
File Linked to: name of the table and so on
Chapter-3 SYSTEM DESIGN

3.1 ERD, DFD
3.2 Input and Output Screen Design
3.3 Process involved
3.4 Testing & Debugging(Types of testing(white box, black
box, acceptance, alpha-beta testing, Validation testing)
Chapter-4 Coding and Screenshots of the project
4.1 Coding
4.2 Screenshots of the project
Chapter-5 Conclusion, Future Scope and References
5.1 Conclusion
5.2 Future Scope
\
References/Bibliography (as per format) refer Annexure-IV
Annexure-IV
LIST OF TABLES
Table No Description Page No
3.1 Employee‟s Personnel Information 18
3.2 PurchaseInformation 20
3.3 StockInformation 22
3.4 MasterTable 26
LIST OF FIGURES
Figure No Description Page No

1.1 Organizational Chart 5
3.1 DataEntryScreen forPurchase 21
4.1
LIST OF ABBREVIATIONS
Abbreviation Description
CAD Context Analysis Diagram
DFD Data Flow Diagram
HIPO Hierarchical Input Process Output
References/Bibliography:
1. PattersonDW,“IntroductiontoArtificialIntelligenceandExpertSystems”,SecondEdition,2
002,PrenticeHall ofIndia Private Ltd.,New Delhi.
2. V.Rajaraman,“AnIntroductiontoDigitalComputerDesign”,ThirdEdition,1995,PrenticeH
allofIndia PrivateLtd., New Delhi.
Note: All of the above three will be prepared on separate pages.

Accredited ‘A’ G
Grade
rade by NAAC & Recognised U/s 2(f) of UGC act
Template for back-quote

Guidelines for Data Analytics Using Python Major Project
Minor Project Topic Summary

Synopsis
1. Name / title of the project,
2. Statement about the problem
3. Significance of the Project (It must address Present State of the Art.)
4. Objective
5. Scope
6. H/W& S/W Specification
7. Data Collection and Methodology
8. Algorithm
9. Limitations / constraints of the project,
10. Conclusion, Future Scope for Modification,
11. References/Bibliography
CONTENTS
ABSTRACT
LIST OF FIGURES
LIST OF TABLES
LIST OF ABBREVATIONS
SYNOPSIS
CHAPTER -1 INTRODUCTION
1.1 Description of the topic: (Introduction the project's background and context.)
1.2 Problem Statement :( State the problem in a clear and concise manner. A problem
statement is a short, clear Explanation of an issue or challenge)
1.3 Objectives
1.4 Scope of the Project: (Cover the functionality and performance of the project)
1.5 Project planning Activities
1.5.1 Team-Member wise work distribution table
1.5.2 PERT Chart
1.6 Organization of the report
CHAPTER 2 – LITERATURE REVIEW
(Summary of Paper Studied (Discuss relevant theories, concepts, and previous work
related to your project. And integrate a Literature review of at least 8 research papers of
the related studies in a table)
Title of Research Paper Author/Author(s) detail with year Findings
CHAPTER 3 – SYSTEM DESIGN AND METHODOLOGY

3.1 System Design: (Explain the system architecture in detail)
3.2 Algorithm Used (Describe in detail the algorithm you are using to address this
problem)
CHAPTER 4 – IMPLEMENTATION & RESULT

4.1 Hardware and Software Requirement:
4.2 Implementation Details: (Description of all modules in detail)
4.3 Results: (Use visualizations, tables, and graphs to illustrate your findings effectively.)
CHAPTER 5 – CONCLUSION AND FUTURE WORK
5.1 Conclusion: (Performance Evaluation in terms of various performance metrices.)
5.2 Future Scope: (Address the limitations of your project work. For each shortcoming,
Propose additions or enhancements that would help overcome it.)
REFERENCES
ANNEXURES (Code must be annexed)
Guidelines for IoT Minor Project

Minor Project Topic Summary
(IoT)
SYNOPSIS
1. Title of Project
2. Problems with the Existing System
(Note: Consider the previously existing project as Manual)
3. Related Work: (Review at least seven research papers related to thefield of
study)
4. Description of the Proposed System
5. Tools/Platform
6. Future Scope
CHAPTER 1- Introduction
1.1 Objectives and Motivation of Project

1.2 Organization of the report
1.3 Tools/Platforms
1.3.1 Hardware Specification tools
1.3.2 Software Specification Tools
1.3.3 Any additional hardware and software requirement along with the versions can
be included.
1.4 Description of Proposed System

1.5 Project planning Activities
1.5.1 Team-Member wise work distribution table
1.5.2 Gantt Chart
Chapter 2 – Literature Review

2.1 Summary of Paper Studies
2.2 Integrated summary of the Literature studied.
Chapter 3: System Overview & System Hardware

3. 1 System Overview
3.2 Block Diagram
3.3 Hardware Tool

3.4 System Hardware
3.4.1 Raspberry pi/Arduino uno
3.4.2Proposed System Module Description
3.4.3 Circuit Diagram
3.4.4 Pin Diagram
3.4.5 Hardware Description (In detail: Include Features, Specifications)
Chapter: 4 System Software & Result

4.1 Description of System Software
4.2 Flow Chart
4.3 IoT: IDE description (respective to proposed system example: Android, Raspbian)
4.4 Steps involved in: Title of Project (i.e. working of Proposed System)
4.5 Program Code
4.6 Results: Snapshots: input and output modules.
Chapter 5: Challenges, Future Scope & Conclusion

5.1 Challenges
5.2 Limitations
5.3 Applications
5.4 Future Scope
5.5 Conclusion
References
ANNEXURES

Minor Project Report Format

Uploaded by

Minor Project Report Format

Uploaded by

INSTITUTE OF INFORMATION TECHNOLOGY & MANAGEMENT

INSTITUTE OF INFORMATION TECHNOLOGY & MANAGEMENT, NEW DELHI

Date: September 25, 2024

Minor Project Guidelines for BCA-V semester

CO # Detailed Statement of the CO BT Level Mapping to PO #

CO1 An ability to understand the principles and BTL2 PO1,PO3,PO4,PO5,

University Scheme for Summer Training & Project

(a) External : Project (60 Marks), where a written report is to be submitted. It

NOTE: ANY PREVIOUS WORK OR BORROWED REPORT WILL BE SUMMARILY

Format & Final Report

GENERAL GUIDELINES FOR THE PROJECT WORK

FORMAT OF THE PROJECT REPORT

FORMAT OF THE STUDENT PROJECT REPORT ON COMPLETION OF THE PROJECT

FORMAT OF PROJECT REPORT

I. Cover Page as per format

1.1 Objective & Scope of the Project

Chapter-3 SYSTEM DESIGN

The format of the title page is attached as Annexure-I.

TEMPLATE FOR CHAPTER SCHEME

FORMAT OF LIST OF TABLES AND FIGURES

The format of list of Tables/Figures/Abbreviation and References/Bibliography is attached as

6. Page Specification: (Written paper and source code)

Title of the Project Report

Submitted in partial fulfillment of the requirements

for the award of the degree of

Bachelor of Computer Applications

Guru Gobind Singh Indraprastha University, Delhi

Guide: Submitted by:

Institute of Information Technology & Management,

Signature of the Student 1

Signature of the Guide:

Countersign HOD Countersign Director

This is to certify that the dissertation/project report entitled “…………………………………” is

Signature of the student

(Font size -18)

1.3.1 Introduction – A single paragraph about SRS

The following subsections of Software Requirement Specifications Document should

1.3.3 Scope – scope of your proposed system

Front End Client

Interaction of Product with the

Assumptions and Dependencies – The application is developed on the following assumptions.

1.3.8 System Interfaces None

1.3.9 User Interfaces

1.3.12 Specific Requirements

The proposed information system contains the following data

Chapter 2: System Design

No. Process Input Output

2.1.4 Use case diagram

2.2.1 Login database

2.4 Interface Design

Chapter-3 SYSTEM DESIGN

Figure No Description Page No

Note: All of the above three will be prepared on separate pages.

Template for back-quote

Guidelines for Data Analytics Using Python Major Project

Minor Project Topic Summary

Title of Research Paper Author/Author(s) detail with year Findings

CHAPTER 3 – SYSTEM DESIGN AND METHODOLOGY

CHAPTER 4 – IMPLEMENTATION & RESULT

Guidelines for IoT Minor Project

1.1 Objectives and Motivation of Project

1.4 Description of Proposed System

Chapter 2 – Literature Review

Chapter 3: System Overview & System Hardware

3.3 Hardware Tool

Chapter: 4 System Software & Result

Chapter 5: Challenges, Future Scope & Conclusion

You might also like