Term Project Deliverable 2
IS 3063 Term Project Deliverable 1 Template
Group Number: 3
Your Name: Aman Ali
Your email: [email protected]
Group proposal section:
1. Description of the business context and related data management problem(s)
In today's dynamic educational landscape, efficient data management is paramount to providing a seamless learning experience. Educational institutions face numerous challenges in managing student enrollments, courses, and instructors, which can lead to administrative inefficiencies and data inaccuracies. The "Student Enrollment Management System" project aims to address these challenges by introducing a comprehensive database application. This proposal outlines the business context, identifies the problems that this system will solve, describes the entities and their attributes, defines critical business rules, presents a tentative Entity-Relationship Diagram (ERD), and provides an overview of the application's functionality.
The Student Enrollment Management System (SEMS) is a database application developed to streamline and enhance the student enrollment process at XYZ University. This documentation outlines the project proposal, including the problem statement, proposed database solution, and an Entity-Relationship Diagram (ERD) for the system.
The manual student enrollment process at XYZ University is error-prone, leads to scheduling conflicts, and causes delays in providing essential services. These challenges necessitate the development of a robust SEMS to address the following issues:
• Lack of a centralized system for student registration.
• Scheduling conflicts due to manual enrollment.
• Inaccurate course management leading to credit-hour discrepancies.
• Limited reporting capabilities for administrators
2. The entities and the attributes
Entity: STUDENT
|
Attribute |
Data Type |
Required/Optional |
E.g. |
Description |
Null value |
|
StdtID |
INT(10) |
Required |
123 |
Student ID |
|
|
FName |
CHAR(10) |
Required |
John |
Student’s first name |
|
|
LName |
CHAR(10) |
Required |
Martin |
Student’s last name |
|
|
DateOfBirth |
DATE |
Required |
01/20/1989 |
Student’s date of birth |
|
|
NextOfKin |
CHAR(50) |
Optional |
Lucas B. Martin |
Student’s closest living blood relative |
|
|
EmergCont |
INT(15) |
Optional |
+1(210)352-7846 |
Emergency contact |
|
|
Address |
CHAR(30) |
Required |
23 Street A |
Student’s address |
|
|
Relationship |
CHAR(10) |
Optional |
Mother |
Relation of emergency contact to student |
|
|
PhoneNo |
INT(15) |
Required |
+1(210)345-6732 |
Student’s phone number |
|
|
|
VARCHAR (200) |
Required |
Student’s email |
|
Entity: SUBJECT
|
Attribute |
Data Type |
Required /Optional |
E.g. |
Description |
Null Value |
|
SubjID |
INT(10) |
Required |
456 |
Subject ID |
|
|
SubjTitle |
CHAR(50) |
Required |
Biology |
Title of the subject |
|
|
AttrbName |
CHAR(50) |
Required |
Science |
Name of the attribute |
|
Entity: INSTRUCTOR
|
Attribute |
Data Type |
Required /Optional |
E.g. |
Description |
Null Value |
|
InstID |
INT(10) |
Required |
1234567890 |
Instructor ID |
|
|
FName |
CHAR(10) |
Required |
John |
Instructor’s first name |
|
|
LName |
CHAR(10) |
Required |
Doe |
Instructor’s last name |
|
|
PhoneNo |
INT(15) |
Required |
+1(210)345-6732 |
Instructor’s phone number |
|
|
|
VARCHAR (200) |
Required |
Instructor’s email |
|
|
|
Address |
VARCHAR(100) |
Required |
987 1st St |
Instructor’s address |
|
Entity: ASSIGNMENT
|
Attribute |
Data Type |
Required/Optional |
E.g. |
Description |
Null Value |
|
AssignmID |
INT(10) |
Required |
1234567890 |
Assignment ID |
|
|
InstID |
INT(10) |
Required |
0987654321 |
Instructor ID |
|
|
CourseID |
INT(10) |
Required |
1234567890 |
Course ID |
|
Entity: ENROLLMENT
|
Attribute |
Data Type |
Required/Optional |
E.g. |
Description |
Null Value |
|
EnrollmID |
INT(10) |
Required |
1234567890 |
Student’s enrollment ID |
|
|
StdtID |
INT(10) |
Required |
0987654321 |
Student ID |
|
|
CourseID |
INT(10) |
Required |
1234567890 |
Course ID |
|
|
EnrollmDate |
DATE |
Optional |
12/30/1997 |
Student’s enrollment date |
|
Entity: COURSE
|
Attribute |
Data Type |
Required /Optional |
E.g. |
Description |
Null Value |
|
CourseID |
INT(10) |
Required |
1234567890 |
Course ID |
|
|
SubjID |
INT(10) |
Required |
0987654321 |
Subject ID of the course |
|
|
CourseTitle |
CHAR(50) |
Required |
History 101 |
Title of the course |
|
|
Descr |
VARCHAR (100) |
Optional |
This course is an introduction to history. |
Description of the course |
|
|
CredHrs |
INT(4) |
Required |
3 |
Measures the time needed for learning in a course |
|
3. Business rules that define all the relationships among entities, the constraints, and the attribute domains (if any).
Relationships:
1. Student - Enrollment (One-to-Many):
· One student can have one or many enrollments.
· This relationship allows tracking of multiple enrollments by a single student.
2. Enrollment - Student (One & only one):
· One enrollment can only be assigned to one student.
3. Enrollment - Course (One or many):
· One enrollment can have one or many courses at the same time.
4. Enrollment - Subject (One-to-many):
· One enrollment can have one or many subjects.
5. Subject - Enrollment (Zero or many)
· One subject can have zero or many enrollments.
6. Subject - Course (Zero or many):
· One subject can be assigned to zero or many courses.
7. Course - Subject (One & only one):
· One course can be assigned to one and only one subject.
· This relationship organizes courses into subject categories.
8. Course - Enrollment (Zero or Many):
· One course can have zero or many student enrollments.
9. Course - Assignment (Zero or many):
· One course can have zero or many assignments.
10. Assignment - Course (One-to-one):
· One assignment belongs to one course.
11. Assignment - Instructor (One or many):
· One assignment can have one or many instructors assigned to it.
12. Instructor - Assignment (One-to-Many):
· One instructor can have zero or many assignments.
4. ERD
5. A summary of the functionality of the application (i.e. what the users can do with this application, future extension/integration with other systems etc.).
Functionality of SEMS Application:
· Student Enrollment:
· Users (administrators and staff) can enroll students into courses.
· SEMS will ensure that there are no scheduling conflicts during enrollment.
· Data accuracy is maintained during the enrollment process.
· Subject and Course Management:
· Users can create and manage subjects and courses.
· Courses are categorized under subjects, allowing for easy organization.
· Descriptive information about courses is available, including titles, descriptions, and credit hours.
· Instructor Management:
· Instructors can be added, and their details are recorded in the system.
· Instructors are associated with specific courses and assignments.
· Assignment Management:
· Users can create assignments for courses.
· Assignments are associated with specific courses and instructors.
· SEMS ensures that assignments are correctly linked to courses.
· Enrollment Tracking:
· SEMS maintains a record of student enrollments in courses.
· Enrollment dates are recorded for reference.
· The system allows administrators to access enrollment history.
· User Communication:
· SEMS supports communication with students and instructors via email.
· Users can send notifications and updates regarding enrollment and assignments.
· Reporting and Analytics:
· The application offers reporting capabilities for administrators.
· Users can generate reports on enrollment data, course statistics, and more.
· Analytics tools help identify trends and insights for decision-making.