ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

TABLE OF CONTENTS PAGE NO

LIST OF TABLES ….. ................................................................................................................................................. ..IV
LIST OF FIGURES ……………………………………………………………………………………………………………………………………………..V
ACRONYM ..................................................................................................................................................................... VIII
Acknowledgment ................................................................................................................................................................ IX
ABSTRACT ............................................................................................................................................................................ X
CHAPTER ONE .................................................................................................................................................................. - 1 -
PROJECT PROPOSAL ..................................................................................................................................................... - 1 -
1.1 INTRODUCTION................................................................................................................................................ - 1 -
1.2. BACKGROUND ....................................................................................................................................................... - 1 -
1.3 STATEMENT OF THE PROBLEM .............................................................................................................................. - 2 -
1.4OBJECTIVES OF THE PROJECT ................................................................................................................................. - 2 -
1.4.1General objective............................................................................................................................................. - 2 -
1.4.2 Specific objectives........................................................................................................................................... - 3 -
1.5 SIGNIFICANCE OF THE PROJECT ............................................................................................................................. - 3 -
1.6. FEASIBILITY STUDY ................................................................................................................................................ - 4 -
1.6.1 Economic Feasibility ....................................................................................................................................... - 4 -
1.6.2 Technical Feasibility ........................................................................................................................................ - 6 -
1.6.3 Operational feasibility..................................................................................................................................... - 6 -
1.6.4. Schedule Feasibility........................................................................................................................................ - 7 -
1.6.5. Legal and contractual feasibility .................................................................................................................... - 7 -
1.6.6 Political feasibility ........................................................................................................................................... - 8 -
1.7. SCOPE OF THE PROJECT ........................................................................................................................................ - 8 -
1.8. METHODOLOGY .................................................................................................................................................. - 10 -
1.8.1 Data gathering techniques............................................................................................................................ - 10 -
1.8.2 Analysis and Design Methodology ................................................................................................................ - 10 -
1.8.3 Implementation Methodology ..................................................................................................................... - 11 -
1.8.4 Testing methodology ................................................................................................................................ - 12 -
CHAPTER TWO ........................................................................................................................................................... - 12 -
SYSTEM ANALYSIS .......................................................................................................................................................... - 12 -
2.1 REQUIREMENT ANALYSIS DESCRIPTION .............................................................................................................. - 12 -
I
 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
2.2 OVERVIEW OF THE EXISTING SYSTEM ............................................................................................................. - 13 -
2.2.1Activities of the system.................................................................................................................................. - 13 -
2.2.2 Problem of Existing System .......................................................................................................................... - 14 -
2.2.3 Business rule of the organization ................................................................................................................. - 14 -
2.2.4 Class responsibility collaboration modeling ................................................................................................. - 15 -
2.3 OVERVIEW OF THE PROPOSED SYSTEM .............................................................................................................. - 16 -
2.3.1 Purpose of the proposed system .................................................................................................................. - 18 -
2.3.2 Functional Requirements.............................................................................................................................. - 19 -
2.2.3 Non-Functional Requirements...................................................................................................................... - 20 -
2.3.4 Systems Requirement (Hardware and Software requirement) .................................................................... - 20 -
2.4 SYSTEM MODELING AND ARTIFACT ................................................................................................................... - 21 -
2.4.1 Use case modeling ........................................................................................................................................ - 22 -
2.4.1.1 Business Rule for proposed system ........................................................................................................... - 22 -
2.4.1.2 Essential use case diagram description ..................................................................................................... - 23 -
2.4.1.3. Essential user interface ............................................................................................................................. - 36 -
2.4.2 SEQUENCE DIAGRAM........................................................................................................................................ - 39 -
2.4.3 ACTIVITY DIAGRAM........................................................................................................................................... - 47 -
2.4.4. State chart diagram ......................................................................................................................................... - 57 -
2.4.5Class responsibility collaboration modeling for the proposed system.............................................................. - 67 -
2.4.6Analysis Level of Class Diagram ......................................................................................................................... - 71 -
CHAPTER THREE ............................................................................................................................................................. - 73 -
SYSTEM DESIGN ............................................................................................................................................................. - 73 -
3.1 INTRODUCTION.................................................................................................................................................... - 73 -
3.2 DESIGN GOAL ....................................................................................................................................................... - 73 -
3.3 SYSTEM DECOMPOSITION ................................................................................................................................... - 75 -
3.4COLLABORATION DIAGRAM ................................................................................................................................. - 76 -
3.5 SYSTEM ARCHITECTURE ....................................................................................................................................... - 82 -
3.6 COMPONENT DIAGRAM ...................................................................................................................................... - 84 -
3.7 User interface prototyping design ....................................................................................................................... - 85 -
3.9DESIGN OF CLASS DIAGRAM (CLASS MAPPING) ................................................................................................... - 86 -
3.10DATA BASE DESIGN (PERSISTENT MODELING) ................................................................................................... - 87 -
3.11DEPLOYMENT DIAGRAM..................................................................................................................................... - 88 -
II
 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
Chapter four................................................................................................................................................................... - 89 -
SYSTEM IMPLEMENTATION ....................................................................................................................................... - 89 -
CHAPTER FIVE ................................................................................................................................................................ - 95 -
5.1 PROTOTYPE DEVELOPMENT ................................................................................................................................ - 95 -
CHAPTER six ................................................................................................................................................................. - 105 -
CONCLUSION AND RECOMMENDATION ................................................................................................................. - 105 -
5.1.CONCLUSIONS.................................................................................................................................................... - 105 -
5.2Recommendation ............................................................................................................................................... - 106 -
APPENDEX ............................................................................................................................................................ - 107 -
REFERENCES ............................................................................................................................................................. - 109 -

III
 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

LIST OF TABLES PAGE NO

Table 1.1: Miscellaneous Costs …………………………………………………………………..….…5

Table 1.2: Software Development Costs ………………………………….….………………………...5

Table 1.3: Time Schedule for our Project ………………………………………………………………7

Table 2.1: CRC modelingfor existing system ……………………………………………….………..15

Table2.2: use case description for login ….……………………………………..……………………..24

Table 2.3: use case description for register resident …………………………………………...………25

Table 2.4: use case description for register applicant online ……………………………………...…...26

Table 2.5: use case description for register finished house …………………………………..………..27

Table 2.6: use case description for draw lottery ………………………………………………….…....28

Table 2.7: use case description for notification …………………………………...………………..….29

Table 2.8: use case description payment ……………..………………………………………….…….30

Table 2.9: use case description for control payment……………………………………...………..…..31

Table 2.10: use case description for manage applicant..………………………...…………………...…32

Table 2.11: use case description for manage resident information...……………….………………..…34

Table 2.12: CRC modeling for the proposed system ………………………………………………..…67

Table 2.13:identified class from use case………………………………………………………………67

IV
 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

LIST OF FIGURES PAGE NO

Figure 2.1: Use case of Proposed online condominium house management system………………………….35

Figure 2.2: sample user interface of login ……………………………..…………………………………..….36

Figure 2.3: sample user interface of applicant registration………………………………………………..…...37

Figure 2.4:sample user interface of house registration …………………………….……...………..…….…..37

Figure 2.5: sample user interface of draw lottery ……………...………………………………………..........38

Figure 2.6: sample user interface of notification ………………………………………………………….......38

Figure 2.7: Sequence Diagram of Login ………………………………………………………………………39

Figure 2.8: Sequence Diagram of register resident ………………………………………………...………….40

Figure 2.9: Sequence Diagram of register applicant ………………………………………….……………….41

Figure 2.10: Sequence Diagram of register finished house …………………………………..…………….…42

Figure 2.11: Sequence Diagram of draw lottery ………………………………………………….…………..43

Figure 2.12: Sequence Diagram of notification ……………………………………………………….……....44

Figure 2.13: Sequence Diagram of Manage applicant ………………………………………………………..45

Figure 2.14: Activity Diagram of login ……………………………………………………………………….46

Figure 2.15: Activity Diagram of register resident ……….…………………………………………….…….47

Figure 2.16: Activity Diagram of register finished house …………………………………..………………..48

Figure 2.17: Activity Diagram of draw lottery………………………………………………..………………49

Figure 2.18: Activity Diagram of notification…………………………………………………..…………….50

Figure 2.19: Activity Diagram of update applicant…………………………………………….……………..51

Figure 2.20: Activity Diagram of delete applicant …………………………………………….……………..52

V
 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
Figure 2.21: State chart Diagram of add account ………………………………………………………….53

Figure 2.22: State chart Diagram of update account ………………………………………………………54

Figure 2.23: State chart Diagram of delete account ……………………………………………………….55

Figure 2.24:State chart Diagram of login ………………………………………………………………...56

Figure 2.25: State chart Diagram of register resident ……….……………………………………….……57

Figure 2.26: State chart Diagram of register finished house ……………………………………………....58

Figure 2.27: State chart Diagram of draw lottery…………………………………………………………..59

Figure 2.28: State chart Diagram of notification…………………………………………………………...60

