Is 3063 Term Project Deliverable 2 Group Number 3 Your Name
Is 3063 Term Project Deliverable 2group Number 3your Name Aman Aliyo
Is 3063 Term Project Deliverable 2group Number 3your Name Aman Aliyo
IS 3063 Term Project Deliverable 2 Group Number: 3 Your Name: Aman Ali Your email: [email protected] Professor’s Feedback: “Excellent work up on the Term project. This work will be reflected in the other deliverables. One note, your attributes need a correlation to the entity, i.e.: CUST_FName for yours STUD_StdtID or STUDStdtID.â€
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 | Attribute | Data Type | Required / Optional | Example | Description |
|---|---|---|---|---|---|
| STUDENT | STUD_StdtID | INT(10) | Required | 123 | Student ID |
| STUD_FName | CHAR(10) | Required | John | Student’s first name | |
| STUD_LName | CHAR(10) | Required | Martin | Student’s last name | |
| STUD_DateOfBirth | DATE | Required | 01/20/1989 | Student’s date of birth | |
| STUD_NextOfKin | CHAR(50) | Optional | Lucas B. Martin | Student’s closest living blood relative | |
| STUD_EmergCont | INT(15) | Optional | 9876543210 | Emergency contact number | |
| STUD_Address | CHAR(30) | Required | 23 Street A | Student’s address | |
| STUD_Relations | CHAR(10) | Optional | Mother | Relation of emergency contact to student | |
| STUD_PhoneNo | INT(15) | Required | 1234567890 | Student’s phone number | |
| STUD_Email | VARCHAR(200) | Required | [email protected] | Student’s email | |
| SUBJECT | SUBJ_SubjID | INT(10) | Required | 456 | Subject ID |
| SUBJ_SubjTitle | CHAR(50) | Required | Biology | Title of the subject | |
| SUBJ_AttrbName | CHAR(50) | Required | Science | Name of the attribute | |
| INSTRUCTOR | INSTR_InstrID | INT(10) | Required | 789 | Instructor ID |
| INSTR_FName | CHAR(10) | Required | John | Instructor’s first name | |
| INSTR_LName | CHAR(10) | Required | Doe | Instructor’s last name | |
| INSTR_PhoneNo | INT(15) | Required | 1234567890 | Instructor’s phone number | |
| INSTR_Email | VARCHAR(200) | Required | [email protected] | Instructor’s email | |
| INSTR_Address | VARCHAR(100) | Required | 987 1st St | Instructor’s address | |
| ASSIGNMENT | ASGMT_AsgmtID | INT(10) | Required | 101 | Assignment ID |
| ASGMT_InstrID | INT(10) | Required | 789 | Instructor ID assigned to assignment | |
| ASGMT_CourseID | INT(10) | Required | 301 | Course ID | |
| ENROLLMENT | ENR_EnrollmID | INT(10) | Required | 1001 | Enrollment ID |
| ENR_StdtID | INT(10) | Required | 123 | Student ID | |
| ENR_SubjID | INT(10) | Required | 456 | Subject ID | |
| ENR_CourseID | INT(10) | Required | 301 | Course ID | |
| ENR_EnrollmDate | DATE | Optional | 12/30/1997 | Date of enrollment | |
| COURSE | COUR_CourseID | INT(10) | Required | 301 | Course ID |
| COUR_SubjID | INT(10) | Required | 456 | Subject ID of the course | |
| COUR_CourseTitle | CHAR(50) | Required | History 101 | Title of the course | |
| COUR_CourseDescr | VARCHAR(100) | Optional | This course is an introduction to history. | Description of the course | |
| COUR_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).
- Student - Enrollment (One or many): One student can have one or many enrollments. This allows tracking of multiple enrollments by a single student.
- Enrollment - Student (One & only one): One enrollment can only be assigned to one student.
- Enrollment - Course (One or many): One enrollment can have one or many courses at the same time.
- Enrollment - Subject (One or many): One enrollment can have one or many subjects.
- Subject - Enrollment (Zero or many): One subject can have zero or many enrollments.
- Subject - Course (Zero or many): One subject can be assigned to zero or many courses.
- Course - Subject (One & only one): One course can be assigned to one and only one subject; this organizes courses into subject categories.
- Course - Enrollment (Zero or many): One course can have zero or many student enrollments.
- Course - Assignment (Zero or many): One course can have zero or many assignments.
- Assignment - Course (One-to-one): One assignment belongs to one course.
- Assignment - Instructor (One or many): One assignment can have one or many instructors assigned to it.
- Instructor - Assignment (One or many): One instructor can have zero or many assignments.
4. ERD
(Note: ER Diagram visual not included here; it should depict entities and relationships described above)
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.).
The SEMS application provides comprehensive functionalities including student enrollment, course and subject management, instructor administration, assignment creation, enrollment tracking, and communication tools. Users such as administrators and staff can enroll students, ensuring conflict-free schedules and data accuracy. They can manage course and instructor data, create and link assignments, and view enrollment histories. The system also facilitates notifications via email, comprehensive reporting, and analytics to monitor trends and performance.
Future extensions include integration with Learning Management Systems (LMS), development of student portals for self-service, mobile applications, automated notifications, advanced data analytics with predictive insights, and integration with financial systems for fee management. Security features such as authentication and role-based access are integral to protection of sensitive data, aligning with desired technological advancements. These functionalities aim to streamline administrative operations, enhance educational quality, and improve the overall experience for students, instructors, and administrators.