Property Management Sys Report

You might also like

Download as pdf or txt
Download as pdf or txt
You are on page 1of 33

A

PROJECT REPORT
ON

“PROPERTY MANAGEMENT SYSTEM”


Submitted by
MISS.VARSHA RAMDAS TAPKIR
MR.ROHIT SANTOSH THORAVE
T. Y. BSc(CS)

Semester II
Year: 2020-21

G.H. RAISONI COLLEGE OF ARTS,


COMMERCE & SCIENCE WAGHOLI, PUNE-
412207.
Savitribai Phule Pune University

Under the guidance of Prof. Jadhav P


i
G.H. RAISONI COLLEGE OF ARTS,
COMMERCE & SCIENCE
WAGHOLI, PUNE – 412 207

CERTIFICATE

This is to certify that Ms. VARSHA RAMDAS TAPKIR,


Seat no.10734 and MR.ROHIT SANTOSH THORAVE,
seat no. 10736 of T. Y. BSc(CS) with has satisfactorily
completed his project work under the subject “PROPERTY
Management System” for the academic year 2020-21.

Project Guide INTERNAL EXAMINER

External Examiner H.O.D Principal

ii
ACKNOWLEDGEMENT

A successful project is the result of a good team-work which consists of


not only the partners who put in their long and hard work but also those
who guided them. Indeed, a true saying.
First of all, we would like to thank our Hon’ able Principal Dr. M. D.
Shinde to give us an opportunity to study in this Institute.
We are graceful to Prof. Jadhav. P for providing necessary information,
valuable co-operation, encouragement and all the technical help during
the completion of our project.
We are also thankful to all faculty member who supported us to
complete our Project.
Last but not least, we express our gratitude to the almighty, without
whose blessing nothing is possible .

Students Name:
Ms. Varsha Tapkir
Mr. Rohit Thorave

Signature of Student

iii
Contents
PROJECT REPORT ..................................................................................................................................... i
CERTIFICATE ............................................................................................................................................ ii
ACKNOWLEDGEMENT ............................................................................................................................ iii
INTRODUCTION ....................................................................................................................................... 1
SCOPE OF THE SYSTEM ........................................................................................................................... 2
PROPOSED SYSTEM ................................................................................................................................. 3
SYSTEM ANALYSIS ................................................................................................................................... 4
FEASIBILITY STUDY .................................................................................................................................. 6
HARDWARE & SOFTWARE REQUIREMENT ............................................................................................. 7
DIAGRAMS ............................................................................................................................................ 11
Screens .................................................................................................................................................. 18
User profile ........................................................................................................................................... 20
Property updates .................................................................................................................................. 22
Profile update ....................................................................................................................................... 24
Logout: .................................................................................................................................................. 26
LIMITATION: .......................................................................................................................................... 27
FUTURE ENHANCEMENT ....................................................................................................................... 28

iv
INTRODUCTION

One of the tasks of any manager is to plan and control the


organization in the way that the organization can achieve its goals.
Issues relative with the well-being of man like shelter and others issues
are very important to take decision in the organization. With the help
of property management system those issues would be easily tackle.
This property management system is a software where property details
such as available house details, schedules, address, and others are being
setup by an administrator. The main aim of this project is to ensure
that management abides by regulations and laws when interacting with
tenants and vendors. Another aim is to match with properties for sale
by number of bedrooms / price criteria. Create Letters & contracts
easily using templates. It also aims to allow easy entry of Property and
vendor details

1
SCOPE OF THE SYSTEM

The scope of the project is to design and implement an automated institution


housekeeping system. This project is very mayor to all real estate
departments. The key focus is given on data security, as the project is online and
will be transferred in network. The speed and accuracy will be maintained in a
proper way. Through this project I have tried to automate the task of:
 Category of Property
 Features of Property
 Details of Property
 Price Details
 Available property information
 Entering the detail contact information, and other information.
 Checking password and confirm password.
 Checking username available or not during the registration process.
 Member management
 Member id is generated automatically from the table by auto generation.
 Entering the details like primary information, professional information,
contact information and other information.
 Add Banners and property images
 Save time of search
 Give a modification power to site’s owner. So, Administrator of site can
make any changes such like can add a new property category and property
type details on the working windows.
 Administrator can also change the Banner

2
PROPOSED SYSTEM

 To provide powerful logical user management for security


 To discuss project planning and the planning process
 To list all viewings for property
 To display matched property details easily and quickly by one
 To maintain client details line contact details, required property details,
