Ex.

No:1 LIBRARY MANAGEMENT SYSTEM

Date:

AIM
To design an object oriented model for Library Management System using Argo
UML and to implement it using Java.

PROBLEM STATEMENT
The library management system is a software system that issues books and
magazines to registered students only. The student has to login after getting
registered to the system. The borrower of the book can perform various functions
such as searching for desired book, get the issued book and return the book.
CLASS DIAGRAM
A class diagram in the unified modeling language is a type of static structure
diagram that describes the structure of a system by showing the system’s classes,
their attributes, operations and the relationships among objects. The library
management system makes use of the following classes user,

~1~
librarian, system and DBA.

USE CASE DIAGRAM

Use case is a list of actions or events. Steps typically defining the interactions
between a role and a system to achieve a goal. The use case diagram consists of
various functionality performed by actors like user, librarian, system and DBA.

logi
n

enter name and <<actor>

password >

display
page

requesting for
use book
r

display book
details

search for
book libraria
n

issue
book

return
book

DBA
maintain
database

~2~
DEPLOYMENT DIAGRAM

Deployment diagram is a structure diagram which shows

architecture of the system as deployment of software artifacts to
deployment target. It is the graph of nodes connected by
communication association. It is represented by three dimensional
box. The device node is library management system and execution
environment nodes are user, librarian, system and DBA.

COMPONENT DIAGRAM

Component diagram shows the dependencies and interactions

between software components. Component diagram carries the most
important living actors of the system i.e, user, librarian and DBA.

~3~
 library
management

use DBA
r libraria
n

STATECHART DIAGRAM

State chart diagram is also called as state machine diagram. The

state chart diagram contains the states in the rectangular boxes and the
states are indicated by the dot enclosed. The state chart diagram
describes the behavior of the system. The state chart diagram involves
eight stages such as login, enter details, requesting for book, display
book details, search book, issuebook, return book and logout.

logi enter requestin display

n detail g for book

logou return issue searc

t book book h

COLLABORATION DIAGRAM
Like sequence diagram collaboration diagrams are also called as interaction
diagram. Collaboration diagram convey the same information’s as sequence
diagram but focus on the object roles instead of the times that messages are sent.
Here the actions between various classes are represented by number format for the
case of identification.

~4~
SEQUENCE DIAGRAM
A sequence diagram represent the sequence and interactions of a given use case or
scenario. Sequence diagram capture most of the information about the system. It
is also represent in order by which they occur and have the object in the system
send message to one another. Here the sequence starts with interaction between
user and the system followed by database. Once the book have been selected the
next half of sequence starts between librarian and user followed by database.

~5~
ACTIVITY DIAGRAM

Activity diagram are graphical representation of workflows of stepwise activities

and actions with support for choice, iteration and concurrency. Here in the activity
diagram the user login to the system and perform some main activity which is the
main key element to the system.

~6~
RESULT

Thus the various UML diagrams for library management system was drawnand
the code was generated successfully.

~7~
 Ex No 2 ATM TRANSACTIONS
Date :

AIM

To design an object oriented model for ATM Transaction system using Argo UML.

MODULAR DESCRIPTION

VERIFICATION OF ATM CARD

For the verification of ATM card by the system, the user will enter the secret code. The pin
number or code number is verified with the database of the customers. If the code exactly is
matched with database of that of the customers then transaction can be performed. If the
code does not match withthe database of the customer then the user is requested again to re-
enter the pin number of the accesscard and is continued further.

TRANSACTION

In this module, the necessary transaction to be performed by the user is displayed as

option by the system. The transaction options are withdrawal, deposit, balance
enquiry, mini statement, pin change. The users can withdraw the amount from their
account if the amount is available in their account. The users can also deposit the
amount in their account either by cash or cheque. This module helps the users to
check their balance in their account through balance enquiry and also theycan get the
mini statement for recent transaction done over their account. This module allows the
users to change their pin number if they need.

DISPLAY AND RECEIPT

In this module, after the user performs the transaction process the system displays the
balance amount available in the account and the amount withdrawn by the user through
receipt. The receipt will be provided at the end of the transaction process.

~8~
~9~
~ 10 ~
~ 11 ~
RESULT

Thus the various UML diagrams for ATM Transaction were drawn and code was generated
successfully.

~ 12 ~
Ex.No:03 STUDENT INFORMATION SYSTEM
Date:

AIM
To design an object oriented model for Student information system using Argo
UML.

PROBLEM STATEMENT

The student must register by entering the name and password to login the form.
The admin select the particular student to view the details about that student and
maintaining the student details. This process of student information system is
described sequentially through following steps. The student registers the system.
The admin login to the student information system. He/she search for the list of
students. Then select the particular student. Then view the details of that student.
After displaying the student details then logout.

