Table of Contents 2. Introduction 1 2.1 Purpose 1 2.2 Scope 1 2.3 Definitions, Acronyms, and Abbreviations 1 2.4 References 1 2.5 Overview 1 3. General Description 2 3.1 Product Perspective 2 3.2 Product Functions 2 3.3 User Characteristics 3 3.4 General Constraints 4 3.5 Assumptions and Dependencies 4 4. Specific Requirements 4 4.1 External Interface Requirements 4 4.1.1 User Interfaces 4 4.1.2 Hardware Interfaces 4 4.1.3 Software Interfaces 4 4.1.4 Communications Interfaces 4 4.2 Functional Requirements 4 4.3 Use Cases 7 4.4 Classes 8 4.5 Non-Functional Requirements 9 4.5.1 Performance 9 4.5.2 Reliability 9 4.5.3 Scalability 9 4.5.4 Security 9 5. Analysis Models 9 5.1 Sequence Diagrams 9 5.2 Collaboration Diagrams (STD) 10 5.2 State-Transition Diagrams (STD) 11 5.4 ACTIVITY DIAGRAM……………………………………………………………………………………….15 5.5 DEPLOYMENT DIAGRAM…………………………………………………………………………………15

2. Introduction
The Online Student Course registration system is automated system where the user can register the student for various courses. This is proposed for automating the student’s course registration. While the student joins any educational institution his admission is made on the basis of his previous records. The students who wish to the institution must be given with the available course details. The student is allotted with a seat in the institution based on the marks that he scored in the institution he studied previously. After the confirmation of his joining the student must be given with new identity and records as per the institution.
2.1 Purpose The purpose of this document is to present a detailed description of the Online Course Registration System. It will explain the purpose and features of the system, the interfaces of the system will do, the constraints under which it must operate and how the system will react to external factors. This document is intended for both stakeholders and developers of the system. 2.2 Scope The Online Course Registration System will enable students to register for courses on-line. The Online Course Registration System allows professors to select their teaching courses and to maintain student grades. Course Registration System will help the student to gather information about a particular course and then they can easily register them self in a particular course.The management of the institution can easily see the records of the students and course and fees.
2.3 Definitions, Acronyms, and Abbreviations
CRS: Course Registration System.
AIS : Academic Information System.
SIS : Student Information System.
2.4 References www.google.com , www.scribd.com , www.docsfiles.com. 2.5 Overview
The third chapter, the General Description section, of this document gives an overview of the functionality of the product. It describes the informal requirements and is used to establish a context for the technical requirements specification in the next chapter.
The fourth chapter, Specific Requirements section, of this document is written primarily for the developers and describes in technical terms the details of the functionality of the product.
The fifth chapter, Analysis Model describes the internal functionality of the online course registration system using diagrammatic representations.
3. General Description
3.1 Product Perspective
The system will be operate within university environment. This environment has another systems that will interact with this system so we need interfaces between this systems.

Student information system

Registration system
Database system
Course Registration system

Academic information system

Fig:
3.2 Product Functions
3.2.1. The system shall be able to Access Courses.

student
Select Course

instructor
Update course

Fig: 3.2.2 The system shall support Group Registration features

Access Course
Select Course
Payment
Student
Create Account

Fig:

3.2.3 The system allows admin to modify courses
Registrar
Add Course
Delete Course

Fig:
3.3 User Characteristics
The student expected to be Internet literate Once he/she can log in the system and navigate between WebPages he/she can use basic functionality of the system.
Instructor expected to be internet literate and be able use more complex functionality of the system.
3.4 General Constraints
3.4.1 The system must run in windows operating system environment.
3.4.2 The system shall use mysql database for all data management tasks.
3.4.3 A student cannot register a course if: 1) he/she doesn’t passed with 65% of marks, 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.
3.4.4 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.
3.5 Assumptions and Dependencies The number of Students for a same course exceeds than the allocated size,then their registration can be cancelled automatically by the institution .First come first served and their admissions are based on the institution’s perspectives. 4. Specific Requirements
4.1 External Interface Requirements
4.1.1 User Interfaces The system must interfaces icons or wizard. The GUI screen makes the user friendly.
4.1.2 Hardware Interfaces * Intel Pentium 4 * 1 GB RAM * 50 GB Hard Disk * 1 Network Interface Card (NIC) 4.1.3 Software Interfaces * Windows 7 / XP * IE Browser 8 / Mozilla Firefox * Netbeans * MS SQL Server 2005 * Language : Java(jdk 1.6)
4.1.4 Communications Interfaces The System is User Interface rather than command line prompt.
4.2 Functional Requirements
The Online Course Registration System will replace the existing mainframe course registration system. The new system will interface with the existing Billing System and Course Catalog Database System as shown in the context diagram below:

4.2.1 Logon
Students, professors, and the Course Registrar shall provide a valid ID and password for entry to the C-Registration System. Users are assigned their ID and a temporary password at the time they apply for admission to the College. The system shall enable a user to change their temporary password.
4.2.2 Register for Courses
The system shall display available courses to the student upon request. The student shall be able to query based upon course name, course code, and department. The system shall accept course registrations from students and shall validate based upon course availability, schedule conflicts, and completed pre-requisite courses. The system shall notify the student immediately if the course registration does not succeed. The system shall allow the student to change course selections prior to the end of the registration period.
4.2.3 Course Cancellations
The system shall allow the Registrar to cancel courses. The Registrar typically reviews all courses at the end of the registration period and cancels courses that have no assigned Professor or which have less than 3 registered students. The Course Registrar notifies students of cancelled courses by telephone or mail.
4.2.4 Student Billings
The system shall send notifications to the Billing System following closure of the Registration period. These notifications shall include student name, address, course selections, and payment due.
4.2.5 Enter, Update, and View Professor Information
The system shall accept and update professor information, including name, address, phone, fax, and email address. Professor information shall be available to the Professors and Course Registrar for viewing.
4.2.6 View Student Grades
The system shall enable a student to view one course grade or their entire report card. The system shall protect the student grade information from access from any user other than the student and the Professors.
4.2.7 Select Courses to Teach
The system shall enable Professors to sign up for courses to teach prior to the end of the Registration period.
4.2.8 Enter, Update, and View Student Information
The system shall accept and update student information, including student ID, name, address, phone number, and email address. Student information shall be available to the Professors and Course Registrar for viewing. The system shall ensure that a student only has access to his or her own student information. The Registrar maintains student information.
4.2.9 View Course Catalog Information
The course catalog information maintained in the Course Catalog Database shall be displayed to the user upon request. Users shall be able to query for information based upon course name, course code, professor name, and department.
4.3 Use Cases

Fig:

4.3.1 Register for courses The use case is started by the student. It provides the capability to create, review, modify, and delete a course schedule for a specified semester. All pertinent billing information is sent to the Billing System.

4.3.2 Register for class This use case is started by the professor. It provides the capability to request a printed list of all students assigned to a specified course offering.

4.3.3 Select courses to teach This use case is started by the professor. It provides the capability to select, review, modify, and delete a list of courses to teach for a specified semester.

4.3.4 Maintain student information This use case is started by the registrar. It provides the capability to create, review, modify, and delete student information.
4.3.5 Generate Catalogue This use case is started by the registrar. It provides the capability to generate a catalogue containing a list of course offerings for a specified semester.
4.4 Classes The course registration system is made up of Course, Course maintenances, Course Selection, Registration Form, Add/Remove Course Form, Student, Course offering, Course Roaster and Student Schedule Classes. Of all the Packages, this Package is much more important because this is where student course registration is carried out as well as add and removal or drop of course as necessary. The individual classes are all self-explanatory in the role they play in the entire system.

Fig:

4.5 Non-Functional Requirements
4.5.1 Performance
1.The system shall support up to 2000 simultaneous users against the central database at any given time, and up to 500 simultaneous users against the local servers at any one time.
2.The system shall provide access to the legacy course catalog database with no more than a 10 second latency.
4.5.2 Reliability
The system shall be available 24 hours a day 7 days a week. User can access at anytime.
4.5.3 Scalability
Scaling the system to large number of users: large courses will have hundreds of students.
4.5.4 Security
1. The system must prevent students from changing any schedules other than their own, and professors from modifying assigned course offerings for other professors.
2. Only Professors can enter grades for students.
3. Only the Registrar is allowed to change any student information.

5. Analysis Models
5.1 Sequence Diagrams
The Sequence Diagram shows all sequential steps involved in registering courses by the students. The steps involved in doing this as regards this Sequence Diagram are detailed below:

1.The Registrar Opens Course Registration to student’s and this is made available as Registration Form.
2.The students visits the web Registration Portal to Pick and fill up course registration form
3.After filling up course form, they apply for courses through the Registration Manager.
4.The Registration Manager Forwards the List of Registered students to both the Registrar and Bursary or Billing System.
5.The Billing System the Prepares Bill for the registered Students.
6.The prepared bills are issued to the registered students.
7.In return the Registered Students Pay up bills.
8.On the conformation of bill payment, the students become qualified and can attend classes.

Fig:
5.2 Collaboration Diagram

Fig:
5.3 State-Transition Diagrams (STD)

Fig:
These state chart diagram represents the student and lecturer login information to be verified by the registrar.

Fig:

These State chart diagram represents the student’s selection process of the course. The course is available according to the class availability of students.

Fig:

These diagram represents the registering of subjects by the lecturers. If the lecturer doesn’t having the skill set then he will not allowed to handle that subject.
5.4 Activity Diagram

Fig:

5.5 Deployment Diagram

Fig: