<?xml version="1.0" encoding="UTF-8"?>
<record
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd"
    xmlns="http://www.loc.gov/MARC21/slim">

  <leader>04323nam a2200337 i 4500</leader>
  <controlfield tag="003">MY-KuUP</controlfield>
  <controlfield tag="005">20260106111305.0</controlfield>
  <controlfield tag="006">a||||fr|||| 000 0 </controlfield>
  <controlfield tag="007">ta</controlfield>
  <controlfield tag="008">240729t20242024my a|||fr|||| 000 0 eng d</controlfield>
  <datafield tag="020" ind1=" " ind2=" ">
    <subfield code="a">THE0009899 (Local)</subfield>
    <subfield code="q">Hardback</subfield>
  </datafield>
  <datafield tag="040" ind1=" " ind2=" ">
    <subfield code="a">UMPSA</subfield>
    <subfield code="b">eng</subfield>
    <subfield code="c">UMP</subfield>
    <subfield code="e">rda</subfield>
  </datafield>
  <datafield tag="090" ind1=" " ind2=" ">
    <subfield code="a">FKOM .D84 2024 r Thesis</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Duha Awad Hamed Elneel Elmubarak,</subfield>
    <subfield code="e">author.</subfield>
  </datafield>
  <datafield tag="245" ind1="1" ind2="0">
    <subfield code="a">Stakeholder identification model  for synchronous and asynchronous  e-learning system /</subfield>
    <subfield code="c">Duha Awad Hamed Elneel Elmubarak</subfield>
  </datafield>
  <datafield tag="264" ind1=" " ind2="1">
    <subfield code="a">Kuantan, Pahang :</subfield>
    <subfield code="b">UMPSA,</subfield>
    <subfield code="c">2024</subfield>
  </datafield>
  <datafield tag="264" ind1=" " ind2="4">
    <subfield code="c">&#xA9; 2024</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">xiv, 169 pages :</subfield>
    <subfield code="b">illustrations (some color) ;</subfield>
    <subfield code="c">30 cm. +</subfield>
    <subfield code="e">1 CD-ROM</subfield>
  </datafield>
  <datafield tag="336" ind1=" " ind2=" ">
    <subfield code="2">rdacontent</subfield>
    <subfield code="a">text</subfield>
  </datafield>
  <datafield tag="337" ind1=" " ind2=" ">
    <subfield code="2">rdamedia</subfield>
    <subfield code="a">unmediated</subfield>
  </datafield>
  <datafield tag="338" ind1=" " ind2=" ">
    <subfield code="2">rdacarrier</subfield>
    <subfield code="a">volume</subfield>
  </datafield>
  <datafield tag="347" ind1=" " ind2=" ">
    <subfield code="2">rda</subfield>
    <subfield code="a">text file</subfield>
    <subfield code="b">PDF</subfield>
  </datafield>
  <datafield tag="500" ind1=" " ind2=" ">
    <subfield code="a">Faculty of Computing</subfield>
  </datafield>
  <datafield tag="502" ind1=" " ind2=" ">
    <subfield code="a">Thesis (Doctor of Philosophy) -- Universiti Malaysia Pahang -- 2025</subfield>
  </datafield>
  <datafield tag="504" ind1=" " ind2=" ">
    <subfield code="a">Includes bibliographical references</subfield>
  </datafield>
  <datafield tag="520" ind1="3" ind2=" ">
    <subfield code="a">The system's effective development depends mainly on successfully defining the  requirements. The right requirements rely on accurate stakeholder identification (SI) from  early stages of the system lifecycle. SI is an essential part of the requirements engineering  process and it is a challenging and critical aspect that requires a delicate study to  categorize and classify the right project stakeholders. The e-learning system is considered  a significant platform that has diverse stakeholders which need to be identified. The high  growth of e-learning systems in the last years and the sudden shift from classroom to  online education especially during the covid-19 pandemic made this system become  indispensable. Consequently, this research focuses on identifying the key stakeholders of  the e-learning system based on communication modes (Synchronous, Asynchronous).  The problems that arise sequentially after the launch of the e-learning system and threaten  the continuity of the system are one of the motivators of this research, in addition to the  different types of e-learning modes and diversity e-learning organizations that produce  different unknown stakeholders need to be identified. On the other hand, the limitations  of the existing methods of SI specially in the e-learning system domain and the shortage  of the existing applied processes for requirements elicitation to cooperate with the recent  technologies also stimulated the work of this research. Subsequently, stakeholder  identification model for e-learning system (SIMe) is proposed in order to improve the elearning system requirements engineering process and thus build a sustainable and  continuous system. The SIMe has been constructed based on the e-learning system modes (Synchronous and Asynchronous) platform that helps to determine various activities and  roles accordingly, different types of stakeholders can be identified and categorized.  Moreover, The SIMe used the power/interest grid for more stakeholder identification and  categorization in addition to an Oracle application for the implementation. Three  operative methods are used to evaluate the efficiency of the proposed SIMe. First,  implementing the SIMe to a selected e-learning system, then comparing the SIMe with  the existing SI methodologies in terms of the performance and the fulfilment, and finally  presenting the proposed model to specialists to evaluate its actual performance. The  experiment declares that SIMe can generate the required stakeholder lists with accurate  result which is better than other alternative SI methods. On the other hand, the findings  approve that the SIMe can generate the key stakeholder report, respectively with clear  classification and is more effective compared with other existing techniques.  Additionally, the results of the experts&#x2019; opinions review indicate that they were satisfied  with the SIMe contribution in e-learning system sustainability. In future work, new  prospects can be added for more improvement such as personal considerations,  organizational considerations, emerging technologies and some regulations</subfield>
  </datafield>
  <datafield tag="610" ind1="2" ind2="0">
    <subfield code="a">Faculty of Computing</subfield>
    <subfield code="x">Dissertations</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
    <subfield code="a">Universities and colleges</subfield>
    <subfield code="x">Dissertations</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
    <subfield code="a">Theses</subfield>
    <subfield code="x">Dissertations</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="2">lcc</subfield>
    <subfield code="c">THESIS</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="2">lcc</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">1</subfield>
    <subfield code="a">20000</subfield>
    <subfield code="b">20000</subfield>
    <subfield code="d">2024-07-29</subfield>
    <subfield code="l">0</subfield>
    <subfield code="o">FKOM .D84 2024 r Thesis</subfield>
    <subfield code="p">T000003207</subfield>
    <subfield code="r">2024-07-29 00:00:00</subfield>
    <subfield code="t">1</subfield>
    <subfield code="w">2024-07-29</subfield>
    <subfield code="y">THESIS</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="2">lcc</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">0</subfield>
    <subfield code="a">20000</subfield>
    <subfield code="b">20000</subfield>
    <subfield code="d">2024-07-29</subfield>
    <subfield code="l">0</subfield>
    <subfield code="o">CD13606</subfield>
    <subfield code="p">T000003208</subfield>
    <subfield code="r">2024-07-29 00:00:00</subfield>
    <subfield code="t">1</subfield>
    <subfield code="w">2024-07-29</subfield>
    <subfield code="y">THESIS</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">101010</subfield>
    <subfield code="d">101016</subfield>
  </datafield>
</record>
