Csc577 Srs 4c Group2

SRS for Library Management System
UNIVERSITI TEKNOLOGI MARA
SOFTWARE REQUIREMENTS
SPECIFICATION(SRS)
FOR LIBRARY MANAGEMENT
SYSTEM(LMS)
Version 0.2
Document Reference No: SRS/UML/CSC577/4C/G2/2021
CONFIDENTIAL
Version 0.2 (Confidential) Page 1 of 31 SRS/UML/CSC577/4C/G2/2021

Committee Members:
NUR DIYANA BT AB AZIZ Team Leader/Software Developer
AIRANI NATASHA BINTI MOHD ANIS System Tester/Software Developer
AINA NUR NADZIRAH BINTI System Designer/Software Developer

KHAIRULANUWAR
NURHANIS IZZATY BINTI HAYAZIT Software Requirement Analyst/Software

Developer
Reviewed By: Approved By:
_______________________ ________________________
NURHANIS IZZATY BINTI HAYAZIT NUR DIYANA BT AB AZIZ
Software Requirement Analyst Team Leader
Date:31/5/2021 Date:31/5/2021
CUSTOMER ACCEPTANCE:
Accepted By:
__NURRADIAH __
NURRADIAH BINTI SALIM

Pembantu Pustakawan s17
PD PNM Kg. Tengah Layang-Layang
Date: 2/5/2021

TABLE OF CONTENT
1. INTRODUCTION 5
1.1 Identification 5
1.2 System Overview 5
1.3 Document Overview 5
1.4 Summary of use case 6
2.0 Referenced Document 7

2.1 Goverment Document 7
2.2 Non Goverment Document 7
3.0 Use Case Specification 8

3.1 Authenticate user 8
3.2 Manage Book Detail 10
3.3 Manage Member Detail 13
3.4 Manage Book Transaction 15
3.5 View Report 17
3.6 Search Book List 19
4.0 NOTES 21
4.1 Introduction 21
4.2 Definition 21
4.3 Roles 21
4.4 Abbreviations And Acronym 21
5.0 EXHIBIT 22

LIST OF FIGURES
Figure 5.1 : LMS Authenticate User Sequence Diagram

Figure 5.2 : LMS Search Book List Sequence Diagram
Figure 5.3 : LMS Manage Book Transaction Sequence Diagram
Figure 5.4 : LMS Manage Book Transaction (Exception Flow) Sequence Diagram
Figure 5.5 : LMS Manage Member Detail Sequence Diagram
Figure 5.6: LMS Manage member detail (Exception FLow) Sequence Diagram
Figure 5.7 : LMS Manage New Book Sequence Diagram
Figure 5.8 : LMS Manage New Book(Exception Flow) Sequence Diagram
Figure 5.9 : LMS View Report Sequence Diagram

1. INTRODUCTION
1.1 Identification
System Number : LMS-2021-2
System Name: Library Management System
System Abbreviation: LMS
1.2 System Overview
This existing system in Perpustakaan Desa PNM Kg. Tengah Layang-Layang uses manual
processes for all transaction books. So it's taking more time to settle one transaction at a time.
Therefore, our team decided to propose some solutions to make the manual library
management system to be computerized.
1.3 Document Overview
Scope
In this system, staff are the user. The main task of the system for the user is to register a new
book, reserve and return book transactions that have been made by the library's members. The
member is among the community that came to the library, they can’t access the system.
Purpose
The purpose of this document is to determine the preeminent specification of the LMS in terms
of the needs of the end user. This system is developed to keep and store information of books
and transactions in a more efficient and effective way. Besides, this system can cut time taken
for the staff to key in data from 10 minutes to 3 minutes.

1.4 Summary of use case
1. Authenticate user
2. Manage Book Detail
3. Manage Member Detail
4. Manage Book Transaction
5. View Report
6. Search Book List

2.0 Referenced Document
2.1 Goverment Document
Not Applicable
2.2 Non Goverment Document
1. ITS332 Group Proposal Library Management
2. ITS232 Group Proposal
3. ITS332 Group Software Design description
4. SRA/UML/CSC577/4C/G2/2021 CSC577 Software Requirement Analysis (SRA)