client type like residential and commercial client. Price limit. Preference.
 To maintain property details, registration of property for sale includes
property address, property description, price, facilities available. Store
property floor plan, property documents. Creation of thumbnail of property
images for brochure.

3
SYSTEM ANALYSIS

4.1 FACT FINDING TECHNIQUES


The different fact-finding techniques used by the analyst are:
 QUESTIONNAIRE
 INTERVIEW
 RECORD REVIEW
 OBSERVATION

4.1.1 QUESTIONNAIRE
We used this technique in the initial phases and final phases of our project. In the
initial phases we prepared questionnaires to get some basic information about the
current system. We could find out the work structure of the organization and is
its functioning. In the final stage we used the Questionnaires to get some new
numerical data’s, that was required or was missing after all the observations.
Question asked were both open ended and closed ended. Which were related to
user interaction with current system, updating and rules for records maintenance,
report generated by current system, complications in the system as per the user.

4.1.2 INTERVIEWS

We used this technique frequently in the system analysis after questionnaires.


The interview was unstructured. We choose some people in the organization who
were either the decision makers or operators or user in some activity related with
the project. We interviewed them many times. This helped us to understand all
the steps involved in the activity. he user.

4.1.3 RECORDS REVIEW

This was the most beneficial technique for us while making our database. We
studied the exiting file structure, documents used and generated in the
organization. For every individual piece of information in this file or register we
tried to identify its significance, needs, relational with our data items and any
other features. This process contributed the most, in getting the data in first
normal form.

4
4.1.4 OBSERVATION:

While finding the facts we keenly observed all the activities in the organization.
We paid attention to the transaction, usage of files and documents, the record
keeping and the handling of queries in the existing system. Observation helped
us in finding out the actual way of functioning apart from the ideal or desired.
This helped us majorly in the interface design

5
FEASIBILITY STUDY

Feasibility study is important to evaluate cost and benefit of proposed system.


Feasibility study determines the potential, goal, hardware and software
requirements of existing system. On basis of feasibility study, we can decide that
whether to proceed or to postpone or to cancel the project. In feasibility study
steering committee plays very important role, it studies existing system and
identifies all problems and look three types of feasibility study.

5.1 ECONOMICAL FEASIBILITY

Economic feasibility is concern with total cost and all benefits as well as expected
saving of proposed system. It is also related with maintenance of system and
benefit derived from the system. The cost benefit analysis is common method in
the evaluation of the effectiveness of the system. In our system majority of tools
and technologies that were used are freely available and thus the development
cost is negligible. And the user point of view, there are no cost for using the
system. Hence the system is economically feasible.

5.2 TECHNICAL FEASIBILITY

Technical feasibility is related with study of hardware, software, overall computer


configuration of existing as well as proposed system. Our program is developed
using Java language and can run on any machine and is very easy to operate.
Also, we do not need any resources as the program can be executed on a single
machine. It is found that software and hardware are easily supported by the
system, so no additional requirement of hardware and software necessary.

5.3 OPERATIONAL FEASIBILITY

Operational feasibility is related with human, organizational and political aspects.


Our system is operationally feasible as it very easy for the End users to operate.
This system is developed in Java language. The user who has knowledge of this
language can operate the system.

6
HARDWARE & SOFTWARE REQUIREMENT

6.1 HARDWARE REQUIREMENT


 Hardware Specification:
 Server
 Processor: Intel P-IV (or above)
 RAM: 512 MB (or above)
 Hard disk: 20 GB (or above)
 Client
 Processor: Celeron 500 MHz or more, Intel Pentium III (or above)
 RAM: 128 MB RAM (or above)
 Hard disk: 10 GB (or above)

6.2 SOFTWARE REQUIREMENT


 Web Server: IIS Server
 Web Browser: IE 4 or Netscape 4x or upwards
 Development Tool: ASP.NET, C#, JavaScript, HTML, DHTML, AJAX.
 Database: Microsoft SQL Server 2008

6.3 OPERATING SYSTEM


 Operating System: Window 9x & All Window

7
DATA DICTIONARY
mysql> create table property (proid int primary key, proname varchar (20),
proadd varchar (20), protype varchar (20), proarea int, proprice int);

Query OK, 0 rows affected(0.13 sec)


mysql>create table seller (sno int primary key, sname varchar (20), sad varchar
(20), smob int);

Query OK, 0 rows affected(0.24sec)


mysql>create table buyers (byid int primary key, uname varchar (20), byadd
varchar (20), by_mob int, byemail varchar(20));

