Saturday, March 30, 2019
High Level Design (HLD)
High Level Design (HLD)High aim bearingHigh direct public figure (HLD) gives the complete system normal of locomoteal architecture and selective informationbase founding. For the developers it is very much principal(prenominal) to understand how the play of the system is. In this cast the system design squad testers team and the customers plays an important role. For this entry criteria argon required the document that is SRS and the then give-up the ghost criteria allow for be high level design, projects standards, functional design documents, and the database design documents.Problem specializedation information has to be processed in a effective and efficient way.Time consumption should be less.Easy to implement.selective information Definition/ Dictionary entropy dictionary is a repository that contains every last(predicate)(a) the description of all data produced by the application. It is an organization listing of all data elements that ar pertinent to the syste m. defers flurrys For Colud Sever 1 champaign bear on entropy subject sizeKEYFNameVarchar30 basalSkInt10 possessorVarchar30 blot outNameVarchar15 disconcert 5.1 possessor File Table Design field of operations public figure information TYPESIZEKEYVmInt10 primevalproprietorVarchar20MemoryInt10ThrusholdInt10 preconditionVarchar30AttackerIPInt10AttemptsInt10Table 5.2 virtual(prenominal) Memory1 Table DesignFIELD noneDATA TYPESIZEKEY file nameVarchar30primaryOwnerVarchar20SkInt10Table 5.3 CloudFile1 Table Table DesignFIELD NAMEDATA TYPESIZEKEYOwnerVarchar30primaryFileNameVarchar20SkInt10Table 5.4 pose File1 Table Table DesignFIELD NAMEDATA TYPESIZEKEYRemote utilisationrVarchar30primaryOwnerVarchar20Table 5.5 Remote File Table Table DesignFIELD NAMEDATA TYPESIZEKEYAttackerVarchar30primaryAttackerNameVarchar20IP-AddressInt10Table 5.6 Attacker1 Table Table DesignTables For Cloud Sever 2FIELD NAMEDATA TYPESIZEKEYVmInt10primaryOwnerVarchar20MemoryInt10ThrusholdInt10StatusVarchar30Attac kerIPInt10AttemptsInt10Table 5.7 Virtual Memory2 Table Table DesignFIELD NAMEDATA TYPESIZEKEYFileNameVarchar30primaryOwnerVarchar20SkInt10Table 5.8 Cloud File2 Table Table DesignFIELD NAMEDATA TYPESIZEKEYOwnerVarchar30primaryFileNameVarchar20SkInt10Table 5.9 Receive File2 Table Table DesignRemote File2 TableFIELD NAMEDATA TYPESIZEKEYRemote exploiterVarchar30primaryOwnerVarchar20Table 5.10 Remote File2 Table Table DesignFIELD NAMEDATA TYPESIZEKEYAttackerVarchar30primaryAttackerNameVarchar20IP-AddressInt10Table 5.11 Attacker2 Table Table DesignAssumptions and dependenciesThe go forr should know the authentication details to pr levelt the unofficial access of the system.The user must be sensitive of the government rules and regulations that argon to be implemented on the terms.The user must be aware of the flow at which the process of system takes place.Low level designLow level design (LLD) is like detailing the High level design. It defines the real logic for each and the each eve ry component of the system. club plots with the methods and relation between the classes comes under the low level design.The main phase of the inclination oriented approach is as follows-Object poser energetic mouldingObject modelingObject modeling technique describes a method for the analysis, design, and implementation of a system using an object-oriented technique.Object modeling technique consists of four phases, which peck be performed iteratively are Analysis, system design, object design, implementationDynamic modelingThe dynamic model describes the functionalities involved in the project and the person performing those functionalities. Following are the different sort of dynamic draws namely Use shimmy, Sequence, activity diagrams.Use circumstance diagramAuse case diagramis the simple and it is a represented as the users fundamental interaction with the system and describes the specifications of ause case. A use case diagram asshole represent the different kinds of users of a system and the different ways that they will interact with the system. Such diagrams is typically used in conjunction with the textualuse caseas hygienic as it will often be accompanied by other(a) kinds of diagrams. It is the high level piece of functionality that the system caters. An actor is one who interacts with the system.This Use Case diagrams are included into two modeling languages defined by the Object Management Group (OMG). Both the UML and SysML standards define a pictorial nonation for modeling use cases with diagrams. One complain is that they will not define the format for depicting these use cases. Generally both the pictorial notation and the descriptions are very important as they document the use case and it is showing the reason for which an actor uses a system.The use case diagram shows the place of use case with the other use cases. As organizing the mechanism a set of consistent and coherent use cases promotes important figure of system b ehavior and kick in a common disposition between the customer or proprietor or user and the teaching team.Sequence diagramsAsequence diagramis a kind ofinteraction diagramthat shows how processes is operated with one another and in what company the processes is operated. It is the construction of aMessage Sequence Chart. A sequence diagram shows how the object interaction is arranged in time sequence. It describes the objects and classes which is involved in the scenario as well as in the sequence of messages that has been exchanged between the objects and it is needed to head for the hills out the functions of the scenario. Sequence diagrams are typically mixed with use case 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 vertical lines (lifelines), the different processes or objects that live parallel and the horizontal arrow. The messages exchanged betw een them in an say in which they cast off occurred. This allows the specification of simple runtime in a pictorial manner.Sequence diagramsCreate the account Account Acceptance res transfer the file File received confirmation Create the End User account Account confirmation Request the file File signal confirmation File sending response VMs details verge Details Account detailsFigure 5.2 Sequence diagramsActivity diagramActivity diagrams is a graphical bureaus of flow of work of steps that have taken in the activities and actions with support for choice and interact and concurrency. In the UML body process diagrams are intends to for both the computational and in any case for the organizational processes (i.e. workflows)..Activity diagrams 1Figure 5.3 Activity diagrams 1Activity diagrams 2Figure 5.4 Activity diagrams 2Functional modelingAfunction modelorfunctional modelinsystems engineeringandsoftware engineering is a structured representation of thefunctions(activities,a ctions,processes,operations) within the modeledsystemor subject area.A function model, similar with theactivity modelorprocess model, is a graphical representation of anenterprises function within a defined scope. The main purposes of the function model is to describe the functions and processes, and help with discovery of information needs and also help to identify opportunities, and establish a basis for determine the return and the actual service costs.Data flow diagramAdata flow diagram(DFD) is a graphical representation of the flow of data through aninformation system modeling its process. The step is used to create an overall view of the system which can be elaborated later. DFDs are also used for visualizationofdata processing(structured design).A DFD shows what role of information will be input to and what type of information will the output from the system, and from where the comes and from where it goes to, and where the data will be exactly stored in the system. It does not show information about(predicate) the time of processes or gives the information about the processes will operate in parallel way or in a sequence way (which is shown on aflowchart).DFDs are the model of the proposed system. They should clearly show the requirements on which the new system should be built. Later during the design activity is taken as the basis for drawing the systems structure charts. The Basic Notation used to create a DFDs are as follows1. Dataflow Data move in a specific direction from an origin to a destination.2. Process People, procedures, or devices that use or produce (Transform) Data. The physical component is not identified.3. Source External sources or destination of data, which may be People, programs, organizations or other entities4. Data retentivity Here data are stored or referenced by a process in the System.ER drawAn ER model is an squeeze way of describing adatabase. In the case of arelational database, which stores data in tables, some of the data in these tables point to data in other tables. It is essential to have one of these if you want to create a good database design. The patterns help management on how the database actual works with all of the interactions and data flows.Building Blocks of Entity Diagram areEntities An entity is a thing that exists and can be uniquely identied.relations A (binary) relationship type is an association between two entity types. set aparts Attribute names (or simply attributes) are properties of entity types.The Main Advantages of Entity relation diagrams areThey are relatively simpleThey are user friendlyThey can provide a unique view of data, which is independent of any data modelsmodule DescriptionNICE Systems consists of following sub modules such asData OwnerCloud overhaul provider (CSP)Virtual Machine for Cloud data memory boardAttack AnalyzerRemote UserData OwnerUsers who have the data and that have to be stored in the maculate and rely on the cloud for data computa tion, it consist of both the individual(a) consumers and the organizations.Cloud Service Provider (CSP)A Cloud Service Provider (CSP) who has significant resources and who are expert in building and managing distributed cloud storage servers on different virtual machines, owns and operates live Cloud Computing systems.Virtual Machine for Cloud data storageCloud data storage, a user will stores his data through a Cloud Service Provider (CSP) into a group of cloud servers, which are running in a simultaneous, the user interacts with the cloud servers via CSP to access or retrieve his data. In some cases, the user may need to perform block level operations on his data. Users should be equipped with security means so that they can make continuous correctness assurance of their stored data even without the existence of local copies. The cloud consists of different Virtual machines on which the owner data will be allocated and shared and the cloud will discover the different types of at tackers calledStable. There does not exist any known exposure on the VM.Vulnerable. Presence of one or more vulnerabilities on a VM, which remains unexploited.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment