ACKNOWLEDGEMENTS

We have taken efforts in this project. However, it would not have been possible without
the kind support and help of many individuals and organizations. We would like to extend
our sincere thanks to all of them. We are highly indebted to Dr. Rachna Patel for their
guidance and constant supervision as well as for providing necessary information
regarding the project & also for their support in completing the project. We would like to
express my gratitude towards our parents & members for their kind co-operation and
encouragement which help us in completion of this project. We would like to express our
special gratitude and thanks to industry persons for giving us such attention and time. Our
thanks and appreciations also go to our colleague in developing the project and people
who have willingly helped us out with their abilities.

Mamta Patel (201303100910029)

Stephanie Noronha (201303100910039)
Nidhi Patel (201303100910059)

CGPIT/ CE_10 i
 ABSTRACT

The Free world system is to create an e-Information about the donor and organization
that are related to donating the useful things. Through this application any person who is
interested in donating their thing(such as any electronic item,clothes ,any stationary item
or anyother things) can register himself in the same way if any organization wants to
register itself with this site that can also register. Moreover if any general consumer
wants to make request of things they need online he can also take the help of this site. The
application takes care of different modules and their associated reports, which are
produced as per the applicable strategies and standards that are put forwarded by the
administrative staff.

CGPIT/ CE_10 ii
 Table of Contents
Acknowledgements...............................................................................................................i

Abstract................................................................................................................................ii

List of Figures......................................................................................................................v

List of Tables......................................................................................................................vi

Chapter 1 Introduction....................................................................................................1

1.1 Background............................................................................................................1

1.2 Problem Definition................................................................................................1

1.3 Motivation.............................................................................................................1

1.4 Scope/Application.................................................................................................1

Chapter 2 System Planning.............................................................................................2

2.1 Project Development Approach.............................................................................2

2.2 System Modules....................................................................................................3

2.3 Functional Requirements.......................................................................................3

2.4 Non Functional Requirements...............................................................................5

2.5 Hardware and software Requirements...................................................................5

2.6 Timeline Chart.......................................................................................................6

Chapter 3 System Design................................................................................................7

3.1 Use Case Diagram.................................................................................................7

3.2 Sequence Diagram.................................................................................................7

3.3 Activity Diagram...................................................................................................8

3.4 Class Diagram.......................................................................................................9

3.5 Database Schema.................................................................................................11

3.6 Data Flow Diagram.............................................................................................13

Chapter 4 Implementation and Testing.........................................................................16

4.1 Snapshots.............................................................................................................16

CGPIT/ CE_10 iii

 4.2 Test Cases............................................................................................................24

Chapter 5 Conclusion and Future Scope.......................................................................26

CGPIT/ CE_10 iv
 LIST OF FIGURES
Figure 2-1 Sample timeline chart.........................................................................................6
Figure 4-1 Home Page.......................................................................................................16
Figure 4-2 Registration Page
Figure 4-3 Login-1 Page
Figure 4-4 Login-2 Page
Figure 4-5 Item Form-1 Page
Figure 4-6 Item Form-2 Page
Figure 4-7 Item Form-3 Page
Figure 4-8 Category-1 Page
Figure 4-9 Category-2 Page
Figure 4-10 Upload Post-1 Page
Figure 4-11 Upload Post-2 Page
Figure 4-12 Display Post-1 Page
Figure 4-13 Display Post-2 Page
Figure 4-14 Event Form Page
Figure 4-15 Display Event Page

CGPIT/ CE_10 v
LIST OF TABLES
Table 3.1 Login Table………………………………………………………………….11
Table 3.2 Register Tab………………………………………………………………….11

Table 3.3 Post Table

…………………………………………………………………….12

Table 3.4 Event Table ……………………………………………………………………12

Table 3.5 Item Table

…………………………………………………………………….12

CGPIT/ CE_10 vi
 Free world

CHAPTER 1 INTRODUCTION

1.1 Background

This document aims to give a brief description about the Free World System Project.
With the help of this document the needs of the user and the solution that will be provided
to that needs will be clearly presented. The Free world application is to create an e-
Information about the donor and organization that are related to donating some of their
useful need which is not needed to them but needed by others. Through this application
any person who is interested in donating their things can register himself in the same way
if any organization wants to register itself with this application that can also register. The
foundations who have registered themselves in this application can also post the event
that they organise and the people willing to help as a volunteer can contact those
foundations.

1.2 Problem Definition

