DOCSLIB.ORG

Borland Together 2008 Borland Together UML 2.1 Guide Borland Software Corporation 4 Hutton Centre Dr., Suite 900 Santa Ana, CA 92707

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Borland Together 2008 Borland Together UML 2.1 Guide Borland Software Corporation 4 Hutton Centre Dr., Suite 900 Santa Ana, CA 92707 Borland Together 2008 Borland Together UML 2.1 Guide Borland Software Corporation 4 Hutton Centre Dr., Suite 900 Santa Ana, CA 92707 Copyright 2009-2010 Micro Focus (IP) Limited. All Rights Reserved.Together contains derivative works of Borland Software Corporation, Copyright 2008-2010 Borland Software Corporation (a Micro Focus company). MICRO FOCUS and the Micro Focus logo, among others, are trademarks or registered trademarks of Micro Focus (IP) Limited or its subsidiaries or affiliated companies in the United States, United Kingdom and other countries. BORLAND, the Borland logo and Together are trademarks or registered trademarks of Borland Software Corporation or its subsidiaries or affiliated companies in the United States, United Kingdom and other countries. All other marks are the property of their respective owners. ii Contents Concepts...................................................................................................................5 UML 2.1 Overview......................................................................................................................5 UML 2.1 Implementation in Together .........................................................................................6 Provided and Required Interface Links of a Port........................................................................6 Required Interface...........................................................................................................7 Provided Interface...........................................................................................................8 UML 2.1 Diagrams.....................................................................................................................8 UML 2.1 Common Diagram Elements and Preferences..................................................9 UML 2.1 Activity Diagram..............................................................................................10 UML 2.1 Class Diagram................................................................................................18 UML 2.1 Component Diagram Definition.......................................................................26 UML 2.1 Composite Structure Diagram.........................................................................30 UML 2.1 Deployment Diagram......................................................................................36 UML 2.1 Profile Diagram...............................................................................................40 UML 2.1 State Machine Diagram..................................................................................43 UML 2.1 Use Case Diagram..........................................................................................47 Procedures..............................................................................................................53 Exporting a Model to UML 2.1..................................................................................................53 Converting a UML 2.0 Model to a UML 2.1 Model...................................................................54 Creating a Required Interface..................................................................................................54 Managing the Visibility of Provided and Required Interface Links............................................55 Working with Associations........................................................................................................56 Creating an Association.................................................................................................56 Creating an Association from Existing Properties.........................................................56 Change the Aggregation Type of an Association...........................................................57 Editing the Properties of AssociationEnds....................................................................57 Running a UML2Tools Report on a UML 2.1 Diagram File......................................................57 Working with UML 2.1 Profiles.................................................................................................58 A Typical Scenario of Creating a Profile........................................................................58 Creating a Project..........................................................................................................59 Creating a Profile...........................................................................................................60 Populating Profile Diagrams..........................................................................................61 Defining Profiles ...........................................................................................................62 Contents | 3 Registering Profiles ......................................................................................................63 Applying Profiles ...........................................................................................................63 Applying Stereotypes ....................................................................................................64 Reference................................................................................................................65 UML 2 Tools Wizard.................................................................................................................65 UML 2.1 Export Audits.............................................................................................................66 4 | Contents Concepts This section contains information about UML 2.1 concepts, capabilities, and best practices. Related Topics UML 2.1 Overview on page 5 UML 2.1 Implementation in Together on page 6 Provided and Required Interface Links of a Port on page 6 UML 2.1 Diagrams on page 8 UML 2.1 Overview The Unified Modeling Language (UML) is a tool maintained by the Object Management Group (OMG) that lets you visually specify the design of software systems using standardized diagrams. With its most recent version, UML 2.1, the UML standard for defining software systems has been functionally extended to address toolsmith issues, including the implementation of redefinition and bidirectional associations in the metamodel. UML 2.1 provides a set of Graphical Modeling Framework (GMF) editors based on the MDT UML2 metamodel. Currently, UML 2.1 supports eight of the thirteen basic diagram types. With the following diagram editors, divided into two functional sets, you can view and edit models: • Behavior – These diagrams depict the interaction of model elements and the different states of the model as its design is applied. • Activity – Similar to a flowchart, these show the flow of activities used to accomplish a single task. • State Machine – Depict the possible states of a model element and the transitions that cause a change in the state. • Use Case – Describe scenarios that a system does, from the point of view of an external observer, in order to accomplish a single task or goal. These diagrams emphasize what a system does rather than how. • Structures – These diagrams depict the static architecture of models, which include the elements that comprise the model and their relationships. • Class – Depict an overview of a system by showing the relationships among its classes rather than what happens when they do interact. • Component – Show the high-level physical analogs of a system and their structural relationships and interfaces. These diagrams are typically used to model the logical components of a system rather than its physical attributes, which are best handled by deployment diagrams. • Composite Structure – Show the configuration of interconnected parts that collaborate to perform the behavior and achieve the purpose of the containing classifier. • Deployment – Depict the hardware functionality of a software system and how it gets executed. • Profile Definition – Let you define all the domain model's non-UML properties and provide a way for metaclasses from existing metamodels to be extended so they can be adapted for different purposes. Concepts | 5 The following resources offer information and assistance: • Eclipse Model Development Tools (MDT) – UML2Tools • Eclipsepedia MDT-UML2Tools FAQ • OMG Unified Modeling Language (OMG UML), Superstructure, V2.1.2 • Mailing list: mdt-uml2tools.dev Note: Since Together 2008 Release 3, the feature set Together UML 2.1 Diagrams is not required to be installed.When not present, the corresponding parts of the user interface and functionality are not available. Refer to the installation instructions in the Release Notes document for additional info about the product installation process. Related Topics Concepts on page 5 UML 2.1 Implementation in Together Even in its latest version of UML, the OMG faces usability issues because of its patchwork contributions from varying groups of vendors and distinct legacy notations. These issues include language complexity, notational inconsistency, semantical ambiguity, and a handicapped interchange format that limits model portability between modeling tools. The Together architecture streamlines some of these challenges. Because of Together's compatibility with XML Metadata Interchange (XMI), you can import projects or sections of projects that were created in other modeling tools. Diagrams of such projects can benefit from Together's sophisticated layout capabilities, which other modeling tools lack. In addition to its support of UML 2.x and XMI format
Load more

