Final Document Proggg1111llll

HAWASSA UNIVERSITY
INSTITUTE OF TECHNOLOGY
FUCULITY OF INFORMATICS
DEPARTMENT OF COMPUTER SCIENCE
TITLE: - Hawassa City Online Condominium House Management System
GROUP MEMBERS ID EMAIL

Temesgen Atire Evcs/146/09 atiretemesgen@gmail.com
Tamirat Gashew Evcs/214/09 tgashe64@gmail.com
Natinael Feleke Evcs/210/09 natifele489@gmail.com
ADVISOR: UMER N.
DATE MAY 17, 2021

Table of Contents
List of tables...................................................................................................................................................... iv
List of figures ..................................................................................................................................................... v
Acronym ........................................................................................................................................................... vi
Acknowledgment ..................................................................................................................................... vii
Abstract ...........................................................................................................................................................viii
CHAPTER ONE ................................................................................................................................................ 1
Introduction .................................................................................................................................................... 1
1.1: Backgroundof The Study ........................................................................................................................ 1
1.2.Statement of The Problem........................................................................................................................ 3
1.3. Objectives of the Project ......................................................................................................................... 4
1.3.1. General Objective ............................................................................................................................ 4
1.3.2. Specific Objectives .......................................................................................................................... 4
1.4. Scope of the Project ................................................................................................................................ 5
1.5. Limitation of the project ......................................................................................................................... 6
1.6. Methodology ........................................................................................................................................... 6
1.6.1. Data collection methodology ........................................................................................................... 6
1.6.2. System Analysis and Design Methodology ..................................................................................... 7
1.6.3. System Implementation Methodology ............................................................................................. 7
1.6.4 Testing and Deployment Methodology............................................................................................. 7
1.6.5 Development Environment ............................................................................................................... 8
1.6.6 System requirements ......................................................................................................................... 9
1.7. Summary ................................................................................................................................................. 9
CHAPTER TWO ............................................................................................................................................. 10
DESCRIPTIONS OF EXSTING SYSTEM ................................................................................................ 10
2.1. Introduction ........................................................................................................................................... 10
2.1.1. Activities of the system ................................................................................................................ 11
2.2. Proposed System Description ............................................................................................................... 11
2.3. Strength of Existing System.................................................................................................................. 13
2.4. Weakness of Existing System ............................................................................................................... 14
2.5. Summary .............................................................................................................................................. 15
CHAPTER THREE ......................................................................................................................................... 16
SYSTEM FEATURES................................................................................................................................. 16
3.1. INTRODUCTION ................................................................................................................................ 16
3.2. Functional Requirements ...................................................................................................................... 16
3.3 Non-Functional Requirements ............................................................................................................... 17
3.4. Analysis Models.................................................................................................................................... 18
3.4.1. Introduction .................................................................................................................................... 18
3.4.2 Use case modeling .......................................................................................................................... 19
Figure 3.1 Use case diagrams for proposed system ................................................................................... 20
TABLE 7 : USE CASE DESCRIPTION FOR REGISTER RESIDENT ........................................................ 22
3.4.2. Sequence diagram .......................................................................................................................... 31
3.4.3. Activity diagram ............................................................................................................................ 39
3.4.4. Class Diagram ................................................................................................................................ 47
3.4.5 User interface design ....................................................................................................................... 49
3.5: summary................................................................................................................................................... 52
CHAPTER FOUR............................................................................................................................................ 53
SYSTEM DESIGN ...................................................................................................................................... 53
4.1 INTRODUCTION ................................................................................................................................. 53
4.2 Purpose of the System Design Document .............................................................................................. 53
4.3 Scope ...................................................................................................................................................... 54
4.4 Architectural Design .............................................................................................................................. 54
4.4.1. Logical View .................................................................................................................................. 55
4.4.2. Process View .................................................................................................................................. 55
4.4.3 Deployment View ........................................................................................................................... 55
4.5.Data Base Design ................................................................................................................................... 57
4.6: summary.................................................................................................................................................... 58
CHAPTER FIVE ............................................................................................................................................. 60
CONCLUSION AND RECOMMENDATION ........................................................................................... 60
5.1.Conclusions ............................................................................................................................................ 60
5.2 Recommendation for future work .......................................................................................................... 60
REFERENCES ............................................................................................................................................ 62
Appendix ...................................................................................................................................................... 63
List of tables
TABLE 1: DESCRIPTION OF HAWSSA CITY ...................... ERROR! BOOKMARK NOT DEFINED.
TABLE 2: HAWASSA SUB CITIES ............................................................................................... 2
TABLE 3: HARDWARE’S REQUIREMENTS .................................................................................. 8
TABLE 4: SOFTWARE REQUIREMENTS ...................................................................................... 9
TABLE 5: COMPARISON BETWEEN EXISTING AND PROPOSED SYSTEMS .................................. 15
TABLE 6: USE CASE DESCRIPTION FOR LOGIN USE CASE............................................................ 20
TABLE 7 : USE CASE DESCRIPTION FOR REGISTER RESIDENT .................................................. 22
TABLE 8: USE CASE DESCRIPTION FOR REGISTER APPLICANT ONLINE ................................... 23
TABLE 9 : USE CASE DESCRIPTION FOR REGISTER FINISHED HOUSE ....................................... 24
TABLE 10 : USE CASE DESCRIPTION FOR DRAW LOTTERY ...................................................... 25
TABLE 11 : USE CASE DESCRIPTION FOR NOTIFICATION ......................................................... 26
TABLE 12: USE CASE DESCRIPTION FOR PAYMENT ................................................................. 26
TABLE 13: USE CASE DESCRIPTION FOR CONTROL PAYMENT ................................................. 28
TABLE 14: USE CASE DESCRIPTION FOR MANAGE APPLICANT ................................................ 29
TABLE 15: USE CASE DESCRIPTION FOR MANAGING INFORMATION. ...................................... 30
TABLE 16: APPENDIX ............................................................................................................. 63
i
List of figures
FIGURE 1 : USE CASE DIAGRAM DESCRIPTION ......................................................................... 20
FIGURE 2: SEQUENCE DIAGRAM FOR CHMS ADMININSTRATOR .............................................. 35
FIGURE 3: SEQUENCE DIAGRAM FOR REGISTERING RESIDENT ................................................ 33
FIGURE 4: SEQUENCE DIAGRAM FOR KEBELE ADMINISTRATOR .............................................. 34
FIGURE 5: SEQUENCE DIAGRAM FOR REGISTER FINISHED HOUSE .......................................... 35
FIGURE 6: SEQUENCE DIAGRAM FOR DRAW LOTTERY ............................................................ 36
FIGURE 7: SEQUENCE DIAGRAM FOR NOTIFICATION ............................................................... 37
FIGURE 8: SEQUENCE DIAGRAM FOR MANAGE APPLICANT ..................................................... 38
FIGURE 9: ACTIVITY DIAGRAM FOR LOGIN ............................................................................. 39
FIGURE 10: ACTIVITY DIAGRAM FOR REGISTERING RESIDENT................................................ 40
FIGURE 11: ACTIVITY DIAGRAM FOR REGISTERING FINISHED HOUSE ..................................... 41
FIGURE 12: ACTIVITY DIAGRAM FOR DRAW LOTTERY ............................................................ 42
FIGURE 13: ACTIVITY DIAGRAM FOR NOTIFICATION .............................................................. 43
FIGURE 14: ACTIVITY DIAGRAM FOR MANAGE APPLICANT .................................................... 44
FIGURE 15: ACTIVITY DIAGRAM FOR MANAGE APPLICANT MODIFICATION ............................ 45
FIGURE 16: ACTIVITY DIAGRAM FOR MANAGE ACCOUNT BY ADDING .................................... 46
FIGURE 17: ACTIVITY DIAGRAM FOR UPDATE ACCOUNT ........................................................ 47
FIGURE 18: SAMPLE OF CLASS DIAGRAM ................................................................................ 48
FIGURE 19: SAMPLE OF USER INTERFACE DESIGN ................................................................... 49
FIGURE 20: USER INTERFACE FOR RESIDENT REGISTRATION FORM ........................................ 50
FIGURE 21: USER INTERFACE SAMPLE FOR MANAGE ACCOUNT PAGE .................................... 51
FIGURE 22: USER INTERFACE SAMPLE FOR USER REGISTRATION PAGE .................................. 52
FIGURE 23: DEPLOYMENT DIAGRAM....................................................................................... 56
FIGURE 24: DATABASE DESIGN DIAGRAM............................................................................... 58
ii
Acronym
BR Business Rule
MWP Manage winner payment
MRI Manage resident information
HCCHMS Hawassa city condominium house management system
MA Manage applicant
MAcc Manage account
RRI Register resident information
KOA Kebele office admin
CHA Condominium house admin
RFH Register finished house
PHP Hypertext Preprocessor
HTML Hypertext Markup Language
CHMO Condominium House Management Office
CHMA Condominium House Management Administrator
UC-ID Use Case Identification Number
HTTP Hypertext Transfer Protocol
iii
Acknowledgment
First of all, we would like to thank our God, who gives us love, patience, healthy, wisdom and ability
to walk through all the problems and obstacles during the period of our study. Then we would like to
thank our advisor, instructor Umer for his constructive opinion and willingness to participate in each
part of our project and his effective direction, assistance and guidance for the accomplishing of this
project. We also want to thank Ato Addisu, officer of Hawassa housing development agency, who
gave us the required information about the office.
Finally, we would like to express love, thanks, appreciation, and respect to our families and friend.
In addition, we would like to thank the teaching staffs of Information system who have contributed
wholly to the success of this project.
iv
Abstract
The purpose of this project is to fulfill the requirement of fist degree of information system as final year
project in order to graduate. Now a day’s ,using computers to simplify boring manual work is significant
because using computer gives many benefits from those benefits speed accuracy, storage capacity, security,
flexibility, cost reduction and minimizing boring manual work. HCCHMS was limited on manual works. This
has limitations for the residents wasting time in front of the office to register.
This project document deals with Hawassa city online condominium house management system
development specifically project proposal system analysis, design, implementation methodology,
testing, maintenance, and deployment of the system and partial conclusion and recommendation of
full Hawassa city online condominium house management system. The propose system maintain
necessary information of the Hawassa housing development agency.
Hawassa city online condominium house management system mainly provides effective and fast data
processing, registration, notification drawing lottery service, and placement.
Hawassa city web based system of managing applicant house information in house development
agency setting is expected to help various services keep an updated data on the status of their
information. In designing and analyzing such a system, object oriented designing and analysis tool
and technique has been employed.
Key word: Hawassa, condominium, php, Dreamweaver, XAMP
v
CHAPTER ONE
Introduction
Now a day, most people are having familiarity with computer and computer based applications.
Many organizations and individuals have their computer based applications for the purpose of
running their business, to perform different activity. The aim of this project is to develop an online
condominium house management system in Hawassa city.
The Hawassa City administration has opened an office Housing Development Agency which has
four departments; Housing Transfer and Administration,Construction and supervision, Support,
Process and Design of condominium houses. Currently, the office process data manually, and this
manual processing system has many drawbacks. Hence with a gear of solving these setbacks the
team are going to develop an online condominium housing management system. After completion
the project is expected to solve the problems that are affecting the condominium housing
development agency offices. Since it is an online system it will reduces costs, time to travel to the
offices, work overload and it also minimizes the space used to store the data. Besides, it enables
applicants online registration, search, update applicants’ data, online drawing lottery, and
placement and register finished condominium houses. the system is not fully automated because it
uses some parts of manually. when registration is done and when they pay their payments. This
are done manually because the stem does not have full information when registers online so the
information of applicant is store manually and online payment is not perfect in the country.
1.1: Backgroundof The Study
The Ethiopian government is trying to solve shortage of house for the low income community
living in the urban area. One solution for this shortage program is condominium housing
development project. Condominium housing is the name given to the forms of housing contract
when each resident house had own their individual unit. All homeowners own all of the land on a
condominium site. A condominium association that jointly represents ownership of the whole
employing strict management to ensure funding from each homeowner under takes the external
maintenance of the roof and walls.
Condominium house owners can permit for rent out their home to residents, although leasing rights
may be subject to condition or restrictions set forth in original declaration, such as rent cap on the
total number of units a community can lease at any one time or otherwise as permitted local law.
Hawassa city Online condominium house management system Page 1