People should help the needy so that their needs also gets satisfied and we can also
promote humanity. For this purpose various things that are not useful to the the user can
donate to the needy so that they can get help. This paper proposes the Free world System
using Android which can be used to donate things to the needy through any of the
foundation.

1.3 Motivation/ Objective

The software is needed to be develop to spread humanity in this world so that we can
create a bond within each other so that there are no discrimination between each other.

1.4 Scope/Application
The software is needed to be develop to spread humanity in this world so that we can
create a bond within each other so that there are no discrimination between each other.

CGPIT/ CE_10 1
 Free world

CHAPTER 2 SYSTEM PLANNING

2.1 Project Development Approach

Each project need to be developed with software model which makes the project with
high quality, reliable and cost effective.

 Iterative Waterfall model

 This application follows Iterative waterfall model. In this firstly simple
implementation is done of small set of software requirements and slowly the
complete system is implemented. At each iteration the design modification can be
made and new functional capabilities can be added.
 We have selected this model because Iterative process starts with a simple
implementation of a subset of the software requirements and iteratively enhances
the evolving versions until the full system is implemented. At each iteration,
design modifications are made and new functional capabilities are added. The
basic idea behind this method is to develop a system through repeated cycles
(iterative) and in smaller portions at a time (incremental).
 Advantages of your software model:
1. Some working functionality can be developed quickly and early in the life cycle.
2. Results are obtained early and periodically.
3. Parallel development can be planned.
4. Progress can be measured.
5. Less costly to change the scope/requirements.
6. Testing and debugging during smaller iteration is easy.
7. Risks are identified and resolved during iteration; and each iteration is an easily
managed milestone.
8. Easier to manage risk - High risk part is done first.
9. With every increment operational product is delivered.
10. Issues, challenges & risks identified from each increment can be utilized/applied
to the next increment.
11. Risk analysis is better.
12. It supports changing requirements.
13. Initial Operating time is less.

CGPIT/ CE_10 2
 Free world

14. Better suited for large and mission-critical projects.

15. During life cycle software is produced early which facilitates customer evaluation
and feedback.

2.2 System Modules

Here are some modules that we have use in this project:

2.2.1 Admin
Admin can add, modify and delete various post and events and other items displayed in
the project.

2.2.2 User
User can upload photos of things that they need to donate and also upload post the things
that promote humanity.

2.2.3 Post
User can also upload post the things that promote humanity.

2.2.4 Upload things to donate

User can upload photos of things that they need to donate to help other people.

2.2.5 Event management

Other Institutes who had register which organize events also upload events so that people
can know about the events and can help other people thrgh events.

2.3 Functional Requirements

-This section provides requirements overview of project. This project will be required
Android and PHP as a frontend and the backend SQLite database will be running.

ID Title & Description

FR1 Title: User registration/Institute registration

Desc: User/Institute can register themselves to use this application.

FR2 Title: User Login/Institute Login

CGPIT/ CE_10 3
 Free world

Desc: User/Institute should be able to login through application. The user/Institute must
provide user-name and password.

FR3 Title: Upload things to donate

Desc: User can upload the useful things to donate to the needy.

FR4 Title: User can exchange the things with the Institute :

Desc: User can get the things needed from this application to donate to needy.

FR5 Title: GPS Tracker:

Desc: Through GPS tracker the user can find nearest Institute who supports humanity and
helps the people and so the user can donate things to that institute.

FR6 Title: Upload photos who so ever does good work.

Desc: User can upload photos if the user finds someone is doing some work to promote
humanity.

FR7 Title: Search Products

Desc: User can search any products they need to donate.

FR8 Title: Alerts and notification

CGPIT/ CE_10 4
 Free world

Desc: User can get notified that their things have been successfully reached to an institute
by checking the status of their donated things.

FR9 Title: Can serve as a volunteer

Desc: User can also serve as a volunteer by registering themselves as a volunteer and
adding their details for how much time they can serve to help the needy.

FR1
0 Title: Can help in any events organized by the institute

Desc: User can who has registered as a volunteer or any user who is willing to help the
institute for any event organized by the institute can join the event by notifying the
institute that they want to help.

2.4 Non Functional Requirements

Portability: This application should be portable on any windows based system and
any android versions.

Security: The person who has user-name and password can only access their own
account.

Performance: This application should require highly internet connection.

Reliability: The application should be highly reliable and it should generate all the
updated information in correct order.

Serviceability: The user can donate things to the needy.

2.5 Hardware and software Requirements

 Hardware Requirements:

CGPIT/ CE_10 5
 Free world

1. Hardisk-300GB
2. RAM-4GB
 Software Requirements:
1. Front-end-Java language
2. OS-Windows 7
3. Back-end-SQLITE database (local database)

2.6 Timeline Chart

Requirements 15
gathering days 6/25 -
7/21
35 7/5 -
Design
days 8/8

45 7/30 -
Coding days 9/12

Testing 47 8/20 -
days 10/5

Deployment 48 8/29 -
days 10/15

22 10/15 -
Maintenance 11/5
days

2016
2016 Aug Sept Oct Nov Dec

Figure 2-1 Sample timeline chart

CGPIT/ CE_10 6
 Free world

CHAPTER 3 SYSTEM DESIGN

3.1 Use Case Diagram

Use case diagrams are used to gather the requirements of a system including internal and
external influences. These requirements are mostly design requirements. So when a
system is analyzed to gather its functionalities use cases are prepared and actors are
identified.

CGPIT/ CE_10 7
 Free world

3.2 Sequence Diagram

Describe the flow of messages, events, actions between objects. Show concurrent
processes and activations. Show time sequences that are not easily depicted in other
diagrams. Typically used during analysis and design to document and understand the
logical flow of your system.

3.3 Activity Diagram

The basic purposes of activity diagrams are similar to other four diagrams. It captures
the dynamic behaviour of the system. Other four diagrams are used to show the message
flow from one object to another but activity diagram is used to show message flow from
one activity to another. Activity is a particular operation of the system. Activity
diagrams are not only used for visualizing dynamic nature of a system but they are also
used to construct the executable system by using forward and reverse engineering
techniques. The only missing thing in activity diagram is the message part.

CGPIT/ CE_10 8
 Free world

3.4 Class Diagram

The class diagram is a static diagram. It represents the static view of an application.
Class diagram is not only used for visualizing, describing and documenting different
aspects of a system but also for constructing executable code of the software application.
The class diagram describes the attributes and operations of a class and also the
constraints imposed on the system. The class diagrams are widely used in the modelling
of object oriented systems because they are the only UML diagrams which can be
mapped directly with object oriented languages.

CGPIT/ CE_10 9
 Free world

CGPIT/ CE_10 10
 Free world

3.5 Database Schema

List out all the tables thatwe have used in our project.
Table 3.1 Login Table

Column Name Data Type Size Constraint Description

Id INT 5 Primary Key ID No.

User VARCHAR 50 --- Username

Pass VARCHAR 50 --- Password

Table 3.2 Register Table

Column Name Data Type Size Constraint Description

Id INT 5 Primary Key ID No.

First_name VARCHAR 50 --- Username

Last_name VARCHAR 50 --- Password

Address VARCHAR 200 --- Address

Username VARCHAR 200 Foreign Key Username

Password VARCHAR 200 --- Password

Confirm_Pass VARCHAR 200 --- Confirm_Password

Mobile_no. INT 200 --- Mobile_no.

Location VARCHAR 200 --- Location

Choice VARCHAR 200 --- Choice

CGPIT/ CE_10 11
 Free world

Table 3.3 Post Table

Column Name Data Type Size Constraint Description

Id INT 5 Primary Key ID No.

Title VARCHAR 500 --- Title

Description VARCHAR 500 --- Description

Image path VARCHAR 500 --- Image path

Table 3.4 Event Table

Column Name Data Type Size Constraint Description

Id INT 5 Primary Key ID No.

Institute_name VARCHAR 500 --- Institute_name

Title VARCHAR 500 --- Title

Description VARCHAR 200 --- Description

No_of_volunteers INT 200 --- No_of_volunteers

Event_time VARCHAR 200 --- Event_time

Event_place VARCHAR 200 --- Event_place

Event_date INT 200 --- Mobile_no.

Table 3.5 Item Table

Column Name Data Type Size Constraint Description

Id INT 5 Primary Key ID No.

App_name VARCHAR 50 --- Applicant_name

CGPIT/ CE_10 12
 Free world

Title VARCHAR 50 --- Title

Description VARCHAR 200 --- Description

Image_path VARCHAR 200 --- Image_path

3.6 Data Flow Diagram

