Online Seminar Management System

Software Requirements Specification

Table of Contents
1. Introduction
1.1 Purpose
1.2 Scope
1.3 Definitions, acronyms, and abbreviations
1.4 References
1.5 Overview

2. Overall description
2.1 Product perspective
2.2 Product functions
2.3 User characteristics
2.4 Constraints
2.5 Assumptions and dependencies

3. Specific requirements
3.1 External interface requirements
3.1.1 User interfaces
3.1.2 Hardware interfaces
3.1.3 Software interfaces
3.1.4 Communications interfaces

3.2 Functional requirements

3.3 Performance requirements
3.4 Design constraints
3.5 Software system attributes
1. Introduction
Borrowing books, returning books or viewing the available books at the Library of the Computer
Dept. is currently done manually where in the student has to go to the Library and check the
available books at the Library. Students check the list of books available and borrow the books if
the book is a borrow book otherwise it is of waste for the student to come to the library to come
to check for the books if the student doesn’t get the book. Then the librarian checks the student
id and allows the member to check out the book and the librarian then updates the member
database and also the books database.

We have decided to investigate the use of an Online Library Management System. This system
would be used by members who may be students or professors of the department to check the
availability of the books and borrow the books, and by the librarian to update the databases.
The purpose of this document is to analyze and elaborate on the high-level needs and features
of the Online Seminar Management System. It focuses on the capabilities and facilities
provided by a Library. The details of what all are the needs of the Online Seminar Management
System and if it fulfils these needs are detailed in the use-case and supplementary
specifications.

1.1 Purpose
The purpose of Software Requirements Specification (SRS) document is to describe the external
behavior of the Online Seminar Management System. Requirements Specification defines and
describes the operations, interfaces, performance, and quality assurance requirements of the
Online Seminar Management System. The document also describes the nonfunctional
requirements such as the user, hardware and software interfaces. It also describes the design
constraints that are to be considered when the system is to be designed, and other factors
necessary to provide a complete and comprehensive description of the requirements for the
software. Thus the Software Requirements Specification (SRS) captures the complete software
requirements for the system.

1.2 Scope
The Software Requirements Specification captures all the requirements in a single document.
The Online Seminar Management System that is to be developed provides the faculty and
students of Computer Engineering with books information, online booking of books and many
other facilities. The Online Library System is supposed to have the following features.

 The product provides the members with online booking of books capabilities and the
Online Library System is up and running all day.
 The system provides logon facility to the users.
 The system provides the members with the option to check their account and/or change
their options like password of the account whenever needed all through the day during
the library hours.
  The system allows the members to view the books 24 hours a day and all the through
the semester.
 The system lets the seminar administrator to check which all members have booked the
books and whether they can borrow any more books or not.
 The system allows the seminar administrator to create the books categories, add/delete
books and maintain the books categories.

1.3 Definitions, Acronyms and Abbreviations

The following are the list of conventions and acronyms used in this document and the project as
well:

Administrator: A login id representing a user with user administration privileges to the software

 User: A general login id assigned to most users

 Client: Intended users for the software
 SQL Server: A server used to store data in an organized format
 JOOMLA: open source content management system used for designing
websites
 XAMPP : application providing SQL server and APACHE TOMCAT server
 APACHE TOMCAT: web server

1.4 References
The SRS document uses the following as references:

 Joomla! 1.5: Quick Start Guide

 Joomla! A User’s Guide: Building a Successful Joomla Powered Website
 www.joomla.org

1.5 Overview
The SRS will provide a detailed description of the Online Library System. This document will
provide the outline of the requirements, overview of the characteristics and constraints of the
system.

1.5.1 Section 2: This section of the SRS will provide the general factors that affect the product
and its requirements. It provides the background for those requirements. The items such as
product perspective, product function, user characteristics, constraints, assumptions and
dependencies and requirements subsets are described in this section.

1.5.2 Section 3: This section of SRS contains all the software requirements mentioned in section
2 in detail sufficient enough to enable designers to design the system to satisfy the
requirements and testers to test if the system satisfies those requirements.
2. Overall Description

2.1 Product Perspective