CLASS DIAGRAM
The class diagram is the graphical representation of all classes used in the system.
The class diagram is drawn as rectangular box with three components or
compartments like class name, attributes and operations. The student information
system makes use of the following classes like student, staff, system, DBA and
server.

~ 13 ~
COLLABORATION DIAGRAM
A Collaboration diagram represents the collaboration in which is a set of objects
related to achieve a desired outcome. In collaboration, the sequence is indicated
by numbering the message several numbering schemes are available. Login,
request access, allow access, display, view details, logout, login, request access,
allow access, display, enter profile, enter mark, provide data, logout, store data,
update data.

~ 14 ~
SEQUENCE DIAGRAM

A Sequence diagram represent the sequence and interactionof a

given usecase or scenario. Sequence diagram capture most of the
information about the system. Here the sequence starts between the
student and the system. The second half of interaction takes place
between staff and system then by police and followed

~ 15 ~
 by database. The student first login to the system and then viewthe
details of the details. Staff login to the system enter mark and enter the
details of the student. DBA store and update the detailsof the student.

COMPONENT DIAGRAM

Component diagram carries the major living actors of thesystem.

The component diagram main purpose is to show the
structural relationship between components of the system.The main
component of the system is student information system and the other
components of the system are student, staff and DBA.
student
information
system

student staff DBA

USE CASE DIAGRAM

Use case diagram is a graph of actors, a set of use cases, association betweenthe
actors and the use cases and generalization among the cases. Use case diagram is a
list of actions or events. Use case diagram was drawn to represent the static design
view of the system. Steps typically defined the interactions between a role and a
system to achieve a goal. The use case diagram consists of various functionality
performed by the actors like student, staff, system, DBA and server. The use case
diagram consists of various functionality like login, display, enter profile, enter
mark, view details, update details, allow access, request access, store details,
logout.

~ 16 ~
 logi
n

<<actor>
displa >
y projection
of student

enter
profile

enter
mark

s
tudent view
details staf
f

update
details

allow acces
serve s
r DBA

reques t
access

store
data

DEPLOYMENT DIAGRAM

Deployment diagram shows the configuration of runtime

processing elements and the software components processes and
objects that live in them. Component diagram are used in conjunction
with deployment diagram to show how physical modules code are
distributed on various hardware platform. The processor node in the
system is student information system andthe execution environment
nodes or device nodes are student,staff and DBA.

~ 17 ~
STATE CHART DIAGRAM
A State chart diagram is also called as state machine diagram. The state chart
contains the states in the rectangular boxes and the states are indicated by the dot
enclosed. The state chart diagram describes the behavior of the system. The state
chart involves six stages such as login, enter mark, enter profile, view details,
provide details, update details, store details and logout.

logi ente enter

n r profil

view
details

logou store updat

t detail e

~ 18 ~
ACTIVITY DIAGRAM

Activity diagram are graphical representation of stepwise

activities and actions with support for choice, interaction and
concurrency. Here in the activity diagram the student login to the
system and view the details of the student. The staff login to the system
for entering the student details and update the details in the database.
The final interaction is the DBA store the details of the student.

~ 19 ~
RESULT

Thus the various UML diagrams for student informationsystem were drawn and code was generated
successfully.

~ 20 ~
 Ex No 04 MATRIMONY SERVIVE
Date:

AIM:
To create a system to perform the Matrimony Service.

PROBLEM STATEMENT

In UML, a Matrimony Service can be modeled using several diagrams, including use
case diagrams, class diagrams, and sequence diagrams. Here's a brief overview of
how a Matrimony Service can be represented in UML

Use Case Diagram:

A use case diagram can be used to show the different actors (users) of the matrimony
service and the different use cases they can perform. For example, the actors could be
registered users, Admin’s, and guests. The use cases could include creating a profile,
searching for potential matches, sending messages, and managing account settings.

~ 21 ~
Class Diagram:

A class diagram can be used to show the different classes and their relationships in the

matrimony service. For example, there could be classes for user profiles, messages,

preferences, and matches. The relationships between these classes could include

inheritance, aggregation, and association

~ 22 ~
Activity Diagram:

An activity diagram can be used to show the different activities or processes involved in using
the matrimony service. For example, an activity diagram could show the steps involved in
searching for potential matches, such as setting search criteria, viewing search results, and
sending messages

~ 23 ~
~ 24 ~
Sequence Diagram:

A sequence diagram can be used to show the interactions between different objects or
components in the matrimony service. For example, a sequence diagram could show the
steps involved in creating a user profile, such as entering personal information, uploading
photos, and setting preferences.

State Diagram:

A state diagram can be used to show the different states and transitions for a particular
object or component in the matrimony service. For example, a state diagram could show
the different states that a user profile can be in, such as incomplete, pending approval,
active, and deactivated.

~ 25 ~
RESULT

Thus the various UML diagrams for Matrimony Service were drawn and code was generated
successfully

~ 26 ~
Ex no: 5 STOCK MAINTENANCE

Date:

AIM:
To create a system to perform the Stock maintenance

(I)PROBLEM STATEMENT
The stock maintenance system must take care of sales information of the
company and must analyze the potential of the trade. It maintains the number of
items that are added or removed. The sales person initiates this Use case. The
sales person is allowed to update information and view the database.

(II) SOFTWARE REQUIREMENT SPECIFICATION

PURPOSE
The entire process of Stock maintenances done in a manual manner
Considering the fact that the number of customers for purchase is increasing every
year, a maintenance system is essential to meet the demand. So this system uses
several programming and database techniques to elucidate the work involved in
this process.

SCOPE
• The System provides an interface to the customer where they can fillin
orders for the item needed.
• The sales person is concerned with the issue of items and can usethis
system.

~ 27 ~
 • Provide a communication platform between the customer and thesales
person.

TOOLS TO BE USED
• Eclipse IDE (Integrated Development Environment)
• Rational Rose tool (for developing UML Patterns)
(III) USE CASE DIAGRAM
The functionality of a system can be described in a number of different
use-cases, each of which represents a specific flow of events in a system. It is a
graph of actors, a set of use-cases enclosed in a boundary, communication,
associations between the actors and the use-cases, and generalization among the
use-cases

Place
Order

Track
order

Custome
r
Validate
Customer
Ship
Order

Ship Partial
Order
Sales
Person

Bill Customer

Fig.3. USE CASE DIAGRAM

~ 28 ~
(IV) ACTIVITY DIAGRAM

It shows organization and their dependence among the set of components.

These diagrams are particularly useful in connection with workflow and in
describing behavior that has a lot of parallel processing. An activity is a state of
doing something: either a real-world process, or the execution of a software
routine.

Custome
r
Sales
Request
Service

Pay Take Fill

Order Order

Delive
r

Collec
t

Fig.4. ACTIVITY DIAGRAM

~ 29 ~
(V) CLASS DIAGRAM

Description:
 A class diagram describes the type of objects in system and
various kinds of relationships that exists among them.
 Class diagrams and collaboration diagrams are alternate
representations of object models.

Fig.5. CLASS DIAGRAM

~ 30 ~
(VI) UML INTERACTION DIAGRAMS

It is the combination of sequence and collaboration diagram. It is used to

depict the flow of events in the system over a timeline. The interaction diagram is
a dynamic model which shows how the system behaves during dynamic
execution.

An Order
An An Order
An An Order
An Order Line AA Stock
Stock
Order Order Line Item
Item
Prepar
e
Prepar
e
Has
Stock:=Check

[has
Stock]:Remove
Needs reorder:=needs to
reorder()

[needs reorder]:new
A AReorder
Reorder
Item Item

AA Delivery
Delivery
Item
Item
[Has Stock]:
new

Fig.6.1 SEQUENCE DIAGRAM

~ 31 ~
COLLABORATION DIAGRAM

Collaboration diagram and sequence diagrams are alternate representations

of an interaction. A collaboration diagram is an interaction diagram that shows the
order of messages that implement an operation or a transaction.

ORDER ENTRY
WINDOW

1: prepare()
AN ER
ORD

2: *[for all order lines]prepare()

3: hasstock=check
needs Reorder=need to Reorder

ORDER LINE STOCK ITEM

4: [hasstock]remove()

6: 5: [needs Reorder]:new
[hasstock]:ne
w

DELIVERY ITEM REORDER ITEM

~ 32 ~
(VII) PARTIAL LAYERD LOGICAL ARCHITECTURE DIAGRAM

UI

Swing Text

StMain System StMaint

Console

Domain

Customer Order

Register Invoice Stock

Shipment
Product

Technical Se rvices

Persistence SOAP Log4J

DBFacade

~ 33 ~
(VIII) DEPLOYMENT DIAGRAM AND COMPONENT DIAGRAM

Deployment diagrams are used to visualize the topology of the physical

components of a system where the software components are deployed.

Fig.8.1.DEPLOYMENT DIAGRAM

LAN
<<database>> <<client
:MySQL workstation>>:
GenericPC

Component Diagram

Component diagrams are used to visualize the organization and relationships

among components in a system.

Fig.8.2.COMPONENT DIAGRAM

~ 34 ~
RESULT
Thus the project for stock maintenance system has beensuccessfully
executed and codes are generated.
~ 35 ~