A Project on “……Project Name……..

Submitted for the partial fulfillment of the Degree of Bachelor of

Computer Application under MaulanaAbulKalam Azad
University of Technology, West Bengal.
 A Project on “……Project Name……..”

Project Related Diagram

(if needed)

Submitted by …………Student Name………

SWAMI VIVEKANANDA INSTITUTE OF MODERN SCIENCE

Kolkata, West Bengal

 SWAMI VIVEKANANDA INSTITUTE OF MODERN SCIENCE

Kolkata, West Bengal

Student Name:

Roll Number:

Registration No. Year

Department: Computer Application

Course: Bachelor of Computer Application

Session:

Paper Name:

Paper Code:

College Code: 264

University Name: Maulana Abul Kalam Azad University of

Technology
 SWAMI VIVEKANANDA INSTITUTE
OF
MODERN SCIENCE

Affiliated to Maulana Abul Kalam Azad University of Technology, WB

Sonarpur Station Road, Karbala, P.O. - Narendrapur, P.S. - Sonarpur, Kolkata-700103

TO WHOM IT MAY CONCERN

This is to certify that the project entitled “E-CHATTING APPLICATION” with

reference to Swami Vivekananda Institute of Modern Science, Sonarpur, Kolkata-
700103 is submitted by SAYANTAN SARKAR[3rd year, 2nd semester, registration
no. 202641001210035 year 2020-21, roll no. 26401220033] under the Department
of Computer Application for thepartial fulfilment of the degree of BCA, under
Maulana Abul Kalam Azad University of Technology, WB, embodies the work
has been done by him under our supervision.

................................... ...................................
Prof. Gargi Gupta Dr. Meghdoot Ghosh
(Vice-Principal) (Principal)
SVIMS SVIMS

.................................................. ...................................................

Prof.(Dr.) Ambalika Ghosh Prof.(Dr.) Ambalika Ghosh

(Internal Project Guide) (Head of The Department)
Department of Computer Application Department of Computer Application
SVIMS SVIMS

Date:
Place: Kolkata
 DECLARATION

I declare that this written submission represents my ideas in my own words and where others’
ideas or words have been included, I have adequately cited and referenced the original sources. I
also declare that I have adhered to all principles of academic honesty and integrity and have not
misrepresented or fabricated or falsified any idea/data/fact/source in my submission. I understand
that any violation of the above will cause for disciplinary action by the Institute and can also
evoke penal action from the sources which have thus not been properly cited or from whom
proper permission has not been taken when needed.

Place: with sincere regards

Date: student Name

 ACKNOWLEDGEMENT
I think this is an opportunity to thank all the individuals without their help in this project have
been incomplete.
I would like to thank "Dr. NANDAN GUPTA", Director of Swami Vivekananda Institute of
Modern Science and "Dr. MEGHDOOT GHOSH", Principal of Swami Vivekananda Institute
of Modern Science and "Prof. GARGI GUPTA", Vice- Principal of Swami Vivekananda
Institute of Modern Science, Karbala More, Sonarpur Station Road, Kolkata-700103.
I would also like to thank “Prof. Dr. AMBALIKA GHOSH”, Head of the Department of
Computer Application and Science
My profound gratitude goes to “Prof. Dr. AMBALIKA GHOSH”, Assistant Professor,
Department of Computer Application & Science, as our internal guide. I would also express my
sincere thanks to the persons who are helpful in explaining about domain information of the
existing system.
I am thankful to all the FACULTY MEMBERS and Lab Assistant of Department of Computer
Application & Science, also the rest of the FACULTY MEMBERS of Swami Vivekananda
Institute of Modern Science.
I am grateful to my PARENTS and FRIENDS for supporting me directly and indirectly during
the project.
Finally, I would like to mention here that I am indebted to each and everybody who have been
associated with my project at any stage but whose name doesn't find a place in this
acknowledgment.
WZ

Date:…………………………
…………………………
With sincere
Student Name
 Table of Content

Sl. No Topic Page Number

1 Introduction 1
 Abstract
whole description of the project (Minimum 2 Pages)
 Introduction 1|P a g e
General introduction as well as topic specific introduction of the project.
Start page numbering from here
(5-10 pages)
 Literature Review 2|P a g e
Name of the author with topic name, year along abstract of the work (5-10 pages)
 3|P a g e

Body
-Start with purpose or objective of doing this project.
-Dealing with details of the topic:
Eg. Topic is Library Management System
-Then it should come topic like:
What is Library Management system, Purpose, Technology used, Front end, Back end,
Dashboard Panel, Log in details etc.
-It must have heading and subheading
-It must include 60 pages

For Science student body must have

-Objective of experiment
-Materials required
-Instruments required
-Procedure
 4|P a g e

Discussions
-It must include chart, graphs, tables, bar graphs with explanation
For science students:
-Minimum 10 pages
-Result of the experiments
-Discussion of the result
-tables, chart, graph with explanation
 5|P a g e

