Project Library System

PROJECT NO.1 LIBRARY MANAGEMENT SYSTEM

USE CASE DIAGRAM

ACTORS ·

Registered User

·

Borrower

·

Librarian

·

Student

·

Staff

USE CASES ·

Login

·

Browse

·

Search

·

Article Printing

·

Manage Browser

·

Manage Items

·

Manage Titles

·

Assure Identity Of Browser

·

Manage Suppliers Data

·

Make Reservation

·

Remove Reservation

·

Check Out Item

·

Return Item

FUNCTIONAL REQUIREMENTS ·

Only a Registered User can Access the Library Management System

·

Librarian & Borrower are the Registered Users

·

Borrower can be a Student or a Staff member

·

The Library system has to maintain all the relevant information about books, Student Information.

·

The Borrower has to select the Books/Journals(Items)/can make Reservation from the given list.

·

The Librarian has to check for the status.

·

The Library system has to send the status of the book.

·

The Librarian sends an acknowledgement to the Borrower.

·

The Librarian Performs the required transaction

·

The Librarian updates the relevant information of Books or Journals.

COMMON MODELING TECHNIQUES: To model the context of system. ·

Identify the actors that surround the system by considering which require help from the system to perform their tasks; which groups are needed to execute the system’s function, which groups are needed to interact with external hardware or other software system and which systems are needed

to

perform

secondary

functions

for

administration

and

maintenance. ·

Organize actors that are similar to one another in a generalization / specification hierarchy. (Registered User—Borrower, Librarian)

·

Where it aids understandability, provide a stereotype for each such actor.

·

Populate the use case diagram with these actors and specify the paths of communication for each actor to the system’s Use Cases.

CLASS DIAGRAM (Checkout Item)

CLASS NAMES: ·

UIAgent

·

Borrower

·

Title

·

Item

·

CheckoutItemForm

·

CheckoutItemFormContorller

·

Staff

·

Student

UIAgent class: Operations: ·

main()

Borrower class: Operations: ·

checkout()

Title class: Operations: ·

getmatching()

·

getitems()

Item class: Operations:

·

setStatus()

CheckoutItemForm Class: Operations: · specifycriteria() · search() · selecttitle() · selectitem() · checkout()

CheckoutItemFormController Class: Operations: · search() · getItem() · checkout()

Student Class: Staff Class:

FUNCTIONAL REQUIREMENTS: ·

Each class has some responsibilities to be performed.

·

Based on responsibilities that each class has, its attributes and Operations are identified.

·

Depending on the type of attributes and operations their visibility is chosen.

·

Depending on the Class its multiplicity is decided (i.e. how many other classes are related to it).

·

Based on the functionality messages are given to relate classes

·

Only a Registered User can Access the Library Management System

·

Librarian & Borrower are the Registered Users

·

The Library system has to maintain all the relevant information about books, Student Information.

·

The Borrower(Student, Faculty) has to search the Books/Journals and can make Reservation from the given list.

·

The Librarian has to check for the Item status.

·

The Library system has to send the status of the book.

·

The Item class updates the relevant information of Books or Journals (Set Status).

COMMON MODELING TECHNIQUES: To model a collaboration. ·

Identify the Mechanism would like to model. A mechanism represents some function or behavior of the part of the system you are modeling that results from the interaction of a society of classes, interfaces and other things.

·

For each mechanism identify the classes, interfaces and other collaborations that participate in this collaboration that participate. Identify the relationships among all there things as well.

·

Use scenario to work through there things. A long the way, you’ll discover parts of your model that were missing and parts that were just plain semantically.

·

Because sure to populate there elements with their contents. For classes, start with getting a good balance of responsibilities, then; overtime turn there into concrete attribute and operations.

SEQUENCE DIAGRAM (Checkout Item) OBJECTS: ·

Borrower

·

UIAgent

·

CheckoutItemForm

·

CheckoutItemFormcontroller

·

Item

·

Title

MESSAGES: ·

Specify Criteria

·

Search

·

Get matching

·

Select title

·

Get item

·

Select item

·

Checkout

·

Set status

. FUNCTIONAL REQUIREMENTS ·

Registered User Requests Transaction By Specifing Criteria

·

User searches for an Item

·

