Hsrms

1
Housing Society Record
Management System
By
OSAMA SHAHID
[BSCS-F14-0105]
SANA KHAN
[BSCS-F14-0135]
2018
Faculty of Engineering Sciences and Technology
Hamdard Institute of Engineering and Technology
Hamdard University, Main Campus, Karachi, Pakistan

2
Management System
By
OSAMA SHAHID
[BSCS-F14-0105]
SANA KHAN
[BSCS-F14-0135]
Under the Supervision of
Muhammad Adeel Mannan
2018

3
Management System
By
OSAMA SHAHID
[BSCS-F14-0105]
SANA KHAN
[BSCS-F14-0135]
A project presented to the
In partial fulfilment of the requirements for the degree of
Bachelors of Science
In
Computer Science

I
Faculty of Engineering Sciences and
Technology
CERTIFICATE
This project “Housing Society Record Management System” presented by
OSAMA SHAHID and SANA KHAN under the direction of their project
advisor and approved by the project examination committee, has been
presented to and accepted by the Hamdard Institute of Engineering and
Technology, in partial fulfilment of the requirements for the bachelor degree
of Computer Science.
Assistant Prof. Muhammad Adeel Mannan Member
(Project Advisor) (Name & Signature)
Prof. Dr Aqeel-Ur-Rehman Member
(Chairman, Department of Computing) (Name & Signature)
Prof. Dr Pervez Akhtar
(Acting, Director HIET)

I
ABSTRACT
Housing Society Record Management System aims at making the current situation in the
society simple and efficient. Society Management System reduces the conflicts that arise
within the society by providing facilities such as online monitoring, service request system
etc. It automates certain attributes that occur within the society and makes it easy for the
members of the society an easy access to the social happenings and ongoings.
It is a comprehensive and modern housing society management software for real estate and
residential complex sectors. It has been designed with People as well as Business as focal
points. It is developed to assist your office staff with day to day society operations
management and to give a unique living experience to residents. It assists you with end-to-
end management of processes: such as plots sales & purchase, registration, payment
instalments management, notification system charges, and much more.

II
ACKNOWLEDGEMENT
In the name of Allah, the most Gracious and the Most Merciful.
Peace and blessing of Allah be upon Prophet Muhammad ‫ﷺ‬
First, praise of Allah, for giving us this opportunity, the strength and the patience to complete
our FYP finally, after the challenges and difficulties. We would like to thank our supervisor
Assistant Prof. Muhammad Adeel Mannan for his guidance, motivation and most of his
significant contribution to this project. We would also like to thank our parents for financial
and moral support and our friends who have helped and motivated us throughout. May Allah
reward them all abundantly. (Ameen)

III
DEDICATION
This report is dedicated to Hamdard University, Shaheed Hakim Muhammad Saeed, and our
Teacher, our Supervisor, our Parents, our fellow colleagues and the hard-working students of
HIET, with a hope that they will succeed in every aspect of their Academic Career and this
project may help them in any aspect of their life.

IV
TABLE OF CONTENTS
ABSTRACT........................................................................................................................................... I
ACKNOWLEDGEMENT...................................................................................................................II
DEDICATION.................................................................................................................................... III
LIST OF FIGUERS............................................................................................................................VI
LIST OF TABLES.......................................................................................................................... VIII
CHAPTER 1..........................................................................................................................................9
1.1 Motivations..................................................................................................................9
1.2 Problem Statement ......................................................................................................9
1.3 Objectives and Contributions......................................................................................9
1.4 Project Scope.............................................................................................................10
1.5 Organization of the Report........................................................................................10
Chapter 2 .............................................................................................................................................12
2.1 Introduction....................................................................................................................12
2.3 Functional and Non-Functional Requirements..............................................................14
2.3.1 Functional Requirements ......................................................................................14
2.3.2 Non-Functional Requirements..............................................................................15
2.4 Project Significance .......................................................................................................15
2.5 Software Platforms.........................................................................................................15
2.5.1 Web Technology...................................................................................................15
2.5.2 Android Technology.............................................................................................15
2.6 Scalability ......................................................................................................................16
2.7 Services..........................................................................................................................16
CHAPTER 3........................................................................................................................................17
3.1 Use Case Diagram..........................................................................................................17
3.2 Activity Diagram ...........................................................................................................18
3.3 System Block Diagram ..................................................................................................20
3.4 System Architecture.......................................................................................................20
3.5 Entity Relationship Diagram..........................................................................................21
3.6 Inside Project .................................................................................................................22
3.6.1 XAMPP...............................................................................................................23
3.6.2 Router....................................................................................................................23
3.6.3 Android Smart Phone............................................................................................24
3.7 Used Technologies.........................................................................................................24
3.7.1 PHP (Personal Home Page) ..................................................................................24

V
3.7.2 My SQL .................................................................................................................24
3.7.3 React Native JS......................................................................................................25
3.7.4 JWT (Jason Web Token) .......................................................................................25
3.7.5 Lumen Framework.................................................................................................25
Chapter 4 .............................................................................................................................................27
4.1 Project Timeline Summary ............................................................................................27
4.2 Project Timeline Details ................................................................................................27
4.3 Black Box Testing..........................................................................................................28
4.3.1 System Testing......................................................................................................29
4.3.2 Integration Testing................................................................................................29
4.3.3 Unit Testing ..........................................................................................................29
4.3.4 User Acceptance Testing ......................................................................................30
4.4 Test Cases ......................................................................................................................30
Test Case # 1..................................................................................................................31
Test Case # 2..................................................................................................................31
Test Case # 3..................................................................................................................32
Test Case # 4..................................................................................................................32
Test Case # 5..................................................................................................................33
Test Case # 6..................................................................................................................33
CHAPTER 5........................................................................................................................................34
5.1 Mobile App Based GUI .................................................................................................34
5.2 Web Based GUI.............................................................................................................40
CHAPTER 6........................................................................................................................................50
6.1 Limitations.....................................................................................................................50
6.2 Conclusion .....................................................................................................................50
6.3 Future Works .................................................................................................................50
References............................................................................................................................................51
APPENDICES .....................................................................................................................52
APPENDIX A: CODING – SERVER-SIDE CODING ......................................................52
APPENDIX B: CODGING –JSON PACKAGE.................................................................55
APPENDIX C: COGING-LOGIN FILE .............................................................................55
APPENDIX D: ROUTES…………………………………………………………………………..63
APPENDIX E : CONTROLLERS…………………………………………………….………...…63