Case Studies
Problems and solutions (5-10 pages)
Eg:
Test Objective:
The objective our test plan is to find and report as many bugs as possible to improve the integrity
of our program. Although exhaustive testing is not possible, we will exercise a broad range of
tests to achieve our goal. We will be testing a Binary Search Tree Application utilizing a pre-
order traversal format. There will be eight key functions used to manage our application: load,
store, clear, search, insert, delete, list in ascending order, and list in descending order. Our user
interface to utilize these functions is designed to be user-friendly and provide easy manipulation
of the free. The application will only be used as a demonstration tool, but we would like to
ensure that it could be run from a variety of platforms with little impact on preformation or
usability.
Process Overview:
The following represents the overall flow of the testing process:
1.Identify the requirement to be tested. All test cases shall be derived using the current Program
Specification.
2.Identify which particular test will be used to test each model.
3.Identify the expected results for each test.
4.Document the test data, test cases, and test configuration used during the testing process. This
information shall be submitted via the Unit/System Test Report(STR)
5.Perform the test.
6.Successful unit testing is required before the unit is eligible for component integration/System
testing.
7.Unsuccessful testing requires a Bug Report Form to be generated. This document shall
describe the test case, the problem encountered, its possible cause, and the sequence of events
that led to the problem. It shall be used as a basis for later technical analysis.
8.Test documents and reports shall be submitted. Any specification to be reviewed, received or
updated shall be handled immediately.
UNIT TESTING
Testing is done at the source code level for language specific programming errors such as bad
syntax, logic errors or to test particular functions or code modules. The unit test cases shall be
designed to test the validity of the programs correctness.
Unit testing has the greatest effect in the quality of our code when it's an integral part of our
software development worth flow. In our project we used this testing by ensuring whether the
output is correct with respect to the output.
ALPHA TESTING
This is a form of internal acceptance testing performed mainly by the in-house software QA and
testing teams. Alpha testing is the last testing done by the test teams at the development site after
the acceptance testing and before releasing the software for beta test.
Alpha testing can also be done by the potential users or customers of the application. But still,
this is a form of in-house acceptance testing.
 6|P a g e

BETA TESTING
This is a testing stage followed by the internal full alpha test cycle. This is the final testing phase
where the companies release the software to few external user groups outside the company test
teams or employees. This initial software version is known as the beta version. Most companies
gather user feedback in this release.
In short, beta testing can be defined as— the testing carried out by real users in a real
environment.
WHITE BOX TESTING
In White box testing the UI is by passed, inputs and outputs are tested directly at the code
level and the results are compared against specifications. This form of testing ignores the
function of the program under test and will focus only on its code and the structure of that code .
 7|P a g e

Conclusion
-Future prospects
-Any updated features
-Software with aid in working condition
-Scope, helps to mankind
-Any counselling session
-Questionnaires
(Page limit 10 pages)
 8|P a g e

Picture Gallery
-A separate table of gallery content should be given after table of content
-Each Picture or diagram must have Fig. No/ Diagram No. name or explanation of the picture
Eg:

Diagram 1: System design for Library management system

 9|P a g e

Bibliography
-Author Name
-Book Name
-Publishing house
Eg:

Kadri F., Dairi A., Harrou F., Sun Y. Towards accurate prediction of patient length of stay at
emergency department: A GAN-driven deep learning framework. J. Ambient Intell. Humaniz.
Comput. 2022:1–15. doi: 10.1007/s12652-022-03717-z.
 10|P a g e
References
-Complete URL Address
(N.B.: No Google.com or Wikipedia.com)
Eg:

https://hbr.org/2012/03/spotify-a-digital-music-service-revolutionizes-how-people-listen-to-
music
https://www.forbes.com/sites/paultassi/2019/02/20/the-audio-streaming-
explosion/?sh=5a5d5d563b5b

https://www.juniperresearch.com/researchstore/forecasting-analysis/digital-music-revenue
 11|P a g e

General Information
1. Project should be minimum of 100 pages for UG and 100+ pages for PG. No questions to
be asked in the project. Indirect speech
2. Font size for heading -16
Sub heading-14
Main body-12
Font style-Times New Roman
3. Hard cover color may be black/blue/green/maroon
4. Page numbering should start from ….
Introduction…….pg1
Conclusion……..pg100
5. If any picture gallery given then separate page numbering should be done.
6. Project should contain colored pictures with name of the diagram & figure. Even
numbering can be done also.
7. Picture can be put either in between writings or can be put separately as PICTURE
GALLERY after conclusion.
8. If Tables, Chart, Graphs are used they also must have a name of table or graph
9. Proper explanation of Chart, Graphs, Table or Diagram is required.
10. Page numbering, Page bordering is must
11. Proper alignment of lines, paragraph or distance between lines, distance between
paragraphs should be maintained.
12. Emphasis should be given on formatting & justification. Whole page should be utilized
properly.