3.0 Use Case Specification
3.1 Authenticate user
3.1.1 Description
The Use Case describes the process by which the Actor log in to the Library Management
Systems as a user or admin.
3.1.2 Pre-Condition
The Actor is an authorized user and has successfully registered into the system.
3.1.3 Post-Condition
The Actor has successfully logged in to the system.
3.1.4 Actors
Library Staff.
Library Member.
3.1.5 Flow Of Events
3.1.5.1 Primary Flow
P: Authenticate User
1. The Use Case starts when the Actor opens the log in screen from the system.
2. The system displays the screen to the Actor.
3. By default, the system displays log in form.
4. The Actor must enter required information such as
○ Username
○ Password
5. The Actor confirms to log in into the system and proceed to home screen.
6. If no information is entered, the Actor closes the screen.
7. The Use Case ends.
3.1.5.2 Alternative Flow

Not applicable.
3.1.5.3 Exception Flow

Not applicable.
3.1.6 “Include” Use Case

Not applicable.
3.1.7 “Extend” Use Case

Not applicable.

3.2 Manage Book Detail
3.2.1 Description
The Use Case describes the process by which the Actor manage the new book information’s
that supplied by vendor.
3.2.2 Pre-Condition
The Actor is an authorized user and has successfully logged in to system.
The New Book list has been listed by vendor.
The Actor successfully register the new book list.
3.2.4 Actors
Library Staff
P: Fill Book Details

1. The Use Case starts when the Actor opens add book detail screen from the
system.
2. The system displays the screen to the Actor where the Actor can insert new
details of new book. The form list displayed such as:
- Book Information including:
● ISBN
● Title
● Author
● Number of copies
● Shelf Number
3. After the form has been filled by the Actor, the Actor will submit the form to the
system.
4. The system asks for confirmation from the Actor either to proceed or not.
5. The Actor confirms to register the form.
6. The system store the new book detail in database.
7. If no book to add, the Actor closes the screen.

A1: Update Book Detail

1. By default, the system displays the list of registered books to the Actor.
2. The Actor selects one of the lists in order to modify the book detail.
3. Once the book detail is modified, the Actor will save the changes by selecting the
update function from the system.
5. The Actor confirms to update the form.
6. The system replaces book detail with new data and displays back to the Actor.
7. If there is no book to update, the Actor closes the screen.
A2: Delete Book Detail

1. By default, the system displays the list of registered books to the Actor.
2. The Actor selects one of the lists in order to remove the book detail from the list.
3. Once the book detail is selected, the Actor will remove it by selecting delete
function from the system.
5. The Actor confirms to delete the list.
6. The system removes book details from the database.
7. If there is no book to delete, the Actor closes the screen.
E: Invalid Input
1. The system prompts a message that the input is invalid.

Not applicable.

Not applicable.

3.3 Manage Member Detail
3.3.1 Description
The use case describes the process by which the actors manage the library member’s
information details.
3.3.2 Pre-Condition
The actor is an authorized admin registered in the system.
The actor successfully registers new members with their personal information details.
3.3.4 Actors
Library administrator.
P: Member Registration
1. The use case begins when the actor open the registration member screen from
the system
2. The system displays the screen to the actor.
3. The actor enters the member’s personal information details.
4. The system recorded the new member’s registration.
5. The system updates the member’s registration recorded in the system.
6. The screen displays the new registered member’s details recorded.
7. Use case end.
A1: Update Status

1. The system display list of recorded library members.
2. The actor pick one of the selected member to modify the status.
3. Once the status is modify, the actor saves the changes by selecting update
4. The system display updated member’s information detail.
5. If there’s no details to modify, the actor close the screen.
6. The use case end.

E1: Input needed

1. The system displays an appropriate error message when there’s a field unfill.
E2: Invalid Input

1. The system displays an appropriate error message that the input is in invalid
format.
2. The Actor closes the message.
3. The system returns to the previous screen.
E3: System Connection Error
1. At any step, the system connection could not be established or maintained.

