Software Requirements Specification

For

ONLINE MENTOR SYSTEM

Version 1.0 approved

Guided By: Prof. Sidharth dash

Team Members: 1. ABINASH BHERA 2. KHUSHBOO MISHRA 3. VIVEK KUMAR 4. AYUSHI MOHANTY

DEPARTMENT OF CSE & IT SIET, DHENKANAL

Software Requirements Specification for Online Banking

Page ii

Table of Contents
Table of Contents .......................................................................................................................... ii Revision History ............................................................................................................................ ii 1. Introduction..............................................................................................................................1
1.1 Purpose ............................................................................................................................................ 1 1.2 Document Conventions ................................................................................................................... 1 1.3 Intended Audience and Reading Suggestions ................................................................................. 1 1.4 Project Scope ................................................................................................................................... 1 1.5 References........................................................................................................................................ 2

2. Overall Description ..................................................................................................................2

2.1 Product Perspective ......................................................................................................................... 2 2.2 Product Features .............................................................................................................................. 2 2.3 User Classes and Characteristics ..................................................................................................... 2 2.4 Operating Environment ................................................................................................................... 2 2.5 Design and Implementation Constraints ......................................................................................... 2 2.6 User Documentation ........................................................................................................................ 3 2.7 Assumptions and Dependencies ...................................................................................................... 3

3. System Features .......................................................................................................................3

3.1 System Feature 1.............................................................................................................................. 3 3.2 System Feature 2 (and so on) .......................................................................................................... 4

4. External Interface Requirements ...........................................................................................4

4.1 User Interfaces ................................................................................................................................. 4 4.2 Hardware Interfaces......................................................................................................................... 4 4.3 Software Interfaces .......................................................................................................................... 4 4.4 Communications Interfaces ............................................................................................................. 4

5. Other Nonfunctional Requirements .......................................................................................5

5.1 Performance Requirements.............................................................................................................. 5 5.2 Safety Requirements ........................................................................................................................ 5 5.3 Security Requirements..................................................................................................................... 5 5.4 Software Quality Attributes ............................................................................................................. 5

6. Other Requirements ................................................................................................................5 Appendix A: Glossary ...................................................................................................................5 Appendix B: Analysis Models .......................................................................................................6

Appendix C: Issues List.................................................................................................................6

Revision History
Name Date Reason For Changes Version

Software Requirements Specification for <Project>

Page 5

1. Introduction
Online Mentor System is a web based system through which mentor and mentee can communicate to each other regarding the problems and its solution.

1.1 Purpose
The purpose of this document is to describe the design of the project name ONLINE MENTOR SYSTEM. The purpose of design documentation is to express the vision for the project, describe the contents, and present a plan for implementation. The main purpose of our project are the following:

Automatic Report Generation Response should be easier. Updation/Modification can be Easier

1.2 Document Conventions

Throughout this document, the following conventions have been used:

Font-Times New Roman Size 16 for main heading Size 14 for sub heading Size 12 for the rest of the document Words in Bold are important terms , and have been formatted to grab the attention

1.3 Intended Audience and Reading Suggestions

The expected audience of this document is the Mentor, students and Administrator including the persons who will use this system, Team members, academicians etc. All technical description and design can be tracked to the use cases and requirements for the project.

1.4 Project Scope

This product has great future scope. The software developed on and for the Windows XP and later versions environments and Linux OS. This project also provides security with the use of Login-id and Password, so that any unauthorized users. The only customers that will have proper access authority can access the software.
1.5

References
Principle of Software Engineering by Rajib Mall Fundamental of Software Project management by Rajib Mall http://www.studentmentor.org/ http://www.mentornet.net/ http://otc.rutgers.edu/remp/mentors.php

Software Requirements Specification for <Project>

Page 6

2. Overall Description
2.1 Product Perspective
This section aims to describe both the existing and the proposed systems, with respect to why the proposed system is needed. There is not any existing ONLINE MENTOR SYSTEM. The benefits of this project is it is online and can be accessed from anywhere.

2.2 Product Features

o
o

Login system of online mentor system Registration Update student information Display students information Give response through email Remove members Providing security Low cost Basic computer knowledge required Configurable and extensible application UI design

o o o o
o o o

2.3 User Classes and Characteristics

There are 3 types of user of this softwareA. Students. B. Mentors. C. Administrator. 1. Students can Register and share their problem with their mentors. 2. A Mentor can able to track/analyze the student as per its attendance and performance and also generate the report and act as a problem solver for students. 3. Administrators can access all the details of the student and also the report generated by the mentors.

Software Requirements Specification for <Project>

Page 7

2.4 Operating Environment Minimum requirement for execution of the project is:
1. A java supporting operating system(Windows XP and later, linux). 2. Minimum of 512 MB of RAM. 3. 1 GB of hard disk. 4. A web browser(Internet Explorer ,Mozila Firefox etc.) 5. PC must have access to the internet.
2.5

Design and Implementation Constraints

1) The interface will be in English only. 2) The system is working for single server. 3) There is no maintainability or backup so availability will get affected. 4) The system is a single user system. 5) GUI features available.

2.6 User Documentation

After the completion of the project a well documented user manual will be provided.

2.7 Assumptions and Dependencies