Recommended publications
  • Model Based Systems Engineering Approach to Autonomous Driving
    DEGREE PROJECT IN ELECTRICAL ENGINEERING, SECOND CYCLE, 30 CREDITS STOCKHOLM, SWEDEN 2018 Model Based Systems Engineering Approach to Autonomous Driving Application of SysML for trajectory planning of autonomous vehicle SARANGI VEERMANI LEKAMANI KTH ROYAL INSTITUTE OF TECHNOLOGY SCHOOL OF ELECTRICAL ENGINEERING AND COMPUTER SCIENCE Author Sarangi Veeramani Lekamani [email protected] School of Electrical Engineering and Computer Science KTH Royal Institute of Technology Place for Project Sodertalje, Sweden AVL MTC AB Examiner Ingo Sander School of Electrical Engineering and Computer Science KTH Royal Institute of Technology Supervisor George Ungureanu School of Electrical Engineering and Computer Science KTH Royal Institute of Technology Industrial Supervisor Hakan Sahin AVL MTC AB Abstract Model Based Systems Engineering (MBSE) approach aims at implementing various processes of Systems Engineering (SE) through diagrams that provide different perspectives of the same underlying system. This approach provides a basis that helps develop a complex system in a systematic manner. Thus, this thesis aims at deriving a system model through this approach for the purpose of autonomous driving, specifically focusing on developing the subsystem responsible for generating a feasible trajectory for a miniature vehicle, called AutoCar, to enable it to move towards a goal. The report provides a background on MBSE and System Modeling Language (SysML) which is used for modelling the system. With this background, an MBSE framework for AutoCar is derived and the overall system design is explained. This report further explains the concepts involved in autonomous trajectory planning followed by an introduction to Robot Operating System (ROS) and its application for trajectory planning of the system. The report concludes with a detailed analysis on the benefits of using this approach for developing a system.
    [Show full text]
  • Information Technology and Software Development
    Course Title: Information Technology and Software Development NATIONAL OPEN UNIVERSITY OF NIGERIA SCHOOL OF SCIENCE AND TECHNOLOGY COURSE CODE: CIT 703 COURSE TITLE: Information Technology and Software Development National Open University of Nigeria, Victoria Island, Lagos Page 1 Course Title: Information Technology and Software Development Course Code Course Title Information Technology and Software Development Course Developer/Writer Eze, Festus Chux Department of Computer Science Ebonyi State University Abakaliki Course Editor Programme Leader Course Coordinator National Open University of Nigeria, Victoria Island, Lagos Page 2 Course Title: Information Technology and Software Development Introduction Information Technology and Software Development is a three credit load course for all the students offering Post Graduate Diploma (PGD) in Computer Science, Information Technology and other allied courses. Software Development is a major branch in computing and information Technology. A software development professional oversees the processes of software development, the management of software development project, the maintenance of the installed software in an organisation. For sometime the field has been dominated with what is the definitive process of software development. Furthermore there has been the running battle between professionals and managers on who should control a software development project. There is an attempt to classify it as any other project that an organisation handles hence anybody could manage it. Whereas others see it as a highly professional issue that requires high precision in design, management and implementation. However, software development is all involving. It involves the user (client) whose interest is paramount. The developing organisation and her professionals ( team)are of great importance. Therefore a successful exercise can only take place when all these variegated interests are harmonised.
    [Show full text]
  • APECS: Polychrony Based End-To-End Embedded System Design and Code Synthesis
    APECS: Polychrony based End-to-End Embedded System Design and Code Synthesis Matthew E. Anderson Dissertation submitted to the faculty of the Virginia Polytechnic Institute and State University in partial fulfillment of the requirements for the degree of Doctor of Philosophy in Computer Engineering Sandeep K. Shukla, Chair Lamine Mili Alireza Haghighat Chao Wang Yi Deng April 3, 2015 Blacksburg, Virginia Keywords: AADL, CPS, Model-based code synthesis, correct-by-construction code synthesis, Polychrony, code generators, OSATE, Ocarina Copyright 2015, Matthew E. Anderson APECS: Polychrony based End-to-End Embedded System Design and Code Synthesis Matthew E. Anderson (ABSTRACT) The development of high integrity embedded systems remains an arduous and error-prone task, despite the efforts by researchers in inventing tools and techniques for design automa- tion. Much of the problem arises from the fact that the semantics of the modeling languages for the various tools, are often distinct, and the semantics gaps are often filled manually through the engineer's understanding of one model or an abstraction. This provides an op- portunity for bugs to creep in, other than standardising software engineering errors germane to such complex system engineering. Since embedded systems applications such as avionics, automotive, or industrial automation are safety critical, it is very important to invent tools, and methodologies for safe and reliable system design. Much of the tools, and techniques deal with either the design of embedded platforms (hardware, networking, firmware etc), and software stack separately. The problem of the semantic gap between these two, as well as between models of computation used to capture semantics must be solved in order to design safer embedded systems.
    [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]
  • Tram - Trng - Modeling - UML Startup - All.Pages 2 1991 Booch 91
    UML Start-Up Training UB1 Index History Overview Diagrams Use Case Diagram Sequence Diagram Activity Diagram Class Diagram Composite Structure Diagram UML State Machine Diagram This training course is designed with the intention to teach UML in not Package Diagram longer than a day. Yes UML is a complicated language with a lot of diagrams, model elements, a complex syntax and semantic; and most people claim that it takes a long time to learn that language. But: if we concentrate our efforts to the most important part of the language you will be able to become familiar with it in a day. And: use it frequently, then you’ll get the less important things by use and by reading a good book: the standard (visit the web pages from OMG and you’ll manage to download the standard, it’s free of charge). History The “OO tower” of Babel In the early Nineties there was a vast amount of competing object oriented modeling approaches together with corresponding kinds of diagrams and CASE environments which, sometimes more and sometimes less, differ from each other. Examples: Object-Oriented Analysis (OOA): Coad-Yourdon 1991 Object-Oriented Design (OOD): Booch 1991 Object Modeling Technique (OMT): Rumbaugh 1991 OO Software Engineering (OOSE): Jacobson 1992 Fusion: Coleman 1994 The Idea: Unified Modeling Language The idea of Grady Booch: A number of OO modeling dialects is replaced by a standardized language in order to bury unnecessary ditch (and religious) wars in the OO environment unite advantages of different modeling approaches relieve potential users of being spoilt for choice provide for the preconditions for data exchange between OO tools enable close integration of OO tools reduce dependencies of users of one supplier release tool manufacturers of the support of many approaches.
    [Show full text]
  • Fakulta Informatiky UML Modeling Tools for Blind People Bakalářská
    Masarykova univerzita Fakulta informatiky UML modeling tools for blind people Bakalářská práce Lukáš Tyrychtr 2017 MASARYKOVA UNIVERZITA Fakulta informatiky ZADÁNÍ BAKALÁŘSKÉ PRÁCE Student: Lukáš Tyrychtr Program: Aplikovaná informatika Obor: Aplikovaná informatika Specializace: Bez specializace Garant oboru: prof. RNDr. Jiří Barnat, Ph.D. Vedoucí práce: Mgr. Dalibor Toth Katedra: Katedra počítačových systémů a komunikací Název práce: Nástroje pro UML modelování pro nevidomé Název práce anglicky: UML modeling tools for blind people Zadání: The thesis will focus on software engineering modeling tools for blind people, mainly at com•monly used models -UML and ERD (Plant UML, bachelor thesis of Bc. Mikulášek -Models of Structured Analysis for Blind Persons -2009). Student will evaluate identified tools and he will also try to contact another similar centers which cooperate in this domain (e.g. Karlsruhe Institute of Technology, Tsukuba University of Technology). The thesis will also contain Plant UML tool outputs evaluation in three categories -students of Software engineering at Faculty of Informatics, MU, Brno; lecturers of the same course; person without UML knowledge (e.g. customer) The thesis will contain short summary (2 standardized pages) of results in English (in case it will not be written in English). Literatura: ARLOW, Jim a Ila NEUSTADT. UML a unifikovaný proces vývoje aplikací : průvodce ana­lýzou a návrhem objektově orientovaného softwaru. Brno: Computer Press, 2003. xiii, 387. ISBN 807226947X. FOWLER, Martin a Kendall SCOTT. UML distilled : a brief guide to the standard object mode•ling language. 2nd ed. Boston: Addison-Wesley, 2000. xix, 186 s. ISBN 0-201-65783-X. Zadání bylo schváleno prostřednictvím IS MU. Prohlašuji, že tato práce je mým původním autorským dílem, které jsem vypracoval(a) samostatně.
    [Show full text]
  • Deriving Architecture Design Variants for System Optimization from Design Space Descriptions Expressed Using a Uml Profile
    DERIVING ARCHITECTURE DESIGN VARIANTS FOR SYSTEM OPTIMIZATION FROM DESIGN SPACE DESCRIPTIONS EXPRESSED USING A UML PROFILE Alexander Wichmann Francesco Bedini Ralph Maschotta Armin Zimmermann Technische Universität Ilmenau Department of Computer Science and Automation System and Software Engineering Group PO-Box 100 565, 98684 Ilmenau, Germany [email protected] ABSTRACT In complex (dynamic) systems, models are usually too complex for a direct evaluation, and simulation is the method of choice (indirect optimization). Another aspect is the structure of the design space for complex system. In a recent paper of the authors, an approach is presented for design space description with a UML profile-based description of architectural variations of complex dynamic systems. In orderto execute a simulation of a system variant, one has to be chosen based on the used heuristic, and specified in a standardized way to be used for constructing the actual simulation model with the use of a library of template models. This paper approaches a method to automatically generated individual UML object models from the design space specification for a given parameter selection. Keywords: UML profile, architecture design space description, system optimization, design variants 1 INTRODUCTION Model-based systems design is an important help in the design process of complex systems and aims at reduced risks and better design decisions without the need to implement costly prototypes. In the end, each engineering task can be viewed as an optimization problem of finding the best design alternative under given constraints. However, automatic optimization methods can often not be used because of the complexity of the problem field.
    [Show full text]
  • Evaluating Information Systems: Constructing a Model Processing Framework Relatório Final
    Evaluating Information Systems: Constructing a Model Processing Framework Relatório Final João Dias Santa de Vasconcelos Duarte Dissertação para obtenção do Grau de Mestre em Engenharia Informática e de Computadores Júri Presidente: Prof. José Tribolet Orientador: Prof. André Vasconcelos Vogal: Prof. Pedro Sousa Acompanhante: Eng. José Alegria Junho de 2009 Dedico este trabalho à minha família e à minha namorada, Ana. Não teria conseguido sem o vosso apoio. Muito obrigado. i Abstract Enterprises are growing increasingly hungry for information: the will to empower decisions with carefully digested data, the wish of transform all implicit knowledge into clearly dened, explicit repositories that can be shared by all and the desire to monitor all aspects of their internal dynamics. In the past decade, the rush to technology has created several aws when it comes to managing computers, applications, mid- dleware and information systems and so organisations struggle to understand how all these elements are behaving. Even today, as Enterprise Architectures grow in signicance and are acknowledged as advantageous arti- facts to help manage change, their benet to the organisation has yet to be fully explored. We therefore combine our desire for real-time evaluation with the benets of architecture representation to produce an ontologically supported method of modelling, capturing and evaluating systemic behaviour. We produce a conceptual framework to performing this task, while avoiding the imprecise denitions of quality and quality attributes. According to our abstraction, transfering that responsibility to the end user is essencial since such aspects are subjective and depend on the human context in which they exist. This conceptualisation was materialised in a model-eval-display loop framework, and implemented using Model Driven Software Development practices and tools.
    [Show full text]
  • Unified Modeling Language (UML)
    Unified Modeling Language (UML) Troy Mockenhaupt Chi-Hang ( Alex) Lin Pejman ( PJ ) Yedidsion Overview Definition History Behavior Diagrams Interaction Diagrams Structural Diagrams Tools Effect on Software Engineering Definition A standard language for specifying, visualizing, and constructing software artifacts Non-restrictive Expressive and visual modeling language Independent of language and process History First modeling languages emerge 1970s “method wars” of the 1990s Methods began merging techniques 1994 – Booch and Rumbaugh unify Booch and Object Modeling Technique 1995-1996 Jacobson incorporates OOSE methods – term UML is coined 1997 – Object Management Group (OMG) accepted UML as standard History (cont.) UML 2.0 adopted in 2005 2.1.1 and 2.1.2 in 2007 ( never formally released ) UML 2.2 in 2009 UML 2.3 in 2010 UML 2.4.1 2011 UML 1.x vs 2.x 1.x vs 2.x Significant changes 1.x 2.x Activity Diagram Specialized form of Increasing the scope State Diagrams of usage Package Diagram Insufficient for large Added models Component Diagram No port and Added connectors Timing Diagram No syntax for timing Added purposes Behavior Diagrams ● Activity Diagram (basic program flow & capture decision points) ● Use Case Diagram (model user/system interactions) ● State Machine Diagram (“run state” of a model when it executes) Activity Diagram ● Shows the overall flow of control ● Comprises: choice, iteration, and concurrency ● Business and operational step-by-step workflows of components in a system ● A form of flowchart that
    [Show full text]
  • A UML Profile for Delta-Oriented Programming to Support Software
    A UML Profile for Delta-Oriented Programming to Support Software Product Line Engineering? Maya R. A. Setyautami1, Reiner Hähnle2, Radu Muschevici2, and Ade Azurat1 1 Fakultas Ilmu Komputer Universitas Indonesia Depok, Indonesia {mayaretno|ade}@cs.ui.ac.id 2 Department of Computer Science Technische Universität Darmstadt, Darmstadt, Germany {haehnle|radu}@cs.tu-darmstadt.de Abstract. Feature-based approaches to software design, like delta-ori- ented programming, are well-suited to support multi-product software development paradigms, such as Software Product Lines. Currently, the popular UML notation does not support delta-oriented software design, so that several ad-hoc notations tend to be used. This paper presents a systematic approach to import concepts from delta-oriented programming into the mainstream notation UML. This is done with minimal overhead by specifying a new, slim, delta-oriented UML profile. It is compatible with languages that support delta-oriented programming such as DeltaJ and ABS. The usefulness of the profile is evaluated with a case study. 1 Introduction The modeling of product variability—to identify and to manage the commonalities and differences among software products—is a key issue of any software product line (SPL) development process [14]. Variability modeling spans all phases of SPL development, from analyzing the problem by gathering requirements, to design and implementation of a solution in the form of software. Variability modeling is thus a concern in both the problem space and the solution space. In the problem space, variability is typically modeled by abstracting require- ments to features and describing dependencies between features in a feature model [10].
    [Show full text]
  • Product Support\Lifefitness\Treadmills
    1 2 YOU ARE CAUTIONED THAT ANY CHANGES OR MODIFICATIONS TO THIS EQUIPMENT COULD VOID YOUR PRODUCT WARRANTY. MISE EN GARDE : TOUTE MODIFICATION, TOUT CHANGEMENT APPORTÉS À L’APPAREIL PEUVENT ANNULER LA GARANTIE. Before using your Life Fitness 3500 treadmill, it is essential that you read this ENTIRE operation manual. It won’t take very long, and it will help you set up your Life Fitness 3500 aerobic trainer quickly and use it correctly. Avant d’utiliser l’exerciseur Life Fitness, il est nécesaire de lire le guide d’utilisa- tion COMPLÈTEMENT.. Il suffit de quelques instants pour apprendre à assembler et à utiliser correctement l’exerciseur aérobique Life Fitness. WARNING - To reduce the risk of burns, fire, electric shock, or injury to persons: • An appliance should never be left unattended when plugged in. Unplug from outlet when not in use. • To disconnect, turn all controls to the off position, then remove the plug from the outlet. • Connect this appliance to a properly grounded outlet only. See Grounding Instructions. MISE EN GARDE - Pour réduire les risques de brûlure, d’incendie, de secousse électrique ou de blessure: • Ne jamais laisser un appareil sans surveillance lorsqu’il est branché. Le débrancher s’il n’est pas utilisé. • Pour débrancher l’appareil, fermer tous les contrôles et retirer la fiche de la prise murale. • Brancher l’appareil dans une prise correctement mise à la terre. Se reporter- aus «Instructions de mise à la terre». 3 CORPORATE HEADQUARTERS 10601 West Belmont Avenue Franklin Park, Illinois 60131 U.S.A. (847) 288-3300 • FAX: (847) 288-3703 (800) 735-3867 (Toll-free within the U.S.
    [Show full text]
  • Introducing the Metamodel Views
    ENTERPRISE ARCHITECT User Guide Series Introducing the Metamodel Views Author: Sparx Systems Date: 2021-09-02 Version: 15.2 CREATED WITH Table of Contents Introducing the Metamodel Views 3 Built-in Metamodel Diagram View 5 Custom Metamodel Diagram View 9 Define Metamodel Constraints 15 Constraints on Meta-Constraint connector 20 Metamodel Constraints and the Quick Linker 27 Introducing the Metamodel Views 2 September, 2021 Introducing the Metamodel Views Enterprise Architect includes an extremely powerful and flexible system of Views of both system-defined and user-defined metamodels. The Views system provides highly focused diagrams that limit the number of elements and connections available to only the core required to achieve a specific task. For example, a Hierarchy View imposed on a Class diagram might limit the only element available to 'Class' and the only connector to 'Inheritance'. Using the Views system to guide the modeling palette and relationships available, you will build tight and purposeful diagrams that use only the required elements within the current modeling context. Cutting out the noise and reducing the set of constructs available is a great way of making sure a design is addressing the intended purpose and avoiding extraneous elements that might negatively impact the readability and correctness of the model. Metamodel Views Category Description System Enterprise Architect provides a wide range of built-in Metamodel Views that address numerous modeling scenarios and domains. Many of the Model Wizard patterns are pre-set with a Metamodel View, and the 'New Diagram' dialog includes many derivative diagram views that extend and refine the capabilities of the base diagram types.
    [Show full text]