ASSIGNMENT

Software Requirement Engineering Lab

SWE 226
Submitted to
Fazle Mohammed Tawsif
Lecturer
Department of Software Engineering
Shahjalal University of Science and Technology,
Sylhet.

Submitted by:
MD.Ariful Islam
Reg. no: 2018831049
Department of Software Engineering
IICT
Shahjalal University of Science and Technology, Sylhet.

Rafat Ahmed Khan

Reg. no: 2018831028
Department of Software Engineering
IICT
Shahjalal University of Science and Technology, Sylhet
 UML Design of a Library Management System
The UML swim-lane diagram is a useful variation of the activity
diagram and allows engineers to represent the flow of activities
described by the use case and at the same time indicate which actor or
analysis class has responsibility for the action described by an activity
rectangle. Here we will understand the designing of swim lane diagram
for the library management system.
Two analysis classes- User and system – have direct or indirect
responsibilities in the context of swim-lane diagram for library
management system. Every activity is placed inside a swim-lane of a
particular analysis class. For example, the system class represents the
server of the system where all the request and data will be placed. The
activity diagram notes three status display responsibilities of the system
– “status for books’ unavailability”, “status for invalid user” and “status
for book issued”. However, arrows lead from that swim-lane back to the
user swim-lane, where user actions occur.

Use case diagram

A UML use case diagram is the primary form of system/software
requirements for a new software program underdeveloped. Use cases
specify the expected behavior (what), and not the exact method of
making it happen (how). Use cases once specified can be denoted both
textual and visual representation (i.e. use case diagram). A key concept
of use case modeling is that it helps us design a system from the end
user's perspective. It is an effective technique for communicating
system behavior in the user's terms by specifying all externally visible
system behavior.
Use case diagram for library management system

Use case Diagram

Class Diagram for Library Management System
In Object-Oriented modeling, the main building block generally represents
different objects in a system, their attributes, their different functions, and
relationships among objects. These building blocks are known as Class
Diagram.
Class diagrams are generally used for conceptual modeling of static view of a
software application, and for modeling translating models into programming
code in a detailed manner. At time of developing or construction software
systems, a class diagram is widely used. They are also used for data modeling.

Classes of Library Management System:

Library Management System class –
It manages all operations of Library Management System. It is central part of
organization for which software is being designed.
 User Class –
It manages all operations of user.

 Librarian Class – It manages all operations of Librarian.

 Book Class –
It manages all operations of books. It is basic building block of system.

 Account Class –
It manages all operations of account.

 Library database Class –

It manages all operations of library database.

 Staff Class –
It manages all operations of staff.

 Student Class –
It manages all operations of student.

Class diagrams are generally used for conceptual modeling of static

view of a software application and for modeling translating models into
programming code in a detailed manner.
The Noun-Verb method perfectly balances out the need for simple,
comprehensible process diagrams that are also sufficiently detailed to
enable the identification and analysis of performance improvement
opportunities. Anyone involved in process mapping or process
improvement will instantly see the benefits when they adopt this
approach.

Activity diagram for Library Management System

The activity diagram used to describe flow of activity through a series of
actions. Activity diagram is a important diagram to describe the system.
The activity described as a action or operation of the system.