Figure 2.29: State chart Diagram of update applicant……………………………………………………..61

Figure 2.30: State chart Diagram of delete applicant ……………………………………………………..62

Figure 2.31:State chart Diagram of add account …………………………………………………………63

Figure 2.32: State chart Diagram of update account …………………………………………………...….64

Figure 2.33: State chart Diagram of delete account ………………………….……………………………65

Figure 2.34 analysis level class diagram ……………………………………..……………………..……..71

Figure 3.1: system decomposition Diagram..…………………..…..... ……………..………………..……75

Figure 3.2: Collaboration Diagram for login…..…......................................................................................76

Figure 3.3: Collaboration Diagram of register applicant …………………………………….…………......77

Figure 3.4: Collaboration Diagram of register finished house ……………….............................................78

Figure 3.5: Collaboration Diagram of draw lottery ……………………….…………………………………79

Figure 3.6: Collaboration Diagram of notification ……………….…...........................................................80

Figure 3.7: Collaboration Diagram of manage applicant…………………………………………………….81

VI
 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
Figure 3.8: system architecture …………………………………………………………………………….82

Figure 3.9: component diagram………………………………………………………………………….....83

Figure 3.10user interface prototyping …………………………………………………………………...…84

Figure 3.14: design level class diagram …………………………………………………………………....85

Figure 3.15: database design ………………………………………………………………………………..86

Figure 3.16: deployment diagram ………………………………………………………………………...…87

Fig: 4.1: User Interface Design for Home……………………………………………………………………89

Fig: 4.2: User Interface Design for login……………………………………………………………………..90

Fig: 4.3: User Interface Design for apply form………………………………………………………………91

Fig:4.4:user interface design for draw lottery……………………………………………………...…………93

VII
 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

ACRONYM

BR Business Rule
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

VIII
 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

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 YeshialemGezahegn for her constructive opinion and willingness
to participate in each part of our project and her effective direction,
assistance and guidance for the accomplishing of this project. We also want
to thank AtoGetachew, officer of Debreberhan 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. Also we would like to thank the teaching staffs of
Information system who have contributed wholly to the success of this
project.

IX
 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

ABSTRACT

This project document deals with online condominium house management system
development specifically project proposal system analysis, design, and implementation
methodology and partial conclusion and recommendation of full online condominium
house management system. Our propose system maintain necessary information of the
Debreberhan housing development agency.

Online condominium house management system mainly provides effective and fast data
processing, registration, notification drawing lottery service, and placement. This 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
designingandanalysis tool and technique has been employed. Generally, the main goal of
online condominium house management system isto shorten data-processing time, to
reduce errors, to improve the accuracy of input and to providedata reliability of the
information and to change the manual data handling system into automated system.

X
 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

CHAPTER ONE
PROJECT PROPOSAL
1.1 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 Debreberhan city.
Debreberhan city administration has opened an office namedDebreberhan
Housing Development Agency which has four departments; Housing Transfer and
Administration, Construction and supervision, Support, Process and Design of
condominium houses. Currently, the office/agency/ process data manually, and
this manual processing system has many drawbacks.Hence with a gear of solving
these setbacks we 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.

1.2. BACKGROUND

The Ethiopian government is trying to solve shortage of house for the low-income
communityliving in the urban area. One solution for this shortage program of
condominium housing development project.(Zelalemyirga adamu,2012).Condominium
housing is the name given to the forms of housing contract when each resident

-1-
 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
.

-2-
 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
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.
Debreberhan city condominium house management office is among the offices
that are found under Debreberhan city administration. It was established in 1999
E.C. The office is able to construct houses in 4 phases. The first project was
completed in 1999 E.C by building 18 blocks and the second project is completed
in the year 2000 E.C. by building 23 blocks that are also sold to the town
residence and merchants. The office constructed 41 building in four (4) areas. The
four (4) areas that the buildings are erected found in: around Semayawi hotel,
around Melekte academy, Debreberhan blanket factory and around Debreberhan
university. The office provides different functions for its surrounding inter alia 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 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 Debreberhan 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.

DEPARTMENT OF INFORMATION SYTSEM, - [2015] -1-

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
 Improving small industries to big industries.

1.3 STATEMENT OF THE PROBLEM

Currently the office is usingmanual handling system in its day to day

activities which has many problems.
These problems are:-
 Problem in distributing condominium house:-Since they do manually
it’s difficult to know the occupied class and unoccupied class surely.
 Problem in management:-since there are a lot of documents in the
office it’s 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 also 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.
 The manual lottery system is error prone, vulnerable to corruption.

1.4OBJECTIVES OF THE PROJECT

In this project we can specify the objective of the project as general objective and
specific objective.

1.4.1General objective
The general objective of this project is to develop online condominium house
management system for Debreberhan city.

DEPARTMENT OF INFORMATION SYTSEM, - [2015] -2-

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

1.4.2 Specific objectives

The specific objectives of our project are:-
 Analyze the limitations of the existing system
 Suggest alternative problems and selecting the best among the
alternative
 Analysis and design a system which is secured, efficient and user
friendly
 Design the system that will solve the current problems and provide
reliable functionalities.
 Implementation of the proposed system in efficient way
 Giving recommendation on further studies to be conducted on the areas of
condominium house management system

1.5 SIGNIFICANCE OF THE PROJECT

This document aims to give a brief description about the condominium house
management System. Accurate, timeliness, reliable, secured, relevant and
valuable data are needed for condominium house management in all dimensions.

 This project will reduces work overload of condominium house

development office workers.
 Make the work environment favorable, information dissemination from
agency to applicant/resident easily.
 The system will helps the Debreberhan city condominium house
development office workers to handle the applicant effectively and
supports the smooth functioning of the business.
 The system increase document preservation without need of large area.
 This project will provide a basis for validation and verification process.
 Fast accessibility of stored data and saving of resource.

DEPARTMENT OF INFORMATION SYTSEM, - [2015] -3-

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

1.6. FEASIBILITY STUDY

Most of information system projects have budgets and deadlines, and analysis of
factors for the feasibility forms the business case (analysis of assumptions like
resource availability and potential problem and system costs and benefits) that
justifies the expenditure on the project. The feasibility factors are in six categories.

1.6.1 Economic Feasibility

Our proposed system was justified by cost and benefit. Criteria to ensure that
effort is concentrated on project, which will give best, return at the earliest. One of
the factors, which affect the development of a new system, is the cost it would
require. The following are some of the important financial questions were asked
during preliminary investigation:
 The costs conduct a full system investigation.
 The cost of the hardware and software.
 The benefits in the form of reduced costs or fewer costly errors.
By conducting cost benefit analysis we found that our proposed system is
economically feasible due to the factor of cost and benefit and theirrelationship.
Our team has conducted analysis by identifying tangible and intangible cost
needed for system development.
 Cost of the Project
 Tangible Cost: The tangible costs to be acquired in developing the
systemare:-

 Miscellaneous Cost which includes hardware development cost

and other costs.
 Software development cost

a. Miscellaneous Cost

This cost contains the various types of costs in which we spent for the
development of the project or the University covers some of the hardware

DEPARTMENT OF INFORMATION SYTSEM, - [2015] -4-

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
expenses. The following table lists the different miscellanies costs that we spent in
the process of the development of the system.

Table 1.1: Miscellanies Costs

Resources Amount Price

Pen 6 pen 24 Birr
Printing 150pages 150 Birr
Paper 1 pack 90 Birr
Flash disk 2 450 Birr
CDRW 5 60 Birr
Laptop 1 10000 Birr
Desktop 1 By university
Total 10774 Birr

b. Software Development Cost

For this particular project we will use different software but the software is

provided by the university.

Table 1.2 Software Development Costs

Type of Software’s Price

Microsoft windows 7/8 by the university

Microsoft Office by the university

MySQL from Xampp Free down load

Visual Paradigm for UML Free download

11.0/Microsoft Visio
Notepad++ Free download
/Rational Rose
Dream waver Free download
Total 0.00 Birr

DEPARTMENT OF INFORMATION SYTSEM, - [2015] -5-

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
 Intangible Costs

Those are costs which are uncountable .The intangible costs to be acquired in
developing the system are:-
a. Human Knowledge
Our knowledge that we spent to develop the system may not be measureable
in terms of money.

Generally this project is economically feasible because its anticipated benefit is

greater than the expected cost that is listed in the above table.

1.6.2 Technical Feasibility

Our proposed system was evaluated from the technical point of view. The
assessment of this feasibility must be based on an outline design of the system
requirement in the terms of input, output, programs and procedures. Having
identified an outline system, the investigation must go on to suggest the type of
equipment, required method developing the system, of running the system once it
has been designed.
Technical issues raised during the investigation are:
 Does the existing technology sufficient for the suggested one?
 Can the system expand if developed?
Through the technology may become outdated after some period of time, due to
the fact that new version of same software supports older versions, the system
may still be used. So there are minimal constraints in this project, and it in turn
indicatesthat the solution is technically feasible.

1.6.3 Operational feasibility

