EXPERIMENT NO. 1(a)

AIM:- To draw a use case diagram of Library Management System.

EQUIPMENT/SOFTWARE USED:- Rational Rose

THEORY:-

Use Case Diagram

Definition

A use case diagram in the Unified Modeling Language (UML) is a type of behavioral diagram defined by and created from a Use-case analysis. The use case diagram shows the position or context of the use case among other use cases. A use case diagram at its simplest is a representation of a user's interaction with the system and depicting the specifications of a use case. A use case diagram can portray the different types of users of a system and the various ways that they interact with the system. This type of diagram is typically used in conjunction with the textual use case and will often be accompanied by other types of diagrams as well.

As an organizing mechanism, a set of consistent, coherent use cases promotes a useful picture of system behavior, a common understanding between the customer/owner/user and the development team

Aim/purpose of use case diagram

Its purpose is to present a graphical overview of the functionality provided by a system in terms of actors, their goals (represented as use cases), and any dependencies between those use cases. The main purpose of a use case diagram is to show what system functions are performed for which actor.

Elements of use case diagram

UCDs have only 4 major elements: The actors that the system you are describing interacts with, the system itself, the use cases, or services, that the system knows how to perform, and the lines that represent relationships between these elements.

ACTORS : An actor portrays any entity (or entities) that performs certain roles in a given system. The different roles the actor represents are the actual business roles of users in a given system. An actor in a use case diagram interacts with a use case. For example, for modeling a banking application, a customer entity represents an actor in the application.

USE CASE : A use case in a use case diagram is a visual representation of a distinct business functionality in a system.

SYSTEM BOUNDARY: A system boundary defines the scope of what a system will be. A system cannot have infinite functionality.

ASSOCIATION: An association is a connection between an actor and a use case. An association indicates that an actor can carry out a use case. Several actors at one use case mean that each actor can carry out the use case on his or her own and not that the actors carry out the use case together:

Use case diagram of Library Management System:-

Description:-

1. Actors(a) User-Specialization Actors: Student, Faculty(b) Librarian(c) Vendor

2. Use Cases(a) Search book

Introduction: User looks for a particular book in the libraryActors: UserPre-Condition: Library Management System, should be logged in by the user.Post-Condition: User either finds the required book in the list or exits due to book being found.

Normal Flow: 1. User enters search items. 2. System displays all possible matching items. 3. User selects the required book from the specified list. 4. System displays the selected book.

Alternative Flow: 1. System has no books to search. 2. System has no books matching user terms. 3. User does not find the required book in the displayed list. 4. User exits and tries more search items.

(b) FoundIntroduction: User finds a book he is looking for.Actors: UserPre-Condition: User enters the book term to be searched.Post-Condition: The book is found.Normal Flow: 1. System displays the required book.

2. User affirms.Alternative Flow: 1. User exits without affirming.

(c) Not foundIntroduction: User does not find the book he is looking for.Actors: UserPre-Condition: User enters the book term to be searched.Post-Condition: The book is not found.Normal Flow: 1. System does not display the required book.

2. User exits and tries more search items.Alternative Flow: 1. User exits without affirming and tries more search items.

(d) Return bookIntroduction: User returns the book.Actors: UserPre-Condition: User has issued a book.Post-Condition: The book is returned.Normal Flow: 1. User has a book.

2. User returns the book.Alternative Flow: 1. User exits without returning. 2. User tries more search items.

(e) Request Issue of BookIntroduction: User requests issue of a book.Actors: UserPre-Condition: The availability of the book is true.

Post-Condition: The user selects a book to be issued.Normal Flow: 1. User selects of the available book.

2. System validates the book.Alternative Flow: 1. If the user selects an invalid book, system notifies the user of invalid selection.

(f) Fine paymentIntroduction: User pays the fine for returning the book late.Actors: UserPre-Condition: User has not returned the book.Post-Condition: User pays fine.Normal Flow: 1. Librarian Calculates Fine. 2. User pays the fine, returns the book. 3. Database is updated.Alternative Flow: 1. User does not pay the fine. 2. User tries more search items. 3. User exits without paying the fine.

(g) Request new Book

Introduction: User requests for a new book.Actors: UserPre-Condition: User is not able to search a particular book.Post-Condition: User places an order for a new book.Normal Flow: 1. Librarian orders the vendor for a new book. 2. Vendor takes the order and provides the new book. 3. Database is updated.Alternative Flow: 1. User does not find a book. 2. User tries more search items. 3. User exits.

(h) Issue Book

Introduction: Librarian issues book .Actors: LibrarianPre-Condition: User wants a book.Post-Condition: Librarian issues the book.Normal Flow: 1. User requests for a book. 2. Librarian issues the book. 3. Database is updated.

Alternative Flow: 1. User does not find a book. 2. System does not have the search item.

3. Librarian places an order for new books. 4. User exits.

(i) Manage all Issues

Introduction: Librarian manages all the issues.Actors: LibrarianPre-Condition: There is an issue by the user.Post-Condition: Librarian manages the issue.Normal Flow: 1. Librarian orders the vendor for a new book. 2. Alternative Flow: 1. User does not find a book.

Manage all issues

I. Introduction: The actor manages all the issues regarding the library.II.Actors: LibrarianIII.Pre-Condition: There is an issue raised by the user.IV.Post-Condition: Librarian manages the issue, system updates the database.V.Normal Flow: 1. User raises an issue. 2. Librarian manages the issues.VI. Alternative Flow: N/AVII.Related Use Cases: N/A

Collect Fine

I. Introduction: The actor collects the fine for returning the book late.II.Actors: LibrarianIII.Pre-Condition: User has returned the book late and librarian calculates the fine.IV.Post-Condition: Librarian collects the fine, system updates the database.V.Normal Flow: 1. User returns the book late. 2. Librarian calculates the fine.VI. Alternative Flow: N/AVII.Related Use Cases: N/A

Gives order

I. Introduction: The actor gives order for a new book.II.Actors: LibrarianIII.Pre-Condition: Librarian orders a new book.IV.Post-Condition: Vendor provides a new book..V.Normal Flow: 1. User requests for a new book 2. Librarian orders the vendor for a new book. 3. Vendor processes the order and provides the book.VI. Alternative Flow: In step 3 of normal flow,Librarian gives order to the vendor.

VII.Related Use Cases: N/A

Takes order

I. Introduction: The actor takes an order from the Librarian.II.Actors: Vendor.III.Pre-Condition: Librarian gives order.IV.Post-Condition: Vendor takes the order, system updates the database.V.Normal Flow: 1. User requests for a new book from the library. 2. Librarian orders the vendor. 3. Vendor takes the order.VI. Alternative Flow: N/AVII.Related Use Cases: N/A

Process order

I. Introduction: The actor processes an order.II.Actors: Vendor.III.Pre-Condition: Librarian gives order.IV.Post-Condition: Vendor processes the order, system updates the database.V.Normal Flow: 1. Librarian orders the vendor for a new book.. 2. Vendor takes the order and processes it.VI. Alternative Flow: N/AVII.Related Use Cases: N/A

Provides new book

I. Introduction: The actor provides a new book.II.Actors: Vendor.III.Pre-Condition: Librarian gives order.IV.Post-Condition: Vendor processes the order and provides a new book, system updates the database.V.Normal Flow: 1. Vendor takes the order and processes it. 2. Vendor provides a new bookVI. Alternative Flow: N/AVII.Related Use Cases: N/A

RESULT:- Use case diagram for library management system has been drawn.