+ All Categories

anbu

Date post: 23-Nov-2014
Category:
Upload: sridaran-vijayaraghavachari
View: 172 times
Download: 0 times
Share this document with a friend
Popular Tags:
32
ONLINE COURSE REGISTRATION SYSTEM SCOPE The need for structured storage, modification and maintenance of huge amounts of data has resulted in the emergence of the Database Management System (DBMS) as one of the core fields in the Computer Science industry. DBMS is the system of computer software that is aimed to provide a managing tool for maintaining the data, through various data models. The purpose of implementing this project is to understand the data modeling concepts that is used in a real time scenario and to implement a fully functional database system which interacts with a front end interface AUDIENCE The intended users are student apply for the course. ORGANISATION The document describes the student analysis system requirements in terms of system requirements, executive summary, analysis, and design diagrams. SYSTEM REQUIRMENT AND SPECIFICATION The following subsection describes the student analysis system requirements specification in terms of problem statement and feasibility studies. Step 1: PROBLEM STATEMENT
Transcript
Page 1: anbu

ONLINE COURSE REGISTRATION SYSTEM

SCOPE

The need for structured storage, modification and maintenance of huge amounts of data has resulted in the emergence of the Database Management System (DBMS) as one of the core fields in the Computer Science industry. DBMS is the system of computer software that is aimed to provide a managing tool for maintaining the data, through various data models. The purpose of implementing this project is to understand the data modeling concepts that is used in a real time scenario and to implement a fully functional database system which interacts with a front end interface AUDIENCE

The intended users are student apply for the course.

ORGANISATIONThe document describes the student analysis system requirements in terms of system

requirements, executive summary, analysis, and design diagrams.

SYSTEM REQUIRMENT AND SPECIFICATION

The following subsection describes the student analysis system requirements specification in terms of problem statement and feasibility studies.

Step 1: PROBLEM STATEMENT

An Online Course Reservation system for Sri Sai Ram Engineering College is to be developed with a front-end web interface and a back-end database. An example of the system would be Sri Sai Ram Engineering College’s Course Registration System. Any database system can be chosen as the back-end such as Oracle, MySQL, Microsoft SQL Server, DB2, Access But the data base system used here MS access Any web server can be chosen for the front end such as Tomcat, Glassfish, etc but here basic HTML is used.. Any server side language can be chosen such as PHP, JSP, ASP, etc. but here JAVA is used.

Step 2: PROJECT SPECIFICATION

A high level description of the project:

• Each student has a unique student ID and a profile. The profile includes first/last names, gender,date of birth, local address, department, enrolled year, username, login password, and may have a picture. You can also add other necessary information.

Page 2: anbu

• 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. • A department 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. • 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. • A student cannot register a course if: 1) he/she doesn’t 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: 1) the classroom has already occupied by another course in the same period, 2) he/she has another course in the same period, 3) 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

MAJOR DESIGN CONDITIONS Major design decisions in the project were discussed and entered in a shared online

Google document so that as and when someone thinks of a new idea for bonus functionality we were able to add in the document and share it with the other person (2 in a team). The design schema and other field information were also stored and work performed on a day-by-day basis was logged so that we were aware on the progress of the project. 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 class room 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

Page 3: anbu

student requests that he wants to graduate to the Grad Advisor in his department and the Advisorrequests DB Administrators to update the student’s `graduated` field.

FUNCTIONALITIES OF A STUDENT

- Register a course - Constraints checked here include •MAX courses registered this semester, in our system its 4, • 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 - Drop course option is provided on this page - Can view additional information about the courses he has taken. . - Can view courses with prerequisite information - Can also request for graduation, we have enforced a minimum of 10 courses for a student to graduate, If this request is not met the graduation request is denied else it if forwarded to the graduate advisor.

FUNCTIONALITIES OF AN INSTRUCTOR

Can view current schedule in a tabular format- Can edit Course details - Details such as Seats left - to increase or decrease the capacity of the course (seats cannot be more than class capacity) - Can add a new course to the database under his profile and department. - The input parameters in the form are checked for valid input data before updating the database. - Conflicts with the instructor's schedule as well as conflicts in timing with other courses in the same classroom are checked. - Can view classroom availability as well as maximum capacity of classroom when course information is updated or new classroom is added -Instructor can view info of all the students registered in the courses he/she is handling.IMPLEMENTATION METHODS

The Online Course Registration project was implemented successfully using the Apache Server with MySQL running as the back end database and PHP used as the server side language. The implementation methods were chosen carefully taking into consideration the possibilities of hosting this project online in a server after the semester. Several high profile hosting companies support mySQL and PHP. Comparisons can be drawn later based on performance, execution time, efficiency, memory usage by implementing the system in different servers with various