VI
LIST OF FIGURES
Figure No Description Page No
Figure 1.1: Project Scope............................................................................................... 11
Figure 3.1: Use Case Diagram – Web Application ....................................................... 17
Figure 3.1: Use Case Diagram – Android Application ………………………………...17
Figure 3.3: Activity Diagram – Web Application ......................................................... 19
Figure 3.4: Activity Diagram -- Android Application....................................................19
Figure 3.5: System Block Diagram................................................................................ 20
Figure 3.6: System Architecture .................................................................................... 21
Figure 3.7: ER Diagram................................................................................................. 22
Figure 3.8: XAMPP .................................................................................................... ...23
Figure 3.9: WIFI Router ................................................................................................ 23
Figure 3.10: Android Phone........................................................................................... 24
Figure 4.1: Gantt Chart Summary.................................................................................. 27
Figure 4.2: Gantt Chart Details...................................................................................... 28
Figure 5.1: Login Interface ............................................................................................ 34
Figure 5.2: Login Successful ......................................................................................... 35
Figure 5.3: Remaining Installments............................................................................... 35
Figure 5.4: Account Ledger ........................................................................................... 36
Figure 5.5: Service List.................................................................................................. 36
Figure 5.6: Electrician Service....................................................................................... 36
Figure 5.7: Painter Service............................................................................................. 36
Figure 5.8: Plumber Service .......................................................................................... 36
Figure 5.9: Gardener Service ......................................................................................... 37
Figure 5.10: Charges List............................................................................................... 38
Figure 5.11: Worker Panel............................................................................................. 38

VII
Figure 5.12: Worker Login successful .......................................................................... 38
Figure 5.13: List of Houses............................................................................................ 38
Figure 5.14: Amount Charge ......................................................................................... 39
Figure 5.15: Total Amount ............................................................................................ 39
Figure 5.16: Website Home Page .................................................................................. 40
Figure 5.17: Listing of Houses and Plots ...................................................................... 40
Figure 5.18:House / Plot Details.................................................................................... 41
Figure 5.19: Services ..................................................................................................... 41
Figure 5.20: Admin Panel - Dashboard ......................................................................... 42
Figure 5.21: Add Login.................................................................................................. 43
Figure 5.22: Manage Category ...................................................................................... 44
Figure 5.23: Add Category ............................................................................................ 45
Figure 5.24: Add House................................................................................................. 45
Figure 5.25: Manage House........................................................................................... 46
Figure 5.26: Manage Society......................................................................................... 47
Figure 5.27: Add Society............................................................................................... 47
Figure 5.28: Add Payments............................................................................................ 48
Figure 5.29: Manage Payments...................................................................................... 48
Figure 5.30: Service Request ......................................................................................... 50
Figure 5.31: Add Details................................................................................................ 51

VIII
LIST OF TABLES
Table No Description Page No
Table 2.1: Summary Of Research Papers ..................................................................................4
Table 4.1: Test Case # 1...........................................................................................................29
Table 4.2: Test Case # 2...........................................................................................................29
Table 4.3: Test Case # 3...........................................................................................................30
Table 4.4: Test Case # 4...........................................................................................................30
Table 4.5: Test Case # 5...........................................................................................................31
Table 4.6: Test Case # 6...........................................................................................................31

9
CHAPTER 1
1. INTRODUCTION
In this chapter, we will discuss the motivational concept, basic scope of our project i.e. Housing
Society Record Management System and the primary goals that are being achieved to fulfil the
concept of Housing Society.
1.1 Motivations
This system of keeping up a housing society is made in such a way, with the goal that the most
widely recognized issue looked in private societies are illuminated. This system is a web and
versatile application framework to oversee everyday exercises of any co-agent hosing society. The
main functionality of this project is that the client should be aware of all the services he will be
availed from the society management to complain management or from having payment of house
to requesting for a maintainer. This idea came up to our mind and we had discussed with our
supervisor.
1.2 Problem Statement
For the most part, in the public arena all the work is chosen in gatherings and upkeep charges,
contact no of individuals is noted on the papers. There is no mechanized framework for doing
every one of the things that by and large occur in the public arena with the goal that individuals
can come to recognize what is going on in the public eye. New purchasers of the general public
are not ready to visit the area because of their bother of accessibility or would prefer not to
squander their chance on visits.
1.3 Objectives and Contributions
The main scope of the project can be described is as follows:
• To provide a reliable interaction between customer and dealer/Web-based using HTML,
CSS, JavaScript, and Bootstrap, jQuery Material UI, MYSQL and PHP.

10
• Native iOS and Android application on React Native using Native base, React Navigation, and
Lumen which fulfils the requirement of getting the amount of instalment paid, alerts of billing
payment vouchers and society news update.
• A system, which fulfils the basic needs of society through the modern IT advancement.
1.4 Project Scope
Following modules are included in Project scope:
WEB VISITOR
Video Streaming Notifications Payment Alerts
Other details
Request
For
Services
Video Streaming
No Of
payments
No of
Installments
Notifications +
3
LOGIN
USER
ADMIN PANEL
User CRUD Property CRUD
Send Notifications
Manage Services Generate Bill
SEND AND RECEIVE RESPONSESEND AND RECEIVE RESPONSE
Figure 1.1: Project Scope
1.5 Organization of the Report
The reports start with the presentation of the ideas, which constitute the establishment stone of the
undertaking itself as well as the general space to which the task has a place and is proposed to
target.

11
Further, on, the report has been divided into two major sections apart from other relevant details
such as introduction and appendices. These two major parts are ‘Software Engineering’ and
‘Project Related Details’.
• The Software Engineering part covers all the details of the software side required to develop
this project such as Software Engineering life cycle, Software Schedule development, Software
Risk management etc.
• While project related Details cover detail like Housing Society Management System and
Motivation, Scope many more things.
By the end of the report, the Conclusion section provides the results of the project and future work,
which can be done in the same direction.

