TABLE OF CONTENT^

CHAPTER ONE ........................................................................................................... 1

INTRODUCTION................................................................................................... 1
1.1 Background of the organization ........................................................................ 1
1.2 Introduction of the Land management System ................................................. 1
1.3 Statements of the land management system problem ....................................... 2
1.4 Objectives of land management system ............................................................ 3
1.4.1 General objectives .......................................................................................... 3
1.4.2 specific objective ............................................................................................ 3
1.5 Methodology ..................................................................................................... 4
1.5.1 Methodology of the project ........................................................................... 5
1.5.2 Methodology for data collection .................................................................... 5
1.5.3 System Development Methodology .............................................................. 6
1.5.4 System Development Life Cycle (SDLC)...................................................... 7
1.5.5 System development tools.............................................................................. 8
1.6 Scope Of The Study .......................................................................................... 9
1.7 Significance of Land Management System....................................................... 9
1.8 Feasibility Assessment .................................................................................... 10
1.8.1 Economic Feasibility.................................................................................... 11
1.8. 2Technical Feasibility .................................................................................... 11
1.8.3 Operational Feasibility ................................................................................. 11
1.8.4 Legal and Political Feasibility...................................................................... 11
1.9 Data Flow Diagram ......................................................................................... 11
1.9.1 Level 0 DFD ................................................................................................. 12
1.9.2 Level 1 DFD ................................................................................................. 13
1.9.3 Level 2 DFD ................................................................................................. 13
1.9.4 User DFD ..................................................................................................... 14
CHAPTER TWO ......................................................................................................... 16
MODELING AND DESIGN ................................................................................ 16
2.1 Description Of The Current System................................................................ 16
2.1.1 Existing System............................................................................................ 16
2.1.2 The Proposed System ................................................................................... 17
2.2 E-R Diagram ......................................................................................... 17
2.2.1 Relational Tables ......................................................................................... 18
2.2.2 Relation ........................................................................................................ 20
Parcel_Owner Table .............................................................................................. 24
2.3 Class Responsibility Responsibility (CRC) .................................................... 24
2.4 Use Case Modeling ......................................................................................... 26
2.4.1 Essential Use Case Modeling ....................................................................... 26
2.5 System Use Case Modeling............................................................................. 28
2.5.1 System Use Case Description ...................................................................... 30
2.6 Functional and Non-Functional Requirements .............................................. 35
2.6.1 Functional Requirements.............................................................................. 35

I
 2.6.2 Non-Functional Requirements ..................................................................... 35
2.7 User Interface Prototype.................................................................................. 36
2.7.1 Traditional User Interface Prototype ............................................................ 36
2.7.3 User Interface Flow Diagram ....................................................................... 37
CHAPTER THREE ..................................................................................................... 39
Design document ................................................................................................... 39
3.1 Class Modeling................................................................................................ 39
3.1.1 Class Modeling Diagram.............................................................................. 39
3.2 Sequence Diagram........................................................................................... 40
3.2.1 Sequence Diagram For Login Page.............................................................. 41
3.2.2 Sequence Diagram For Land Admin............................................................ 42
3.3 Activity diagram.............................................................................................. 43
3.4 User Interface Design ...................................................................................... 45
3.5 Object Diagram ............................................................................................... 47
3.6 persistence Modeling....................................................................................... 49
3.7 Deployment Diagram ...................................................................................... 51
CONCLUSION ............................................................................................................ 52
Reference............................................................................................................... 54

II
 List Of Figures

Figure 1.1 DFD level 0 diagram ....................................................................................... 12

Figure 1.3 level 2 DFD ............................................................................................... 14
Figure 1.4 User DFD.................................................................................................... 15
Figure 2.3 Essential model........................................................................................... 28
Figure 2.4 system use case modeling........................................................................... 30
Figure 3.2 sequence diagram for Login page............................................................... 42
Figure 3.4 Activity diagram for login page ................................................................ 44
Figure 3.5 activity diagram for System Admin ........................................................... 45
Figure 3.6 UI Design.................................................................................................... 46
Figure 3.7 Object Diagram........................................................................................... 48
Figure 3.9 deployment Diagram .................................................................................. 51

III
 List Of Tables

Table 2.1 Relational Tables ......................................................................................... 19

Table 2.2 Initial relation............................................................................................... 20
Table 2.3 1NF Relation ................................................................................................ 21
Table 2.4 2NF Relation ................................................................................................ 22
Table 2.5 3NF Relation ................................................................................................ 23

IV
 CHAPTER ONE

INTRODUCTION

1.1 Background of the organization

Background of Haromaya Woreda Land Management System (LMS) Organization

History:
 Haromaya Woreda LMS Organization was established in 1700 EC[this is an
example, But not exact year] with the goal of modernizing and improving land
management practices in the region. It was founded by a group of land manageme nt
experts and technology enthusiasts who saw the need for a more efficient and
transparent system for managing land-related information and activities.
Mission:
 Our mission is to provide a comprehensive and user-friendly Land Manageme nt
System that meets the needs of land administrators, government agencies, and
landowners. We aim to streamline land management processes, improve data
accuracy, and promote sustainable land use practices.
Goals:
 Develop and maintain a state-of-the-art Land Management System that meets
industry standards and best practices.
 Provide training and support to land administrators and users to ensure effective
use of the LMS.
 Collaborate with government agencies and stakeholders to improve land
management policies and practices.
 Enhance public access to land-related information and promote transparency in
land transactions.

1.2 Introduction of the Land management System

 A Land Management System (LMS) is a software application designed to facilita te

the management and administration of land-related information. It serves as a
central repository for data related to land parcels, ownership, transactions, and land

