Uml Practical

8/2/2019 Uml Practical

1/58

3

PROJECT REPORT ON

ONLINE BANKING SYSTEM

SUMBITTED TOProf. Pratibha Deshmukh

SUBMITTED BY Dipak Sonnar (Roll No.- 47)


2/58

3

We would like to take this opportunity to convey my heart-full thanks

& deep appreciation for the help rendered to us, by all of you resulting in the

successful completion of our UML project. We wish to give grateful

acknowledgment to all ever-helpful people whose experience and guidance

allowed us to make this invaluable piece of mere hard work.

We are highly indebted to our Project Guide Prof. Pratibha

Deshmukh for continuous support and guidance without which this project

couldnt have been in reality. We would like to thank Prof. Pratibha

Deshmukh for their backing support in lab thoroughly checking of our

project and reports and also provided suggestion for improvement.

We express our deep regards to all of those who stretch their helping

hand in the execution of our UML project. And thankful to those whom we

forgot to thank.

We would like to thank my colleagues who were readly in a positive commentall the time.


3/58

3

TOPIC PAGE No.

1. INTRODUCTION. 042. CURRENT SYSTEM. 053. LIMITATION OF CURRENT SYSTEM. 064. PROPOSED SYSTEM. 075. DOMAIN ANALYSIS. 086. REQUIREMENT SPECIFICATION. 097. BUSINESS PROCESS. 108. USE CASE. 12

9. CLASS DIAGRAM. 1510.ACTIVITY DIAGRAM. 1911.STATECHART DIAGRAM. 2412.SEQUENCE DIAGRAM. 2713.COLLABORATION DIAGRAM. 3314.LOGICAL ARCHETECTURE. 3815.HARDWARE ARCHETECTURE. 3916.IMPLEMENTATION ARCHETECTURE. 41


4/58

3

Online Banking Syatem

Online Banking system is a very use full way of transaction in

todays busy life .

This starts from account creation and end with successful

transaction .

Some organization having e-business there online banking

required for making payment. such that this system maintain allprocess happen in online transaction like, account creation ,logion

details ,authentication .

Transfer of payment from one account to another account.

maintaining all

E-transaction details ,ATM system also comes under the online

banking ,that required card issue ,pin creation ,authentication

Here in this system we are planning to implement an softwaresolution that will handle all those activity that takes place in online

transaction.

This Software system is an Object Oriented Designed system. so it

can match any latest Object oriented supported technology tool to

build the system.


5/58

3

1. Current system is having standalone architecture .

2. Current system will transfer money by only bank.

3. Current system is maintain data about transaction .

4. We can take monthly report from system.

5. Current system provides pass book for transaction.


6/58

3

There are few limitation in the current system

For making payment every time we have to visit bank

Stand alone system is take time for transferring money and

having lots of processes .

System cannot produce payment reports as needed on time,

they will first have to visit bank and then only they can

prepare the reports.

Payment reports cannot be generated immediately.

As the world expanding business overseas current system isnot suitable.


7/58

3

The system should create new user account for e-

banking.

System will create user name and password.

System having capability to transfer amount from any

bank .

System is online thats means u can transfer money

from anywhere.

System is easy to make online payment. with thepayment gate way. System should update database

accordingly.

The proposed system is an Object oriented Software

system.

System can support the latest technology.

The system will reduce the work to visit bank.

Fast in Report generation.

Generally used to make payment ,transfer money,

checking balance

User friendly in nature.

Huge customer database supports system.


8/58

3

1. What is Class Diagram

2. Iterative and Incremental Design

3. Develop Class Diagram: Using Different Approach

4. Stages in Building a Class Diagram

5. Object Identification

6. Before Daigramming Classes: Object Identification

7. Object Identification Technuiques

8. Object Categories

9. Textual Analysis

Step 1: Requirement Statement

Step 2: Identifying Nouns

Step 3: Rejection Criteria for Candidate Objects

Step 4: Preparing Revised Object List Analysis Decisions

10. Practical Training: Conduct Textual Analysis .

11. Idenitify Object Relationships

12. Assoications and Multiplicity .

13 Inheritence.


9/58

3

14. Step-by-Steo Demo - Drawing Class Diagram.

Software Requirement

Oracle 9i for DataBase.

Windows Operating System(XP/Server).

Java