12
CHAPTER 2
2. LITERATURE REVIEW
2.1 Introduction
In this chapter, Literature Review of the project is reviewing from the before research that are
written with there too many efforts. The reviewing is including the process that relates to the
Housing Society that relates with Record Management System.
As the result, this chapter can determine the findings of the management system, which are used
to develop the project requirement as the tools to develop and the project schedule, and milestones.
2.2 Literature Review
The Housing service provides by different builders and platforms are manual, there is a need of
broker for sale or purchase. The idea is to give a direct coordination between the housing service
and the client or end user.
In this study and the related research, there is no proper solution to the problem. There is only the
management system provides to society to resolve their maintenance issues. The system provides
a unique interface to every user to interact with the system.
The system accepts queries from users, evaluates the need of the query, and fires it over the
database and results are displayed to the user. The system has automated functionality for
calculating monthly maintenance bill and the member can view their bill status on their account.
Proper management of the above tasks thus requires functionality based and automated mobile
application.
Productivity will experience a rise and there will be a subsequent fall in time and efforts of the
managing committee. Members can have access to their housing society day or night irrespective
of their remoteness. The application designed automatically generates the financial report for a
housing society describing the incoming funds and their utilization. The managing committee
members do the periodic transactions and updates. This allows the society residents to be assured
as to where the funds are employed. Here as residents register themselves with their apartment
details and access the services like viewing maintenance charges and financial reports thus
keeping transparency intact.

13
Author/ Date Theoretical
/
Conceptual
Framework
Analysis &
Results
Conclusions Implications for
Future research
1.ADDA
ERP.[1]
Brings
Professionalism
and
Transparency
to running of
the Association.
Ability to
moderate
Conversation
posts by residents
nominated as
Conversation
Moderators
In all
progressive
neighbourhoods
, Apartment
Owners
Associations,
Housing
Societies, or
Resident
Welfare
Associations
act as a strong
anchor.
The most captivating, helpful, great
network highlight of your ADDA. Be
that as it may, regularly it transforms
into a seething battleground where
upsetting words are traded, inner selves
are wounded, and neighborly decency is
broken.
2. Online real
estate
management
System. [2]
Online Market
Understanding
customer need.
Understand the
buying cycle
To know what
are our
compotators.
Each Real estate
can know
information
about the
consumers before
signing the lease
to know if there
is any unpaid
money or if it
using the
property is bad.
Information
Gathering and
system
Analysis We
visit more than
3company and
we make an
interview with
them.
Land can question around Tenant to
know the unpaid bunches or the season
of the reestablishment contract.
3.Rental
House
Management
System.[3]
The focus of
this research
project is
basically
managing to
the house for
low income,
medium and
high incomes
households or
what is
Commonly
known as
affordable
housing.
Developing rental
houses comes
with many
advantages
especially for the
Landlords who
are able to
increase their
profits through
rent paid by the
tenants.
To develop a
rental house
management
system that
allows the user
to view
customer’s data
as well as
houses record.
Enhance the
A system for apps.

14
4.Green Villa
housing
society
management
System.[4]
Facilities
include 24-hrs
Security,
Internet café,
24-hrs water
supply.
Entertainment
department is for
the
Members and by
the members.
It has various
departments,
which provide
you with the
best of its
services.
This facilitates you with modern
benefits and comforts.
2.3 Functional and Non-Functional Requirements
2.3.1 Functional Requirements
The web-based Management System has:
• Login
• Client Panel
• Admin Panel
• House Monitoring
• Alerts
• Next Payment Alert
• No. of Instalment Paid
• No. of Instalment left
• Construction Site Visit Date and Time Conformation
The Native Mobile App System has:
• Login
• No. of instalment Paid
• No. of instalment left
• House Monitoring
• Request for Services
• Electrician
• Painter
• Gardener

15
• Plumber
• Service Charges List
2.3.2 Non-Functional Requirements
• Efficiency
• Effectiveness
• Extensibility
• Portability
• Quality
• Reliability
2.4 Project Significance
The reports start with the presentation of the ideas, which constitute the establishment stone of the
undertaking itself as well as the general space to which the venture has a place and is expected to
target. The point of this task is to give an answer for social orders i.e. sufficiently adaptable to be
altered and executed according to future necessities. We have attempted our best to present this
free and user– agreeable site to Society individuals. Warnings for different happenings in the
public is added to the framework with the goal that clients do not miss the updates and happenings
of the public. The versatile application will cover what is the essential requirement for today's on
a single tick the housing benefit (I. e repairperson, circuit technician and so forth.) at your doorstep
and bill will be issued against your administrations.
2.5 Software Platforms
2.5.1 Web Technology
• Xampp Server 7.0.30
• Apache Web Server
• PHP 7.0 (Server Side)
• MySQL
• JWT (JASON WEB TOKEN)
2.5.2 Android Technology
• React Native

16
• JavaScript
• CSS
• JSX
• Native Base
• Lumen
• Composer
• JSON
2.6 Scalability
Housing Society Record Management System is a scalable project as we can add some more
features to it like administration voting system, parking management system based on image,
society security management system, society hall allotment system, HR Management of society
and etc.
2.7 Services
HRMS consist of mobile and web-based system, which is totally controlled through a web-based
admin panel that controls all the activities throughout both applications. If the user becomes the
part of the system, he can monitor all the goings of the society and can get the service at his
doorstep. All the system is controlled through the single database and communicate through
JASON WEB TOKEN.

17
CHAPTER 3
3. PROJECTS DIAGRAM
Based on the above literature review and project scope here are some diagrams, which illustrates
that what will be our project or the system is capable to reach the desired results.
3.1 Use Case Diagram
A utilization case graph can abridge the subtle elements of your framework's clients (otherwise
called on-screen characters) and their collaborations with the framework. To fabricate one, you'll
utilize an arrangement of particular images and connectors. A powerful utilize case graph can
enable your group to talk about and speak to:
Situations in which your framework or application cooperates with individuals, associations, or
outer frameworks

18
Objectives that your framework or application helps those substances (known as on-screen
characters) accomplish
The extent of your framework.
Figure 2.1 Use Case Diagram – Web-Based Application
Figure 3.2 Use Case Diagram - Android Application
3.2 Activity Diagram
Activity diagrams are graphical portrayals of work processes of stepwise exercises and activities
with help for decision, emphasis and simultaneousness. In the Unified Modeling Language,
activity diagrams are proposed to demonstrate both computational and authoritative procedures

19
(i.e. work processes). Movement outlines demonstrate the general stream of control.
Visit to Website
Virtual Tour of Plots
Payments Of Plot
ALERTS
Enable Online
Payment
Next Payment
Alert
Number of
Instalment Paid
Number of
Instalment Left
Site Visit Time And
Date
PLOT/SITE MNITORING
WEB BASED HRMS
Login
Sign Up
Figure 3.3 Activity Diagram – Web-Based Application
Visit to Application
Alerts
Enable Online
Payment
Next Payment
Alert
Number of
Instalment Paid
Number of
Instalment Left
Site Visit Time And
Date
Search For the Service
Search for the
Maintainer
MAINTAIANCE BILL
ANDROID BASED HRMS
Login
Figure 3.4 Activity Diagram – Android Application

