System Level Design Languages:Deployment Diagram

By -

Deployment Diagram

A deployment diagram shows how hardware elements (called nodes) are related to each other and how software elements are mapped onto them. In other words, this diagram shows the general hardware/ software configuration used for running a system. See Figure 86.7 for an example of a deployment diagram. A deployment diagram includes nodes, node instances, artifacts, and connectors between these elements.

A node can be hardware or software element. For example, it can be a Linux server, or an Oracle database. In UML, each node has a name and a stereotype and is displayed by a 3-D box. Several built- in stereotypes exist for nodes, such as ((cdrom)), ((pc client)), ((storage)), and ((Unix server)). There are also icons for these stereotypes which can be used to define the node’s type.

In addition to nodes, a node instance can also be used in a deployment diagram. The relation between a node and a node instance is similar to the relation between a class and an object from that class. The UML representation of a node instance is similar to a node, but differs in the name format. The name of a node instance is like instance-name:node-name. It must also be underlined. Figure 86.8 shows a node instance.

The result of a software development process can be represented as an artifact. These results can be executable files (e.g., with ((executable)) stereotype), source files, user manuals, help files, etc. In UML, an artifact is shown by a rectangle with the ((artifact)) stereotype such as IODriver and Simulator in Figure 86.7, or a document icon in its top-right corner. Each node can include one or more artifacts inside (((storage device)) in Figure 86.7).

System Level Design Languages-0203

System Level Design Languages-0204

A deployment diagram consists of nodes connected to each other by connectors. Each connector in this diagram can have a stereotype and a multiplicity at each end. Figure 86.7 demonstrates a deployment diagram for the SSimBoard system.

Comments

Post a Comment

Popular posts from this blog

SRAM:Decoder and Word-Line Decoding Circuit [10–13].

By -
Image
Decoder and Word-Line Decoding Circuit [10–13] Two kinds of decoders are used in SRAM: the row decoder and the column decoder. Row decoders are needed to select one row of word-lines out of a set of rows in the array. A fast decoder can be implemented by using AND/NAND and OR/NOR gates. Figure 52.7 shows the schematic diagrams of static and dynamic AND gate decoders. The static NAND-type structure is chosen due to its low power consumption, that is, only the decoded row transitions. The dynamic structure is chosen due to its speed and power improvement over conventional static NAND gates. From a low-voltage operation standpoint, a dynamic NOR-base decoding would provide lower delay times through the decoder due to the limited amount of stacking of devices. Figure 52.8 shows circuit diagrams of dynamic NOR gates. The dynamic CMOS gate as shown in Figure 52.8(a) consists of input- NMOSs whose drain nodes are precharged to a high level by a PMOS when a clock signal Φ is at a low lev...
Read more

ASIC and Custom IC Cell Information Representation:GDS2

By -
Image
GDS2 The Graphical Design System (GDS) format is a binary format developed by Calma Company in 1971 to convey IC layout information between IC designers and fabricators. Calma presented GDS2 format, the improved version of GDS, in 1978. Finally in 1991, when Cadence acquired Calma, GDS2 rights were transferred to it. In the design process, after the completion of routing and placement, design rule check (DRC) and layout versus schematic (LVS) are performed to verify the final layout. Then the verified layout, dumped in a GDS2 file, is transferred to IC foundries for fabrication. GDS2 File Format GDS2 is a standard mask layout intermediate format containing a single cell or a library of cells each of which includes a number of geometrical objects such as boundaries, paths, boxes, etc. These objects correspond to different layers of a cell where each layer is specified by a layer number and data type [3]. The file format of GDS2 is in binary. A GDS2 file contains a number of variable...
Read more

Timing Description Languages:SDF

By -
Image
SDF Standard Delay Format (SDF) is an ASCII format used to convey timing information between EDA tools. SDF was first developed by Cadence in 1990. Open Verilog International (OVI) approved SDF version 2 in 1993 and SDF version 2.1 and 3 in the following years. Improving SDF version 3 features, resulted in IEEE Standard 1497 [1]. Role of SDF in Design Process SDF can be used in different levels of a design process to annotate timing specifications, including timing data and constraints. Timing constraints are used during the forward-annotation process while timing data are applied during the back-annotation process. Forward-annotation process deals with porting timing constraints to synthesis, floorplanner, layout, and routing tools to meet the required constraints. During the design process, timing data can be back-annotated to analysis tools (including simulators, static timing analysis tools, etc.) to provide more accurate timing representations. SDF Structure An SDF f...
Read more