Internet explorer or any browser.

Hardware Reuirement.

Printer.

Pentium-4 OR Above PC.

Key Board.

Mouse/Pointing Device.


10/58

3

A business process:

1. Has a Goal2. Has specific inputs

3. Has specific outputs

4. Uses resources

5. Has a number of activities that are performed in some order

6. May affect more than one organizational unit. Horizontal organizational

impact

7. Creates value of some kind for the customer. The customer may be internal or

external.


11/58

3


12/58

3


13/58

3

Use Case Diagram: -

A use case diagram depicts participation relationships

between actors and use cases. The diagram has an association

between an actor and each use case in which the actor

participates. This diagram contains three basic components:

System Actor Use case

Notations used in Use case diagram are as follows:

Tool Name Notation Description

System

System System boundary where all usecases will reside.

ActorActor

Actor which uses the system.


14/58

3

Use Case RegistrationIt is generally function or

process in the system.

Associatio

n

It shows direct association

between actor and use cases.

Dependen

cy

It shows dependency between

two use cases.

Includes It means one use case includes

another use case.

Extends

It means one use case invokes

another use case optionally or

sometimes.

Uses It means one use case invokes

another use case always.

USE CASE DIAGRAM FOR EMPLOYEE PAYROLL


15/58

3


16/58

3

Class Diagram:


17/58

3

A Class diagram is a visual representation of an application

showing its classes and the relationships between those classes.

When you open a Class diagram, the IDE displays a specific

selection of UML element icons in the Modeling Palette. Using the

Class diagram model, you describe the static structure of theelements in your application. The IDE lets you graphically create

diagrams that contain classes. The classes are arranged in

hierarchies that share common structure and behavior and are

associated with other classes.

Notations used in Class Diagram are as follows:


ClassClassName

+Attribute1

+Attribute2

+Operation1()

+Operation2()

A class defines a collection of

similar instances. It exists at

compilation time and serves

as a type. It defines the

interface and implementation

of its instances.

Object

Raj : S tudent

An object is a particular

instance of a class. Each

object represents a particular

instance of something in the

problem or solution domain

and is created as needed.

Association An association is a

relationship between classesin a class diagram.


18/58

3

Association

Class

C l a s s 1 C l a s s 2

A s s o c ia t io n C la s s

An association can be

modeled as a class. Each

instance of the class

represents a link between

objects. An association classis like any other class except

that its instances represent

links. It can have

independent behaviors, and

it can be associated with

other classes.

AggregationClass1

Class2

The aggregation relationshipis a special form of

association used to model

the whole-part or part-of

relationship.

Specializatio

n &

Generalization

V e h i c l e

C a r T ruc k

Specialization is a

relationship between classes.

Specialization is the is-a-kind-of relationship, in which

the specialization is the

subclass, or subtype and the

generalization is the super

class or supertype.

DependencyClass1

Class2

A dependency is a catch all

relationship. It can appear inany diagram and is used to

model different kinds of

relationships.


19/58

3

CLASS DIAGRAM FOR EMPLOYEE PAYROLL


20/58

3


21/58

3

Activity Diagram: -


22/58

3

An activity diagram depicts a workflow view of activities.

You can also draw a system-level activity diagram in which each

use case is modeled as an activity. That activity diagram specifies

the temporal sequencing of the use cases.

Notations used in Activity diagram are as follows:


Initial State The initial state of the

activity.

Action State Issue BookRepresents the activity.

DecisionOne activity conditionally

follows another activity.

Synchronizati

on

Multiple activities either

follow or precedes

synchronization bar.

TransitionShows the flow between

activities.

Signal send

stateInvalid Member

Used to send the signals.

Flow finalShows the final flow of

activity.

Final stateShows the final state i.e.

end of activity.

Activity Diagram of Online Transaction Transactionsystem.


23/58

3


24/58

3

Activity Diagram of Client Desktop Transaction

system.


25/58

3


26/58

3

Activity Diagram of Web Mearchant Transactionsystem.


27/58

3


28/58

3

State Chart Diagram:


29/58

3

A State chart or transition diagram describes the state-

based behaviour of a class of instances across all scenarios. An

object has meaningful state-based behaviour if you can say one of

the following:

The object passes through a set of states.

Some of the objects behaviours are meaningful in some

