Smart Society System

(Android App and Web based)

By

Rehan
(BSCS-FA17-081)

Muhammad Umer Ijaz

(BSCS-FA17-070)

TANZEEM ASLAM
(BSSE-FA17-015)

KHUBAIB UR REHMAN
(BSSE-FA17-031)

Bachelor of Science in Computer Science

Bachelor of Science in Software Engineering

Department of Computational Science

The University of Faisalabad
 September 2015

DECLARATION

We hereby declare that the content of this project report entitled "Smart Society system Mobile
App and Web based" submitted to the "DEPARTMENT OF COMPUTATIONAL SCIENCES", is a record
of an original work done by us under the guidance of Supervisor "Name" and that no part has been
plagiarized (except the referenceces, some standard mathematical or genetic models / equestions /
protocols etc). Also, this project work is submitted in the partial fulfillment of the requirements for
the degree of Bachelor of Software Engineering. The univeristy may take action if the above
satatement found inaccurate at any stage.

Student Name Registration No. Signature

…………………….. ……………………… ………………………
…………………….. ……………………… ……………………….
…………………….. …………………….. ……………………..

Supervisor: Signature/Date

2
3
 Certificate

This is to certify that Tanzeem Aslam (BSSE-FA17-015), Khubaib ur Rehman (BSSE-FA17-031)

have worked on and completed their final year project of Bachelors of Science in Software
Engineering (BSSE) And Rehan (BSCS-FA17-081) & Muhammad Umer ijaz (BSCS-FA17-070)
have worked on and completed their final year project of Bachelors of Science in Computer
Science(BSCS) for Computer Science Department of The University of Faisalabad, as required by
their degree under my guidance and instructions. In our opinion, it is satisfactory and up to the mark
and therefore fulfills the requirements of Bachelors of Science in Computer Science
(BSCS),Software Engineering (BSSE).

Approved by . . . :

Supervisor: Name of the Supervisor (Title)

Internal Examiner: Name of the Internal Examiner (Title)

External Examiner: Name of the External Examiner (Title)

Project Coordinator: Name of the Project Coordinator (Title)

Head of the Department: Name of the HOD (Title)

4
July30st , 2021

5
 Acknowledgments

We hereby declare that the content of this project report entitled “ Smart Society Sytem Android App
and Web based” submitted to the “DEPARTMENT OF COMPUTER SCIENCES”, is a record of an
original work done by us under the guidance of Supervisor “Muhammad Zubair” and that no part has
been plagiarized (except the referenceces, some standard mathematical or genetic
models/equestions/protocols etc). Also, this project work is submitted in the partial fulfillment of the
requirements for the degree of Bachelor of Software Engineering. The univeristy may take action if
the above satatement found inaccurate at any stage.

Project Members Registration No. Signature

Rehan BSSE-FA16-049 ________________

Muhammad Umer Ijaz BSSE-FA16-049 ________________

Tanzeem Aslam BSSE-FA16-049 ________________

Khubaib ur Rehman BSSE-FA16-073 ________________

6
A UTHOR NAME
Islamabad, Pakistan September

2015

7
 Table of Contents

List of Figures………………………………………………………………………
List of Table………………………………………………………………………
Abstract……………………………………………………………………………..
1 Introduction1
1.1 Statement of the problem? . . . . . . . . . . . . . . . . . . . . . . . .
1
1.2 Historical background . . . . . . . . . . . . . . . . . . . . . . . . .
1
1.2 Significance of Problem. . . . . . . . . . . . . . . . . . . . . . . . .
1
2 Literature Review3

3 Methodology 7
4.1 System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7
4.2 Design Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7
4.3 Design Methodology . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7
4.4 High Level Design ........................... . .
8
4.5 Low Level Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8
4.6 Database Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8
4.7 GUI Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9
4.8 External Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9
4 Results and discussion 13

5 Conclusions15

Limitations
Conclusion
Future Work

6 References19
AUser Manual

viii
 List of Figures

1.1 Final Year Project Lifecycle...........................................................................2

List of Tables
Acronyms
DSA Data Structure and Algorithms
OOP Object Oriented Programming PF
Programming Fundamentals
SE Software Engineering
SQL Structured Query Language
UNESCO United Nations Educational, Scientific and Cultural Organization
UNICODE Unique, Universal, and Uniform Character enCoding
XML Extensible Markup Language

Abstract
This system is developed to manage everyday society activities of any housing society just like we
are making it for Canal Garden society Fsd.
Generally , in society all the work is manually. For example if some friends of society member wants
to come to society ,the society members firat have to call gatekeeper to tell him that his friend his
coming ,So that he can let the person enter ther society and it is not easier for the guard to identify
it is the same person whose permission was allowed by the society member. Contact no of
members are noted on the papers.All the complains are done by society members to the admin can
be forgetted .So with this system the admin can see and track record of complains by the Society

