<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article  PUBLIC "-//NLM//DTD Journal Publishing DTD v3.0 20080202//EN" "http://dtd.nlm.nih.gov/publishing/3.0/journalpublishing3.dtd">
<article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" dtd-version="3.0" xml:lang="en" article-type="research article">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JCC</journal-id>
      <journal-title-group>
        <journal-title>Journal of Computer and Communications</journal-title>
      </journal-title-group>
      <issn pub-type="epub">2327-5219</issn>
      <publisher>
        <publisher-name>Scientific Research Publishing</publisher-name>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="doi">10.4236/jcc.2024.121015</article-id>
      <article-id pub-id-type="publisher-id">JCC-131011</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Articles</subject>
        </subj-group>
        <subj-group subj-group-type="Discipline-v2">
          <subject>Computer Science&amp;Communications</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>


          A Generic and Reliable Land Acquisition Protocol Implementation for Sub-Saharan Africa Countries

        </article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author" xlink:type="simple">
          <name name-style="western">
            <surname>Bayomock</surname>
            <given-names>Linwa André Claude</given-names>
          </name>
          <xref ref-type="aff" rid="aff1">
            <sup>1</sup>
          </xref>
          <xref ref-type="corresp" rid="cor1">
            <sup>*</sup>
          </xref>
        </contrib>
        <contrib contrib-type="author" xlink:type="simple">
          <name name-style="western">
            <surname>Traore</surname>
            <given-names>Hamidou</given-names>
          </name>
          <xref ref-type="aff" rid="aff1">
            <sup>1</sup>
          </xref>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <addr-line>Department of Computer Science, International University of Grand-Bassam, Grand-Bassam, Ivory Coast</addr-line>
      </aff>
      <pub-date pub-type="epub">
        <day>03</day>
        <month>01</month>
        <year>2024</year>
      </pub-date>
      <volume>12</volume>
      <issue>01</issue>
      <fpage>208</fpage>
      <lpage>245</lpage>
      <history>
        <date date-type="received">
          <day>16,</day>
          <month>December</month>
          <year>2023</year>
        </date>
        <date date-type="rev-recd">
          <day>28,</day>
          <month>January</month>
          <year>2024</year>
        </date>
        <date date-type="accepted">
          <day>31,</day>
          <month>January</month>
          <year>2024</year>
        </date>
      </history>
      <permissions>
        <copyright-statement>&#169; Copyright  2014 by authors and Scientific Research Publishing Inc. </copyright-statement>
        <copyright-year>2014</copyright-year>
        <license>
          <license-p>This work is licensed under the Creative Commons Attribution International License (CC BY). http://creativecommons.org/licenses/by/4.0/</license-p>
        </license>
      </permissions>
      <abstract>
        <p>


          Land acquisition is subject of many frauds worldwide. In Africa countries, land acquisition frauds are a real curse. Main reasons of the high land acquisition frauds in Africa are a lack of a reliable land acquisition protocol implementation, no centralized information system that records land transactions and integrates all actors, lack of education about the acquisition protocol and lack of applied sanctions in case of frauds. As of sanctions, the issue is bound to the corruption plague in Africa. Authorities that are supposed to rule the laws are not well paid and are part of the corruption scheme. Most frequent frauds are multiple sales of the same land, falsified land title, false owner identification. In Africa, a land belongs generally to the first residents of the area. To claim ownership of a land, an owner should be recognized by the rural or city authorities. To achieve this recognition, he must obtain from those authorities an attribution letter. The author proposed a complete and reliable land acquisition protocol named ACLAP (Africa Countries Land Acquisition Protocol). The purpose of this paper is to explain the main components of the protocol implementation and show its efficiency when confronting fraud threats. In this paper, a Generic and Reliable Land Acquisition Protocol Implementation in Sub-Saharan Africa countries context is proposed. The platform keeps relevant land transaction information for administrators, managers, buyers, sellers, or for people consultation purpose. The application may be used in village, city, department, region, or country for land management decision making.

        </p>
      </abstract>
      <kwd-group>
        <kwd>Land</kwd>
        <kwd> Acquisition</kwd>
        <kwd> Protocol</kwd>
        <kwd> Reliable</kwd>
        <kwd> Africa</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="s1">
      <title>1. Introduction</title>
      <p>Land is the subject of the interest in the land acquisition. What is a land? In literature many land definitions are published. But in the context of this paper, a land is an earth area that has well known geographical boundaries. A land has adjacent lands and may have vegetation, rivers, forest, animals, and other things included in the identified area. Acquiring a land is a process that aims at the end to assign a land ownership to a buyer, a physical or moral person.</p>
      <p>Meanwhile questions remained as to whether the seller is really the owner. Does he have the right to sell? When managing villages, cities, departments, regions or countries, the administrators’ main challenge is to first know or establish the geographical boundaries of the area under their management. Main actors (seller, buyer, and/or domain administrators) of a land acquisition endeavor are confronted with the same problem. In addition to areas limits, answers must be provided to other questions as the land ownership determination problem? Does the land belong to the seller? Does the seller have the required owner representative rights as per the law?</p>
      <p>In sub-Saharan Africa countries, the land first owners are the inhabitants, i.e., the families that first established themselves in the concerned areas, Mwangi Gideon W. (2011). Their land area limits are generally recognized using landscape signs as lakes, trees, or roads. Most of the time, the physical recognition of those signs is not recorded on papers or electronically, making it very difficult for those that have been instructed about those limit signs to be fair, concise or precise in the recognition of the area limits. With years and the effects of nature, used signs may disappear, and may create dispute scenarios.</p>
      <p>In the case of a land mutation (sell or rent), the land owner is sometimes questionable. The land owner anterior history may require laws to be said and applied. These aggrieving issues make the land acquisition process in Sub-Saharan Africa countries a real bottleneck and something to be very cautious before entering into.</p>
      <p>
        The authors [<xref ref-type="bibr" rid="scirp.131011-ref1">1</xref>] proposed a robust and reliable land acquisition protocol (ACLAP) that takes in account those challenges and minimizes the frauds using a strong control of data integrity.
      </p>
      <p>The acquisition process is a set of activities/services that are well-orchestrated to meet the final goal of assigning the land to the right person. The services orchestration is included in an architecture that takes into account the requirements that the proposed implementation must solve. These services are discovered, and structured and their related data model is elaborated. The minimal infrastructure required to deploy the land acquisition is designed considering the security constraints aspects.</p>
      <p>Solutions proposed relied in land management or administration without strong considerations to solve land acquisitions frauds. None of the proposed solution is built through a protocol that takes into account all actors of the land acquisition process.</p>
      <p>The organization of this paper is as follows: after the introduction, the motivations that sustain this work are explained, and then a summary of related work is provided, followed by the requirements land acquisition. Afterwards, the proposed architecture is presented including the data model, the services and their interactions; then the implementation guides, technologies and codes are explained. The obtained results are published and analyzed; finally the conclusion is given.</p>
    </sec>
    <sec id="s2">
      <title>2. Motivations</title>
      <p>We have three main motivations for this work and these are: economic, social and reduction of potential conflicts.</p>
      <p>Land is an important resource for a nation. Generally defined as a part of earth not covered by water, the land is the first and most important resource of a country. It is used for habitation, for agriculture, for mines extraction, for petrol extraction, to bury human bodies, to build or support infrastructures, and more. Some of its values are bound to human works and other values are nature gifts. Land is thus very important for international and national perspectives. A country must know its area boundaries and the boundaries with its neighbor countries. Country boundaries are generally recognized by United Nations Organization. Internally, a country has administrative subdivisions. Those administrative structures put in place for governance purpose are divided in regions, departments, cities, or villages. Each of those divisions must be clearly identified geographically and its boundaries must be known. Land revenue generated by a country can then be drilled down to the granularity of a region, department, city or village to show the contribution of each subdivision to the economic wealth of a country. Therefore, the land and its economic aspects (boundaries, geographical situation, pictures, detected natural resources, and evaluation) must be well identified and recorded in a land information system.</p>
      <p>In some communities of Sub-Saharan country (e.g. Ivory Coast), a land belongs to a cultural/traditional group. These cultural groups have implemented a system to manage social problems and these organizations oversee the development of activities in their respective region. The leaders of those communities play an important role in applying the policy put in place. In this regard, their decisions are recognized by the government. On the other hand, in the cities, the government has administrative personnel that is in charge of the land acquisition process. A land information system must identify all authorities that are involved in the land acquisition approval and integrity, determine the land owner and the land buyer, register the land acquisition transaction and the land boundaries. The land information system must record also the historical information to maintain the traceability of owners, authorities or others actors over time.</p>
      <p>Even when the rules and land acquisition processes are well implemented, there are some gray parts in the process that may generate conflictual situations. Non honest individuals may sell the same land to many potential acquirers before the transaction is actually recorded in the system. Causes of this issue may be due in fact that a dishonest owner has some complicity at certain decision level or the buyer may not be aware of the whole land acquisition process. Other scenarios may be a fraudster that sells a land that he does not own to one or many clients. Thus, a land information system can be critical in helping avoid some of these frauds. In the meantime, the use of the land information system must be emphasized and people involved in a land purchasing must be educated on the official land acquisition process to reduce frauds percentage. And potential acquirers may thereby consult available land information to know more about the most recent data about the coveted land.</p>
      <p>
        Many countries, mainly those that are under-developed, are not using reliable data as inputs in land costs. This means that the error margin and incertitude of the provided costs are generally unknown and the stated cost may be way higher than the normal one. With a reliable land information system, a higher quality of recorded data can be used as inputs in the land functions dealing with costs and can also be instrumental in readjusting the land governance policies. In fact, Land governance is a set of policies that go across different administration units to optimize the land cost, usability, tenure and/or development of land management [<xref ref-type="bibr" rid="scirp.131011-ref2">2</xref>] .
      </p>
      <p>
        In Sub-Saharan Africa countries, almost each person knows at least one relative (friend, family member) that has been abused in a land acquisition transaction. Sometimes, even tactical and temporary solution, shared by experienced people may not work. Considering these facts, software research may contribute in reducing the abuse risks through a Generic and Reliable Land Acquisition Protocol Implementation for the Sub-Saharan Africa countries context. A Generic and Reliable Land Acquisition Protocol (ACLAP) proposed by [<xref ref-type="bibr" rid="scirp.131011-ref1">1</xref>] will be used to support the implementation.
      </p>
    </sec>
    <sec id="s3">
      <title>3. Related Work</title>
      <p>Related publications may be classified in three categories: land governance, land acquisition, and land information system frameworks.</p>
      <p>
        Land governance is a set of business functions or objectives, resource supports, constraints, data, and organization of administrative units, business processes and their information flows, delivery of required documents with the goal to optimize the land administration costs. The implementation of a governance vision requires the usage of a structured framework that drives its deployment through the different administrative units. The author in [<xref ref-type="bibr" rid="scirp.131011-ref3">3</xref>] proposes a framework GLAP (Global Land Administration Perspective) that has four business functions: land tenure, land use, land value and land development. The land tenure englobes activities as the processes and institutions related to securing access to land and inventing commodities in land, and their allocation, recording and security; cadastral mapping and legal surveys to determine parcel boundaries; creating new properties or altering existing properties; the transfer of property or use from one party to another through sale, lease or credit security; and the management and adjudication of doubts and disputes regarding land rights and parcel boundaries. The land value contains the processes and organizations in charge of the land value assessment and properties; the tax revenue calculation and revenue gathering; and the management and adjudication of land valuation and taxation disputes. The land use controls the processes and institutions of land use through adoption of planning policies and land use regulations at national, regional and local levels; the enforcement of land use regulations; and the management and adjudication of land use conflicts [<xref ref-type="bibr" rid="scirp.131011-ref4">4</xref>] . The land development is related to the processes and institutions in charge of building new physical infrastructure and utilities; the implementation of construction planning; public acquisition of land [<xref ref-type="bibr" rid="scirp.131011-ref5">5</xref>] ; expropriation; change of land use through granting of planning permissions, building and land use permits; and finally the distribution of development costs [<xref ref-type="bibr" rid="scirp.131011-ref6">6</xref>] . Authors in [<xref ref-type="bibr" rid="scirp.131011-ref7">7</xref>] propose a framework named FELA (Framework for Effective Land Administration). FELA provides a framework that drives the implementation of country sustainable development goals. FELA also guides for the establishment of responsible land governance structures, effective and efficient land institutions, and leadership in the land sector, with clearly defined propositions, ideally centered upon transparency, accountability, inclusiveness, accessibility, participation, gender and youth sensitivity, consideration of the vulnerable and marginalized people. FELA has six business objectives: land use, land development, land tenure, land value, land policies and integrated geospatial information. Land Policies objective is an additional business objective compared to GLAP, and it is related to laws and policies surrounding the establishment, renewal and strengthening of land administration and management systems; it is to be driven by responses to social, economic and environmental needs. In general, having holistic land policies based around sustainability will result in a more efficient legislative design and administration [<xref ref-type="bibr" rid="scirp.131011-ref8">8</xref>] [<xref ref-type="bibr" rid="scirp.131011-ref9">9</xref>] . The integrated geospatial information provides a basis, a reference and a mechanism to establish or improve national geospatial information management arrangements. It coordinates alignment activities between existing national capacities, and infrastructures, including in the land sector.
      </p>
      <p>Both GLAP and FELA are high quality frameworks used as standards in the development of land administration management. However, those frameworks are guidelines to optimize land governance and do not define how information could be extracted from processes to build a business intelligence system that sustain decision making and reduce land conflicts.</p>
      <p>
        Another research axis is the “land management applications”. In [<xref ref-type="bibr" rid="scirp.131011-ref10">10</xref>] , a land information system for villages and towns is proposed. It handles land usability, farm land protection, and land registration with spatial geo-information, laws enforcement and maintenance services. In [<xref ref-type="bibr" rid="scirp.131011-ref3">3</xref>] , the author proposes the land information systems for Denmark. The solution is based on GLAP framework and large module interactions without a clear identification of their interfaces with the business intelligence system.
      </p>
      <p>
        One important land research axis is the land planning, use and management. In [<xref ref-type="bibr" rid="scirp.131011-ref11">11</xref>] [<xref ref-type="bibr" rid="scirp.131011-ref12">12</xref>] , the authors propose an approach to measure land use and management through audit functions. The approach requires collecting evaluation measures of land potentials, as well as measures relative to how the land has been used so far, then the environment impact measures of the land usability. The authors in [<xref ref-type="bibr" rid="scirp.131011-ref13">13</xref>] [<xref ref-type="bibr" rid="scirp.131011-ref14">14</xref>] use the same evaluation measures to take land planning decisions relative to the land management orientations. Both papers are very high quality but they do not elaborate on the land management infrastructure support: the land information system.
      </p>
      <p>
        Other aspect is the implementation GAP of the LIS (Land Information System) in developed countries versus developing countries. Unlike in developed countries where LIS are well implemented and largely used, implementing a LIS in developing countries is challenging [<xref ref-type="bibr" rid="scirp.131011-ref15">15</xref>] [<xref ref-type="bibr" rid="scirp.131011-ref16">16</xref>] . In developing countries where such information systems are in place, they remain latent; hence, essential decisions are made based on limited information [<xref ref-type="bibr" rid="scirp.131011-ref17">17</xref>] . For example, after efficiently implementing LIS in Rwanda, the bureaucratic nature of the registration system discouraged landowners from registering their properties, thereby making their LIS non-reliable for decision making [<xref ref-type="bibr" rid="scirp.131011-ref18">18</xref>] . Similarly, Kenya’s LIS is not maintained and their data records are not up to date due to informal registration that is not documented [<xref ref-type="bibr" rid="scirp.131011-ref19">19</xref>] [<xref ref-type="bibr" rid="scirp.131011-ref20">20</xref>] . Other challenges may result from inadequate land data, poor data quality, and the government’s unwillingness to invest in LIS [<xref ref-type="bibr" rid="scirp.131011-ref21">21</xref>] [<xref ref-type="bibr" rid="scirp.131011-ref22">22</xref>] . In the scope of innovation in information technology such as LIS, the authors in [<xref ref-type="bibr" rid="scirp.131011-ref23">23</xref>] argued that the system’s adoption and usage are crucial factors in achieving the overall success of implementation. LIS must be used to achieve the expected outcome; however, this is often not the case in many developing countries. Liberia, for instance, has failed to integrate their LIS into their land administration function [<xref ref-type="bibr" rid="scirp.131011-ref24">24</xref>] .
      </p>
      <p>Our proposed is based on a simple, reliable land acquisition that include the main actors of the process. But its success is bound to the education of the users that must know about its existence and broking the resistance of administrative that are comfortable with the lack of strong rules of current land acquisition process in Sub-Saharan countries.</p>
    </sec>
    <sec id="s4">
      <title>4. Used Land Acquisition Process and Protocol Description</title>
      <sec id="s4_1">
        <title>4.1. Land Acquisition Process</title>
        <p>
          The land acquisition process is varying from one country to another. In [<xref ref-type="bibr" rid="scirp.131011-ref1">1</xref>] , the land acquisition processes of three selected countries are described: C&#244;te d’Ivoire, Senegal and Cameroun.
        </p>
        <p>1) C&#244;te d’Ivoire</p>
        <p>
          The land acquisition involves five main actors: the seller, the buyer, the approval committee that confirms the transaction, the urban administrator representative, the domain administrator representative [<xref ref-type="bibr" rid="scirp.131011-ref25">25</xref>] . The buyer is the land acquirer. He collects from the seller, the existing land documents that he wants to buy. Then he checks with an urban administrator representative (MCLAU representative) about the current owner and if the land is not a private domain of the nation. If there is no problem with the checks, he may continue the acquisition process or stops. In case he chooses to continue the process, he will then proceed to the payment part by first negotiating the payment date with the approval committee. Then an invitation is sent to the approval committee team members about the land acquisition payment. At the payment date, the buyer pays the land at the negotiated price along with the related administration fees. Afterwards, a bill receipt is delivered immediately to him. And one to two weeks later, an attribution letter signed by the highest member of the approval committee team is delivered to the buyer. The buyer introduces an ACD (Attestation of definitive concession) request to an urban administrator with all requested documents (technical drawing and location, request fees, tax of land title). The urban administrator checks the genuineness of the provided documents and transfers the file to the domain administrator for the land title establishment. After verifying the successful completion of land title, an urban administrator delivered the ACD to the buyer.
        </p>
        <p>2) Cameroun</p>
        <p>
          In Cameroon, the land acquisition is done in five main phases and involves six main actors: the buyer, the seller, the geometer, the urban agent/administrator, the notary, and the domain agent/administrator [<xref ref-type="bibr" rid="scirp.131011-ref26">26</xref>] [<xref ref-type="bibr" rid="scirp.131011-ref27">27</xref>] . The first phase is the land split and mutation. In this phase the seller wants to sell part or total area of his land. The seller is the initiator of this act. He fills the request of land split or mutation in favor of the buyer. The land split or mutation form signed by all parties is then joined to the technical documents produced by a geometer after the drawing of various graphs regarding the topography of the land, the geographical area limits of the land, the position of the land with respect to other well registered and adjacent lands and their submission to an urban administrator. In the second phase, the request form is processed by a cadastral administrative unit and a validation form is given attesting the conformity of produced documents as well as the urban map road plan in the concerned area. In the third phase, when the urban administrative unit receives a positive feedback from the cadastral unit, he then issues an urban certificate. Using the urban certificate, the seller and buyer meet with a notary to conclude the land purchase. The payment of the land at the agreement price is done in front of the notary at the fourth phase. At the fifth phase, the land certificate is established by the notary and a copy is given to the buyer.
        </p>
        <p>3) Senegal</p>
        <p>
          In Senegal, the land acquisition is done in four main phases and involves six main actors [<xref ref-type="bibr" rid="scirp.131011-ref28">28</xref>] . The first phase is a request introduced by the seller to the cadastral administrative unit. The request goal is to obtain the cadastral drawings that determine the geographical area limits of the land, the position of the land with respect to other well registered and adjacent lands, the land classification (public, individual private, national private domain, or national domain). In case the land belongs to an individual, the purchase must be completed in the presence of a notary and he/she must produce an official purchase document that is joined to the land title request. Then, the seller in conjunction with the buyer make a land title request to APIX (a central organization that is handling all land titles’ processing) organization. The file received by APIX must contain the following documents: the purchase form signed by a notary, the cadastral land drawings, the building house project architecture drawings and engineering, project cost estimates, the number of jobs created. After a successful land title request processing, the APIX delivers a land title to the buyer.
        </p>
      </sec>
      <sec id="s4_2">
        <title>4.2. Proposed and Used Land Acquisition Protocol ACLAP</title>
        <p>1) Land Acquisition Protocol Work Flow</p>
        <p>
          The land acquisition processes in Cameroun, Senegal and C&#244;te d’Ivoire have similar type of actors [<xref ref-type="bibr" rid="scirp.131011-ref1">1</xref>] . But those actors are sometimes named differently. For example, in Cameroun, the urban agent/administrator actor is equivalent to MCLAU agent in C&#244;te d’Ivoire and an APIX agent in Senegal. In the generic work flow of land title acquisition process (<xref ref-type="fig" rid="fig1">Figure 1</xref>), we are using the urban agent word to identify the concerned agent. For integrity, transparency and earlier fraud detections, a generic work flow of land title acquisition is proposed. This work flow has the advantage that it can be applied in many African countries as they have similar land acquisition processes. The integrity and conformity of documents are part of the work flow orientations and decisions.
        </p>
        <p>2) ACLAP Protocol Description</p>
        <p>a) The buyer checks or lookups for land on sale in a particular area. He/She may use different channels (web sites, well known sellers, recommended sellers, etc.). The buyer must provide his metrics in terms of price, location, square area, etc…</p>
        <p>b) The seller agent sends back available lands that match the given criteria along with the associated ownership documents (land title, land location, land drawings, etc.).</p>
        <p>c) The buyer picks the land that he likes and sends the corresponding land ownership documents to an urban agent for an integrity verification.</p>
        <p>d) The urban agent checks the documents conformity with the domain administrator and sends back his response about the conformity of the documents. He also includes in the response whether the land’s ownership has not changed in the past or whether it is in the process of changing ownership.</p>
        <p>e) In case the land ownership is good, the seller requests to the urban agent the design of the land drawings that match the targeted land.</p>
        <p>f) The urban agent forwards the request of the land drawing task to the cadastral services, and then, the request is assigned to a geometer.</p>
        <p>g) The geometer makes the land drawings and the cadastral services return them to the urban agent.</p>
        <p>h) The urban agent then gives a copy of the land drawings to the buyer.</p>
        <p>i) The buyer and the seller meet with the notary for the payment.</p>
        <p>j) The buyer and the seller provide to the notary the original land documents as well as the approved documents and land drawings obtained from the urban agent.</p>
        <p>k) The notary checks the conformity of the documents.</p>
        <p>l) After a successful land conformity check, the buyer pays for the agreed price and fees, and gives the money to the notary.</p>
        <p>m) The notary verifies that the amount matches the agreed price plus his own fees.</p>
        <p>n) The notary then gives to the buyer his due and produces two receipts one for the seller and one for the buyer.</p>
        <p>o) The notary requests to an urban agent a land title and ownership change on behalf of the buyer and the seller.</p>
        <p>p) The urban agent forwards to the cadastral services a land title request establishment.</p>
        <p>q) The domain administrator then checks for the land title and establishes a land title and returns it to the urban agent.</p>
        <p>r) The urban agent notifies and sends the land title to the notary.</p>
        <p>s) The notary notifies the buyer and delivers to him/her a land title.</p>
      </sec>
    </sec>
    <sec id="s5">
      <title>5. Protocol Requirements and Solution Approaches</title>
      <p>The requirements that are in scope of the implemented protocol requirements are: integrity, confidentiality and reliability.</p>
      <sec id="s5_1">
        <title>5.1. Integrity</title>
        <p>The importance of integrity in the land acquisition is very high. We define as integrity, the protection of the important data collected and saved in the information system of the land acquisition. These collected data that must be protected are related to the identity of the application actors (buyer, seller, owner, notary, land title administrator, urban agent, and urban administrator) as well as land document authenticity (urban land certification, attribution land letter, or land title).</p>
        <p>
          An attacker of the system may be external or internal to the involved organizations that have access rights on the information system resources. The proposed solution takes in account the different cases (<xref ref-type="table" rid="table1">Table 1</xref>).
        </p>
      </sec>
      <sec id="s5_2">
        <title>5.2. Confidentiality</title>
        <p>
          Sensitive data that are intercepted or read from the database won’t be exploitable by the attacker as they will be encrypted by a RSA or 3DES Key (<xref ref-type="table" rid="table2">Table 2</xref>).
        </p>
      </sec>
      <sec id="s5_3">
        <title>5.3. Reliability</title>
        <p>
          Users are expected to use the land information system anytime. Degradation of the quality of service should not stop the user accessibility to the information system. To achieve this requirement (<xref ref-type="table" rid="table3">Table 3</xref>), servers must be redundant to allow the service relay in case the primary server instance failed to deliver services, the secondary server instance will be used. Strong security policy must also be put in place to protect the software and other system resource from attacks as the DoS (Denial of Services).
        </p>
      </sec>
    </sec>
    <sec id="s6">
      <title>6. Proposed Architecture</title>
      <sec id="s6_1">
        <title>6.1. Infrastructure Architecture</title>
        <p>The infrastructure architecture is composed of client and server subsystems</p>
        <table-wrap id="table1" >
          <label>
            <xref ref-type="table" rid="table1">Table 1</xref>
          </label>
          <caption>
            <title> Integrity solution approach</title>
          </caption>
          <table>
            <tbody>
              <thead>
                <tr>
                  <th align="center" valign="middle" >Threat</th>
                  <th align="center" valign="middle" >Description</th>
                  <th align="center" valign="middle" >Solution</th>
                  <th align="center" valign="middle" >Technologies</th>
                </tr>
              </thead>
              <tr>
                <td align="center" valign="middle" >Theft of the identity</td>
                <td align="center" valign="middle" >Theft of a user identity consists to take advantage of the weak access rights constraints to the information system or the lack of users’ IT knowledge and then obtain their credentials to the information system.</td>
                <td align="center" valign="middle" >In case the attacker got credentials of an authorize user as the username, it is imperative to make it hard to him to get access to the sensitive data of the information system. The proposed solution is to use something that belongs to the user meaning the biometric technology.</td>
                <td align="center" valign="middle" >The iris biometric is the recommended one. It is known as the best biometric in term of accuracy (the image match incertitude is less than 1%).</td>
              </tr>
              <tr>
                <td align="center" valign="middle" >Alteration of an authentic document</td>
                <td align="center" valign="middle" >The attacker may use a replay technique by altering an original and authentic document received from the information system.</td>
                <td align="center" valign="middle" >The solution consists to stamp a shared document with a date and a unique code. The code is uniquely recorded in the system and it is signed with a private key. Any shared document has a validity of 24 h maximum.</td>
                <td align="center" valign="middle" >The size of the code is an important factor in the solution. A 512 bits is challenging enough when it is coupled with a RSA encryption algorithm.</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <table-wrap id="table2" >
          <label>
            <xref ref-type="table" rid="table2">Table 2</xref>
          </label>
          <caption>
            <title> Confidentiality solution approach</title>
          </caption>
          <table>
            <tbody>
              <thead>
                <tr>
                  <th align="center" valign="middle" >Threat</th>
                  <th align="center" valign="middle" >Description</th>
                  <th align="center" valign="middle" >Solution</th>
                  <th align="center" valign="middle" >Technologies</th>
                </tr>
              </thead>
              <tr>
                <td align="center" valign="middle" >Plain text document captured during data transportation</td>
                <td align="center" valign="middle" >Non encrypted data sent between two end machines that are communication, may be captured by an attacker.</td>
                <td align="center" valign="middle" >The solution resides to use a strong encryption algorithm (3DES or RSA).</td>
                <td align="center" valign="middle" >Use RSA private and public keys. A key size of 2048 bits is an excellent choice.</td>
              </tr>
              <tr>
                <td align="center" valign="middle" >Non encrypted and Saved sensitive data</td>
                <td align="center" valign="middle" >An attacker that works for an organization that produces and has access to sensitive data may use this advantage to attack the information system.</td>
                <td align="center" valign="middle" >The solution resides in encrypting sensitive data first, then save them in the storage system. The use of a strong encryption algorithm (3DES or RSA) is recommended.</td>
                <td align="center" valign="middle" >Use RSA private and public keys. A key size of 2048 bits is an excellent choice.</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <table-wrap id="table3" >
          <label>
            <xref ref-type="table" rid="table3">Table 3</xref>
          </label>
          <caption>
            <title> Reliability solution approach</title>
          </caption>
          <table>
            <tbody>
              <thead>
                <tr>
                  <th align="center" valign="middle" >Threat</th>
                  <th align="center" valign="middle" >Description</th>
                  <th align="center" valign="middle" >Solution</th>
                  <th align="center" valign="middle" >Technologies</th>
                </tr>
              </thead>
              <tr>
                <td align="center" valign="middle" >DoS attack</td>
                <td align="center" valign="middle" >Prevent the information system to use its resource, pushing to a big degradation of the quality of services.</td>
                <td align="center" valign="middle" >Put in place a network and application firewall as well a good anti-virus tool to preserve server machines.</td>
                <td align="center" valign="middle" >Use RSA private and public keys. A key size of 2048 bits is an excellent choice.</td>
              </tr>
              <tr>
                <td align="center" valign="middle" >Degradation of services offered</td>
                <td align="center" valign="middle" >The information system is not able de deliver an acceptable quality of services.</td>
                <td align="center" valign="middle" >A redundancy plan is recommended.</td>
                <td align="center" valign="middle" >Secondary server should have similar characteristics as the principal server.</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <p>
          (<xref ref-type="fig" rid="fig2">Figure 2</xref>).
        </p>
        <p>&#183; The client subsystem is the set of machines used by clients (buyer, seller, urban agent/administrator, domain administrator, geometer, and notary). Those machines are either mobile phones, tabs, laptops, or computers. They are connected to the proposed solution through Web browser and Internet Protocol.</p>
        <p>&#183; The server subsystem is the set of Web servers (main server and backup</p>
        <p>servers), application server and database servers (urban and domains servers). The server subsystem contains the application software. The database subsystem manages the land data and the land transaction information. The database subsystem contains the set of metadata and data required and that supports the land application.</p>
      </sec>
      <sec id="s6_2">
        <title>6.2. Software Architecture</title>
        <p>
          The software architecture (<xref ref-type="fig" rid="fig3">Figure 3</xref>) is made of 6 layers: web pages’ orchestration and navigation, web listeners’ services, web views, entity management, data entities and data access management.
        </p>
        <p>&#183; The web pages’ orchestration and navigation layer contains web pages and the navigation flow between web pages. A web page is designed using the MVC pattern. Each web page is bound to a view object and may incorporation listeners to capture the user events.</p>
        <p>&#183; The web listeners’ service layer is a set of classes that handle user events on the web pages. The web page user events are bound to the listeners. The listener</p>
        <p>performs the requested action and returns the results. The results are rendered by calling a returned page or by displaying a dialog message.</p>
        <p>&#183; The web view layer is a set of classes that encapsulates the application data displayed on a web pages. Each class acting a view, has a scope (application, session, view or request). The view in an application scope is acting as a global or shareable view and its object content is applied to all application users. In case of the session scope, the view is active for a user full session. In case of the view scope, the view is active as long as the view is still used in the web page navigation. In the request scope, the view is active only for the current request.</p>
        <p>&#183; The entity management layer contains the set of classes that manages (creates, finds, updates and/or deletes) the basic or plain data entity.</p>
        <p>&#183; The data entities layer contains the set of plain classes required to build the application. In general, each data entity is mapped to a database table.</p>
        <p>&#183; The data access layer contains the class or classes that interact with the database tables. The interaction with the database is achieved via a database connectivity protocol.</p>
        <p>&#183; The database subsystem contains the set of metadata and data required and that supports the land application.</p>
      </sec>
      <sec id="s6_3">
        <title>6.3. Use Cases</title>
        <p>
          The implementation of the solution is an ongoing process. A use case is a service offered to the users to interact with the server machines. Due to the implementation complexity and limited funds for the project, for the first implementation version, the following use cases have been taken in account (<xref ref-type="fig" rid="fig4">Figure 4</xref>). In Tables 4-15, the main use cases of the application are described.
        </p>
        <table-wrap-group id="4">
          <label>
            <xref ref-type="table" rid="table4">Table 4</xref>
          </label>
          <caption>
            <title> Add urban/cadastral/notary manager account</title>
          </caption>
        </table-wrap-group>
        <table-wrap id="table5" >
          <label>
            <xref ref-type="table" rid="table5">Table 5</xref>
          </label>
          <caption>
            <title> Find urban/cadastral/notary manager account</title>
          </caption>
          <table>
            <tbody>
              <thead>
                <tr>
                  <th align="center" valign="middle" >Use case Name</th>
                  <th align="center" valign="middle" >Find Urban/Cadastral Manager Account</th>
                </tr>
              </thead>
              <tr>
                <td align="center" valign="middle" >Primary actor</td>
                <td align="center" valign="middle" >System administrator</td>
              </tr>
              <tr>
                <td align="center" valign="middle" >Secondary actor</td>
                <td align="center" valign="middle" >Application System</td>
              </tr>
              <tr>
                <td align="center" valign="middle" >Brief description</td>
                <td align="center" valign="middle" >This use case allows the administrator to search Account record in the application system.</td>
              </tr>
              <tr>
                <td align="center" valign="middle" >Pre-condition</td>
                <td align="center" valign="middle" >1. The user is logged into the application system. 2. The application system displays a welcome page with all services.</td>
              </tr>
              <tr>
                <td align="center" valign="middle" >Normal flows</td>
                <td align="center" valign="middle" >1. The user clicks on “Account Services” button 2. The system returns the “Account Services” sub-menu which contains the following items: a. Urban Services b. Cadastral Services c. Notary Services 3. The domain administrator selects the service he/she wants to visit 4. In case, the administrator selects “Urban Services”, then the system returns a table containing users’ information plus the (create, refresh, search) buttons at the top left corner of the table. 5. The domain administrator selects the “Search” button, then the system returns an input window. 6. The domain administrator enters a keyword and clicks on “Search” button to display the record associated to the keyword entered. 7. In case, the administrator selects “Cadastral Services”, then the system returns the similar information as at step 4 8. The system displays the corresponding record that matches the keyword entered by the domain administrator.</td>
              </tr>
              <tr>
                <td align="center" valign="middle" >Alternate flows</td>
                <td align="center" valign="middle" >1. The administrator enters a keyword that does not match any record. 2. The system displays an error message “Record not found”. 3. The administrator can either try again or cancel the operation by clicking on “Erase” button. 4. If the administrator clicks on “Erase” button, the system returns back to the table containing the users’ information page.</td>
              </tr>
              <tr>
                <td align="center" valign="middle" >Post-condition</td>
                <td align="center" valign="middle" >If the use case was successful, the system displays the record that match the entered keyword. Otherwise, the system displays no record.</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <table-wrap id="table6" >
          <label>
            <xref ref-type="table" rid="table6">Table 6</xref>
          </label>
          <caption>
            <title> Delete/deactivate urban/cadastral manager account</title>
          </caption>
          <table>
            <tbody>
              <thead>
                <tr>
                  <th align="center" valign="middle" >Use case Name</th>
                  <th align="center" valign="middle" >Delete/Deactivate Urban/Cadastral Manager account</th>
                </tr>
              </thead>
              <tr>
                <td align="center" valign="middle" >Primary actor</td>
                <td align="center" valign="middle" >System administrator</td>
              </tr>
              <tr>
                <td align="center" valign="middle" >Secondary actor</td>
                <td align="center" valign="middle" >Application System</td>
              </tr>
              <tr>
                <td align="center" valign="middle" >Brief description</td>
                <td align="center" valign="middle" >This use case allows the system administrator to delete/Deactivate Account record from the application system.</td>
              </tr>
              <tr>
                <td align="center" valign="middle" >Pre-condition</td>
                <td align="center" valign="middle" >1. The user is logged into the application system. 2. The application system displays a welcome page with all services</td>
              </tr>
              <tr>
                <td align="center" valign="middle" >Normal flows</td>
                <td align="center" valign="middle" >1. The administrator clicks on “Account Services” button 2. The system returns the “Account Services” sub-menu which contains the following items: a. Urban Services b. Cadastral Services c. Notary Services 3. In case, the user selects “Urban Services”, then the system returns a table containing users’ information plus the (create, refresh, search) buttons at the top left corner of the table and three buttons (Edit, Delete, PDF) on the right end of the table. 4. The administrator clicks on “Delete” button 5. The system returns a window with “Yes” and “No” to confirm the deletion. 6. In case the administrator selects “Yes”, the system extracts the user data with the id and delete the record associated from the database. 7. The operation is canceled if the administrator selects “No” 8. The system returns to the previous state.</td>
              </tr>
              <tr>
                <td align="center" valign="middle" >Alternate flows</td>
                <td align="center" valign="middle" >1. The administrator can either try again or cancel the operation by clicking on “No” button. 2. If the administrator clicks on “No” button, the system returns back to the previous state.</td>
              </tr>
              <tr>
                <td align="center" valign="middle" >Post-condition</td>
                <td align="center" valign="middle" >If the use case was successful, the selected record is deleted from the system. Otherwise, the state of the system is unchanged by the use case.</td>
              </tr>
              <tr>
                <td align="center" valign="middle" >Exceptions</td>
                <td align="center" valign="middle" >The administrator aborts the delete operation by clicking on “No” button at step 7 of the Normal Flow</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <table-wrap-group id="7">
          <label>
            <xref ref-type="table" rid="table7">Table 7</xref>
          </label>
          <caption>
            <title> AUpdate urban/cadastral/notary manager account</title>
          </caption>
        </table-wrap-group>
        <table-wrap-group id="8">
          <label>
            <xref ref-type="table" rid="table8">Table 8</xref>
          </label>
          <caption>
            <title> Add buyer/seller account</title>
          </caption>
        </table-wrap-group>
        <table-wrap id="table9" >
          <label>
            <xref ref-type="table" rid="table9">Table 9</xref>
          </label>
          <caption>
            <title> Find Buyer/Seller account solves: FR13, FR27</title>
          </caption>
          <table>
            <tbody>
              <thead>
                <tr>
                  <th align="center" valign="middle" >Use case Name</th>
                  <th align="center" valign="middle" >Find Buyer/Seller Account</th>
                </tr>
              </thead>
              <tr>
                <td align="center" valign="middle" >Primary actor</td>
                <td align="center" valign="middle" >Urban Service Manager</td>
              </tr>
              <tr>
                <td align="center" valign="middle" >Secondary actor</td>
                <td align="center" valign="middle" >Application System</td>
              </tr>
              <tr>
                <td align="center" valign="middle" >Brief description</td>
                <td align="center" valign="middle" >This use case allows the urban service manager to search for buyer, seller account record in the application system.</td>
              </tr>
              <tr>
                <td align="center" valign="middle" >Pre-condition</td>
                <td align="center" valign="middle" >1. The user is logged into the application system. 2. The application system displays the home page with all services.</td>
              </tr>
              <tr>
                <td align="center" valign="middle" >Normal flows</td>
                <td align="center" valign="middle" >1. The urban service manager clicks on “Manage Buyers Information” button 2. The system returns the “List of buyers” page. With a search bar at the top of the list. 3. The urban service manager enters a keyword (code, first name, last name, e-mail, phone number) and clicks on “Search” button 4. In the case, the urban service manager selects “Manage Sellers Information”, then the system returns the similar information as at step 3. 5. The system extracts the keyword and displays the corresponding record that matches the keyword entered by the urban service manager.</td>
              </tr>
              <tr>
                <td align="center" valign="middle" >Alternate flows</td>
                <td align="center" valign="middle" >1. The urban service manager enters a keyword (code, first name, last name, e-mail, phone number) that does not match any record. 2. The system displays an error message “No record found”. 3. The urban service manager can either try again or cancel the operation by clicking on “Go Back” button. 4. If the urban service manager clicks on “Erase” icon, the system displays back the “List of users” page.</td>
              </tr>
              <tr>
                <td align="center" valign="middle" >Post-condition</td>
                <td align="center" valign="middle" >If the use case was successful, the system displays the record that match the entered keyword. Otherwise, the system displays no record.</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        <table-wrap id="table10" >
          <label>
            <xref ref-type="table" rid="table1">Table 1</xref>0
          </label>
          <caption>
            <title> Delete/deactivate buyer/seller account management</title>
          </caption>
          <table>
            <tbody>
              <thead>
                <tr>
                  <th align="center" valign="middle" >Use case Name</th>
                  <th align="center" valign="middle" >Delete/Deactivate Buyer/Seller Account</th>
                </tr>
              </thead>
              <tr>
                <td align="center" valign="middle" >Primary actor</td>
                <td align="center" valign="middle" >Urban Service Manager</td>
              </tr>
              <tr>
                <td align="center" valign="middle" >Secondary actor</td>
                <td align="center" valign="middle" >Application system, Buyer, Seller</td>
              </tr>
              <tr>
                <td align="center" valign="middle" >Brief description</td>
                <td align="center" valign="middle" >This use case allows the Urban Service Manager to delete/Deactivate a buyer, seller login account to the application system.</td>
              </tr>
              <tr>
                <td align="center" valign="middle" >Pre-condition</td>
                <td align="center" valign="middle" >1. The user is logged into the application system. 2. The application system displays the home page with all services.</td>
              </tr>
              <tr>
                <td align="center" valign="middle" >Normal flows</td>
                <td align="center" valign="middle" >1. The urban service manager clicks on “Manage Buyers Information” button 2. The system returns the “List of buyers” page. 3. The urban service manager clicks on the “Enabled” column button of the record he/she wants to disable. 4. The system returns a conformation message “The buyer has been disabled” 5. The system extracts the corresponding record and delete the associated record in the account data table. 6. In the case, the urban service manager selects “Manage Sellers Information”, then the system returns the similar information as at step 2.</td>
              </tr>
              <tr>
                <td align="center" valign="middle" >Alternate flows</td>
                <td align="center" valign="middle" >1. The system displays an error message “Record not found” 2. If the urban service manager clicks on “Enabled” button, the system displays a message “The buyer has been enabled”.</td>
              </tr>
              <tr>
                <td align="center" valign="middle" >Post-condition</td>
                <td align="center" valign="middle" >If the use case was successful, the urban service manager sends an email warning the user that his/her account has been deleted/deactivated by providing the reason.</td>
              </tr>
            </tbody>
          </table>
        </table-wrap>
        </sec></sec></body>
        <back>
          <ref-list>
            <title>References</title>
            <ref id="scirp.131011-ref1">
              <label>1</label>
              <mixed-citation publication-type="other" xlink:type="simple">Linwa, A.C.B. and Lebi, J.-M.D. (2022) A Generic and Reliable Land Acquisition Protocol on Software Architecture for Sub-Saharan Africa Countries. International Technologist, 18, 1-13.</mixed-citation>
            </ref>
            <ref id="scirp.131011-ref2">
              <label>2</label>
              <mixed-citation publication-type="other" xlink:type="simple">Palmer, D., Fricska, S. and Wehrmann, B. (2009) Pour une Meilleure Gouvernance des Terres. FAO, 74.</mixed-citation>
            </ref>
            <ref id="scirp.131011-ref3">
              <label>3</label>
              <mixed-citation publication-type="other" xlink:type="simple">Enemark, S. (2009) Land Administration Systems-Managing Rights, Restrictions and Responsibilities in Land. Map World Forum, Hyedrabad, 10-13 February 2009, 9.</mixed-citation>
            </ref>
            <ref id="scirp.131011-ref4">
              <label>4</label>
              <mixed-citation publication-type="other" xlink:type="simple">PNUD (2012) Guide pratique pour la prévention et la gestion des conflits liés à la terre et aux ressources naturelles: Terre et Conflits. 96.</mixed-citation>
            </ref>
            <ref id="scirp.131011-ref5">
              <label>5</label>
              <mixed-citation publication-type="other" xlink:type="simple">Williamson, I.P. and Wallace, J. (2007) New Roles of Land Administration. Proceedings, International Workshop on Good Land Administration—Its Role in Economic Development, Ulaanbaatar, Mongolia, http://hdl.handle.net/11343/34936</mixed-citation>
            </ref>
            <ref id="scirp.131011-ref6">
              <label>6</label>
              <mixed-citation publication-type="other" xlink:type="simple">WOCAT (2011) La pratique de la gestion durable des terres. TerrAfrica, Pages 243, La pratique de la gestion durable des terres (fao.org).</mixed-citation>
            </ref>
            <ref id="scirp.131011-ref7">
              <label>7</label>
              <mixed-citation publication-type="other" xlink:type="simple">De Zeeuw, K., Benn, T., Unger, E.-M., Bennett, R. and Teo, C.H. (2020) United Nations-Framework for Effective Land Administration (FELA). 2020 Annual World Bank Conference on Land and Poverty, Washington DC, 16-20 March 2020, 30.</mixed-citation>
            </ref>
            <ref id="scirp.131011-ref8">
              <label>8</label>
              <mixed-citation publication-type="other" xlink:type="simple">Hurni, H. (1997) Concepts of sustainable land management. ITC Journal, 3/4, 210-215.</mixed-citation>
            </ref>
            <ref id="scirp.131011-ref9">
              <label>9</label>
              <mixed-citation publication-type="other" xlink:type="simple">Traoré, H. (2023) A Generic and Reliable Land Acquisition Application for Sub-Saharan Countries. Capstone Thesis, International University of Grand-Bassam, Grand-Bassam.</mixed-citation>
            </ref>
            <ref id="scirp.131011-ref10">
              <label>10</label>
              <mixed-citation publication-type="other" xlink:type="simple">Liang, Y.S., Sun, W.B., Diao, H.T. and Li, Y. (2010) The Design and Development of the Land Management System in Dingzhuang Town Based on Spatial Data. 4th Conference on Computer and Computing Technologies in Agriculture (CCTA), Nanchang, October 2010, 57-65. https://doi.org/10.1007/978-3-642-18354-6_9</mixed-citation>
            </ref>
            <ref id="scirp.131011-ref11">
              <label>11</label>
              <mixed-citation publication-type="other" xlink:type="simple">De Maria, M. (2019) Understanding Land in the Context of Large-Scale Land Acquisitions: A Brief History of Land in Economics. Land, 8, 15. https://doi.org/10.3390/land8010015</mixed-citation>
            </ref>
            <ref id="scirp.131011-ref12">
              <label>12</label>
              <mixed-citation publication-type="other" xlink:type="simple">Intosai, W. (2012) Land Use and Land Management Practices in Environmental. INTOSAI Working Group on Environmental Auditing (WGEA), 81.</mixed-citation>
            </ref>
            <ref id="scirp.131011-ref13">
              <label>13</label>
              <mixed-citation publication-type="book" xlink:type="simple">Bürgi, M., Hersperger, A.M., Hall, M., Southgate, E.W.B. and Schneeberger, N. (2007) Using the Past to Understand the Present Land Use and Land Cover. In: Kienast, F., Wildi, O. and Ghosh, S., Eds., A Changing World, Springer, Dordrecht, 133-144. https://doi.org/10.1007/978-1-4020-4436-6_9</mixed-citation>
            </ref>
            <ref id="scirp.131011-ref14">
              <label>14</label>
              <mixed-citation publication-type="other" xlink:type="simple">Ziadat, F. (2017) Land Resource Planning for Sustainable Land Management. FAO: Land and Water Division Working Papers, 70.</mixed-citation>
            </ref>
            <ref id="scirp.131011-ref15">
              <label>15</label>
              <mixed-citation publication-type="other" xlink:type="simple">Berisso, Z.A. and de Vries, W.T. (2010) Exploring Characteristics of GIS Adoption Decisions and Type of Induced Changes in Developing Countries: The Case of Ethiopia. The Electronic Journal of Information Systems in Developing Countries, 40, 1-16. https://doi.org/10.1002/j.1681-4835.2010.tb00284.x</mixed-citation>
            </ref>
            <ref id="scirp.131011-ref16">
              <label>16</label>
              <mixed-citation publication-type="other" xlink:type="simple">Correia, Z.X., Moore, A.B. and Goodwin, D.P. (2021) Accessibility of Land Data and Information Integration in Recently-Independent Countries: Timor-Leste Case Study. Papers in Regional Science, 100, 203-225. https://doi.org/10.1111/pirs.12560</mixed-citation>
            </ref>
            <ref id="scirp.131011-ref17">
              <label>17</label>
              <mixed-citation publication-type="other" xlink:type="simple">Karikari, I., Stillwell, J. and Carver, S. (2003) Land Administration and GIS: The Case of Ghana. Progress in Development Studies, 3, 223-242. https://doi.org/10.1191/1464993403ps050ra</mixed-citation>
            </ref>
            <ref id="scirp.131011-ref18">
              <label>18</label>
              <mixed-citation publication-type="other" xlink:type="simple">Biraro, M. (2014) Land Information Updating: Assessment and Options for Rwanda. University of Twente, Enschede.</mixed-citation>
            </ref>
            <ref id="scirp.131011-ref19">
              <label>19</label>
              <mixed-citation publication-type="other" xlink:type="simple">Mwangi Gideon, W. (2011) Development of Integrated Land Information Management System in Kenya. Master Sciences Thesis, University of Nairobi, Nairobi.</mixed-citation>
            </ref>
            <ref id="scirp.131011-ref20">
              <label>20</label>
              <mixed-citation publication-type="other" xlink:type="simple">Siriba, D.N. and Dalyot, S. (2017) Adoption of Volunteered Geographic Information into the Formal Land Administration System in Kenya. Land Use Policy, 63, 279-287. https://doi.org/10.1016/j.landusepol.2017.01.036</mixed-citation>
            </ref>
            <ref id="scirp.131011-ref21">
              <label>21</label>
              <mixed-citation publication-type="other" xlink:type="simple">Gluszak, M. (2008) Land Acquisition in Development Projects: Investment Value and Risks. SRE-Discussion Papers 2008/06, Vienna University of Economics and Business, Vienna.</mixed-citation>
            </ref>
            <ref id="scirp.131011-ref22">
              <label>22</label>
              <mixed-citation publication-type="other" xlink:type="simple">Yaw Adiaba, S. (2014) A Framework for Land Information Management in Ghana. PhD Thesis, University of Wolverhampton, Wolverhampton.https://wlv.openrepository.com/bitstream/handle/2436/332138/THESIS0920118doc.pdf?sequence=1&amp;isAllowed=y</mixed-citation>
            </ref>
            <ref id="scirp.131011-ref23">
              <label>23</label>
              <mixed-citation publication-type="other" xlink:type="simple">Davis, F.D. (1989) Perceived Usefulness, Perceived Ease of Use, and User Acceptance of Information Technology. MIS Quarterly, 13, 319-340. https://doi.org/10.2307/249008</mixed-citation>
            </ref>
            <ref id="scirp.131011-ref24">
              <label>24</label>
              <mixed-citation publication-type="other" xlink:type="simple">Zeng, Z. and Cleon, C.B. (2018) Factors Affecting the Adoption of a Land Information System: An Empirical Analysis in Liberia. Land Use Policy, 73, 353-362. https://doi.org/10.1016/j.landusepol.2017.12.034</mixed-citation>
            </ref>
            <ref id="scirp.131011-ref25">
              <label>25</label>
              <mixed-citation publication-type="other" xlink:type="simple">Ouattara, A. and Gouvernement de C&amp;ocirc;te d’Ivoire (2013) Les Règles d’Acquisition des Terrains Urbains.</mixed-citation>
            </ref>
            <ref id="scirp.131011-ref26">
              <label>26</label>
              <mixed-citation publication-type="other" xlink:type="simple">Nguiffo, S. and Seigneret, A. (2021) La réforme foncière au Cameroun: une vision cohérente proposée par la société civile. IIED, London. https://pubs.iied.org/20126IIED</mixed-citation>
            </ref>
            <ref id="scirp.131011-ref27">
              <label>27</label>
              <mixed-citation publication-type="other" xlink:type="simple">Yang, P. (1er Ministre) (2014) Texte régulation la gestion de la terre. https://extwprlegs1.fao.org/docs/pdf/Cmr176509.pdf</mixed-citation>
            </ref>
            <ref id="scirp.131011-ref28">
              <label>28</label>
              <mixed-citation publication-type="other" xlink:type="simple">Direction des Collectivités Locales (2012) Manuel des procédures Foncières des Communautés Rurales. Ministère de l’Aménagement du Territoire et des Collectivités Locales du Sénégal, 81.</mixed-citation>
            </ref>
          </ref-list>
        </back>
</article>