It determines how the proposed system will satisfy the need of Debreberhancity
house development agency, and it also offers Secure, accurate and efficient system
to the organization. The system in which we are developing is also compatible to
all operating systems and web browsers.

DEPARTMENT OF INFORMATION SYTSEM, - [2015] -6-

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
By conducting operational feasibility study we examined whether the new project
will attain its desired objective, we also understand the degree to which the
proposed system will likely solve the problems t, so in this study we identify that
operational feasible that the system is user friendly, easy to access. It can be run
in any operating system.

1.6.4. Schedule Feasibility

The time given for this project is around seven month. First three month for
design and the next four-month are for implementation of the designed. Based on
the department schedule we also have developed our own schedule to finish the
project atop stint.

Table 1.3 time schedule for system development

Activity Submission date

December January February March- June

1.system development
proposal
2.system analysis

3.system design

4.system implementation

1.6.5. Legal and contractual feasibility

This is the process of assessing potential legal and contractual ramification due to
the construction of a system.When we first think to planned and select a system,
we have to consider law, financial reporting, standard, as well as the current
contractual obligation. Every activity that will be controlled or performed by the

DEPARTMENT OF INFORMATION SYTSEM, - [2015] -7-

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
proposed system must be controlled by the appropriate law and policy that govern
the Deberberhan housing development agency.

1.6.6 Political feasibility

Debreberhan online condominium house management systemeither directly or

indirectly it is not related with politics of the country. The main goal of the system
is to be cost benefit, get satisfaction from resident and provided quality service.
By considering the benefit that we accrue, and totally the system does not have
contact with political view.

1.7. SCOPE and LIMITATION OF THE PROJECT

1.7.1 scope of the project
The system focus on online condominium house management system will cover
only in Debreberhan 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
of time.

DEPARTMENT OF INFORMATION SYTSEM, - [2015] -8-

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
 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.
 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:-Condominium house
administrator can controls the applicant payment status regarding
condominium house from prepayment to until the applicant finish the
payment by just making a connection with the bank administrator.

1.7.2 Limitation of the project

Our system is limited only in the process condominium house management of the DebreBerhancity

The system does not include the following:

The system may not automate fully because:
 Our system does not include online payment for applicant who wants to register to get house
The above activities or subsystems are proposed system limitations because of thefollowing reasons:
 Time:-Is the main factor of limitation our proposed systems that limit its performance
because while we are developing the system it takes more time and we 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 vulnurable
 accessiblity
 Resource: - we have not laptop as an alternative when arbitrary failed the desktop
and also when the power is off for a long time.

DEPARTMENT OF INFORMATION SYTSEM, - [2015] -9-

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

1.8. METHODOLOGY
1.8.1 Data gathering techniques

For the collection of data: Observation, Interview and Document analysis was
used.

 Observation:-Observation is common methods of scientific research to

collect the data. We 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. We used interview to get information
about the existing system for developing our project. The interview was
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. Weused this method to know all about the staff
mission, vision, function and overall of their work in short and brief.

1.8.2 Analysis and Design Methodology

In the project analysis and design phase we used unified modeling language
(UML).
 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 was 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.

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 10 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
 Classes are considered as component or module and
combination of the components will give us our web based
system software.
 It is fast and widely used model due to reusability of codes.

1.8.3 Implementation Methodology

Different hardware’s were used to develop our project.

 Computer:

 Highest processor speed and latest CPU,4GB RAM, Hard disc 500 GB

 Network cable: -was used to get the internet access by connecting

internet line from internet switch to computer for further reading and
search of information from internet.
 Flash Disk and CD: -used for the movement of data from one machine to
another. We used both CD and flash disk when we move our data from
one machine to another.
Software

 Front end software

Microsoft office word:-It is very useful because it takes less time to write and
format the text, communicative effectively smart diagram and chart tools,
quickly assemble document. By looking its useful properties we used Microsoft
office word to type our project work to get all the above the benefits of it.
Power point:- was used to present the document in forms that can be
understood easily. We also used it to present our presentation in short and brief
way.

 Back end software

MYSQL: - this software was used to create the database of the project.
NOTEPAD++, Dreamweaver: - Dreamweaver is important to write our html code
and PHP codes.

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 11 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
JavaScript: - JavaScript is very interesting language used to validate data and
develop different messages. We used to validate our data which we used in html
code.
Visual paradigm, rationalrose, Edraw: To develop the UML diagrams our
project team used this software.

1.8.4 Testing methodology

Before directly deploying this system the team performed different testing for
its functionality and meeting customers need. First the team tested each unit
at each phase. So, if a problem is encountered it will immediately fixed.
Second the team performed an integration testing to check whether the
system meets all the functional requirements.

CHAPTER TWO

SYSTEM ANALYSIS
2.1 REQUIREMENT ANALYSIS DESCRIPTION
In this chapter we studied the existing system deeply, since it is necessary to know the
existing working system of office so as to develop a better system. When we
studied the existing system we 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, we also determined the requirement or the feature that
must be included in the proposed system. Furthermore by analyzing the current system,
we could also estimate how the propose system solve the setbacks of the existing
system.

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 12 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

2.2 OVERVIEW OF THE EXISTING SYSTEM

In the existing system, there are three bureaus /offices that are concerned with
the issue of giving and distributing the condominium houses for applicants.
The bureaus/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.
 Debreberhan City Municipalities Office: The condominium housing
management offices ask information about the customer to the Debreberhan
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.
 Debreberhan 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.

2.2.1Activities of the system

Here under we have listed several activities of the current system that are operated
manually:

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 13 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
 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.2 Problem of Existing System

The existing system has many problems. Among others

 Lack of accurate data ,

 The system has problems related to security.
 It takes long time to search data ,
 Lack of efficiency, effectiveness,
 Since it operable manually it uses large amount of space to store data. Lack of
portability’s,
 Redundancy of data is the most important one.

2.2.3 Business rule of the organization

1. The applicant for house should be above 18 years old

2. The applicant should be from Debreberhan city or should live for at least 6
month
3. The applicant should apply if he/she has no house that is registered by their
name before
4. The applicant must have a resident id card given from his Keble and renewed
ID card with in year.
5. The applicant should have the capacity some percent of the total cost

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 14 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
6. Women have the opportunity to get the house 20 %( affirmative action).
7. When people who are disabled have the chance to get the house ground floor
is assigned to them.
8. Payment type 100%, by division of long time payment
9. If the applicant has a house registered by him/her husband/wife he/she is
not allowed to take house.
10.When the applicant pays pre-payment he/she must agree to open closed
account at the lender bank.

2.2.4 Class responsibility collaboration modeling

CRC modeling techniques are used to model the existing system that help as build
the proposed class diagram by observing how the existing system is collaborate
with each activity. A class represents a collection of similar objects, a
responsibility is something that a class knows or does, and a collaborator is
another class that a class interacts with to fulfill its responsibilities.

Table 2.1 CRC modeling

Keble officer
Register resident Resident
Give resident id Resident
Name
Record resident date
Address
Application
age
Application for
condominium house
Resident id no
Application
Marital status

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 15 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
Name of applicant
Condominium House Condominium
address house
Condominum house
Payment form
Building
Marital status
House type House type
Age
Block name
House no
Contactor name
Site name

House type
Studio
One bed room Payment
Payment
Two bed room
Full payment
Three bed room
Pre - payment House type
Payment
Long division Application
Address of houses
payment
Block number

2.3 OVERVIEW OF THE PROPOSED SYSTEM

The proposed systemwas designed in order to reduce the problem arise in existing
system. This system has 3 administrator with different privilege,other user.
The kebele administrator registers on the Debreberhan online condominium
house management system web site. But the peoples who are going to register on
the system must be residents of Debereberhan city. If they are come from other

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 16 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
city, they must live in Debereberhan 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.

The condominium house management administrator performs different

activities on this system. Some the activities that are performed by the
condominium house management system administrators are he/she registers
user type of other condominium house administrator and to the table
user_type.Inthese tables, 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 equatingthe number of houses available and applicants, the

systemdraws 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 Debereberhan online condominium house management system

administrators can view information related to house, sites, blocks and winners of
condominium and other information’s related to condominium house. He/she
have to delete and update these information’s available in the system that are

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 17 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
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.

The condominium house management administrators will have applicant

payment status controlling page on the Debereberhan 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 and delete payer’s
information from the database and update payment, when he/she add payment.

Generally, the system will onlyallow those residents who are registered by the
kebele administrator on the Debereberhan online condominium house
management system. To apply the applicants are required to enter resident id no
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, he/she is not allowed to apply again.

2.3.1 Purpose of the proposed system

The proposed system provides:

 Efficient way of applicant’s data management:-Since the proposed system
uses database system there is no loose of data .The applicant information will
highly secured, the search and update of applicant will be simple.
 Efficient distributing method: - This means our system uses efficient lottery
system for distributing Condominium houses for the winner applicant.
 Give online information registration:-The proposed system gives online
information about Condominium house for applicant, so to know the criteria
that must be full fill to register and also can register online at a time if the
applicant far from the kebele or sub city that he/she lives.

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 18 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
 Give’s Notification information:-The proposed system will be expected to