In Ethiopia, there was some cities has this condominium house system,From those listed countries
are Hawssa one of the biggest cities and regional capitals of Ethiopia, Hawassa city administration
one that which uses this condominium house system
TABLE 1: DESCRIPTION OF HAWSSA CITY
Hawassa city Specification

Location In Sidama Regional state
The shores of lake Hawassa city Covered in great rift valley
The distance From Addis Ababa 273 km south
Hawassa city, which is the economic and cultural hub of the region, is divided into 10 sub cities
which in the table below:
TABLE 2: HAWASSA SUB CITIES
.
City Sub cities
Tabor
Hayikdar
Menehariya
Misrak
Hawella Tulla
HAWASSA
Bahil adarash
Addis ketema
Mehalketema
Datu
Ceffe
In recent times, there have been increasing demands for housing and housing land in the town,
according to the official of the municipality. However, as the kebele (smallest administrative body
within the sub cities) and public houses constructed by the municipality have been totally
inadequate in meeting the housing demand, many people are forced to live in crowded conditions
by paying rent for private houses or rooms. Hawassa city condominium house management office
is among the offices that are found under Hawassa city administration. It was established before
between 2005-2006 E.C. The Hawassa city administration office provides different functions for
its surrounding it distributes houses especially for low income residents. Besides that the offices
improves the living standard of low incoming resident by creating of employment opportunities.
The project generated the required data from primary sources using two types of questionnaire one
for renters and the other for home owners. A multi stage sampling procedure was used to select
the condominium sites and eligible respondents. Hawassa city administration was purposively
selected being one of the cities with a high shelter poverty affordability problem in Southern
Ethiopia. There are around 11 condominium sites in the city administration, all sites were
identified since most of them were reported completed and all of the units transferred to
beneficiaries.
The office has the following missions: -
 Provision of affordable housing for low and medium income of the city inhabitant and
ensuring resident security.
 Improve the leaving standard of city resident by expanding employment creation.
 Provide premium condominium and commercial units that will be result to enhanced
value of the client’s lives resources and overall business.
 Improving small industries to big industries.
1.2.Statement of The Problem

In Ethiopia, there is lot of problems from those problems the house problem is one issue. To solve
this problem the government gives the opportunity to reduce the shortage of house a condominium
house system is started in many countries. In addition, the condominium system is done in many
universities by different researchers. The team refer from the Debrebirehan universities document
. The team tries to solve the problem, which they cannot solve. They cannot develop the payment
method. The registration is online due to this time there is a person who don’t have knowledge
about the technology. When the notification is released the person cannot read the notification, so
we develop the system is to send a message on by his phone number in place of accessing online
system. Currently the office is using manual handling system in its day to day activities which has
many problems. From those problems some are described below : -
 Problem in distributing condominium house:-Since they do manually, it is difficult to
know the occupied class and unoccupied class surely.

 Problem in management:-since there are many documents in the office, it is hard to
manage such huge data manually.
 Data Redundancy:-Since there is no organized data base there is problem of giving more
than one house for a single person.
 Lack of accuracy and loss of document:-Since registration is handled manually, there is
chance of getting two houses for single family like husband and wife and loss of applicant
and contractor data.
 Lack of security:-Since the office use manual system, the mechanism of data handling is
unsecured.
 They need large number of human resource to process office job.
1.3. Objectives of the Project

1.3.1. General Objective
The general objectives of the project to develop online condominium house management system
for Hawassa city. This system to automate partially the current system and improve the
management in terms of speed, accuracy, data handling, security, stability and adaptability.
1.3.2. Specific Objectives
The Specific objectives of the system is to do the operations that are manually worked. It uses
digital system by converting the manual system. Therefore, the team can achieve he general
objective by fulfilling the specific objective listed below : -
 Study factors related with HCCHMS.
 Collect the data of existing system.
 Analyze the existing system.
 Design a new system.
 Implementation of the proposed system.
 Testing the proposed system.
 Deploy the proposed system.
 Maintain the new system.
 Giving recommendation for future work.