ix
mebers to him. So all work is done on paper so it is very difficult to manage complains and keep
track of all the visitor information in the society. This society co operative society management
system will computerize all day to day operation in the society. This System also keep the details of
service providers who provide different services like Security, Complaining, Dues payment,
Equipment Maintenance etc. There is no Computerized system for that doing all the things that
generally happen in society, so that members can come to know what is happening in society. This
system of maintaining a society is made in such a way, so that the most common problem faced in
residential societies are solved. Using this system Advance payments can be made with
banktransfer or JazzCash.User can send complains to society admin and also send visitor pictuer
and information to guard about that. Admin can note complains of society.Admin can also track
visitor information.Admin can also track old visitor to the Society.
.

x
 Chapter 1

Introduction
1.1 Is computer science science?

• Project Background/Overview
Our project is releted to Society management
system to manage daily tasks of societies such as Complain,Visitor mangement ,society
dues payment etc.
Today all the work is done by hand on paper for example if someone wants to visit
someone in society he first have to go through the call to society member then society
member tell the guard that his reletive or friend is coming but still the guard cant fully
know that the person is coming how shall be he looklike,anyone with that name can
come to guard and tell his name and succesfully enter the society.But in our system
the user can send the name Cnic photo and upcoming user photo to the guard ,So that
now guard can easily check upcoming visitor.
The other module of our app is that user can easily report complains to the admin of
society ,Now the admin can easily operates the admin panel of sytem and can see what
user is filed the complain,the admin can also check upcoming vistor and also checked
report of the previous vistors

• Problem Description
Every modern Society wants to convert their system to online for
better aproach,speed and long term data saving.More then 80% to 90% societies are
currently working on page’s by hand and not working securely.Our aim is to convert
over socities fully online ,so that they can do every thing on one click by hand on
there smart phone. That’s why we are creating android app for guard and society
members user ,so that they can be in touch by single click.We also made admin panel
for Society admin where he can see complain and solve that complains,and also can
track record of no of visitors.

1
  Project Objectives

The main goal of this project is to convert all the societies in Pakistan
fully online and yes there are some main objectives of that are as fellows.

 Project Scope

This project can enable the all societies to work for their betterment.when all the society
will be working online it will makes all us work more effeciently.

This project can lead to an ever-emerging market of customes of societies.

In Future we also want add other modules such apartment find and assign functions to
app.

 Motivations
We got our motivation from our Supervisor friend who is currently living in the Canal
Garden Society where all society work is currently being done by hand ,so he asked us to
this project for his Society.

 The Degree Project Report

The project report is an extremely important aspect of the degree project. It should be
properly structured and contain all the necessary and appropriate information regarding
the project.