gives notification through posting in the website and andprovidind the
notification information in the applicant user account

2.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. And Register winner after the lottery is drawn the
system canable register the winners’.
In order to draw lottery for applicant we 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 opend
user account of the applicant and provide the abilty 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 ispaid how many of
them are not start paying specified payment will be controlled.

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 19 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
 Posting news and notice: the system can post news and notice for the
people in order to make them informed by the condominium house
adminstrator.

2.2.3 Non-Functional Requirements

Nonfunctional (supplementary) 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: Our 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.
And also there must be a physical security hat secures (especially) 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’s measured
by its speed of processor.
 Back up:-The system should have back up using external hard disk. The
backup is taken weekly.

2.3.4 Systems Requirement (Hardware and Software requirement)

The Online condominium house management system needs different hardware

and software’s for the system development process.
Hardware
 Intel Processor highest processor speed

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 20 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
 8Gb RAM
 Hard disc 500 GB

Software
 Mozilla Firefox latest version
 Operating system like
 window 7 64-bit and 32-bit,
 wampp software for data storage and database management
 PHP server side programming language
 Visual paradigm to draw UML (unifying modeling language)

2.4 SYSTEM MODELING AND ARTIFACT

System modeling is a technique to express, visualize, analyze and transform the
architecture of a system. Here, our proposed system may consist of software
components, hardware components, or both and the connections between these
components. A system model is then a skeletal model of the system that help as to
model our function of the system and it is used to ensure that a developing piece
of software evolves in a consistent manner and that the task of integrating
software components is simplified.

In our project we used unified modeling language to model our system.

The Unified Modeling Language (UML) is a general-purpose modeling language in
the field of software engineering, which is designed to provide a standard way to
visualize the design of a system. There are different model diagram in UML that we
used to model the system.

 Use case modeling

 Dynamic model
 Sequence diagram
 Activity diagram

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 21 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
 Static model
 State chart diagram
 Class diagram

2.4.1 Use case modeling

Our Use case describes the behavior of the proposed system as seen from an actor’s
point view. A use case describes a function provided by the system as a set of events
that yield a visible result for the actors. In the analysis phase they represent the
functionality of the system. In our use case modeling we included collection of all
actors and all use cases.

2.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 Debreberhan
condominium house management system are listed as following:-
BR1: The applicant should be from Debreberhan city or should live for at least 6
month.
BR2: The applicant should apply if he/she 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 %( affirmative action).
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 he/she must agree to open closed
account at the lender bank.
BR8: Applicant must select type of house he/she want (studio, one bed room, two bed
rooms, three rooms).
BR9: The applicant should have the capacity some percent of the total cost.

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 22 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

online condominium house management system

manage winner Include

registration of
payment Include
applicant

applic

de »
ant

«i n
cl u

lu
Include
Include

«inc
register finihed

d
e »
«in
bank house clu
de
»
«inc
l ude Extend logout
include»
control payment Include
« include
Include »
login page register resident
» information
l ude
«inc Include »
«i
nc

de
clu
lu

notification »
de

i n
condo «
u de
»

cl
minu «in Include
»
de

m hou Include
clu

se manage resident
«in

draw lottery
admin Include
information

manage applicant

Include

manage account kebele

office
admini

Figure 2.1 Use case diagrams for proposed system

2.4.1.2 Essential use case diagram description

Each use case are described in a manner to give direction how the specified us
case are operated

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 23 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

Table 2.2use 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
system. the login interface and
Step3: by selects account allows the user for the user
type user fills his or her name and password.
username and password. Step5:display login
Step4: click login button. successful
Step6: the User gets access Step7: displays its main
the system. window.

Step8: Use case ends.

Post The main page will be displayed then user gets access to
condition its privilege and after finishing his/her work he can logout

Alternative course of action

If they user is not authorized

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

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 24 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

Table 2.3 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: a. The user must login to register the resident information

(UC_01)

b. The applicant must be presented physically

c.TheKeble administratormust check the resident

information like where did he live how many year the
applicant lives in the given Keble.
Flow Event: Actor action System response
Step1: open resident Step2: The System display
registration page from registration form
menu Step5:display register successful
Step3: fill the resident Step6: finished registration and
registration data the use case end
Step4: click register
button

Post condition Resident must be registered.

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 25 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

Alternative course of action

A.5:the system display error message if the resident information already stored in
the database

Table 2.4 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

Precondition: 1.He/she 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)
Flow Event: Actor action System response
Step 1: the applicant opens Step2 : the system display
the home page of the the home page
website. Step4: the system displays
Step3: Selectapply for the conformation page.
house. Step 6: the system display
Step5:fill resident_id and last applicant registration form
name Step7: the system display
Step7:fill the registration register successfully
form and click register message
button

Exception If there is no internet connection there is no registration.

Condition:

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 26 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

Post The applicant must be registered successfully.

condition

Alternative course of action

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 2.5 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 administratorRegister
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
Flow Event: Actor action System response
Step1: open house Step2:display house registration
registration page from menu form
Step3: fill the finished Step6:display register successful
house information data Step7: finish recording and the use
Step 4:repeat information case end
until registration is over
Step5: click register button

Exception
Condition:
Post The entire new houses that are finished must be registered or
condition recorded with their full description

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 27 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

Alternative course of action

A.1: if there is no new finished condominium house, the condominium house
management administrator stop or pause the use case.

Table 2.6 use case description for draw lottery

Use case Name Draw lottery

UC_ID: UC_05
Actor: Condominium house administrator
Description: Condominium house management office
administratordraw 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
Flow Event: Actor action System response
Step1: open draw lottery Step2: display the draw
page from menu page
Step3: fill the lottery Step6:display lottery
information successful
Step 4:repeat information Step7: finish draw lottery s
the process end and the use case end
Step5: click draw lottery
button

Exception
Condition:
Post The system must draw lottery effectively for the applicant.
condition

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 28 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

Alternative course of action

A.6: if there is no finished house the system display “there is no finished house to
draw lottery “.

Table 2.7 use case description for notification use case

Use case Name Notification

UC_ID: UC_06
Actor: Condominium house administrator
Description: Condominium house management office administrator after
drawing lottery he/she 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
Flow Event: Actor action System response
Step1: click notification Step2: display notification
page from menu page
Step3: fill the notification Step6:display sent successful
Step 4:repeat information message
the process end Step7: finish notification and
Step5: click send button the use case end

Post The entire winner must be notified

condition

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 29 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

Table 2.8 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

Flow Event: Actor action System response

Step1: click payment link Step2: display payment page
from registration form Step5:display payment
Step3: fill all payment successful message
information. Step7: finish payment and the
Step 4:click pay button use case end
Post The condominium house administrator must control payment
condition process.

Alternative course of action

A.5.1.if the applicant does not have bank account number the system display
error message.

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 30 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
A.5.2.if the applicant has insufficient balance in his/her bank account
insufficient balance message will be displayed

Table 2.9 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);
Flow Event: Actor action System response
Step 1:CHMadministrator Step2: the system displays
open payment control page the paymentcontrollingpage.
Step 3:CHM administrator
view the payment table of
the applicant.

Post The CHM administrator should view all the applicant

condition payment process data.

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 31 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

Table 2.10 use case description for manage applicant

Use case Manage applicant

Name
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

Precondition: The Administrator must login to the system to manage

applicant.
Flow Event: Actor action System response
Step 1: the Administrator Step2: the system display
click manage applicant link the manage applicant page
Step3: the administrator Step4: the system display
enter the id number of the the update form with the
applicant to update registered applicant
Step 5: the administrator information
fill the new updated Step7: display update
information of the successful page
applicant.
Step 6:click submit button

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 32 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
Flow of event (for Actor action System response
search applicant )
Step 1: the Administrator Step2 : the system display
click manage applicant link mange applicant page
Step 3: the administrator Step4: the system display
enters the id number of the the applicant information
applicant to search and Step8: finished searching
and stop the use case
click search button.

Actor action System response

Step 1: the Administrator Step2 : the system display
Flow of event
for delete click manage applicant link mange applicant page
applicant
Step 3: the administrator Step4: the system display
enters the id number of the the applicant information
applicant to search and Step6: the system display
click search button. delete successful message
Step 5:the administrator and stop the use case
enterdelete button

Alternative course action: for update applicant

A.5: the system does not display update form to update the applicant information
with the entered id.

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 33 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
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.

Alternate course action: for delete applicant

A.4: the system displays fill again message to Administrator if the entered id is
incorrect.
A.6: the system display deletion failed if the entered data are not available.
Table 2.11 use case description for managing resident 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 kebeleAdministrator must login to the system to

manage resident information
Flow Event: Actor action System response

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 34 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
Step 1: the Keble Step2: the system display
Administrator click manage the manage resident form.
resident link Step4: the system display
Step3: the administrator the update form with the
enter the id number of the registered 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
deleteresident
Step 1: the Administrator Step2 : the system display
information )
click manage resident link mange resident
Step 3: the administrator Step4: the system display
enters the id number of the the applicant information
applicant to search and Step5: finished searching
click search button. display the searched
Step 6:the applicant may information
click delete button Step 7:the system display
delete successfull message
and stop the use case