20
3.3 System Block Diagram
A block diagram is a diagram of a system in which the principal parts or functions are represented
by blocks connected by lines that show the relationships of the blocks. They are heavily used in
engineering in hardware design, electronic design, software design, and process flow diagrams. Its
structure provides a high-level overview of major system components, key process participants,
and important working relationships.
DB_HSRMS
USERS
WEB BASED HSRMS
JASON
WEB
TOKEN
REQUEST FOR
SERVICE
REQUEST FOR
SERVICE
QUERY
RESULTS
QUERY
RESULTS
Figure 3.5 System Block Diagram
3.4 System Architecture
A system design could be an abstract model that defines the structure, behaviour, and additional
views of a system. associate degree design description could be a formal description and
illustration of a system, organized in a very method that supports reasoning regarding the structures
and behaviors of the system. The systems design method is wherever the ideas which will be the
backbone of the particular system area unit developed. it's an abstract model that describes the
structure and behaviour of the planned system or of the associate degree existing system. The
model might embrace the technical framework, end-user needs, and a listing of system elements

21
(hardware and software). The key choices that require to be created throughout the systems design
method are:
 The attributes of the new system.
 The sort of design.
 Type of computer code used (custom or off-the-shelf)
 Types of technologies used.
 How the system is going to be deployed.
Figure 3.6 System Architecture
3.5 Entity Relationship Diagram
An entity-relationship model (ER model) describes inter-related things of interest in an
exceedingly specific domain of data. associate degree ER model consists of
entity varieties (which classify the items of interest) and specifies relationships which will exist
between instances of these entity varieties. Entity–relationship modelling was developed
for information style by Peter bird genus and printed in an exceedingly 1976 paper. Some ER
modelers show super and subtype entities connected by generalization-specialization
relationships, associate degreed an ER model may be used additionally within the specification of
domain-specific ontologies. primarily, an abstract or logical ERD can visually show however the
terms in your gloss relate to at least
HOUSING SOCIETY RMS
HOUSING SOCIETY RMS
SERVER MACHINE
HOSUING
SOCIETY
RMS
APACHE WEB SERVER
DATABASE
REQUEST
RESPOND
REQUEST
RESPOND
RESPOND TO
LOGIN
CREDENTIALS
DATA AGAINST
THE
RESPECTIVE ID

22
one another. they're particularly useful in elucidative info models for relative information
and serving to business users perceive database structures at a high level and while not details.
Figure 3.7 ER Diagram Summary
3.6 Inside Project
HSRM comprises of both web and mobile application, both are dependent on a single database,
which connects each other through JSON web service and works in a method that all the record
from the web and mobile application stores in the database through it. Our project consists of the
following hardware and software technologies:

23
3.6.1 XAMPP
XAMPP may be a free and open supply cross-platform net server answer stack package
developed by Apache Friends, consisting chiefly of the Apache HTTP Server, Maria DB info,
and interpreters for scripts written within the PHP and Perl programming languages. XAMPP
stands for Cross-Platform (X), Apache (A), Maria sound unit (M), PHP (P) and Perl (P). it's a
straightforward, light-weight Apache distribution that creates it extraordinarily straightforward
for developers to make a neighborhood net server for testing and reading functions. Everything
required to line up an online server – server application (Apache), info (Maria DB), Associate in
Nursing scripting language (PHP) – is enclosed in an extractable file.
Figure 3.8: XAMPP
3.6.2 Router
150Mbps wireless data rates ideal for video streaming, online gaming and internet calling.
Wireless security encryption easily at a push of WPS button. IP based bandwidth control allows
administrators to determine how much bandwidth is allotted to each PC.WDS wireless bridge
provides seamless bridging to expand your wireless network
Figure 3.9: WIFI Router

24
3.6.3 Android Smart Phone
Android is that the name of the mobile package owned by associate Yankee company, Google. It
most typically comes put in on a spread of smartphones and tablets from a bunch of makers
giving users access to Google’s own services like Search, YouTube, Maps, Gmail and a lot of.
This means you'll simply hunt for data on the online, watch videos, look for directions and write
emails on your phone, even as you'd on your laptop, however, there's a lot of to automaton than
these straightforward examples.
Figure 3.10: Android Phone
3.7 Used Technologies
Besides hardware, the following tools and techniques were used to grab the value from hardware
feed them to the database then let the application to view the desired results.
3.7.1 PHP (Personal Home Page)
PHP is a general-purpose scripting language that is especially suited to server-side web
development, in which case PHP generally runs on a web server. Any PHP code in a requested file
is executed by the PHP runtime, usually to create dynamic web page content or dynamic images
used on websites or elsewhere.
3.7.2 My SQL
MySQL is an open supply relational database management system. info in a very MySQL
information is kept within the style of connected tables. MySQL databases are generally used for
internet application development (often-accessed mistreatment PHP). A MySQL information is

25
accessed (queried) directly using; C, C++, Eiffel, Java, Perl, PHP and Python pc languages. there's
conjointly third-party support for affiliation in a very Windows surroundings. MySQL databases
are queried employing a set of the quality Structured source language (SQL) commands.
3.7.3 React Native JS
React Native enables you to build mobile apps victimisation solely JavaScript. It uses identical
style as React, property you compose an expensive mobile UI from declarative elements. With
React Native, you are doing not build a “mobile net app”, AN “HTML5 app”, or a “hybrid app”.
You build a true mobile app that's indistinguishable from AN app designed victimisation
Objective-C or Java. React Native uses identical elementary UI building blocks as regular iOS and
robot apps. you only place those building blocks along victimisation JavaScript and React.
React Native combines swimmingly with elements written in Objective-C, Java, or Swift. it's
straightforward to change posture to native code if you would like to optimize many aspects of
your application. it's additionally straightforward to make a part of your app in React Native, and
a part of your app victimization the native code directly - that's, however, the Facebook app
works.3.7.4
JWT (Jason Web Token)
JSON Web Token (JWT) is AN open customary (RFC 7519) that defines a compact and self-
contained method for firm transmission data between parties as a JSON object. This data may
be verified and trusty because of it is digitally signed. JWTs may be signed employing a secret
(with the HMAC algorithm) or a public/private key combine exploitation RSA.
This is the foremost common state of affairs for exploitation JWT. Once the user is logged
in, every succeeding request can embrace the JWT, permitting the user to access routes, services,
and resources that area unit permissible therewith token. Single Sign-On could be a feature
that wide uses JWT these days, thanks to its little overhead and its ability to be simply used
across completely different domains.
3.7.5 Lumen Framework
Lumen could be a new project from Laravel creator Taylor Otwell. It is a "micro-framework",
which means it is a smaller, faster, throw version of a full internet application framework. PHP
has two different well-liked micro-frameworks, Slim and Silex.

