High level design HLD Essay

2. High degree design

High degree design ( HLD ) gives the complete system design of functional architecture and database design. For the developers it is really much of import to understand how the flow of the system is. In this stage the system design squad examiners squad and the clients plays an of import function. For this entry standards are required the papers that is SRS and the so issue standards will be high degree design, undertakings criterions, functional design paperss, and the database design paperss.

5.2.2.1 Problem specification

• Data has to be processed in a effectual and efficient manner.
• Time ingestion should be less.
• Easy to implement.

5.2.2.2 Data Definition/ Dictionary

Data lexicon is a depository that contains all the description of all informations produced by the application. It is an organisation listing of all informations elements that are pertinent to the system.

Tables

Tables For Colud Sever 1

Field Name	DATA TYPE	Size	Key
FName	Varchar	30	primary
Sk	Int	10
Owner	Varchar	30
CloudName	Varchar	15

Table 5.1: Owner File [ Table Design ]

Field Name	DATA TYPE	Size	Key
Vm	Int	10	primary
Owner	Varchar	20
Memory	Int	10
Thrushold	Int	10
Status	Varchar	30
AttackerIP	Int	10
Attempts	Int	10

Table 5.2: Virtual Memory1 [ Table Design ]

Field Name	DATA TYPE	Size	Key
Filename	Varchar	30	primary
Owner	Varchar	20
Sk	Int	10

Table 5.3: CloudFile1 Table [ Table Design ]

Field Name	DATA TYPE	Size	Key
Owner	Varchar	30	primary
Filename	Varchar	20
Sk	Int	10

Table 5.4: Receive File1 Table [ Table Design ]

Field Name	DATA TYPE	Size	Key
RemoteUser	Varchar	30	primary
Owner	Varchar	20

Table 5.5: Remote File Table [ Table Design ]

Field Name	DATA TYPE	Size	Key
Attacker	Varchar	30	primary
AttackerName	Varchar	20
IP-Address	Int	10

Table 5.6: Attacker1 Table [ Table Design ]

Tables For Cloud Sever 2

Field Name	DATA TYPE	Size	Key
Vm	Int	10	primary
Owner	Varchar	20
Memory	Int	10
Thrushold	Int	10
Status	Varchar	30
AttackerIP	Int	10
Attempts	Int	10

Table 5.7: Virtual Memory2 Table [ Table Design ]

Field Name	DATA TYPE	Size	Key
Filename	Varchar	30	primary
Owner	Varchar	20
Sk	Int	10

Table 5.8: Cloud File2 Table [ Table Design ]

Field Name	DATA TYPE	Size	Key
Owner	Varchar	30	primary
Filename	Varchar	20
Sk	Int	10

Table 5.9: Receive File2 Table [ Table Design ]

Remote File2 Table

Field Name	DATA TYPE	Size	Key
RemoteUser	Varchar	30	primary
Owner	Varchar	20

Table 5.10: Distant File2 Table [ Table Design ]

Field Name	DATA TYPE	Size	Key
Attacker	Varchar	30	primary
AttackerName	Varchar	20
IP-Address	Int	10

Table 5.11: Attacker2 Table [ Table Design ]

5.2.3 Premises and dependences

• The user should cognize the hallmark inside informations to forestall the unauthorised entree of the system.
• The user must be cognizant of the authorities regulations and ordinances that are to be implemented on the footings.
• The user must be cognizant of the flow at which the procedure of system takes topographic point.

5.2.4 Low degree design

Low degree design ( LLD ) is like detailing the High degree design. It defines the existent logic for each and the each every constituent of the system. Class diagrams with the methods and relation between the categories comes under the low degree design.

The chief stage of the object oriented attack is as follows: –

• Object mold
• Dynamic mold

Object mold

• Object mold technique describes a method for the analysis, design, and execution of a system utilizing an object-oriented technique.
• Object mold technique consists of four stages, which can be performed iteratively are Analysis, system design, object design, execution

Dynamic mold

The dynamic theoretical account describes the functionalities involved in the undertaking and the individual executing those functionalities. Following are the different sort of dynamic diagrams viz. ; Use instance, Sequence, Activity diagrams.

5.2.5 Use instance diagram

Ause instance diagramis the simple and it is a represented as the user’s interaction with the system and describes the specifications of ause instance. A usage instance diagram can stand for the different sorts of users of a system and the different ways that they will interact with the system. Such diagrams is typically used in concurrence with the textualuse caseas good as it will frequently be accompanied by other sorts of diagrams. It is the high degree piece of functionality that the system provides. An histrion is one who interacts with the system.

This Use Case diagrams are included into two patterning linguistic communications defined by the Object Management Group ( OMG ) . Both the UML and SysML criterions specify a graphical notation for patterning usage instances with diagrams. One complain is that they will non specify the format for picturing these usage instances. Generally both the graphical notation and the descriptions are really of import as they document the usage instance and it is demoing the ground for which an histrion uses a system.

The usage instance diagram shows the topographic point of usage instance with the other usage instances. As forming the mechanism a set of consistent and consistent usage instances promotes of import figure of system behaviour and have a common apprehension between the client or proprietor or user and the development squad.

USE CASE DIAGRAM

Figure 5.1: Use instance diagram