Alternate course action: for update resident information

A.4: the system display 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

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 35 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
A.4: the system displays fill again message to Administrator if the entered id is
incorrect.
A.6: the applicant may not click the delete button so that there is no display
delete successful message

2.4.1.3. Essential user interface

Invalid username and

Account type
password message
display only
User name

Password

Login button

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 36 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
Figure 2.2user interface sample for login form

Fill Applicant registration form

Full name
Input field

Address
Input field

Resident id
Input field

Marital status
Input field

Gender
Input field
apply
Physical status
Input field
Figure 2.3. Sample user for applicant
registration

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 37 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
House registration form

Block number
Input field

Site id
Input field

House type
Input field

House number
Input field

Floor number
Input field

Contratctor name Figure2.4 sample for house registration

Input field
Register

Draw lottery page

invalid or valid drawing
message display

Site name
Input field

House type
Input field

Draw lottery button

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 38 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
Figure 2.5 sample user interface for draw lottery

Message sent success full

Notification page
or sending failed message

Subject email

Body of the email

Send button

Figure2.6 sample user interface for notification

2.4.2 SEQUENCE DIAGRAM

 Sequence diagram: an "interaction diagram" that models a single scenario
executing in the system.
 A Sequence diagram is an interaction diagram that shows how processes
operate 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 (massimofelici,2011).

Key parts of a sequence diagram

 Participant
 Message

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 39 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

main login link login form login user_accou