26
Lumen is for comes and elements that may like the convenience and power of Laravel however
can afford to sacrifice some configurability and adaptability in exchange for a speed boost.
Lumen is targeted at micro-services--small, loosely coupled elements that typically support and
enhance a core project. Micro services square measure separated elements with finite contexts
(meaning they need well-defined interfaces between every other), therefore in an exceedingly
micro service design, you would possibly have many little Lumen apps that support another,
presumably Laravel-powered, app.

27
CHAPTER 4
4. Project Planning
4.1 Project Timeline Summary
This Project has been divided into 5 milestones namely “Requirement Gathering” involving 73
days followed by “Requirement Analysis” involving 15 days followed by “Literature Review”
consisting of 22 days followed by “Implementation” involving 189 days followed “Integration
testing” involving 16 days with final “Documentation” processed in 5 days, whereas Saturday and
Sunday were not considered as working days. This project took approximately 1 year and 5 months
to be completed starting from 15 February 2017 and 26 July 2018.
Figure 4.1: Gantt chart Summary
4.2 Project Timeline Details
A timeline may be an approach of displaying an inventory of events in written account order,
typically delineate as a project artifact. It is usually a graphic style showing a protracted bar tagged
with dates aboard itself and frequently events tagged on points wherever they would have
happened. A project timeline is extremely careful, with many tasks and subtasks, or terribly
straightforward, listing solely a couple of deliverables and deadlines. A project timeline must
capture the subsequent key items of data just like the list of tasks to be complete. The dates on that

28
the tasks ought to be complete and the expected length of every task and dependencies between
tasks.
Figure 4.2: Gantt chart Details
4.3 Black Box Testing
Black Box Testing, additionally referred to as behavioral testing, may be a software package
testing methodology during which the inner structure/ design/ implementation of the item being
tested is not familiar to the tester. These tests are often purposeful or non-functional, the' typically
purposeful. Testing, either purposeful or non-functional, while not related to the inner structure of
the part or system.

29
This technique is that the procedure to derive associate degreed/or choose check cases supported
an analysis of the specification, either purposeful or non-functional, of a part or system while no
relation to its internal structure. Black Box testing method is applicable to the following levels of
software testing:
 System Testing
 Integration Testing
 Acceptance Testing
 User Acceptance Testing
The higher the level, and hence the bigger and more complex the box, the black box testing method
comes into use.
4.3.1 System Testing
System Testing could be a level of the code testing wherever an entire and integrated code is tested.
The aim of this take a look at is to gauge the system’s compliance with the desired needs. The
method of testing AN integrated system to verify that it meets specified needs. System testing is
that the testing of entire and totally integrated wares. Usually, a code is barely one component of
a bigger computer-based system. Ultimately, a code is interfaced with different software/hardware
systems. System testing is truly a series of various tests whose sole purpose is to exercise the
complete computer-based system. System testing involves testing the totally integrated
applications as well as external peripherals to envision however, elements move with each other
and with the system as an entire. This is often conjointly referred to as End-to-End testing situation.
Verify thorough testing of each input within the application to envision for desired outputs. Testing
of the user's expertise with the applying.
That is a basic description of what is concerned in system testing. You wish to make elaborated
take a look at cases and look at sites that look at every facet of the applying as seen from the skin
while not staring at the particular ASCII text file.
4.3.2 Integration Testing
Integration testing finds the bugs that occur once 2 or a lot of models integrated. The main purpose
of Integration testing is to identify the purposeful, demand and performance level bugs. once

30
modules not integrated, they perform as per demand however once they integrated, functional,
demand and performance connected problems can occur thanks to the mixing.
4.3.3 Unit Testing
Unit testing could be a level of software package testing wherever individual units/ parts of a
software package square measure tested. the aim is to validate that every unit of the software
package performs as designed. The unit is that the smallest testable a part of the software package.
it always has one or many inputs and frequently one output. In procedural programming, a unit
could also be a personal program, function, procedure, etc. In object-oriented programming, the
tiniest unit could be a technique, which can belong to a base/ super category, abstract category or
derived/ kid category. Unit testing frameworks, drivers, stubs, and mock/ faux objects square
measure wont to assist in unit testing. Unit Testing is often performed by software package
developers themselves or their peers. In rare cases, freelance software package testers may
additionally perform it.
4.3.4 User Acceptance Testing
User acceptance testing (UAT) is that the last part of the package testing method. During UAT,
actual coding system users scrutinize the pc code to make positive it'll handle required tasks in
real-world eventualities, in line with specifications. UAT is in addition known as beta testing,
application testing or end-user testing. UAT directly involves the meant users of the package. UAT
is implemented by making coding system getable for a free beta trial on net or through associate
degree in-house testing team comprised of actual package users.
4.4 Test Cases
In the simplest type, a test case could be a set of conditions or variables underneath that a tester
determines whether the software satisfies needs and functions properly.
A test case could be a single possible take a look at that a tester carries out. It guides them through
the steps of the take a look at. You will be able to think about an action as a group of systematic
directions to verify one thing behaves because it is needed to behave.
When testing begins, the take a look acting team follows the test cases or “scripts” they wrote to
execute the tests and verify the package. The sequence or cluster of test cases is termed a test suite.

31
Test Case # 1
Test Case Title: Testing the login mechanism of Housing Society Record Management System.
Table 4.1: Test Case # 1
Preconditions
Make username and password of the
system to provide access to few
authorizers
Actions
Click the login button after providing
username and password for accessing
information of the user.
Expected Results
The system should access the panel of
different users
Tested By Sana Khan
Result Pass
Test Case # 2
Test Case Title: Testing the Sign Up mechanism of Housing Society Record Management System.
Preconditions
Make all the details in the form of
different types of case sensitivities.
Actions
Click the Register button after providing
Expected Results Details in the user's table must be entered
Tested By Sana Khan
Result Pass