1.4. Scope of the Project
The scope of the system is , it can reduces the existing system problem’s in many ways. The
system focus on online and the applicants can use a technology on hand phone and computer so to
get more information and access to house they uses this the Hawassa city online condominium
house management. The online condominium house management system will cover only in
Hawassa city and will perform the following activities:
 Registration of resident: the proposed system will register full information of Keble
resident that help the resident in order to be applicant for condominium house.
 Online Registration of Applicants:-The proposed system will registers all the applicant
information that is used to get the condominium house.
 Register Finished Condominium houses:-register the finished condominium houses that
are found in different sites. Besides, it helps to know the number of applicant relative to
the number of finished condominium house.
 Update Applicant’s Data: It updates the applicant information when needed.
 Search Applicant’s Data: To search applicant data within short period.
 Draw Lottery: The draw lottery helps to identify the applicant that gets the condominium
house. This is used because the number of finished house is not balanced with the number
of applicant.in addition it gives a priority for who pay full payment, who was a resident in
that place before the house is building and who pays 95% a payment.
 Notification:-those applicants who have own lottery houses are not expected to come to
the office. Notification will be done by simply login to their account and search winning
status by using resident id as a primary key.
 Control applicant payment status:-Hawassa Condominium house administrator can
controls the applicant payment status regarding condominium house from prepayment until
the applicant finish the payment by just making a connection with the bank administrator.
 Charitable priority: -When drawing the lottery there is a priority for who will apply and pays
the payment and a resident who can live the place where the condominium is built has a priority
to get house or they will get a replacement for their place or thirdly who pays the 95% will get
the lottery and others will wait the next season, but not include nation and religion.

1.5. Limitation of the project
The system is limited only in the process of condominium house management of the Hawassa city.
The system does not include the following:-
The system may not automate fully: - because the system does not include online
payment for applicant, who wants to register to get house due to online payment system is
now a day, itself a big system, so it is not include in the project. The proposed system
limitations are happen because of the following reasons:
 Time:-Is the main factor of limitation the proposed systems that limit its performance
because while the team are developing the system it takes more time and the team
may not get enough time to automate the system.
 Security: since its difficult paying large amount of money online because of different
security issue , its vulnerable
 Accessibility: -the team do not get full information about Hawassa cities because the
team limited in one place so there is a lot of problem that the team cannot cover.
1.6. Methodology
Methodology is the systematic, theoretical analysis of the methods applied to a field of study. It
includes the theoretical analysis of the body of methods and principles associated with a branch of
knowledge. Typically, it encompasses concepts such as data collection paradigm, theoretical
model for analysis and design follows, phases in software development, testing and deployment.
1.6.1. Data collection methodology
Any project work is only as good as the data that drives it, so choosing the right technique of data
collection can make all the difference. In addition, there are varieties of methods to use when
gathering primary and secondary data for the project. Therefore, the team used the data collection
methods are listed below:
 Observation:-Observation is common methods of scientific research to collect the data.
The team used observation to know how the existing system work, to know exactly how
different sub offices and how office member are handling the work in the office.
 Interview:-Interview is particularly useful for getting the history behind the participant’s
experiences. The team used interview to get information about the existing system for

developing the project. The interview were conducted on the head of city condominium
house management office and staff members.
 Document Analysis: - Document analysis is used to understand how the system is working.
The team used this method to know all about the staff mission, vision, function and overall
of their work in short and brief.
1.6.2. System Analysis and Design Methodology

In the project analysis and design phase the team used unified modeling language (UML): because The
UML is used to represent a collection of best engineering practices that have proven successful in
the modeling of large and complex systems. The UML is a very important part of developing
objects oriented software and the software development process. The UML uses mostly graphical
notations to express the design of software projects. Using the UML helps project teams
communicate, explore potential designs, and validate the architectural design of the software.
 The data analysis model applied in this project is an object-oriented approach. For
designing purposes an object-oriented designing were applied in this project. Since it is
easy to maintain if any error is occurred.
 Regarding implementation, PHP programming language will selected for this project since
it can be dynamically changed.
 The system development model were used in this project is Component Based Model
for the reasons that component based model Uses object-oriented paradigms. Classes
are considered as component or module and combination of the components will give
us the web based system software. It is fast and widely used model due to reusability
of codes.
1.6.3. System Implementation Methodology
The team will observe for develop and design system to using Agile Model because group of
iterative and incremental software development methods. It encourages flexibility and speed in
responding to change. It requires collaboration between self-organized, cross-functional teams to
generate requirements and solutions. Generally, this case Agile is best choice for us.
1.6.4 Testing and Deployment Methodology
There are different methodologies for software development process. Among these, the team
preferred to employ agile methods for various reasons. Agile methods are incremental

development methods that focus on rapid development, frequent releases of the software, reducing
process overheads and producing high-quality code. They involve the customer directly in the
development process.Agile is a software development methodology to build software
incrementally using short iterations of 1 to 4 weeks so that the development process is aligned with
the changing business needs. Instead of a single pass development of 6 to 18 months where all the
requirements and risks are predicted up front, Agile adopts a process of frequent feedback where
a workable product is delivered after 1 to 4-week iteration. Agile software development has the
following characteristics:
Light Weighted methodology
Small to medium sized teams
vague and changing requirements
changing techniques
Simple design
Minimal system into production
1.6.5 Development Environment
Software development environment refers to the collection of hardware and software tools a
system developer uses to build software systems.
TABLE 3: HARDWARE’S REQUIREMENTS
HARDWARE Specification
Computer 500 GB Hard Disk,4 GB, core i3 2.30 GHZ,64 bit OS
Monitor To display the out put
Keyboard To input the data
Mouse To input the data
Network cable used to internet access
Flash disk To transfer data from one place to another
Printer To print the documentation
Hard disk To store a data
Cpu To do the main programs

TABLE 4: SOFTWARE REQUIREMENTS
SOFTWARE Specification
XAMPP,MYSQL used to create the database of the project

Dezign To develop database diagram
Edraw max 8,Ms office Visio 2003 To develop UML diagram
Notepad++,Sublime text To write the system code
Javascript ,HTML 5,CSS3 used to validate data and write the

system code
Ms office word 2016 To write the documentation of the
project
Ms office ppt 2016 Used for representation shortly and
briefly the project
Google chrome,Opera,Mozilla uses to access internet and testing system
1.6.6 System requirements
In this project the system requirement is used efficiently, all computer software needs certain
hardware components architecture, processing power, memory, secondary storage, display adapter
and other software resources platform, API, Drivers and Web Browsers to be present on a
computer.
1.7. Summary
Many organizations and individuals have their computer-based applications to perform different
activity. The main aim of the project is to develop a web based condominium house management
system in Hawassa city. The City administration has Housing Development Agency which has
four departments; Housing Transfer and Administration, Construction and supervision, Support,
Process and Design of condominium houses. Currently, the office process data manually, and this
manual processing system has many drawbacks. Hence, with a gear of solving these setbacks the
team are going to develop a web-based condominium housing management system. After
completion, the project is expected to solve the problems. Since it is a web, based system it will
reduces things. Besides, it enables applicants online registration, search, update applicants’ data,
online drawing lottery, and placement and register finished condominium houses. The office
missions have to Provision of affordable housing for low and medium income of the city
inhabitant, to ensuring resident security, to improve the living standard of city resident by
expanding employment creation and to Improving small industries to big industries.

CHAPTER TWO
DESCRIPTIONS OF EXSTING SYSTEM

2.1. Introduction
Hawassa City Administration condominium house management system is now a day’s plays great
role on shortage of house by giving different services to the residents.
 Currently Hawassa city condominium house management system is using manual based
system.
 Manual based system is traditional way of data and information handling where paper
are used for the purpose. There is intensive human labor. Events and objects are written
on papers that are kept in files.
 Each of the files containing various kinds of information, which is labeled and stored in
much cabinet. The cabinet cannot be kept on safe place for security purpose based
on the sensitivity of the information contained in it. The existing system difficult to update
retrieval and integrate.
 Most of the operations are done manually like send data, registering data, taking actions
against, view status etc. These are done manually, and it would take time. This is
ineffective, inefficient and unsafe .it reduces the quality of the services. The current system
has many problems like: -
 Registration of new applicant as well as search for existing applicant record also paper
based and currently registering the applicant on a computer but cannot send data from
services office to offices.
 The applicant document is stored in the catalog according to the registration assigned to
the house. It takes time to search applicants file, it needs high cost, when it done in manual
system and paper based recording applicants history are cannot be claimed as secure.
 The paper based existing system data might be damaged by different cases like fire and
natural cases. File stored in room, as a result, the file may be fade because of long time
storing on the shelf. Therefore, developing an automated web based condominium house
information system is found to be important to address those problems.

2.1.1. Activities of the system
Ethiopian government is planned reduce the shortage of homeless people by giving the chance to
get house by paying some percent of the payment, this system is done by the residentially of the
place .to do this the Hawassa city uses manual system.it has some activities when the process is
done .from this activities some are listed here that are manually operated are:
Registering applicant
Storing applicant’s data.
Announcement
Registering result of lottery
Manual notification by using notice board.
Gives payment form for applicant to pay in the Ethiopian national bank.
Control the status condominium houses.
Draw lottery manually.
Placement of lottery winners.
2.2. Proposed System Description

The proposed system is designed in order to reduce the problem arise in existing system. This
system is not fully automated because of some system are done manually .when applicant registers
the criteria is needed this criteria is present in manually and the payment system is not work
because the system is not applicable in the country.by this justification the proposed system is not
fully automated.th system has three administrators and sub administrators.
The three administrators are listed below:
1. The kebele administrator
 Registers on the Hawassa city online condominium house management system web
site. The peoples are going to register on the system must be residents of Hawassa
city. If they come from other city, they must live in Hawassa for minimum 6 month.
 The kebele administrator has the permission to add resident information, delete and
modify resident information.
 Keble administrator record all the necessary information of the resident.

 Kebele administrator has the privilege for creating deleting, updating account with
Keble administrator user type.
 Applicant in proposed system is any resident of Keble who had registered in Keble
database with full information.
 If the applicant information is recorded in Keble database,
 applicant can apply for house in the online condominium house management
system by creating there account or
 signup for accessing the application form and must pay the pre-payment by
using external system bank, and
 As a business rule, condominium house management system and all applicant
must have bank account number on specific bank.
2. The Hawassa city condominium house management administrator performs
different activities on this system.
 Some of the activities that are performed by the condominium house management
system administrators are
 The registers user type of other condominium house administrator and to the user
type.
 The users or administrators have user type, user name and password to log in to
their administration page.
 Moreover, on this system the condominium administrators enables to register
houses that are finished and ready to give services for the residents with their
block number and address that the house is constructed also by entering related
information about house.
 After that by equating the number of houses available and applicants, the system
draws lottery to select winners from the applicants.
 Then next to this step, winner’s notification is send to the winners of house by
their e-mail address.
 The Hawassa city online condominium house management system
administrators can view information related to house, sites, blocks and winners
of condominium and other information is related to condominium house.

 Applicant have to modify and update these information’s available in the system
that are related to condominium houses information’s.
 Winner of the condominium house lottery must pay-payment at least monthly
by opening payment page and selecting long division payment type.
3. The Hawassa city condominium house management administrators of applicants
 Have applicant payment status controlling page on the Hawassa online condominium
house management system and on this system:
 The administrator can view and control who are going to pay for condominium
house.
 The administrator is also able to show the payer information, modify payer’s
information from the database, and update payment, when applicant add
payment.
 Generally, the system will only allow those residents who are registered by the
kebele administrator on the Hawassa online condominium house management
system.
 To apply the applicants are required to enter resident id number and last name
for the purpose of security.
 Selected last name of the applicant inserted must match with the last name of
the applicant in the database with that resident id.
 While the applicant is trying to apply to condominium house, if they did mistake
the system shows error message to the applicant.
 If one applicant is already applies one’s, applicant is not allowed to apply again.
2.3. Strength of Existing System

The strengths of the existing system is it uses all mechanism to handle the data and management
system together when registering they uses the kebele id card and residential of the person in the
city .Some of available strength which are performed under that related with housing information
system in existing systems have the following features:-In the existing system, there are three
bureaus that are concerned with the issue of giving and distributing the condominium houses for
applicants. The offices are-

 Kebele’ Offices: provide the following service for the resident. Register resident that need condominium
house. It passes all the resident applicant information to the city administrator office of housing
development agency.
 Hawassa City Municipalities Office: The condominium housing management offices ask information
about the customer to the Hawassa city municipality’s offices and the offices responsibilities is checking
whether any house is register by the customer name or by his family. If the customer registers any house
the applicant’s will not accepted. If there is no house registered by the applicant the condominium housing
management offices permits to get the house of condominium house for the
applicant.
 Hawassa City Condominium House development Office: Collect applicant data that is already
registered in all kebele’s of the city and receive the constructed condominium houses from Condominium
houses construction agency. Then draw the lottery in order to get a condominium
houses. When the winner of the lottery pays the money, pre-payment or full payment. After these, this
agency in turn distributes the condominium house for the applicant that won the lottery. The office also
gives services, maintenance and infrastructure to the applicant.
2.4. Weakness of Existing System

The existing system has many weaknesses. When they registers and after registers applicants it
has many weakness with regarding of some issues this issues are listed below:
 It takes long time to search data:- When searching data it takes time to get the applicant
data is because there is a lot data is stored together in cabinet form.to search users data
can take time.
 Lack of Effectiveness:- Since it operable, manually it uses large amount of space to
store data.
 Lack of portability’s:- The data cannot be transferred from one place to another because
the uses paper system so applicant data should be stored only in cabinet form
 Lack of performance:- In terms of performance, the existing system is not as satisfactory
because it is time consuming, energy consuming and does not support the employee to
remember their appointments and their status in anywhere anytime fashion. Searching files
from some documents can take time.
 Input and Output drawbacks:- The information of a certain applicant could be
redundant and inflexible and these inputs may lead to create confusion and unnecessary

and produce inaccurate output. Generally, there is registration or add applicant is
redundant and again applicant folder findings are much take time.
 Security and Controls:- Since every file and record of the status of applicant information
is stored in the manual way, it is difficult to control and secure these manual files/data.
The existing manual system is not secure there is no authentication mechanism for
documenting information.
 Efficiency - It is also difficult to list all the appointments with applicants on the paper, the
paper may lose. The response time not very small and take more time. The existing system
has low efficiency of speed, conception of time, utilization of resource because it works
manually.
2.5. Summary
Under this chapter the team wants to describe the comparison between the two in shortly.The proposed
system is designed in order to reduce the problem arise in existing system. This system has 3
administrator and sub admins.
TABLE 5: COMPARISON BETWEEN EXISTING AND PROPOSED SYSTEMS
Existing system Proposed system
Poor performance Better performance

Low security Uses better secured mechanism
Less Storage More storage
Less efficiency More efficiency
Nearest to corruption minimize corruption
It takes time and large human source It takes less time and human source
The strengths of the existing system is it uses all mechanism to handle the data and management
system together when registering they uses the kebele id card and residential of the person in the
city. In the existing system, there are three bureaus are concerned with the issue of giving and distributing
the condominium houses for applicants. Finally, the team wants to describe the weakness of the existing
system by some issues

CHAPTER THREE
SYSTEM FEATURES
3.1. INTRODUCTION
In this chapter, the team studied the existing system deeply, since it is necessary to know the existing
working system of office to develop a better system. When the team studied the existing system,
the team gave emphasis for here under listed questions:
 How the existing system is working?
 What kind of method they use to handle applicant data?
 In what way the office is handling resident complaint.
 What is the business rule they use?
After studying the existing system, team also determined the requirement or the feature that must be
included in the proposed system. Furthermore by analyzing the current system, the team could also
estimate how the propose system solve the setbacks of the existing system.
3.2. Functional Requirements

