Final Document Group 5 Sec One
Final Document Group 5 Sec One
Final Document Group 5 Sec One
By
Mekelle University
School of Computing
2015/16
Certificate
By
Acknowledgement
First of all thanks to God for helping us to overcome this project. Then our grateful
thanks go to our advisor Instructor. Fkrezgy Yohhanes for his special contribution,
support, directions assistance, guidance and helping us throughout the project. Special
thanks should be given to our department supplying project writing guidelines and
noticing the final time of the project which accelerated us to accomplish our task at a
time. Besides, this project makes us realized the value of working together as a team
in sharing and developing ideas, which challenges use every minute. Not forget, great
appreciation go to Mekelle Town Land Administration staffs who played a great role
in our analysis phase by giving us information we want. Their patience and responses
to our question is unforgettable. The whole program really brought us together to
appreciate the true value of friendship and respect of each other.
Abstract
This project is concerned with the introduction, analysis, design and later on the
implementation of LRS. The current Land registration system is currently working by
using manual way which means fully paperwork, which consist a lot of man power
and time in managing the record and Registration process. And human mistake is
unavoidable while the workload is increasing. Therefore we motivate for the
developing of Land Registration System, which making their Registration process
form paperwork into automate system. Land registration system other than replace
their manual work such as Registration, Transaction, also including new function such
as online View Parcel information any time anywhere.
Contents
Chapter one ................................................................................................................................ 1
1. INTRODUCTION ......................................................................................................... 1
1.1 Background of the project .................................................................................................... 1
1.2 Statements of the problem ............................................................................................... 2
1.3 Objective of the study ...................................................................................................... 2
1.3.1 General objective ...................................................................................................... 2
1.3.2 Specific objective ...................................................................................................... 2
1.4 Significance of the project ............................................................................................... 3
1.5. Scope of the project ........................................................................................................ 3
1.6 Methodology .................................................................................................................... 4
; 1.6.1 Data sources ......................................................................................................... 4
1.6.2 Data collection method ............................................................................................. 4
1.6.3 Tools to use ............................................................................................................... 4
1.6.4 Software use .............................................................................................................. 5
1.7. Budget planning .............................................................................................................. 5
1.8. Time schedule ................................................................................................................. 5
Chapter Two .............................................................................................................................. 6
System Analysis ..................................................................................................................... 6
2. Introduction .................................................................................................................... 6
2.1. Purpose of the project ................................................................................................. 7
2.2. Scope of the system .................................................................................................... 7
2.3. Objectives and success criteria of the project ............................................................. 7
2.4. Definitions, acronyms, and abbreviations ................................................................... 7
2.5. Current system description ......................................................................................... 8
2.5.1 Registration Procedure and Registration................................................................... 8
2.6. The proposed system................................................................................................... 9
2.6.2 Functional requirement ........................................................................................... 10
2.6.3 Nonfunctional requirement ..................................................................................... 12
2.7. System modeling........................................................................................................... 14
2.7.1 Scenarios ................................................................................................................. 14
2.7.2 Use case Diagram ................................................................................................... 14
2.7.3. Use case description .............................................................................................. 17
Table of figures
Chapter one
1. INTRODUCTION
Development literature is filled with information concerning the importance of land
and land rights in the economic development process. Individual and secure land
tenure rights are vital components of a productive agricultural sector, which is crucial
to poverty alleviation and economic growth. In most instances, secure land tenure
requires that legal rights to land are adequately defined and documented. Defining and
documenting land owners' legal rights and the extent of the landholding are important
for simplifying land transactions, using land as collateral for credit, and enabling land
administration.
1. Residence
2. Business
3. Social service
4. Industry
5. Urban agriculture
6. Mixed use
Data storage and retrieval system is not automated. The amount of vacant land
and plotted land is known but not recorded in the database.
There is high redundancy in data storage.
Land preparation and allocation for investment is inefficient and time
consuming that results delays and frustration especially for investors.
This discourages investment activity in the city.
Allocation of a given pieces of land to more than one applications owner
leading to conflicts.
Cross checking manual documents of the owner by document identification
method is very difficult.
Very let delivery of owners land registration
It is less secure as it is vulnerable to unauthorized access; any one enters to the
office see owners profile, edit manual document, data theft and unauthorized
data modification as it’s accessible by anyone who has access to the room
(including the janitors).
Design a system that could be applicable to the city land administration office.
However the issue of land taxation would be out of our scope. Since it has its
own administration.
The system is web based and mainly used for Land registration purpose.
It allows to update owners profile when land bequests, splitting, merging,
selling is needed.
The system allows the following operation:
Searching
Updating
deleting record
1.6 Methodology
; 1.6.1 Data sources
The main data source for this project was the office of Mekelle city land
administration.
8 Transportation - - 150birr
9 Laptop 1 - -
Total 594ETB
Chapter Two
System Analysis
2. Introduction
There is land registration process in Ethiopia land registration is a process of
registering land information which is an immovable property of the person who have
the right to hold land. In the case of mekelle city there is a land registration institution.
The registration institution has a responsibility of registering and issuing certificate
for land owner. But the registry process is done by manual registry form.
Customer (Land Owner): a person who have the right to hold land or the owner of
the land.
Administrator: A person who control or manage all the functionality of the system.
Parcel: means an area of land its boundary extent is clearly defined and demarcated
on the ground and drawn upon a map with rights having a unique parcel identification
code;
2.6.1 Overview
The proposed system is also efficient in file handling system. The major thing in the
proposed system is authenticating typical users. Authorized users only access the
system. Unauthorized person is not allowed to access the system. They are prevented
by user name and password mechanism.
The need to develop automating registration system of the Mekelle town land
administration to register land is that current activities of the administration are time
consuming and labor intensive due to manual system. Consequently delays the
development of the town.
The system registers Land information of the owner easily to identify individuals who
own lands. When an individual requests for land, first his full information is
registered and checked on a database weather he has register land before means The
system identifies the customer whether he/she is resident or new comer by checking
their document id during registration. Services given by proposed system are
summarized as below:
The system gives document ID for the documents of an individual who take
plot to identify them.
Description: The system must continuously add user based on the correct
input given.
Requirements: The system need inputs like full name, username, user type like
registrar officer, administrator, and landowner to add user. Fill the inputs correctly
and then click the add user button.
Ranking: Essential
[FR-02]: Register
Description: The system must register land owner information and parcel
information correctly.
Requirements: The system need inputs like full name, address, age, gender,
parcel code marriage status, region, registration date, sub city, city, kebele,
occopetion, tenure type, service, encumbrance, anualfee, area.
Ranking: essential
[FR-03]: Delete user
Description: The systems delete land owner information as well as personal
information.
Requirements: The system must allow the administrator to delete user in the
system .to delete first search the lad owner information by name and then click
delete button.
The system must allow the Registrar to delete parcel in the system.
Ranking: essential
[FR-04]: Search user
Description: The system must provide the functionality for searching for
previous
Transactions.
Requirements: The system must allow the user to search according to: Name
Ranking: Essential
Requirements: To update land owner information you must search the land owner
information by name and update what you want record then click update update.
Ranking: desirable
Description: The system must allow export certificate with full information.
Ranking: essential
[NFR-1] usability
Rank: essential.
[FR-2] reliability
Requirement: the system must be includes all the requirements of the client.
Rank: essential.
[NFR-3] performance
Description: describes the ability of the system for its function and
Waiting for an application to load can be frustrating for an end user. so make them
Requirements: The System must have a startup time of less than 5 seconds,
Ranking: Desirable
Description: The system must report results from searches within a specified period
Of time.
1. When the system searches according the request, the results from the search
Must be reported within 30 seconds.
2. When the system searches through the entire database, the results
Ranking: Essential
[NFR-5 supportability.
Requirement: The system must compile and run successfully on any Windows.
Rank: essential.
[NFR-6] Legal
Description: the system is legal in terms of federal democratic republic Ethiopian rule
in article 40(7) of the constitution.
Requirements: the system must fill full the rule and regulation of Ethiopia.
Rank: desirable
[NFR-7] implementation
Description: The system is implemented using PHP, HTML and uses MySQL for
database.
Rank: desirable.
[NFR-8] interface
Requirement: the system has an interface that enables for the data flows
Rank: essential.
[NFR-9] packaging
Rank: essential.
Adelady wants to register the land information in land registration institution. First
Adela day apply to registering institution for registration. Because the application for
registration shall be made by filling the forms prepared by the registering institution
for this purpose and upon payment the service fee. The register officer amanuel shall,
upon receiving a duly completed application form for landholding registration, assign
serial number in sequential order to each application to be placed in folder, and
also amanuel shall verify that the applicant's request. After that amnuel register
adeladys necessary information like, first name, Last Name, city, sub city, gender,
region, marriage status, address, document id, service type, parcel code, boundary,
area etc. Now Adeladays land information is correctly registered and take his
prepared certificate in the registration instution. But one day adeladay want to merge,
split, bequest or sell; to someone from his family member. So adeladay communicate
with amanuel in the registration institution after that register officer amnuel update
adeladys information to the required person and the new person can take certificate of
the land right.
Use cases describe the behavior of the system when one of these actors sends one
particular stimulus. This behavior is described textually. It describes the nature of the
stimulus that triggers the use case; the inputs from and outputs to other actors, and the
behaviors that convert the inputs to the outputs. The text of the use case also usually
describes everything that can go wrong during the course of the specified behavior,
and what remedial action the system will take. Use case diagrams are used for
documenting the system’s behavior from the user’s point of view. Those diagrams are
used to identify the processes/ functions and the main elements which form the
system. The processes/functions are called use cases and the main elements are called
actors. The diagram also shows the interactions that occur with each of the actors,
with each use case. The UML notation for a use has the following three elements.
Informally speaking, a use case is a story or a case of using a system by some users to
carry out a process. A bit more precisely speaking, a use case describes the sequence
of events of some types of users, called Actors, using some part of the system
functionality to complete a process.
Actors: An actor represents a coherent set of roles that are entities external to the
system can play in using the system, rather than representing a particular individual.
An actor represents a type of users of the system or external systems that the system
interacts with.
In this project we have three actors each has its own activities /use cases.
1. Register Officer
2. Customer(Land Owner)
3. Administrator
1. Register Officer; allows to performing the following action
Register customer; update Land holding right, view customer’s information when
needed.
Can view his parcel information, change his own password, see and export his
certificate.
3. Administrator
A person who control or manage all the functionality of the system like; add user,
delete user, give privilege for users etc.
Search
LogHistory
<<initiate>>
<<initiate>>
GenerateCertificate <<initiate>>
«include»
+<initiate>
«include»
<<initiate>> «include»
RegistrationOfficer
Login
<<initiate>> Administrator
initiate <<initiate>>
Register
<<initiate>> «include»
«include»
«include» DeleteUser
«extend»
«include»
ViewParcel «include»
Logout
<<initiate>>
Delee Parcel
<<participate>>
Customer
Actors Administrator
Preconditions
actor enters to the system
Preconditions
actor enters to the system
1. Register Officer
2. Customer(Land Owner)
3. Administrator
4. Parcel
5. Account
6. Audit log
Register Officer; allows to performing the following action
Register customer; update Land holding right, view customer’s information when
needed. Customer (Land Owner) can view his parcel information, change his own
password, see and export his certificate.
Administrator: A person who control or manage all the functionality of the system
like; add user, delete user, give privilege for users etc.
Parcel: means an area of land its boundary extent is clearly defined and demarcated
on the ground and drawn upon a map with rights having a unique parcel identification
code;
Customer(Landowner)
+ address: string
+ age: int
Parcel + date: int
+ Documentid: string
+ Address: string + fullName: string
+ agreement era: string + Gender: string
+ anual fee: string + Id(primary key): string
+ Area: string + Kebele: string
+ Boundary: string + mariagestatus: string Administrator
- Encumbrance: char Own
+ Region: string
+ Id(foriegn key): string - Adress: string
1..* 1 + Subcity: string
+ Land tenure: string - age: int
+ Location: string - Fname: string
+ Exportcertificate() : void
+ parcelcode: string - Gender: string
+ Search() : void
+ Purpose: string - L name: string
+ View() : void
Account
has
AuditLog
Initiate()
<<create>>()
UserName()
Password()
Validate(Username,Password)
Invalid()
valid()
X X X X X
sd Class Mo...
Click
CustomerRegistration link()
BasicCourseOfaction
Click()
initiate()
Create()
DisplayForm()
Fill
Form()
Invalid()
Valid()
Register()
Succesfully registerd()
Actor:
customer
X X X X X
X
sd Class Mo...
loged in to()
press()
create()
displayform()
fill form()
add user()
invalid input()
valid input()
submit()
sucessfuly added()
Chapter Three
3. System Design Document
3.1 Purpose of the SDD
This section focuses on the Design goal, descriptions of current software architecture,
proposed system architecture, subsystem decomposition, software and hardware
mapping, the user model of the system in terms of access control, the boundary
conditions: startup, shutdown, and error behavior of the system, and also a brief
description of the implementation plan for the subsystem. The purpose of design is to
model the structural aspects of the system architecture. So that one could see it as the
application of the systems theory to product development. For this project we used an
Object-Oriented analysis and design methods for our project which is widely used for
modeling software systems. ;
OOD: object oriented design used to design the project by representing real world
things.
3.4. Overview:
SDD focuses on the Design goal, descriptions of current software architecture,
proposed system architecture, subsystem decomposition, software and hardware
mapping, the user model of the system in terms of access control, the boundary
conditions: startup, shutdown, and error behavior of the system, and also a brief
description of the implementation plan for the subsystem. In this design phase, we
focus on the processes, data structures, and software and hardware components to
implement the system using structural or Object Oriented approaches.
• Database security
Even if accessed by many users from different locations the system can be fully
managed and maintained by operating on the central server; no intervention is
required to install or maintain workstations.
Users can access the system from any workstation running a generic Web Browser
that support both local and remote connections through the internet.
End users can access the system data only through the application layer which
implements appropriate business rules to allow only authorized operations based
on the actual user permissions; no direct access to the physical database is needed.
The centralization of the data allows efficient monitoring and backup procedures; no
data is stored on clients.
LAN
LRS Internet
Account Management
LRS
internet brow ser
Web Serv er
appache
DB serv er MySql
Id Int 11 - X
Kebele Varchar 30 - X
Gender Varchar 30 - X
Date Int 11 - X
Date Int 20 - X
Time Int 20 - X
Area Varchar 30 - X
Work Varchar 40 - X
Password Varchar 15 - X
Confidentiality:
The only people to see the data those authorized to see it. Private data is kept
private; personal privacy is respected.
Integrity:
There are limits on who can change the land registration System.
Availability:
The registered parcel and customer information data is available at all times to
authorized users.
Accountability:
It is possible to discover that after the event who has modified what data in the land
registration System
R U D V R U D V R U D V
Inform
ation
Audit no no no n no no n y no no no n
log o o e o
s
The land registration System does not have any startup or shutdown
procedures. Since it is a website, startup and shutdown are controlled by the
web server and host, both of which are outside of land registration System’s
scope. The website is designed to be online 24 hours a day; 7 days a week;
365 days a year except during system maintenance. If the web server and host
are running, then land registration System is operational.
Initialization
The land registration System does not require any initialization upon system
startup. When creating the website for the first time some interesting persistent
data needed to be added to the database. However these operations can be
performed at any time. If the web server is rebooted for example, it is not
necessary to re-add the previously performed operations, since this
information already exists inside the database.
Configuration: -The land registration System contains the following
configuration options:
Add/Delete user account
registration management
v iew management
account management
database
Account Management
Account management is LRS sub system that are used to perform the following
operations
- Add user account
- Delete user account
- Edit profile
- Manage User Authentication and access control
Some input output mockups are discussed below.
Chapter four
4. Testing and debugging
4.1. Introduction
The implementation document enables the user (society) as well as the administrator
to work with the system and to use the application efficiently and effectively. It helps
users not to be confused with the system. It includes sample snapshot. It gives the
users a brief over view of the system.
4.2. Objective
The implementation is to change what we did in the design Phased to machine
readable form by writing code using php to all modules. The system contains many
forms that are connected to the data base in each individual form also combined in
one module in order to work the system as whole.
4.4. Testing
Final phase of implementation is testing. Testing is a process to show the correctness
of the program. Testing is checking of System Implementation
Implementation is the phase where objectives of physical operations of the system
turned into reality i.e. real working model. The crucial phase in the system
development life cycle is the successful implementation of the new system design.
The process of converting as new system into an operational one is known as system
implementation. This includes all those activities that take place to convert from an
old system to a new system.
4.5. Coding
The system workability in an attempt to discover errors and avoiding such errors from
the system. In this the team members tested the entire system as a whole with all
forms, code in this we tested all the functionalities in the System. All errors in the
forms, functions have been tested. The following are different testing strategies.
4.4.2. Unit Testing
Unit testing is every module of the System is separately tested. It is often done by the
programmer to test that the unit he/she has implemented is producing expected output
against given input.
Test Case 1:
Test Case ID = Administrator – TestCase02
Unit to Test = add user
Assumptions = successfully registered!
Test Data = first Name (invalid, Valid, empty)
Last name(invalid, valid, empty)
User type(Selected, empty)
Password (invalid, valid, empty)
conform password (not match, matched, empty)
Test Case 2:
Test Case ID = register officer – TestCase01
Unit to Test = Registration
Assumptions = successfully registered!
Test Data = first Name (invalid, Valid, empty)
Last name(invalid, valid, empty)
City(valid, empty)
Sub city(valid, empty)
kebele(invalid, valid, empty)
Marriage status (selected, empty)
Gender(selected, empty)
Parcel code (invalid, valid, empty)
Land level(invalid , valid, empty)
Area (invalid, empty)
Service type (Selected, empty)
Boundary (invalid, empty)
Land Tenure(invalid, empty)
Annual fee(invalid, empty)
Agreement era(invalid, empty)
Encumbrance(invalid, empty)
In acceptance testing the customers provides the input data to validate the system
operation. It is also known as functional testing, black-box testing, release
acceptance, QA testing, application testing, confidence testing, final testing,
validation testing, or factory acceptance testing
Chapter Five
5. Conclusion and Recommendation
5.1. Conclusion
Generally in this project, we developed an automated LRS that facilitates various
activities taking place at the Mekelle Land Administration. The LRS do different
activities such as Parcel registration User registration, update parcel information,
delete parcel information and also anyone who has internet access can view parcel
information using the search service in the system. We realize that the existing system
is not capable of reducing errors and too backward to work in a flexible manner.
However, the newly developed system has dynamic features of manipulating and
managing data. Furthermore this document briefly describes the problems and the
solutions we proposed with the figures to visualize better and steps taken to solve the
problem. In other words this document introduces the technical details of the LRS. In
the first part of the technical design the major functions needed to develop LRS are
introduced. Later on, these major functions and their sub-functions are visualized with
the use case diagrams. In the second part, user interfaces are described in a detailed
manner with figures. Lastly, data modules and their relationships are discussed. We
believe from heartily that the existing problems of the LRS will be resolved and a
sustainable working environment will be created just by taking advantage of the
newly developed system. To conclude, this document constitutes a base for the
development of LRS. In addition, with implementing the new system will make the
overall system more convenient and give fast and reliable service for users which has
continuous relation with Land Administration office. Overall the implementation of
this project was an excellent learning opportunity for us.
5.2. Recommendation
This paper will recommend specific steps to transform the elements of the LRS in to
technologies. These steps, if taken, will result in better support to users while
expediting access to different information requirements and decreasing the workload
of the employees. These improvements will depend on the creation of an integrated
software development with one lead agent in charge of developing, maintaining, and
growing the architecture. The Land registration system is immense and expanding.
There should be one centralized element responsible for design control and
monitoring. It is imperative that automation is properly reviewed and focused around
the Core Task of Registration and user management. There needs to be a plan for the
entire system. This plan must be an active document that grows with changes while
anticipating future requirements. The following paragraphs will provide specific
recommendations Automation of Common Tasks: LRS tasks were manual
procedures. Instead of multiple manual submissions of identical information,
automation solutions could significantly simplify these tasks with the use of
standardized applications within existing software solutions. Rapid Response: Land
Registration System Automation must be responsive to the needs and requirements of
the Land owner and Land administration employees. The design must be responsive
enough to implement changes prior to requirements for users the final
recommendation is to establish effective, efficient and reliable information
Registration system for Land Administration as well as for all Land owners of
Ethiopia.
6. Glossary
Main terms
Use case: A use case expresses a contract between the stakeholders of a system about
its behavior. It describes the system’s behavior and interactions under various
conditions as it responds to a request on behalf of the stakeholders, the primary actor,
showing how the primary Actor’s goal gets delivered or fails. The use case collects
together the scenarios related to the primary actor’s goal.
Use case diagram: In UML, the diagram showing the external actors, the system
boundary, the use cases as ellipses, and arrows connecting actors to ellipses or ellipses
to ellipses. Primarily useful as a context diagram and table of contents.
Sequence diagram: In UML, the diagram showing actors across the top, owning
columns of space, and interactions as arrows between columns, with time flowing
down the page. Useful for showing one scenario graphically.
Class diagram: Class diagrams show the classes of a system and their
interrelationship’s. Class diagrams are often mistakenly referred to as object models.
Customer (Land Owner): a person who have the right to hold land or the owner of
the land.
Administrator: A person who control or manage all the functionality of the system.
Parcel: means an area of land its boundary extent is clearly defined and demarcated
on the ground and drawn upon a map with rights having a unique parcel identification
code;
OOD: object oriented design used to design the project by representing real world
things.
7. Reference
(Proclamation) Federal negarit gazette (the whole document is depend on this
article because we concern Land registration in the case of Ethiopia)
Usable land registration system Pdf files(These was some useful guide for us to
understand the analysis phase )
www.mekellelandadministration.gov.et