Download as pdf or txt
Download as pdf or txt
You are on page 1of 7

Case study

UNIT XIV CASE STUDY


NOTES
Structure
14.0 Introduction
14.1 Objective
14.2 Foundation Class Library
14.2.1 Library Management system
14.3 Client server computing

14.0 INTRODUCTION
The aim of a case study is to teach the student to observe the issue
professionally and solve the problem of the definite case successfully. The
cause and effect of the problem which has occurred and focus on the
solution of the matter with the help of the reliable and valid methods. The
success of the case study depends on the quality of the chosen solution.
14.1 OBJECTIVE
After going through this unit, you will be able to:
Understand what a case study is
Understand a particular topic clearly with cause and solution
Understand the methods available to reach a solution

14.2 FOUNDATION CLASS LIBRARY


14.2.1. Library Management system
The case study is library management software for the purpose of
monitoring and controlling the transactions in a library. This case study on
the library management system gives us the complete information about
the library and the daily transactions done in a Library. We need to
maintain the record of news and retrieve the details of books available in
the library which mainly focuses on basic operations in a library like
adding new member, new books, and up new information, searching books
and members and facility to borrow and return books. It features a familiar
and well thought-out, an attractive user interface, combined with strong
searching, insertion and reporting capabilities. The report generation
facility of library system helps to get a good idea of which are borrowed by
the members, makes users possible to generate hard copy.

The following are the brief description on the functions achieved through
this case study:

Self-Instructional Material
Case study
End-Users:
also to cater the needs
NOTES
of the users.

librarian.

Class Diagram

Classes identified
Library are Books database
Library
Location Title
Librarian
Librarian id Author
Books Database Book id
User +update()

Vendor

Librarian User
Vendor
Details Details
Book details
Librarian id User id
+Issue status()
+search()
+Complaint resolution() +search()
+supply book()
+tracking() +request()
+payment
+calculate fine() +complaints()
details()
+vendor request() +pay fine()
+payment()

General user Registered user

+register() +login()
+history()
+unregister()

Actors vs Use Cases

Librarian

User

Self-Instructional Material
Case study

NOTES

Books Database

status

Vendors

Sequence Diagram
Sequence diagram for searching a book and issuing it as per the
request by the user from the librarian:

Self-Instructional Material
Case study

NOTES

Collaboration Diagram for searching a book and issuing it as per the


request by the user from the librarian:
1.1 Authenticate
2.1 Search for the book
3.1 Book status:issued
Library Books database
computer

1.1.1.1 logged in or wrong password


2.1.1.1 book found or not 1.1.1 Acknowledge
3.2 book issued 2.1.1 acknowledge of the search
4.1 logout successful

1. login
2. enter book name
3. request for issue
4. logout
User

Self-Instructional Material
Case study
Activity Diagram
Activities:
User Login and Authentication NOTES
Search book operation for Reader
Acknowledge and Issue books to the users by the Librarian
Provide books requested by the Librarian from the Vendor
Bill payment from the Librarian to the Vendor
Status of the books updated in the Books Database

Start

login

No Yes

Valid user

Provi Payme Track


de nt complai

Search
book
Book

No
Book
updat Reque
Yes st to
found Pay bill to
librari

Updated
No

Reque
st for
Yes
i

logout

Self-Instructional Material
Case study State Chart Diagram
States:
NOTES Authentication
Successfully logged on or re-login
Search for a book (user) / request the vendor (librarian) / provide the
requested book (vendor)
Receive acknowledgement
Logged off / re-search / new function

Transitions:
Authenticate ---> Logged in
Logged in ---> Search <---> Acknowledgement
Logged in ---> Request Vendor <---> Provide Book <--->
Acknowledgement
Logged in ---> Provide Book <---> Acknowledgement
Acknowledgement ---> Logged off

Component Diagram
Components:

Register Page (visitor / vendor)


Login Page (user / librarian / vendor)
Search Page (user / librarian / vendor)
Request Vendor Page (librarian)
Request Book Issue Page (user / vendor)
Issue Status Page (librarian)
Make Payment Page (librarian / vendor)Provide Books Page (librarian)
Logout Page (user / librarian / vendor)

Self-Instructional Material
Case study

NOTES

Deployment Diagram
Systems Used:

Local Consoles / Computers for login and search purposes by users,


librarian and vendors.
Library LAN Server interconnecting all the systems to the Database.
Internet to provide access to Venodors to supply the requested books by
the Librarian
Vendor Server to maintain the records of the requests made by the librarian
and books provided to the library.

Self-Instructional Material

You might also like