Software Requirements Specification for Web Library Management System (WLMS), Essays (university) of Mathematics

Download Software Requirements Specification for Web Library Management System (WLMS) and more Essays (university) Mathematics in PDF only on Docsity!

Software Requirements Specification

For

Web Library Management System

Version x.xx

Prepared by

<std_Name, std_No>

Proposed to

<instructor_Name>

Software Requirements Specification for WLMS Page ii

Table of Contents

Table of Contents .......................................................................................................................... ii Revision History .......................................................................................................................... iiii Table of Contents ......................................................................................................................... ii

Software Requirements Specification for WLMS Page iv

LIST OF TABLES

Table 1 Attributes Saved About Member ....................................................... 17 Table 2 Attributes Saved About Librarians .................................................... 18 Table 3 Attributes Saved About Library Items ............................................... 18 Table 4 Attributes Saved About Books........................................................... 19 Table 5 Attributes Saved About DVD's .......................................................... 19 Table 6 Attributes Saved About Magazine ..................................................... 19

Software Requirements Specification for WLMS Page v

• 1. Introduction Table of Contents v
  • 1.1 Purpose...........................................................................................................................................
  • 1.2 Scope..............................................................................................................................................
  • 1.3 Intended Audience Definitions, acronyms and abbreviations.........................................................
  • 1.3.1 Audience Definitions
  • 1.3.2 Acronyms and abbrevaitions
  • 1.4 References
  • 1.5 Overview
• 2. Overall Description
  • 2.1 Product Perspective
  • 2.2 Product Functions
  • 2.2.1 Administrators
  • 2.2.2 Normal Users ( library members)
  • 2.3 Operating Environment
  • 2.4 User Characteristics
  • 2.5 Design and Implementation Constraints
  • 2.6 Assumptions and Dependencies
• 3. Specific Requirements .............................................................................................................
  • 3.1 Functional Requirements
  • 3.1.1 Librarian
  • 3.1.2 Normal User
  • 3.1.3 Common Functions
  • 3.2 Non-Functional Requirements
  • 3.2.1 Error Handling
  • 3.2.2 Performance Requirements
  • 3.2.3 Safety Requirements
  • 3.2.4 Security Requirements
• 4. Interfaces and Possible Scenarios ...........................................................................................
  • 4.1 Login Interface
  • 4.2 Registration Interface
  • 4.3 Personal Data Editing
  • 4.4 Search.............................................................................................................................................
  • 4.5 Advanced Search
  • 4.6 Book View
  • 4.7 DVD View
  • 4.8 Categories View
  • 4.9 Librarian’s Control Panel
  • 4.10 Activating a User Account
  • 4.11 Adding a Book
  • 4.12 Library Manager Control Panel
  • 4.13 Adding a Librarian
• 5. Stored Items ............................................................................................................................
  • 5.1 Member
  • 5.2 Librarian
  • 5.3 Library Items
  • 5.4 Books, DVDs, Magazines and Journals
• Figure 1 Main menu LIST OF FIGURES
• Figure 2 Login error message
• Figure 3 Retrieve password form
• Figure 4 User registration form
• Figure 5 Server-Side Validation
• Figure 6 Client-Side Validation
• Figure 7 Personal data editing interface
• Figure 8 Search interface
• Figure 9 Advaned search interface
• Figure 10 View book interface
• Figure 11 DVD view interface
• Figure 12 Categories view
• Figure 13 Librarian’s control panel
• Figure 14 Activating a user account interface
• Figure 15 Adding a book interface
• Figure 16 Library Manager Control Panel
• Figure 17 Adding a Librarian interface

1.4 References

 IEEE 830-1998 standard for writing SRS document.  I. Sommerville, Software Engineering, 8 th^ ed. England: Addison-Wesley, 2007.

1.5 Overview

Section 2 defines the general functions of WLMS, operating environment and user constraints along with our assumptions.

Section 3 specifies functional and nonfunctional requirements; all of them are described to a level of detail sufficient for designers to design a system.

Section 4 illustrates interfaces and its possible scenarios along with some screenshots to make a general idea about the interfaces.

Section 5 specifies all stored information that we are concerned about for every entity in the website.

2. Overall Description

2.1 Product Perspective

WLMS is a replacement for the ordinary library management systems which depend on paper work for recording book and users’ information.

WLMS will provide an advanced book search mechanism and will make it easy to borrow, insert and index a book in the library.

2.2 Product Functions

2.2.1 Administrators

 Admin should be able to insert, modify and delete books.  Can accept or reject a new user according to the library policy or payment methods.  Increase the period for borrowing a book for specific type or group of users.  Can get the information (status report) of any member who has borrowed a book.  Add and edit book categories and arrange books by categories.  Add and edit authors and publishers information.  Can send lateness warnings to people who have exceeded deadline date.  Can record books returned by users.

2.2.2 Normal Users (Library Members)

 The member should be provided with the updated information about the books catalog.  Members are given a provision to check their account’s information and change it.  Members have the ability to search through books by subject, title, authors or any information related to the book.  Can extend the period of borrowing books according to the library policy.  The customer may suggest a book to be brought to the library book collection.

2.3 Operating Environment

The WLMS is a website and shall operate in all famous browsers, for a model we are taking Microsoft Internet Explorer versions 7.0, 8.0 and 9.0, with Flash Player 9 and JavaScript.

