Article Per Year (5 Year)
p-Index From 2021 - 2026
0.23
P-Index
This Author published in this journals
All Journal Jatilima : Jurnal Multimedia Dan Teknologi Informasi
Sagita Rosmaida
Universitas Budi Darma
Computer Science & IT

Published : 1 Documents Claim Missing Document
Claim Missing Document
Check
Articles

Found 1 Documents
Search

 1 
Design of an Integrated Database for Managing Student Academic Activities Zulfi Azhar; Sagita Rosmaida
Jurnal Multimedia dan Teknologi Informasi (Jatilima) Vol. 7 No. 04 (2025): Jatilima : Jurnal Multimedia Dan Teknologi Informasi
Publisher : Cattleya Darmaya Fortuna

Show Abstract | Download Original | Original Source | Check in Google Scholar | DOI: 10.54209/jatilima.v7i04.2713

Abstract

This study designs an integrated relational database for managing student academic activities using a relational approach and the Database Development Life Cycle. The schema integrates study programs, lecturers, students, academic years, courses, curricula, course classes, schedules, study plans (KRS), attendance, grades, academic advising, and student activities. Conceptual modeling was performed using an Entity Relationship Diagram, followed by conversion to a relational schema and normalization through Third Normal Form (3NF). The database prototype consists of 15 principal tables equipped with primary keys, foreign keys, unique constraints, check constraints, and indexes. Verification used synthetic data rather than institutional student records, including 120 students, 12 lecturers, 24 courses, 48 course classes, 720 KRS-detail records, 2,880 attendance records, and 720 grade records. Eight integrity and integrated-query scenarios were executed successfully, including rejection of duplicate student identifiers, prevention of orphan KRS-detail records, restriction of deleting referenced courses, and retrieval of integrated academic histories. The results show that the proposed schema maintains referential consistency and supports cross-module tracing of student academic activities from a single data source. The prototype is intended as a database foundation; production adoption still requires institutional validation, security controls, audit logging, backup and recovery, concurrency testing, and integration mapping.
Co-Authors Zulfi Azhar