Final Uml

Advance Software Engineering File
EXPERIMENT NO -1
AIM: - Introduction to UML
UML is a standard language for specifying, visualizing, constructing,
and documenting the artifacts of software systems.UML was created by Object Management
Group (OMG) and UML 1.0 specification draft was proposed to the OMG in January 1997.
OMG is continuously putting effort to make a truly industry standard.
UML stands for Unified Modeling Language.
UML is different from the other common programming languages like C++, Java,
COBOL etc.
UML is a pictorial language used to make software blue prints.
So UML can be described as a general purpose visual modeling language to visualize,

specify, construct and document software system. Although UML is generally used to
model software systems but it is not limited within this boundary. It is also used to model
non software systems as well like process flow in a manufacturing unit etc.
A conceptual model of UML:

To understand conceptual model of UML first we need to clarify What is a conceptual
model? and Why a conceptual model is at all required?
A conceptual model can be defined as a model which is made of concepts and their
relationships.
A conceptual model is the first step before drawing a UML diagram. It helps to
understand the entities in the real world and how they interact with each other.
As UML describes the real time systems it is very important to make a conceptual model and
then proceed gradually. Conceptual model of UML can be mastered by learning the following
three major elements:
UML building blocks
Rules to connect the building blocks
Common mechanisms of UML
The building blocks of UML can be defined as:
Things
Relationships
Diagrams
(1) Things:
Things are the most important building blocks of UML. Things can be:
Structural
Behavioral
Grouping
Annotational
Structural things:
The Structural things define the static part of the model. They represent physical and
conceptual elements. Following are the brief descriptions of the structural things.
Class:
Class represents set of objects having similar responsibilities.
Interface:
Interface defines a set of operations which specify the responsibility of a class.
Collaboration:
Collaboration defines interaction between elements.
Use case:
Use case represents a set of actions performed by a system for a specific goal.
2
Component:
Component describes physical part of a system.
Behavioral things:
A behavioral thing consists of the dynamic parts of UML models. Following are the
behavioral things:
Interaction:
Interaction is defined as a behavior that consists of a group of messages exchanged among
elements to accomplish a specific task.
State machine:
State machine is useful when the state of an object in its life cycle is important. It defines the
sequence of states an object goes through in response to events. Events are external factors
responsible for state change.
Grouping things:
Grouping things can be defined as a mechanism to group elements of a UML model
together. There is only one grouping thing available:
Package:
Package is the only one grouping thing available for gathering structural and behavioral
things.
Annotational things:
Annotational things can be defined as a mechanism to capture remarks, descriptions,
and comments of UML model elements. Note is the only one Annotational thing available.
Note:
A note is used to render comments, constraints etc of an UML element.
(2) Relationship:
Relationship is another most important building block of UML. It shows how
elements are associated with each other and this association describes the functionality of an
application.
There are four kinds of relationships available.
Dependency:
Dependency is a relationship between two things in which change in one element also affects
the other one.
Association:
Association is basically a set of links that connects elements of an UML model. It also
describes how many objects are taking part in that relationship.
Generalization:
Generalization can be defined as a relationship which connects a specialized element with a
generalized element. It basically describes inheritance relationship in the world of objects.
Realization:
Realization can be defined as a relationship in which two elements are connected. One
element describes some responsibility which is not implemented and the other one
implements them. This relationship exists in case of interfaces.
(3) UML Diagrams:

