Documentation
Documentation
BY:
SUPERVISOR:
AUGUST 2023
ii | P a g e
DECLARATION
This project is presented as part of the requirements for BSc. Information Technology
awarded by Pentecost University. I hereby declare that this project is entirely the result of
hard work, research, and enquiries. All sources of information have however been
acknowledged with due respect.
iii | P a g e
ACKNOWLEDGEMENT
iv | P a g e
ABSTRACT
In developing countries like Democratic Republic of Cong, the performance of real estate
remains unsatisfactory as many residential; commercial and Office spaces are unoccupied
since Real-estate agents cannot be consulted with ease and at one convenience. Acquiring an
apartment in Ilorin as a case study has been one of the most stressful task in the past few
years, take for instance the process of acquiring an apartment you have to call an agent, then
meet with him/her at a time that is convenient for him, if at all you get through to seeing him,
you now need to pay for a form that entitles you to see the properties at hand, then, the agent
takes you to see an apartment and if you don’t like that one he takes you to see another one
and if at the end you don’t like it. He calls another partner of his, and then you now start
virtually the whole process with the new agent after wasting your time, financial recourses,
transporting the agent around. The study will evaluate existing real estate management
systems and provide a remedial solution to challenges identified from various real estate
management systems by developing a real estate management web application. The system
will enable clients to view the properties of their choice without necessarily going on a hunt
for a property, in other words clients can always be in the comfort of their room, offices etc to
check out images of the apartment on the websites as to the one of their choices and on a
v|Page
Table of Contents
DECLARATION...................................................................................................................................3
ACKNOWLEDGEMENT....................................................................................................................4
ABSTRACT..........................................................................................................................................5
CONTENT TABLE..............................................................................................................................8
CONTENT OF FIGURES..................................................................................................................8
CONTENT OF APPENDIX................................................................................................................9
CHAPTER ONE................................................................................................................................10
INTRODUCTION..........................................................................................................................10
BACKGROUND TO THE STUDY...............................................................................................11
PROBLEM STATEMENT.............................................................................................................12
AIM AND OBJECTIVES OF THE STUDY.................................................................................12
SCOPE OF THE STUDY.............................................................................................................13
CHAPTER TWO................................................................................................................................14
LITERATURE REVIEW................................................................................................................14
SYSTEMS REVIEW.................................................................................................................14
REVIEW OF TOOLS................................................................................................................16
METHODOLOGY..........................................................................................................................17
CHAPTER THREE...........................................................................................................................20
METHODOLOGY..........................................................................................................................20
CHAPTER FOUR..............................................................................................................................25
DESIGN AND IMPLEMENTATION............................................................................................25
CONTEXT DIAGRAM..............................................................................................................25
DATA FLOW DIAGRAM.........................................................................................................25
USE CASE DIAGRAM.............................................................................................................26
ENTITY RELATIONSHIP DIAGRAM..................................................................................27
DATA DICTIONARY................................................................................................................29
CHAPTER FIVE................................................................................................................................31
SUMMARY, CONCLUSION AND LIMITATIONS..................................................................................31
INTRODUCTION.......................................................................................................................31
SUMMARY................................................................................................................................31
CONCLUSION..........................................................................................................................31
REFERENCES..............................................................................................................................33
APPENDIXES...................................................................................................................................34
vi | P a g e
APPENDIX 1.................................................................................................................................34
TENANT INTERFACE..............................................................................................................34
OWNER INTERFACE..............................................................................................................34
ADMINISTRATOR INTERFACE.............................................................................................34
APPENDIX 2.................................................................................................................................34
CODES.......................................................................................................................................34
vii | P a g e
CONTENT TABLE
CONTENT OF FIGURES
viii | P a g e
CONTENT OF APPENDIX
ix | P a g e
x|Page
CHAPTER ONE
INTRODUCTION
An estate can be defined as a large area or amount of land or property that is owned by one
person or by a family or corporation. Estate management is quite a broad term for a few areas
that include property management, surveying, business and finance and the built
environment. Closer ties are beginning to emerge between estate and property management
and business and financial practices, and essentially the subject is primarily concerned with
the valuation and management of land and buildings in the public and private sector. With
house prices rising at an astonishing rate over the last few years and now the recession, the
government has come under increasing pressure to be relieved from a 'housing crisis'. This
crisis has come about because of the rise in house prices which first-time buyers can no
longer afford and a lack of affordable housing for the citizens. Also, the rise in investment
buyers has meant that a lot of properties that those on average wages could have once been
able to buy, now have to rent instead. All of this has become an area of tremendous interest.
The government has predicted that more homes are needed, but where these houses are to be
built has also courted controversy. Estate Managers typically set the service standard and are
responsible for the hiring, training, and ongoing management of staff required to meet the
service needs of the household. In addition to personnel management, the administrative
functions are many. All related financial matters including accounting, budgets, and payroll
normally pass through the estate manager’s hands. Based on the size of the property, the
Estate Manager may wear many other hats.
Depending on the nature of the property, an owner of property has the right to
consume, sell, rent, mortgage, transfer, exchange or destroy their property, and/or to exclude
others from doing these things. A title, or a right of ownership, establishes the relation
between the property and other persons, assuring the owner the right to dispose of the
property as they see fit. Some philosophers assert that property rights arise from social
convention. Others find origins for them in morality or natural law. So, estate management
system is needed to take care of keeping records of the estate transactions in terms of
allocation, transfer of property, revoke, or sale of a property. Maintaining such record
manually will be cumbersome hence the need for an estate management system that will
1|Page
automate all estate transactions. This research work is sub divided into five chapters as
follows: chapter one which contains the introduction of the work, Chapter two contains the
literature review of existing systems, their successes and limitations shall also be discussed in
this chapter, and a literature review and of the methodology used. Chapter three contains the
analyses and design of the proposed system considering the methodology used. Chapter four
is where the actual implementation using the appropriate programming language is discussed,
and finally chapter five contains the summary, conclusion, recommendation, and limitations.
Land use, land valuation, and the determination of the incomes of landowners, are among the
oldest questions in economic theory (Shavell, 2004). Land is an essential input (factor of
production) for agriculture, and agriculture is by far the most important economic activity in
preindustrial societies. With the advent of industrialization, important new uses for land
emerged, as sites for factories, warehouses, offices, and urban agglomerations. Also, the
value of real property taking the form of man-made structures and machinery increases
relative to the value of land alone. The concept of real property eventually comes to
effectively encompass all forms of tangible fixed capital. With the rise of extractive
industries, real property comes to encompass natural capital. With the rise of tourism and
leisure, real property comes to include scenic and other amenity values. Starting in the 1960s,
as part of the emerging field of law and economics, economists and legal scholars began to
study the property rights enjoyed by tenants under the various estates, and the economic
benefits and costs of the various estates, Epstein (2007). This resulted in a much-improved
understanding of the:
Property rights enjoyed by tenants under the various estates. These include the right to:
· Transfer (alienate) some or all these rights to others on mutually agreeable terms.
· Nature and consequences of transaction costs when changing and transferring estates.
PROBLEM STATEMENT
2|Page
Housing is a basic need for all. Over the years, increase in population and income has led to
an equivalent increase in housing demand. Managing these demands manually will pose great
challenges and difficulties; hence there is a need to automate the management process.
Keeping record in an estate concerning lands, buildings and their owners has been a great
task to the government and the governed. Access to estate information proves difficult that
most times people are defrauded due to lack of property information. Illegal sales of lands
and houses without the consent of the owner are very common. Valuation of estate for the
purpose of paying tax to government is not achieved, hence the need for computerization of
estate management system.
The aim of this research work is to develop a real estate management system to make estate
information accessible to both government and individuals who may like to acquire building
or landed property.
1. To develop a web application that will keep information on land size, land location and
landowners in an estate
As the goal of this project is to develop a web application to manage real estate efficiently,
this system will be designed keeping in mind the conditions (easy to use, feasibility and user
friendly) stated above. The scope involves the development, implementation, and utilization
of technological solutions to streamline and automate real estate operations. The proposed
project would cover:
1. Developing a web application to effectively manage real estates in terms of listing and
advertising properties, managing a centralized database of properties, customer relationship
management, financial management, lease and tenancy management, etc.
3|Page
2. Implementing it on a computer system.
CHAPTER TWO
LITERATURE REVIEW
SYSTEMS REVIEW
The following are the systems we reviewed:
ZWANDAKO.com
Zwandako is a dynamic real estate management system that specializes in facilitating
seamless property advertising and connecting potential buyers to property owners. It offers a
comprehensive platform that caters to both property seekers and advertisers
For property seekers: Advanced Search Filters, listing details, Direct Contact, Sav and
Compare, Mobile Accessibility, User profiles.
LIMITATIONS
- Limited scope: it does not offer lease management, rent collection, or maintenance
tracking.
- No verification mechanism: the system lacks a verification process for property
listings or advertisers, this could potentially lead to fraudulent listings or unreliable or
unreliable advertisers.
4|Page
- Dependency on User Input: the accuracy and completeness of property listings
depend on the information provided by advertisers. Incomplete or outdated
information could lead to a frustrating experience for property seekers.
SUMMARY OF LIMITATIONS
Overall, the Zwandako system’s functionalities cater to the needs of property advertisers and
seekers by providing a user-friendly interface, facilitating direct connections, offering
detailed property information, and optimizing the property search and advertising processes.
However, the system possesses some limitations like limited scope, no verification
mechanism, dependency on user input.
Our new developed system seeks to address some of these limitations to ensure the
development of user-friendly and secure overall system. The system we develop provides
lease management, verification process for property listings, a chat to allow communication
within the system instead of limiting the system to only advertising.
FUNCTIONALITIES
Property listings, Advanced search filters, direct contact, property descriptions, image
galleries, favourites and saved searches, maps and location, user profiles, reviews and ratings,
notifications, support and help.
ADVANTAGES
Wide audience reach, User-friendly Interface, Detailed listings, responsive design.
LIMITATIONS
- Dependency on User Input: the accuracy and completeness of property listings
depend on the information provided by advertisers. Incomplete or outdated
information could lead to a frustrating experience for property seekers.
- Limited scope: it does not offer lease management, rent collection, or maintenance
tracking.
5|Page
- No verification mechanism: the system lacks a verification process for property
listings or advertisers, this could potentially lead to fraudulent listings or unreliable or
unreliable advertisers.
REVIEW OF TOOLS
- XAMPP server: XAMPP is a cross-platform web server that is free and open-
source. XAMPP is a short form for Cross-Platform, Apache, MySQL, PHP, and Perl.
XAMPP is a popular cross-platform web server that allows programmers to write and
test their code on a local webserver. It was created by Apache Friends, and the public
can revise or modify its native source code. It includes MariaDB, Apache HTTP
Server, and interpreters for PHP and Perl, among other computer languages.
6|Page
- CSS: CSS stands for Cascading Style Sheets. It is a style sheet language which is
used to describe the look and formatting of a document written in markup language. It
provides an additional feature to HTML. It is generally used with HTML to change
the style of web pages and user interfaces. It can also be used with any kind of XML
documents including plain XML, SVG and XUL.
METHODOLOGY
produce higher quality software, and higher quality of life for the development team. XP is
the most specific of the agile frameworks regarding appropriate engineering practices for
software development.
The technology you are using allows for automated unit and functional tests
7|Page
Extreme programming has given vital impetus to software development, but it’s not suitable
for every scenario and team. XP assumes that the customer does not have a clear picture of
the finished product at the beginning of the project. In these cases, the software can be agile,
This way, the customer is satisfied: The development team works with the customer to find
the right solution and the customer is involved in every step. Furthermore, developers can
implement projects as they see fit, instead of constantly making compromises. However, it’s
very difficult to use XP if the customer comes to the development team with a finished
Pair programming can present problems for small teams because they don’t have the
necessary resources for it. Plus, regular meetings with customers take up time that could be
spent on actual programming. In an ideal situation, that doesn’t matter: The final product will
clearly be better if the team has the time and resources they need.
However, in the real world, developers are constrained by limited budgets and clear
deadlines. Furthermore, the customer may lack the interest or ability to get involved to the
However, if the circumstances are right for extreme programming, a team can deliver an
excellent product with this method. Continuous testing results in stable software systems.
The iterative approach, combined with a minimalist mindset, ensures that teams develop only
Advantages Disadvantages
8|Page
Advantages Disadvantages
9|Page
CHAPTER THREE
METHODOLOGY
This chapter explain the set of guidelines, practices, and processes we followed to plan,
implement, test, deploy, and maintain the system. In this chapter, we will describe the
system’s specifications and design and describe the system requirements, database and
design, and user interacting interface.
The project’s methodology includes the various phases and procedures implemented in the
planning and executing processes, which also aided in choosing perfect programming
languages, to ease the project’s completion.
The required methodology for this project is the Extreme Programming methodology, which
is one the Agile methodologies.
PLANNING
10 | P a g e
The planning phase requires the gathering of information that sum up to building the system.
Time was taken to think of an effective way to ensure that the objectives of the project were
properly addressed. Measures that were taken in other to ensure that the proposed system
addresses every loophole in the manual process of acquiring listings. This measure involves
thinking and organizing (e.g., observations, interviews etc.) the activities required to achieve
the full execution of the system.
REQUIREMENT ANALYSIS
The system must be a secure site with 3 types of roles: clients, agents, and administrator.
Clients must be able to search for listings uploaded by agents via the location, price range etc.
Administrator must be able to register agents and give them access to the system. The
administrator must be able to view the agents’ profiles and agents: upload listings.
Develop a small number of web pages that use data from a MySQL database,
11 | P a g e
1. The system would reduce client and business stress and increase productivity.
2. The system would enable clients to always view/ find properties of their choice even
from their comfort zone.
3. The system would monitor customer’s relation which includes the frequency of their
visits, needs, and wants through the means of a database and to receive feedbacks.
4. The system would enable clients to make easy decisions from the information gotten
on the internet.
5. With the system in place potential customers and interested persons can contact the
establishment and make enquiries.
1. The system would be easy to use for all employees and users would adapt easily.
2. The system would be upgradeable.
3. The system would be easy to maintain.
4. The system would be compatible on all web browsers and mobile phone browsers.
5. The system would be scalable.
Design comes before coding; the design phase is the process of creating of a plan for a
system. The coding phase is the iteration process of writing codes for the functionality of the
system.
TOOLS USED
The tools to be used for the development of the proposed system and the task they perform:
12 | P a g e
3.3.1.2 DESIGN FEATURES OF THE DATABASE
The database will be created after defining the table and the fields that will be contained in
the tables. This process includes defining the data types of the data to be stored in each field
in the tables. Definition of the relationships between the various entities in the database (One
to One, One to Many, Many to Many). In the development of this software there is need for
data integrity and availability which explains the creation of relationships between various
tables in the database. The table below describes the data contained in the database record.
Field Name contains the attributes of an attribute, type describes the data type of the data to
be stored in the table, and the Length specifies the number of characters to be stored. Among
other tables below is a representation of the clients table and the property table.
Owner’s table
Tenant’s table
Property’s table
CLASS OF USERS
There shall be three (3) classes of users for the application. They are as follows:
This is the general view of the application for the clients to gain access to view the properties
available for sale, rent etc. A user would only have access to the front end of the application
which means they will only be privileged to view properties, contact the expert via a form but
they cannot change the content of the application.
This is the view where users with the administrator right can create, retrieve, update, and
delete the content on the application. The administrator would have basic programming skills
13 | P a g e
in HTML, JavaScript, PHP and MySQL server in other to have such right and enable the
effective running of the application. This is so because the changes that would be
implemented on the application through an authoring tool such as Dreamweaver, Notepad++
etc, and the database management would be done through MySQL server.
CHAPTER FOUR
Implementing a new system can be done in several ways which includes direct, phased, pilot
or parallel running.
CONTEXT DIAGRAM
Context diagrams show the interactions between a system and other actors (external factors)
with which the system is designed to interface. System context diagrams can clarify the
context which the system will be part of.[11]
15 | P a g e
the tasks, services, and functions required by a system/subsystem of an application.
Association: shows the participation of an actor in a use case. Extends relationship specifies
that the incorporation of the extension of use case is dependent on what happens when the
base use case executes. [9]
Let’s consider the use case of the following actors: admin, owner, and tenant.
16 | P a g e
connectors that visualize two important information: The major entities within the system
scope, and the inter-relationships among these entities. [10]
17 | P a g e
DATA DICTIONARY
A Data Dictionary is a collection of names, definitions, and attributes about data elements
that are being used or captured in a database, information system, or part of a research
project. It describes the meanings and purposes of data elements within the context of a
project, and provides guidance on interpretation, accepted meanings and representation. A
Data Dictionary also provides metadata about data elements. The metadata included in a Data
Dictionary can assist in defining the scope and characteristics of data elements, as well the
rules for their usage and application. [12]
Add_property
Attributes Data types Field size Constraints Description
property_id Int 10 PRIMARY Property Id
KEY
Country Varchar 50 NOT NULL
province Varchar 50 NOT NULL
Zone varchar 50 NOT NULL
District varchar 50 NOT NULL
City varchar 100 NOT NULL
vdc_municipality varchar 50 NOT NULL
ward_no int 10 NOT NULL
tole varchar 100 NOT NULL
contact_no Big_int 10 NOT NULL
property_type varchar 50 NOT NULL Type of the house
estimated_price Big_int 10 NOT NULL Price of the property
total_rooms Int 10 NOT NULL Number of rooms
bedroom Int 10 NOT NULL Number of bedrooms
living_room Int 10 NOT NULL Number of living rooms
kitchen Int 10 NOT NULL Number kitchen
bathroom int 10 NOT NULL Number of bathrooms
description Varchar 2000 NOT NULL Description of the property
Owner_id int NOT NULL Foreign key
owner
Attributes Data types Field Constraints Description
size
owner_id int 10 PRIMARY Id of the owner, autogenerated
KEY
full_name varchar 100 NOT NULL Name of the owner
email varchar 100 NOT NULL Email of the owner
password varchar 100 NOT NULL password
phone_no bigint 10 NOT NULL Phone number
address varchar 200 NOT NULL Address of the owner
id_type varchar 100 NOT NULL
18 | P a g e
id_photo varchar 1000 NOT NULL
tenant
Attributes Data types Field size Constraints Description
owner_id Int 10 PRIMARY KEY Id of the tenant, autogenerated
full_name varchar 100 NOT NULL Name of the tenant
email varchar 100 NOT NULL Email of the tenant
password varchar 100 NOT NULL password
phone_no bigint 10 NOT NULL Phone number
address varchar 200 NOT NULL Address of the tenant
id_type varchar 100 NOT NULL Type of the id card
id_photo varchar 1000 NOT NULL Photo of the id card
tenant
Attributes Data types Field size Constraints Description
owner_id Int 10 PRIMARY Id of the admin, autogenerated
KEY
email varchar 100 NOT NULL Email of the admin
password varchar 100 NOT NULL password
19 | P a g e
CHAPTER FIVE
SUMMARY, CONCLUSION AND LIMITATIONS
INTRODUCTION
This is the final chapter of the project work with the topic “design and implementation of a
real estate agency management system” This chapter contains the summary, conclusions, and
recommendation.
SUMMARY
The design and development of the real estate agency management system has been
presented as “Teamlet”. It shows that the internet system is a system that connects literally
billions of people to communicate with each other worldwide almost instantaneously. Being
the largest network we have in our time the system “Teamlet” was developed to integrate
clients with agents of real estate and enable them to rent, buy or sell houses at their
conveniences. The system has made it easier for the agency organization to showcase its
services and provide information link between potential/existing clients.
CONCLUSION
The design and implementation of this project information and knowledge gathered from
clients or individuals seeking apartments, a conclusion was drawn which is that the design
has closed the gap between the Agencies and the potential/existing clients. It gives room for
clients to cut through the tedious manual process of acquiring apartments and properties, it
also reduces three types of cost which are search cost, processing cost and transaction cost.
However, loading time was quite long; the design also enables potential customers (clients)
and interested persons to contact the agency in charge for enquires and feedback mechanisms.
It is observed that some pages required more time to load due to the graphics attached to
them.
RECOMMENDATION
In respect to the above conclusion I hereby recommend that the system be employed by
various agency organizations as it will not only pull traffic, be an avenue of marketing
multiple properties to a wider audience at a time but it will also help clients to view the
20 | P a g e
various properties and pick one that best picks their interest, and reduce the stress of going
from one agents office to the other, from one apartment to the other, it will also reduce cost
on the client side.
21 | P a g e
REFERENCES
[1] https://www.educba.com/what-is-xampp/
[2] https://www.agilealliance.org/glossary/xp/
#q=~(infinite~false~filters~(postType~(~'post~'aa_book~'aa_event_session~'aa_exper
ience_report~'aa_glossary~'aa_research_paper~'aa_video)~tags~(~'xp))~searchTerm~
'~sort~false~sortDirection~'asc~page~1)
[3] www.extremeprogramming.org:
[4] https://www.tutorialspoint.com/javascript/javascript_overview.htm
[5] https://www.javatpoint.com/what-is-css
[6] https://www.hostinger.com/tutorials/what-is-mysql#What_is_MySQL
[7] https://www.tutorialspoint.com/php/index.htm
[8] https://www.investopedia.com/terms/h/html.asp
[9] https://www.javatpoint.com/uml-use-case-diagram
[10] https://www.visual-paradigm.com/guide/data-modeling/what-is-entity-relationship-
diagram/
[11] https://uwaterloo.ca/ist-project-management-office/tools-and-templates/tools/context-
diagram
[12] https://library.ucmerced.edu/data-dictionaries
22 | P a g e
[13]
APPENDIXES
APPENDIX 1
TENANT INTERFACE
OWNER INTERFACE
ADMINISTRATOR INTERFACE
APPENDIX 2
CODES
ADMINISTRATOR LOGIN
AMINISTRATOR DASHBOARD
TENANT REGISTER
TENANT LOGIN
OWNER LOGIN
OWNER DASHBOARD
OWNER INDEX PAGE
23 | P a g e