MIS602 Data Modelling: Student Record Management System Report

This report details the development and analysis of a student record management system, created for Torrens University Australia. The student implemented a database using a spreadsheet, creating different versions to manage student records, course enrollments, and faculty assignments. The report describes the implementation, including the creation of data objects, attributes, and the evolution of the database through several versions, adding and removing attributes as required. A critical analysis evaluates the suitability of the database objects and identifies areas for improvement, such as the addition of primary and super keys for better data integrity and consistency. The report also references relevant literature on database design and management. In conclusion, the student successfully created a student database management system capable of storing and organizing student and course data, with suggestions for future enhancements.

Running head: STUDENT RECORD MANAGEMENT SYSTEM
Student Record Management System
Name of the student:
Name of the university:
Author note:

1STUDENT RECORD MANAGEMENT SYSTEM
Table of Contents
Introduction......................................................................................................................................
Implementation................................................................................................................................
Critical Analysis..............................................................................................................................
Conclusion.......................................................................................................................................

2STUDENT RECORD MANAGEMENT SYSTEM
Introduction
Database Management System is defined as a type of system software that is
responsible for creating and managing the databases within system (Coronel & Morris, 2016).
It allows users to systematically create, update, mage or retrieve the data sets according to
need. An excel spreadsheet within an organizational structure lends itself while describing
how a database system works (Laudon & Laudon, 2016). A database is a collection of
connected objects in a spreadsheet that are associated while creating single record inside a
community of multiple records within the database table. Spreadsheets are itself a database
but not a relational one. A relational database within a database management system is a
combination of spreadsheet tables along with the slave tables associated with the database
management system. In this assessment based on the identified scenario the key data objects
are identified along with their respective attributes and all are defined within a spreadsheet.
Based on the different versions of the spreadsheet a detailed document is thus prepared so as
to reflect the activity undertaken.
Implementation
As per the requirement of Torrens University Australia, a new Student record
management system needed to be developed. The new data base thus developed enabled the
managing of students who are enrolled with the university (Read & Ginn, 2015). The
database also enabled managing of datasets of course students who are already enrolled with
the university besides managing the staffs assigned with each of the courses. The spreadsheet
file thus we prepared consisted of several versions where the version 1 of the spreadsheet
included creating of 30 rows of data with all the possible database objects. In this version we
have include the student’s name along with the student IDs. The course in which they are
enrolled, the batch and the course faculty are included within the columns of the database. In

3STUDENT RECORD MANAGEMENT SYSTEM
this way we have created 30 individual rows along with the mentioned data objects. While
creating the rows within the database with the database objects we have kept in mind to keep
the length of the texts within the columns within limit as it ensures more security and
performance related reasons. The database objects created within the database tables will help
in managing the relationship between the university and the students who are enrolled within
the database rows. It will also help in maintaining the student records enrolled with different
courses with the batch year and the faculties related with each of the courses. The next data
object that is created in the version 2 of the student record management system consisted of
updating the last 2 records of the table while adding additional 5 rows of data. Here we have
updated the last 2 record of the version 1 of data object table. The student Id ST029 and
ST030 of version 1 is updated while updating the names of the students to Stephen Flair and
Jack Lehmann. After updating the last 2 records, additional 5 rows of data are added. When
additional 5 rows are added to the overall management system of the student record, the
entire information about the attributes that includes Student ID, Student Name, Course
Enrolled, Batch and Course Faculty are all updated at the same time. In the next step of
developing a student record management system, the version 3 of the spreadsheet included
adding of 2 new attributes with in the table of the student record management system. In this
case, we have added two new attributes which includes the Faculty ID and the Course IDs.
The course ID attribute is directly related with the Courses that are enrolled within the
database table and the Faculty ID attribute is related to the Course faculty who are related to
each of the courses that students are enrolled with. All the individual attributes of the table
are updated after adding the two new attributes in the student record management system.
The final version of the spreadsheet related to the student record management system
included removal of 5 existing attributes from the database table while adding 5 more rows of
data. In this version, we have removed all the 5 attributes including Student Name, Course

4STUDENT RECORD MANAGEMENT SYSTEM
Enrolled, Batch, Faculty ID and Course Faculty (Dixson, 2015). While doing so we are left
with only two attributes including Student ID and Course ID. After that as per requirement,
we have updated the table while adding 5 more rows under the attributes Student ID and
Course ID. After undertaking the required activities, the main objectives of the assessment is
achieved in developing a database management system that will allow the university in
storing records of students based on the different attributes included within the database table.
Each of the database attributes are related with each other. The student ID and the Student
Name attribute contain data of all the students who are registered with the university under
different programs. The different courses that are carried out within the university are
recorded under the attribute Course ID and Course Enrolled. The educational institution is
required to conform to the fair use of the Student Record System (Elmasri, 2017). In this
respect, the persons who are related with the use of the Student Record Management System
needs to follow certain points which include:
1. They need to be informed about the existence of the system.
2. Individuals should be well informed about the type of data that is stored within the record
of the database management system (Henrie et al., 2015).
3. They need to ensure that the data that are used are for intended purpose only.
Critical Analysis
The original data object is found to be partially suitable for the requirement version 1
as the database object contains only one candidate key that can be used to uniquely identify a
tuple. The students are mapped to courses, course batch as well as the faculty who will be
conducting the courses (Kolaitis, 2018). This makes it possible to have three more attributes
in place that should act as super keys to uniquely identify the course name, batch name and
faculty name. However no such attributes are present in the original database table. As a

5STUDENT RECORD MANAGEMENT SYSTEM
result the database object cannot be termed completely suitable for the requirements
specified.
The data objects and attributes that are used as inputs in designing the database as also
the summary document may have followed the requirements but might not necessarily be
consistent. This is because the data objects that apply for the requirements of version 2 and
version 3 are based on the original data object created for the requirement version number 1.
The data object for requirement version 4 involves removal of five attributes, and is applied
on the third data object which has seven attributes and not the original data object which has
only five attributes (Bergamaschi et al., 2016). This thus leads to inconsistency which
ultimately affects the effectiveness of the database design. As a result it could have helped if
the original database object contained few more attributes so that the data object for the
requirement version 4 could have also been based upon the original database object and not
the object for requirement version 3.
It is evident that improvements can be made to the database objects by the students
involved. For this it can be hugely beneficial for the students if they can consult the
“Fundamentals of database system” which helps in gaining in depth understanding in
designing effective database solutions as also get to know about both logical and physical
concepts that are relevant to designing databases (Elmasri, 2017). Another useful reading
would be “Fundamentals of Database Design”. This paper provides a detailed walkthrough
on key concepts of databases, the conceptual design, entity relationship models, the logical
design, relational model and its implementation along with the best practises for designing
databases (Harrington, 2016). The scope of database studies covered by these two articles
combined negate the requirement of consulting any additional materials and provide clear and
concise information that is specifically needed for getting started with designing databases
and handling database objects and attributes.

6STUDENT RECORD MANAGEMENT SYSTEM
In this report, the suitability of the database objects have been questioned due to the
lack of certain attributes. Yet the concerned database solution can be useful for scenarios
which require minimalistic database implementation approach and help speed up processes.
However to ensure all properties of database design are met and to ensure the solution can be
normalized easily the suggested improvements does prove to be beneficial for most use cases.
Conclusion
In conclusion the different versions that are mentioned within the requirement of the
assessment are carried out efficiently. As a result of which a robust student database
management system for the institution to hold large amount of data within the tables is
generated (Yue, 2016). The database thus created will provide an efficient way to store and
organize the data related to student and the course taken by them along with the faculties
related with each course (Kuh et al., 2015). The spreadsheets thus created will also serve as a
centralized facility that will enable simplicity while working with the registrar.

7STUDENT RECORD MANAGEMENT SYSTEM
References:
Bergamaschi, S., Guerra, F., Interlandi, M., Trillo-Lado, R., & Velegrakis, Y. (2016).
Combining user and database perspective for solving keyword queries over relational
databases. Information Systems, 55, 1-19.
Coronel, C., & Morris, S. (2016). Database systems: design, implementation, & management.
Cengage Learning.
Dixson, M. D. (2015). Measuring student engagement in the online course: The Online
Student Engagement scale (OSE). Online Learning, 19(4), n4.
Elmasri, R. (2017). Fundamentals of database systems.
Elmasri, R. (2017). Fundamentals of database systems.
Harrington, J. L. (2016). Relational database design and implementation. Morgan Kaufmann.
Henrie, C. R., Bodily, R., Manwaring, K. C., & Graham, C. R. (2015). Exploring intensive
longitudinal measures of student engagement in blended learning. The International
Review of Research in Open and Distributed Learning, 16(3).
Kolaitis, P. G. (2018, May). Reflections on schema mappings, data exchange, and metadata
management. In Proceedings of the 35th ACM SIGMOD-SIGACT-SIGAI Symposium
on Principles of Database Systems (pp. 107-109). ACM.
Kuh, G. D., Ikenberry, S. O., Jankowski, N., Cain, T. R., Hutchings, P., & Kinzie, J.
(2015). Using evidence of student learning to improve higher education. John Wiley
& Sons.
Laudon, K. C., & Laudon, J. P. (2016). Management information system. Pearson Education
India.

8STUDENT RECORD MANAGEMENT SYSTEM
Read, J., & Ginn, M. L. (2015). Records management. Cengage Learning.
Yue, F. U. (2016, May). A study of student information management software. In 2016 IEEE
International Conference of Online Analysis and Computing Science (ICOACS) (pp.
393-396). IEEE.