login : keble admin
window controller nt table
UC_01 andCHM admin
actor: keble 1:admin activate UI
admin, CHMS
adminstrator
2:click login llink
1.one of the adminstrator
open system and activate 3:display login form
main window
2.the adminstrator click
on login link
3.system display login 4:select usertype fill user name and pasword
form
4.adminstrator select 5:click login button 6:validate()
user type and fill user
7: try_again
name and password
8:login to the system
4adminstrator click login 9:check()
button
6.the system validate the
data that are recorderd
7.if the filled data is
incorrec the system
display try_agin message
8.the validated data willl 10:respnse to login form
go to the database.
9.check the avalablity of
the user account
10.after checking the
avalablity of tha user
account the system
return a response(failed
to login,or login sucessful
message will be returned
to login form

Figure 2.7 sequence diagram for login

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 40 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

register registration data registration table

: resident : kebele
resident page controlor
admin
UC_02 1:ask for registration

2:check related information

3:open registration form
1. resident ask for
registration 3:1 open form
2.the kebele admin
check avalable 4: enter resident data
information 4.1 check validity
3. click the registration
form 4.1.1:return status
3.1 .the system display
5:save the resident data
the registration form
4.the kebele admin fill
the resident data 5.1:return save status
4.1 the system chek
the validty of the data 6:message
4.1.1.return status
5.save the filled data on 7: finished registration
the registration tableon
the database
5.1 return the save
status
6:display message in
the regstraation page.
7.the resident finish the
registration and leave
the office

Figure 2.8: sequence diagram for registering resident

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 41 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

Home Page Confirmition Kebele Data Controller Registration Applicant Payment Form
: Applicant
Page Database Form Registration table

1. Activate The Home Page

2. Click on Apply For House

3. Display()

4. Enter ID Number
5. Click On Enter Button

6. Check Availability

6.1 Error Message (if not Available)

7. Display()

8. Fill Form

9. Click On register

9.1 Validate()

9.2 Fill Data Again(if it is not valid)

10. Add Data to The Database

10.1 Validate()

11. Display Succsessful Message ()

12. Display()

13. Fill Form

13.1 Validate ()

14. Error Message (If The Account Number is not valid or Have no enough Balance)

15. Perform Payment

16. Display Successful Message()

Figure 2.9: sequence diagram for online registeration of applicant

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 42 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

register house registration house data house registrtaion

finished house : condominum
page controller table
UC_04 house admin
1.click register house link

1.the adminstartor 2.dispay house registration form

select the house
3: fill the registration form
registration page
2.the system display
4:click register button
the house registation
form
3the adminstrator fill 5:validate entered d...
the house information 6:fill the data again
4.click the register
button
5.the sysem validate 7:save entered house d...
the entered
information 8:check
6.the system may
display fill again
messsageif ther is un
filled or incorrect data 9:display prompt
7 the system save
the entered new
house information in
the registration table
on the data base
8 the databas check
the saved data
9 system display the
response on the
registration page.

Figure 2.10: sequence diagram for register finished house

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 43 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

draw lottery
UC_05 admin home draw lottery lottery bank lottery draw lottery winner
: condominum
page page controller table table
house admin
1.the condominum 1:clcik draw lottery link
house admin click
draw lottery link 2:open draw lottery page
2.the system open
draw lottery page 3:fill the lottery data
3. condominum
house admin fill 3.1:click draw button
4:check validity
the lottery data
3.1click the draw 4.1: filllottery data again
button
4 the system 5.draw lottery
check the validity
of the filled data
5 the system draw 5.1 return lottery failure
lottery
6.the system save 6:save the lottery data
the data in to
lottery winner table
6.1 the system 6.1 return status
return the status 7 load status of lottery
7.system load
status of lottery

Figure 2.11: sequence diagram for draw lottery

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 44 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

notification admin home notification data controller notificatio

: condominum
UC_06 page page n table
house admin
1:click notification link
1.condominium house 1.1:open notification page
admin click
notification link 2:insert email id
1.1: the system
display the notification 3.insert notification message
page
2.the admin insert 4:click send button
winner email id
3.nsert the notification
message 4.1:check validity of email
4.click send button
4.1 the system 5 return response
validiate the email 6:save the notification data
address
5. return response
(failed/sucess)
6 the system save the
notifiation data

Figure 2.12:sequence diagram for notification

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 45 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

manage
applicant manage registration data appliant
:
UC_09 applicant form controller table
condomin...

1 .condominum house 1:clcik manage applicant link

admin click manage
appliant link
1.1 the system open 1.1:open the registration form
the manage applicant
page
2.the admin insert
2.insert id
applicant id
3.clcik search button
3. click search button
3.1 check the validity 3.1 check the validity of id
of id
3.2 if the ID is 3.2:return response
incorrect the system
display fill the correct 3.3:retrive the appliant data
id message
3.3 if the id is correct 3.4:check
the system search the 4: display the registered appliant data
data from table.
3.4 the system check
existing data
5.1:enter modifed data
4: if there is
registered data
display the data 5.2:click update button
5.1.if the admin need
5.3:check validity
to update replace the
existing data ,edit the
register data
5.2.clik update button 6:save updated data
5.3.check validity
5.4.return error
response if entered 6.1:check existing data
data is not correct
6:if data is correct 7: return success/failed response
the system save
updated data
6.1 system check
existing data
7 .return update
sucessful if the data
is updated

Figure 2.13: sequence diagram for mange applicant

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 46 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

2.4.3 ACTIVITY DIAGRAM

The basic purposes of activity diagrams are to captures the dynamic behavior of
the system. As we 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.Activity is a particular operation of the system.
Activity 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. Activity diagram does not show any message flow
from one activity to another (julee Kendal,2011)

user browse display click on display fill user name,acount

website home page login link login form type password

login
UC_01 not correct validate
actor :condominum
house adminstrator correct
kebele adminstrator
display
user page

Figure2.14: activity diagrams for login

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 47 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

keble admin browse display display fill user name,acount

click on
website home page login link login form type password

register not correct validate

resident correct
UC_02
actor keble display kebele
adminstrator admin page

click register
resident link

display
registration form
incorrect
fill the resident
information

logout dispaly register correct check clik register

sucess fulmessage button

Figure 2.15:activitydiagrams for registering resident

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 48 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

condominum
house admin browse display click on display fill user name,acount
website home page login link login form type password

not correct validate

register finished
house correct
UC_04 display condominum
actor ondominum admin page
house
adminstrator
click register
new house link

display house
registration form
incorrect
fill house
information

logout dispaly register correct check clik register

sucess fulmessage button

Figure 2.16: activity diagramsfor registering finished house

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 49 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

condominum admin fill user name,acount

browse display click on display
website home page login link login form type password

not correct validate

draw lottery correct
UC_05 display condominum
actor admin page
condominum
house click draw
adminstrator lottery link

display draw
incorrect lottery page

fill lottery
data

logout display list of correct check clik draw

winner lottery button

Figure 2.17: activity diagrams for draw lottery

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 50 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

condominum
house admin browse display click on display fill user name,acount
website home page login link login form type password

not correct validate

correct
notification
UC_06 display condominum
actor condominum admin page
house adminstrator

click notification
link

display
incorrect notification page
enter winner email
id and notification

logout display sent correct check clik send

successful message

Figure 2.18:activitydiagrams for notification

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 51 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

condominum
house admin browse display fill user name,acount
click on display
website home page login link login form type password

not correct validate

manage appliant (update correct
appliant) display condominum
UC_08 admin page
actor condominum house
adminstrator
manage
appliant link

display manage
not valid applicant page
incorrect
insert id no to
search
click update enter display registered
correct check click search
button new data data
button
valid

display update logout

successful message

Figure 2.19: Activity diagram for updating applicant

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 52 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

condominum house admin

browse display click on display fill user name,acount
website home page login link login form type password

not correct validate

manage appliant correct
(delete appliant)
display condominum
UC_08
admin page
actor condominum
house adminstrator manage
appliant link

display manage
applicant page
not valid
incorrect
insert id no to
search

display registration check click search

click delete correct
form button
button
valid
display delete
successful message

logout

Figure 2.20:Activity diagram for deleting applicant

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 53 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

adminstrator
browse display click on manage display manage click add
website home page acount acount page account

display
account form
manage account (add
enter new account
account)
information
UC_10
actor :condominum click on
house adminstrator submit button
kebele adminstrator not correct
check

correct

logout created

Figure 2.21: Activity diagram for adding account

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 54 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

adminstrator
browse display click on manage display manage click on change
website home page acount acount page account

display
account form
manage account
enter new updated
(update account)
information
UC_010
actor :condominum click on
house adminstrator submit button
kebele adminstrator not correct
check

correct

logout updated

Figure 2.22: Activity diagram for update account

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 55 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

condominum click on delete

click on manage display manage
house adm... browse display
account
website home page acount acount page

display
account form
manage account
(delete account)
enter acount
UC_010
data to delete
actor :condominum
house adminstrator
kebele adminstrator click on
delete button
not correct
check

correct

logout deleted

Figure 2.23: Activity diagram for delete account

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 56 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

2.4.4. State chart diagram

As its name indicates, it clarifies the purpose of the diagram and other details. It
also describes different states of a component in a system. The states are specific
to a component/object of a system. Constructing state chart diagram to clarify
different states of an object and these states are controlled by external or internal
events. The state chart diagram for different activity is constructed in the following
way(julee Kendal,2011).

browse display click on display login fill user name,acount

website home page login link form type password

not correct validate

idle

correct

intial state
display
final state user page
complete state

Figure 2.24:state chart diagram for login

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 57 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

intial state display kebele

idle display loged in
home page admin page

registration
form
incorrect
fill the resident
information

registered correct check clik register

button
complete state

final state

Figure 2.25:state chart diagram for register resident

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 58 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

display login display condominum

idle
intial state home page admin page

click register
new house link

display house
registration form
incorrect
fill house
information

registered correct check clik register

house button

complete state

final state

Figure 2.26:state chart diagram for register finished house

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 59 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

idle display login in display condominum

intial state home page admin page

click draw
lottery link

display draw
lottery page
incorrect

fill lottery
data

display list of correct check clik draw

winner lottery button

complete state

final state

Figure 2.27:state chart diagramsfor draw lottery

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 60 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

browse display home click on display condominum

intial state website page login link admin page

click notification
link

display
notification page
incorrect
enter winner email id
and notification

sent message correct check clik send

complete state

final state

Figure 2.28: state chart diagrams for notification

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 61 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

click on manage display manage click on update

idle display applicant
home page applicant applicant page

not correct display

intial state registration form

enter new updated

information

updated correct check click on submit

button

complete state
final state

Figure 2.29:state chart diagram for update applicant

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 62 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

idle display login in display manage click on delete

intial state home page applicant applicant

display
registration form

enter applicant
data to delete

click on delete
not correct button
check
correct
deleted
final state
complete state

Figure 2.30: state chart diagram for delete applicant

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 63 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

idle display click on manage display manage click on add

home page acount acount page account

not correct display

account form
intial state

enter new account

information

created correct check click on submit

button

complete state

final state

Figure 2.31: state chart diagram for add account

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 64 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

idle display click on manage display manage click on change

home page acount acount page account

not correct
display
account form
intial state

enter new updated

information

updated correct check click on submit

button

complete state

final state

Figure 2.32: state chart diagram for update account

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 65 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

idle display loged in display manage click on delete

intial state home page acount page account

display
account form

enter acount
data to delete

click on delete
not correct button

check

correct

deleted
final state
complete state

Figure 2.33: state chart diagrams for delete account

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 66 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

2.4.5Class responsibility collaboration modeling for the proposed system

1. Identified CRC modeling for each class

Table 2.12 CRC modeling for the proposed system

Keble adminsitator<<actor> Resident <<actor>>

Register resident Name

Give resident id Resident Address
Applicant
Record resident date age
Application for
condominium house
Resident id no
Applicant<< actor>> Marital status
Name of applicant
Condominium House house
Registration of house <<UI>
address
Building
Marital status
House type Condominium
House application
Block name house
Age
House no administrator
Gender
Contactor name
payment
Site name
Condominium
house
User account <<UI>> administrator
Account type
User name of administrator Keble admin
Password of administrator CHM admin
Account no

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 67 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

Condominum house administrator <<actor>>

Register house
Draw lottery Registration of House
Send notification for Applicant
winner user account
Manage applicant draw lottery
Manage user account notification
Control payment

2. Identified Classes from the Use Case and CRC

Use cases Classes

1.registration applicant Applicant

2.registration of resident Kebele administrator
3.registration of finished house CHMS administrator
4.draw lottery CHMS administrator
5.notification CHMS administrator
6.payment applicant
7.control payment CHMS administrator
8 manage applicant information CHMS administrator
9.manage resident information Kebele administrator
10.mange user account Kebele administrator ,CHMS
administrator,

Table 2.13identified class from use case

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 68 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
3. Identifying the responsibility of each class

1. Applicant
Used to represent the person who needs to register for getting condominium house
2. Resident
It is a person who is a resident in a specified Keble and who need to register on
kebele database and get the necessary service he need and in system the resident
may become an applicant
3. kebele 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

4. CHMS administrator

It is the representation of the real world condominium house management

administration, which uses an automated system to manage.

5. House

House is the representation of the real world class of materials.

We have the following attributes and operation in each class

 Applicant

 Attributes:applicant_id, house_type
 Operation:apply (), pay_ payment ()

 Resident

 Attributes: first name, last name middle name, physical status, gender,
resident id number , age, occupation, house_no, keble, woreda,phone_no, e-
mail,
 Operation: register ()

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 69 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
 Keble administrator

 Attributes:first_name, last_name, phone_no, email

 Operation: register resident (), manage resident information (), manage
account

 CHMS administrator

 Attributes: first name, last name, phone_no, e_mail.

 Operation: manage applicant, manage account (),draw
lottery(),notification(),placement ,payment control().

 User Account

 Attributes: username, password and usertype

o Operation: create account ()

 House

 Attributes: house number, house type, block name , block number , site
name ,contractor information
 Operation: house registration ().

4. Identifying The Relationship Between Classes

In our analysis class diagram, the following types of relationship exists

Association relationship exists between the following classes:

A. one-to-one relationship
Resident to applicant

 One resident should only register as applicant once

Applicant to house
 One applicant can only register to get one house only
B. one-to-many relationship

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 70 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
Kebele administrator to user account
 one kebele administrator can add new user account and many user
account of kebele administration privilege may be available
CHMA to user account
 one CHMS administrator can add new user account and many user
account of CHMS administration privilege may available
Kebele administrator to resident.
 One kebele administrator has the privilege to register many resident
information
CHMA to house
 one CHMS administrator can register and manage multiple house

2.4.6Analysis Level of Class Diagram

Class Diagrams are 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.
Our 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 our system want to manage.

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 71 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
 Bank administrator: it is an administrator that manage winner payment
process

Figure2.34: analysis level class diagrams

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 72 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

CHAPTER THREE

SYSTEM DESIGN
3.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 we can use
structured or object oriented approaches.
In the case of online Debreberhan condominium house management system our
system design modeling,willfill the gap between the system specification produced
during requirement elicitation and analysis which is concentrated on the purpose
and the functionality of the onlineDebreberhan 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.

3.2 DESIGN GOAL

In our system development process system design part is very important so as 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 non-
functional requirement is the description of the feature characters and attributes
of the system.

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 73 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
Some of the design goals are:-
 Security- The system should be secured that unauthorized user can not
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 (error message)
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
(like name phone no, Email address).
 Modifiability:-The proposed system able to handle applicant data based 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: - 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: - online condominium house managementsystem 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.

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 74 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

3.3 SYSTEM DECOMPOSITION

The system is divided in to modules. There are five modules in this system with
their function. Those modules are Registration module, placement module,
security module and Notification module, payment module
 Registration module
 Register resident
 Register applicant
 Register house
 Draw lottery
 Security module
 Login page
 Password
 User name
 User Type
 Only administrators of kebele, condominium administrator and have their
own page on the Debereberhan online condominium house management
system page .they will perform those activity listed on each page.
 Notification module
 Posting notification information through
 Email
 Posting on the website front page
 Payment module
 Payment can be
 Pre-payment type
 Long division payment type
 Full payment type

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 75 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

payment
notification

security online condominum

house managment
system draw lottery

registration

applicant
house registration
registration

Figure 3.1 system decomposition diagrams

3.4COLLABORATION DIAGRAM
A collaboration diagram describes interactions among objects in terms of
sequenced messages. Collaboration diagrams represent a combination of
information taken from class, sequence, and use case diagrams describing both
the static structure and dynamic behavior of a system (julee Kendal,2011).

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 76 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

1: 1:user ativate UI 2: 2:click login link

main login
window link
admin 9: 9:display adminstrator home page
adminstrator
5: 5:click login button
home page
8: 8:login to the system
6: 6:validate()
4: 4:select account type fill username and passward
login
controller

3: 3:display login form

7: 7:try again

login
form

Figure 3.2 collaboration diagrams for login

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 77 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

3: 3:open registration f...

5: 4: enter resident data 8: 5:save the resident data
registration registration
page table
: kebele admin 4: 3:1 open form 9: 5.1:return save status
10: 6:message

1: 1:ask for registration 7: 4.1.1:return status

6: 4.1 check validity

2: 2:check related information

11: 7: finished registration

data
controlor
: resident

Figure 3.3colaboration diagram for resident registration

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 78 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

house registration
1: 1.click register house link page
3: 3: fill the registration form
8: 8:check
2: 2.dispay house registration form 9: 9:display prompt

6: 6:fill the data again house registrtaion

: condominum table
house admin 4: 4:click register button
7: 7:save entered house data

5: 5:validate entered data

house data
controller

Figure 3.4 collaboration diagram finished house registration

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 79 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

draw lottery
page 9: 6:save the lottery data
3: 3:fill the lottery data
10: 6.1 return status lottery winner
table
2: 2:open draw lottery page
11: 7 load status of lottery 7: 5.draw lottery
: condominum
house admin
6: 4.1: filllottery data again 8: 5.1 return lottery failure
4: 3.1:click draw button

1: 1:clcik draw lottery link lottery draw

5: 4:check validity table

admin home lottery bank

page controller

Figure 3.5 collaboration diagrams for draw lottery

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 80 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

admin home
page

1: 1:click notification link

3: 2:insert email id 7: 5 return response
4: 3.insert notification message
notification
page
2: 1.1:open notification page
: condominum
house admin

5: 4:click send button

6: 4.1:check validity of email

8: 6:save the notification data

data notification
controller table

Figure 3.6 collaboration diagrams for notification

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 81 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

3: 2.insert id
1: 1:clcik manage applicant link 10: 5.1:enter modifed data registration
manage form
: condominum
house admin applicant 2: 1.1:open the registration form

9: 4: display the registered appliant d...

6: 3.2:return response 15: 7: return success/failed response
4: 3.clcik search button
11: 5.2:click update button
8: 3.4:check
14: 6.1:check existing data
5: 3.1 check the validity of...
12: 5.3:check validity
appliant
7: 3.3:retrive the appliant d... table
13: 6:save updated data

data
controller

Figure 3.7collaboration diagram for manage applicant

3.5 SYSTEM ARCHITECTURE

In our project the team used 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 class which the team uses to write the function which works as a mediator
to transfer data from application layer or presentation layer to data layer. This

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 82 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
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 team can get or set the data using
these properties into the variables. The third tire is the data access layer which 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.

Interface (User interface, System Interface)

()

ProcessApplication, Controller) System

(User interface, System Interface) (Infrastructure, Platform)

(Application, Controller)
Domain (Business)

(Business)(Data)
Persistence

(Data)
Data sources

Figure 3.8system architecture

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 83 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

3.6 COMPONENT DIAGRAM

Component diagrams are used to model physical aspects of a system or element
like executable libraries, files document. Proposed system building component
diagrams are used to visualize the condominium house management office and
relationships among components in a system. These diagrams are also used to
make executable systems.

register house
«executable »

draw lottery
«executable »

notification
CHMO Adminstrator «executable »
security
manage placement «infrastructure »
«executable »

bank adminstrator
manage applicant
«executable »

payment control persistance

«executable » «infrastructure »
kebele administrator

manage payment
«executable »

Database
manage account
applicant «Table »
«executable »

register resident
«executable »

manage residant
«executable »

register applicant
«executable »

search winning status

«executable »

Figure 3.9 component diagram

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 84 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
3.7 User interface prototyping design

Figure 3.10user interface prototype design

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 85 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

3.9DESIGN OF CLASS DIAGRAM (CLASS MAPPING)

Figure 3.11 design of class diagram (class mapping)

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 86 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

3.10DATA BASE DESIGN (PERSISTENT MODELING)

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 data base

Figure 3.12 database design

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 87 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

3.11DEPLOYMENT DIAGRAM
Deployment diagram shows execution architecture of systems that represent the
assignment (deployment) of software artifacts to deployment targets
(usually nodes).Deployment diagrams 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

application
server
register
HTTPS house SQL
database_server
client draw
browser lottery

CHMO notification
security persistence
adminstrator
control
payment
manage
applicant database
manage
bank
winner
adminstrator
payment

manage
user
account
register
keble resident
adminstrator
manage
residant
applicant
register
applicant
search
winning
status

Figure 3.13 deployment diagram

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 88 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

Chapter four
SYSTEM IMPLEMENTATION
4.1 introduction

Implementation is an understanding of a technical specification or algorithm as

a program, software component, or other computer system through computer

programming and deployment. In our project, implementation exist for a given

specification or standard. So the team is in a position of converting all documents
gathered and designed into the code so that the system will be implemented for
the user to be used for the purpose it developed. To implement it, the organization
must host the site and must have server system.

4.2. Sample user interface

In this system, users will interact with the system through the following user
interfaces.

Home Page: This form appears on the site in which the system deployed is opened
and contains some links which lead the user to other page according to his/her
privilege, and if the user is authorized user or has an account, he/she will directly
go to the page that he/she wants by entering correct category, User ID and
password, for applying to get house and other privileged administrator also can
login and perform different task

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 89 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

Fig: 4.1: User Interface Design for Home

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 90 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

Fig: 4.2: User Interface Design for login

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 91 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

Fig: 4.3: User Interface Design forapply form

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 92 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

Fig: 4.4: User Interface Design for draw lottery

4.3Testing methodology
 Unit testing

Unit testing is a software development process in which the smallest testable parts
of an application, called units, are individually and independently scrutinized for
proper operation. Unit testing involves only those characteristics that are vital to
the performance of the unit under test. This encourages developers to modify the
source code without immediate concerns about how such changes might affect the
functioning of other units or the program as a whole. Once all of the units in a
program have been found to be working in the most efficient and error-free
manner possible, larger components of the program can be evaluated by means of
integration testing.
 Integration testing

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 93 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
Integration testing, also known as integration and testing (I&T), is a software
development process which program units are combined and tested as groups in
multiple ways. There are two major ways of carrying out an integration test, called
the bottom-up method and the top-down method. Bottom-up integration testing
begins with unit testing, followed by tests of progressively higher-level
combinations of units called modules or builds. In top-down integration testing,
the highest-level modules are tested first and progressively lower-level modules
are tested after that. In a comprehensive software development environment,
bottom-up testing is usually done first, followed by top-down testing. The process
concludes with multiple tests of the complete application, preferably in scenarios
designed to mimic those it will encounter in customers' computers, systems and
networks.
 Alpha testing
In this testing method, the system will tested by giving the correct input. It is
tested by a customer at the developer Site.
 Beta testing
In this testing method, team forced the system to be tested for incorrect data
input. The System was tested by the customer at their actual work place.
If any failures occurred while testing the system in all the above testing methods,
the team took immediate correction beginning where this fault occurred before
jumping to next work so that it will meet the goal. If all the above testing methods
are carried out and find to be valid the system was directly deployed.

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 94 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

CHAPTER FIVE
5.1 PROTOTYPE DEVELOPMENT
Prototype development can be defined it is the sample code of the given project. These are
some of the sample codes that we have done it.

//login sample code

<?php

session_start();//Start session

require_once('connection.php');//Include database connection details

$errmsg_arr = array();//Array to store validation errors

$errflag = false; //Validation error flag

//Connect to mysql server

$link = mysql_connect($mysql_hostname, $mysql_user, $mysql_password);