Depending on the Status Controller performs Required Transaction (Checkout Item, Return, Renewal).

·

Update Status

·

Complete required Transaction.

COMMON MODELING TECHNIQUES: To model a flow of control by time ordering. ·

Set the context for the interaction, whether it is a system, subsystem, operation or class or one scenario of a use case or collaboration.

·

Set the stage for the interaction by identifying which objects play a role in the interaction lay them out on the sequence diagram from left to right, placing the more important objects to the left and their neighboring objects to the right.

·

Set the lifetime for each object. In most cases, objects will persist though the entire interaction and explicitly indicate their birth and death will appropriately stereotyped messages.

·

Starting with the message that initiates this interaction layout each subsequent message from top to bottom, between the lifelines.

·

If you need to visualize the nesting of messages or the points in time when actual computation is taking place, ad an each object lifeline with its focus of control.

·

If you need to specify time or space constraints, adorn each message with a timing mark and attach suitable time or space constraints.

·

If you need to specify time or space constraints adorn each message.

·

To specify this flow of control more formally, attach pre and post conditions to each message.

COLLABORATION DIAGRAM (Validating user) OBJECTS: ·

UIAgent

·

Validator

·

Form

·

FormController

FUNCTIONAL REQUIREMENTS ·

Registered User Specifies His User Name And Password

·

His Password is Verified By The Validator

TO MODEL A FLOW OF CONTROL BY ORGANIZATION ·

Set the context for the interaction.

·

Set the stage for the interaction.

·

Set the initial properties of each of these objects.

·

Specify the links among these objects, along which messages may pass. ·

Layout the association links first, there is the most important ones, because they represent structural connections.

·

Layout other links next, and adorn then with suitable path sterotypes. ·

Starting with the message that initiates this interaction attach each subsequent message to the appropriate link.

·

If you need to specify time or space constraints adorn each message with a timing mark and attach suitable time or space constraints.

·

If you need to specify this flow of control more formally, attach pre and post conditions to each message.

STATE CHART DIAGRAM EVENTS: ·

Logged in

·

Specify criteria

·

Make reservation.

·

Checkout Item.

FUNCTIONAL REQUIREMENTS ·

User Gets Logged In

·

User searches for an Item

·

Selects the Type of Transaction to be Performed

·

Required Operation is performed.

COMMON MODELING TECHNIQUES: To model a reactive objects. ·

Choose the context for the state machine, whether; it is a class, a use case or system.

·

Decide on the stable states of the object by considering the conditions in which the object may exist for some identifiable period of time.

·

Decide on the meaningful partial ordering of stable states over the lifetime of the object.

·

Decide on the event that may triggers a transition from state to state.

·

Attach actions to these transitions and / or to these states.

·

Check that all states are reachable under some combination of events.

·

Check that all states are reachable under some combination of events.

·

Check that no state is a deadened from which no combination of events will transition the object out of that state.

·

Trace through the state machine, either manually as by using tools, to check it against expected sequences of events and their responses.

ACTIVITY DIAGRAM ACTION STATES : ·

Enter Login Id and Password.

·

Validate Password

·

User Interaction Starts

·

Select The Service Required

·

Search Item

·

Printing An Article

·

Make Reservation

·

Checkout An Item

·

Return An Item

·

Managing Browsers

·

Managing Items

·

Managing Suppliers Data

·

Managing Titles

·

Logout

·

Exit.

FUNCTIONAL REQUIREMENTS ·

Initially Registered User can Login into Library Management System

·

His Password is Verified

·

Branching takes place if correct continues accessing else tries Logging again

·

The Required Transaction is selected by the user.

·

Required Operation is performed.

·

The user can repeat any operation required again or log out of the system,

COMMON MODELING TECHNIQUES: To model an Operation. ·

Collect the abstractions that are involved in this operation.

This

operation parameters the attributes of the enclosing class, and enter certain neighboring classes. ·

Identify the preconditions at the operation’s initial state and the post conditions at the operations final state.

·

Beginning at the operation’s initial state, specify the activities and actions that take place over time and render then in the activity diagram as either activity states or action states.

·

Use branching as necessary to specify conditional paths and iteration. (Verify Password)

·

Only if an active class owns this operation, Use joining and forking as necessary to specify parallel flows of control.