UML diagrams are the ultimate output of the entire discussion. All the elements,
relationships are used to make a complete UML diagram and the diagram represents a
system.
The visual effect of the UML diagram is the most important part of the entire process. All the
other elements are used to make it a complete one.
There are two broad caetgories of diagrams and then are again divided into sub-categories:
Structural Diagrams
Behavioral Diagrams
Structural Diagrams:
The structural diagrams represent the static aspect of the system. These static aspects
represent those parts of a diagram which forms the main structure and therefore stable.
These static parts are represents by classes, interfaces, objects, components and nodes. The
four structural diagrams are:
Class diagram
Object diagram
Component diagram
Deployment diagram
Class Diagram:
Class diagrams are the most common diagrams used in UML. Class diagram consists of
classes, interfaces, associations and collaboration.
Class diagrams basically represent the object oriented view of a system which is static in
nature.Active class is used in a class diagram to represent the concurrency of the
system.Class diagram represents the object orientation of a system. So it is generally used for
5
development purpose. This is the most widely used diagram at the time of system
construction.
Object Diagram:
Object diagrams can be described as an instance of class diagram. So these diagrams are
more close to real life scenarios where we implement a system.Object diagrams are a set of
objects and their relationships just like class diagrams and also represent the static view of the
system.
The usage of object diagrams is similar to class diagrams but they are used to build prototype
of a system from practical perspective.
Component Diagram:
Component diagrams represent a set of components and their relationships. These
components consist of classes, interfaces or collaborations. So Component diagrams
represent the implementation view of a system. During design phase software artifacts
(classes, interfaces etc) of a system are arranged in different groups depending upon their
relationship. Now these groups are known as components.
Finally, component diagrams are used to visualize the implementation.
Deployment Diagram:
Deployment diagrams are a set of nodes and their relationships. These nodes are physical
entities where the components are deployed.
Deployment diagrams are used for visualizing deployment view of a system. This is generally
used by the deployment team.
Behavioral Diagrams:
Any system can have two aspects, static and dynamic. So a model is considered as
complete when both the aspects are covered fully.Behavioral diagrams basically capture the
dynamic aspect of a system. Dynamic aspect can be further described as the changing/moving
parts of a system.UML has the following five types of behavioral diagrams:
Use case diagram
Sequence diagram
Collaboration diagram
Statechart diagram
Activity diagram
Use case Diagram:

Use case diagrams are a set of use cases, actors and their relationships. They represent the use
case view of a system.A use case represents a particular functionality of a system.
So use case diagram is used to describe the relationships among the functionalities and their
internal/external controllers. These controllers are known as actors.
Sequence Diagram:
A sequence diagram is an interaction diagram. From the name it is clear that the diagram
deals with some sequences, which are the sequence of messages flowing from one object to
another.Interaction among the components of a system is very important from
implementation and execution perspective.
So Sequence diagram is used to visualize the sequence of calls in a system to perform a
specific functionality.
Collaboration Diagram:
Collaboration diagram is another form of interaction diagram. It represents the structural
organization of a system and the messages sent/received. Structural organization consists of
objects and links.
The purpose of collaboration diagram is similar to sequence diagram. But the specific
purpose of collaboration diagram is to visualize the organization of objects and their
interaction.
Statechart Diagram:
Any real time system is expected to be reacted by some kind of internal/external events.
These events are responsible for state change of the system.Statechart diagram is used to
represent the event driven state change of a system. It basically describes the state change of
a class, interface etc.
State chart diagram is used to visualize the reaction of a system by internal/external factors.
Activity Diagram:
Activity diagram describes the flow of control in a system. So it consists of activities and
links. The flow can be sequential, concurrent or branched.Activities are nothing but the
functions of a system. Numbers of activity diagrams are prepared to capture the entire flow in
a system.
Activity diagrams are used to visualize the flow of controls in a system. This is prepared to
have an idea of how the system will work when executed.
EXPERIMENT NO -2
AIM: - DRAW A USE CASE DIAGRAM OF ATM MACHINE
SYSTEM.
The Use Case Diagram of Banking System include three actors which are as follows :1. User
2. ATM Machine
3. Bank
User: - There are various types of users like corporate user etc. User is the one who
wants to use ATM machine for withdrawing his cash from his account. He should have his
ATM card of any bank. Before using ATM machine he should know the procedure of ATM
machine and his bank account deposits.
ATM Machine: - It is an Automated Teller Machine which is used to withdrawal cash

directly without going to bank.
Bank: - It is an organization which provides various facilities to the user related to

money , investments, accounts etc. It act as the back end of the ATM machine.
PROCESSES: Insert Card: - In this the customer insert his ATM card i.e. put inside his card into ATM
machine for some seconds and then take outside.
Verify Card: - This will check the card. Basically this will check that whether the ATM
card is valid or not.
8
Enter Pin: - After the card validation the ATM machine displays a question for entering
the ATM card pin which is the confidential for the user, then a request is sent to the bank
through ATM machine.
Verify Pin: - In this the entered pin is verified or checked by sending acknowledgement
to the ATM machine by the bank.
Withdraw Money: - Withdrawn money process includes two further processes

Saving Account and Current Saving.
Enter Amount: - Now all the validations are done and user can enter the amount which
he wants to debit from his Bank account.
Check Balance: - After entering specific amount the ATM machine sends request to
the bank to check the current balance of the users account or entered amount.
Receive Entered Amount: - After checking the balance the ATM machine receives
the amount entered by the user from the bank.
Amount Withdrawn: - The amount is withdrawn from the ATM machine by

