Library Management System - SRS, Study Guides, Projects, Research of Software Engineering

Download Library Management System - SRS and more Study Guides, Projects, Research Software Engineering in PDF only on Docsity!

Software Requirements Specification

Online Library System

prepared by

Ahmed Ramadan Farag Ahmed

supervision

DR. Zeiad Al Saghir

Table of Contents

Table of Contents

• Online Library System
• Table of Contents
• 1. Introduction
  • 1.1. Purpose
  • 1.2. Scope
  • 1.3. Glossary
  • 1.5. Document overview
• 2.1. Overall description
  • 2.2. System environment
  • 2.3. Product Perspective
  • 2.4. Product Function
  • 2.5. User Characteristics
  • 2.6. Design and implement constrains
• 3.1. Requirement Specifications
  • 3.2. External interface specifications
  • 3.3. Functional Requirements
  • 3.4. Detailed Non-Functional Requirements
  • 3.5. System Evolution

2.1. Overall description

The Online library system encompasses numerous files and information from the library Database. This system will be completely web-based, linking to library system and the remote web server from a standard web browser. An Internet connection is necessary to access the system.

2.1. System environment

Figure 1 System Design The library web site will be operated from the library Web Server. When Users are connects to the library web server will then interact with the Library Database through Database Engine, which allows the Windows type program to transfer data to and from a database.

2.2. Product Perspective Online library system is replacement for the library system which depend on paper work for recording books and users information.

2.3. Product Function 2.3.1. Administrator/Librarians 2.3.1.1. should be able to insert, modify and delete books. 2.3.1.2. shall record books returned by users. 2.3.1.3. shall accept or reject a new user according to the library policy or payment methods 2.3.1.4. shall get information of any member who has borrowed a book. 2.3.1.5. shall add and edit book categories and arrange books by categories. 2.3.1.6. shall add and edit authors and publishers information. 2.3.1.7. should send warning to members who have exceeded the return time. 2.3.2. Library members 2.3.2.1. should be registered to the system to have all system facilities. 2.3.2.2. should be provided with the updated information about the books catalog. 2.3.2.3. shall given access to check their account's information and change it. 2.3.2.4. shall have the ability to search through books by any information related to the book. 2.3.2.5. shall suggest a book to be brought to the library book collection.

2.4. User Characteristics The users can be separated into three groups: 2.4.1. Administrator: Who maintain the website. Admin should have more knowledge of web application development. Admin is able to fix any problems. 2.4.2. Librarians: Have Powers of employees to manage the system. Librarians assumed to have basic knowledge of computers and internet. 2.4.3. Library Members: Library members assumed to have basic knowledge of computers and internet.

2.5. Design and implement constrains

• The information of all user's, books must be stored in a data base that is access by web site.
• The online library system is running 24 hours a day , 7 days a week.
• Use ASP.net to create web site.
• MS SQL Server will be used as SQL engine and data base.
• Users shall access from any computer or mobile phone that has internet browsing capabilities.
• User should have their correct usernames and passwords to login into website.

3.1. Requirement Specifications

3.1. External interface specifications

3.1.1. User interfaces: 3.1.1.1. Login interface:

• In case the user is not registered yet, he can enter the details and register.
• If the user entered either his username or password incorrectly then an error message occurs. 3.1.1.2. Search interface:
• The member or librarian can search through books by any information related to the book such as title, authors, and subjects. 3.1.1.3. tegories View interface:
• Categories view shows the books categories view with ability to Librarians to add, edit or delete category from the list. 3.1.1.4. ibrarian's control panel interface:
• Control panel will allow librarians to add, confirm or remove users.

3.1.2. Hardware interfaces:

• The basic requirements of a computer system, no other specific hardware is required to run the software.

3.1.3. Software interfaces:

• Compatible browser to load and view the web pages.
• Operating System.

- UC2: Add Book Record Primary Actor : Librarian, Administrator Precondition: Already login Main Success Scenario: 1. Select the menu option to add record of the different books 2. the record of the books updating of the previous record and assign a number to each book done. Exception Scenarios: - 1 a) Wrong Password. - System tell user to correct the password entered.

3.2.2.3 Search Book

