INSTITUTE FOR ADVANCED COMPUTING AND SOFTWARE DEVELOPMENT AKURDI, PUNE

SRS ON ONLINE STUDENT MANAGEMENT SYSTEM DAC-Aug-2013

Submitted By: Group No: 22 Priyanka Patil Sumit Nikode Swapnil Thakur Kumudini Tadge

Mr. Dhananjay N. Patil Course Coordinator

Mr. Milind Arjun Project Guide

Table of Contents
List of Figures..................................................................................................... 2 1.0. Introduction ................................................................................................ 1 1.1 1.2 1.3 Purpose ...................................................................................................................... 3 Scope of Project ......................................................................................................... 4 Overview of Document .............................................................................................. 4

2.0.Overall Description ....................................................................................... 6 2.1 2.2 2.3 2.4 System Environment ............................................................................................. 6 Functional Requirements Specification .............................................................. 7 User Characteristics............................................................................................ 10 Non-Functional Requirements .......................................................................... 10

3.0. Requirements Specification ........................................................................ 11 3.1 3.2 External Interface Requirements ....................................................................... 11 Functional Requirements..Error!

Bookmark not defined. 3.2.1 3.2.2 3.2.2 3.2.3 3.2.4 3.3 Student Login .................................................Error! Bookmark not defined. Display Notice Board.... Apply for Exam..............................................Error! Bookmark not defined. Apply for Leave .............................................Error! Bookmark not defined. Edit profile .....................................................Error! Bookmark not defined.

Detailed Non-Functional Requirements ............................................................ 11 3.3.1 3.3.2 Logical Structure of the Data ........................................................................ 11 Security ..........................................................Error! Bookmark not defined.

Index ............................................................... Error! Bookmark not defined.

List of Figures: Figure 1 Use case ............................................................................................................. 7 Figure 2 - DFD .................................................................................................................. 23 Figure 3 - ERD .................................................................................................................. 25

Introduction

1.1. Purpose

The student management system is an automated version of manual Student Management System. It can handle all details about a student. The details include college details, subject details, student personnel details, academic details, exam details etc. In case of manual system they need a lot of time, manpower etc. Here almost all work is computerized. So the accuracy is maintained. Maintaining backup is very easy. It can do with in a few minutes. Our system has two type of accessing modes, administrator and user. Student management system is managed by an administrator. It is the job of the administrator to insert update and monitor the whole process. When a user log in to the system. He would only view details of the student. He can't perform any changes .The system has five modules. They are Login and subject Student Details Notice board Online leave application Online Exam Management One module is aimed at developing an online leave management system that is of importance to a college. The Leave Management System (LMS) is an Intranet based application that can be accessed throughout the College or a specified group/Dept. This system can be used to automate the workflow of leave applications and their approvals. The periodic crediting of leave is also automated. There are features like email notifications, cancellation of leave, automatic approval of leave, report generators etc in this system.

The purpose of on-line test simulator is to take online test in an efficient manner and no time wasting for checking the paper. The main objective of on-line test simulator is to efficiently evaluate the candidate thoroughly a fully automated system that not only saves lot of time but also gives fast results. For students they give papers according to their convenience and time and there is no need of using extra thing like paper, pen etc.

1.2. Scope of Project Student Management System is web based application which tracks all the details of a student throughout the end of his course which can be used for all reporting purpose. Others modules: Student can see noticeboard from anywhere, Student can send leave to coordinator and wait for reply whether approved or leave is rejected. This can be used in educational institutions as well as in corporate world. Can be used anywhere any time as it is a web based application (user Location doesnt matter).No restriction that examiner has to be present when the candidate takes the test. Student cap edit profile.

Initial functional requirements will be: The system shall enable students to retrieve contact information of students. The system shall allow students to edit their personal information. The system shall allow students to send leave application to coordinator. The system shall notify students of events (posted news messages, team Invites and scheduled exams) The system shall enable students to subscribe/unsubscribe to exams.