the user.
Receive Mini-Statement: - Slip received from ATM machine by the user.
Insert Card
Verify Card
Enter Pin
Pin Verification
Entered Amount
Enter Amount
ATM
User
Check Balance
Amount Withdrawn
Withdraw Money
Bank
Card Verified
Recieve Mini-Statement
<<include>>
Pin Verified
Transaction
<<include>>
Recieve Entered Amount

Saving Account
Current Account
Balance Enquiry
Balance Checked
Use Case Diagram of ATM Machine System
EXPERIMENT NO -3
AIM: - DRAW A USE CASE DIAGRAM OF ONLINE SHOPPING CART
SYSTEM.
The Use Case Diagram of Shopping Cart System includes three actors which are as follows:1. Customer
2. Shopping Cart
3. Admin
Customer: - Any Customer can do online shopping through a website.

10
Admin: - He can manage the all products, bills and customers info.
Shopping Cart: -In this the customer can order any product.
PROCESSES: Register: - For buying any product each customer should first register himself to the
Shopping Cart.
Add User Info: -After registration to the shopping cart the users info is added to the
admin panel.
Sign In: - After registration customer sign in to shopping cart for buy any product or to
see any product.
Authentication: - Admin verify the customers detail registered to the shopping cart.
View Products: - After authentication customer can see all the products.
Buy Product: - Customer buys products from the shopping cart.
Manage Products: - Admin manage all products that is added to the shopping cart.
This include further two more processes In Stock and Out Of Stock products.
Payment: - After buy any product, the payment is made to the shopping cart by the
customer. Payment process extend to the By credit card or By Cash on delivery process
that is payment can be done either by credit card or by cash.
Payment Received: - Shopping Cart sends the payment received

acknowledgement to the customer.
Deliver Product: - Product is delivered to the customer by the shopping cart after the
payment received.
11
Manage Products
Register
<<include>>
Sign In
In Stock <<include>>
Out of Stock
View Products
Buy Product
Add User Info
Authentication
Registered
Customer
Admin
Deliver Product
Payment
<<extend>>Payment Recieved
<<extend>>
Shopping Cart
By Credit Card
By Cash on Delivery
Use Case Diagram of Online Shopping Cart
EXPERIMENT NO-4
AIM: - DRAW A CLASS DIAGRAM OF ATM SYSYTEM.
Classes used in this are:
User: Here are various types of users like corporate user etc. User is the one who wants
to use ATM machine for withdrawing his cash from his account. He should have his ATM
12
card of any bank. Before using ATM machine he should know the procedure of using
ATM machine and his bank account deposits.
ATM Machine: It is an automated teller machine which is used to withdrawl each

directly without going to bank.
Bank: It is an organization which provides various facilities to the user related to

money, investments, accounts etc. It act as the back end for the ATM machine.
Employee: He can do all the work of the bank.

Manager & Cashier: Includes in the employee class.
Attributes of Class User:
Name
Address
Phone no
Account no
Operations done by the User:

Insert card
Withdraw money
Check balance
Attributes of Class Bank:

Name
Address
Phone no
Operations done by the Bank:

Verify account
Verify user
Check balance
Attributes of Class ATM:

13
Address
Phone no
Operations done by the ATM:

Withdraw money
Check balance
Attributes of Class Employee:

Name
Address
Phone no
Operations done by the Employee:

Work
There is generalization between employee, manager and cashier.
There is dependency between bank, manager, cashier and employee.
14
entered amount
enter amount
user
Atm
+name
+adrees
+phone_no
+account no
enter card
+insert card()
+withdraw money()
+check balance()
enter pin
pin verification
+address
+phone_no
+wiithdraw money()
+check balance()
bank
+name
+address
+phone number
card verify
balance checked
recieve enter amount
amount withdrawn
balance enquiry
employee
+name
+adrees
+phone number
+work()
manager
cashier
+name
+phone_no
+address
+name
+address
+phone_no
+manage work()
+work()
Class Diagram of ATM Machine
15
+verify account()
+verify user()
+check balance()
EXPERIMENT NO-5
AIM: - DRAW A CLASS DIAGRAM OF ONLINE SHOPPING CART
SYSYTEM.
Classes used in this are:
Customer: - Customer is who visit the website and view the products and buy any
product which he wants.
Website: -That contain number of products for shopping to the customer.