- UC3: Search Book Primary Actor : Librarian, Administrator, Member Precondition: System has been programmed for searching all item in database. Main Success Scenario: 1. Visit the main page. 2. Enter data and information such as title, author's name etc. 3. Click the search button. 4. View the search result. 5. Proceed to the next activity. Exception Scenarios: - 2 a) Search item does not exist. - System show error message.

3.2.2.4 Search member record

- UC4: Search member record Primary Actor : Librarian, Administrator. Precondition: None. Main Success Scenario: 1. Select the menu option to search member record. 2. Enters the name, father's name, Registration number. 3. Click the search button. 4. View the search result. Exception Scenarios: - 2 a) Incorrect data entered. - System show error message.

3.2.2.5 Issue Book

- UC5: Issue Book Primary Actor : Librarian. Precondition: User must be eligible for taking reqested item & Item is available. Main Success Scenario: 1. Visit login page and log in. 2. click on Issue button. 3. Add Issue books record Exception Scenarios: - 3 a) Required book is not available in library. - System show error message.

3.2.2.6 Download E-books

- UC6: Download E-books

Primary Actor : Member. Precondition: User must be already registered and entered payment methods. Main Success Scenario:

1. Visit login page and log in.
2. Click the download button.
3. Select the book from the list.
4. check the payment mehods.
5. down load done Exception Scenarios:

• 4 a) Balance is not enough.
  • System show error message.

3.2.2.7 Update Book Record

- UC7: Update book record Primary Actor : Administrator, Librarian. Precondition: The books have been issued. Main Success Scenario: 1. Select the menu option to enter the issued books record 2. Edit issued books record. Exception Scenarios: - 2 a) Required book is not available. - System show error message.

3.2.2.8 Update Member Record

- UC8: Update member record Primary Actor : Administrator, Librarian. Precondition: Must be logged in as administrator or librarian. Main Success Scenario: 1. Visit login page and log in. 2. Click the member record button. 3. Select the member. 4. click on the edit button. 5. Proceed to the next activity Exception Scenarios: - 1 a) Invalid user. - System show error message.

3.2.2.9 Reserve Book

- UC9: Reserve book Primary Actor : Member. Precondition: member must be registered Main Success Scenario: 1. Visit login page and log in. 2. search for specific book. 3. found the book 4. click on the reservation button. 5. System ask for member ID. 6. member enters the ID. 7. Book has been reserved

• System show error message.

3.2.2.13 Copy

- UC13: Copy Primary Actor : Member, Librarian. Precondition: Member must visit library building. Main Success Scenario: 1. Visit login page and log in. 2. Click on the copy button. 3. search for a book by related information. 4. Found a book. 5. Click to copy botton. 6. Fill copy request. 7. Librarian must be confirm the copy request. 8. Proceed to the next activity Exception Scenarios: - 4 a) Book not available. - System show error message. - 7 a) Librarian not confirm the copy request. - System show error message.

3.2.2.14 Return Book

- UC14: Return book Primary Actor : Member, Librarian. Precondition: Member has borrowed or reserved the book. Main Success Scenario: 1. member visit the library to return a book. 2. member gives his library card and the book to the librarian. 3. Librarian checks if the book is returned on time. 4. librarian will update book information. 5. Proceed to the next activity Exception Scenarios: - 3 a) The book is not returned on time. - Librarian generates fine slip.

3.2.2.15 Fine Payment

- UC15: Fine payment Primary Actor : Member, Librarian. Precondition: System has been programmed for automated report generation. Main Success Scenario: 1. Database is automatically checked daily for over due. 2. Send mail to users having over due. 3. Increase fine if not cleared. 4. update database. 5. Proceed to the next activity Exception Scenarios: - 1 a) System is not ready. - System show error message.

3.2.2.16 Logout

- UC16: Logout Primary Actor : Member, Librarian, Administrator Precondition: Must be logged in. Main Success Scenario: click to the logout button Exception Scenarios: None.

3.2.3. Sequence Diagrams

3.2.3.1. Search

Figure 3 Search Sequence diagram

3.3. Detailed Non-Functional Requirements

3.3.1. Error Handling

• Library System shall handle expected and non-expected errors in ways that prevent loss in information and long downtime period.

3.3.2. Performance Requirements

• Library System shall accommodate high number of books and users without any fault.

3.3.3. Safety Requirements

• Library System use shall not cause any harm to human users.

3.3.4. Security Requirements