Scribd
Upload
356 views8 pages

Software Testing & Quality Assurance MCA

The document discusses Unified Modeling Language (UML) and provides examples of UML diagrams that can be used to model an Automated Teller Machine (ATM) system, including: 1. A use case diagram to show the functionality of the ATM system. 2. Class, sequence, state, activity, and component diagrams that can model different views of the ATM system such as the static structure, dynamic interactions, states and activities, and physical components. 3. Specific examples of a state chart, activity, and sequence diagram for the ATM to illustrate how each type of diagram can be used to model aspects of the system.

Uploaded by

Aman Rai
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
356 views8 pages

Software Testing & Quality Assurance MCA

The document discusses Unified Modeling Language (UML) and provides examples of UML diagrams that can be used to model an Automated Teller Machine (ATM) system, including: 1. A use case diagram to show the functionality of the ATM system. 2. Class, sequence, state, activity, and component diagrams that can model different views of the ATM system such as the static structure, dynamic interactions, states and activities, and physical components. 3. Specific examples of a state chart, activity, and sequence diagram for the ATM to illustrate how each type of diagram can be used to model aspects of the system.

Uploaded by

Aman Rai
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 8

OBJECTIVE: Use case diagram for ATM.

APPARATUS REQUIRED: Case Tools and Testing.

THEORY: Description about UML

1. Model
 A model is a simplification of reality.
 A model provides the blueprints of a system.
 A model may be structural, emphasizing the organization of the system,
or it may be behavioral, emphasizing the dynamics of the system.
 We build models so that we can better understand the system we are
developing.
 We build models of complex systems because we cannot comprehend
such a system in its entirety.

Through modeling, we achieve four aims.

 Models help us to visualize a system as it is or as we want it to be.


 Models permit us to specify the structure or behavior of a system.
 Models give us a template that guides us in constructing as system.
 Models document the decisions we have made

2. Principles of Modeling

 The choice of what models to create has a profound influence on how


a problem is attacked and how a solution is shaped
 Every model may be expressed at different levels of precision
 The best models are connected to reality
 No single model is sufficient. Every nontrivial system is best
approached through a small set of nearly independent models

3. Unified Modeling Language (UML)

The UML is a language for

 Visualizing
 Specifying
 Constructing
 Documenting

The UML is a Language

 A modeling language is a language whose vocabulary and


rules focus on the conceptual and physical representation of
a system

The UML is a Language for Visualizing


 Some programmers think of an implementation and then
code it. Some programmers think mentally i.e. they even
sketch out a few ideas on a paper. That means some things
are best modeled textually, others are best modeled
graphically. The UML is such a graphical language.

The UML is a Language for Specifying

 Specifying means building models. It specifies of all the


important analysis, design, and implementation decisions
that must be made in developing a software project.

The UML is a Language for constructing

 The UML is not a visual programming language, but its


models can be directly connected to a variety of a
programming language. This means that it is possible to
map from a model in the UML to a programming language
such as Java, C++.

The UML is a Language for Documenting

 A Healthy software organization produces all sorts of


artifacts in addition to raw executable code. These artifacts
include
1. Requirements
2. Architecture
3. Design
4. Source code
5. Project plans
6. Tests
7. Releases
 The UML addresses the documentation of a system’s
architecture and all of its detail

4. Architectural views of UML

The user model view

- Use Case Diagram - The functionality of a system

The structural model view

- Class Diagram - The static structure of a system

- Object Diagram - The static structure of a system at a particular time

The behavioral model view

- Sequence Diagram - Interaction among elements of a system in a time sequence


- Collaboration diagram - Interaction among elements and their relations organized in
time and space

- State Diagram - The status condition and responses of the elements of a system

- Activity Diagram - The activities of the system

The implementation model view

- Component Diagram - The organization of the elements realizing the system

The Environment model view

- Deployment diagram - Configuration of environment elements and the


mapping of elements realizing the system into them

Bank officer

Change pin Transfer fund

Deposit funds
Customer Make payment
Client

Withdraw money View balance

Transfer funds
OBJECTIVE: State chart diagram for ATM.

APPARATUS REQUIRED: Case Tools and Testing.


THEORY: A Statechart diagram shows a state machine, emphazing the flow of control from
state to state .A state machine is a behavior that specifies the sequences of states an object goes
through during its life time in response to events together with responses to those events. We can
use these diagrams to model the dynamic view of a system.
OBJECTIVE: Activity diagram for ATM

APPARATUS REQUIRED: Case Tools and Testing.


THEORY: An activity diagram shows the flow from activity to activity .An activity is an
ongoing non atomic execution within a state machine. Activities ultimately results in some
action, which is made up of executable atomic computations. we can use these diagrams to
model the dynamic aspects of a system.
Component diagrams are used to model physical aspects of a system. Now the question is what
are these physical aspects? Physical aspects are the elements like executables, libraries, files,
documents etc which resides in a node. So component diagrams are used to visualize the
organization and relationships among components in a system. These diagrams are also used to
make executable systems.

Insert
card

Enter
PIN

Connect Not connected

Enter
transition
Any more transaction

No more transaction

Remove
card

Activity Diagram of ATM


OBJECTIVE: Sequence diagram for ATM.

APPARATUS REQUIRED: Case Tools and Testing.


THEORY: A Sequence diagram is an interaction diagram that emphasizes the time ordering of
messages. This diagram is used to show the dynamic view of a system.

A : Atm ac : B : Bank
machine account client
1: Insert card

Insert PIN

3 : Enter PIN

4 : Verification

5 : PIN ok

6 : Request for transaction

7 : Process transaction

8 : Enter amount

9 : Amount entered

10 : Withdrawal

11 : Withdrawal success

12 : Dispense cash

13 : take cash

14 : Terminate

15 : Print slip

16 : Eject card
OBJECTIVE: Introduction of UML, Class Diagram for ATM

APPARATUS REQUIRED: Case Tools and Testing.

ATM Class Diagram

You might also like