2. The system displays an appropriate error message.
4. The System returns to the previous screen.

Not applicable.

Not applicable.

3.4 Manage Book Transaction
3.4.1 Description
The use case describe the process by which the actor manage the process of book transaction.
3.4.2 Pre-Condition
The actor is an authorized admin registered in the system.
The actor successfully record and update book transaction.
3.4.4 Actors
Library Staff
P: Booking Transaction
1. The use case begins when the actor open the booking transaction screen from
the system
2. The system display the screen to the actor.
3. The actor check the Id of member to ensure the status either to return or booked
4. The actor enter the booking details of the member
5. The system recorded the booking.
6. The system update the booking transaction recorded in the system.
7. The screen display the new transaction recorded.
8. Use case end.
A1: Update Status

1. The system display list of recorded booking transaction
2. The actor pick one of the selected member to modify the status.
3. Once the status is modify, the actor saves the changes by selecting update
4. The system display updated booking transaction.
5. If there’s no details to modify, the actor close the screen.

6. The use case end.

E1: Input needed

1. The system displays an appropriate error message when there’s a field unfill.
E2: Invalid Input

1. The system displays an appropriate error message that the input is in invalid
format.
3. The system returns to the previous screen.
E3: System Connection Error
1. At any step, the system connection could not be established or maintained.

2. The system displays an appropriate error message.
4. The System returns to the previous screen.
Not applicable.
Not applicable.

3.5 View Report
3.5.1 Description
The Use Case describes the process by which the Actor can view issue book transaction
reports.
3.5.2 Pre-Condition
The user is an authorized user and has successfully logged in to the system.
The user successfully views the requested report.
3.5.4 Actors
Library Staff
P: View Report
1. The Use case starts when the Actor opens the view report screen from the
system.
2. The system displays the screen to the Actor.
3. The Actor selects month and year to view reports from the system.
4. The system generates the report in the form of printable format and displays it to
the Actor.
5. The Actor prints the generated issued book report.
Not applicable.

Not applicable
Not applicable.
Not applicable.

3.6 Search Book List
3.6.1 Description
The Use Case describes the process by which the Actors can search for the book they prefer
and get book details in the search book list.
3.6.2 Pre-Condition
The Actor is an authorized user and has successfully logged in to the system.
The Library Book List has been loaded into the system.
The Actor has successfully searched for book detail.
3.6.4 Actors
Library Staff.
Library Member.
P: Search Book List
1. The Use Case starts when the Actor opens the search book list from the system.
2. The system displays the screen to the Actor where the Actor can search book
title, author, or publisher to find the book that they prefer.
3. The Actor selects to view book details from the system.
4. The system display book details on the screen.
5. If book details do not exist, the Actor closes the screen.

Not applicable.


Not applicable.

Not applicable.

Not applicable.

4.0 NOTES
4.1 Introduction
This glossary will be expanded throughout the life of the project.
4.2 Definition
This section describes definitions for all terms used in this document.
PNM A library established under the National Library Act 1972. PNM role
is to preserve and expand the use of published collections from
within a respective country as well as collections published in other
countries that relate to it.
4.3 Roles
This chapter describes the roles definition from user point of view.
Staff A person who key in new book info and does the borrow and return
process.
Member A person who registered as library member to use library services.
Vendor A person that supply new book to the library
4.4 Abbreviations And Acronym

This chapter describes the abbreviations and acronyms used in this document and arrange in
alphabetical order.
LMS Library Management System
NFR Non-Functional Requirement
PNM National Library of Malaysia
SRS Software Requirement Specifications

5.0 EXHIBIT
APPENDIX 1
SEQUENCE DIAGRAM FOR LIBRARY MANAGEMENT SYSTEM

Sequence Diagrams
Figure 5.1 : LMS Authenticate User Sequence Diagram

Figure 5.2 : LMS Search Book List Sequence Diagram

Figure 5.3 : LMS Manage Book Transaction Sequence Diagram

Figure 5.4 : LMS Manage Book Transaction (Exception Flow) Sequence Diagram