Order: - Include all the orders of the products done by the customer in the shopping
cart.
Admin: - Admin manage all the products in website that is delete or add products to
the website.
Shipment: - This includes the delivery of product to the customer and confirmation
of the payment of the product .
Payment: - This includes the mode of the payment done by the customer either by
credit card or by debit card.
Attributes of Class Customer:

Cust_name
Cust_address
Cust_phoneno
Operations done by the Customers:

Browse_website
Give_order
Make_payment
Receive_product
Operations of Class Admin:

Manage_products
16
Add_products
Delete_products
Attributes of Class Website:

Buy_products
Visit
Operations of Class Website:

Update_products
Receive_orders
Payment
Shipment
Attributes of Class Payment:

Account_no
Bank_name
Payment
Operations of Class Payment:

By_credit_card
By_debit_card
By_cash
Give_payment
Attributes of Class Shipment:

Cust_address
Order_no
Cust_phoneno
17
Operations of Class Shipment:

Confirm_payment
Confirm_order
Attributes of Class Order:

Order_no
Order_details
Order_date
Operations of Class Order:

Place_order
Check_order_details
Add_to_shipping_cart
There is a generalization between payment, debit card, credit card and cash on delivery
classes.
There is a dependency between shipment, debit card, credit card and cash on delivery
classes.
18
Admin
+manage_products()
+add_products()
+delete_products()
Customer
+Cust_name
+Cust_address
+Cust_phoneno
Website
+buy_products
+visit
+update_products()
+recieve_orders()
+payment()
+shipment()
+browse_website()
+give_order()
+make_payment()
+recieve_product()
+order_no
+order_details
+order_date
+place_order()
+check_order_detail()
+add_to_shipping_cart()
+account_no
+bank_name
+payment
+by_credit_card()
+by_debit_card()
+by_cash()
+give_payment()
Shipment
Order
Payment
+cust_address
+order_no
+cust_phoneno
+confirm_payment()
+confirm_order()
Cash On Delivery
Credit Card
+credit_card_no
+bank_name
+account_no
+make_payment()
Debit Card
+debit_card_no
+bank_name
+account_no
+make_payment()
Class Diagram of Online Shopping Cart
19
+order_no
+shipment_no
+delivered()
+not_delivered()
EXPERIMENT NO-6
AIM: - DRAW A SEQUENCE DIAGRAM OF ATM MACHINE.
The sequence diagram of ATM machine include three objects which are as follows:
1. User
2. ATM
3. Bank
Stimulus used in this are:

1. Enter Card
2. Verify Card
3, 4. Card Verified
5. Enter Pin
6. Pin Verification
7, 8. Pin Verified
9. Withdraw Money
10. Enter Amount
11. Amount Entered
12. Gave Amount
13. Receive Amount
14. Balance Enquiry
15. Check Balance
16. Balanced Checked
17. Receive Mini-Statement
20
ATM
User
Bank
1 : Enter Card()
2 : Verify Card()
3 : Card Verified()
4 : CArd Verified()
5 : Enter Pin()
6 : Pin Verification()
7 : Pin Verified()
8 : Pin Verified()
9 : Withdraw Money()
10 : Enter Amount()
11 : Amount Entered()
12 : Gave Amount()
13 : Recieve Amount()
14 : Balance Enquiry()
15 : Check Balance()
16 : Balance Checked()
17 : Recieve Mini Statement()
Sequence Diagram of ATM Machine
EXPERIMENT NO -7
21
AIM: -DRAW A SEQUENCE DIAGRAM OF ONLINE SHOPPING CART

SYSTEM.
The sequence diagram of ATM machine include three objects which are as follows:
1. Customer
2. Shopping cart
3. Admin
Stimulus used in this are:

1. Register
2. Add Customer Info
3, 4. Registered
5. Sign In
6. Authentication
7. Authentication Done
8. View Products
9. Manage Products
10. Buy Product
11. Payment
12. By Credit Card
13. By cash on Delivery
14. Check Payment
15, 16. Payment Received
17. Deliver Product
22
Shopping Cart
Customer
1 : Register()
Admin
2 : Add Customer Info()
3 : Registered()
4 : Registered()
5 : Sign In()
6 : Authentication()
7 : Authentication Done()
8 : Manage Products()
9 : View Products()
10 : Buy Product()
11 : Payment()
12 : By Credit Card()
13 : By Cash on Delivery()
14 : Check Payment()
15 : Payment Recieved()
17 : Deliver Product()
Sequence Diagram of Online Shopping Cart
23
EXPERIMENT NO-8
AIM: -DRAW A COLLABORATION DIAGRAM OF ATM MACHINE
SYSTEM
The collaboration diagram of ATM machine include three objects which are as follows:
1. User
2. ATM
3. Bank
There is Link build up between User and ATM, ATM and Bank.
Forward Stimulus Used in this are:
Insert Card
Verify Card
Enter Pin
Verify Pin
Withdraw Money
Enter Amount
Check Entered Amount
Balance Enquiry
Check Balance
Reverse Stimulus Used in this are:
Card Verified
Pin Verified
Gave Money
Receive Money
Generate Slip
Receive Mini Statement
24
2 : Verify Card()
1 : Insert Card()
User
ATM
5 : Enter pin()
9 : Withdraw Money()
6 : Verify Pin()
11 : Check Entered Amount()
10 : Enter Amount()
14 : Balance Enquiry()
15 : Check Balance()
4 : Card Verified()
3 : Card Verified()
8 : Pin Verified()
7 : Pin Verified()
13 : Recieve Money()
12 : Gave Money()
17 : Recieve Mini Statement()
16 : Generate Slip()
Collaboration diagram of ATM Machine
25
Bank
EXPERIMENT NO-9
AIM: - DRAW A COLLABORATION DIAGRAM OF ONLINE
SHOPPING CART SYSTEM
The collaboration diagram of Online Shopping Cart System includes three objects which are
as follows:
1. Customer
2. Shopping Cart
3. Admin
There is Link build up between Customer and Shopping Cart, Shopping Cart and Admin.
Forward Stimulus Used in this are:
Register
Add customer Info
Sign In
Authentication
Manage products
View Product
Buy product
Payment
By Credit Card
By Cash on Delivery
Check Payment
Reverse Stimulus Used in this are:
Registered
Authentication Done
Payment received
Deliver Product
26
1 : Register()
Customer
5 : Sign In()
Shopping Cart
9 : View Products()
Admin
2 : Add Customer info()
6 : Authentication()
10 : Buy product()
8 : Manage Products()
11 : Payment()
12 : By Credit Card()
14 : Check Payment()
13 : By Cash on Delivery()
4 : Registered()
3 : Registered()
7 : Authentication Done()
17 : Deliver Product()
Collaboration Diagram of Online Shopping Cart System
27
EXPERIMENT NO-10
AIM: - DRAW AN ACTIVITY DIAGRAM OF ONLINE SHOPPING
CART SYSTEM
The activity diagram of Online Shopping Cart System includes three entities which are as
follows:
1. Customer
2. Shopping Cart
3. Admin
Customer entity includes the initial state which is Visit site activity.
Final state is collect cash activity.
Activities included in this are:
Initial state activity Visit Site & Register activity is done by Customer entity.
Registration activity is done by Shopping cart entity.
Registration successful activity done by Admin entity.
Login
Check User
Verify Account
Verified
View Products
Buy Products
Then If the product is in stock then do the payment otherwise the product is out of stock.
By credit card does online payment otherwise choose By cash to do payment on delivery.
Deliver Product
Collect Cash is the final activity done by shopping cart.
28
Customer
Shopping Cart
Visit Site
Registration
Admin
Registration Sucessfull
Register
Login
Check User
View Products
Manage products
Verified
Buy Products
If out of stock
Payment
If in Stock
Product out of stock
By Credit Card
Online Payment
By Cash
Cash on Delivery
Verify account
Collect Cash
Deliver Product
Activity Diagram of Online Shopping Cart System
29
EXPERIMENT NO-11
AIM: -DRAW AN ACTIVITY DIAGRAM OF ATM MACHINE SYSTEM
The activity diagram of ATM machine include three entities which are as follows:
1. User
2. ATM
3. Bank
Insert Card
Validate Atm Card, If the ATM Card is valid then enter pin activity will perform otherwise
Return ATM Card.
Authentication
Enter Pin
Validate Pin, If the Pin is valid then enter amount activity will perform otherwise Return
Card.
Pin Authentication
Enter Amount
Check Balance, If the amount is less than balance then this perform two parallel activity take
money from slot and update account.
Take Money from Slot
Update Account
Show New Balance
Eject Card
30
Activity Diagram of ATM Machine System
31
EXPERIMENT NO-12
AIM: -DRAW AN STATE CHART DIAGRAM OF ATM MACHINE
SYSTEM
The state chart diagram of ATM machine include five entities which are as follows:
1. Reading Card
2. Reading Pin
3. Choosing Pin
4. Performing Transaction
5. Ejecting Card
Reading Card
Return ATM Card.
Reading Pin
Card.
Performing Transaction
Update Account
Ejecting Card
32
Figure: State Chart Diagram for ATM System

