Declaration

We hereby declare that the project work entitled “Happy to Help” is an authentic record
of our own work carried out as requirements of Capstone Project for the award of B.Tech
degree in Computer Science and Engineering from Lovely Professional University,
Phagwara, under the guidance of Mr. Harjit Singh, during January to April 2019. All the
information furnished in this capstone project report is based on our own intensive work
and is genuine.

Project Group

Name of Student 1: MANINDER KAUR

Registration Number: 11607025

Name of Student 2: GURJOT KAUR

Registration Number: 11603065

Name of Student 3: SIMRANPREET KAUR

Registration Number: 11615288

Name of Student 4: TARANJOT

Registration Number: 11713748
 Certificate
This is to certify that the declaration statement made by this group of students is correct to the
best of my knowledge and belief. They will complete this project under my guidance and
supervision. The present work is the result of their original investigation, efforts and study. No
part of the work has been ever submitted for any other degree at any University. The Capstone
Project is fit for the submission and partial fulfilment of the conditions for the award of B. Tech
degree in Computer Science and Engineering from Lovely Professional University, Phagwara.

Signature and Name of Supervisor

Mr. Harjit Singh

Designation: Assistant Professor

School of Computer Science and Engineering

Lovely Professional University,
Phagwara, Punjab

Date: 25th April, 2019

 ACKNOWLEDGEMENT

We are sincerely thankful to all those people who have been giving us assistance in the
making of the project. We would like to acknowledge with thanks the kind of patronage,
loving inspiration and timely guidance, given by our course mentor Mr. Harjit Singh. And
we would also like to express our sincere thanks to all the faculties whose teachings
gave us conceptual understanding and clarity of comprehension, which ultimately made
the work of the project easier. Last but not the least we pay a deep sense of gratitude to
our family members and friends who have been constant source of inspiration and
support and their valuable advice for the preparation of this project.
INDEX

1. Introduction 5
1.1 Objectives of the Project 5
1.2 Project Description 5

2. System Description 6
2.1 Intended Audience 6
2.2 Assumption and Dependencies 6
2.3 Functional Requirements 7
2.4 Non-Functional Requirements 7

3. Design 10
3.1. Database Design 10
3.2. Data Flow Diagram 11
3.3. ER Diagram 12

4. Technology to Use 13

5. Other Requirements 14

6. Cost Estimation 15
1. INTRODUCTION
1.1Objectives of the Project
1. The website will act as a guide for the NGO's.
2. Providing NGO's with detailed dynamic list of products which the donators
want to give.
3. Providing options for donating things.
4. Providing NGO’s, a common platform to advertise their requirements.
5. Providing services to NGO's a dashboard to monitor various statistic related
to their services which we can providing to a NGO's.
1.2Project Description
Website that will act as intermediate between NGO’s and donators. This will
reflect things that will be required by NGO’s and donator can donate if they have
particular things to donate. There is no website for more than NGO’s and donators
can donate online to NGO’s with the help of website we’re planning to make.
This will help donators to know the need of NGO’s and vice-versa.
 2. SYSTEM DESCRIPTION
1. Intended Audience
i. Admins – Who will have full access to every data on the website.
ii. Customers – Who are the NGO owners and people who want to donate things
that they don’t require anymore both (NGO owners and people who want to
donate) has to register themselves and will provide authentic data to be displayed
on the website.
iii. Visitors – People who wants to make a donation.
2. Assumptions and Dependencies
i. Computerized system alone does not ensure accuracy, and the information on
the website is only as good as the data entry that created it.
ii. Since it is a website, it requires undisturbed internet connectivity.
iii. It is understood that the user is aware of handling the computer system and has a
basic knowledge of English Language.
iv. In terms of hardware interface, the system should be able to function on any
device with the working web browser that supports HTML5, CSS and JavaScript.
v. Limited to HTTP/HTTPS.
vi. No multilingual support.

