Professional Documents
Culture Documents
Property Management Sys Report
Property Management Sys Report
Property Management Sys Report
PROJECT REPORT
ON
Semester II
Year: 2020-21
CERTIFICATE
ii
ACKNOWLEDGEMENT
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
1
SCOPE OF THE SYSTEM
2
PROPOSED SYSTEM
3
SYSTEM ANALYSIS
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
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
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.
6
HARDWARE & SOFTWARE REQUIREMENT
7
DATA DICTIONARY
mysql> create table property (proid int primary key, proname varchar (20),
proadd varchar (20), protype varchar (20), proarea int, proprice int);
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:
13
USECASE DIAGRAM
Sign up
submit
Property Inspection
Show property
selection
Facility show case
buy
Sell
14
ER DIAGRAM OF PROPERTY MANGEMENT SYSTEM:
Login User
Mob no.
By. Name
Seller name
Seller id
By. ID By. add
has
Buyer seller
property
P id P price
P name P type
P add
15
Activity diagram:
User login
approval
Buyer requirements
16
Collaboration diagram
1.login
property Database
2.login successful
7 registeration
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