Initial non-functional requirements will be: Each student will have a web page personalized based on his or her recent details. The system shall protect the users privacy. The system shall prevent students from viewing grades of others. The system shall provide a user-customizable visibility policy for the personal information. Application will be accessed through a Browser Interface.

1.3 Overview of Document

The next chapter, the Overall 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 third chapter, Requirements Specification section, of this document is written primarily for the developers and describes in technical terms the details of the functionality of the product.

Both sections of the document describe the same software product in its entirety, but are intended for different audiences and thus use different language.

2.0.

Overall Description

2.1

System Environment

Figure 1 Use Case

The system has two active actors student and admin which shows student interaction with admin. Student register, apply for leave, appearing for exam, and admin approve the leave ,show result of exam and shows daily updates like daily time table, any new notice for student etc.

Get Register

fill online form

login Admin Student set question paper

Get Questions

Submit paper

declare result

leave application

leave approverd

logout

2.2

Functional Requirements Specification

This section outlines the use cases for each of the student for login process and authenticated by admin. In comparison to the present system the proposed system will be less time consuming and is more efficient. Analysis will be very easy in proposed system as it is automated. Result will be very precise and accurate and will be declared in very short span of time because calculation and evaluations are done by the simulator itself. The proposed system is very secure as no chances of leakage of question paper as it is dependent on the administrator only. The logs of appeared candidates and their marks are stored and can be backup for future use

Use case: Login Diagram:

Login

Student Admin password

Brief Description The student accesses the online student management Website, check for daily update, appear for exam online and can apply for leave by sending mail to co-coordinator.

Initial Step-By-Step Description Before this use case can be initiated, the User has already accessed the Online student management Website.

1. The student login. 2. The system authenticate student by checking password.

Use case: Leave Application. Diagram:

Apply for Leave <<include>> detailed Leave statement Student Admin

Send Mail

Approve/cancel

Brief Description The Student Login to the System for Checking daily updates and appearing online exam and apply for leave.

Initial Step-By-Step Description Before this use case can be initiated, the student has already connected to the Website.

1. The student logins to website. 2. Student Apply for Leave. 3. Admin approve or reject leave.

This diagram shows the detailed description of whole process from login, applying for leave, appear for exam, shows daily updates.

2.3 User Characteristics The User is expected to be Internet literate and be able to use a search engine. The main screen of the Online Student Management System Website will have the registration function and a link to Administrator. The Administrator expected to be managing the student details, update notice board, provide online question paper, evaluate result and shows to student, and reply for leave application whether approved or rejected.

2.4 Non-Functional Requirements The system shall protect the users privacy. The system shall prevent students from viewing grades of others .The system shall provide a user-customizable visibility policy for the personal information. Application will be accessed through a Browser Interface. The inter face would be viewed best using 1024 x 768 and 800 x 600 pixels resolution setting. The software would be fully compatible with Microsoft Internet Explorer and or Mozilla Firefox for version 7 and above. No user would be able to access any part of the application Without logging in to the system.

3.0.

Requirements Specification

3.1

External Interface Requirements The admin ensures the database of student is maintained properly, the security is provided for students data and passwords. Student has to register.

3.2

Functional RequirementsError! Bookmark not defined. 3.2.1 3.2.2 Student LoginError! Bookmark not defined. Display Notice Board Apply for LeaveError! Bookmark not defined.

3.2.3Error! Bookmark not defined. 3.2.4 3.2.5

Apply for Exam Error! Bookmark not defined. Edit profileError! Bookmark not defined.

3.3 Detailed Non-Functional Requirements

3.3.1 Logical Structure of the Data The logical structure of the data to be stored in the internal Article Manager database is given below. Student will be able to create own profile by registering them, view their profile, able to log in, log out also include information about exams , leave for which they applied Student register itself by filling form and submit it to admin, he can log in and check for daily updates, leave if he/she wants, check own profile and update it .can see notice board online ,appear for online exam ,paper will given by admin to student he/she apply the paper ,admin evaluate the result, and shows the marks obtained 3.3.2 Security 3.2.3 Hardware Requirement: PROCESSOR RAM HARD DISC : Pentium IV & Above. : 1 GB & Above. : 40 GB & above.