A data flow diagram (DFD) is a graphical representation of the "flow" of data through
an information system, modelling its process aspects. A DFD is often used as a
preliminary step to create an overview of the system, which can later be elaborated.
[2]
DFDs can also be used for the visualization of data processing (structured design). A
DFD shows what kind of information will be input to and output from the system, where
the data will come from and go to, and where the data will be stored. It does not show
information about the timing of process or information about whether processes will
operate in sequence or in parallel (which is shown on a flowchart).
 DFD level 0:

 DFD Level 1:

CGPIT/ CE_10 13
 Free world

 DFD Level 2.0

 DFD Level 2 for 3.0

 DFD level 2 for 4.0

CGPIT/ CE_10 14
 Free world

 DFD level 2 for 5.0

CGPIT/ CE_10 15
 Free world

CHAPTER 4 IMPLEMENTATION AND TESTING

4.1 Snapshots
 Home Page

Figure 4-2 Home Page

 Registration Page

CGPIT/ CE_10 16
 Free world

Figure 4-2 Registration Page

Title: User registration/Institute registration:

Desc: User/Any Institute should be able to register through application. The user/Institue
must provide user-name, password and email-address and other information of their own.

 Login Page

Figure 4-3 Login Page

CGPIT/ CE_10 17
 Free world

Figure 4-4 Home Page

Title: User Login/Institute Login

Desc: User/Institute should be able to login through application. The user/Institute must
provide user-name and password.

 Item form Page

Figure 4-5 Item form Page

CGPIT/ CE_10 18
 Free world

Figure 4-6 Item form Page

Figure 4-7 Item form Page

Title: Item Form:

Desc: User can upload things to donate.

CGPIT/ CE_10 19
 Free world

 Category Page

Figure 4-8 Category Page

Figure 4-9 Category Page

CGPIT/ CE_10 20
 Free world

Title: Upload things to donate:

Desc: User can upload the useful things to donate to the needy.

 Upload Post Page

Figure 4-10 Upload Post Page

Figure 4-11 Upload Post Page

CGPIT/ CE_10 21
 Free world

Title: Upload photos who so ever does good work.

Desc: User can upload photos if the user finds someone is doing some work to promote
humanity.

 Display Post Page

Figure 4-12 Display Post Page

Figure 4-13 Display Post Page

CGPIT/ CE_10 22
 Free world

Title: Upload photos who so ever does good work.

Desc: User can upload photos if the user finds someone is doing some work to promote
humanity.

 Event Form Page

Figure 4-14 Event form Page

Title: Can serve as a volunteer.

Desc: User can also serve as a volunteer by registering themselves as a volunteer and
adding their details for how much time they can serve to help the needy.

 Display Event Page

CGPIT/ CE_10 23
 Free world

Figure 4-15 Display Event Page

Title: Can serve as a volunteer.

Desc: User can also serve as a volunteer by registering themselves as a volunteer and
adding their details for how much time they can serve to help the needy.

4.2 Test Cases

Sample test cases are given as below:

Test ID Case Test Data Expected Result Actual Result Pass/Fail

1 Login - Internet If Login ID & If Login ID & Pass

Connectivity password is empty or password is
- Login ID invalid and No Internet empty or invalid
- Password connectivity then and No Internet
dispay Error message connectivity then
otherwise dispay Error
Login sucessfully message.
2 Home Swipe down First time First time Pass
(Networth) For Synchronization Synchronized.
Synchronization When swipe down, When swipe
Networth report will down,
refresh. Networth report

CGPIT/ CE_10 24
 Free world

refreshed.
3 Reports Select given Display report as per Report displayed Pass
inputs for selection of inputs. as per selection
particular of inputs.
reports.
4 Forgot Email Id If Email Id is valid Password is reset Pass
password &Authorized then new if the Email id is
password is set by authorized and
received email. valid.

5 Logout Select Logout User should Logout of User get Logout Pass
the application and of the application
redirected to Login and redirected to
page. Login page.
6 Exit Select Exit Application should be Application is Pass
closed. closed.

CGPIT/ CE_10 25
 Free world

CHAPTER 5 CONCLUSION AND FUTURE SCOPE

The proposed system uses GPS and Web Technology in order to enhance the positioning
experience. The Free world system effectively helps the user about to help the needy
person through some institute. The user can server as a volunteer, can post or also upload
things that he/ she needs to donate to the needy. As a future work, the proposed system
can be implemented to help the needy with the help of the social networking
websites such as Facebook, Twitter etc.

CGPIT/ CE_10 26
 Free world

CGPIT/ CE_10 27