Procedure (I) Problem statement

Exam Registration system is used in the effective dispatch of registration form to all of the students. This system adopts a comprehensive approach to minimize the manual work and schedule resources, time in a cogent manner. The core of the system is to get the online registration form (with details such as name, reg. no etc.,) filled by the student whose testament is verified for its genuineness by the Exam Registration System with respect to the already existing information in the database. This forms the first and foremost step in the processing of exam application. After the first round of verification done by the system, the information is in turn forwarded to the exam Controller. The application is then processed manually based on the report given by the system. The system also provides the student the list of exam dates. The controller will be provided with fees details to display the current status of application to the student, which they can view in their online interface. After all the necessary criteria have been met, the original information is added to the database and the hall ticket is sent to the student.

(II)Software requirements specification

Introduction

Exam Registration System is an interface between the Student and the Exam Controller responsible for the Issue of Hall Ticket. It aims at improving the efficiency in the Issue of Hall ticket and reduces the complexities involved in it to the maximum possible extent.

Purpose

If the entire process of ‘Issue of Hall ticket’ is done in a manual manner then it would take several days for the hall ticket to reach the student. Considering the fact that the number of students for hall ticket 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. As this is a matter of National Security, the system has been carefully verified and validated in order to satisfy it.

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 controller concerned with the issue of hall ticket 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 controller. Students will come to know their status of application and the date in which they must subject themselves for annual document verification.

Definitions, acronyms and the abbreviations

• Exam Controller – Refers to the super user who is the Central Authority who has been vested with the privilege to manage the entire system.
• Student – One who wishes to obtain the Hall Ticket.
• ERS – Refers to this Examination Registration 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 ERS acts as an interface between the ‘student’ and the ‘exam controller’. 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 hall ticket.

Software interface

• Front End Client – The exporter online interface is built using JSP and HTML.
• Web Server – Apache Tomcat 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 Registration of information by the Students.
• SMS and Mail updates to the students by the controller.
• Controller can generate reports from the information and is the only authorized personnel to add the eligible application information to the database.

User characteristics

• Student – They are the people who desire to obtain the hall ticket and submit the information to the database.
• Exam Controller – He has certain privileges to add the registration status and to approve the issue of hall ticket. He may contain a group of persons under him to verify the documents and give suggestions whether or not to approve the dispatch of hall ticket.

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 Students and Exam Controller must have basic knowledge of computers and the English Language.
• The student may be required to scan the documents and send.

(III) Use case diagram

The Exam Registration use cases in our system are:

• Login
• View exam details
• Register
• Acknowledgement
• Fee Processing

Actors involved

• Student
• System DB

Use case name: Login

The student enters his username and password to login and retrieve the information.

Use case name: View exam details

The student views the details about the exam schedule which contains Date, time, etc.

Use case name: Register

The student should notify the fee details that only the student can pay the correct amount.

Use case name: Acknowledgement

The exam fees should be paid by the student to get the hall ticket from the exam controller.

Use case name: Fee processing

All the details should be viewed by both the student and the controller to verify whether all the entered details are correct.

Activity diagram

Class diagram

The class diagram, also referred to as object modeling, is the main static analysis diagram. The main task of object modeling is to graphically show what each object will do in the problem domain. The problem domain describes the structure and the relationships among objects.

The Exam Registration System class diagram consists of four classes of the registration system:

Student Details

It consists of six attributes and six operations. The attributes are id, password, name, age, sex, course. The operations of this class are login(), logout(), confirmation(), register(), new fees details().

Exam Details

It consists of four attributes and six methods. The attributes are userid, password, exam fees, fees due. The methods are login(), logout(), fees details(), display fees(), confirmation(), exam controller().

Register

This class is used to maintain the registered student information such as subject registered, date of registration, etc.

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 and collaboration diagram represent that the student enters the information to get the hall ticket, and the exam controller issues the hall ticket after verifying the necessary items, and this data is stored in the database.

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.