if(!$link) {

die('Failed to connect to server: ' . mysql_error());

$db = mysql_select_db("condominium");

if(!$db) {

header("location:login.php");

exit();

//echo"try to insert all necessary values";

$errflag = true;

//exit();

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 95 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
//Function to sanitize values received from the form. Prevents SQL injection

function clean($str) {

$str = @trim($str);

if(get_magic_quotes_gpc()) {

$str = stripslashes($str);

returnmysql_real_escape_string($str);

//Sanitize the POST values

$UserType = $_POST['UserType'];

$UserName = $_POST['UserName'];

$Password = $_POST['Password'];

//Create query

/*$qry="SELECT * FROM User_Type WHERE UserType='$UserType' AND

UserName='$UserName' AND Password='$Password'";*/

$qry="SELECT * FROM user_type WHERE UserType='$UserType' AND

UserName='$UserName' AND Password='".md5($_POST['Password'])."'";

$result=mysql_query($qry);

//Check whether the query was successful or not

if($result) {

if((mysql_num_rows($result)== 1)&& ($UserType =='condominium')) {

//Login Successful

session_regenerate_id();

$user = mysql_fetch_assoc($result);

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 96 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
$_SESSION['SESS_UTYPE'] = $user['UserType'];

$_SESSION['SESS_UNAME'] = $user['UserName'];

$_SESSION['SESS_PASSWORD'] = $user['Password'];

session_write_close();

header("location:condominiumAdmin.php");

exit();

else if((mysql_num_rows($result)== 1)&& ($UserType =='kebele')) {

//Login Successful

session_regenerate_id();

$user = mysql_fetch_assoc($result);

$_SESSION['SESS_UTYPE'] = $user['UserType'];

$_SESSION['SESS_UNAME'] = $user['UserName'];

$_SESSION['SESS_PASSWORD'] = $user['Password'];

session_write_close();

header("location:kebeleAdmin.php");

exit();

else if((mysql_num_rows($result) == 1)&& ($UserType =='bank')) {

//Login Successful

session_regenerate_id();

$user = mysql_fetch_assoc($result);

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 97 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
$_SESSION['SESS_UTYPE'] = $user['UserType'];

$_SESSION['SESS_UNAME'] = $user['UserName'];

$_SESSION['SESS_PASSWORD'] = $user['Password'];

session_write_close();

header("location:bankAdmin.php");

exit();

else {

//Login failed

header("location:login.php");

//echo"pleaseenter your password and your user name and select user type
to select database";

exit();

else {

die("synatx error in the query");

?>

<link href="css/styless.css" rel='stylesheet' type='text/css' />

<link href='http://fonts.googleapis.com/css?family=Open+Sans:700,300,600,800,400'
rel='stylesheet' type='text/css'>

<link href='http://fonts.googleapis.com/css?family=Marvel:400,700' rel='stylesheet'

type='text/css'>

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 98 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

<script src="js/jquery-1.8.0.min.js" type="text/javascript"></script>

<!--[if lt IE 9]>

<scriptsrc="js/modernizr.custom.js"></script>

<![endif]-->

<script src="js/jquery.carouFredSel-5.5.0-packed.js" type="text/javascript"></script>

<script src="js/functions.js" type="text/javascript"></script>

<script language="javascript">

var flag=0;

functionusertype()

user=loginform.UserType.value;

if(user=="0")

document.getElementById("error3").innerHTML="select user type";

document.getElementById("UserType").style.borderColor='red';

flag=1;

function check(form)

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 99 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
flag=0;

usertype();

if(flag==1)

return false;

else

return true;

</script>

</head>

//House insertion sample code

<?php

include("connection.php");

?>

<?php

session_start();

if(empty($_POST))

$_SESSION['house']=array();

$BlockNo = $_POST['BlockNo'];

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 100 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
$SiteId = $_POST['SiteId'];

$HouseType = $_POST['HouseType'];

$FloorType = $_POST['FloorType'];

$ServiceType = $_POST['ServiceType'];

$reserved = $_POST['reserved'];

if(empty($BlockNo) && empty($SiteId) || empty($HouseType) ||

empty($FloorType) || empty($ServiceType) || empty($reserved))

header("location:house.php");

exit();

$link=mysql_connect("localhost","root","");

mysql_select_db("condominium",$link);

$p="select * from house";

$ros=mysql_query($p,$link);

$q="insert into
house(BlockNo,SiteId,HouseType,FloorType,ServiceType,reserved)

values('$BlockNo','$SiteId','$HouseType','$FloorType','$ServiceType','$reserved')";

$query=$link.mysql_query($q);

if(!$query)

echo"UNABLE TO INSERT".mysql_error();

}else{

header("location:housesuccess.php");

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 101 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
echo"inserted successfully";

exit();

$link.mysql_close();

?>

//Apply for house sample code

<?php

session_start();

if( !$_SESSION['user_no'])

header('location: login.php');

?>

<?php

include("connection.php");

//mag show sang information sang user nga nag login

$user_id=$_SESSION['user_no'] ;

$result=mysql_query("select * from User_Type where

user_no='$user_id'")or die(mysql_error);

//$FirstName=$row['FirstName'];

//$LastName=$row['LastName'];

?>

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 102 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
<?php

$_SESSION['applicant']=array();

//$ApplicantId = $_POST['ApplicantId'];

$ResidentId = $_POST['ResidentId'];

$ServiceType = $_POST['ServiceType'];

$HouseType = $_POST['HouseType'];

$SiteId = $_POST['SiteId'];

$PhysicalStatus = $_POST['PhysicalStatus'];

$Gender = $_POST['Gender'];

$Email = $_POST['Email'];

$MartialStatus = $_POST['MartialStatus'];

$winstatus = $_POST['win'];

if(empty($_POST['ApplicantId']) && empty($_POST['ResidentId']) ||

empty($_POST['ServiceType']) || empty($_POST['HouseType']) ||
empty($_POST['PhysicalStatus']) || empty($_POST['Gender']) || empty($_POST['MartialStatus'])
|| empty($_POST['Email']) )

echo "empty value";

header("location:Applicant.php");

$ResidentId = $_POST['ResidentId'];

if($ResidentId != '') {

$qry = "SELECT * FROM applicant WHERE ResidentId='$ResidentId'";

$result = mysql_query($qry);

$_SESSION['SESS_ResidentId'] = $result['ResidentId'];

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 103 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
if($result) {

if(mysql_num_rows($result) > 0) {

echo"you are aleadyapplayed ";

header("location:aplayform.php");

exit();}

else {

die("Query failed");

$q="insert into
applicant(ApplicantId,ResidentId,ServiceType,HouseType,SiteId,PhysicalStatus,Gender,Email,Mar
tialStatus,win,user_no)

values('$ResidentId','$ResidentId','$ServiceType','$HouseType','$SiteId','$PhysicalStatus','
$Gender','$Email','$MartialStatus','$winstatus','$user_id')";

$query=mysql_query($q);

if($query){

echo"you have aplied successfully!";

echo '<meta content="2;bankAdmin1.php" http-equiv="refresh"/>';

else{

echo"UNABLE TO INSERT".mysql_error();

echo '<meta content="2;bankAdmin1.php" http-equiv="refresh"/>';

?>

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 104 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

CHAPTER six
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 willprovide online application, so that the
resident can apply from home or anywhere else via such system. Our proposed
onlinecondominium 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 we were trying to assess the existing system and studying each
and every activity of the existing system by conducting different data gathering
methodology. Then after examination of the limitation of existing system we
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
toaccomplish the objective of the proposed system implementation tool such as
(PHP, MYSQL, HTML…ETC) and design model such as (use casemodeling,
sequence diagram are specified and most of the designing tool were used in
chapter twoandthree. Home page, main page, and other page functionality
loginisillustrated. The activity diagram shows different type of user interacts with
the system.Furthermore, the use cases showed what the user will do with the
system. And finally each class and attribute wasexplained 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
we conclude that the proposed system that we designed to implement will be

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 105 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
efficient and effective one to solve current problem, if we implement it in carefully
planned manner.

5.2Recommendation
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 we need to rethink how we use such
technology with in the environment which is not easily adopted with.

However,theliterature 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 we are designed to implement does not include or perform other
functionality, so 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 managementfunctionality,
security mechanism like digital signature.

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 106 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

APPENDEX
Symbol Description
Actor

System boundary

Decision

Use case

class

Object life line

Deployment diagram

Message line extends from the lifeline of one

object to the lifeline of another object.
Include, relates to the include use case to
indicate inserted behavior

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 107 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015
Create Return Message

Starting point of activity/state diagram

Ending point of activity/state diagram

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 108 -

 ONLINE CONDOMINIUM HOUSE MANAGEMENT SYSTEM 2015

REFERENCES
1. ZELALEM YIRGA ADAMU,(2012),bahir Dar; Condominium; 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. Bahir Dar City Administration. (2006). City Administration Model Condominium Agreement
and Housing. Bahir Dar: Ethiopia.
5. Benjaminsen, T. and Lund, C. (Eds.) (2002). Securing land rights in Africa. The European
Journal of Development Research, 14, (2), 11-30.
6. 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
7. SYSTEM ANALYSIS AND DESIGN 8thedtionkennethekendall and julee.kendall
8. Ambler, Scott (2001) The Object primer: The application Developers Guide to Object Oriented
and the UML.2nd rev. Ed England: The Cambridge University Press.
9. Massimofelici(2011) 3rd edtion object oriented ANALYSIS AND DESIGN OF SYSTEM
10. http://msdn.microsoft.com/en-us/library/dd409393.aspx
11. http://www.sourcecodester.com/php
12. http://www.w3schools.com/php/php_mysql_intro.asp

DEPARTMENT OF INFORMATION SYTSEM, - [2015] - 109 -