Student Registration System

Contents
1.Problem Defination…….............................................................................. 3

2.Objectives Of the Project……...................................................................... 3

3.Function Requirment…… ........................................................................... 4

5.Scenario of Student Registration System…… ............................................... 6

6.Data Flow Diagram…… .............................................................................. 7

7.E-R Diagram…… ........................................................................................ 9

8.Use Case Diagram…… .............................................................................. 10

9.Class Diagram…… .................................................................................... 11

1. Problem Defination
The existing Student Registration System of registration requires many
documents and application forms to be filled out. Data has to be repeatedly entered
at each stage of the process and multiple files are made for each student. Documents
are verified with multiple copies made for record and the testing process is
conducted independently which again compounds the paperwork required. The
amount of data processing required for each stage of the process ensures that the
process of new student admission takes a long time.

2. Objectives Of the Project

The aim of this Student Registration System project is to build a student

registration system that will completely automate the process of new student

registration in a university. The system will handle the document submission,

testing process , registration of new students , allow students to select course and

allow Professors to access the on-line system to indicate which courses they will be

teaching . The system will be web based and will have two implementations i.e.

client side (student) and server side (university). The server side implementation

can only be accessed over the university intranet while the client side can be

accessed over the internet .

3. Function Requirment
We get functional Requirements through interviews and questionnaires by

visiting some universities , asking those in charge of these Universities some

questions for having a general picture about the nature of universities work

and the remarkable problems encountered by them in their daily work. Those

questions were as follows:

1. Does the universities have System for Registration?

The Answer of majority of Universities is (No) and they are still dependent on

traditional way for Registration..

2. Do you feel comfortable when using the Traditional method in Registration

or you face problems?

The Answer was (No) stating that there are several problems encountering

them while using a traditional method.

3. Does the recent available electronic system solves all problems and meets all

needs?

The answer was (No) showing that there are some services which are not

provided by those systems.

4. What is the most important information and student records that want to
record in the long term ?
The answer are ID Student and name and that courses that be token by this

student .

After taking with users and listening to user's needs or requirements, asking

questions in collect Data phase , after this phase we define Function Requirment

The functional requirements for the system are following :

1 - The system should allow the Student to register

2 - The system should allow the Student to login
3 - The system should allow the Admin to login
4 - The system should allow the Professor to login
5 - The system allow the Student to request a course catalogue containing a list

of course offerings for the semester

6 - The system allow Student to select Course that be token or submission

7 - The Student can bill or make payment for the semester

8 - The system allow the Professor to indicate which courses they will be

teaching .

9 - The system should allow the Student change their schedules and drop or
add course during semester
10 - The system allow admin to manage courses (create , modify ,
remove).
11 - The system allow the admin to manage Student and professor(Add ,
delete , Edit).
12 - The system allow professor to see signed Student to course
13 - The system allow the Registrar to Generate course catalog.
5. Scenario of Student Registration System
At the beginning of each semester students may request a course catalogue
containing a list of course offerings for the semester. Information about each course,
such as professor, department, and prerequisites will be included to help students
make informed decisions. The new on-line registration system will allow students to
select four course offerings for the coming semester. In addition, each student will
indicate two alternative choices in case a course offering becomes filled or
canceled. No course offering will have more than ten students. No course offering
will have fewer than three students. A course offering with fewer than three
students will be canceled. Once the registration process is completed for a student,
the registration system sends
information to the billing system, so the student can be billed for the semester.

This system is designed in such a way that Professors must be able to access the on-

line system to indicate which courses they will be teaching. They will also need to

see which students signed up for their course offering. For each semester, there is a

period of time that students can change their schedules. Students must be able to

access the on-line system during this time to add or drop courses. The billing

system will credit all students for courses dropped during this period of time.’
6. Data Flow Diagram

Student

Request catalog

Register

View payments
Enter payments

View Student ,course 0

Enter Student detials Student

Registration
Registerar System

See Course
Select Course

Professor

Level Zero Data Flow Diagram

 Student
Courses records

View registerted course

register
Registerar

2.0
submited
Course
registers views

teach
1.0

Register
Students

Professor

records

3.0
Students record

Enter

Professor database

Level one Data Flow Diagram

7. E-R Diagram
firstName lastName
firstName lastName
phone Address
firstName phone
name Address
phone
Address
lastName name name
ID
Registrar

Admin ID
adminNo registerrarNo Professor
1

manage

manage

manage
courseName
M
Discription
address M M
phone
firstName startDa te M
courseNo
price
dateRegister endDate
lastName name

M train

studID
Student M register M Course

work_in

Address

in name
location
phone
1
name
collegeID
departmentID
contian 1
M college
Department
8. Use Case Diagram

Student Registration System

createNewCourse
<<extend>>
manage <<extend>> ModifyCourse
course
<<extend>>

RemoveCourse

manage <<extend>> add student see signed Student to course

Student
Admin
<<extend>>

delete
student add teacher
<<extend>>

manage
Professor <<extend>>
remove teacher
Professor

Dispaly Course

login and logout from system

view course
update My profile offering roster

reset password

Student add Course Registrar

select course to teach

drop course

payment
viewRegisteredCourse

Generate course catalogue

billing
 9. Class Diagram
<<data Type>>
Address Registerar
city -registerarNo:String
Dist
streetname -userName:String
housenumber -firstName:String
1 -lastName:String 1
-password:String
-email:String
+login():void
+resetPassword():bool
+getName():String
1….*
+logout():void
+addRegisterar():void
Professor
Admin +updateRegisterar():void
1 1 -professorNo:Integer
-adminNo:Integer -firsrName:String
-firsrName:String -lastName:String
-lastName:String -phone:String
-phone:String 1….* -nationalID:String
-nationalID:String manage
-address:String
1…..*
maintian
+login( -email:String
angeLanguage():void -userName:String
+logout():void -password:String
+login()
teach +addProfessor()
1 maintian +editProfessor()
+deleteProfessor()
++register():void
+resetPassword():bool
1…..* +getName():String

Course
RegisteratedCourse 0….*

manage
-courseNo:int
-registrationNo:int -courseName:date
-registrationDate:date -discription:int
1
-startCourse:String -price:int
-endCourse:int 1…..6
+addregistration:void +addCourse():void
+t():void +removeCouse():void
+editPayment():void +updateCourse:void
+setAmount(double ):void +setPrice(double ):void
+():double +getPrice():double
1….*
+cancelregistration():void

1….* 0…..*

Student
-studentID:int payment
-firstName:String
-lastName:String -paymnetNo:int
-phone:String -makeDate:date
-address:Addres -cardNumber:String
-birthDate:date 1 -costNo:int
1….* -email:String -mount:double
+login():void +addpayment():void
+addStudent():void +deletepayment():void
+updateStudent():void +editPayment():void
0…..*
+removeStudent():void +setAmount(double ):void
+setAddress(Address ):void +getAmount():double
+getAddress():Address +getCardNumber():String
+viewRegisteretedCourse():void 0….*
++register():void
1
+resetPassword():bool
+getName():String
+logout():void
1