1
 use. LMS is used by government agencies, real estate developers, and other
organizations involved in land management to streamline processes, ensure
compliance with regulations, and improve decision-making.
 A Land Management System is a valuable tool for organizations involved in land
management, providing them with the necessary tools to manage land informa tio n
efficiently, ensure compliance, and make informed decisions.

1.3 Statements of the land management system problem

As we observed current Haramaya Woreda Management System of the land is like most
of other our country environment Management process is traditional and not
comfortable to users and other employers we say that in tradition management system
there are a lot of problems.
Some of these are:-
 Data Fragmentation: Land-related information is often scattered across multip le
sources and formats, leading to inefficiencies and inaccuracies in managing land
data.

 Manual Processes: Many land management processes, such as data entry, record-
keeping, and transaction management, are still done manually, leading to errors
and delays.

 Lack of Transparency: The lack of a centralized system for managing land data
can result in a lack of transparency and accountability in land transactions and
ownership.

 Compliance Challenges: Ensuring compliance with land-related regulations and

policies is difficult due to the complexity and volume of regulations.

 Limited Access to Information: Stakeholders often have limited access to

accurate and up-to-date land information, hindering informed decision- making.

2
 Risk of Fraud and Corruption: Manual processes and lack of transparency
increase the risk of fraud and corruption in land transactions.

 Environmental Impact: Inadequate management of land data and processes can

have negative environmental impacts, such as unsustainable land use practices.

 Addressing these problems requires the development and implementation of a

robust Land Management System that can streamline processes, improve data
accuracy and accessibility, ensure compliance, and support sustainable land use
practices.

1.4 Objectives of land management system

1.4.1 General objectives

 The general objectives of this project is to develop computerized land manageme nt

system of Haramaya woreda and maximum the data security of the organiza tio n
and the user.

1.4.2 specific objective

 A land management system typically aims to achieve several specific objectives

related to the efficient and sustainable use of land resources.
Some of these are:-
 Resource Planning: Efficiently plan the use of land resources for various purposes
such as agriculture, forestry, urban development, conservation, etc.
 Land Use Allocation: Allocate land for different uses based on factors such as
zoning regulations, environmental considerations, and socioeconomic needs.

 Environmental Conservation: Promote the conservation and sustainable use of

natural resources, including biodiversity, soil, water, and air quality.

3
 Disaster Risk Reduction: Mitigate risks associated with natural disasters such as
floods, wildfires, and landslides through effective land use planning and
management.

 Infrastructure Development: Facilitate the development of infrastruc ture

projects such as roads, utilities, and public facilities while minimizing negative
impacts on the environment and communities.

 Revenue Generation: Generate revenue for governments or landowners through

mechanisms such as land leasing, permitting, or resource extraction.

 Community Development: Support the social and economic development of

communities by providing access to land for housing, agriculture, and livelihoods.

 Legal Compliance: Ensure compliance with land-related laws, regulations, and

policies to maintain order and fairness in land use and ownership.

 Data Management: Manage land-related data, including land parcels, ownership

information, land use plans, and environmental assessments, to support decision-
making and monitoring.

 Conflict Resolution: Resolve conflicts related to land ownership, land use rights,
and resource access through legal and administrative processes.

 By addressing these objectives, a land management system can contribute to

sustainable development, environmental protection, and social well-being in a
region or country.

1.5 Methodology

Methodology refers to the systematic, theoretical analysis of the methods applied within
a particular field of study or activity.

4
1.5.1 Methodology of the project

 In the context of our project(LMS), the methodology would be the approach or

framework used to plan, implement, and monitor the management of land resources.
It would include the steps, processes, and tools used to achieve the objectives of
the land management system, such as resource planning, environme nta l
conservation, and community development.

 When we are working our project we use different methods and techniques .
Before we used our techniques we have done reviewing the possible
requirements.Review was on the available literature about the existing
management system of the land. Which will give the strategy design
Questionnaires were used to verify the current system, observation was used to
elect specific requirements and sampling was used to select the respondents who
provide the data. This methods helps us to achieve the specific objectives of our
project.

1.5.2 Methodology for data collection

 The method used to collect data for a land management system (LMS) depends on
the type of data being collected and the resources available.then the following
methods to collect our projects data:-

 Interviews and Focus Group Discussions: Interviews and focus group

discussions can be used to gather qualitative data from stakeholders about their
perceptions, preferences, and experiences related to land management. These
methods can provide valuable insights into community needs and concerns.

 Document Review: Reviewing documents such as land records, land use plans,
environmental impact assessments, and policy documents can provide valuable
information for land management planning and decision-making.

5
 By using a combination of these methods, we are collect important data types to
develop our system effectively.

1.5.3 System Development Methodology

 In the system analysis and design phase of a project we should use the
Waterfall Model.
 Waterfall Model is a traditional, linear software development methodology. It
follows a sequential order, where progress is seen as flowing steadily downwards
(like a waterfall) through the phases of conception, initiation, analysis, design,
construction, testing, deployment, and maintenance.

Some of key characteristics:

 Sequential Approach: The Waterfall Model follows a sequential approach, with

each phase being completed before the next one begins. This means that progress
flows downwards, and once a phase is completed, it is considered locked-in.

 Phased Development: It is divided into distinct phases, including requireme nts

analysis, design, implementation, testing, and maintenance. Each phase has
specific deliverable and goals.

 Documentation: The model emphasizes extensive documentation at each phase.

Requirements, design, and test documents are prepared to ensure that all
stakeholders have a clear understanding of the project.

 Validation: Each phase's deliverable are validated before moving to the next phase.
This ensures that any errors or issues are caught early in the process.

 Rigidity: The Waterfall Model is often criticized for its rigidity. Once a phase is
