Aim: To create a system through which students can register to the courses desired by them

Procedure:Problem statement

The system is built to be used by students and managed by an administrator. The student and employee have to login to the system before any processing can be done. The student can see the courses available to him/her and register the course he/she wants. The administrator can maintain the course details and view all the students who have registered to any course.

(II)Software Requirements Specification

Introduction

Course Reservation System is an interface between the Student and the Registrar responsible for the issue of Course. It aims at improving the efficiency in the issue of Course and reduces the complexities involved in it to the maximum possible extent.

Purpose

If the entire process of ‘Issue of Course’ is done in a manual manner then it would take several months for the course to reach the applicant. Considering the fact that the number of applicants for course is increasing every year, an Automated System becomes essential to meet the demand. So this system uses several programming and database techniques to elucidate the work involved in this process.

Scope

• The System provides an online interface to the user where they can fill in their personal details and submit the necessary documents (may be by scanning).
• The Registrar concerned with the issue of course can use this system to reduce his workload and process the application in a speedy manner.
• Provide a communication platform between the Student and the Registrar.

Definitions, acronyms and the abbreviations

• Registrar: Refers to the super user with the privilege to manage the entire system.
• Applicant: One who wishes to register the Course.
• OCRS: Refers to online Course Reservation System.
• HTML: Markup Language used for creating web pages.
• J2EE: Java 2 Enterprise Edition is a programming platform java platform for developing and running distributed java applications.
• HTTP: Hyper Text Transfer Protocol.
• TCP/IP: Transmission Control Protocol/Internet Protocol is the communication protocol used to connect hosts on the Internet.

Technologies to be used

• HTML
• JSP
• JavaScript
• Java

Tools to be used

• Eclipse IDE (Integrated Development Environment)
• Rational Rose tool (for developing UML Patterns)

Overview

SRS includes two sections: overall description and specific requirements. Overall Description will describe the major role of the system components and inter-connections. Specific Requirements will describe roles & functions of the actors.

Overall Description

Product perspective

The OCRS acts as an interface between the Student and the ‘Registrar’. This system tries to make the interface as simple as possible and at the same time not risking the security of Data stored in. This minimizes the time duration in which the user receives the course.

Software interface

• Front End Client: The Student and Registrar online interface is built using JSP and HTML. The Administrator’s local interface is built using Java.
• Web Server: Tomcat Apache application server (Oracle Corporation).
• Back End: Oracle 11g database.

Hardware interface

The server is directly connected to the client systems. The client systems have access to the database in the server.

System functions

• Secure Reservation of information by the Students.
• SMS and Mail updates to the students by the Registrar.
• Registrar can generate reports from the information and is the only authorized personnel to add the eligible application information to the database.

User characteristics

• Applicant: They are the person who desires to obtain the course and submit the information to the database.
• Administrator: He has certain privileges to add the course status and to approve the issue of course. He may contain a group of persons under him to verify the documents and give suggestions whether or not to approve the dispatch of course.

Constraints

• The applicants require a computer to submit their information.
• Although security is given high importance, there is always a chance of intrusion in the web world which requires constant monitoring.
• The user has to be careful while submitting the information. Much care is required.

Assumptions and dependencies

• The Applicants and Administrator must have basic knowledge of computers and English Language.
• The applicants may be required to scan the documents and send.

(III) Use-case diagram

The course registration system has the following use-cases:

1. Login
2. View course details
3. Reserve for course
4. Pay fee
5. Check status

Actors involved

1. Student
2. Registrar

Use case name: Login

The user enters the username and password and chooses if the user is student or Registrar. If entered details are valid, the user’s account becomes available. If it is invalid, an appropriate message is displayed to the user.

Use case name: View course details

In this use case, a student can search all the courses available to him and choose the best course he wants. The student can view the course duration, faculty, and department of the courses he may choose.

Use case name: Reserve for course

When a student has successfully chosen a course, he can register for that course. Upon registration, the student’s details are stored in the database.

Use case name: Pay fee

After registration to any course, the student may see the details of his current course. He may wish to know details about fees and other information.

Use case name: Check status

The student tries to check the status in which category applied. The system displays the status information to the student.

Activity Diagram

Class Diagram

The class diagram is a graphical representation of all the classes used in the system and their operations, attributes, and relationships. The course registration system makes use of the following classes:

1. Student
2. Course Catalog
3. Reserve Course

1) Student

It consists of the details of all the students present in the database. The attributes present in this class are student id, student name, student qualification, student address1, student address2, student address3, student mobile no, student email, student dob, student sex. The object of this class is created as soon as the student registers for a course. The operations available to this class are add details(), modify details(), del details(), reserve course().

2) Course Catalog

The course catalog class consists of course id, course name, course duration, course fee, course eligibility, total no of seats, course available seats. The operations are add course(), update course(), del course().

3) Reserve Course

The reserve catalog class consists of student id, course id, date, amt paid, reg id, DD no. The operations are get course details(), check eligibility(), confirm registration().

Interaction Diagram

• A sequence diagram represents the sequence and interactions of a given use-case or scenario. Sequence diagrams can capture most of the information about the system. Most object-to-object interactions and operations are considered events, and events include signals, inputs, decisions, interrupts, transitions, and actions to or from users or external devices.
• An event is also considered to be any action by an object that sends information. The event line represents a message sent from one object to another, in which the “from” object is requesting an operation be performed by the “to” object. The “to” object performs the operation using a method that the class contains.
• It is also represented by the order in which things occur and how the objects in the system send messages to one another.
• The sequence diagram for each use-case that exists when a user administrator checks status and new registration about the course registration system are given.
• Users have to first log in to the system before performing any operation. The user has to provide the necessary details to the system for login.

  

State Chart Diagram

Every object undergoes some state and on receiving some event the state gets changed. This transition of the state can be represented by the state transition diagram.

Deployment Diagram and Component Diagram

Deployment diagrams are used to visualize the topology of the physical components of a system where the software components are deployed.

Component Diagram

Component diagrams are used to visualize the organization and relationships among components in a system.