1.

SYSTEM DESIGN
1.1 ARCHITECTURE DIAGRAM

User

Customer Administrator Supplier

Online Hide Sensitive View Non

Purchase Data Sensitive Data

1.2 DATA FLOW DIAGRAM

A data flow diagram (DFD) is a graphical representation of the "flow" of data through an
information system. It differs from the flowchart as it shows the data flow instead of the
control flow of the program.

A data flow diagram can also be used for the visualization of data processing (structured
design).

With a dataflow diagram, users are able to visualize how the system will operate, what
the system will accomplish, and how the system will be implemented. Dataflow diagrams
can be used to provide the end user with a physical idea of where the data they input
ultimately has an effect upon the structure of the whole system from order to dispatch to
report. How any system is developed can be determined through a dataflow diagram.
DFD Start

Logi
n

Admin Customer
Login Type check

Add Distributor, Create new

Add Product User account
Distributor
View Customer, View products
Distributor,
Product
View Non Add to
Sensitive Cart
Item set
BinaryFormat Buy
Conversion, Products
Extension,
Integration

stopSt
 1.3 UML DIAGRAM
USE CASE DIAGRAM
A use case diagram in the Unified Modeling Language (UML) is a type of behavioural
diagram defined by the and created from a Use-case analysis. Its purpose is to present
a graphical overview of the functionality provided by a system in terms of actors, their
goals (represented as use cases), and any dependencies between those use cases.

The main purpose of a use case diagram' is to show, what system functions are
performed for which actors. Roles of the actors in the system can be depicted.

The use case diagram show the position or context of the use case among other use
cases. As an organizing mechanism, a set of consistent, coherent use cases promotes a
useful picture of system behavior, a common understanding between the
customer/owner/user and the development team.

Admin-HideSensitiveData

Login
Customer-PurchaseOnline

Distributor-ViewNonSensitiveData
CLASS DIAGRAM
A class diagram in the Unified Modeling Language (UML), is a type of static structure
diagram that describes the structure of a system by showing the system's classes, their
attributes, and the relationships between the classes. The UML specify two types of
scope for members: instance and classifier. In the case of instance members, the scope
is a specific instance. For attributes, it means that its value can vary between instances.
For methods, it means that its invocation affects the instance state, in other words,
affects the instance attributes. Otherwise, in the classifier member, the scope is the
class. For attributes, it means that its value is equal for all instances. For methods, it
means that its invocation do not affect the instance state. Classifier members are
commonly recognized as "static" in many programming languages. To indicate that a
member has the classifier scope, its name must be underlined. Otherwise, as default,
the instance scope is considered.

index

username
password
logintype

LoginSubmit

CustomerHome Admin Distributor

Products
product ItemSet
Distributors
view cart Support
Customers

getTransItemset
getProductList addProduct
CustTransaction DistRegistration
createExtension
SEQUENCE DIAGRAM
A sequence diagram in Unified Modelling Language (UML) is a kind of interaction
diagram, that shows how processes operate one with another and in what order. It is a
construct of a Message Sequence Chart.

A sequence diagram shows, as parallel vertical lines ("lifelines"), different processes or

objects that live simultaneously, and, as horizontal arrows, the messages exchanged
between them, in the order in which they occur. This allows the specification of simple
runtime scenarios in a graphical manner.

index Admin customer Distributor

LoginType add product

Add To Cart

Validate Card Details

Hide Sensitive Data

View NonSensitiveData

Add Distributor

Distribute Products
 1.4 ACTIVITY DIAGRAM

Activity diagrams are a loosely defined diagram technique for showing workflows of
stepwise activities and actions, with support for choice, iteration and concurrency.[1] In
the Unified Modeling Language, activity diagrams can be used to describe the business
and operational step-by-step workflows of components in a system. An activity diagram
shows the overall flow of control.

Login

Admin Customer

Distributor
View
Add Distributor,
Non Sensitive Create new
Add Product
Item set User account

View products
View Customer,
Distributor,
Product
Add to Cart

Buy Products
BinaryFormat
Conversion,
Extension,
Integration

Logout
 1.5 COLLABORATION DIAGRAM

A collaboration diagram, also called a communication diagram or interaction diagram, is

an illustration of the relationships and interactions among software objects in the Unified
Modeling Language (UML). The concept is more than a decade old although it has been
refined as modeling paradigms have evolved.

A collaboration diagram resembles a flowchart that portrays the roles, functionality and
behavior of individual objects as well as the overall operation of the system in real time.
Objects are shown as rectangles with naming labels inside. These labels are preceded
by colons and may be underlined. The relationships between the objects are shown as
lines connecting the rectangles. The messages between objects are shown as arrows
connecting the relevant rectangles along with labels that define the message
sequencing.

1.LoginTypeCheck

LoginSubmit

admin
2.Add Product
Customer
3.Add Distributor
Distributor
4.Add To Cart
Product 5.Validate Card Details
Distributor Table
6.view non sensitive itemset
Cart
Bank

Transaction details