33
EXPERIMENT NO-13
AIM: -DRAW AN COMPONENT DIAGRAM OF ATM MACHINE
SYSTEM
A component diagram in the Unified Modeling Language, depicts how components are wired
together to form larger components and or software systems. Components diagrams can be
used to illustrate the structure of arbitrarily complex systems.
The component diagram of ATM machine include three entities which are as follows:
1. Bank
2. User Interface
3. Atm User Interface
Insert Card
Return ATM Card.
Authentication
Enter Pin
Card.
Pin Authentication
Enter Amount
Update Account
Show New Balance
Eject Card
34
Bank.java
Atm User
Interface.java
communicates with
Atm
Control.java
Figure: Component Diagram for ATM System
35
EXPERIMENT NO-14
AIM: -DRAW AN DEPLOYMENT DIAGRAM OF ATM MACHINE
SYSTEM
A deployment diagram in the Unified Modeling Language serves to model the physical
deployment of artifacts on deployment targets. Deployment diagrams show the allocation of
Artifacts to Nodes according to the Deployments defined between them. Deployment of an
artifact to a node is indicated by placing the artifact inside the node.
The deployment diagram of ATM machine include three entities which are as follows:
1. Atm Client
2. Atm Server
3. Data BaseServer
Insert Card
Return ATM Card.
Authentication
Enter Pin
Card.
Pin Authentication
Enter Amount
Update Account
Show New Balance
Eject Card
36
Atm Client
<<Tcp/IP>>
Atm Server
Data
Baseserver
Figure: Deployment Diagram for ATM
37

Final Uml

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Final Uml

Uploaded by

Copyright:

Available Formats

Advance Software Engineering File

UML stands for Unified Modeling Language.

UML is a pictorial language used to make software blue prints.

So UML can be described as a general purpose visual modeling language to visualize,

A conceptual model of UML:

UML building blocks

Rules to connect the building blocks

Common mechanisms of UML

The building blocks of UML can be defined as:

Advance Software Engineering File

Advance Software Engineering File

Advance Software Engineering File

Advance Software Engineering File

(3) UML Diagrams:

Advance Software Engineering File

Use case diagram

Advance Software Engineering File

Use case Diagram:

Advance Software Engineering File

ATM Machine: - It is an Automated Teller Machine which is used to withdrawal cash

Bank: - It is an organization which provides various facilities to the user related to

Advance Software Engineering File

Withdraw Money: - Withdrawn money process includes two further processes

Amount Withdrawn: - The amount is withdrawn from the ATM machine by

Advance Software Engineering File

Recieve Entered Amount

Use Case Diagram of ATM Machine System

Customer: - Any Customer can do online shopping through a website.

Advance Software Engineering File

Payment Received: - Shopping Cart sends the payment received

Advance Software Engineering File

Add User Info

Use Case Diagram of Online Shopping Cart

Advance Software Engineering File

ATM Machine: It is an automated teller machine which is used to withdrawl each

Bank: It is an organization which provides various facilities to the user related to

Employee: He can do all the work of the bank.

Operations done by the User:

Attributes of Class Bank:

Operations done by the Bank:

Attributes of Class ATM:

Advance Software Engineering File

Operations done by the ATM:

Attributes of Class Employee:

Operations done by the Employee:

Advance Software Engineering File

Class Diagram of ATM Machine

Advance Software Engineering File

Website: -That contain number of products for shopping to the customer.

Attributes of Class Customer:

Operations done by the Customers:

Operations of Class Admin:

Advance Software Engineering File

Attributes of Class Website:

Operations of Class Website:

Attributes of Class Payment:

Operations of Class Payment:

Attributes of Class Shipment:

Advance Software Engineering File

Operations of Class Shipment:

Attributes of Class Order:

Operations of Class Order:

Advance Software Engineering File