3. Functional Requirements
i. Login :- Admins need to login to system by entering valid user id and password to
get full access of the website’s Admin Panel. Service owner’s login to the system
by entering valid user id and password to access their dashboard.
ii. Registration:- Service providers need to get themselves registered under their
service category to avail dashboard on the platform. Their after they need to
update their profile according to their business goals and target audience.
iii. Recover Password:- Admins and service owner need to enter correct combination
of codes from their secret grid provided at the time of registration or can later be
downloaded form profile section.
 iv. Logout:- Admins and service owners must logout in order to end their session so
as to maintain their privacy and account security.
v. Add donation:- To let Users to add things they wants to donate.
vi. View donation:-To let Users view things available so that NGO who wants it can
have it.
vii. Receive donation:-NGO can pick up donated things according to their
requirements.
viii. Statistics/Analytics:- This module will be integrated in the dashboard to translate
all the data available into easily understandable form or visualizations, wherefrom
various statistics will be derived and will be shown on user’s dashboard.
ix. Maintain Profile:- User Profile-This is the module to be used by service owners to
maintain their own profile that will be displayed to the visitors as contact
information. Business Profile-This is the module where service owners will add all
relevant details about the services they are offering. This module will take a
detailed input from the vendors to create the best and efficient search results.
According to the category of service that vendor selects, the layout, features,
options and entry fields of the dashboard will vary.

4. Non-Functional Requirements
i. Security
1. The system uses Hyper Text Transfer Protocol Secure (HTTPS) in
all transactions that include any confidential customer information.
2. The system must automatically log out all customers after a period of
inactivity.
3. The system should not leave any cookies on the customer’s computer
containing the user’s password.
4. Each time the user will sign in, a notification email will be sent on
registered email for security.
5. The system’s back-end servers shall only be accessible to authenticated
administrators.
 6. Sensitive data will be encrypted before being sent over insecure
connections like the internet.
ii. Reliability
1. The system provides storage of all databases on redundant computers with
automatic switchover.
2. The reliability of the overall program depends on the reliability of the
separate components. The main pillar of reliability of the system is the
backup of the database which is continuously maintained and updated to
reflect the most recent changes.
3. Thus, the overall stability of the system depends on the stability of
container and its underlying operating system.
iii. Availability
1. The system should be available at all times, meaning the user can access it
using a web browser, only restricted by the down time of the server on
which the system runs. In case of a of a hardware failure or database
corruption, a replacement page will be shown. Also in case of a hardware
failure or database corruption, backups of the database should be retrieved
from the server and saved by the administrator. Then the service will be
restarted. It means 24 X 7 availability.
iv. Maintainability
1. A commercial database is used for maintaining the database and the
application server takes care of the site. In case of a failure, a re-
initialization of the program will be done. Also, the software design is
being done with modularity in mind so that maintainability can be done
efficiently.
v. Portability
1. The application is HTML and scripting language based. So The end-user
part is fully portable and any system using any web browser should be able
to use the features of the system, including any hardware platform that is
available or will be available in the future.
2. An end-user is using this system on any OS; either it is Windows or Linux.
3. The system shall run on PC, Laptops, and PDA etc.
3. System Design
3.1 Database Design
3.2 DFD
3.3 ER Daigram
4. Technology to use

The web Website will be developed under two phases, the front-end
development and the backend development. Front-end technology
used are :

1. HTML 5

2. CSS 3

3. JavaScript

4. Bootstrap 4

Back-end technology used are :

1. PHP (Server Side Scripting)

2. MySQL database

3. Ajax
5.Other Requirements

When the system is completely developed and deployed, few

sessions will be required to make the users of the system understand
about the functionality of it and some time to adapt to the system.
After those sessions, it’s required that a member from the
development team should spend sometime in the system background
for some time period. That time period will be used in identifying
new bugs that could not be reached in the earlier phases of the
development process.
6. COST ESTIMATION
The project’s development involves no cost. It is a zero-budget
project while it is in development phase. All developments tools used
are easy to use and are available free of cost. The deployment phase
will cost around 1000-2000 INR for registering domain name and
availing online web hosting services form 3rd Party. After that an
annual cost of 400-1000 INR will be there for continuing hosing.