0% found this document useful (0 votes)
183 views

University Database

The document describes creating an entity relationship diagram for a university database. It identifies the key entities like department, professor, course, and student. It analyzes the relationships between entities like a one-to-one relationship between professor and school, and a many-to-many relationship between students and classes. The document also discusses using UML class diagrams to define primary and foreign keys for each table and types of business intelligence reports that could help with course management, enrollment, and historical tracking. Finally, it mentions three vendors that have developed efficient school management systems and compares their key aspects.

Uploaded by

Evans Oduor
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
183 views

University Database

The document describes creating an entity relationship diagram for a university database. It identifies the key entities like department, professor, course, and student. It analyzes the relationships between entities like a one-to-one relationship between professor and school, and a many-to-many relationship between students and classes. The document also discusses using UML class diagrams to define primary and foreign keys for each table and types of business intelligence reports that could help with course management, enrollment, and historical tracking. Finally, it mentions three vendors that have developed efficient school management systems and compares their key aspects.

Uploaded by

Evans Oduor
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

1

University Database

Name

Department; University

Course Code; Course Name

Tutor

Date
2

University Database

Entity Relationship Model Describing the data structure that will store all data element.

To understand what the stakeholders require, a comprehensive review of the attributes,

requirements, entities and their relationships has to be undertaken since they are the main

activities as far as building a university database is concerned. Before creating the Entity

Relationship Diagram, it was decided that a designer would need to identify all of the major

entities as well as all of the relationships between them. Also included are all of the attributes of

each entity, as well as the primary keys that describe these entities.

(See figure 1in the attached document in Visio)

Assumptions or limitations for each relationship

Following the examination of the requirements of the institution’s database, several

assumptions were made in an attempt to understand how the entities and their attributes relate.

The already stated entities include Department, Professor, School, Course, Student, Class, Room,

and Enrolment. The university is sub-sectioned into different branches where every branch has a

dean that is also a professor by qualification. As a result, the professor and the school have a one-

to-one relationship. This means that a professor can be the dean of a maximum of a single school

but can teach many courses in a single branch.

The university may have multiple branches. There are one or more departments in each

branch. Each department can only represent one school. The relationship between a department

and a course is one to many meaning that a department can offer more than one course, but if the

university offers a classified course, it will be labeled as optional to the department entity. There

is one too many relationship between the course and the class. This is due to the fact that a single
3

department can offer multiple classes of similar course whereas each of the classes is taught by a

single professor in one location and at a given time.

While one department can have many professors, it is only one professor that head a

department at a time, so the relationship between the department and the professor is optional.

One student can enroll in multiple classes, and each class may have more than ten students,

resulting in a many to many relationship represented as (M: N relationship) between the students

and the classes. Each department provides a variety of majors to students who are affiliated with

that department. Each student is only allowed to have one major that is associated with a

department. As a result, the department is optional for the student.

Using a UML to create a primary key and foreign keys for class diagram for each table.

(See figure 2 in the attached document in Visio)

Four types of business intelligence reports that could help the university in course

management, student enrollment, or historical tracking.

Business reporting is critical to all organizations and enterprises. Having the most up-to-

date data will enable the institution to make sound business decisions that will aid in the

organization's future operations. In contrast to the weekly reports that causes delays, the

university could create reports quickly. This ought to be managed through minimum duplication

in order to provide information for decision-making as well as the tools to do so.

Manager reports, transactional reports and operational reports should be generated by the

management team. Managed reporting is the most effective method to generate a scheduled

report, such as the total income for the fiscal quarter. The operational and transactional reports

show how many classes a specific student has enrolled in, as well as how many professors are
4

teaching which classes. A statement report would detail income as well as expenditures and

liabilities for each of the campuses of the university. Reports on production can be run on

voluminous data obtained from existing production databases, and reports could easily be

generated to provide answers to certain business queries. These reports would be extremely

beneficial to the university in making decisions regarding which campuses should offer which

courses and which courses have the greatest number of interested people at any given time.

Three vendors that developed and are employing efficient registrar and school

management system

Various vendors develop and implement business systems in different ways. The

University of Arizona has taken a novel approach to data management, analysis, and

presentation. The institution’s business intelligence allows for easy retrieval and access of

individuals’ private financial data from one source, providing easy and secure access to data for

management. As a result, retrieval takes up little time, while analysis and decision-making take

up the majority of the time.

According to the Executive Director at Kennesaw University, the use of BI tools has

evolved significantly as far as metadata that details the mechanism and the time a set of data is

collected. These tools conceal nuances such as where the data is stored, allowing users to

generate reports with little or no IT expertise (Apfeld, 2019). Furthermore, the drag and drop

functions found in BI tools make report creation very user-friendly. It would then be wise to

propose that Warsaw University take a similar approach to obtain user-friendly tools for easier

and more effective system monitoring.

Compare and contest the key aspects that each system offers.
5

A relational database management system ensures referential integrity and allows for

primary and foreign keys between entities. When the university requires monitoring of system

activities, an Oracle Business Intelligence Enterprise Editor can be useful. This will aid in school

recruitment, retention, and course scheduling. The OBIEE tool will also make it easier to enroll

and drop students, as well as provide information on the number of classes offered on each

campus, the number of professors on each campus, income and expenses in general. This will be

a fantastic tool for allowing IT novices to create and generate reports without having to wait for

IT experts.
6

References

Apfeld, B. (2019). Spatial and Temporal University Database. Working Paper, University of

Texas.Unified Modeling Language - UML.

(n.d.). Retrieved July 28, 2021, from

http://faculty.kfupm.edu.sa/ICS/sukairi/ics434/course_resources/2-Advanced Data

Modeling/ch4.pdf

Verifying Use Cases, Data Flow Diagrams, Entity Relationship Diagrams, and State Diagrams

via State Linkages. (n.d.). Retrieved July 28, 2021, from

http://www.modernanalyst.com/Resources/Articles/tabid/115/ID/2788/Verifying-Use-

Cases-Data-Flow-Diagrams-Entity-Relationship-Diagrams-and-State-Diagrams-via-

State-Linkages.aspx

You might also like