32
Test Case # 3
Test Case Title: Testing the Video (House Monitoring) of Housing Society Record Management
System.
Preconditions
To check whether the video monitoring is
working or not
Actions
Click the monitoring button after providing
Expected Results Live Video played
Tested By Sana Khan
Result Pass
Test Case # 4
Test Case Title: Testing the Service Charge mechanism of Housing Society Record Management
System.
Preconditions
Make admission of services of the system
to provide access to few authorizers
Actions
Click the login button after providing
Expected Results
The system should access the panel of
different users
Tested By Sana Khan
Result Pass

33
Test Case # 5
Test Case Title: Testing the Main Dashboard accesses of different users in the Housing Society
Record Management System.
Preconditions Users must login in the system
Actions
Click on login button in login panel after
providing username and password
Expected Results
The system should identify the user request
to get into it is of the system according to
his role.
Tested By Sana Khan
Result Pass
Test Case # 6
Test Case Title: Testing the Maintainer panel after login the user is only getting service providing
facility.
Preconditions
Must be able to add services to the user of
the respective house
Actions Service addition facility
Expected Results
The maintainer should be able to add the
houses and can only view as he has the
rights
Tested By Sana Khan
Result Pass

34
CHAPTER 5
5. GUI of Housing Society Record Management System
5.1 Mobile App Based GUI
Figure 5.1: Login Screen email address and password is required
Figure 5.2: Pop up with login message if the id password is correct
Figure 5.1: Login Interface Figure 5.2: Login Successful
Figure 5.3: Personal profile with instalment information
Figure 5.4: Personal profile with remain dues to be cleared

35
Figure 5.3: Remaining Installments Figure 5.4: Account Ledger
Figure 5.5: Selection of service from the list
Figure 5.6: Service choose and showing options to send information or go back

36
Figure 5.5: Service List Figure 5.6: Electrician Service
Figure 5.7: Painter Service Figure 5.8: Plumber Service

37
Figure 5.10: Service charge list
Figure 5.9: Gardener Service Figure 5.10: Charges List
Figure 5.11: Worker panel loin panel
Figure 5.12: Login successful in work panel

38
Figure 5.11: Worker Panel Figure 5.12: Login Successful
Figure 5.13: List of service asked houses in worker panel
Figure 5.14: service that availed by the house
Figure 5.13: List of Houses Figure 5.14: Amount Charge

39
Figure 5.15: the total amount of service charged
Figure 5.15: Total Amount

40
5.2 Web-Based GUI
Figure 5.16: Home screen for the end user
Figure 5.16: Home Screen
Figure 5.17: List of houses or plot
Figure 5.17: List of Houses/Plots

41
Figure 5.18: Details of house or plot
Figure 5.18: House / Plot Details
Figure 5.19: List of services provided
Figure 5.19: Service

42
Figure 5.20: Contact us page fill the details will go to the admin that has been filled
Figure 5.20: Contact Us
Figure 5.21: Admin dashboard view after login
Figure 5.21: Admin Dashboard

43
Figure 5.22: Login Page username password required for login
Figure 5.22: Login Page
Figure 5.23: Add category Screen that will reflect main user view
Figure 5.23: Add Category

44
Figure 5.24: Category List
Fisas
Figure 5.24: Manage Category
Figure 5.25: Add house entry form with some fields.
Figure 5.25: Add House

45
Figure 5.26: Listing of entered houses.
Figure 5.26: Manage House / Plot
Figure 5.27: Listing of the societies.
Figure 5.27: Manage Society

46
Figure 5.28: Add society form.
Figure 5.28: Add Society
Figure 5.29: Add Payment Form Used for notifications.
Figure 5.29: Add Payment

47
Figure 5.30: Listing of payments of each user against the notifications.
Figure 5.30: Manage Property
Figure 5.31: Listing of registered users.
Figure 5.31: Users

48
Figure 5.32: Listing of Service Requests that have been received from the end users.
Figure 5.32: Service Request
Figures 5.33: Listing of houses that have paid against the services we had provided.
Figure 5.33: Service

49
Figure 5.34: Listing of societies.
Figure 5.34: Manage Society
Figure 5.35: Listing of contacted users.
Figure 5.35: Contact

50
CHAPTER 6
6. Conclusion and Future Work
6.1 Limitations
 Online Payments of bills.
 This project is deployed locally not globally.
 Availability of more services.
 UI / UX modifications.
6.2 Conclusion
In conclusion, we have developed a web and Android based system which allow the users (i.e.
students or teachers) to work on a single database which is Android and web-based . Through
where clients and society members can view their details along with the monitoring facility, they
can also ask for the maintains services through mobile application and bill is also generated
through the maintainer so that he can pay bill on doorstep. Admin panel can view update and delete
all the activities within the application.
6.3 Future Works
There is always a chance of improvement; the following are the aspects where the system requires
some time to be analyzed and modified:
 Improve the quality of design.
 Improve quality if database management systems.
 Enhance the code structure.
 Enhance application functionality.
 Provide the live IP to the system and make it accessible from anywhere from the world.
 Enhance android application or may also introduce across other platforms
 The system is flexible, can be deployed in any other society with little modifications.

51
REFERENCES
1] S.Banerjee,"Aboutus,"2008.[Online].Available:
https://apartmentadda.com/home/aboutUsPage_inc_team.php.
[2] J.Odeh,"Onlinerealestatemanagementsystem,"[Online].Available:
https://www.slideshare.net/jazod7/online-real-estate-management-system-34844226.
[3] Henry Peter Gommans, , G.M.N., and , A.N.O.: ‘Rental House Management System’,
International Journal of Scientific and Research Publications, , 2014, 4, (II)
[4] P. trainer, "Green Villa housing society management system," 3 june 2015. [Online].
Available: http://www.1000projects.info/visual-basic-vb-projects/green-villa-housing-
society-managementsystem/1106
[5] Prachi Pakhale, S.S., Swsati Dhake,: ‘Online Housing Society Management System’,
International Journal for Research in Applied Science & Engineering Technology (IJRASET)
2016, 4, (III)
[6] Summit, S.C.C.: ‘Envisioning And Implementation a Smart Society’
[7] Rutuja Vatharkar, P.P., Swati Sonar, Prof. Shivganga Gavhane ‘IMPLEMENTATION OF
SOCIETY MANAGEMENT SYSTEM: SOCIETALES’, International Journal of Science &
Technology 2016, 6, (2)
[8] M.M.Y, "About Us," 1987. [Online]. Available:
http://www.society123.com/stpages/featureslist.html.
[9] Prof. Virupaksha Gowda, S., Sowmya Lakshmi , Zeenath, Ghaleppa: ‘Apartment
Management System’, International Journal for Technological Research In Engineering
2016, 3, (9)
[10] "Smart society index," [Online]. Available:
https://www.smartsociety.in/Pages/Info/about.html.
[11] Shivganga Gavhane , S.S., Rutuja Vatharkar,Pratiksha Patil: ‘Study of Implementation of
Society Management System’, International Journal of Computer Applications, 2015, 132,
(1)