Functional Requirements are those that refer to the functionality of the system, i.e., what services it
will provide to the user. It is Statements about service that the system should provide, and also how the
system should react to particular inputs and how the system should behave in particular situations.
 Register applicant online: The system would be able to register applicants’ who needs a
condominium house online. Without coming to the condominium office, they can able to
register online by using the proposed system.
 Register finished condominium house: The system able to register finished condominium
house
 Update applicant information: The system able to search, Insert, delete and update the
applicant information when it is needed.
 Draw lottery: The system able to draw lottery from people who applied to get the
condominium house. In addition, Register winner after the lottery is drawn the system can able
register the winners’. In order to draw lottery for applicant the team used simple random

sampling algorithm that are easy to implement for drawing lottery by taking sample randomly
from applicant as well as from registered house
 Notification: The system should be able to give notification through the opened user account
of the applicant and provide the ability of searching there winning status by their own resident
id
 Payment: during and after registration for house the applicant can process payment by using
his/her bank account number on specified bank.
 Controlling applicant payment status: The system must be able to control the payment
process of winners’. How much the winner is paid how many of them are not start paying
specified payment will be controlled.
 Posting news and notice: the system can post news and notice for the people in order to make
them informed by the condominium house administrator.
3.3 Non-Functional Requirements

Nonfunctional requirements pertain to other information needed to produce the correct system and are
detailed separately. Constraints on the services or functions offered by the system such as timing
constraints, constraints on the development process, standards, etc.
 User interface: The system provides PHP user interfaces that are compatible with windows
platform
 Hardware consideration: The organization should have computers having typical storage
capacity and processing speed.
 Error handling: the system handles error by showing the message” invalid input” when the
user enter invalid input.
 Security: The system should have a security privilege that secures the system. In addition,
there must be a physical security that secures the server computer. That means the server
computer is only allowed for the server admin. The admin of the system change yearly.
 Performance characteristics: The end user computer should have medium processor and the
server computer should have large processor. It is measured by its speed of processor.
 Back up:-The system should have back up using external hard disk. The backup is taken
weekly.

3.4. Analysis Models
3.4.1. Introduction
Analysis modeling uses a combination of text and diagrammatic forms to depict requirements for
data, function, and behavior in a way that is relatively easy to understand, and more important,
straightforward to review for correctness, completeness, and consistency. The analysis model must
achieve three primary objectives:
To describe what the customer requires,
to establish a basis for the creation of a software design,
To define a set of requirements that can be validated once the system is built.
An Actor represents anything or anyone that interacts with a system. This may include people,
external system. Actors are always external to the system being model and have unique names and
descriptions in the existing system, there are three bureaus that are concerned with the issue of
giving and distributing the condominium houses for applicants.
The bureaus are:
 Kebele’ Offices: provide the following service for the resident.-Register resident that need
condominium house. It passes all the resident applicant information to the city
administrator office of housing development agency.
 Hawassa City Municipalities Office: The condominium housing management offices ask
information about the customer to the Hawassa city municipality’s offices and the offices
responsibilities is checking whether any house is register by the customer name or by his
family. If any house is registered by the customer the applicant’s will not accepted. If there
is no house registered by the applicant the condominium housing management offices
permits to get the house of condominium house for the applicant.
 Hawassa City Condominium House development Office:
 Collect applicant data that is already registered in all kebele’s of the city and receive the
constructed condominium houses from Condominium houses construction agency.
 Then draw the lottery in order to get a condominium houses.
 When the winner of the lottery pays the money, pre-payment or full payment.

 After these, this agency in turn distributes the condominium house for the applicant that
won the lottery balance with the number of the constructed house.
 The office also gives services, maintenance and infrastructure to the applicant.
3.4.2 Use case modeling

The Use case describes the behavior of the hawassa condominium house system as seen from an actor’s
point view. In the analysis phase, they represent the functionality of the system. In the use case
modeling the team included collection of all actors and all use cases.
3.4.1.1 Business Rule for proposed system

Identifying the business rule of the proposed system will help us to specify and describe each use case
in effective way. The business rules of the Hawassa condominium house management system are listed
as following:-
BR1: The applicant should be from Hawassa city or should live for at least 6 month.
BR2: The applicant should apply if applicant has no house that is registered by their name before.
BR3: the system kebele administrator and CHMA must have user account for managing the activity
specified and limited to their privilege.
BR4: Women have the opportunity to get the house 20%.
BR5: When people who are disabled have the chance to get the house ground floor is assigned to them.
BR6: Payment type 100%, by division of long time, pre-payment. Every applicant for house must pay
the pre-payment account during registration.
BR7: When the applicant pays, pre-payment applicant must agree to open closed account at the lender
bank.
BR8: Applicant must select type of house applicant want studio, one bedroom, two bedrooms, and
three rooms.

BR9: The applicant should have the capacity some percent of the total cost.
Figure 3.1 UseFIGURE

case diagrams
1 : USE CASEfor proposed
DIAGRAM system
DESCRIPTION
3.4.1.2.
Essential use case diagram description
Each use case are described in a manner to give direction how the specified use case are operated

TABLE 6: USE CASE DESCRIPTION FOR LOGIN USE CASE
Use case Name Login
UC_ID: UC_01
Actor: users (condominium house management officer

administrator, Keble administrator ,applicant)
Description: This use case is used to ensure security for login into the system
Precondition: The user must have at least correct username and password.
Flow Event: Actor action System response
Step1: User has to open the Step2: The System displays the
system. login interface and allows
Step3: by selects account type the user for the user name and
user fills his or her username and password.
password. Step5:display login successful
Step4: click login button. Step6: Step7: displays its main window.
the User gets access the system. Step8: Use case ends.
Post condition The main page will be displayed then user gets access to its privilege and
after finishing his/her work he can logout
Alternative course of action
If the user is not authorized
A.6: The system gives a conformation that is wrong username or password

TABLE 7 : USE CASE DESCRIPTION FOR REGISTER RESIDENT
Use case Name Register resident
UC_ID: UC_02
Actor: Keble administrator
Description: The Keble administers Register new applicant information.
Stake Holders Resident: to register
Precondition: The user must login to register the resident information

(UC_01)
The applicant must be presented physically
c. TheKeble administrator must check the resident information like
where did he live how many year the applicant lives in the given
Keble.
Step1:open resident Step2: The System display registration form
registration page from
Step5:display register successful Step6:
menu
finished registration and the use case end
Step3: fill the resident
registration data
Step4: click register
button
Post condition Resident must be registered.
A.5:the system display error message if the resident information already stored in the database

TABLE 8: USE CASE DESCRIPTION FOR REGISTER APPLICANT ONLINE
Use case Name Register applicant online
UC_ID: UC_03
Actor: Applicant
Description: This use case done by the applicant in order to register new applicant for
getting condominium house.
Stake Holders Applicant : for registering
Precondition: 1.Applicant must have an internet connection, and must first registered
necessary information by Keble administer.
2. a. The user must login to register the resident information (UC_01)
Step 1: the applicant opens the Step2 : the system display the home
home page of the website. page
Step3: Select apply for Step4: the system displays the
house. conformation page.
Step5:fill resident id and last name Step 6: the system display applicant
Step7:fill the registration form and registration form
click register button Step7: the system display register
successfully message
Exception Condition: If there is no internet connection there is no registration.
Post condition The applicant must be registered successfully.
A6: The system display register failed message if there is un filled information in the form.
A6: The system display error message if the applicant information is not registered in the Keble admin.

TABLE 9 : USE CASE DESCRIPTION FOR REGISTER FINISHED HOUSE
Use case Name Register finished house
UC_ID: UC_04
Actor: Condominium house administrator
Description: Condominium house management office administrator Register house that are
finished or ready with their full description
Stake Holders Constructor: build the new house
Precondition: he user must login to register the applicant information (UC_01),

new finished house must be existed
Step1: open house Step2:display house registration form

registration page from menu Step6:display register successful Step7:
Step3: fill the finished house finish recording and the use case end
information data
Step 4:repeat information until
registration is over Step5: click
register button
Exception The system display error message if the resident information already stored in
Condition: the database
Post condition The entire new houses that are finished must be registered or recorded with their
full description
A.1: if there is no new finished condominium house, the condominium house management
administrator stop or pause the use case.