1) User must be trained for basic computer functionalities. 2) User must have the basic knowledge of English 3) The system must be able to respond to database software within reasonable time.

Software Requirements Specification for <Project>

Page 8

3. System Features
3.1 LOGIN
3.1.1 DESCRIPTION & PRIORITY This feature will be used to LOG IN into the online mentor system (only permitted users can use the OMS). It is done in order to prevent any misuse of OMS.

3.1.2 STIMULUS / RESPONSE SEQUENCES

When the user gives the correct username and password combination, he/she is transferred to the ma in screen or the main page.

3.1.3 FUNCTIONAL REQUIREMENTS Purpose

To check the credibility of an user and to prevent any misuse of the product

Inputs
The input will be username and password combination

outputs
The user will be transferred to the main page on successful validation and will be alerted if the validation is unsuccessful

3.2 NEW MENTOR/STUDENT REGISTRATION 3.2.1 DESCRIPTION & PRIORITY

Its purpose is to create a new member of the college. A member must be registered before he/she can create any new accounts in OSM.

3.2.2 STIMULUS / RESPONSE SEQUENCES

On successful validation of each data field (member details), the registration takes placeand the succe ss message is displayed.

3.2.3 FUNCTIONAL REQUIREMENTS Purpose

To register a new member

Inputs
The required data for registration of a new member in the OMS (Like Name, Address, branch, ID, Designation etc).

Output

Software Requirements Specification for <Project>

Page 9

A Success Message be displayed on successful registration or else an error message will be displayed.

3.4 UPDATING MENTOR/STUDENT INFORMATION 3.4.1 DESCRIPTION & PRIORITY

To update and change the mentor/student profile

3.4.2 STIMULUS / RESPONSE SEQUENCES

On successful validation of each data field, the updating Procedure takes place.

3.4.3 FUNCTIONAL REQUIREMENTS Purpose

To update the mentor/student profile

Inputs
The required data for updating the information of a mentor /student would be given

Output
Either a successful acknowledgment is displayed or else an error message is displayed.

3.5 VIEW DETAILS OF A STUDENT

3.5.1 DESCRIPTION & PRIORITY
This feature would be used to view the details of a students (like attendance, marks etc).

3.5.2 STIMULUS / RESPONSE SEQUENCES

On successful validation of the students ID and password, the respective details are displayed

3.5.3 FUNCTIONAL REQUIREMENTS Purpose

To view the details of a students.

Input
Id and password

Output
On successful verification, the details of the respective entities are displayed or else an error message is displayed.

3.6. Logout
3.6.1 DESCRIPTION & PRIORITY

Software Requirements Specification for <Project>

This feature would enable the user to successfully end his Session and Logout the OMS. After Logging Out, he/she would not be able to perform any of the operations until he/she is again logged In.

Page 10

3.6.2 STIMULUS / RESPONSE SEQUENCES

On clicking the Logout Button, the session is terminated and the Login screen appears.

3.6.3 FUNCTIONAL REQUIREMENTS Purpose

To successfully end the user session and Logout of the OMS.

Inputs
The input will be Username and Password combination

Output
The user will be transferred to the main page on successful validation and will be redirected to the Login Page if the validation is unsuccessful.

Software Requirements Specification for <Project>

Page 11

3.2 System Feature 2 (and so on)

4. External Interface Requirements

4.1 User Interfaces User of the system will be provided with the Graphical user interface, there is no command line interface for any functions of the product. The user will get 2 pages 1. Login page followed by Password

4.2 Hardware Interfaces Hardware requirements for Insurance on internet will be same for both the parties which are follows: Processor: - Pentium IV or above. 128 MB or above. HD: NIC: 4.3 20 GB or above. For each party RAM:

Software Interfaces

Software Requirements Specification for <Project>

1. Operating system:

Page 12

It can work on Operating Systems like Windows XP/7/VISTA. 2. JAVA development tool kit.

Software Requirements Specification for <Project>

Page 13

4.4 Communications Interfaces The two parties should be connected through either by LAN or WAN for the communication.

Software Requirements Specification for <Project>

5. Other Nonfunctional Requirements

Page 14

5.1 Performance Requirements In order to maintain an acceptable speed at maximum number of uploads allowed from a particular user will be any number of users can access the system at any time. Also connections to the servers will be based on the criteria of attributes of the user like his location, and server will be working whole 24X 7 times. 5.2 Safety Requirements It will be maintained by developer as no information cant lost for damages to the system for any causes. 5.3 Security Requirements

Sensitive data is protected from unwanted access by users appropriate technology and implementing strict user-access criteria. Facility of unique user number and Password in such a way that unauthorized user cannot log in. Operational rights for each user/terminal can be defined. Thus, a user can have access to specific terminals and specific options only.

5.4 Software Quality Attributes

Software Requirements Specification for <Project>

Page 15

This project would be developed completely using open source software and platforms. So, Anybody can use and enhance the software further without spending any money.

6. Other Requirements
Not Applicable

Appendix A: Glossary

Software Requirements Specification for <Project>

Page 16

Appendix B: Analysis Models

Diagram related to operation, external view, internal view, user view.

Appendix C: Issues List

Internal Issues:

manpower labor

problems

objections

manager resistance organizational conflicts policies External issues:-

social

acceptability

legal aspects Government regulations.