Developing Web Application For The Student Affairs Department Using The ASP.Net MVC Architecture

2023

Full text Open access: Gold Metadata (CSL-JSON)
DOI 10.47526/2023-3/2524-0080.06
Data confidence 70 medium
How this score is calculated

It is built from checkable properties of the record itself: whether the article has a DOI, how many independent sources confirmed its data, whether the required fields are filled in, and how recent the latest confirmation is. Disagreement between sources and a missing identifier lower it. A value of 80 or above means the record was published without further checking; 60 to 79 means it is published at reduced confidence, with a manual check advisable. A record verified by an editor by hand is never pushed below 90 by a recalculation. This scores our data about the article, not the article itself.

Abstract

The developments in internet technology have led many institutions to renew themselves in various fields, and one of them is educational institutions. Especially for the student affairs departments of universities, having an effective web application has become important with the developing technology. All universities that prioritize development should have a strong and interactive student affairs web application that will not only promote the university but also facilitate the implementation of related student affairs from a design and software perspective. It has been found that the error rate in student affairs significantly decreases with web applications, and the unit performance in terms of access and service to students also significantly increases. In this study, the Student Affairs Department web application was developed based on ASP.Net MVC (Model View Controller) technology. ASP.Net MVC technology enables web applications to be more secure, easier to design, and code. The model-view-controller system has provided convenience in the organization of both the front-end and back-end structures. Microsoft SQL was used as the database, and the Code First approach was preferred as the database method. The Language Integrated Query component was used in the back-end structure for communication with the database. Overall, this design allows for easy updates, optimization, and dynamization of the code, as well as removing repetitions from the code.