5.2.6 Sequence diagrams

Asequence diagramis a sort ofinteraction diagramthat shows how procedures is operated with one another and in what order the procedures is operated. It is the building of aMessage Sequence Chart. A sequence diagram shows how the object interaction is arranged in clip sequence. It describes the objects and categories which is involved in the scenario every bit good as in the sequence of messages that has been exchanged between the objects and it is needed to transport out the maps of the scenario. Sequence diagrams are typically assorted with use instance in the Logical View of the system in the development. Sequence diagrams are calledevent diagrams orevent scenarios andtiming diagrams.

A sequence diagram shows the parallel perpendicular lines (line of lifes) , the different procedures or objects that live analogue and the horizontal pointer. The messages exchanged between them in an order in which they have occurred. This allows the specification of simple runtime in a graphical mode.

Sequence diagrams

Make the history

Account Acceptance RESs

Upload the file

File received verification

Make the End User history

Account verification

Request the file

File request verification

File directing response

VM’s inside informations

Threshold Detailss

History inside informations

Figure 5.2: Sequence diagrams

5.2.7 Activity diagram

Activity diagrams is a graphical representations of flow of work of stairss that have taken in the activities and actions with support for pick and interact and concurrence. In the UML activity diagrams are intends to for both the computational and besides for the organisational procedures ( i.e. work flows ) ..

Activity diagrams 1

Figure 5.3: Activity diagrams 1

Activity diagrams 2

Figure 5.4: Activity diagrams 2

5.2.7 Functional mold

Afunction modelorfunctional modelinsystems engineeringandsoftware technology is a structured representation of thefunctions ( activities, actions, procedures, operations ) within the modeledsystemor capable country.

A map theoretical account, similar with theactivity modelorprocess theoretical account, is a graphical representation of anenterprise ‘s map within a defined range. The chief intents of the map theoretical account is to depict the maps and procedures, and aid with find of information demands and besides assist to place chances, and set up a footing for determine the merchandise and the existent service costs.

5.2.7.1 Data flow diagram

Adata flow diagram ( DFD ) is a graphical representation of the flow of informations through aninformation system patterning its procedure. The measure is used to make an overall position of the system which can be elaborated subsequently. DFDs are besides used for visualizationofdata processing ( structured design ) .

A DFD shows what type of information will be input to and what type of information will the end product from the system, and from where the comes and from where it goes to, and where the information will be precisely stored in the system. It does non demo information about the clip of procedures or gives the information about the procedures will run in parallel manner or in a sequence manner ( which is shown on aflowchart ) .

DFDs are the theoretical account of the proposed system. They should clearly demo the demands on which the new system should be built. Later during the design activity is taken as the footing for pulling the system’s construction charts. The Basic Notation used to make a DFD’s are as follows:

1. Dataflow:Datas move in a specific way from an beginning to a finish.

2. Procedure:Peoples, processs, or devices that use or produce ( Transform ) Data. The physical constituent is non identified.

3. Beginning:External beginnings or finish of informations, which may be Peoples, plans, organisations or other entities.

4. Datas Shop:Here informations are stored or referenced by a procedure in the System.

Data Flow Diagram

5.2.7.2 ER Diagram

An ER theoretical account is an abstract manner of depicting adatabase. In the instance of arelational database, which shops informations in tabular arraies, some of the informations in these tabular arraies point to informations in other tabular arraies. It is indispensable to hold one of these if you want to make a good database design. The forms help concentrate on how the database existent works with all of the interactions and informations flows.

Constructing Blocks of Entity Diagram are:

• Entities: An entity is a ‘’thing” that exists and can be unambiguously identii¬?ed.
• Relationss: A ( binary ) relationship type is an association between two entity types.
• Properties: Attribute names ( or merely properties ) are belongingss of entity types.

The Main Advantages of Entity relation diagrams are:

• They are comparatively simple
• They are user friendly
• They can supply a alone position of informations, which is independent of any informations theoretical accounts

5.2.8 Module Description

Nice Systems consists of following sub faculties such as:

• Data Owner
• Cloud Service Provider ( CSP )
• Virtual Machine for Cloud informations storage
• Attack Analyzer
• Remote User

Data Owner:

Users who have the informations and that have to be stored in the cloud and rely on the cloud for informations calculation, it consist of both the single consumers and the organisations.

Cloud Service Provider ( CSP ) :

A Cloud Service Provider ( CSP ) who has important resources and who are adept in edifice and managing distributed cloud storage waiters on different practical machines, owns and operates unrecorded Cloud Computing systems.

Virtual Machine for Cloud informations storage

Cloud informations storage, a user will shops his informations through a Cloud Service Provider ( CSP ) into a group of cloud waiters, which are running in a coincident, the user interacts with the cloud waiters via CSP to entree or recover his informations. In some instances, the user may necessitate to execute block degree operations on his informations. Users should be equipped with security agencies so that they can do uninterrupted rightness confidence of their stored informations even without the being of local transcripts. The cloud consists of different Virtual machines on which the proprietor informations will be allocated and shared and the cloud will listen the different types of aggressors called

1. Stable.There does non be any known exposure on the VM.
2. Vulnerable.Presence of one or more exposures on a VM, which remains undeveloped.