completed, it is difficult to go back and make changes without starting over from
the beginning.

6
 Suitability: It is best suited for projects where the requirements are well-
understood and unlikely to change significantly during the development process.

Advantages And Disadvantages Of The Model

Advantages:-
 Clear project milestones and deliverables.
 Well-defined requirements at the beginning of the project.
 Easy to manage and understand for small projects with stable requirements.
Disadvantages:-
 Limited flexibility to accommodate changes.
 High risk of customer dissatisfaction if requirements are misunderstood.
 Testing is often rushed at the end of the project.

1.5.4 System Development Life Cycle (SDLC)

The System Development Life Cycle (SDLC) is a framework that describes the stages
involved in the development of software or information systems. It provides a
structured approach to planning, creating, testing, and deploying our system.

 Planning: This phase involves defining the project scope, goals, and requireme nts.
It also includes feasibility studies and resource planning.

 Analysis: During this phase, the system's requirements are analyzed in detail. This
includes gathering information from stakeholders and understanding the system's
needs.

 Design: In this phase, the system architecture is designed based on the

requirements gathered in the analysis phase. This includes creating technica l
specifications and designing the user interface.

7
 Development: This is the phase where the actual coding and programming of the
system take place. Developers build the system based on the design specificatio ns.

 Testing: Once the system is developed, it undergoes testing to ensure that it meets
the requirements and functions correctly. This includes both functional and non-
functional testing.

 Deployment: After testing, the system is deployed to the production environme nt.
This includes installing the system, configuring it, and making it available to users.

 Maintenance: Once the system is in production, it requires ongoing maintena nce

and support. This includes fixing bugs, adding new features, and making updates
to keep the system running smoothly
 Our project is rotate through.the above System Development Life cycles.
 We use SDLC because of it helps for us to many ways.
for example:-
 To ensure that projects are completed on time.
 To reduce the cost.
 To identifying and managing risk throughout the development process.
 To ensure that software and information systems are developed in a systematic and
controlled manner,
 leading to higher quality products that meet the needs of stakeholders.

1.5.5 System development tools

 Microsoft Word: These tools can be used to create documents for gathering and
analyzing requirements. They allow for easy collaboration and document sharing.
 Draw.io:These tool is a free online offline diagramming application for creating
various types of diagrams, such as flowcharts, User Interface Diagrams(USD), Use
Case Diagram(UCD), Sequence Diagram(SD), Activity Diagram(AD), Class
Diagram(CD), Deployment Diagram(DD), Persistence Modeling

8
1.6 Scope Of The Study

 Scope of the study refers to the boundaries and limitations within the system will
be connected.it means that what will be covered and what will be not covered in
the study.
 Land Parcel Management: Tracking and managing information about land
parcels, including ownership, boundaries, and land use.

 Land Use Planning: Supporting the planning and allocation of land for various
purposes, such as agriculture, residential, commercial, or conservation.

 Environmental Monitoring: Monitoring and managing environmental factors

related to land use, such as soil quality, water resources, and biodiversity.

 Regulatory Compliance: Ensuring that land management activities comply with

relevant laws, regulations, and policies.

 Reporting and Analysis: Providing tools for generating reports and analyzing data
related to land management for decision-making purposes.

 GIS Integration: Integrating with Geographic Information Systems (GIS) to

visualize and analyze spatial data related to land management.

 Stakeholder Collaboration: Facilitating collaboration and communication among

stakeholders involved in land management, such as government agencies,
landowners, developers, and environmental groups.
 The above scope of the system is essential for ensuring that it meets the
requirements and expectations of its users and stakeholders.

1.7 Significance of Land Management System

 Significance refers to the importance, relevance, or meaningfulness of something.

In the context of a Land Management System (LMS), significance can be
understood in terms of the impact and benefits that the system provides.

9
 Efficient Land Use: An LMS helps optimize land use by providing tools for
planning, monitoring, and managing land resources effectively. This can lead to
more sustainable development practices and prevent over-exploitation of land.

 Environmental Conservation: By monitoring environmental factors and

enforcing regulations related to land use, an LMS can contribute to the
conservation of natural resources and biodiversity.

 Improved Decision Making: An LMS provides data and analytical tools that can
help stakeholders make informed decisions about land use, planning, and
development.

 Regulatory Compliance: An LMS helps ensure that land management activities

comply with relevant laws, regulations, and policies, reducing the risk of legal
issues and conflicts.

 Stakeholder Engagement: An LMS can facilitate communication and

collaboration among stakeholders involved in land management, leading to more
inclusive and transparent decision-making processes.

 Data Management: An LMS helps organize and manage data related to land
parcels, ownership, and use, making it easier to access and use this information for
various purposes.

 Economic Development: Effective land management can contribute to economic

development by supporting activities such as agriculture, infrastruc ture
development, and urban planning.

1.8 Feasibility Assessment

A feasibility assessment is an evaluation of the practicality and potential success of a

proposed project or system. In the context of our project(LMS), a feasibility assessment
would typically include includes a lot .Then we mention some of them:-

10
 Economic Feasibility
 Technical Feasibility
 Operational Feasibility
 Legal and Political Feasibility

1.8.1 Economic Feasibility

 Evaluate the costs associated with implementing and maintaining the LMS,
including initial setup costs, licensing fees, training, and ongoing maintena nce.
Compare these costs to the expected benefits and returns on investment.

1.8. 2Technical Feasibility

 Assess the technical requirements and capabilities of the proposed LMS, includ ing
hardware, software, and infrastructure. Consider if the technology is compatible
with existing systems and if it can handle the expected workload.

1.8.3 Operational Feasibility

 Determine if the organization has the resources, skills, and capabilities to operate