The proposed Online Seminar Management System is an on-line Library Management System
using JOOMLA which is one of the most popular open source Content Management System
renowned for its flexibility. This System will provide a search functionality to facilitate the search
of resources. This search will be based on various categories viz. book name, book author or the
ISBN. Also Advanced Search feature is provided in order to search various categories
simultaneously. The System will also have an ADMINISTRATOR who has full-fledged rights with
regards to add/update/remove the resources and the resource users from the system;
managing resources across branches – such as transferring books across these branches. The
users can know the number of available books, information about their account etc. The System
should reflect and support this decentralized structure.

  2.2 Product Features

There are two different users who will be using this product:

 Librarian who will be acting as the Super Administrator.

 Faculty Members will be acting as Administrator.
 Student of the Department who will be accessing the Library online.

The features that are available to the Librarian are:

 A librarian can issue a book to the student

 Can view The different categories of books available in the Library
 Can view the List of books available in each category
 Can take the book returned from  students
 Add books and their information of the books to the database
  Edit the information of the existing books.
 Can check the report of the issued Books.
 Can access all the accounts of the faculty members and students.

The features available to the Students are:

 Can view The different categories of books available in the Library

 Can view the List of books available in each category
 Can own an account in the library
 Can view the books issued to him
 Can put a request for a new  book
 Can search for a particular book

 2.3 User Classes and Characteristics

There are various kinds of users for the product. Usually web products are visited by various
users for different reasons.

 The users include :

 Students who will be using the above features by accessing the Library online.

 Faculty members who will have the facilities available to the administrator.

 Librarian who will be acting as the controller and he will have all the privileges
of a super administrator.

2.4 Operating Environment

The product will be operating in Windows environment. Also it will be compatible with the IE
6.0.  Most of the features will be compatible with the Mozilla Firefox & Opera 7.0 or higher
version. The only requirement to use this online product would be the internet connection.
2.5 Design and Implementation Constraints

The Product is developed using Joomla. The backend database for this SQL Server. The product
is accomplished with login facility so that specific function is available to specific student.

2.6 Assumptions and Dependencies

The product needs following third party product.

 SQL server to store the database.

 Joomla! to develop the Product.

 Apache Tomcat to act as a Web Server.

 
3. Specific Requirements

3.1 External interface requirements

3.1.1 User Interfaces

 3.1.2 Hardware interfaces

Server Side:

 Operating System: Windows XP  ,Windows VISTA

 Processor: Pentium  3.0 GHz or higher
 RAM: 256 Mb or more
 Hard Drive: 10 GB or more

  Client side:

 Operating System: Windows XP, Windows VISTA

 Processor: Pentium III or 2.0 GHz or higher.
 RAM: 256 Mb or more

3.1.3 Software interfaces

 Database: SQL Server.

 Application: JOOMLA
 Web Server:  APACHE TOMCAT

3.1.4 Communications interfaces

     The Customer must connect to the Internet to access the Website:

 Dialup Modem of 52 kbps

 Broadband Internet

3.2 Functional requirements

3.2.1 Logon Capabilities

The system shall provide the users with logon capabilities .

 3.2.2 Mobile Devices

The Online Library System is also supported on mobile devices such as cell phones.

3.2.3 Alerts

The system can alert the Librarian or the administrator in case of any problems .       

3.2.4 GUI

The user interface must be customizable by the administrator

3.2.5 Dependencies with other requirements

All user interfaces should be able to interact with the user management module and a part of
the interface must be dedicated to the login/logon module.

3.3 Performance requirements

The proposed system that we are going to develop will be used as the Chief performance system within
the Computer Department which interact with the staff and students. Therefore, it is expected that the
database would perform functionally all the requirements that are specified by the Computer
Department.

3.4 Design constraints

The system must be designed to allow web usability. That is, the system must be designed in such a way
that will be easy to use and visible on most of the browsers.

3.5 Software system attributes

 The Quality of the database is maintained in such a way so that it can be very user friendly to all
the users of the database.
 The database should have the option of book search by a variety of fields like book name,
author, ISBN number etc.
 For those books which are not available ebooks’ links should be provided.