Student Request System Prototype Using Low-Code Development Platform
Student request system is an online information system that a department allows students to ask officers to do something, which it is like a service center or help desk. However, many universities have numerous issues for both faculty officers and students. For instance, faculty officers have to cop...
Saved in:
| Main Author: | |
|---|---|
| Other Authors: | |
| Format: | Conference or Workshop Item |
| Published: |
2023
|
| Subjects: | |
| Online Access: | https://repository.li.mahidol.ac.th/handle/123456789/84320 |
| Tags: |
Add Tag
No Tags, Be the first to tag this record!
|
| Institution: | Mahidol University |
| Summary: | Student request system is an online information system that a department allows students to ask officers to do something, which it is like a service center or help desk. However, many universities have numerous issues for both faculty officers and students. For instance, faculty officers have to cope with document management with many manual tasks. Also, students need to deal with their request submission manually, and they may make a mistake from that. Besides, they cannot track their submitted request status. To resolve those issues, we proposed an online student request system prototype to make most processes to be more automated by making use of low-code development platforms including Microsoft 365 Apps, Microsoft Power Apps as an interface dashboard, Power Automate as workflow control, and Share-Point as data storage. As a result, with our proposed system, students will have less procedures for request submission, and the system could prevent some mistakes that might happen during submission, such as input validation in online request forms. In addition, they can track their request status. On the other hands, our proposed system could reduce workload and improve data management for faculty staff as well. Finally, our system was tested for accuracy and satisfaction with about 20 users including the faculty staff and students. We evaluated our prototype for two aspects: function accuracy and user satisfaction. For the testing result, we found that all functions worked very well, and we got high satisfaction score (4.44 of 5 in average) from all testers. |
|---|