Figure 5.5 : LMS Manage Member Detail Sequence Diagram

Figure 5.6:LMS Manage member detail (Exception FLow) Sequence Diagram

Figure 5.7 : LMS Manage New Book Sequence Diagram

Figure 5.8 : LMS Manage New Book(Exception Flow) Sequence Diagram

Figure 5.9 : LMS View Report Sequence Diagram

Csc577 Srs 4c Group2

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Csc577 Srs 4c Group2

Uploaded by

Copyright:

Available Formats

SRS for Library Management System

UNIVERSITI TEKNOLOGI MARA

Version 0.2 (Confidential) Page 1 of 31 SRS/UML/CSC577/4C/G2/2021

NUR DIYANA BT AB AZIZ Team Leader/Software Developer

AIRANI NATASHA BINTI MOHD ANIS System Tester/Software Developer

AINA NUR NADZIRAH BINTI System Designer/Software Developer

NURHANIS IZZATY BINTI HAYAZIT Software Requirement Analyst/Software

Reviewed By: Approved By:

NURHANIS IZZATY BINTI HAYAZIT NUR DIYANA BT AB AZIZ

Software Requirement Analyst Team Leader

NURRADIAH BINTI SALIM

Version 0.2 (Confidential) Page 2 of 31 SRS/UML/CSC577/4C/G2/2021

2.0 Referenced Document 7

3.0 Use Case Specification 8

Version 0.2 (Confidential) Page 3 of 31 SRS/UML/CSC577/4C/G2/2021

Figure 5.1 : LMS Authenticate User Sequence Diagram

Version 0.2 (Confidential) Page 4 of 31 SRS/UML/CSC577/4C/G2/2021

System Name: Library Management System

System Abbreviation: LMS

1.2 System Overview

1.3 Document Overview

Version 0.2 (Confidential) Page 5 of 31 SRS/UML/CSC577/4C/G2/2021

1.4 Summary of use case

Version 0.2 (Confidential) Page 6 of 31 SRS/UML/CSC577/4C/G2/2021

2.0 Referenced Document

2.1 Goverment Document

2.2 Non Goverment Document

1. ITS332 Group Proposal Library Management

2. ITS232 Group Proposal

3. ITS332 Group Software Design description

4. SRA/UML/CSC577/4C/G2/2021 CSC577 Software Requirement Analysis (SRA)

Version 0.2 (Confidential) Page 7 of 31 SRS/UML/CSC577/4C/G2/2021

3.0 Use Case Specification

3.1 Authenticate user

3.1.5 Flow Of Events

3.1.5.1 Primary Flow

3.1.5.2 Alternative Flow

3.1.5.3 Exception Flow

Version 0.2 (Confidential) Page 8 of 31 SRS/UML/CSC577/4C/G2/2021

3.1.6 “Include” Use Case

3.1.7 “Extend” Use Case

Version 0.2 (Confidential) Page 9 of 31 SRS/UML/CSC577/4C/G2/2021

3.2 Manage Book Detail

The Actor is an authorized user and has successfully logged in to system.

The New Book list has been listed by vendor.

The Actor successfully register the new book list.

3.2.5 Flow Of Events

3.2.5.1 Primary Flow

P: Fill Book Details

Version 0.2 (Confidential) Page 10 of 31 SRS/UML/CSC577/4C/G2/2021

3.2.5.2 Alternative Flow

A1: Update Book Detail

A2: Delete Book Detail

3.2.5.3 Exception Flow

Version 0.2 (Confidential) Page 11 of 31 SRS/UML/CSC577/4C/G2/2021

3.2.6 “Include” Use Case

3.2.7 “Extend” Use Case

Version 0.2 (Confidential) Page 12 of 31 SRS/UML/CSC577/4C/G2/2021

3.3 Manage Member Detail

3.3.5 Flow Of Events

3.3.5.1 Primary Flow

3.3.5.2 Alternative Flow

A1: Update Status

Version 0.2 (Confidential) Page 13 of 31 SRS/UML/CSC577/4C/G2/2021