the LMS effectively. Consider factors such as staff training needs, organizatio na l
readiness, and potential disruptions to current operations.

1.8.4 Legal and Political Feasibility

 Identify any legal or regulatory requirements that must be met when implementing
the LMS, such as data protection laws, land use regulations, or environme nta l
regulations. Ensure that the LMS complies with these requirements.

1.9 Data Flow Diagram

 A Data Flow Diagram (DFD) is a graphical representation of the flow of data

within a system. It visually shows how data moves through processes and stores in

11
 a system. DFDs are commonly used in system analysis and design to model the
processes involved in a system and the interactions between these processes.

In a DFD, there are four main components:

 External Entities: These are sources or destinations of data outside the system.
External entities interact with the system by sending or receiving data.
 Processes: Processes represent actions or transformations that occur within the
system. They take input data, perform some processing, and produce output data.
 Data Stores: Data stores represent where data is stored within the system. They
can be databases, files, or any other storage medium.
 Data Flows: Data flows represent the movement of data between external entities,
processes, and data stores. They are represented by arrows and show the direction
of data flow.

1.9.1 Level 0 DFD

 A Level 0 Data Flow Diagram (DFD) is the highest- level view of a system that
shows the major processes and data flows in the system.

Figure 1.1 DFD level 0 diagram

12
1.9.2 Level 1 DFD

 Level 1 DFD: expands on the processes, data flows, and data stores identified in
the Level 0 DFD and decomposes them into more detailed sub processes.

Figure 1.2 level 1 DFD

1.9.3 Level 2 DFD

 Level 2 DFD breaks down the processes into even more detailed sub processes,
providing a more granular view of the system's functionality.

13
Figure 1.3 level 2 DFD

1.9.4 User DFD

 how a user interacts with the Land Management System (LMS) to request and view
land information without directly connecting to the database.

14
Figure 1.4 User DFD

 User interacts with the system by requesting land information.

 The request is processed by the system's data access layer (e.g., application
server, API).
 The data access layer queries the database for the requested information.
 The retrieved data is formatted by the data access layer.
 The formatted data is returned to the user interface for display to the user.

15
 CHAPTER TWO

MODELING AND DESIGN

2.1 Description Of The Current System

2.1.1 Existing System

 Purpose: The LMS is designed to manage land-related data, processes, and

transactions, often used by government agencies, real estate companies, or land
developers.
 Features: It includes features such as parcel management, land use planning,
zoning information, permitting, and property tax assessment.
 Technology Stack: The LMS is built using Geographic Information System(GIS),
database management system](DBMS).
 User Interface: It provides a user-friendly interface for users to view maps, search
for land parcels, and access property-related information like Land gift, Land
Register etc related to Land.
 Integration: The LMS may be integrated with other systems, such as GIS software,
property valuation tools, and document management systems.
 Data Management: It includes tools for storing, updating, and querying land -
related data, such as property boundaries, ownership records, and land use
regulations.
 Reporting: The LMS provides reporting capabilities to generate reports on land
parcels, ownership details, land use patterns, and other relevant information.
 Accessibility: It complies with accessibility standards to ensure all users, includ ing
those with disabilities, can access and use the system effectively.
 Support and Maintenance: The LMS is supported by a team that provides regular
maintenance, updates, and technical support to ensure its smooth operation.
 User Base: It is currently used by [number of users, e.g., government agencies,
real estate developers] for managing land-related information and processes.
 Limitations/Challenges:
