Activity For Admin module

An activity diagram illustrates the dynamic nature of a system by modeling the flow of control from activity to activity. An activity represents an operation on some class in the system that results in a change in the state of the system. Typically, activity diagrams are used to model workflow or business processes and internal operation. Because an activity diagram is a special kind of statechart diagram, it uses some of the same modeling conventions.

Admin interface

Admin login

no

yes View all data

Allow new data

View Auditing data details

Activity for Auditor:

Activity for User

Auditor interface

user interface

Auditor login

no

user login

no

yes View all data

yes upload data

Change or unchange data

Encrypt and store data

Store

Secure key

All files alert

View data

SEQUENCE DIAGRAM An interaction is a behavior that comprises of a set of messages exchanged among a set of objects within a context to accomplish a purpose. We use interactions to model the dynamic aspects of the model. When an object passes a message to another object, the receiving object might in turn send a message to another object, which might send a message to yet another object, and so on. This stream of messages forms a sequence. Any sequence must have a beginning; the start of every sequence is rooted in some process or thread. Each process or thread within a system defines a distinct flow

of control, messages are ordered in sequence of time.

Admin Sequence

User Sequence:

Auditor sequence:

CLASS DIAGRAM A class is a description of a set of objects that share the same attributes, operations, relationships and semantics. Graphically it is rendered as a rectangle. An attribute is named property of a class that defines a range of values that instance of that class may hold. An attribute represents some property of the thing you are modeling that is shared by all the objects of that class. Operation is the implementation of the services that can be requested from any object of the class to affect behavior. A Class diagram shows a set of classes, interfaces, collaborations and their relationships

6.4 Collaboration Diagram:

A collaboration diagram is one of the five diagrams that are used to model the dynamic aspects of the system. A collaboration diagram shows a set of objects, links between the objects and messages that are dispatched between those objects.

Admin collaboration diagram

User Collabaration diagram

Auditor collaboration diagram

Component diagram --------------------------component diagrams are used to visualize the organization and relationships among components in a system. These diagrams are also used to make executable systems.

Client Processing

Front Display

Cloud

Help System

Deployment Diagram --------------------------Deployment diagrams are used to describe the static deployment view of a system. Deployment diagrams consist of nodes and their relationships. Deployment diagrams are used for describing the hardware components where software components are deployed. Component diagrams and deployment diagrams are closely related. Component diagrams are used to describe the components and deployment diagrams shows how they are deployed in hardware.

client2 client x

client y

Server N

Server

client1

client z

clientN