Query OK, 0 rows affected(0.20sec)


mysql> create table user (uid int primary key, uname varchar (20), umobile int,
uemail varchar (20), uadd varchar (20));

Query OK, 0 rows affected(0.17sec)


mysql>create table logic (logid in primary key, log username varchar (20),
logpass varchar (20);
Query OK, 0 rows affected(0.8sec)

8
TABLES: -
1) Property TABLE:
Field Name Data Type Length Description
Pro-id Int Define property id
Pro-name char Property name
Pro-add Char property address
Pro-type Char Property type
Pro-area Int Property area
Pro-price int Property rate

2) Seller table:
Field name Data type Length Description
S-no int Seller number
S-name char Seller Name
S-add char Seller address
S-mob int Mobile number

3) Buyers table:
Field Data type Length Description
by-id Int Buyer id
By-name Char Buyer name
By-add Char Buyer address
By-mob Int Mobile number
By-email Varchar Buyer email

9
4)User table:
Field name Data type length Description
U-id int User id
U-name char User name
u-mobile int User contact
u-email varchar User email
u-add varchar User address

5)Login table:
Field name Data type length Description
log-id int Login Id
Log-username char login username
Log-pass char Login password

10
DIAGRAMS

CLASS DIAGRAM: -

11
COMPONENT DIAGRAM:

PHP/ JAVA

DATABASE

12
DEPLOYMENT DIAGRAM:

USER COMPUTER DATABASE

13
USECASE DIAGRAM

Find property Requirement

Fix price Fix budget

advrtisement Look up locality

Sign up

Log in or log out

submit

Property Inspection
Show property
selection
Facility show case
buy
Sell

14
ER DIAGRAM OF PROPERTY MANGEMENT SYSTEM:

User id User name


password
Log In ID
User email

Login User
Mob no.

By. Name
Seller name
Seller id
By. ID By. add

has
Buyer seller

By. email Seller mo.no


By. Mobile
No.

property
P id P price

P name P type

P add

15
Activity diagram:

User login

Re-enter the password

approval

Enter the property database

Buyer requirements

Show the property

Buy the property

16
Collaboration diagram

1.login

property Database

2.login successful
7 registeration

4 buy it 3.lookup property

5.sell property

seller buyer
6.pay for property

17
Screens

Login:

18
19
User profile

20
21
Property updates

22
23
Profile update

24
25
Logout:

26
LIMITATION:

Limitations are matters and occurrences that arise in a study which are out of the
researcher's control. They limit the extensity to which a study can go, and
sometimes affect the end result and conclusions that can be drawn. The few
limitations in this web application are as follows:
 Lack of funds
 Inadequate timing
 Property is displayed for the limited number of days.
 Maps are not provided for the convenience of the user.
 Advance search facility is available for only registered user.
 Only few cities property can be uploaded.
 It doesn’t have online agreement facility.

27
FUTURE ENHANCEMENT

Nothing is perfect in this world. So, we are also no exception. Although, we have
tried our best to present the information effectively, yet, there can be further
enhancement in the Application.
We have taken care of all the critical aspects, which need to take care of during
the development of the Project.
Like the things this project also has some limitations and can further be enhances
by someone, because there are certain drawbacks that do not permit the system
to be 100% accurate.
The application is yet to be released and a lot of enhancements are already thought
of which are proposed to be implemented in the final version of the web-
application. The web-application has also provided feedback page on its home
page so that the users can provide their inputs of any functionalities/facilities they
would like to have in the web application.
The system is highly flexible one and is well efficient to make easy interactions
with the client. The key focus is given on data security, as the project is online
and will be transferred in network. The speed and accuracy will be maintained in
a proper way.
This will be a user-friendly one and can successfully overcome strict and severe
validation checks. The system will be a flexible one and changes whenever can
be made easy. Using the facility and flexibility in .NET and SQL, the software
can be developed in a neat and simple manner there by reducing the operator’s
work.
Since the project is developed in .NET as a front-end and SQL Server as a back-
end it can be modified easily and used for a long period. Following are some of
the enhancement proposed to be implemented in final version.
 Maps are provided to facilitate the users.
 Lease option should be provided regarding properties.
 Give access of website on mobile and PDAs
 Send SMS to property owner who have registered and uploaded
his property.
 Giving property site for all metro cities.
 Upload videos / 3d views of the property.

28
 BIBLIOGRAPHY
 WWW.WIKIPEDIA.ORG
 WWW.CODEPROJECT.COM

29

You might also like