Page 4: anbu

traffic load.

Step3: UML USE CASE MODELA use-case diagram is a graph of actors, a set of use cases enclosed by a system boundary, communication associations between actors and the use cases and generalization among use cases.

Description of use case and actorsThe Online Course Reservation System is used by the students.

Actor name: Student

Page 5: anbu

Description: The actor must be able to enter the data and reserve the particular course and register for that particular course.

Package name: Course Reservation SystemIt includes the following use cases.

Use Case Name: Course Pamplet

Description: Course Pamplet is followed about a Two types.

1.Engineering Course:

Engineering Course followed about 3 types.

1.Mechanical Engineering

2.Electronics And Communication Engineering

3.Electronics And Electrical Engineering

2.Technology Course: 1.Information Technology

2.Computer Science Engineering

Use Case Name: Registration

Description: The User Fills the Registration Form and Select Required Course.

Use Case Name: Manintain Detail

Two Types:` 1.Student Detail: The Student Detail are finally Stored in the DataBase.

2.Instructor Detail: The Instructor Detail Stored in the DataBase.

Page 6: anbu

Step 4: ACTIVITY DIAGRAM FOR A BUSINESS PROCESSAn activity diagram is a variation or special case of state machine, in which the states are

activities representing the performance of operations and transitions are triggered by the process. completion of the operations. An activity diagram models the entire business

Page 7: anbu
Page 8: anbu

Step 5: UML CLASS DIAGRAMS

SUPER CLASS:The superclass for Online Course Reservation System is the Information.

SUBCLASSThe subclass includes

Course User

CLASS DIAGRAM:

Page 9: anbu
Page 10: anbu

Step 6: UML INERACTION DIAGRAMSA.5.1 SEQUENCE DIAGRAMSequence diagrams are an easy and intuitive way of describing the behavior of the system by viewing the interaction between the system and its environment. A sequence diagram shows the objects participating in a time sequence. It shows the objects participating in an interaction by their lifelines an the messages they exchange, arranged in a time sequence.

Page 11: anbu

SEQUENCE DIAGRAM:

A.5.2 COLLABORATION DIAGRAMA collaboration diagram represents a collaboration, which is a set of objects related in a particular context, and interaction, which is a set of objects within the collaboration, to achieve a desired outcome.

Page 12: anbu

Step 8: PACKAGE DIAGRAM:A package is a group of modeling elements. It may contain both subordinate packages and ordinary model elements. The entire system can be thought of as a single high-level package , with all the uml diagrams organized within it. It is used to designate the logical , physical and also the use case groups.

Page 13: anbu

Step 12: COMPONENT AND DEPLOYMENT DIAGRAMS:

CODING:

Form 2:Private Sub Command1_Click()Me.HideForm12.Show

End Sub

Private Sub Command2_Click()Me.HideForm13.Show

End Sub

Form 12:Private Sub Command1_Click()If Text1(0).Text = "admin" And Text2.Text = "admin" ThenForm2.ShowElseMsgBox ("Invalid password")End If

End SubForm 13:

Private Sub Command1_Click()Me.HideForm3.Show

End Sub

Page 14: anbu

Form 3:Private Sub It_Click()End Sub

Private Sub Command1_Click()Me.HideForm1.Show

End Sub

Private Sub Label2_Click()Me.HideForm4.ShowEnd Sub

Private Sub Label3_Click()Me.HideForm5.Show

End Sub

Private Sub Label6_Click()Me.HideForm8.Show

End Sub

Private Sub Label7_Click()Me.HideForm9.Show

End Sub

Form 1:

Private Sub Command1_Click()'If Text1.Text = "" Or Text2.Text = "" Or Combo1.Text = "" Or Combo2.Text = "" Or Text4.Text = "" Then'MsgBox "enter all the fields"

Page 15: anbu

'End If'Command2.SetFocus

If Combo1.Text = "ECE" ThenIf Combo2.Text = "OC" And Text2.Text >= "198" And Text2.Text <= "200" ThenMsgBox "registered successfully"Adodc1.Recordset.Update'Form1.Refresh'Me.HideElseIf Combo2.Text = "BC" And Text2.Text >= "195" And Text2.Text <= "200" ThenMsgBox "registered successfully"Adodc1.Recordset.Update'Form_load()

'Me.HideElseIf Combo2.Text = "MBC" And Text2.Text >= "190" And Text2.Text <= "200" ThenMsgBox "registered successfully"Adodc1.Recordset.UpdateForm1.Refresh'Me.HideElseIf Combo2.Text = "SC" And Text2.Text >= "190" And Text2.Text <= "200" ThenMsgBox "registered successfully"Adodc1.Recordset.UpdateForm1.Refresh

'Me.HideElseMsgBox "invalid cutoff"Adodc1.RefreshForm1.Refresh'Me.HideEnd IfEnd IfEnd IfEnd If

ElseIf Combo1.Text = "EEE" ThenIf Combo2.Text = "OC" And Text2.Text >= "195" And Text2.Text <= "200" Then

MsgBox "registered successfully"Adodc1.Recordset.Update

Page 16: anbu

Form1.RefreshElseIf Combo2.Text = "BC" And Text2.Text >= "190" And Text2.Text <= "200" ThenMsgBox "registered successfully"Adodc1.Recordset.UpdateForm1.RefreshElseIf Combo2.Text = "MBC" And Text2.Text >= "189" And Text2.Text <= "200" ThenMsgBox "registered successfully"Adodc1.Recordset.UpdateForm1.RefreshElseIf Combo2.Text = "SC" And Text2.Text >= "185" And Text2.Text <= "200" ThenMsgBox "registered successfully"Adodc1.Recordset.UpdateForm1.RefreshElseMsgBox "invalid cutoff"Adodc1.RefreshForm1.Refresh'Me.HideEnd IfEnd IfEnd IfEnd IfCommand3.SetFocusElseIf Combo1.Text = "CSE" ThenIf Combo2.Text = "OC" And Text2.Text >= "193" And Text2.Text <= "200" ThenMsgBox "registered successfully"Adodc1.Recordset.UpdateForm1.RefreshElseIf Combo2.Text = "BC" And Text2.Text >= "189" And Text2.Text <= "200" ThenMsgBox "registered successfully"Adodc1.Recordset.UpdateForm1.RefreshElseIf Combo2.Text = "MBC" And Text2.Text >= "185" And Text2.Text <= "200" ThenMsgBox "registered successfully"Adodc1.Recordset.UpdateForm1.RefreshElseIf Combo2.Text = "SC" And Text2.Text >= "183" And Text2.Text <= "200" ThenMsgBox "registered successfully"Adodc1.Recordset.Update

Page 17: anbu

Form1.RefreshElseMsgBox "invalid cutoff"Adodc1.RefreshForm1.Refresh'Me.HideEnd IfEnd IfEnd IfEnd IfCommand3.SetFocusElseIf Combo1.Text = "IT" ThenIf Combo2.Text = "OC" And Text2.Text >= "190" And Text2.Text <= "200" ThenMsgBox "registered successfully"Adodc1.Recordset.UpdateForm1.RefreshElseIf Combo2.Text = "BC" And Text2.Text >= "185" And Text2.Text <= "200" ThenMsgBox "registered successfully"Adodc1.Recordset.UpdateForm1.RefreshElseIf Combo2.Text = "MBC" And Text2.Text >= "181" And Text2.Text <= "200" ThenMsgBox "registered successfully"Adodc1.Recordset.UpdateForm1.RefreshElseIf Combo2.Text = "SC" And Text2.Text >= "178" And Text2.Text <= "200" ThenMsgBox "registered successfully"Adodc1.Recordset.UpdateForm1.RefreshElseMsgBox "invalid cutoff"Adodc1.RefreshForm1.Refresh'Me.HideEnd IfEnd IfEnd IfEnd IfCommand3.SetFocusEnd IfEnd IfEnd IfEnd If

Page 18: anbu

Adodc1.RefreshEnd Sub

Private Sub Command2_Click()EndEnd Sub

Private Sub Command3_Click()Adodc1.Recordset.UpdateDataReport1.ShowAdodc1.RefreshEnd Sub

Private Sub Form_Load()Combo1.AddItem "ECE"Combo1.AddItem "EEE"Combo1.AddItem "IT"Combo1.AddItem "CSE"Combo2.AddItem "BC"Combo2.AddItem "MBC"Combo2.AddItem "SC"Combo2.AddItem "OC"Text1.Text = ""Text2.Text = ""Text4.Text = ""

End SubForm 4:

Private Sub Command1_Click()Me.HideForm3.Show

End Sub

Form 5:Private Sub Command1_Click()Me.HideForm3.Show

End SubForm 6:

Private Sub Command1_Click()

Page 19: anbu

Me.HideForm3.Show

End SubForm 7:

Private Sub Command1_Click()Me.HideForm3.Show

End Sub

Page 20: anbu
Page 21: anbu
Page 22: anbu
Page 23: anbu
Page 24: anbu
Page 25: anbu
Page 26: anbu
Page 27: anbu

Recommended