TABLE 10 : USE CASE DESCRIPTION FOR DRAW LOTTERY
Use case Name Draw lottery
UC_ID: UC_05
Description: Condominium house management office administrator draw

lottery for applicant in efficient way, by considering the finished new
house
Stake Holders Applicant: to win lottery
Precondition: The user must login to register the applicant information (UC_01),
registered applicant and registered house must exist
Step1: open draw lottery page Step2: display the draw page
from menu Step6:display lottery successful
Step3: fill the lottery Step7: finish draw lottery s and
information the use case end
Step 4:repeat information the
process end
Step5: click draw lottery button
Exception
Condition:
Post condition The system must draw lottery effectively for the applicant.
A.6: if there is no finished house the system display “there is no finished house to draw lottery .

TABLE 11 : USE CASE DESCRIPTION FOR NOTIFICATION
Use case Name Notification

UC_ID: UC_06
Description: Condominium house management office administrator after drawing

lottery applicant notify the result for the lottery winner applicant.
Stake Holders applicant: to know about their winner of the house
Precondition: The actor must login to register the applicant information (UC_01).The
winner of the house must exist. And the applicant must have an email
address
Step1: click notification page Step2: display notification page

from menu Step6:display sent successful
Step3: fill the notification message
Step 4:repeat information the Step7: finish notification and the use
process end case end
Step5: click send button
Post condition The entire winner must be notified

TABLE 12: USE CASE DESCRIPTION FOR PAYMENT
Use case Name payment

UC_ID: UC-07
Actor: applicant
Description: Applicant who apply for house pay the payment of the house
Stake Holders Applicant :- to pay payment
Precondition: a.The applicant must have account no on specific bank
b.The applicant must fill the registration form first
Step1: click payment link from Step2: display payment page

registration form
Step5:display payment
Step3: fill all successful message
payment information. Step7: finish payment and the use
Step 4:click pay button case end
Post condition The condominium house administrator must control payment process.
A.5.1.if the applicant does not have bank account number the system display error message.
A.5.2.if the applicant has insufficient balance in his/her bank account insufficient balance message
will be displayed

TABLE 13: USE CASE DESCRIPTION FOR CONTROL PAYMENT
Use case Name control payment

UC_ID: UC_08
Actor: CHM administrator
Description: This use case done condominium house admin and

applicant to control the payment process of applicant
Precondition: The condominium house administrator must login to the system

(UC_01);
Step 1:CHM administrator open Step2: the system displays the

payment control page payment controlling page.
Step 3:CHM administrator view
the payment table of the applicant.
Post condition The CHM administrator should view all the applicant payment process
data.

TABLE 14: USE CASE DESCRIPTION FOR MANAGE APPLICANT
Use case Name Manage applicant

UC_ID: UC_09
Actor: condominium office Administrator
Description: This use case is done by the CHM Administrator when they need update,
search and delete applicant information
Stake Holders Office administrator
Precondition: The Administrator must login to the system to manage applicant.
Step 1: the Administrator click Step2: the system display the
manage applicant link manage applicant page
Step3: the administrator enter the id Step4: the system display the
number of the applicant to update update form with the
Step 5: the administrator fill the new registered applicant
updated information of the applicant. information
Step 6:click submit button Step7: display update
successful page
Flow of event (for Actor action System response
search applicant )
Step 1: the Administrator click manage Step2 : the system display
applicant link mange applicant page
Step 3: the administrator enters the id Step4: the system display the
number of the applicant to search and applicant information
click search button. Step8: finished searching and
stop the use case
Actor action System response
Step 1: the Administrator click manage Step2 : the system display
Flow of event for applicant link mange applicant page
delete Step 3: the administrator enters the id Step4: the system display the
applicant number of the applicant to search and applicant information
click search button. Step6: the system display delete
Step 5:the administrator enter delete successful message and stop the
button use case
Alternative course action: for update applicant
A.5: the system does not display update form to update the applicant information with the
entered id.
A.8: the system display error message if the applicant information doesn’t fill accurately.

Alternate course action: for search applicant
A.4: the system displays fill again message to Administrator if the entered id is incorrect.
TABLE 15: USE CASE DESCRIPTION FOR MANAGING INFORMATION.
Use case Name Manage resident information

UC_ID: UC_10
Actor: Keble administrator
Description: This use case is done by the Keble Administrator when they need
update, search and delete applicant information
Stake Holders
Precondition: The kebele Administrator must login to the system to manage
resident information
Step 1: the Keble Step2: the system display the
Administrator click manage resident form.
manage resident link Step4: the system display the
Step3: the administrator update form with the registered
enter the id number of the resident
resident to update information
Step 5: the administrator Step7: display update
fill the new updated successful page
information of the
resident.
Step 6:click submit button
Flow of event (for Actor action System response
search and
Modify resident Step 1: the Administrator Step2 : the system display mange
information ) click manage resident resident
link Step4: the system display the
Step 3: the administrator applicant information
enters the id number of Step5: finished searching display
the applicant to search and the searched
click search button. information
Step 6:the applicant may Step 7:the system display delete
click modify button successful message and stop the
use case
A.6: the system display deletion failed if the entered data are not available.

Alternate course action: for update resident information
A.4: the system displays no registered resident information message
A.7: the system display error message if the applicant information doesn’t fill accurately.
Alternate course action: delete resident information
A.4: the system displays fill again message to Administrator if the entered id is incorrect.
A.6: the applicant may not click the modify button so that there is no display modify successful
message.
3.4.2. Sequence diagram
A Sequence diagram is an interaction diagram that shows how the hawassa city condominium
house process operates with one another and in what order. It is a construct of a Message Sequence
Chart. A sequence diagram shows object interactions arranged in time sequence
Key parts of a sequence diagram
 Participant
 Message

FIGURE 2: SEQUENCE DESCRIPTION FOR CHMS ADMINISTRATOR

FIGURE 3: REGISTER RESIDENT

FIGURE 4: SEQUENCE DIAGRAM FOR KEBELE ADMINISTRATOR

FIGURE 5: SEQUENCE DIAGRAM FOR REGISTER FINISHED HOUSE

FIGURE 6: SEQUENCE DIAGRAM FOR DRAW LOTTERY

FIGURE 7: SEQUENCE DIAGRAM FOR NOTIFICATION

FIGURE 8: SEQUENCE DIAGRAM FOR MANAGE APPLICANT

3.4.3. Activity diagram
The basic purposes of this diagrams are to captures the dynamic behavior of the hawassa
condominium system. As the team described above sequential diagram shows the message
flow from one object to another whereas activity diagram is used to show message flow from
one activity to another. It is a particular operation of the system. This diagrams are not only
used for visualizing dynamic nature of a system but they are also helpful to construct the
executable system by using forward and reverse engineering techniques.
FIGURE 9: ACTIVITY DIAGRAM FOR LOGIN

FIGURE 10: ACTIVITY DIAGRAM FOR REGISTERING RESIDENT

FIGURE 11: ACTIVITY DIAGRAM FOR REGISTERING FINISHED HOUSE

FIGURE 12: ACTIVITY DIAGRAM FOR DRAW LOTTERY

FIGURE 13: ACTIVITY DIAGRAM FOR NOTIFICATION

FIGURE 14: ACTIVITY DIAGRAM FOR MANAGE APPLICANT

FIGURE 15: ACTIVITY DIAGRAM FOR MANAGE APPLICANT MODIFICATION

FIGURE 16: ACTIVITY DIAGRAM FOR MANAGE ACCOUNT BY ADDING

FIGURE 17: ACTIVITY DIAGRAM FOR UPDATE ACCOUNT
3.4.4. Class Diagram

Used to represent the structure of the system in terms of objects, their notes and nature of
relationship between classes. It shows the static features of the objects and do not represent any
particular processing.
The system has the following classes:
 Keble administrator: is the representation of the real world class of administrator which
interacts with system to accomplish different task such as registration of resident ,give
resident id manage resident information

 CHMA: is the representation of the real world condominium house management
administration, which uses an automated system to manage
 Applicant: it is the representation of the real world class of materials.
 Resident: the representation of the real world class which interacts with system to be
