LIBRARY MANAGEMENT SYSTEM

Requirement Specification:-
Requirement 1:

Description: Add a student record.

 Each student should have following attributes:

o Student ID/SSN (unique)
o Name
o Address
o Phone number

Requirement 2:

Description: Update/ Delete a student record.

 The record would be selected using the student ID

 Updates can be made on full. Items only:
o Name
o Address
o Phone number
 The record can be deleted if there are no books issued by user.

Requirement 3:

Description: Add a book item

 Each book shall have following attributes:
o Call Number
o ISBN
o Title
o Author name

 The call number format to be adopted would be as follows

o (First 2 alphabets of title) –(first 2 alphabets of author) – sequence
number of book

 The ISBN number format to be adopted would be as follows:

o (Numeric code for subject)-(sequence number)
o NNN-NNNNN
o It would be unique for each specific title/author combination
 Author name shall support 30 character names
 PAGE 2

 Title shall support 100 character names

Requirement 4:

Description: Update / Delete a book item

 The book item can be retrieved using the call number
 The data items which can be updated are:
o ISBN
o Title
o Author name

 The book can be deleted only if no user has issued it.

Requirement 5:

Description: Query the book database

 The product shall let Librarian query books’ detail information by their ISBN
number or Author or Title.
 The search results would produce a list of books, which match the search
parameters with following details:
o Call number
o ISBN number
o Title
o Author

 The display would also provide the number of copies which is available for
issue
 The display shall provide a means to select one or more rows to a user-list
 A detailed view of each book should provide information about check-
in/check out status, with the borrower’s information.
 The search display will be restricted to 20 results per page and there would be
means to navigate from sets of search results.
 The user can perform multiple searches before finally selecting a set of books
for check in or checkout. These should be stored across searches.

Requirement 6:

Description: Check-out a book

 PAGE 3

 Librarians and member of the library can check out a book using its call
number.
 The checkout can be initiated from a previous search operation where user has
selected a set of books.
 The student ID who is issuing the book would be entered.
 The issue date would automatically reflect the current system date.
 The due date would automatically be stamped as 7 days from current date.

Requirement 7:

Description: Check-in a book

 Librarians and member of the library can check in a book using its call
number.
 The check-in can be initiated from a previous search operation where user has
selected a set of books.
 The return date would automatically reflect the current system date.
 Any late fees would be computed as difference between due date and return
date at rate of one dollar a day.

Requirement 8:

Description: Display book detail

 This view would display details about a selected book from search operation.
 The details to be displayed are:
o Call number
o ISBN
o Title
o Author
o Issue status (In library or checked out)
o If book is checked out it would display
o User ID & Name
o Checkout date
o Due date

Requirement 9:

Description: View student detail

 Librarians can select a user record for detailed view.
 PAGE 4

 The detail view should show:

o User name, ID, Address & Phone number.
o The books issued by user with issue date, due date, call number, title.
o Late fees & Fines summary and total.
Performance Requirements:
 The check in and check out system will respond to the user no more than 7
seconds.
 The search function will respond to the user no more than 10 seconds.

Security requirements:
 All the account managing operations can be used by only librarian.
 The check-in, check-out and recall system can be used by only member of the
library.
 The book return report and book borrowing report can be generated by only
librarian.

Reliability requirements:
 The system shall generate error messages when the user attempts to enter
invalid data.
 If the system is down, it shall be recovered within 15 minutes.
 The system shall be recovered without interference at user terminal if it is
down.
 The system shall have 99.9% reliability during library operating hours.
 PAGE 5

LIBRARY MANAGEMENT SYSTEM

USECASE DIAGRAM

A use case is a set of scenarios that describing an interaction between a user

and a system.  A use case diagram displays the relationship among actors and use
cases.  The two main components of a use case diagram are use cases and actors.

An actor is represents a user or another system that will interact with the
system you are modeling.  A use case is an external view of the system that represents
some action the user might perform in order to complete a task.

The bellow diagram reveals the high-level functionality of the system.

Here in this system, the primary user of the system is librarian who is responsible for
user creation, book item creation, check-in, checkout and all search operations. The
student refers to an end-user of the system who is a member of the library and a
student at the university.

Use case’s description is as shown below:-

Name: Add/Edit/Delete Student record.

Description: Only librarians are responsible for adding/editing/deleting student
record.
Actors: Librarian
Trigger: According to the need of librarian.
Result: The details of the student get updated.
Essential process: Identify user by login process.
Carry out manipulation task according to requirement.
Check student details are updated or not.