[List any limitations or challenges of the current LMS, such as data integration issues,
limited Scala Description of the Current Land Management System (LMS):

16
2.1.2 The Proposed System

 Proposed System is computer based or digital system for recording Land

Information and it applies to woreda’s people specifically looks in to the subject of
Land Management.
Expected Advantages of The Proposed System
 The system is very simple to use, edit, manage and so. It has the following
features:-
 Ensuring data accuracy
 Minimize manual data entry
 High efficiency
 Better Service
 User friendly & Interactive
 Use minimum time to achieve the goal

 2.2 E-R Diagram

 An Entity-Relationship (E-R) diagram is a visual representation of the entities

(things) in a system or business, their attributes (properties), and the relations hips
between them. It's commonly used in database design to model the structure of a
database.
 E-R diagrams are useful for understanding the data requirements of a system and
are often created early in the database design process to help clarify the structure
of the database before it is implemented.

17
Figure 2.1 Conceptual E-R Model

2.2.1 Relational Tables

 Relational tables are structures used to organize and store data in a relationa l
database management system (RDBMS). These tables are composed of rows and
columns, where each row represents a record or tuple, and each column represents
an attribute or field.
 In relational databases, data is stored in multiple related tables, each designed to
hold information about a specific type of entity (such as Owner, L_Admin,
S_Admin, Parcel, Record_Office ). The tables are related to each other through the
use of keys, which are columns that uniquely identify each row within a table and
establish relationships between tables.

18
Table 2.1 Relational Tables

19
2.2.2 Relation

Initial Relation (Table):

Owner

Table 2.2 Initial relation

Owner_ID Name Address Phone Email Parcel_ID Parcel_No Parcel location

Area(sq)
1 Chala Bate,Maya 0987654328 [email protected] 101 01 1324 East of
Haramaya
2 Aster Gendeje 0978654325 [email protected] 102 02 4321 West of
Haramaya
3 Kebede Gendemude 0912345678 [email protected] 103 03 5234 East of
Haramaya
4 Chaltu GendeBue 0989980987 [email protected] 104 04 7654 East of
Haramaya

Step 1: Identify Functional Dependencies (FDs)

 Land_Owner_ID → Name, Address, Phone_Number, Email, Land_Parcel_ID
 Land_Parcel_ID → Parcel_Number, Size, Location
Step 2: Determine Candidate Key
 Land_Owner_ID is the candidate key for Land_Owner
Step 3: Normalize to First Normal Form (1NF)
 Ensure all columns contain atomic values (no repeating groups or arrays)

20
 Done already in the initial relation

Table 2.3 1NF Relation

Owner_I Name Address Phone Email Parcel_I Parcel_N Parcel location

D D o Area(s
q)
1 Chala Bate 09876543 [email protected] 101 01 1324 East of
28 om Haromaya

1 Chala Maya 09876543 [email protected] 101 01 1324 East of

28 om Haromaya

2 Aster Gendeje 09786543 [email protected] 102 02 4321 West of

25 om Haromaya

3 Kebed Gendemu 09123456 [email protected] 103 03 5234 East of

e de 78 m Haromaya
4 Chalu GendeBue 09899809 [email protected] 104 04 7654 East of
87 Haromaya

21
Step 4: Normalize to Second Normal Form (2NF)
 No partial dependencies (attributes depend on the entire primary key)
 Split the relation into three relations:
 Land_Owner(Land_Owner_ID, Name, Address, Phone_Number, Email)
 Land_Parcel(Land_Parcel_ID, Parcel_Number, Size, Location)
Owner
Table 2.4 2NF Relation

Owner_ID Name Phone Email

1 Chala 0987654328 [email protected]

2 Aster 0978654325 [email protected]

3 Kebede 0912345678 [email protected]

4 Chaltu 0989980987 [email protected]

Address
Address_ID Owner_ID Address

1 1 Bate
2 1 Maya
3 2 Gendeje
4 3 Gendemude
5 4 Gendebu

Land_Parcel
Parcel_ID Parcel_No Parcel location
Area(sq)
101 01 1324 East of
Haramaya
102 02 4321 West of
Haramaya
103 03 5234 East of
Haromaya
104 04 7654 East of
Haramaya

22
Step 5: Normalize to Third Normal Form (3NF)

 No transitive dependencies (attributes depend only on the candidate keys, not on

other non-prime attributes)
 All relations are already in 3NF after the split in step 4.
Land_Owne r

Table 2.5 3NF Relation

Owner_ID Name Address Phone Email

1 Chala Bate 0987654328 [email protected]

2 Aster Gendeje 0978654325 [email protected]

3 Kebede Gendemude 0912345678 [email protected]

4 Chaltu GendeBue 0989980987 [email protected]

Address
Address_ID Owner_ID Address

1 1 Bate
2 1 Maya
3 2 Gendeje
4 3 Gendemude
5 4 Gendebu

23
Land_Parcel
Parcel_ID Parcel_No Parcel location
Area(sq)
101 01 1324 East of
Haramaya
102 02 4321 West of
Haramaya
103 03 5234 East of
Haramaya
104 04 7654 East of
Haramaya

Parcel_Owner Table

Owner_ID Parcel_ID
1 101
1 101
2 102
3 103
4 104

2.3 Class Responsibility Responsibility (CRC)

 CRC cards are a brainstorming tool used in the design of object-oriented software.
 CRC card is a physical card representing a single class.
Each card lists:
 Class Names:-name of the class.
 Attributes and methods(responsibilities):-are something that a class knows or
dose.
 Class associations(Collaborations) :-Another class that a class interact with to
fulfill its responsibilities.

24
Figure 2.2 - CRC modal

25
2.4 Use Case Modeling

 Use case modeling is a technique used in software engineering to visually represent

the functional requirements of a system and the interactions between users (actors)
and the system. It helps in understanding how users will interact with the system
to achieve specific goals or tasks.
 It is divided in to two. These are :-
 Essential Use Case Modeling
 System Use Case Modeling

2.4.1 Essential Use Case Modeling

 Essential use case modeling focuses on capturing the essential

requirements of a system, specifically the core functionalities and

interactions between users (actors) and the system. It aims to provide a

high-level view of the system's behavior without getting into detailed

design or implementation specifics. Essential use case modeling is often

used in the early stages of software development to establish the system's

scope and requirements.

 The actors are:-
 User
 Land Administration
 System Administration
 Engineers
 Record Office

 The Use Cases Are:-

 Land registration, Gift land, Rent land , Site the land, check land use planning,
check rent agreement, check gift agreement, check site plan, manage
regulatory reporting,
Manage budget & finance, add user, Delete user, Update user, Remove user,
Deactivate user, Reactive user, record plan site, record land use, record level of

26
land, record area of land, record restriction of land, record property details, record
land characteristics, record land utility & infrastructure, record land use & zoning,
record access &transportation, record environmental consideration,

27
Figure 2.3 Essential model

2.5 System Use Case Modeling

 Use case modeling for a Land Management System (LMS) involves identifying
the various actors (users and external systems) and their interactions with the
system.
Actors and use case of System use case diagram:

28
1. land administrator:-check land use planing, check rent agreement, check gift
agreement, check site plan, manage regulatory reporting, manage budget & finance
2. .System administrator:- add user, delete user, update user, remove user, deactivate
user, reactivate user
3. Engineer:- record plan site, record land use, record level of land, record area of land,
record restriction of land,
4. Record office:- record property details, record land characteristics, record land
utility & infrastructure, record land use & zoning, record access & transportatio n,
record environmental consideration
5. User:- register the land, gift the land, site the land, rent the land

29
Figure 2.4 system use case modeling

2.5.1 System Use Case Description

30
1. Land Administrator:
Use Case 1: Manage Land Information
Description: The Land Administrator can add, update, and delete land information in
the system.
Actors: Land Administrator
Pte-conditions: The Land Administrator is logged into the system.
Basic Flow:
1. The Land Administrator selects the option to manage land information.
2. The system displays a list of existing land information.
3. The Land Administrator can add new land information, update existing
information, or delete land information.
4. The system updates the information accordingly.
2.System Administrator:
2.Use Case 1: Manage System account
Description: The System Administrator can configure system settings.
Actors: System Administrator
Preconditions: The System Administrator is logged into the system.
Basic Flow:
1. The System Administrator selects the option to manage system settings.
2. The system displays a list of available settings.
3. The System Administrator can modify the settings as required.
4. The system saves the updated settings.
3.Engineer:
Use Case 1: View Land Information
Description: The Engineer can view land information relevant to their projects.
Actors: Engineer
Preconditions : The Engineer is logged into the system.
Basic Flow:
1. The Engineer selects the option to view land information.
2. The system displays a list of land information relevant to the Engineer's projects.
3. The Engineer can select a specific land record to view detailed information.
4.User:
Use Case 1: Search for Land
Description: The User can search for land based on various criteria.

31
Actors: User
Preconditions : The User is logged into the system.
Basic Flow:
1. The User selects the option to search for land.
2. The system displays search criteria such as location, size, etc.
3. The User enters the search criteria and submits the search request.
4. The system retrieves and displays the matching land records.
5.Registrar Office:
Use Case 1: Manage Land Registration
Description: The Registrar Office can manage land registration processes.
Actors: Registrar Office
Preconditions : The Registrar Office is logged into the system.
Basic Flow:
1. The Registrar Office selects the option to manage land registration.
2. The system displays options for registering new land or updating existing
registrations.
3. The Registrar Office can add new registrations, update existing registrations, or
delete registrations.
4. The system updates the registration information accordingly.
5. login
Use Case: Login to the System
Description: This use case describes the steps involved in logging into the Land
Management System.
Actors: User, System
Preconditions : The system is running and accessible to the user. The user has valid
credentials (username and password).
Basic Flow:
1. The user accesses the login page of the Land Management System.
2. The system displays the login form, prompting the user to enter their username and
password.
3. The user enters their username and password.
4. The system validates the credentials against the stored user database.
5. If the credentials are valid, the system logs the user into the system and redirects
them to the home page.

32
6. If the credentials are invalid, the system displays an error message and prompts the
user to re-enter their credentials.
Post-conditions: The user is logged into the system and has access to their authorized
functionalities.
Alternative Flows:
Invalid Credentials:
 If the user enters invalid credentials, the system displays an error message and
prompts the user to re-enter their credentials.
Forgot Password:
 If the user forgets their password, they can click on the "Forgot Password" link.
 The system prompts the user to enter their email address.
 The system sends a password reset link to the user's email address.
 The user can reset their password using the link provided in the email.
Account Lockout:
 After a certain number of failed login attempts, the system locks the user's account
for a specified period to prevent unauthorized access.
 The user can contact the system administrator to unlock their account.
Exceptions:
System Unavailable:
 If the system is unavailable due to maintenance or other reasons, the user is
informed with a message indicating when the system will be available again.
Technical Issues:
 If there are technical issues during the login process, such as database connectivity
problems, the system displays a generic error message and advises the user to try
again later or contact support.
7. Gift the Land:
Description: This functionality allows users to gift land to another party.
Actors: Land Owner, Recipient
Basic Flow:
1. The Land Owner initiates the process of gifting land through the system.
2. The system verifies the ownership of the land and the identity of the recipient.
3. The Land Owner provides details of the gift, including the recipient's informatio n
and any conditions attached to the gift.
4. The system processes the gift, updating the land ownership records accordingly.

33
5. The system notifies the recipient of the gift.
8. Rent the Land:
Description: This functionality allows users to rent out their land to another party.
Actors: Land Owner, Tenant
Basic Flow:
1. The Land Owner initiates the process of renting out the land through the system.
2. The system verifies the ownership of the land and the identity of the tenant.
3. The Land Owner provides details of the rental agreement, including the rental
period, rent amount, and any other conditions.
4. The system processes the rental agreement, updating the land ownership records
and generating a rental agreement document.
5. The system notifies the tenant of the rental agreement.

9. Register the Land:

Description: This functionality allows users to register their land with the appropriate
authorities.
Actors: Land Owner, Registrar Office
Basic Flow:
1. The Land Owner initiates the process of registering the land through the system.
2. The system verifies the ownership of the land and the requirements for registratio n.
3. The Land Owner provides the necessary documentation and information for
registration.
4. The system processes the registration, updating the land records and generating a
registration certificate.
5. The system notifies the Land Owner of the successful registration.
10. Site the Land:
Description: This functionality allows users to designate specific areas of the land for
various purposes, such as residential, commercial, agricultural, etc.
Actors: Land Owner, Planner
Basic Flow:
1. The Land Owner initiates the process of citing the land through the system.
2. The system displays a map of the land and allows the Land Owner to designate
different areas for different purposes.

34
3. The Land Owner specifies the purpose of each designated area and any specific
requirements or conditions.
4. The system processes the citing, updating the land records with the designated
areas and purposes.
5. The system notifies the Land Owner of the successful citing.

2.6 Functional and Non-Functional Requirements

In a Land Management System (LMS), functional and non-functional requirements are

crucial for defining what the system should do and how it should perform.

2.6.1 Functional Requirements

 Functional requirements describe the specific behaviors or functions the system

must perform. For an LMS, these might include:
 Land Registration: Ability to register new land parcels, including details like
location, size, ownership information, and legal status.
 Land Mapping: Functionality to map land parcels using GIS (Geographic
Information System) tools, allowing users to view, search, and analyze land data
spatially.
 Land Transaction: Support for land transactions such as sales, leases, and
transfers, including features for recording transaction details and updating
ownership records.
 Land Use Planning: Tools for land use planning, zoning, and regulatio n
enforcement to ensure proper land utilization and development.
 Reporting: Generation of reports related to land ownership, transactions, and land
use patterns for monitoring and decision-making purposes.

2.6.2 Non-Functional Requirements

 Non-functional requirements describe the qualities or constraints that the system

must satisfy. For an LMS, these might include:

 Performance: The system should be responsive and able to handle a large volume
of land data efficiently, especially during peak usage times.

35
 Security: Robust security measures to protect sensitive land data from
unauthorized access, modification, or loss.
 Usability: Intuitive user interfaces that are easy to navigate and understand,
catering to users with varying levels of technical expertise.
 Reliability: The system should be reliable, with minimal downtime and the ability
to recover quickly from failures.
 Scalability: Ability to scale the system to accommodate future growth in users and
data volume without significant performance degradation.

 By clearly defining these requirements, stakeholders can ensure that the Land
Management System meets their needs and performs effectively and efficiently.

2.7 User Interface Prototype

 A user interface prototype is like a rough sketch or early version of a user interface.
It's used to test ideas and get feedback before creating the final design. The
prototype shows how the final product will look and work, from basic sketches to
more detailed designs
 UI prototype:- is a preliminary version of a user interface that is created to
visualize and test the design of a software application or system. It simulates the
look and feel of the final product, allowing designers, developers, and stakeholders
to interact with the interface and understand how it will function.

 UI prototype:- can range from simple paper sketches to interactive digita l

mockups, depending on the complexity of the project and the level of detail
required. They typically focus on key aspects of the interface, such as layout,
navigation, content presentation, and interactive elements like buttons, forms, and
menus.

2.7.1 Traditional User Interface Prototype

 A traditional user interface (UI) prototype refers to a prototype that is

created using non-digital methods or tools, such as paper sketches or .

36
 These prototypes are typically used in the early stages of the design
process to explore and communicate design ideas before moving on to
more detailed digital prototypes.
 Like Paper Prototypes : Paper prototypes are hand-drawn sketches of the UI
design on paper. They are used to quickly explore different design ideas and gather
feedback from stakeholders. Paper prototypes are easy and inexpensive to create,
allowing for rapid iteration and refinement of the design

2.7.3 User Interface Flow Diagram

37
Figure2.5 User Interface Flow Diagram

38
 CHAPTER THREE

Design document

3.1 Class Modeling

 Class modeling, also known as class diagramming, is a fundamental aspect of

object-oriented design in software engineering. It involves creating a visual
representation of the classes, attributes, methods, and relationships within a system.
Class diagrams are part of the Unified Modeling Language (UML) and are used to
describe the static structure of a system.

In class modeling, each class is represented as a box with three compartments:

1. The top compartment contains the name of the class.

2. The middle compartment contains the attributes of the class.
3. The bottom compartment contains the methods or operations of the class.
 Arrows between classes represent relationships, such as associations,
generalizations, or dependencies. Associations indicate relationships between
classes, generalizations represent inheritance relationships, and dependencies
indicate that one class depends on another class.

3.1.1 Class Modeling Diagram

 Class Modeling Diagrams are used in the early stages of software

development to help designers and developers understand the structure of

the system and how different parts of the system interact with each other.

They serve as a blueprint for designing the actual implementation of the

system.
 Represents the static structure of a system.

39
Figure 3.1 class modeling diagram

3.2 Sequence Diagram

 A sequence diagram is a type of interaction diagram in UML (Unified Modeling

Language) that shows how objects interact in a particula r sequence to perform a
specific task or scenario. It illustrates the flow of messages and the order in which
interactions occur between objects over time. Sequence diagrams are particula r ly
useful for visualizing the dynamic behavior of a system.
It include the following key elements:

 Objects: Represented as vertical lifelines, which show the lifespan of an object

during the sequence.
 Messages: Represented as arrows between lifelines, indicating the flow of
messages between objects. Messages can be synchronous (denoted by a solid arrow)
or asynchronous (denoted by a dashed arrow).

40
 Activation Bars: Represented as boxes on a lifeline, indicating the period of time
during which an object is performing an operation.
 Return Messages: Represented as dashed arrows returning from a called object to
the calling object, indicating the return of a value or control.
 Constraints: Additional information can be added to sequence diagrams, such as
constraints on messages or conditions under which messages are sent.
 Sequence diagrams are commonly used during the design phase of software
development to visualize and clarify the interactions between objects in a system.
They help developers understand the flow of control and the timing of interactio ns,
which can be useful for identifying potential issues and optimizing the design of a
system.

3.2.1 Sequence Diagram For Login Page

41
Figure 3.2 sequence diagram for Login page

3.2.2 Sequence Diagram For Land Admin

Figure 3.3 sequence diagram for L admin

42
3.3 Activity diagram

 An activity diagram is a type of behavioral diagram in UML (Unified Modeling

Language) that illustrates the flow of control or the sequence of activities in a
system, process, or workflow. It visually represents a series of actions or activities
and the flow of control from one activity to another.

 Activity diagrams are typically used to model business processes, software

workflows, or complex algorithms. They use various symbols to represent differe nt
elements, such as:

 Activity: Represents a specific action or operation, shown as a rounded rectangle.

 Transition: Shows the flow of control from one activity to another, represented by
an arrow.
 Decision: Represents a decision point in the flow, where the flow can take differe nt
paths based on certain conditions, shown as a diamond shape.
 Merge: Shows the merging of multiple paths of control flow, represented by a
diamond shape with multiple incoming arrows and one outgoing arrow.
 Activity diagrams are useful for visualizing the steps and logic of a process, helping
to understand, communicate, and improve the process. They are also valuable for
software developers to design and document the flow of activities in software
systems.

43
Figure 3.4 Activity diagram for login page

44
Figure 3.5 activity diagram for System Admin

3.4 User Interface Design

 User Interface (UI) Design is the process of designing interfaces for software
applications or systems, focusing on creating visually appealing, user-friendly, and
intuitive interfaces. UI design considers the look, feel, and interactivity of the
interface to enhance user experience. It involves understanding user needs, creating
wireframes or prototypes, and implementing the final design.

45
Figure 3.6 UI Design

46
3.5 Object Diagram

 An object diagram in Unified Modeling Language (UML) is a diagram that shows

a complete or partial view of the structure of a modeled system at a specific time.
It represents instances of classes (objects) and their relationships at a particular
moment, providing a snapshot of the system's state.

The followings are Key terms of Object diagram

 Instance Representation: An object diagram represents instances of classes as

objects. These objects are specific instances with actual attribute values.
 Relationships: Object diagrams show relationships between objects, such as
associations, aggregations, or compositions.
 Simplified View: Object diagrams typically focus on a specific scenario or part of
the system, showing only the objects relevant to that scenario.
 Static Structure: Unlike sequence diagrams or activity diagrams, which show
dynamic behavior, object diagrams represent the static structure of the system at a
point in time.
 Usefulness: Object diagrams are useful for illustrating examples or instances of
classes and their relationships, helping to understand how objects interact in the
system.

47
Figure 3.7 Object Diagram

48
3.6 persistence Modeling

 Persistence modeling, in the context of software development, refers to the way

data is represented and stored in a database or other persistent storage system. It
involves mapping the objects and relationships in a software application to the
corresponding data structures and schema in the underlying storage system.

 Persistence modeling often involves the use of Object-Relational Mapping (ORM)

frameworks, which help developers interact with databases using an object-
oriented approach. ORM frameworks like Hibernate (for Java) or Entity
Framework (for .NET) provide mechanisms to map objects to database tables,
manage database transactions, and perform CRUD (Create, Read, Update, Delete)
operations on the data.

 Persistence modeling is important for maintaining data consistency and integr ity
in an application, as well as for optimizing data access and storage. It allows
developers to work with data in a way that is natural and intuitive within the context
of their programming language, while also taking advantage of the performance
and scalability benefits of relational databases.

49
Figure 3.8 persistence model

50
3.7 Deployment Diagram

 A Deployment Diagram in UML shows how software components are deployed on

hardware nodes, illustrating the physical architecture of a system. Nodes represent
hardware or software environments, and artifacts represent files or executable
deployed on nodes. It helps visualize component distribution and deployme nt
dependencies.
 MySQL Console: Represents a tool or interface for managing the MySQL
database.

Figure 3.9 deployment Diagram

51
 The above figure is combination of both Node Deployment Diagram and
Component Deployment Diagram:
 Node Deployment Diagram: This type of diagram would show the physical nodes
(servers, devices) and their relationships. It would include nodes like "Web Server"
and "Database Server" and illustrate how they are connected.
 Component Deployment Diagram: This type of diagram would show the
components (software modules) and how they are deployed on nodes. It would
include components like "Web Application" and "MySQL Database" and show
how they are distributed across nodes.

 Limitation Of The project

 Unexpected Technical Challenges:
 Encountering unforeseen technical issues, such as bugs, performance bottlenecks,
or hardware limitations, can lead to delays.
 Complexity of Requirements:
 Understanding and accurately capturing complex requirements may take more time
than anticipated, especially if the stakeholders' needs are not clear from the
beginning.

CONCLUSION

 Implementing a Land Management System (LMS) presents a range of

opportunities and challenges. While the system can significantly improve land
administration by providing accurate, accessible, and secure land records, various
limitations must be carefully managed.
 Key limitations include resource constraints, technical complexity, data quality
issues, stakeholder resistance, and regulatory challenges. Additiona lly,
infrastructure limitations, data security concerns, training needs, project
management difficulties, cultural factors, scalability, and environmental conditio ns
all pose significant challenges that can impact the successful implementation of an
LMS.

52
 To overcome these challenges and ensure the effective deployment of the system,
it is crucial to:

 Allocate Adequate Resources: Ensure sufficient financial, technical, and human

resources to support the project.
 Engage Stakeholders: Involve all relevant stakeholders early in the process to
gain their support and address any concerns.
 Ensure Data Quality: Focus on improving the quality and availability of land data.
 Build Robust Infrastructure: Invest in the necessary technological infrastructure,
especially in underdeveloped areas.
 Prioritize Security and Privacy: Implement strong data security measures to
protect sensitive information..
 Practice Effective Project Management: Use sound project manageme nt
principles to coordinate activities and manage risks.
 Plan for Scalability and Maintenance: Design the system to be scalable and
ensure plans are in place for ongoing maintenance and support.
 By addressing these limitations proactively, the implementation of an LMS can
lead to more efficient land management processes, improved transparency, and
better land governance. Ultimately, the successful deployment of a Land
Management System can contribute to sustainable development and economic
growth by ensuring that land resources are managed effectively and equitably.

53
 Reference

 https://www.databasestar.com/database- normalization/
 https://www.lucidchart.com/pages/data-flow-diagram
 https://www.lucidchart.com/pages/er-diagrams
 https://www.visual-paradigm.com/guide/uml-unified-modeling-
language/what-is-class-diagram/
 Some of other worked projects I see them as an example
 Youtube

54