registered in the Keble database and who get resident id and who may or may not apply
for having condominium house
 User account: the way the 2 system administrator access there administrator page and
perform their own activity through there user account user name ,password, user type.
 House: it is an item that the system want to manage.
 Bank administrator: it is an administrator that manage winner payment process
FIGURE 18: SAMPLE OF CLASS DIAGRAM

3.4.5 User interface design
There are various types of user-computer interface designs, each of which has a typical character
and ability. So when the project is finalized it look like the following interfaces, some are listed
below.
FIGURE 19: SAMPLE OF USER INTERFACE DESIGN

Figure user interface sample for login form
FIGURE 20: USER INTERFACE FOR RESIDENT REGISTRATION FORM

FIGURE 21: USER INTERFACE SAMPLE FOR MANAGE ACCOUNT PAGE

FIGURE 22: USER INTERFACE SAMPLE FOR USER REGISTRATION PAGE
3.5: summary
In this chapter, the team studied the existing system deeply, since it is necessary to know the existing
working system of office to develop a better system.Functional Requirements are those that refer to
the functionality of the system, i.e., what services it will provide to the user.Nonfunctional
requirements pertain to other information needed to produce the correct system and are detailed
separately.Analysis modeling uses a combination of text and diagrammatic forms to depict
requirements for data, function, and behavior in a way that is relatively easy to understand, and
more important, straightforward to review for correctness, completeness, and consistency.The Use
case describes the behavior of the hawassa condominium house system as seen from an actor’s point
view.The basic purposes of this diagrams are to captures the dynamic behavior of the hawassa
condominium system system. There are various types of user-computer interface designs, each of
which has a typical character and ability.

CHAPTER FOUR
SYSTEM DESIGN
4.1 INTRODUCTION
System Design phase is process of describing, organizing, and structuring system components at
architectural design level and detailed design level. Build a system Design converts functional
models from analysis into models that helps to represent the solution for the problem. In system
Designing process the team can use structured or object oriented approaches.
In the case of online Hawassa city condominium, house management system the system design
modeling will fill the gap between the system specification produced during requirement
elicitation and analysis which is concentrated on the purpose and the functionality of the online
Hawassa city condominium house management system.
In the design phase of the online condominium house management system, system decomposition,
component modeling, database design ,class mapping ,deployment diagram and the exact architecture of
the proposed system which is the user interface prototyping will be showed in detail is showed in detail.
4.2 Purpose of the System Design Document
In the system development, process system design part is very important to make the
implementation of the proposed system very easy. The different types of the system modeling
techniques that are used to make easy the implementation of the system such as deployment and
component modeling are show in detail. Not only the system modeling techniques but also some
system design techniques such as system decomposition design are cover in detail in this phase.
The nonfunctional requirement is the description of the feature characters and attributes of the
system.
Some of the design goals are:-
 Security- The system should be secured that unauthorized user cannot access the
data that does not concern with them.
 Reliability- The system should be reliable.
 Fault Tolerance-The system should be able to give response when the user enter
incorrect input. This recommends the user to enter correct input.
 Throughput:-Since online condominium, house management system has web
application it is able to perform many tasks at any time.
 Robustness: - The system has the ability to survive wrong applicant inputs. Besides
this end applicant that use online condominium house management system site have
limited access regarding info about applicant name phone no, Email address.
 Modifiability:-The proposed system able to handle applicant databased on selected
service center such as kebele office and condominium house constructor. The
system can be modified by adding some addition futures like different controls and
form
 Usability: - Hawassa city online condominium house management system provide
easy user-friendly interface for users of the systems. It also provides help menu,
which gives brief description how to use the system so that user can be able to use
it easily.
 Memory: -- Hawassa city online condominium house management system requires
the following space to run the system. Desktop or laptop computers and web server
computers having more than 4GB of RAM and high storage capacity and
processing speed.
4.3 Scope
System design is the first of the three technical activities -design, code and test that is required to
build and verify software. The importance can be stated with a single word “Quality”. Design is
the place where quality is fostered in software development. The team will see architecture design,
deployment view, logical view, and process view, purpose of system design document and
database design.
4.4 Architectural Design
In this project, the team use a three-tier architecture, which has three layers. These three layers are
the Application or Presentation layer, the business layer and the data access layer. Application or
presentation layer is the form, which provides the user interface to either programmer or end user.
The business layer is the layer uses to write the function which works as a mediator to transfer data
from application layer or presentation layer to data layer. This layer also has a property layer which
is a class where variables are declared corresponding to the fields of the database which can be
required for the application and make the properties so that the the team can get or set the data
using these properties into the variables. The third tire is the data access layer that is also a class

to get or set data to the database queries back and forth. This layer only interacts with the database.
The database queries or stored procedures will be written here to access the data from the database
or to perform any operation to the database. When the team use three-tier architecture, the system
has these benefits: -
Managing data is independent from the physical storage, Migration to new graphical environments
is faster, It is possible to make changes on the presentation level without affecting the other two
business or data access layer, As each tier is independent it is possible to use different sets of
developers, Since the client doesn’t have direct access to the database business logic is more
Secure. When one tier fails, there is no data loss, because you are always secure by accessing the
other tier, Security policies can be imposed without affecting the clients. It has better wait
balancing system because the entire workload is divided, A change from one DBMS to other will
only involve a change to the part in the data Access layer, A change in the Use Interface from
desktop to the web, will need only some changes In the components of the presentation layer.
4.4.1. Logical View
Describes the most important use case realizations, for example, the dynamic aspects of the
condominium architecture. Design level class diagrams have to be included also to illustrate the
relationships Describe the abstract descriptions of a system's parts. Used to model what a system
is made up of and how the parts interact with each other. The types of UML diagrams that typically
make up this view include class, object, state machine, and interaction diagrams. Between
architecturally significant classes, subsystems, packages and layers.
4.4.2. Process View
The Process Model illustrates the course registration classes organized as executable processes.
Processes exist to support applicant registration, administrator functions, registration closing, and
access to the system. It illustrates all function of the system.
4.4.3 Deployment View
This shows the execution architecture of systems that represent the assignment of software targets
to hawassa city condominium house management office. This diagram are used to depict the
relationship among run-time components and hardware nodes. Components are self-contained
entities that provide service to other components or actors run time components.

FIGURE 23: DEPLOYMENT DIAGRAM
The user operates at the client side. In addition, get any service from the system. And the system
will process the request, connect to a My SQL database server, and produce a response to the
client. The system could access the database to produce the required information to the user.
Client Tier : This level of the application is the user interface. The main function of the interface
is to translate tasks and results to something the user can understand. The user enters the address
in the web browser and in the browser; the URL is decoded into protocol/host/file, i.e. host name
converted to IP address. Then an issue request is sent to remote server using appropriate protocol.
Also a returned HTML from the logic tier might be accepted. In the presentation layer, interaction
with client side scripts using HTML 5 is supported and user imputer of variety controls on the
form is accepted.
Middle Tier
This layer coordinates the application processes commands, makes logical decisions and
evaluations, and performs different activities related to the system. It also moves and processes

data. Between the two surrounding layers. In the logic, performing detailed processing of data
from presentation layer. Server such as Apache or Server Script PHP can be used to support this.
With Apache Server the appropriate action to be taken is identified, such as fetching a file, or
passing request to an interpreter. With Server script in PHP interacting with server such as
accessing input or generating input is done. It interprets therequests according to medical rules and
pat appropriate data from the persistence layer
Data Layer
Here information is stored and retrieved from a database. The information is then passed back to
the logic tier for processing and then eventually back to the user. This tier consists of database
servers. The interaction with the database is done using standard languages such as SQL queries
using database specific protocol over TCP/IP. The data structures are defined and modified
themselves, that insertion, updating and deleting of data for example. Data maintenance should be
maintained with backup and recovered. Access to compilation of queries should be optimized,
with indexing or replication of tables.
4.5.Data Base Design
Data that must be stored in the database for future use with their data type and their domain must
be designed as a database design, this kind of design help as to build table relationship as well as
dependency between different tables in the database