Name: Add/Edit/Delete Book item.

Description: Only librarians are responsible for adding/editing/deleting student
record.
Actors: Librarian
Trigger: According to the requirement of librarian.
Result: The details of the book get updated.
Essential process: Identify user by login process.
Carry out manipulation task according to requirement.
Check book details are updated or not.

Name: Search for book.

Description: Librarians and Student are responsible for search book.
 PAGE 6

Actors: Librarian, Student

Trigger: Librarian or student searches book according to their need.
Result: Book details should be displayed.
Essential process: Identify Librarian or Student by login process.
Search for required book.
Check availability of book.
Display required book details.

Name: Check-Out Book.

Description: Librarians and Student are responsible for check-out book.
Actors: Librarian, Student
Trigger: Student or librarian requests for check-out book with the help of book call
number and their id.
Result: Check-out confirmed.
Essential process: Identify Librarian or Student by login process.
Check whether check-out is completed or not.

Name: Check-In Book.

Description: Librarians and Student are responsible for check-in book.
Actors: Librarian, Student
Trigger: Student or librarian requests for check-in book with the help of book call
number and their id.
Result: Check-in confirmed.
Essential process: Identify Librarian or Student by login process.
Check whether check-in is completed or not.
Overdue alert

Name: Display book-detail.

Description: When the librarian or student searches book for borrow at that time the
system shows the details of the book.
Actors: Librarian, Student
Trigger: Student or librarian searches book for borrowing.
Result: Specific book-details should be displayed in terms of call number, title,
author etc...
Essential process: Identify Librarian or Student by login process.
Search a specific book.
Display book-detail.

Name: View student detail.

Description: Librarian can select a student record for detail view.
Actors: Librarian..
Trigger: When the librarian wants to check student record.
Result: Specific student details displayed in terms of student id, phone number, books
issued by that student with the issue date & due date, late fees etc…
Essential process: Identify Librarian or Student by login process.
Search a specific student.
View student detail.
 PAGE 7

USECASE DIAGRAM
FOR
LIBRARY MANAGEMENT SYSTEM
 PAGE 8

LIBRARY MANAG.EMENT SYSTEM

CLASS DIAGRAM

Class diagrams are widely used to describe the types of objects in a system
and their relationships.  Class diagrams model class structure and contents using
design elements such as classes, packages and objects. Class diagrams describe three
different perspectives when designing a system, conceptual, specification, and
implementation. These perspectives become evident as the diagram is created and
help solidify the design. 
Classes are composed of three things: a name, attributes, and operations. 
Below is an example of a class.

Association is a generic relationship between two classes and is modeled by a line

connecting the two classes. This line also shows the feature multiplicity. (One-to-one,
one-to-many, many-to-many). For example

.
Aggregations indicate whole part-of relationship. It is represented by .

Composition relationship means the class is a member of another class. It cannot be

present by itself. It is represented by

Generalization relationship means “is-a “relationship. It is represented by

The above class diagram reveals the main class is library management system which
is divided in to two users like student and librarian. Student and librarian perform
tasks according to their need. The other class name is transaction and book.

.
 PAGE 9

CLASS DIAGRAM
FOR
LIBRARY MANAGEMENT SYSTEM

LIBRARY MANAGEMENT SYSTEM

 PAGE 10

OBJECT DIAGRAM

DEF: It is a diagram that shows set of objects and their relationships.

CONTENTS: Objects, Links.

USES:

1) Object diagrams are used to model static design view of a system.

2) Object diagrams are used to visualizing, specifying, constructing and
documenting structural models or static aspects of a system through
forward and reverse engg.

OBJECT DIAGRAM
FOR
LIBRARY MANAGEMENT SYSTEM
LIBRARY MANAGEMENT SYSTEM
 PAGE 11

INTERACTION DIAGRAM

DEF: This diagram shows the interaction in between different objects and their
relationships including the messages that may be dispatched among them.

CONTENTS: Objects, Links and Messages.

USES: Interaction diagrams are used to modeling dynamic aspects of a system or

subsystem or operation or a class.

Interaction diagrams are 2 types :

SEQUENCE DIAGRAM : It is a interaction that emphasizes the time ordering

of messages. Graphically the sequence diagram is a table that shows objects arranged
along the x-axis and messages, ordered in increasing time along the y-axis.

Features: there are two types