52
APPENDICES
APPENDIX A: CODING – SERVER-SIDE CODING
import React, { Component } from 'react';
import {
StyleSheet,ViewS
} from 'react-native';
import {Container, Header, Content, Footer, Title, Label, TextInput,
Input, InputGroup, Button, Icon, Form, Item,
FooterTab, Text, Badge ,Grid, Col
} from 'native-base';
import { navigationOptions, navigation } from 'react-navigation';
import {API_URL} from './../../utilities/Globals';
import Jmheader from './../../components/jmheader'
import Jmfooter from './../../components/jmfooter';
type Props = {};
export default class AddServices extends Component<Props> {
static navigationOptions = {
header: null
}
async submitForm () {
try {
let data = { service_name, service_price } = this.state;
this.setState({isLoading:true});
fetch(API_URL+"services", {
method: 'POST',
headers: {
Accept: 'application/json',
'Content-Type': 'application/json',
},
body: JSON.stringify(data)
})
.then((response) => response.json())
.then((responseData) => {
if(responseData.status) {
this.setState({isLoading:false});
this.props.navigation.goBack()

53
}
})
.done();
} catch (error) {
console.error(error);
}
}
updateFormField = fieldName => text => {
this.setState({ [fieldName]: text })
}
componentDidMount(){
return fetch(API_URL+'services')
.then((responseJson) => {
this.setState({
isLoading: false,
service_name: '',
service_price: '',
}, function(){
});
})
.catch((error) =>{
console.error(error);
});
}
render() {
const { state, navigate } = this.props.navigation;
return (
<Container>
<Jmheader title="Add new Service"
navigation={this.props.navigation} />
<Content >
<Grid style={{alignItems: 'center'}}>
<Col>
<Form>
<Item floatingLabel>
<Label>Service Name</Label>
<Input
onChangeText={this.updateFormField('service_name')}/>

54
</Item>
<Item floatingLabel last>
<Label>Service Price</Label>
<Input
onChangeText={this.updateFormField('service_price')}/>
</Item>
</Form>
</Col>
</Grid>
<Grid style={{alignItems: 'center'}}>
<Col>
</Col>
</Grid>
<Grid style={{alignItems: 'center'}} style={{padding:
30}}>
<Col>
<Button block bordered info onPress={() =>
this.submitForm()}>
<Text> Save </Text>
</Button>
</Col>
</Grid>
<Grid style={{alignItems: 'center'}} style={{padding:
30}}>
<Col>
<Button block bordered info onPress={() =>
this.props.navigation.goBack()} >
<Text> Go back... </Text>
</Button>
</Col>
</Grid>
</Content>
{/* <Jmfooter navigation={this.props.navigation} /> */}
</Container>
);
}
}
const styles = StyleSheet.create({
container: {
justifyContent: 'center',
marginTop: 50,
padding: 20,

55
backgroundColor: '#ffffff',
},
});
APPENDIX B: CODGING –JSON PACKAGE
{
"name": "hsrms",
"version": "0.0.1",
"private": true,
"scripts": {
"start": "node node_modules/react-native/local-cli/cli.js start",
"test": "jest"
},
"dependencies": {
"native-base": "^2.0.12",
"react": "15.4.2",
"react-native": "0.42.0",
"react-native-fetch-blob": "^0.10.2",
"react-native-file-picker": "0.0.5",
"react-native-html-to-pdf": "^0.3.0",
"react-native-modal-picker": "0.0.16",
"react-native-side-menu": "^0.20.1",
"react-native-simple-modal": "^4.0.2",
"react-native-swiper": "^1.5.4",
"react-redux": "^5.0.3",
"redux": "^3.6.0"
},
"devDependencies": {
"babel-jest": "19.0.0",
"babel-preset-react-native": "1.9.1",
"jest": "19.0.2",
"react-test-renderer": "15.4.2"
},
"jest": {
"preset": "react-native"
APPENDIX C: COGING-LOGIN FILE
import React, { Component } from 'react';
import {Toast} from 'native-base';
import {
AppRegistry,
StyleSheet,
Text,
View,

56
Image,
Dimensions,
TextInput,
Button,
TouchableOpacity,
AsyncStorage,
} from 'react-native';
const { width, height } = Dimensions.get("window");
const background = require("./login1_bg.png");
const mark = require("./login1_mark.png");
const lockIcon = require("./login1_lock.png");
const personIcon = require("./login1_person.png");
export default class LoginScreen extends Component {
constructor(props) {
super(props);
this.state = {
username: null,
password:null,
toastdata:null,
utoken:null
};
}
showtoast(){
Toast.show({
text: this.state.toastdata,
position: 'bottom',
buttonText: 'Okay'
})
}
_navigate(){
this.props.navigator.push({
name: 'SignupScreen',
})
}
componentWillMount(){
AsyncStorage.getItem("@MySuperStore:jtoken")
.then((value) =>{
this.setState({"utoken": value});
fetch('http://192.168.0.102/fyp/users', {
method: 'GET',
headers: {
'authorization': this.state.utoken,
}
})

57
console.log(responseJson.teacher+" token");
console.log(responseJson.teacher+" is teacher");
if(responseJson.status!='0'){
if(responseJson.teacher=='1'){
name: 'Folders', // Matches route.name
});
}
name: 'Stu', // Matches route.name
});
}
}
})
.catch((error) => { console.error(error); });
});
}
_login(){
let username = this.state.username;
let password = this.state.password;
fetch('http://192.168.0.102/fyp/token', {
method: 'POST',
headers: {
},
body: JSON.stringify({
username: username,
password: password
})
})
console.log(responseJson);
if(responseJson.status!= "0"){
AsyncStorage.setItem('@MySuperStore:jtoken',
responseJson.token);
AsyncStorage.setItem('@MySuperStore:jtokenrol',
responseJson.teacher);
name: 'Folders', });