FIGURE 24: DATABASE DESIGN DIAGRAM
4.6: summary
System Design phase is process of describing, organizing, and structuring system components at
architectural design level and detailed design level. Build a system Design converts functional
models from analysis into models that helps to represent the solution for the problem. In system
Designing process the team can use structured or object oriented approaches. In the system
development, process system design part is very important to make the implementation of the
proposed system very easy. System design is the first of the three technical activities -design, code
and test that is required to build and verify software.In this project, the team use a three-tier
architecture, which has three layers. These three layers are the Application or Presentation layer,

the business layer and the data access layer. Application or presentation layer is the form, which
provides the user interface to either programmer or end user. Describes the most important use
case realizations, for example, the dynamic aspects of the condominium architecture.The Process
Model illustrates the course registration classes organized as executable processesThis shows the
execution architecture of systems that represent the assignment of software targets to hawassa
city condominium house management office. The system could access the database to produce the
required information to the user.Client Tier, ,Middle Tier, ,Data Layer. Data that must be stored in
the database for future use with their data type and their domain must be designed as a database
design, this kind of design help as to build table relationship as well as dependency between
different tables in the database

CHAPTER FIVE
CONCLUSION AND RECOMMENDATION
5.1.Conclusions
Implementing the analyzed and designed online condominium house management system might
be the best solution to the current major condominium housing development agency problem, as
it will provide online application, so that the resident can apply from home or anywhere else via
such system. The proposed online condominium house management system will also provide
quick and reliable registration process, lottery drawing process, payment control notification and
placement hence reducing the load of work done by staff and saving time for the applicant who
apply. Therefore, in the first and the second chapter of this project document the team were trying
to assess the existing system and studying each activity of the existing system by conducting
different data gathering methodology. Then after examination of the limitation of existing system,
the team choose the web based system, as it will be able to address problems encountered by users
with in the current condominium administration system. And in order to accomplish the objective
of the proposed system implementation tools used PHP, XAMP, HTML 5 and design model such
as use case modeling, sequence diagram are specified and most of the designing tool were used in
chapter two and three. Home page, main page, and other page functionality login is illustrated. The
activity diagram shows different type of user interacts with the system. Furthermore, the use cases
showed what the user would do with the system. Finally each class and attribute was explained in
detail. Furthermore, the class diagram demonstrates the relationship between classes in the system.
From a proper analysis of positive points and constraints on the existing system the team conclude
that the proposed system that the team designed to implement will be efficient and effective one
to solve current problem, if the implementation is in carefully planned manner.
5.2 Recommendation for future work

The need for transformation of organizational practice from manual system to computerized
system is felt all over the world for various reason discussed in chapter 1 and chapter 2. Technology
is surely the key component of all future organizational success and efficiency. But the team need
to rethink how the usage of such technology with in the environment which is not easily adopted
with.

However, the literature throws light in several challenges in the integration of technology for
condominium house management appealing to those residents who may literate or illiterate, and
not to others. Therefore, there should studies: on how to motivate all residents as well as
administrators at DB to adopt innovative and creative that will help the acquire skills interact with
the proposed system.
The system that the team are designed to implement does not include or perform other
functionality, so when other project team who are interested can build similar system by including
those functionality like managing house contactor information, budget allocation for construction
of house. Full construction management functionality, security mechanism like digital signature
and the clearness of the condominium house when they use it, like dirty, toilet, the roof and others
are build this system who are interested on this system .

REFERENCES
[1]. ZELALEM YIRGA ADAMU,(2012), Institution Analysis;Ethiopia from
www.fig.net/pub/fig2012/papers/ts02c/TS02C_adamu_5531.pdf
[2]. Allen, B., &Reser, D. (1990). Content analysis in library and information science
research. Library & Information Science Research, 12(3), 251-260.
[3]. ANRS. (2006). The Revised Amhara National Regional State Urban City
Administration Proclamation. Proclamation No. 144/2006. ZikreHig. Year 11 No. 18,
2006. .
[4]. Benjaminsen, T. and Lund, C. (Eds.) (2002). Securing land rights in Africa. The
European Journal of Development Research, 14, (2), 11-30.
[5]. Bihon, K. (2007). Housing for the Poor in Addis Ababa. Addis Ababa. Retrieved on
July 4, 2010 from http://www.lth.se/fileadmin/hdm/alumni/papers/sdd2006/sdd2006-
12.pdf
[6]. SYSTEM ANALYSIS AND DESIGN 8thedtionkennethekendall and julee.kendall
[7]. Ambler, Scott (2001) The Object primer: The application Developers Guide to Object
Oriented and the UML.2nd rev. Ed England: The Cambridge University Press.
[8]. .Massimofelici(2011) 3rd edtion object oriented ANALYSIS AND DESIGN OF SYSTEM
[9]. Microsoft http://msdn.microsoft.com/en-us/library/dd409393.aspx
[10]. Source code exprt :http://www.sourcecodester.com/php
[11]. Mysql introduction :http://www.w3schools.com/php/php_mysql_intro.asp

Appendix
TABLE 16: APPENDIX
Symbol Description
Actor
System boundary
Decision
Use case
class
Object life line

ADVISER APPROVAL
I approve that this industrial project report entitled “Your Project Title Goes Here!” by:
Name Signature
Your Names Goes Here!
is approved by me for submission. I certify further that, to the best of my knowledge, the report
represents work carried out by the students.
__________________ _________________________ ________________________

Date Signature Name of Adviser
Examining committee members’ Signature

1.
2.
3.
4.
It is approved that this project has been written in compliance with the formatting rules laid down by the
university.


Final Document Proggg1111llll

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Final Document Proggg1111llll

Uploaded by

Copyright:

Available Formats

HAWASSA UNIVERSITY

DEPARTMENT OF COMPUTER SCIENCE

TITLE: - Hawassa City Online Condominium House Management System

GROUP MEMBERS ID EMAIL

DATE MAY 17, 2021

Key word: Hawassa, condominium, php, Dreamweaver, XAMP

Hawassa city Online condominium house management system Page 1

Hawassa city Specification

The distance From Addis Ababa 273 km south

1.2.Statement of The Problem

Hawassa city Online condominium house management system Page 3

1.3. Objectives of the Project

Hawassa city Online condominium house management system Page 4

Hawassa city Online condominium house management system Page 5

Hawassa city Online condominium house management system Page 6

1.6.2. System Analysis and Design Methodology

Hawassa city Online condominium house management system Page 7

Hawassa city Online condominium house management system Page 8

XAMPP,MYSQL used to create the database of the project

Javascript ,HTML 5,CSS3 used to validate data and write the

1.6.6 System requirements

Hawassa city Online condominium house management system Page 9

DESCRIPTIONS OF EXSTING SYSTEM

Hawassa city Online condominium house management system Page 10

2.2. Proposed System Description

Hawassa city Online condominium house management system Page 11

Hawassa city Online condominium house management system Page 12

3. The Hawassa city condominium house management administrators of applicants

2.3. Strength of Existing System

Hawassa city Online condominium house management system Page 13

2.4. Weakness of Existing System

Hawassa city Online condominium house management system Page 14

Poor performance Better performance

Hawassa city Online condominium house management system Page 15

 How the existing system is working?

 What kind of method they use to handle applicant data?

 In what way the office is handling resident complaint.

 What is the business rule they use?

3.2. Functional Requirements

Hawassa city Online condominium house management system Page 16

3.3 Non-Functional Requirements

Hawassa city Online condominium house management system Page 17

Hawassa city Online condominium house management system Page 18

3.4.2 Use case modeling

3.4.1.1 Business Rule for proposed system

Hawassa city Online condominium house management system Page 19

Figure 3.1 UseFIGURE

Hawassa city Online condominium house management system Page 20

Use case Name Login

Actor: users (condominium house management officer

Flow Event: Actor action System response

Alternative course of action

If the user is not authorized

A.6: The system gives a conformation that is wrong username or password

Hawassa city Online condominium house management system Page 21

Use case Name Register resident

Actor: Keble administrator

Description: The Keble administers Register new applicant information.

Stake Holders Resident: to register

Precondition: The user must login to register the resident information

Post condition Resident must be registered.

Alternative course of action

Hawassa city Online condominium house management system Page 22