The course registration system helps the students to gather information about a particular course and then they can easily register themselves in a particular course.

1. Huda seyam
Doaa Nassar
Course registration system to help student to gather information about a
particular course and then they can easily register them self in a
particular course.
Purpose
• System will allow the registration of students in particular course.
• System has inbuilt validation system to validate the entered data
after successful submission, system will give unique registration
no for each student.
• Student can login into system by using username and check the
details of course, faculty and department
Project Specification
A high-level description of the project:
• Each student has a unique student ID and a profile. The profile includes
username, login password, and may have a picture. You can also add
other necessary information.
• Each instructor has a unique faculty ID and a profile. The profile must
indicate the instructor’s department(s). An instructor may work at more
than one department.
• Course section has a unique department ID, a name, and a list of
faculties.
• Each course has a course number, an instructor, given department,
term, credits, classroom, periods, prerequisite courses, textbooks, and
other information you think is necessary.
• A classroom has a unique ID and a unique location. Classrooms can
hold more than one course each term, but these courses cannot conflict
in time. Classrooms have capacities. Registered students’ number cannot
exceed the classroom capacity.
• Must maintain all the courses a student has already taken/registered.
This is used to check course prerequisites when registration.

2. Huda seyam
Doaa Nassar
• Students may login (with username and password) to the system to
register courses or retrieve all the courses they have already
taken/registered.
• Instructors may login (with username and password) to the system to
add courses or retrieve all the courses they have already given/added.
• details of course registration show :
1) If he/she does not meet the prerequisites.
2) The students registered in the course exceed the capacity of the classroom.
3) The course has a time conflict with other courses in the same
term.
• An instructor cannot add a course if:
4) The classroom has already occupied by another course in the same period.
5) He/she has another course in the same period.
6) He/she is not affiliated to the department of this course.
• A day has 12 periods and a week has 5 days. Instructor provides
periods when adding courses to the system.
• Students may retrieve all the courses given by a department, an
instructor, or held in a specific period.
• There can be an arbitrary number of
students/instructors/departments/classrooms/courses
Scope
The main aim of the project is to learn the intricacies of modeling the
database with the given requirements and using a web based interface
to interact with the back end keeping in mind the data consistency and
the stability of the entire system.

3. Huda seyam
Doaa Nassar
Since the system is developed with a web-based interface, we can start
executing the model with parallel executions with the confidence that
the back end oracle data store will take care of the concurrent
transactions. The ACID (Atomicity, Consistency, Isolation, and Durability)
property of the database helps to keep the system consistent and stable.
System planning
That Define clear, discrete activities and the work needed to complete
each activity.
Create Time and Work Schedule

4. Huda seyam
Doaa Nassar
System analysis
System analysis a detailed study of the various operations performed by
a system and their relationships within and outside of the system. Here
the key question is what all problems exist in the present system? What
must be done to solve the problem?
Analysis begins when a user or manager begins a study of the program
using existing system.
DATA FLOW DIAGRAM
A graphical tool that show the flow of data through a system. Include
data flow, process, external entity and data store

5. Huda seyam
Doaa Nassar

6. Huda seyam
Doaa Nassar

7. Huda seyam
Doaa Nassar
System Design
The purpose of system design is to create a technical solution that
stratifies the functional requirements for the system.
System component are distributed across the physical architecture,
usable interfaces are designed and prototyped.
Designing database
The need for structured storage, modification and maintenance of huge
amounts of data has resulted in the emergence of the Database
Management System (DBMS) that aimed to provide a managing tool for
maintaining the data, through various data models.
Any database system can be chosen as the back-end such as Oracle,
MySQL at web server such as Glassfish and any language can be chosen
such as php
We need to implement this project using MYSQL, and PHP using Apache
server.
• Design schema

8. Huda seyam
Doaa Nassar
ADMIN (name, email, password)
COURSE (course section, name, course ID, description)
COURSE SECTION (name, ID)
INSTRUCTOR (name, email, password, ID, comment)
Users (user_ID, name, email, password, comment)
LESSON (course, name, serial Number, show time, order)
Subscriptions (user ID, course ID)
• Designing forms

9. Huda seyam
Doaa Nassar

10. Huda seyam
Doaa Nassar
Some design challenges:
❖ We used PNG pictures for storing the profile picture information and
found that the storage space went to big numbers. We then changed
the type of data and made it as a jpeg picture.
❖ We missed the term field in the classroom table initially and had to
add the field later to keep track of the classroom information for
previous semesters.
❖ We had not thought about the graduation date field for a student.
When trying to implement a realistic system this field had to be in
place to segregate the graduated students and other current
students.
❖ We had to have an ADMIN login to perform some administrative
tasks. We thought it would be very practical to have this option. For
example, when you are logged in as an admin you can edit the
graduated field for a student. We tried to map the real scenario
where the student requests that he wants to graduate to the Grad
Advisor in his department and the Advisor requests DB
Administrators to update the student’s `graduated` field.

11. Huda seyam
Doaa Nassar
System Implementation
To convert final physical system specification into working and reliable
software
Implemented project must meet the requirements and functionality of
the system to be success and able to support and maintain
That is, student should can:
- login the system and edit his profile data i.e. address/homepage/email
id information and update.
- Register a course
- Constraints checked here include
❖ MAX courses registered this semester, in our system its 3,
❖ Course previously not registered,
❖ Seats lefts in the course,
❖ Prerequisite course registered and
❖ Conflicts in timing with other currently registered courses.
- View his schedule
- Can view class schedule in a tabular format (similar to ISIS)
- Drop course option is provided on this page
- Can view additional information about the courses he has taken.
- Can view textbook information of the courses department wise.
- Can view courses with prerequisite information
- Can view the list of courses using the department and instructor
parameters.
- Can view the list of courses using the day and period parameters.

12. Huda seyam
Doaa Nassar
And Instructor can:
- login the system and view / edit profile information and also update.
- View current schedule in a tabular format (Similar to ISIS)
- Edit Course details - Details such as Seats left - to increase or decrease
the capacity of the course (seats cannot be more than class capacity)
- add a new course to the database under his profile and department.
- view classroom availability as well as maximum capacity of classroom
when course information is updated or new classroom is added
- View info of all the students registered in the courses he/she is
handling.
Support and maintenance
The maintenance phase is the last phase of the SDLC. It is here that the
SDLC becomes a cycle, with the last activity leading back to the first.
This means that the process of maintaining an information system is the
process of returning to the beginning of the SDLC and repeating
development steps until the change is implemented four major activities
occur within maintenance:
1. Obtaining maintenance requests
2. Transforming requests into changes
3. Designing changes
4. Implementing changes
Obtaining maintenance requests requires that a formal process be
established whereby users can submit system change requests, request
new development, to report problems, or to request new features
within an existing system. Such as SSR
in this project we can develop the system by improve another features
as mobile application app for online courses.