58
}if(responseJson.teacher=='0'){
name: 'Stu', });
}
}else{
this.setState({toastdata: "user not found"});
this.showtoast();
}
})
.catch((error) => { console.error(error); });
}
render() {
return (
<View style={styles.container}>
<Image source={background} style={styles.background}
resizeMode="cover">
<View style={styles.markWrap}>
<Image source={mark} style={styles.mark}
resizeMode="contain" />
</View>
<View style={styles.wrapper}>
<View style={styles.inputWrap}>
<View style={styles.iconWrap}>
<Image source={personIcon} style={styles.icon}
</View>
<TextInput
placeholder="email"
placeholderTextColor="#FFF"
style={styles.input}
onChangeText={(username) => this.setState({username})}
/>
</View>
<View style={styles.inputWrap}>
<View style={styles.iconWrap}>
<Image source={lockIcon} style={styles.icon}
</View>
<TextInput
placeholderTextColor="#FFF"
placeholder="Password"
style={styles.input}
secureTextEntry
onChangeText={(password) => this.setState({password})}
/>
</View>

59
<TouchableOpacity activeOpacity={.5} onPress =
{()=>{AsyncStorage.getItem('@MySuperStore:jtoken').then((va)=>{console
.log(va)})}}>
<View>
<Text style={styles.forgotPasswordText}>Forgot
Password?</Text>
</View>
</TouchableOpacity>
<TouchableOpacity activeOpacity={.5}
onPress={this._login.bind(this)}>
<View style={styles.button}>
<Text style={styles.buttonText} >Sign In</Text>
</View>
</TouchableOpacity>
</View>
<View style={styles.container}>
<View style={styles.signupWrap}>
<Text style={styles.accountText}>Don't have an
account?</Text>
<TouchableOpacity activeOpacity={.5}>
<View>
<Text style={{color: "black"}} onPress={ () =>
this._navigate() }>Sign Up</Text>
</View>
</TouchableOpacity>
</View>
</View>
</Image>
</View>
);
}
}
const styles = StyleSheet.create({
container: {
flex: 1,
},
markWrap: {
flex: 1,
paddingVertical: 30,
},
mark: {
width: null,
height: null,
flex: 1,
},
background: {
width,
height,
},
wrapper: {
},

60
inputWrap: {
flexDirection: "row",
marginVertical: 10,
height: 40,
borderBottomWidth: 1,
borderBottomColor: "#CCC"
},
iconWrap: {
paddingHorizontal: 7,
alignItems: "center",
justifyContent: "center",
},
icon: {
height: 20,
width: 20,
},
input: {
flex: 1,
paddingHorizontal: 10,
},
button: {
backgroundColor: "green",
marginTop: 30,
},
buttonText: {
color: "#FFF",
fontSize: 18,
},
forgotPasswordText: {
color: "#D8D8D8",
backgroundColor: "transparent",
textAlign: "right",
paddingRight: 15,
},
signupWrap: {
backgroundColor: "transparent",
flexDirection: "row",
},
accountText: {
color: "#D8D8D8"
},
signupLinkText: {
color: "#FFF",
marginLeft: 5,
}

61
APPENDIX D: ROUTES
?php
$router->get('/', function () use ($router) {
return $router->app->version();
});
$router->post('/login', 'MainController@login');
$router->get('/houses', 'MainController@houses');
$router->get('/services', 'MainController@services');
$router->post('/services', 'MainController@add_services');
$router->post('/add_paid_amount', 'MainController@add_paid_amount');
$router->post('/get_ledger', 'MainController@get_ledger');
$router->post('/get_installments', 'MainController@get_installments');
$router->post('/service_request', 'MainController@service_request');
$router->post('/create_user', 'MainController@createusers');
$router->get('/get_user',
['middleware' => 'auth',
'uses' => 'MainController@getusers']);
APPENDIX E: CONTROLLERS
<?php
namespace AppHttpControllers;
use AppUser;
use AppService;
use AppPaidAmount;
use AppPayment;
use AppServiceRequest;
use IlluminateHttpRequest;
class MainController extends Controller
{
/**
* Create a new controller instance.
*
* @return void
*/
public function __construct()
{
}

62
public function login(Request $request){
$allUsers = User::where('email','=', $request->input('email'))
->where('password', '=', $request->input('password'))
->first();
$allUsers->api_token = rand(10000,99999);
$allUsers->save();
if($allUsers){
$data['message']='successfully login';
$data['status']=true;
$data['api_token']=$allUsers->api_token;
$data['user_type']=$allUsers->user_type;
$data['users_id']=$allUsers->id;
$data['address']=$allUsers->address;
$data['data']='';
}else{
$data['message']='login failed.....';
$data['status']=false;
$data['data']='';
}
return response()->json($data);
}
public function houses(){
$allhouses = User::where('user_type', '=', 'user')->get();
return response()->json($allhouses);
}
public function services(){
$allServices = Service::all();
return response()->json($allServices);
}
public function add_services(Request $request){
$services = new Service();
$services->service_name = $request->input('service_name');
$services->service_price = $request->input('service_price');
if($services->save()){
$data['message']='successfully created service';
$data['data']='';
}else{
$data['message']='service can not create ';
$data['data']='';
}

63
}
public function add_paid_amount(Request $request){
$PaidAmount = new PaidAmount();
$PaidAmount->users_id = $request->input('users_id');
$PaidAmount->total_amount = $request->input('fullTotal');
if($PaidAmount->save()){
$data['message']='successfully Paid';
$data['data']='';
}else{
$data['message']='can not create ';
$data['data']='';
}
}
public function get_ledger(Request $request){
$users_id = $request->input('users_id');
$ledger = PaidAmount::where('users_id', '=', $users_id)->get();
return response()->json($ledger);
}
public function get_installments(Request $request){
$users_id = $request->input('users_id');
$ledger = Payment::where('userid', '=', $users_id)->get();
return response()->json($ledger);
}
public function service_request(Request $request){
$services = new ServiceRequest();
$services->users_id = $request->input('users_id');
$services->request_content = $request->input('request_content');
if($services->save()){
$data['message']='successfully created service request';
$data['data']='';
}else{
$data['message']='service request can not create ';
$data['data']='';
}
}}

Hsrms

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Hsrms

Similar to Hsrms (20)

Recently uploaded

Recently uploaded (20)

Hsrms