Volume 18, Issue 6 (2-2025)
payavard 2025, 18(6): 546-558 |
Back to browse issues page
Ethics code: IR.TBZMED.REC.1398.463
Download citation:
BibTeX | RIS | EndNote | Medlars | ProCite | Reference Manager | RefWorks
Send citation to:
BibTeX | RIS | EndNote | Medlars | ProCite | Reference Manager | RefWorks
Send citation to:
Abdekhoda M, Samad Soltani T, Ghaderi Nansa L. Requirement Analysis and Design of an Alumni Relationship Management Solution for Medical Universities. payavard 2025; 18 (6) :546-558
URL: http://payavard.tums.ac.ir/article-1-7679-en.html
URL: http://payavard.tums.ac.ir/article-1-7679-en.html
1- Professor, Medical Philosophy and History Research Center, Tabriz University of Medical Sciences, Tabriz, Iran; Department of Medical Library and Information Sciences, Tabriz University of Medical Sciences, Tabriz, Iran , Abdekhodam@tbzmed.ac.ir
2- Associate Professor, Department of Health Information Technology, School of Health Management and Medical Informatics, Tabriz University of Medical Sciences, Tabriz, Iran
3- Assistance Professor, Department of Health Information Technology, School of Health Management and Medical Informatics, Tabriz University of Medical Sciences, Tabriz, Iran
2- Associate Professor, Department of Health Information Technology, School of Health Management and Medical Informatics, Tabriz University of Medical Sciences, Tabriz, Iran
3- Assistance Professor, Department of Health Information Technology, School of Health Management and Medical Informatics, Tabriz University of Medical Sciences, Tabriz, Iran
Abstract: (1336 Views)
Background and Aim: Establishing dynamic relationships between graduates and current students should be a high priority for universities striving to progress in the rapidly changing and competitive market of third-generation universities. Due to the lack of effective communication with graduates in Iranian universities and the role of these systems in the technology ecosystem, the aim of this study is to analyze the needs of a graduate alumni management system and propose a conceptual model.
Materials and Methods: The research consisted of two main phases: needs analysis and process and software design. During the requirements engineering, as described in systems analysis and design references, a quick review was first conducted in selected databases regarding the capabilities and use cases of existing studies and the proposed features of innovative graduate alumni management systems. The extracted items from the rapid review were presented in a checklist. Then, functional requirements were extracted through interviews with 10 experts from the university’s educational deputy and faculty, using a two-round Delphi method. In the next stage, work processes were observed, and process owners were interviewed. UML diagrams were used to achieve a suitable description of a good system.
Results: In this study, the requirements were categorized into two main groups, comprising 37 functional and non-functional needs. The functional category included three significant subcategories: basic needs, social needs, and innovation needs. Basic needs encompassed the essentials required for the system’s fundamental operation. Social needs referred to the system’s ability to facilitate user interactions, while innovation needs involved new and creative features that could be added to the system. A software engineering specialist analyzed these functional needs and translated them into system use cases to be effectively incorporated into the system’s development.
Conclusion: The proposed conceptual model of the graduate alumni management system was analyzed and modeled based on user-centered requirements engineering. The proposed model provides a practical document for the effective implementation of a communication mechanism and active interaction between graduates, as well as current students, faculty members, and other staff in an innovation and entrepreneurship ecosystem.
Materials and Methods: The research consisted of two main phases: needs analysis and process and software design. During the requirements engineering, as described in systems analysis and design references, a quick review was first conducted in selected databases regarding the capabilities and use cases of existing studies and the proposed features of innovative graduate alumni management systems. The extracted items from the rapid review were presented in a checklist. Then, functional requirements were extracted through interviews with 10 experts from the university’s educational deputy and faculty, using a two-round Delphi method. In the next stage, work processes were observed, and process owners were interviewed. UML diagrams were used to achieve a suitable description of a good system.
Results: In this study, the requirements were categorized into two main groups, comprising 37 functional and non-functional needs. The functional category included three significant subcategories: basic needs, social needs, and innovation needs. Basic needs encompassed the essentials required for the system’s fundamental operation. Social needs referred to the system’s ability to facilitate user interactions, while innovation needs involved new and creative features that could be added to the system. A software engineering specialist analyzed these functional needs and translated them into system use cases to be effectively incorporated into the system’s development.
Conclusion: The proposed conceptual model of the graduate alumni management system was analyzed and modeled based on user-centered requirements engineering. The proposed model provides a practical document for the effective implementation of a communication mechanism and active interaction between graduates, as well as current students, faculty members, and other staff in an innovation and entrepreneurship ecosystem.
Keywords: Alumni, Relationship Management System, Functional Needs, Conceptual Model, System, Universities
Type of Study: Original Research |
Subject:
Medical Library & Information Sciences
Send email to the article author
| Rights and permissions | |
 |
This work is licensed under a Creative Commons Attribution-NonCommercial 4.0 International License. |