states but meaningless in others. In other words, whether the

object responds to a particular request depends upon the

state it is in.

The objects methods must be executed in a particular order.

Notations used in State Chart diagram are as follows:

Tool

Name

Notation Description

StateOn Shelf

Describes the particular

state of the object.

Composit

e

State

A composite state is

composed of a collection of

lower-level sub-states that

share semantics. The states

outside the composite state

in some cases may ignore

the internal details of the

composite state and

interact with it as a singlestate.

Parallel

State

It shows two internal state

machines that execute in

parallel. The dashed line is

included to emphasize the

concurrency. The

transitions in a state

Pending

OnShelf

Issued

Discard

ed

On

Shelf


30/58

3

machine can also split and

join, resulting in parallel

states.

STATECHART Diagram for Online Banking


31/58

3


32/58

3


33/58

3

Sequence Diagram: -

An interaction diagram is graphical representation of how

objects interact with one another in a scenario. Objectscommunicate in an interaction diagram by sending messages. A

Sequence diagram is organized temporally with the focus on the

order in which messages are sent between objects.

Notations used in Sequence diagram are as follows:


ObjectMember

Object can be an actor,

class or physical entity.

Synchronou

s message

When one object sends this

message & waits for the

response or completion ofprocess.

Asynchrono

us message


message & does not wait

for response or completion

of process.

Return

message

It is used to give response

for a message call.

Found

message

It is used when the sender

object is not known or not

significant.

Lost

message

It is used when the receiver


significant.


34/58

3

Create

message

When new object is created

in the process.

Destroymessage

When an object isdestroyed in the process.

Conditional

message

[if

book


35/58

3

SEQUENCE DIAGRAM FOR CLIENT DESKTOPTRANSCATION


36/58

3

SEQUENCE DIAGRAM FOR ONLINETRANSCATION


37/58

3


38/58

3

LOGIN AND LOGOUT SYSTEM


39/58

3


40/58

3

Collaboration Diagram:

A collaboration diagram is spatially oriented with an

emphasis on the links between objects.

Notations used in Collaboration diagram are as follows:


ObjectPAYROLL

Object can be an actor, class

or physical entity.

Synchronou

s message


message & waits for the

response or completion of

process.

Asynchrono

us message


message & does not wait for

response or completion of

process.

Return

message

It is used to give response

for a message call.

Found

message

It is used when the sender


significant.

Lost

message

It is used when the receiver


significant.

Newmessage

When new object is createdin the process.

Delete

message

When an object is destroyed

in the process.

Conditional

message

[if

book


41/58

3


42/58

3

CO LLABORATION DIAGRAM FOR ONLINEBANKING


43/58

3


44/58

3

CO LLABORATION DIAGRAM FOR PINVALIDATION SYSTEM


45/58

3


46/58

3

CO LLABORATION DIAGRAM FORWEBMERCHANT SYSTEM


47/58

3


48/58

3


49/58

3

Package Diagram:

A system or application, whether object-oriented or not, can

be organized into logical units such as layers or subsystems. Theseare logical because the grouping criterion is conceptual. A layer

can be modeled in UML as a package, which is a logical grouping

of classes or use cases. As such, it can appear in a class diagram

or a use case diagram.

Notation for Package Diagram:

Package1


50/58

3

(LOGICAL ARCHETECTURE) PackageDiagram


51/58

3


52/58

3


53/58

3

COMPONANT DIAGRAM


54/58

3


55/58

3


56/58

3

Deployment Diagram:

A UML Deployment Diagram defines the hardware

architecture of a system or application. Many applications and

systems are distributed, meaning that they span multiple

hardware boxes. The deployment diagram, the UML notation for

hardware architecture, is explained.

The diagram includes a set of nodes depicted as three-

dimensional cubes. Each node represents a class of hardwareprocessor and is labeled with the type of the node. The

relationships between nodes represent physical connections

between the corresponding processors.

Both the nodes and relationships can include cardinality

constraints. The cardinality constraint of a node appears in the

upper right corner of the node (or anywhere within the node ifenclosed with the curly braces) and specifies how many instances

of this type of processor can be included in a deployment of the

system.

Notation:

Node


57/58

3

Deployment Diagram (HARDWAREARCHETECTURE)


58/58

Uml Practical

Documents

Transcript of Uml Practical