1) Object Life Line : An object life line is a vertical dashed line that
represents the existence of an object over a period of time.
2) Focus of control: the focus of control is a tall thin rectangle that
shows the period of time during which an object is performing an
action.

COLLABORATION DIAGRAM : It is a interaction diagram that emphasizes

structural organizations of the objects that send and receive messages.
Graphically the collaboration diagram is a collection of vertices arcs.

Features: there are two types

1) Path: To indicate how one. object is linked to another .
2) Sequence Number: To indicate the time order of a message.
 PAGE 12

SEQUENCE DIAGRAM
FOR
LIBRARY MANAGEMENT SYSTEM
 PAGE 13

COLLABORATION DIAGRAM
FOR
LIBRARY MANAGEMENT SYSTEM

LIBRARY MANAGEMENT SYSTEM

 PAGE 14

ACTIVITY DIAGRAM

DEF: Activity diagrams describe the workflow behavior of a system. 

Activity diagrams are similar to state diagrams because activities are the
state of doing something.  The diagrams describe the state of activities by
showing the sequence of activities performed.  Activity diagrams can
show activities that are conditional or parallel.

Activity states: Activity states mark an action by object. It is represented

by

Transition: When an activity states is completed processing moves to

another activity state. Transition used to mark this movement. It is
represented by

Initial state: The initial state marks the entry point and the initial activity
state. It is represented by

Final state: final states mark by the bulls’ eye. It is represented by

Synchronization bar: Activities often can be done in parallel. To spilt

processing Synchronization bar is used. It is represented by

Branching: The trigger less transitions may have guard conditions that is
will five only if that conditions are met. Whenever decision making or a
Boolean expression is specified branching is done. it represents alternate
paths represented by

◊ .
 PAGE 15

Swimlanes: These are group related activities into one column. These are
useful when modeling new things happen in a system and can be used to
show where activities takes place or who carries out.

IN this diagram we are using 3 swimlanes. They are

1) student
2) admin
3) lms
 PAGE 16

ACTIVITY DIAGRAM
FOR
LIBRARY MANAGEMENT SYSTEM
 PAGE 17

LIBRARY MANAGEMENT SYSTEM

STATE CHART DIAGRAM

Definition: A state chart diagram shows a state machine including simple

states ,transitions or nested composite states.

Contents: Objects ,action states ,a..ctivitystates,forks,joins,intial and final

states apart from nodes and constraints also .

Uses: These are used to model the dynamic aspects of a system ,class or
usecase.

States: A state is a condition or a situation during the life of an object

during which it satisfies some condition performs sosme activity or waits
for some events.It is given by

Transition: Detecting an event may cause an object to move from one

state to another.Such a move is called transition.It is given by
….

STATE CHART DIAGRAM

FOR
LIBRARY MANAGEMENT SYSTEM
PAGE 18
 PAGE 19

LIBRARY MANAGEMENT SYSTEM

COMPONENT DIAGRAM

Definition: component diagram is that which shows a set of components

and their relationships.

Contents:
component,Interfaces,Relationships(dependency,generalization,
association and realization relationships)

Uses: Component diagrams are also used to visualizing ,specifying

documenting component based systems,constructing executables through
forward and reverse engineering .

Component diagrams are used to model the static implementation

view of a system. We do this in 4 ways
1. To model source code
2. To model executable releases
3. To model physical databases
4. To model adaptable system

A component is a physical and replacable part of a system that

conforms to and provides the realization of a set of interfaces.
Graphically shown by

In LMS there are 4 components

1. User
2. Security
3. LMS Application Server
4. Data
 PAGE 20

COMPONENT DIAGRAM
FOR
LIBRARY MANAGEMENT SYSTEM
 PAGE 21

LIBRARY MANAGEMENT SYSTEM

DEPLOYMENT DIAGRAM

Definition: It is a diagram that shows the configuration of the run time processing
nodes and components that live on them.

Contents: Nodes,Relationships(dependence and associations)

Uses:
1. These are used to model static deployment view of a system
2. These are used to visualizing ,specifying constructing and documenting
embedded client-server and distributed systems
3. These are used to define executable systems through forward and reverse
engineering.

A Node is a physical element that exists at runtime and represents a computational

resource ,generally having at lease some memory and often processing capability.

Graphically a node is rendered as a cube.

In LMS we have taken 3 nodes .They are

1. User
2. LMS Application Server
3. Database Server
 PAGE 22

DEPLOYMENT DIAGRAM
FOR
LIBRARY MANAGEMENT SYSTEM