2.4 User Characteristics

Users of the website are members, librarians and the administrators who maintain the website. Members and librarians are assumed to have basic knowledge of computers and Internet browsing. Administrators of the system should have more knowledge of internal modules of the system and are able to rectify small problems that may arise due to disk crashes, power failures and other catastrophes. Friendly user interface, online help and user guide must be sufficient to educate the users on how to use this product without any problems or difficulties.

2.5 Design and Implementation Constraints

 The information of all users, books and libraries must be stored in a database that is accessible by the website.  MS SQL Server will be used as SQL engine and database.  The Online Library System is running 24 hours a day.  Users may access WLMS from any computer that has Internet browsing capabilities and an Internet connection.  Users must have their correct usernames and passwords to enter into their online accounts and do actions.

2.6 Assumptions and Dependencies

The product needs the following third party products.

 Microsoft SQL server to store the database.  ASP.net to develop the Product.

Requirement ID R1.01. Title return book Description Admin should confirm the return of books borrowed by users. Priority 1

3.1.2 Normal User

Requirement ID R1.02. Title register Description when new user enters WLMS for the first time then he has to register Priority 3

Requirement ID R1.02. Title extending borrowing deadline. Description member can extend the borrowing time to some limit decided by Admin Priority 2 Requirement ID R1.02. Title reset password Description when a member forgets his password he can claim it back via e-mail. Priority 1

Requirement ID R1.02. Title edit personal information Description if some user changes for example his mobile number, he can modify it. Priority 2

Requirement ID R1.02. Title reset password Description when a member forgets his password he can claim it back via e-mail. Priority 1

3.1.3 Common Functions

Requirement ID R1.03. Title login Description both Admin and members must be logged in before they modify any information Priority 1

Requirement ID R1.03. Title search for book Description when user or admin wants to search on some book by name, author or subject etc. Priority 1

3.2 Non-functional Requirements

3.2.1 Error handling

 WLMS product shall handle expected and non-expected errors in ways that prevent loss in information and long downtime period.

3.2.2 Performance Requirements

 The system shall accommodate high number of books and users without any fault.  Responses to view information shall take no longer than 5 seconds to appear on the screen.

3.2.3 Safety Requirements

 System use shall not cause any harm to human users.

3.2.4 Security Requirements

 System will use secured database  Normal users can just read information but they cannot edit or modify anything except their personal and some other information.  System will have different types of users and every user has access constraints.

4.2 Registration Interface

When the button تسجيم"" is clicked, the server will check if the username or email is already taken and alert the user as shown in Figure 5

If the user who is trying to register is already a member with the same username he can click on "اضغط هنا " to move to login page.

Figure 4: User registration form

After the guest reads "شروط وضوابط " and agrees it he can continue with registration operation by entering his name, password, e-mail, address, mobile, telephone and personal photo.

When the user finishes entering the required fields, he should click "تسجيم" to be a member of the library.

Users will be warned about any mistakes on data format or any other constrains by validation notes and error messages. Figures below show some of these mistakes with their correction examples.

Figure 5: Server-Side Validation

There are some errors that will be shown instantly to users and do not require the server response after "تسجيم" is clicked. Figure 6 shows these errors.

Validation fields are used to check if passwords entered are identical and it is also used to check if the e-mails are identical.

The Registration form also checks for the entered mobile and telephone and view an example to help the user to enter date in the correct form.

Figure 6: Client-Side Validation

4.4 Search

4.5 Advanced Search

In advanced search user can perform search operation in more specific criteria, as shown in Figure 9, user can search by ”انعنوان “ ,”انمؤنّف“ ,”انموضوع“and/or other criteria. And he can select search in ,” انصحف“ ,”انمجالت“ ,”انكتب“and/or ”انمدمجة األقراص“. The user can roughly select the language of his search contents and how to display the results by two options which are sorting the results and number of results per page. Finally he can specify the date of the contents he wants to find by determining start and end dates.

Figure 8: Search interface

Figure 8 shows the search form. In the form member or librarian can enter the type of media he is looking for and the title he is interested in them he can click on "بحث ". User can also use advanced search for more options.

4.6 Book View

When a Liberian or a member wants to view some book from search results or directly vie some link, the page on Figure 10 shall be shown to him.

As shown in Figure 9, a lot of useful information about the book will be displayed so the user can decide whether this book can be helpful to him or not. This information includes the publication year, publisher, edition, and number of pages, ISBN, table of contents, cover photo and description, from that page the Liberian can edit or delete the book and an active member can borrow it if there is enough number of copies.

4.7 DVD View

Simple information will be shown about the DVDs including its length, type, and available copies. See Figure 11.

Figure 10 : View book interface

Figure 11 : DVD view interface

4.10 Activating a User Account

A librarian must activate the new user account before user can borrow. Librarian can check user info and edit them as will, before he activates the account. See Figure 14.

Figure 13 : Librarian’s control panel

Figure 14 : Activating a user account interface

4.11 Adding A book

Librarian can add a book using form shown in Figure 15, all required fields are validated automatically, and results the error messages shown in red.

4.12 Library Manager Control Panel

This control panel will allow Library manager to add, edit, view, or remove librarians; as an addition to all what librarian can do. See Figure 16.

Figure 16 : Library Manager Control Panel

Figure 15 : Adding a book interface