In the January-February-March 2021 quarter, out of the total internet user population, 88.5% accessed it through mobile phones or smartphones, 16.7% through laptops, and the rest through other internet-connected devices [2]. When compared to the same quarter in 2020, there is a 0.6 percentage point increase in internet access via mobile phones. This figure is expected to rise further in 2022. The usefulness of mobile phones lies in applications. There are various advantages to using mobile applications, particularly in the educational perspective. For example, manual attendance registration by teachers can be time-consuming and prone to errors [3]. It can also consume teachers' time when calculating averages. The use of a mobile attendance system eliminates the drawbacks of the manual system.
The primary motivation for this research is to optimize the time spent by teachers in taking attendance, especially when dealing with a large number of students. Additionally, the goal is to gain experience in developing mobile applications as part of professional growth, utilizing methods and new technologies such as database management, persistence, authentication, and storage with Firebase, and the BrainShop Machine Learning kit [4]. The aim is to create a wellorganized, robust, and consistent application capable of meeting all the basic needs for its launch, following all stages of the XP methodology.
This paper is organized as follows. Section II provides a general overview of various previous studies on methods implemented for student attendance systems using mobile applications. Section III details the application implementation process through the XP methodology. In Sections IV and V, the results and discussion are outlined after testing the application with 100 students from the Faculty of Physical and Formal Sciences and Engineering at the Universidad Católica de Santa María during one month in the odd academic semester 2022-I. Finally, Section VI presents the research conclusions.
In this section, we conduct a systematic review of related works in the development of mobile applications focused on student attendance tracking, with a focus on time optimization and resource use in this process. We also explore those that use cloud-based technologies and their implementation through the use of the XP methodology.
In [5], an automated solution is presented, where a mobile application based on JAVA was developed. It wirelessly connected to a central Database created using MySQL, tasked with registering attendance information. The system was implemented in a university to record student data, absence and presence times, and accumulated attendance per month, resulting in effective and efficient system use. Similarly, in [6], an application was developed for Android and iOS devices to register student attendance as an alternative to manual methods. The proposal includes an application dedicated to teachers and students, displaying information such as the courses taught by teachers and the courses in which students are enrolled. Attendance data is synchronized with the Moodle platform, reflecting this information on the virtual platform. Tools used for development include MariaDB as the database manager and Web Services for application synchronization with the Moodle and institutional databases. The implementation is justified through a survey where 100% of teachers would support the use of an application for attendance and rated its use and synchronization with the virtual platform at 4.8.
Block diagram of the attendance system presented in [5] On the other hand, [7] presents a study where information from 367 students was collected to measure attendance in classes, online learning activities, and performance in online formative assessments. This study applied learning analysis methods to measure attendance, online learning activities, and performance in online formative assessments. The research results contribute to understanding the impact of class attendance on course academic performance and the interaction of participation factors in online learning in the context of technology-enhanced courses.
In the research conducted by [8], a proposed solution to the attendance control problem is presented, consisting of the development of a hybrid Android application prototype. This was achieved by employing open-source technologies such as the Ionic framework and the face-api.js library of JavaScript. The proposal is oriented towards efficient and agile monitoring of student attendance within the classroom, utilizing facial recognition as a key element for faster and more secure control. 92.8% of teachers show satisfaction with the application, feeling more secure with the use of facial recognition for verifying student attendance.
Concerning the use of the Extreme Programming (XP) methodology, [9] developed a mobile application for managing attendance and evaluation information for university students. For this, development environments such as SQLite for database management, Android Studio, and the Extreme Programming methodology were used, allowing acceptance and compliance with the proposal and meeting the requirements demanded by the client. Among the obtained results is the high availability and integrity of information regarding attendance and evaluations. Furthermore, the use of the XP methodology allowed constant feedback with the client and, consequently, continuous improvement of the application.
The data analysis proposed in [10] is used to analyze various skills through the collection of unstructured data to identify trends in job positions in the oil and gas industry. Although the context of the case study is different from that presented in this document, it can be proven that data analysis allows a better understanding of the skills and performance of a group of individuals, identifying them on a scale of 1 to 10 in job recurrence, which is sought to be addressed with attendance analysis and academic performance.
In this context, [11] demonstrated that the use of the XP methodology guarantees the development of applications from small to medium scale. Compared to processes and tools, XP focuses on the aggressive development of mobile applications and allows an immediate response to changes that arise during the development process. Therefore, its use to develop a mobile application for student learning in various schools proves to be efficient and effective.
For predictions and data analysis to be accurate, sensors or tools that collect real-time data are necessary. An example of this is presented in the research [12], where Google tools (Firebase) are used for the immediate collection and ordering of data for the detection of cardiovascular diseases. This demonstrates great effectiveness in recognition and ease of handling a large amount of data. In this context, in the research conducted by [13] on the use of frameworks in the development of mobile applications, a comprehensive investigation is presented on the needs and characteristics that a mobile application must meet. To discover these characteristics, a systematic study mapping, consultation with experts, implementation in projects with agile methodologies, and testing in a university environment were used. The results showed improvement in development and a useful guide to cover all needs or aspects of the mobile application, improve development times, and can also be used as teaching material.
Finally, in the research proposed by [14], an application was developed to monitor the health status of patients with heart problems. Considering that data must be updated in real-time, the researchers concluded that Firebase was the most suitable platform for handling data in the cloud. As mentioned earlier, this tool provides various services such as Analytics that provide data and charts of user interactions. As a final point, the authors highlight the accuracy of the application in offering advice and predictions in sensitive health areas.
In this regard, in relation to the use of NoSQL databases (non-relational databases), [15] presents a method based on computer vision to automate the process of reading water and electricity meters through a mobile application, storing photos and data of readings in a NoSQL database. Through Firebase Storage, it allows a dealer to store and process these readings with the aim of conducting predictive analysis in the future for water or electricity resource management. This method was patented, generating viable results in the meter reading market in Brazil. On the other hand, in [16], they propose a personal and decentralized cloud-based data model to manage health data in schoolchildren using the real-time NoSQL database provided by the Firebase platform. Through this service, a school's health information system can have total control over the administration of sensitive data such as the student's school number, name, temperature test time, temperature data, and the test machine number. This model was tested and applied, fulfilling its objective, and provides schoolchildren with more active control over the health information data of their personal status.
Considering the research conducted, for the development of the proposal, Firebase will be used as the Database manager, as it is a fast and efficient technology for handling a large amount of unstructured data [17], Android as the development platform, and the XP methodology to manage the development of the proposal.
In order to evaluate the satisfaction of teachers and students regarding the use of an application for attendance marking, data will be collected from students of the Professional School of Systems Engineering at the Universidad Católica de Santa María, whose ages range from 19 to 25 years.
The XP methodology consists of the following phases [18]: Planning, Design, Coding, Testing, and Release. As shown in Figure 2.
According to [20], it is important to select the priority functions that will be developed first so that the application can be implemented gradually and meet the main needs of users. In the operation of the application developed in [20], two types of data (Primary and Secondary data) are collected. In this research, primary and secondary data are related to student attendance (see Table 1). In this context, the first thing defined in this phase was the user stories, which in other development methodologies are known as requirements, to later prioritize them. Some of the identified user stories are shown below [21]. The application will allow students to register attendance by selecting the subject they need to mark attendance for through a card on the main screen of the application. Observations: Only courses that correspond to marking attendance will be enabled. That is, if the allowed time for attendance registration is met (±5 minutes) at entry and exit times. Actual Points: 2 Description: The application will allow downloading a spreadsheet-format file that will contain student attendance (in CSV format) when selecting a specific subject. Observations: Only the attendance of those students who marked their attendance within the specified time frame (±5 minutes) of entry and exit will be counted.
In this phase, all the mockups of the application were developed with which end-users would be interacting. While other methodologies usually develop deliverables such as sequence diagrams, in this case, the client-server model was chosen [21]. Below are the main interfaces of the mobile application.
• Students Ø Screen for user login. Ø Screen to view the list of student courses and the attendances they need to mark at the scheduled time. Ø Screen to mark the entry and exit attendance of students.
Teachers Ø Screen for user login. Ø Screen to view the list of courses they teach. Ø Screen to download the attendance list of a specific course.
In this phase, the application's functionalities were coded using the Model View ViewModel (MVVM) design pattern. MVVM allows the implementation of more robust Android applications and aligns well with the chosen development methodology [22]. The structure can be observed as follows. Where the model layer translates all the data and delivers it to the model, the ViewModel layer connects to the database or external APIs, and the view layer presents the data, which can be invoked using commands.
As mentioned earlier, Firebase was used as the database manager due to its advantages, such as cloud storage and rapid scaling, as well as its data analytics addon for generating reports on application demand by users.
In Figure 5, the implemented Firebase database can be visualized. It shows the code of the courses and their corresponding fields, such as classroom, day, entry time, exit time, course name, and teacher. In Cloud Firestore, the storage unit is the document, which is a record using few resources and contains fields with assigned values [23], such as the "email" field. Collections store documents, and in Illustration 5, there is a collection called "attendance," which contains a set of documents that can, in turn, store collections, such as the "courses" collection storing the courses each student is enrolled in. Figure 6 shows the collection of courses, which stores the courses in which the student is enrolled. Each subject has a unique identifier, the subject code.
The following details the data model represented in the student and their corresponding courses' data dictionary.
The attributes handling the main functionalities of the mobile application were collected from students and their corresponding courses in the 4th year of the Systems Engineering professional career (odd semester 2022-I) at the Faculty of Physical and Formal Sciences and Engineering of UCSM, and are shown in Table 5 and 6, respectively.
To generate automatic responses to user questions, such as obtaining instructions on how to use the application or how to mark attendance [24], the BrainShop.ai Machine Learning kit was used. It can respond to user questions based on a knowledge base (a set of previously entered responses in the model) and generate automatic responses for users [25]. The knowledge base and its training are shown below.
The following are the main screens of the resulting application based on the user stories from the planning phase (Phase 01 of the XP methodology). It is important to note that these results are after the testing phase (Phase 04 of the XP methodology).
The following interfaces illustrate how access to the application is achieved, featuring a welcome screen and another where entry is made based on roles (Student -Teacher). The following screens demonstrate how attendance control is carried out by teachers, following these steps:
• Log in to the application with the role of "Teacher" (only accesses identified with this role are recognized). • Navigate to the corresponding course and click on "DOWNLOAD ATTENDANCE CONTROL," which will generate and download a CSV spreadsheet for teachers. Illustration 13 shows an example of attendance control performed by a teacher. The record indicates the date, entry time, and exit time registered by the student. The record corresponds to the "Mobile Technologies -Practice Group 1" course, scheduled for "Tuesday 15:00 -17:00."
When using the XP methodology, it is recommended to use unit tests and acceptance tests [26]. Unit tests verify the code developed by the programming team, while acceptance tests verify if the final product meets the expectations proposed in the planning phase. In our project, each module was tested to ensure that appropriate values were entered, it led the client to correct activities, and maintained integrity and security of the data provided by students and teachers. Finally, customer satisfaction was verified through surveys and scheduled presentations of the final product to determine if all user requirements and expectations were met.
For the application launch, a survey was developed. The survey includes various questions to validate and verify user satisfaction with the use of the application. The criteria considered for the survey development are shown in Table 8. Communication with application users about their comfort level with application navigation. 5
Application Ease of Use Communication with application users about their initial experiences using the application. 6
Application Learning Ease
Communication with application users about the time it takes to adapt to it. 7
Intuitive Application Users are asked to rate the application based on the ease it provides for performing all actions within it. 8
Recommendation of Application Use
Communication with users about the likelihood of recommending the application. 9
Satisfaction Level with Application Use
A form with different areas of the application is provided for users to measure the satisfaction level for each view and a general rating.
For the application launch, the following steps were followed:
• Generate the APK of the application.
• Publish the APK on the website: https://coachup.site/ • Evaluate the results obtained through the survey.
This launch method was chosen for its flexibility and ease, as the application is still in its validation stage.
Information was collected from 100 students and teachers in the 4th year of the Systems Engineering professional career at the Universidad Católica de Santa María for 1 month in the odd academic semester of 2022-I. The results of the conducted surveys are presented below.
The chart shows that 80% of respondents are students, and 20% are teachers. Likewise, a scale was made to assess the satisfaction level of users with the mobile application. Table 9 shows scales, and the chart below shows the responses obtained by students. Among the total respondents, 18 (18%) consider their interaction with the application to be good, 51 (51%) consider it very good, 28 (28%) consider it excellent, and 2 (2%) consider it regular. The latter cases may be due to a lack of internet connection or inappropriate use of the application by users.
Additionally, given that one of the long-term objectives of this research is for the application to be used in all schools of the Universidad Católica de Santa María, a question was asked about whether users would recommend the use of the application to others. The responses to this question are shown below. The chart shows that 92.9% of users would highly recommend the use of the application, while the remaining 7.1% would not recommend it. These cases were evaluated in the testing phase, as many of these users may not have constant internet access or may not use the application appropriately.
The results demonstrate that users (teachers and students at UCSM) feel comfortable using the application to register their attendance, indicating ease of use.
Additionally, acceptance criteria were developed to verify the acceptance levels of the "ASYS" mobile application [8], achieving the following compliance levels for each criterion: Compliance Level (%) Functionality The system meets the necessary functionalities for the correct process in attendance registration and control. 100%
The system works in an integrated manner with the database manager for subsequent functionalities implemented in the application.
The results obtained in section IV indicate the degree of satisfaction that both teachers and students have with the use of the application.
The "ASYS" application meets the registration and attendance control of students.
The table indicates that based on the acceptance criteria, 100% compliance was achieved in the functionality and operability criteria, indicating complete fulfillment. In contrast, in the satisfaction and acceptance criteria, 98% and 92.9% were obtained, respectively, which, according to [8], represents a significant percentage compared to the resulting percentage of the difference (2% and 7.1%, respectively).
• It is concluded that the XP methodology, after executing its first three phases, ensures the quality of the mobile application. It has the advantage of being more customeroriented than development process-oriented, unlike other traditional methodologies that impose a disciplined development plan. • The use of tools and techniques oriented in the XP methodology contributed to the identification of functional and non-functional requirements, which helped in developing an application oriented to compliance with specified guidelines and requirements. • The use of the XP methodology contributes to the development of a mobile application for attendance control by enabling constant communication and feedback with the client/user. It also provides quick responses to changes suggested by the client, thanks to the flexibility of the tools and techniques found in this methodology. • The execution of the mobile application demonstrated positive results in the correct implementation of Firebase services (Cloud Firestore and Firebase Authentication) in the access and attendance marking modules. • The use of the application facilitated attendance registration for students and teachers, allowing the generation of a record with the attendance of each student. • Machine Learning techniques were employed to generate automatic responses to user questions. This functionality of the application proved to be useful when users do not know how to mark their attendance or have other questions related to the use of the application.
As future work, the use of other ML techniques such as image recognition and geolocation for student attendance registration is proposed.
Improvement in control is also suggested. This includes the ability for teachers to download files that allow them to select which types of data they want to retrieve from the database, such as dates or student information. Additionally, enhancing the visualization of control data is proposed, as currently, it is only downloaded in a date and time format when the student registered their attendance (Entry/Exit).
Furthermore, scaling the database to a relational database schema is considered, which can work hand in hand with the UCSM database.
Improving the security of the application is suggested, considering that data is an important asset for an organization. Enhancing application security to a much higher level is part of the future plans.
Implementing the application for iOS operating systems is also planned.