In the present case, the context diagram shows the main functions of the student enrolment system in ABC University based on the details provided in the case study.

Identified users in the context diagram include students’ instructors of the college and officers and directors who have access to the enrolment system.

The information systems diagrams have been drawn as a first attempt to formalize the process flow in the student enrolment system for the University and it provides the fundamental idea about the decomposition of the process.

The basic functionality of the student enrolment system, in this case, has been identified to be providing relevant information to the students related to enrolment and registration as well as providing authenticated access to officers and directors in the University for alteration of the enjoyment process and courses.

1. Context Diagram

2.Level 0 Data Flow Diagram (DFD)

3. Level 1 DFD

4. i) Entities and attributes

The different entities and attributes that can be identified in case of the student enrolment system for ABC University can be listed as follows:

Enrolment entity:

• Enrolment_ID
• Student_ID
• Course_ID
• Enrolment_type
• Enrolment_fees

Fees entity:

• Student_ID
• Course_ID
• Enrolment_type
• Student_Name
• Student_email

Course Entity:

• Course_ID
• Enrolment_fees
• Course_subjects
• Student_ID

Login entity:

• Student_ID
• Student_Password
• Login Username
• Course_ID

Student Entity:

• Student_Name
• Student_ID
• Student_contact
• Student_email
• Course_ID

Timetable entity:

• Course_subjects
• Student_ID
• Course_ID
• Subject_time

Reports Entity:

• Student_ID
• Course_ID
• Perfromance_Reports
• Announcements
• Notifications

Administrators Entity

• User_ID
• User_Name

Description

Each of the entities under the student enrolment system is to be stored in different tables within the database system. Each of the tables defined within tables includes entities and attributes which consist of a combination of the Primary and unique keys. Entities are bonded with one another through the use of foreign keys which are shown in the following sections explaining the database design.

ii) ER diagram

5. File system or database: Relational database design

Requirements:

• Students' access to Enrolment details, payment details, course details, subject time and subject electives details
• Authenticated access of program directors and enrolment officers for altering the student data according to requirements
• Alteration of timetables by timetable managers in ABC University with access to all student details, course details and payment details
• Entering of reports changes by the administrators using the enrolment system interface by enrolment officers and program directors

Data tables

The data tables included in the database design of the student enrolment system for ABC University include tables named:

• Student details
• Course details
• Enrolment details
• Reports
• Login details
• Timetable details
• Subject details

The columns are under each of the tables can be identified as follows:

Fees details

ID (Primary Key) Course_ID Enrolment_type Student_Name Fees_status Student_Email

Student details

• Student_ID
• Student_name
• Contact
• Email
• Course_ID

Course details

• Course_ID (Primary Key)
• Enrolment_fees
• Course_Subjects
• Student_ID
• Fees_status

Enrolment details

• Enrolment_ID (Primary Key)
• Student_ID
• Course_ID
• Enrolment_type
• Enrolment_fees

Reports

• Admin_ID (Primary Key)
• User_ID
• User_Name
• Report_type
• Notification_ID
• Course_ID

Login details

• Login_ID (Primary Key)
• Student_ID
• Password
• Login Username
• Course_ID

Timetable details

• Subject_ID (Primary Key)
• Subject_time
• Student_ID
• Course_ID

Subject details

• Campus_ID (Primary Key)
• Course_ID
• Subject_ID
• Student_ID
• Subject_time
• Subject_name

The Accessibility and authentication functions are related to the login details, reporting and timetable maintenance tables and user interfaces are differentiated for students and administrators including enrolment officers and program directors. The student identification number acts as a foreign key in many of the tables which relate to and define the information flow between the concern tables.