See discussions, stats, and author profiles for this publication at: https://www.researchgate.

net/publication/326463911

SOFTWARE REUSABILITY (WOC 7003) CASE STUDY Library Management

Systems (LMS) Domain
Article · May 2018

CITATIONS READS
0 474

1 author:

Md.Ibnul Adib
University of Malaya
2 PUBLICATIONS 0 CITATIONS

SEE PROFILE

Some of the authors of this publication are also working on these related projects:

Library Management System View project

All content following this page was uploaded by Md.Ibnul Adib on 18 July 2018.

The user has requested enhancement of the downloaded file.

 SOFTWARE REUSABILITY (WOC 7003)

CASE STUDY

Library Management Systems (LMS)

Domain

17-May-2018

MD IBNUL ADIB – WOC 160021

1
Table of Contents
Library Systems Domain Description......................................................................................................3
Requirements Capture (Part A)...............................................................................................................4
LMS Use Case Diagram..........................................................................................................................4

LMS Class Diagram................................................................................................................................4

Use Case Components (Part A*)..............................................................................................................4

Robustness Analysis (Part B)....................................................................................................................5
Design Phase (Part C)...............................................................................................................................5
Variation Points Overview........................................................................................................................6
Registration.............................................................................................................................................6

Borrow....................................................................................................................................................6

Return......................................................................................................................................................6

LMS Domain Solutions.............................................................................................................................7

Requirements Capture (Part A)...........................................................................................................7

Use Case Diagram.............................................................................................................................7

LMS Class Diagram..........................................................................................................................8
Use Case Component (Part A*)........................................................................................................9
Analysis Component (Part B).............................................................................................................11

Registration Management..............................................................................................................11
Borrow Management......................................................................................................................12
Return Management.......................................................................................................................13
Design Component (Part C)...............................................................................................................14

Borrow Management......................................................................................................................14
Return Management.......................................................................................................................15
UML Tools Used......................................................................................................................................16
Reference.................................................................................................................................................16

2
Library Management Systems Domain
Description
As a Lead of the modelling system Engineering Team, which has been assigned to model a
reusable component system for a Library Management Systems Domain that has to cover
requirements capture, robustness analysis and design.

The organization might want the component system to be exceptionally successful to be reusable
and adaptable for building up another library management system that would have the capacity
to deploy on any operating system(OS) platform.

The newly customized system will allow book lovers to register as a borrower for which it is
mandatory to pay a registration fee that can be renewed after every 1 year calculated from the date of
registration. A borrower will be given a month of grace period after a year has been completed. In
case of failure for not paying registration renewal fees within a month after renewal date,

A borrower cannot borrow more than 3 books from the library. A borrowed book has a period of a
month. By end of a month from the borrowed date, the borrower must return the book. The borrower
will be notified after one week of the due date of return, after delay of 2 weeks there will be a fine
imposed on the borrower calculated based on the number of days in delay. This will lead to a
suspension for the borrower. If the borrower has been fined 3 times like this, he/she will no longer be
considered to be benefitted from the library services and will result in an exclusion.

On the other hand, on an event of annual inventory, the librarian has the authority to delete copies of
books too much damaged or old and request to replace those with new ones. In addition, librarian can
decide to purpose extra book copies which has more demand among borrowers.

3
Requirements Capture (Part A)

LMS Use Case Diagram

➢
The use cases and requirements described in the system are to be modelled as a
comprehensive use case diagram for the library management system.
➢
The simplification and include/extends relationships need to be considered in the
diagram depending on LMS domain.
➢
Furthermore, description of use case for every component needs to be converted.

LMS Class Diagram

➢
Designing a LMS domain class diagram for illustrating structure of library
management system.
➢
Finding appropriate model elements, relationships between different classes, class
attributes and operations.

Use Case Components (Part A*)

➢
Identify and analyze the problem domain of LMS, including inspecting and evaluating
the most common cases of the precise library management system from other findings.
➢
Design a domain component to illustrate the structure of the library management system
which must be traceable between every use case components.
➢
Design every use case along with defining the common functionality and variable
functionality into one use case component system model to an analysis
component system model.

4
Robustness Analysis (Part B)
➢
Taking everything from use case model, continue towards analysis phase from (Part A*)
in need of documenting analysis component system diagram by utilizing proper analysis
techniques along with considering the development and communication platforms.
➢
Show traceability in between the analysis and use case component system model and it
should be descriptive to the level of component traceability between both models.
➢
Variable features exact to the different cases of the LMS needs to be taken into
consideration for both use case and analysis models for identifying variants and variable
points.
➢
Illustrate and develop registration, borrow and return functions by reusing proper
components (with or without variable points) of the use case/ analysis component system
using façade and UML/OOSE import statement. Determine suitable
customization/adaptation of components and variable features into these application
systems.

Design Phase (Part C)

➢
After analysis phase, start with design phase from that to document an appropriate
design component system model utilizing related design techniques as well as taking into
consideration communication and development platforms.
➢
Show traceability in between the analysis and design component system model and
it should be descriptive to the level of component traceability between both models.

5
Variation Points Overview
Registration
In case of Registration / Register, the borrower can either register as a new user and pay or
there will be an option to register as a new user. If the borrower pays on the correct time, then it
is considered as a normal pay. Or else the user will be suspended if he/she has not paid on time.

Borrow
Borrow has loan and available resources coming out from the variation point. The user can borrow a
book under loan if number of books is less than 3. If the book is in a waiting list and later is confirmed to
be available for borrow, a notification will be sent by confirming whether the resource is available or no.

Return
From Return variation point, there is fine fee and Borrow Penalty. There will be a notification
sent if the book is being returned within the available time of fine. Under Borrow Penalty, there
is suspend and excluded.

6
LMS Domain Solutions
Requirements Capture (Part A)

Use Case Diagram

7
LMS Class Diagram

8
Use Case Component (Part A*)
Use Case Model (Registration)

Use Case Model (Borrow)

9
Use Case Diagram (Return)

10
Analysis Component (Part B)

Traceability between the use case component model and the analysis object component
model
Registration Management

11
Borrow Management

12
Return Management

13
Design Component (Part C)

Traceability between the analysis object component model and the design object
component model

Borrow Management

14
Return Management

15
 UML Tools Used
➢
Draw.io

Reference
➢
Architecture process and organization for business success

16

View publication stats