3.2.4 Software Requirement: PROGRAMMING LANGUAGE : Java WEB TECHNOLOGY DEVELOPMENT TOOLS DATABASE OPERATING SYSTEM : HTML, JSP, Servlet, AJAX : Eclipse, Apache Tomcat server : Oracle : XP/Win7/Win8.

Error! Bookmark not defined. Software Life Cycle Model:

In order to make this Project we are going to use Classic LIFE CYCLE MODEL .Classic life cycle model is also known as WATER FALL MODEL. The life cycle model demands a Systematic sequential approach to software development that begins at the system level and progress through analysis design coding, testing and maintenance.

The Classic Life Cycle Model The waterfall model is sequential software development process, in which progress is seen as flowing steadily downwards (like a waterfall) through the phases of conception initiation, Analysis, Design (validation), construction. Testing and maintained.

1) System Engineering and Analysis:Because software is always a part of larger system work. Begins by establishing requirement for all system elements and Then allocating some subset of these requirement to the software system Engineering and analysis encompasses the requirement gathering at the system level with a small amount of top level design and analysis.

2) Software requirement Analysis: The requirement gathering process is intensified and focused specifically on the software .Requirement for the both system and software are discussed and reviewed with the customer. The customer specifies the entire requirement or the software and the function to be performed by the software.

3) Design: Software design is actually a multi-step process that focuses on distinct attributes of the program data structure, software architecture, procedural detail and interface of the software that can be assessed or quality before coding begins .Like requirement the design is documented and becomes part of the software.

4) Coding: The design must be translated into a machine readable form. The coding step performs this task. If design is programmed in a detailed manner, coding can be accomplished mechanically.

5) Testing: Once code has been generated programmed testing begins. The testing process focuses on the internals of the software ensuring that all statement have been tested and on the functional

externals hat is conducting tests to uncover the errors and ensure that defined input will produce the results that agree with the required results. Unit testing:In computer programming, Unit testing is software Verification and validation method where the programmer gains confidence that individual units of source code are fit to use A unit is the smallest testable part of an application. In procedural programming a unit may be an individual programmed, function, procedure, etc. while in object-oriented programming, the smallest Unit is a class, which may belong to a base/super class abstract class or derived/child class.

Benefits: The goal of unit testing is to isolate each part of the program and show that the individual parts are correct. A unit test provides a strict written contract that the piece of code must satisfy.

Documentation:Unit testing provides a sort of living documentation of the system. Developers looking to learn what functionality is provided by a unit and how to use it can look at the tests to gain a basic understanding of the unit API.

Limitation of unit testing: Testing cannot be expected to catch error in the program It is impossible to evaluate all execution paths for all but the most trivial programs. The same is true for unit testing. Additionally, by unit testing only types the functionality if the units themselves.

6) Maintenance: Software will undoubtedly undergo change after it is Delivered to the customer .Change will occur because errors have been encountered because the software must be able adopted to accommodate changes in its external environment because the customer requires functional or performance enhancement enhancements. The classic life cycle is the oldest and most widely used paradigm or software engineering

Conclusion: Using this project Online Student Management System, it reduces the manual work of submitting the student details, Displaying Notice Board conducting online exam, applying leave application

Use Case:-

1) Registration

fill the form

data submited

student registration successfull

admin

password given

2) Leave Application

Apply for Leave <<include>> detailed Leave statement Student Admin

Send Mail

Approve/cancel

3) Online Exam:

Get registerd

<<include>>

fill form login <<include>>

Authenticate

answer the question

student

admin set ques papaer

submit paper

Declare results

<<extend>>

Show result

logout

ER Diagram:

DFD : Student Registration

2) Online Exam