DOCSLIB.ORG

Applying System Descriptors to Address Ambiguity on Deployment Diagrams

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Applying System Descriptors to Address Ambiguity on Deployment Diagrams Applying system descriptors to address ambiguity on deployment diagrams Jalves Nicacio Fabio Petrillo Université du Québec à Chicoutimi Université du Québec à Chicoutimi Chicoutimi, Québec, Canada Chicoutimi, Québec, Canada [email protected] [email protected] ABSTRACT 1 INTRODUCTION Communication between practitioners is essential for product qual- In a modelling process, several levels of abstraction can represent ity in the DevOps context. This communication often takes place software systems across different resources, such as text or dia- through deployment diagrams of a system under development. grams. Deployment diagrams are useful for communication and However, it is common diagrams to become ambiguous or incon- understanding of systems, as they motivate a more active discus- sistent as the system progresses and goes to a continuous delivery sion among participants as facilitating the memorization of details pipeline or production. Moreover, diagrams could not follow the about systems [15]. evolution of systems, and it is challenging to associate diagrams to Nowadays, the growth and rapid adoption of DevOps are notori- production. In this paper, we propose the use of system descriptors ous. The benefits obtained by the software industry through con- to address the ambiguity of deployment diagrams. We state three tinuous integration, testing, monitoring and delivery processes are main hypotheses (1) if a deployment diagram is generated from a undeniable. Additionally, the adoption of systems descriptors, such valid system descriptor then the diagram is unambiguous; (2) if a as Puppet, Chef, Docker-compose and Kubernetes Pods, proved to valid system descriptor is generated from a deployment diagram be a prominent approach to increase the quality and productivity then the descriptor is unambiguous; (3) if a diagram ` generated of information systems. from a descriptor 퐴 is unambiguous and if a descriptor 퐵 is gener- However, system diagrams (as UML deployment diagrams) usu- ated from the diagram ` equally unambiguous then descriptors 퐴 ally remain schematic and disassociated from production reality. and 퐵 are equivalent. We report a case study to test our hypothe- Furthermore, diagrams do not follow the evolution of the systems, ses. We constructed a system descriptor from Netflix deployment and there are challenges for engineers to synchronize the diagrams diagram, and we applied our tool to generate a new deployment with the system in production. diagram. Finally, we compare the original and generated diagrams Deployment diagrams are complex to design. Observing architec- to evaluate our proposal. Our case study shows the generated de- ture diagrams from technical blogs of Amazon, Linkedin, or Netflix, ployment diagrams are graphically equivalent to system descriptors we noticed that engineers use general-purpose notations to create and eliminated ambiguous aspects of the original diagram. Thus, models in tools such as Visio or previous draw.io. Furthermore, few our preliminary results lead to further evaluation in controlled and deployment diagrams are created using UML (or partially using empirical experiments to test our hypotheses conclusively. them). Brown [7] states that it is common for engineers to reuse el- ements designed in other diagrams, using the copy-paste technique, CCS CONCEPTS but this can lead to making mistakes and inconsistencies. Moreover, • Computer systems organization ! Distributed architectures; the semantic and semiotic variation of graphical notations for the • Software and its engineering ! System description lan- representation of systems architecture gives engineers the freedom guages; Architecture description languages. to adapt graphical components to different domains, but it also allows ambiguous diagrams. KEYWORDS Thus, in this, paper, we propose the use of system descriptors to address the ambiguity of deployment diagrams. We state three main arXiv:2008.11060v2 [cs.SE] 2 Oct 2020 Deployment diagrams, System architecture, System descriptors hypotheses (1) if a deployment diagram is generated from a valid ACM Reference Format: system descriptor then the diagram is unambiguous; (2) if a valid Jalves Nicacio and Fabio Petrillo. 2018. Applying system descriptors to system descriptor is generated from a deployment diagram then address ambiguity on deployment diagrams. In . ACM, New York, NY, USA, the descriptor is unambiguous; (3) if a diagram ` generated from 8 pages. https://doi.org/ a descriptor 퐴 is unambiguous and if a descriptor 퐵 is generated from the diagram ` equally unambiguous then descriptors 퐴 and 퐵 are equivalent. Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed To evaluate our hypotheses, we performed a case study from for profit or commercial advantage and that copies bear this notice and the full citation a single system descriptor: Docker-compose files. In this way, we on the first page. Copyrights for components of this work owned by others than ACM have implemented a prototype capable of generating architecture must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a diagrams from docker-compose files. The prototype reads all blocks fee. Request permissions from [email protected]. of information and analyzes them according to a meta-model that ,, transforms the tags in the docker-compose file into a visual element © 2020 Association for Computing Machinery. https://doi.org/ of the corresponding diagram. ,, Nicacio and Petrillo The main contribution is to present our hypotheses and our pre- the system, diagrams do a better job when it comes to transmitting liminary evaluation, showing the generated deployment diagram data to humans [12]. could be equivalent to system descriptors and eliminate ambiguous Diagram as Code. Diagram as Code is an approach to generate aspects of the original diagram. The remainder of this paper is diagrams in the same way that IaC generates systems infrastruc- organized as follows: Section 2 presents relevant concepts for this ture: through programming. According to [19], Diagram as Code is research (Section 2.1) and defines and contextualizes the ambiguity the design of systems architecture diagrams, using a specific pro- on deployment diagram (Section 2.2). Our proposal is formalized gramming language to describe the diagram’s elementsand their in Section 3. In Section 4, we describe a study carried out with a relationships. tool prototype that generates deployment diagrams from Docker- This approach has sparked recent interest among software engi- Compose files. In Section 5, we present and discuss a preliminary neering practitioners. A non-exhaustive list of some web articles on evaluation. Section 6 presents related work. Section 7 concludes the subject is given in [6, 12, 18, 19]. Table 1 presents a list compiled our work and presents future works. by [12] of Diagram as Code tools and that we extend by adding two 2 CONTEXT more tools found on the Web: Diagrams [19] and diagrams-as-code [18]. We divided this section into two subsections. Firstly, we present the most relevant concepts for this paper in 2.1. Then, in Section 2.2, Table 1: "Diagram as code" tool list. The list has been ex- we introduce the definition of ambiguity on deployment diagram. tended from [12] 2.1 Relevant concepts Tool Language License Local Online Systems descriptors. They are scripts for automation, standard- Graphviz DOT Eclipse Public License 1.0 yes yes ization and management of infrastructure in production environ- PlantUML Text GPL-3.0 yes yes Mermaid Text MIT License yes yes ments. System descriptors emerge within the context of Infras- Ditaa ASCII LGPL-3.0 yes no tructure as Code (IaC), which specifies the definition and setup WSD Text - no yes of the software infrastructure required to run a system by using code2flow Text - no yes configuration scripts [5]. Structurizr Java, .NET - no yes In practice, system descriptors are artifacts that describe a system Diagrams Python MIT License yes no diagram-as-code Javascript - yes yes architecture. Providers, such as Chef, Dockerfile and Puppet [11, 22, 24], are tools that produce system descriptors. Likewise, container orchestrators, such as Docker-Compose and Kubernetes Pods [10, As far as we know, this is the first work to introduce the diagram 16], also produce system descriptors. as a code approach in the scientific community. The system descriptor files are written in different languages, Deployment diagrams. There is a vast literature on deploy- such as JSON, YAML, or even in a specific domain language (DSL), ment diagrams. According to the UML Specification [14], “deploy- as is the case with the Puppet tool. They can still be written in ment diagrams show the configuration of run-time processing el- general-purpose languages, as is the case with the Chef tool that ements and the software components, processes, and objects that uses Ruby to generate the system descriptor scripts. execute on them”. Another definition says that a deployment dia- The Listing 1 illustrates a system descriptor: a docker-compose gram is a graph of nodes connected by communication associations script that details the configuration of the database service, called [9]. One of the deployment diagram functions is to map the software db. According to the script’s instructions,
Load more

Recommended publications
  • Guidelines for UML Or Sysml Modelling Within an Enterprise Architecture
    Guidelines for UML or SysML modelling within an enterprise architecture Mälardalen University Academy of Innovation, Design and Technology Author: Charlie Höglund Email: [email protected] Bachelor of Science in Computer Science/Basic level, 15hp Date: 2017-06-08 Examiner: Jan Carlson Supervisor: Daniel Sundmark Company supervisor: Fredric Andréasson (Volvo Construction Equipment) Abstract Enterprise Architectures (EA) are used to describe an enterprise’s structure in a standardized way. An Enterprise Architecture also provides decision-support when choosing a direction or making changes at different levels of an enterprise, such as the business architecture or technology architecture level. This can involve decisions such as: What kind of enterprise should this be, what kind of technologies should be used for new system developments etcetera. Therefore, using the Unified Modelling Language (UML) or Systems Modelling Language (SysML) together with standardized guidelines that help you decide what to do before, during, and after modelling could be important for producing correct and useful system models, which later on will be used to develop actual systems. At the moment, standardized guidelines of this kind do not really exist. However, there are a lot of information about why you should use UML or SysML, what kinds of UML or SysML diagrams that exist, or what notations to follow when creating a specific UML or SysML diagram. In this thesis, the objective has been to research about the usefulness and creation of standardized guidelines for UML or SysML modelling in an Enterprise Architecture (i.e. mainly intended for the automotive industry domain). For this reason, the two research questions: “how can you create useful standardized guidelines for UML or SysML modelling?” and “what do useful standardized guidelines for UML or SysML modelling look like?” were chosen.
    [Show full text]
  • OMG Systems Modeling Language (OMG Sysml™) Tutorial 25 June 2007
    OMG Systems Modeling Language (OMG SysML™) Tutorial 25 June 2007 Sanford Friedenthal Alan Moore Rick Steiner (emails included in references at end) Copyright © 2006, 2007 by Object Management Group. Published and used by INCOSE and affiliated societies with permission. Status • Specification status – Adopted by OMG in May ’06 – Finalization Task Force Report in March ’07 – Available Specification v1.0 expected June ‘07 – Revision task force chartered for SysML v1.1 in March ‘07 • This tutorial is based on the OMG SysML adopted specification (ad-06-03-01) and changes proposed by the Finalization Task Force (ptc/07-03-03) • This tutorial, the specifications, papers, and vendor info can be found on the OMG SysML Website at http://www.omgsysml.org/ 7/26/2007 Copyright © 2006,2007 by Object Management Group. 2 Objectives & Intended Audience At the end of this tutorial, you should have an awareness of: • Benefits of model driven approaches for systems engineering • SysML diagrams and language concepts • How to apply SysML as part of a model based SE process • Basic considerations for transitioning to SysML This course is not intended to make you a systems modeler! You must use the language. Intended Audience: • Practicing Systems Engineers interested in system modeling • Software Engineers who want to better understand how to integrate software and system models • Familiarity with UML is not required, but it helps 7/26/2007 Copyright © 2006,2007 by Object Management Group. 3 Topics • Motivation & Background • Diagram Overview and Language Concepts • SysML Modeling as Part of SE Process – Structured Analysis – Distiller Example – OOSEM – Enhanced Security System Example • SysML in a Standards Framework • Transitioning to SysML • Summary 7/26/2007 Copyright © 2006,2007 by Object Management Group.
    [Show full text]
  • AP42 Section: Reference
    AP42 Section: 13.2.1 Reference: 8 Title: Paved Road Particulate Emissions, C. Cowherd, Jr., and P. J. Englehart, EPA-600/7-84-077, U. S. Environmental Protection Agency, Cincinnati, OH, July 1984. United Slates EPA-600 17- 84-077 Environmental Protection Agency July 1984 PAVED ROADS eEPA Research and Ap-42 Section 11.2.51\ Reference Number Development 4 iI J PAVED ROAD PARTICULATE EMISSIONS Source Category Report Prepared for Office of Air Quality Planning and Standards Prepared by Industrial Environmental Research Laboratory Research Triangle Park NC 2771 1 RESEARCH REPORTING SERIES Research reports of the Office of Research and Development, US. Environmental Protection Agency, have been grouped into nine series. These nine broad cate- gories were established to facilitate further development and application of en- vironmental technology. Elimination of traditional grouping was consciously planned to foster technology transfer and a maximum interface in related fields. The nine series are: 1. Environmental Health Effects Research 2. Environmental Protection Technology 3. Ecological Research 4. Environmental Monitoring .. 5. Socioeconomic Environmental Studies 6. Scientific and Technical Assessment Reports (STAR) 7. Interagency Energy-Environment Research and Development 8. “Special” Reports 9. Miscellaneous Reports This report has been assigned to the INTERAGENCY ENERGY-ENVIRONMENT RESEARCH AND DEVELOPMENT series. Reports in this series result from the effort funded under the 17-agency Federal Energy/Environment Research and Development Program. These studies relate to EPA’s mission to protect the public health and welfare from adverse effects of pollutants associated with energy sys- tems. The goal of the Program is to assure the rapid development of domestic energy supplies in an environmentally-compatible manner by providing the nec- essary environmental data and control technology.
    [Show full text]
  • Plantuml Language Reference Guide (Version 1.2021.2)
    Drawing UML with PlantUML PlantUML Language Reference Guide (Version 1.2021.2) PlantUML is a component that allows to quickly write : • Sequence diagram • Usecase diagram • Class diagram • Object diagram • Activity diagram • Component diagram • Deployment diagram • State diagram • Timing diagram The following non-UML diagrams are also supported: • JSON Data • YAML Data • Network diagram (nwdiag) • Wireframe graphical interface • Archimate diagram • Specification and Description Language (SDL) • Ditaa diagram • Gantt diagram • MindMap diagram • Work Breakdown Structure diagram • Mathematic with AsciiMath or JLaTeXMath notation • Entity Relationship diagram Diagrams are defined using a simple and intuitive language. 1 SEQUENCE DIAGRAM 1 Sequence Diagram 1.1 Basic examples The sequence -> is used to draw a message between two participants. Participants do not have to be explicitly declared. To have a dotted arrow, you use --> It is also possible to use <- and <--. That does not change the drawing, but may improve readability. Note that this is only true for sequence diagrams, rules are different for the other diagrams. @startuml Alice -> Bob: Authentication Request Bob --> Alice: Authentication Response Alice -> Bob: Another authentication Request Alice <-- Bob: Another authentication Response @enduml 1.2 Declaring participant If the keyword participant is used to declare a participant, more control on that participant is possible. The order of declaration will be the (default) order of display. Using these other keywords to declare participants
    [Show full text]
  • OMG Systems Modeling Language (OMG Sysml™) Tutorial
    OMG Systems Modeling Language (OMG SysML™) Tutorial 11 July 2006 Sanford Friedenthal Alan Moore Rick Steiner Copyright © 2006 by Object Management Group. Published and used by INCOSE and affiliated societies with permission. Caveat • This material is based on version 1.0 of the SysML specification (ad-06-03-01) – Adopted by OMG in May ’06 – Going through finalization process • OMG SysML Website – http://www.omgsysml.org/ 11 July 2006 Copyright © 2006 by Object Management Group. 2 Objectives & Intended Audience At the end of this tutorial, you should understand the: • Benefits of model driven approaches to systems engineering • Types of SysML diagrams and their basic constructs • Cross-cutting principles for relating elements across diagrams • Relationship between SysML and other Standards • High-level process for transitioning to SysML This course is not intended to make you a systems modeler! You must use the language. Intended Audience: • Practicing Systems Engineers interested in system modeling – Already familiar with system modeling & tools, or – Want to learn about systems modeling • Software Engineers who want to express systems concepts • Familiarity with UML is not required, but it will help 11 July 2006 Copyright © 2006 by Object Management Group. 3 Topics • Motivation & Background (30) • Diagram Overview (135) • SysML Modeling as Part of SE Process (120) – Structured Analysis – Distiller Example – OOSEM – Enhanced Security System Example • SysML in a Standards Framework (20) • Transitioning to SysML (10) • Summary (15) 11 July 2006 Copyright © 2006 by Object Management Group. 4 Motivation & Background SE Practices for Describing Systems Future Past • Specifications • Interface requirements • System design • Analysis & Trade-off • Test plans Moving from Document centric to Model centric 11 July 2006 Copyright © 2006 by Object Management Group.
    [Show full text]
  • Examples of UML Diagrams
    UML Diagrams Examples Examples by Technology or Application Domain Online shopping UML diagrams Ticket vending machine UML diagrams Bank ATM UML diagrams Hospital management UML diagrams Digital imaging and communications in medicine (DICOM) UML diagrams Java technology UML diagrams Application development for Android UML diagrams Software licensing and protection using SafeNet Sentinel HASP security solution Examples by Types of Diagrams Activity diagram examples Class diagram examples Communication diagram examples Component diagram examples Composite structure diagram examples Deployment diagram examples Information flow diagram example Interaction overview diagram examples Object diagram example Package diagram examples Profile diagram examples http://www.uml-diagrams.org/index-examples.html 1/15/17, 1034 AM Page 1 of 33 Sequence diagram examples State machine diagram examples Timing diagram examples Use case diagram examples Use Case Diagrams Business Use Case Diagrams Airport check-in and security screening business model Restaurant business model System Use Case Diagrams Ticket vending machine http://www.uml-diagrams.org/index-examples.html 1/15/17, 1034 AM Page 2 of 33 Bank ATM UML use case diagrams examples Point of Sales (POS) terminal e-Library online public access catalog (OPAC) http://www.uml-diagrams.org/index-examples.html 1/15/17, 1034 AM Page 3 of 33 Online shopping use case diagrams Credit card processing system Website administration http://www.uml-diagrams.org/index-examples.html 1/15/17, 1034 AM Page 4 of 33 Hospital
    [Show full text]
  • Part I Environmental Diagrams
    Adaptive Software Engineering G22.3033-007 Session 3 – Sub-Topic Presentation 1 Use Case Modeling Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute of Mathematical Sciences 1 Part I Environmental Diagrams 2 1 What it is • Environmental Diagram Rent Video Video Store Pay Information System Employees Clerk Customer Payroll Clerk 3 What it is • A picture containing all the important players (Actors) • Includes players both inside and outside of the system • Actors are a critical component • External events are a second critical component 4 2 Creating the Diagram • To create an environmental diagram • 1. Identify all the initiating actors • 2. Identify all the related external events associated with each actor 5 Why it is used • A diagram is needed to show the context or scope of the proposed system • At this time actors and external events are the critical components • It is helpful to include all the participants as well 6 3 Creating the Diagram • 3. Identify all the participating Actors • These actors may be inside (internal) or outside (external) to the system 7 Creating the Diagram • Examples of an internal actor – Clerk who enters the purchase into a Point of Sale terminal – Clerk who places paper in the printer – Accountant who audits report 8 4 Creating the Diagram • Examples of an external actor – Accountant who audits report – A credit authorizing service – A DMV check for renting a car 9 Creating the Diagram •4.Draw a cloud • 5. Then draw initiating actors on the left of the cloud • 6. Then draw participating external actors outside the cloud • 7.
    [Show full text]
  • TAGDUR: a Tool for Producing UML Sequence, Deployment, and Component Diagrams Through Reengineering of Legacy Systems
    TAGDUR: A Tool for Producing UML Sequence, Deployment, and Component Diagrams Through Reengineering of Legacy Systems Richard Millham, Jianjun Pu, Hongji Yang De Montfort University, England [email protected] & [email protected] Abstract: A further introduction of TAGDUR, a documents this transformed system through a reengineering tool that first transforms a series of UML diagrams. This paper focuses on procedural legacy system into an object-oriented, TAGDUR’s generation of sequence, deployment, event-driven system and then models and and component diagrams. Keywords: UML (Unified Modeling Language), Reengineering, WSL This paper is a second installment in a series [4] accommodate a multi-tiered, Web-based that introduces TAGDUR (Transformation and platform. In order to accommodate this Automatic Generation of Documentation in remodeled platform, the original sequential- UML through Reengineering). TAGDUR is a driven, procedurally structured legacy system reengineering tool that transforms a legacy must be transformed to an object-oriented, event- system’s outmoded architecture to a more driven system. Object orientation, because it modern one and then represents this transformed encapsulates variables and procedures into system through a series of UML (Unified modules, is well suited to this new Web Modeling Language) diagrams in order to architecture where pieces of software must be overcome a legacy system’s frequent lack of encapsulated into component modules with documentation. The architectural transformation clearly defined interfaces. A transfer to a Web- is from the legacy system’s original based architecture requires a real-time, event- procedurally-structured to an object-oriented, driven response rather than the legacy system’s event-driven architecture.
    [Show full text]
  • Working with Deployment Diagram
    UNIVERSITY OF ENGINEERING AND TECHNOLOGY, TAXILA FACULTY OF TELECOMMUNICATION AND INFORMATION ENGINEERING SOFTWARE ENGINEERING DEPARTMENT Lab # 09 Working with Deployment Diagram You’ll learn in this Lab: What a deployment diagram is Applying deployment diagrams Deployment diagrams in the big picture of the UML A solid blueprint for setting up the hardware is essential to system design. The UML provides you with symbols for creating a clear picture of how the final hardware setup should look, along with the items that reside on the hardware What is a Deployment Diagram? A deployment diagram shows how artifacts are deployed on system hardware, and how the pieces of hardware connect to one another. The main hardware item is a node, a generic name for a computing resource. A deployment diagram in the Unified Modeling Language models the physical deployment of artifacts on nodes. To describe a web site, for example, a deployment diagram would show what hardware components ("nodes") exist (e.g., a web server, an application server, and a database server), what software components ("artifacts") run on each node (e.g., web application, database), and how the different pieces are connected (e.g. JDBC, REST, RMI). In UML 2.0 a cube represents a node (as was the case in UML 1.x). You supply a name for the node, and you can add the keyword «Device», although it's usually not necessary. Software Design and Architecture 4th Semester-SE UET Taxila Figure1. Representing a node in the UML A Node is either a hardware or software element. It is shown as a three-dimensional box shape, as shown below.
    [Show full text]
  • CSC2125: Modeling Methods, Tools and Techniques Winter 2018
    CSC2125: Modeling Methods, Tools and Techniques Winter 2018 Marsha Chechik Department of Computer Science University of Toronto Software Models http://www.cs.toronto.edu/~chechik/courses18/csc2125 csc2125. Winter 2018, Lecture 2b 1 Plan for the rest of the lecture • Part 0. Modeling • Part 1. Software Models, UML, OCL • Part 2. Meta-modeling, model mappings, DSLs / generic languages, model transformations • Part 3 (if we have time). How usable are models? csc2125. Winter 2018, Lecture 2b 2 csc2125. Winter 2018, Lecture 2b 3 What is Being Modelled? <postal-address> ::= <name-part> <street-address> <zip-part> <name-part> ::= <personal-part> <last-name> <opt-jr-part> <EOL> | <personal-part> <name-part> E = a KLOCb csc2125. Winter 2018, Lecture 2b 4 Models as Views Mason's Carpenter's View Architect's View View Electrician's View Tax Collector's Plumber's View View Landlord's Interior / Tenant's Designer's View View Zoning Law Interior View Designer's View Every view • obtained by a different projection, abstraction, translation • may be expressed in a different notation (modelling language) • reflects a different intent csc2125. Winter 2018, Lecture 2b 5 Modelling Paradigms Fundamental modelling paradigms, each emphasizing some basic view of the software to be developed. Structure Data System Functionality Schema Functionality Software Architecture Use Cases Deployment Algorithms Scenarios Constraints Constraints System System Behaviour Interactions Behaviour csc2125. Winter 2018, Lecture 2b 6 Entity-Relationship Diagrams An ER diagram is a structural model representing a software system's data elements and relationships among them. relationship entity attribute title course enrolled student name course no. id • originally invented for model database design (Chen, 1976) • emphasizes concepts/data • relationships can represent associations, navigability, containment, dependencies, etc.
    [Show full text]
  • Tutorial Exercise 4 Answer
    Information System Design (U08182) Tutorial Exercise 4 Answer 1. List the different categories of software that may be used in developing a system. CASE tools; compilers, interpreters and run-time support; visual editors; integrated development environments; class browsers; component managers; DBMS; CORBA; testing tools; conversion tools; documentation generators; configuration management systems; debuggers. 2. What packages (not the UML package concept) have you used and what categories do they fall into? The answer to this will depend on the individual. Examples would be: Rational Rose – CASE tool; Java – compiler with run-time support; JBuilder – visual editor/IDE; Microsoft Developer’s Studio – IDE; Oracle – DBMS; VisiBroker – CORBA ORB; TestScope – testing tool; ClearCase – configuration mangement tool; gdb – debugger. 3. Define what is meant by a component. A physical element of a system, usually a file of some sort. can be a source file, used in producing the software for the system, or an element of the runtime system 4. Define what is meant by a node. Processor in the implementation of a system, shown in a deployment diagram. 5. What is a notation for a component? U08182 @Peter Lo 2010 1 6. What is a notation for a node? 7. What are the main purposes of using component diagrams? Model physical software components and the relationships between them; Model source code and relationships between files; Model the structure of releases of software; Specify the files that are compiled into an executable. 8. What are the main purposes of using deployment diagrams? Model physical hardware elements and the communication paths between them; Plan the architecture of the system; Document the deployment of software components on hardware nodes.
    [Show full text]
  • Reference Manual for Astah Professional And
    Astah Reference Manual Ver. 8.4 Astah professional Astah UML Copyright© 2006-2021 Change Vision, Inc. All rights reserved. Astah Reference Manual The contents of this manual may be changed without prior notice. The following trademarks and copyright apply to the software that is provided with this manual. Copyright© 2006-2021 Change Vision, Inc. All rights reserved. UML and Unified Modeling Language are either registered trademarks or trademarks of Object Management Group, Inc. in the United States and/or other countries. Java is registered trademarks of Oracle and/or its affiliates. Mind Map is a registered trademark of the Buzan Organization Ltd. If other trademarked product names or company names appear, they are only used as names. Symbols, such as ™, ®, ©, are omitted in the main contents. Astah Reference Manual Introduction This Manual, “Astah Reference Manual”, briefly explains the functions of Astah and how to use them. Astah Professional is a system design tool that supports UML (Unified Modeling Language) 2.x (partly), UML1.4, Flowchart, Data Flow Diagram, ER diagram, CRUD, Requirement diagram and Mind Map. Astah UML is a modeling tool that supports UML (Unified Modeling Language) 2.x (partly), UML1.4 and Mind Map. Structure of this Manual · Chapter 1-3 Overview of Astah and getting started · Chapter 4-6 Basic Astah concepts and Main Menu functions · Chapter 7-13 Basic diagram and model operations · Chapter14 Specific diagram and diagram element operations · Chapter15-46 System set-up and specific Astah features Note · Functions with [P] are supported in Astah Professional only. These are not included in Astah UML.
    [Show full text]