Chapter Four 4. System Design

CHAPTER FOUR
4. SYSTEM DESIGN
4.1 Introduction
Mobile banking enable customer to access the information from
his personal mobile and can able to view his account details. This
system also used to transact money to another client through the
keyboard of the mobile itself.
This chapter mainly focus on how the system is going to be built.
Here all the models and designs are used to describe the overall
design of the system that we are going to develop. This helps us to
implement the system easily as a blue print for the development
of the software.
The following topics are included in this chapter :
Cont..
Class modeling
State chart modeling
Collaboration Modeling
Component Modeling
Deployment modeling
Persistence modeling
User Interface design
4.2
CLASS TYPE ARCHITECTURE LAYERED
4.2.1 User interface layer

This layer wraps access to the logic of your system. There are two
categories of interface class user interface (UI) classes that
provide people access to your system and system interface (SI)
classes that provide access to external systems to your system.
The project user interface divide into three based on the access
right of the customer into all logged in users, Bank manager and
system administrator .
1. Logged in User
Run application
login
Transfer Money
View Balance
Mini-statement Request
Con
2. Logged Bank manager
Run application
login
Send notification for Transaction
View users account details
3. Logged Administrator
Run application
login
Update user account
Add customer information
Control bank server
Cont.
4.2.2 Domain/Business layer
This layer implements the concepts relevant to your business
domain such as mobile users, focusing on the data aspects of the
business objects, plus behaviors specific to individual objects.
Enterprise Java Bean (EJB) entity classes are a common approach to
implementing domain classes within Java.
The following are the business/domain class for the system:
User class
Administrator class
Account class
Cont..
4.2.3 Process/control layer
The system going to develop as the following controller :
Run application
Login
Transfer money
View Balance
Mini statement Request
4.2.4 Persistence
Encapsulate the capability to store, retrieve, and delete objects/data
permanently without revealing details of the underlying storage
technology. Often implement between your object schema and your
database schema and there are various available to you.
Cont.
4.2.5 System
System classes provide operating-system-specific functionality for
your applications, isolating your software from the operating system
(OS) by wrapping OS-specific features, increasing the portability of
your application.
The full diagram see below GO
4.3 CLASS MODELING
Class diagram is a static diagram and it is used to model static

view of a system. Class diagram is also considered as the
foundation for component and deployment diagrams.
Class diagrams are not only used to visualize the static view of
the system but they are also used to construct the executable code
for forward and reverse engineering of any system.
So in a brief, class diagrams are used for:
Describing the static view of the system.
Showing the collaboration among the elements of the static view.
Describing the functionalities performed by the system.
Construction of software applications using object oriented
languages
See the Class modeling diagram Go
4.4 STATE CHART
The state chart diagram used to show the sequence of states that an
object goes through the events that cause the transition from one
state to the other and the actions that result from a state change.
The state diagram depicts the behavior of the system over time.
See the state chart diagram Login, Transfer, view
4.5 COLLABORATION DIAGRAM
Collaboration diagrams represent a combination of information

taken from class, sequence, and use case diagrams describing both
the static structure and dynamic behavior of a system.
The UML Collaboration diagram is used to model how objects
involved in a project interact, with each object instantiating a
particular class in the system.
Objects are connected by links, each link representing an instance of
an association between the respective classes involved.
The link shows messages sent between the objects, and the type of
message passed (synchronous, asynchronous, simple, balking, and
timeout).
See the collaboration diagram below Go
4.6
DATA PERSISTENCE
Database design is the process of producing a detailed data model of

a database.
The database management system (DBMS) is the software used to
implement a database design.
Modern database and applications development software is so easy
to use that many people can quickly learn to implement a simple
database and Develop simple applications within a week or so,
without giving design.
It need for Agree on structure of the database before deciding on a
particular implementation
4.7 COMPONENT MODEL
The component diagram depicts how components are wired

together to form larger components and/or software systems.
Our component modeling describes components of our system
such as user ,manager ,administrator and how can they interact
with each other depending their functionality and what is common
function that can share by all the components of our system.
It can also describe the interaction of our system components with
the security control system.
It helps to model the physical aspect of object-oriented system
software.
Go
4.8 DEPLOYMENT DIAGRAM
Deployment diagram shows the configuration of run-time processing

elements and the software components, processes, the hardware of
the system, the middleware that is used to connect the disparate
machines to one and other and objects that live on them.
We use deployment modeling diagram to show our systems static
view of the run time configuration of processing nodes and the
component that run those nodes
The following figure shows our deployment modeling diagram to
our system.
4.9 USER INTERFACE DESIGN
The user interface is the main component that is used as a

communication medium between the user and the system.
Our system has the following UI :
Administrator Login User Interface
View Balance, Transfer and mini statement UI
See the figure below View Balance, Transfer, mini statement
Back
Back
Back
Back
Back
Back
Back

Chapter Four 4. System Design

Uploaded by

Copyright:

Available Formats

Chapter Four 4. System Design

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

Chapter Four 4. System Design

Uploaded by

Copyright:

Available Formats

CHAPTER FOUR

CLASS TYPE ARCHITECTURE LAYERED

4.2.1 User interface layer

4.3 CLASS MODELING

Class diagram is a static diagram and it is used to model static

4.4 STATE CHART

4.5 COLLABORATION DIAGRAM

Collaboration diagrams represent a combination of information

Database design is the process of producing a detailed data model of

4.7 COMPONENT MODEL

The component diagram depicts how components are wired

4.8 DEPLOYMENT DIAGRAM

Deployment diagram shows the configuration of run-time processing

4.9 USER INTERFACE DESIGN

The user interface is the main component that is used as a

You might also like