PROJECT-II
Project-I
Phase 6 Midterm
Evaluation of Project by
supervisor and submit
FYP Life Cycle FYP Life Cycle form D to
project coordinator
Phase 1 Assign group id`s to
students who register
project-1

2
 Phase 5
Maintain Phase 9
Folder(for project Give awards to
coordinator) and prize winning
File(for supervisor) projects
of each group

Phase 4 Phase 3 Phase 2 Phase 7

Submission of Schedule Defense Phase 9 Collection of
Proposal and form A,B Phase 8
Form G and new presentation, External plagiarism report
submission by student
copy of proposal create panel and Evaluation Open House abstract, cv , Pena
to project coordinator
after defense assign panel to And compile flex and broachers
After selecting
presentation each group result from groups
supervisor and project

Figure 1.1: Final Year Project Lifecycle

Project report has to be progressively developed as and when various stages of project are
completed and last few weeks should be used to bring it together as a coherent document.
A well structured and consistently formatted project report makes reading easier and is
suggestive of a careful and professional attitude towards its preparation.
Remember that quantity does not automatically guarantee quality. A 150 page report is not
twice as good as a 75-page one, nor a 10,000 line implementation twice as good as a 5,000
line one. Conciseness, clarity and elegance are invaluable qualities in report writing, just as
they are in programming, and will be rewarded appropriately.
This document provides various guidelines for preparing a well structured project report.
Organization
Project report orgnization

3
 Chapter 2

Literature Review

Literature review is a systematic method of identifying, evaluating and interpreting the

work (similar to yours) produced by others. This chapter should set the project into context
and give the proposed layout for achieving the project goals. It is an important chapter
especially if the project involves significant amount of ground work. Review prior work
critically, identify gaps in knowledge/areas of application and build an argument for your
own work. When referring to other pieces of work, cite the sources where they are
referred to or used, rather than just listing them at the end.

4
5
 Chapter 3

Methodology

Systems design is the process of defining the architecture, components, modules,

interfaces, and data for a system to satisfy specified requirements. This chapter should have
the following sections:

4.1 System Architecture

This section describes the system in narrative form using non-technical terms. It should
provide a high-level system architecture diagram showing a subsystem breakout of the
system, if applicable. The high-level system architecture or subsystem diagrams should, if
applicable, show interfaces to external systems. Supply a high-level context diagram for the
system and subsystems, if applicable.

4.2 Design Constraints

This section describes any constraints in the system design (reference any trade-off
analyses conducted such, as resource use versus productivity, or conflicts with other
systems) and includes any assumptions made during the developing the system design.

4.3 Design Methodology

The Methodology which we use in making this application is Water Fall Method. Details are
as follow:

6
 7

7
Each product generated is one-of-a-kind, necessitating a customised SDLC approach based on
internal and external factors. The use of the Waterfall model is most appropriate in the following
situations:

⦁ Requirements are very much recorded, clear and fixed.

⦁ Product definition is steady.

⦁ Technology is dynamic.

⦁ Simple and straightforward and use.

⦁ Easy to oversee because of the inflexibility of the model. Each stage has explicit expectations
and a survey procedure.

⦁ Phases are prepared and finished each one in turn.

⦁ Easy to organize undertakings.

4.4 High Level Design

This section describes in further detail elements discussed in the Architecture. High-level
designs are most effective if they attempt to model groups of system elements from a
number of different views. Typical viewpoints are:

1. Conceptual or Logical: This view shows the logical functional elements of the system.
Each component represents a similar grouping of functionality. For UML, this would
be a component diagram or a package diagram.

2. Process: this view is the runtime view of the system. The components are threads or
processes or distributed applications. In UML, this would be a process interaction
diagram.

3. Physical: this view is for distributed systems. The components are physical pro-
cessors that have parts of the system running on them. For UML, this would be a
deployment diagram.

4. Module: this view is for project management and code organization. The components
are typically files or directories. This picture shows how the directory structure of the
build and development environment will be designed.

8
 5. Security: this view typically focuses on the components that cooperate to provide
security features of the system. It is often a subset of the Conceptual view.

4.5 Low Level Design

This section provides low-level design descriptions that directly support construction of
modules. Normally this section would be split into separate documents for different areas
of the design. For each component we now need to break it down into its fundamental
units or modules. For an OO implementation in Java, our components would become
packages. Then the low level design will take each package and break it down into its
classes. For smaller systems, you may have a single UML class diagram that each module
description refers to.

4.6 Database Design

The Following screen shots of database structure and table structure can showcase all the
working and database design for this project

9
 Categories table:

Fig 4.1 categories table:

Admin panel user’s database table:

Fig 4.2 Admin user table:

Complain table:

Fig 4.3 Complain table:

Visitor images, data table:

Fig 4.4 Visitor information table

Mobile app widget table:

In this table all the data related to the mobile widget and preloading images is saved
to database.
Mobile app loged in user’s table:
The data related to registered users is saved in the following table such as user who ave done
their signup after their signup the data is saved in the following table and when the user next
time wants to loged in the system will first check that is entered credentials matched with the
credentials in database ,if then he will allow him the user to access to the system.

10
 Fig 4.4 society user table:

4.7 GUI Design

This section provides the detailed design of the system and subsystem inputs and outputs
relative to the user. Depending on the particular nature of the project, it may be
appropriate to repeat these sections at both the subsystem and design module levels.

4.8 External Interfaces

External systems are any systems that are not within the scope of the system under
development. In this section, describe the electronic interface(s) between this system and
each of the other systems and/or subsystem(s), emphasizing the point of view of the
system being developed.

11
12
 Chapter 4

Results and discussion

The final result that we get after complete installation of the app are as fellows.. A few
transformations are accessible for change.
In information preparing discussion is characterized as the procedure of progress. Usage of a
venture, arranging and filing a complaint again any issue to the admin, visitor management
hierarchical arranging and individual organization, last framework structured and testing
foundation of standard, of execution and control methods, and discussions from old to new
framework. The most extensive procedure concerning execution face is the discussion plan, which
is examined in detail.

• Graphical user interface testing:

It is a type of testing in which all user interface is checked by the Mutiple user’s to see
is user interface is easier for the user to understand .Is there any error in checking
interface because to check is there any error error when performing something on app
or the pp is clearly seen and understand by the user’s.

Basically, it is performed to check responsiveness of the app display is supported on all

mobile device contain latest and backward pc data.

• Usability testing

• Software performance testing

We had tried our app on more 15 mobiles to see if its work on different android
version

• Compatibility testing

We also had tried every device aroud us to see if all things proper on all different
devices containing different types of android version.

13
 • Exception handling

We had also checked our app more 50 time to see how our app react to different
types of firmware version, and it works like a charm in all the devices so its
mean that its has no error.

• Load testing

• Security testing

We are currently using Aes Security in our project to encrypt data from user to
guard and then decrypt that data by the guard so that no one can listen or see the
communication between user’s

• Installation testing

We also had installed the app in our phones to see if it gives any type of error during
installation of our apps.
You just have to turn on the install from unknown devices to give app apk file to be
installed in your mobiles.

14
 For research based projects this chapter should include complete description of evalua-
tion metrics and analysis/discussion of evaluation results.

15
 Chapter 5

Conclusions

The project’s conclusions should list the things which have been learnt as a result of the
work you have done. For example, "The use of overloading in C++ provides a very elegant
mechanism for transparent parallelisation of sequential programs". Avoid tedious personal
reflections like "I learned a lot about C++ programming..." It is common to finish the report
by listing ways in which the project can be taken further. This might, for example, be a plan
for doing the project better if you had a chance to do it again, turning the project
deliverables into a more polished end product.

16
References
In IEEE style

[1] Peter J. Denning. Is computer science science? Commun. ACM, 48(4):27–31, April 2005.
Cited on p.1.

17
18