Experiment No:- 1

AIM:- Explain Introduction to UML.

OUTPUT:- The Unified Modeling Language is a standard

graphical language for modeling object oriented language. It

was developed in mid 1990s as a collaborative effort by James

Rambough, Gredy Booch and Ivar Jacobson, each of whom had

developed its own notation in the early 1990s. The ‘U’ in UML

stands for Unified sine its three developers combined the best

features of the language they have previously developed. UML

was adopted by object Management Group at 1997.

Structural View Behavioral View Class Diagram Sequence Diagram Object Diagram collaboration Diagram State Chart diagram Activity Diagram

Implementation View Environmental View Component Diagram Deployment Diagram

Users View Use Case Diagram

1. Users View:- The users view captures the view of the

system in terms of functionalities applied by the system to

its users. It is a black box view of the system where the

internal structure, the dynamic behavior of different system

components, the implementations, etc. are not captured.

The users view can be considered as the central view and

all other views are required to conform to this view. It is

indeed remarkable that even for object oriented

development, we need a functional view. That is because,

after all, a user considered system as providing a set of

functionalities.

2. Structural View:- It is also called as a static model.. it

defines the structure of the problem in terms of the kind of

objects(classes), in a system, identifying all attributes,

operations and relationships with other objects in the

system,

3. Behavioral View:- It captures how objects interacts with

each other in time to realize the system behavior. The

system behavior captures the time dependent behavior of

the system.

4. Implementation View:- This view captures the important

components of the system and their interdependencies.

5. Environmental View:- This view captures how the

different components are implemented on different piece of

hardware.

Experiment No:-2

AIM:- Draw Use case Diagram of Library Management System.

OUTPUT:-

Maintain Book Details

Login

Maintain Faculty Details

Data Entry

OperaterMaintain Student Records

Return Book

Generate Report

Administrator

Librarian

Search Catalog

Library Staff

Query Book

Student / Faculty

Issue Book

Experiment No:-3

AIM:- Draw Use case Diagram of Railway Reservation System.

OUTPUT:-

Report Generation

Update Train Information

Administrator

Reserve Seat

Reservation Clerk

Login

View Reservation Status

View Train Schedule

Passenger

Cancellation

Experiment No:-4

AIM:- Describe the various relationships between classes with

Diagrammatic representation.

OUTPUT:-

BarcodeReader

IssueBookInterfaceBook

+1

+1

Transaction

+1 +1

Member

+student+0...5

+employee+0...10

+faculty+0...10

IssueBookController

+1

+1+1

+1+1

+1

+1

+1

Experiment No:- 5

AIM:- Draw a class Diagram for 'issue book' in LMS.

OUTPUT:-

Experiment No:-7

AIM:- Draw the Sequence diagram for basic flow scenario of

'issue book' use case in LMS.

OUTPUT:-

: LibraryStaff :

BarcodeReader : IssueBookInterface :

IssueBookController : Member : Transaction : Book

1: getBookBarcodeID()

2: acceptBookBarcodeID()

3: getMemberBarcodeID()

4: acceptMemberBarcodeID()

5: displayMemberDetails(MemberBarcodeID)

6: <<destroy>>

7: issueBook(MemberBarcodeID,BookBarcodeID)

8: issueBook(MemberBarcodeID,BookBarcodeID)

9: validate(MemberBarcodeID)

10: issueBook(MemberBarcodeID,BookBarcodeID)

11: updateIssuestatus(BookBarcodeID)

12: incrementBook(MemberBarcodeID)

Experiment No:-8

AIM:- Draw the Sequence diagram for Alternative flow scenario

of 'issue book' use case in LMS

OUTPUT:-

: LibraryStaff : BarcodeReader : IssueBookInterface :

IssueBookController : Member

1: getBookBarcodeID()

2: acceptBookBarcodeID()

3: getBookBarcodeID()

4: acceptMemberBarcodeID()

5: displayMemberDetails(MemberBarcodeID)

6: <<destroy>>

7: issueBook(MemberBarcodeID,BookBarcodeID)

8: issueBook(MemberBarcodeID,BookBarcodeID)

9: validate(MemberBarcodeID)

10: Invalid Membership

11: Invalid Membership

12: Invalid Membership

13: Account Full

14: Account Full

15: Account Full

Experiment No:-9

AIM:- Draw the Sequence diagram for 'withdraw' Use case

regarding 'ATM system.

OUTPUT:-

Customer GenerateCash(card)

Server

1: insertcard()

2: is= stolencard()

3:

5: [!1s]=getpin(card)

6:

7: isv=isvalid(card)

9: [isv]a=getamount()

11: isA=isvalid(a)

14: displaybalance(card)

15: output(card)

4:

8:

10:

12:

13: GenerateCash(Card)

Experiment No:- 10

AIM:- Draw the Collaboration diagram for basic flow scenario of

'issue book' use case in LMS.

OUTPUT:-

: BarcodeReader

: IssueBookInterface

: IssueBookController

: LibraryStaff

: Member

: Transaction

: Book2: acceptBookBarcodeID()

4: acceptMemberBarcodeID()

6: <<destroy>>

5: displayMemberDetails(MemberBarcodeID)

8: issueBook(MemberBarcodeID,BookBarcodeID)

9: validate(MemberBarcodeID)

10: issueBook(MemberBarcodeID,BookBarcodeID)

1: getBookBarcodeID()3: getMemberBarcodeID()

7: issueBook(MemberBarcodeID,BookBarcodeID)

11: updateIssuestatus(BookBarcodeID)

12: incrementBook(MemberBarcodeID)

Experiment No:-11

AIM:- Draw State Chart Diagram of 'Queue'. And explain all its

events.

OUTPUT:-

EMPTY

HOLDING

FULL DEAD

remove()

destroy()

New

[rear=Max-1] ; insert(x)

destroy()

[front=1] ; remove()

destroy()

insert(x)

new()

[rear<Max-1] ; insert(x)

[front>1] ; remove()

State Event/Method Resultant State

New Empty Holding Full Dead

New

new() √

insert()

remove()

destroy()

Empty

new()

insert() √

remove()

destroy() √

Holding

new()

insert() √ √

remove() √ √

destroy() √

Full

new()

insert()

remove() √

destroy() √