DOCSLIB.ORG

Com.Telelogic.Rhapsody.Core

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Com.Telelogic.Rhapsody.Core com.telelogic.rhapsody.core Package Class Use Tree Serialized Deprecated Index Help PREV PACKAGE NEXT PACKAGE FRAMES NO FRAMES All Classes Package com.telelogic.rhapsody.core Interface Summary The IRPAcceptEventAction interface represents Accept Event IRPAcceptEventAction Action elements in a statechart or activity diagram. The IRPAcceptTimeEvent interface represents Accept Time Event IRPAcceptTimeEvent elements in activity diagrams and statecharts. The IRPAction interface represents the action defined for a IRPAction transition in a statechart. The IRPActionBlock interface represents action blocks in IRPActionBlock sequence diagrams. The IRPActivityDiagram interface represents activity diagrams in IRPActivityDiagram Rational Rhapsody models. IRPActor The IRPActor interface represents actors in Rhapsody models. The IRPAnnotation interface represents the different types of IRPAnnotation annotations you can add to your model - notes, comments, constraints, and requirements. The IRPApplication interface represents the Rhapsody application, IRPApplication and its methods reflect many of the commands that you can access from the Rhapsody menu bar. The IRPArgument interface represents an argument of an IRPArgument operation or an event. IRPASCIIFile The IRPAssociationClass interface represents association classes IRPAssociationClass in Rational Rhapsody models. The IRPAssociationRole interface represents the association roles IRPAssociationRole that link objects in communication diagrams. The IRPAttribute interface represents attributes of a class, and IRPAttribute global variables. IRPAXViewCtrl IRPBaseExternalCodeGeneratorTool The IRPCallOperation interface represents call operation elements IRPCallOperation in activity diagrams. The IRPClass interface represents classes in Rational Rhapsody IRPClass models. Package com.telelogic.rhapsody.core 1 com.telelogic.rhapsody.core Interface Summary Represents the features shared by elements such as classes, actors, IRPClassifier use cases, and types. The IRPClassifierRole interface represents lifelines in sequence IRPClassifierRole diagrams and "objects" (lifelines) in communication diagrams. IRPCodeGenerator IRPCodeGenSimplifiersRegistry The IRPCollaboration interface represents the capabilities included IRPCollaboration in sequence diagrams and communications diagrams. The IRPCollaborationDiagram interface represents collaboration IRPCollaborationDiagram diagrams in a Rational Rhapsody model. The IRPCollection interface contains methods used to store and IRPCollection manipulate collections of various types of elements that you may have in your Rational Rhapsody model. The IRPComment interface represents comments in a Rational IRPComment Rhapsody model. The IRPComponent interface represents a code generation IRPComponent component defined in a Rhapsody model. The IRPComponentDiagram interface represents component IRPComponentDiagram diagrams in Rational Rhapsody models. IRPComponentInstance The IRPConditionMark interface represents condition marks in IRPConditionMark sequence diagrams. The IRPConfiguration interface represents a code generation IRPConfiguration configuration within a specific component. The IRPConnector interface represents the characteristics shared by the various types of "connector" elements that can be included IRPConnector in a statechart, such as condition connectors, history connectors, join sync bar connectors, and fork sync bar connectors. The IRPConstraint interface represents constraints in a Rational IRPConstraint Rhapsody model. The IRPContextSpecification interface represents the exact context IRPContextSpecification of an object in a hierarchy. The IRPControlledFile interface represents a controlled file in a IRPControlledFile Rhapsody model. The IRPDependency interface represents dependencies in a IRPDependency Rational Rhapsody model. The IRPDeploymentDiagram interface represents deployment IRPDeploymentDiagram diagrams in Rational Rhapsody models. Package com.telelogic.rhapsody.core 2 com.telelogic.rhapsody.core Interface Summary The IRPDestructionEvent interface represents destruction events IRPDestructionEvent in sequence diagrams. The IRPDiagram interface contains the methods shared by all the IRPDiagram interfaces that represent specific types of diagrams. IRPDiagSynthAPI IRPEnumerationLiteral The IRPEvent interface represents events in Rational Rhapsody IRPEvent models. IRPEventReception IRPExecutionOccurrence IRPExternalCheckRegistry IRPExternalCodeGeneratorInvoker IRPExternalIDERegistry IRPExternalRoundtripInvoker The IRPFile interface represents a file or folder to be generated IRPFile during code generation. IRPFileFragment IRPFlow The IRPFlowchart interface represents activities in Rational IRPFlowchart Rhapsody models. The IRPFlowItem interface represents item flows in Rational IRPFlowItem Rhapsody models. IRPGeneralization IRPGraphEdge IRPGraphElement IRPGraphicalProperty IRPGraphNode IRPGuard The IRPHyperLink interface represents hyperlinks in Rational IRPHyperLink Rhapsody models. IRPImageMap IRPInstance IRPInstanceSlot IRPInstanceSpecification Package com.telelogic.rhapsody.core 3 com.telelogic.rhapsody.core Interface Summary The IRPInstanceValue interface is used in contexts where a single IRPInstanceValue model element must be stored. IRPIntegrator IRPInteractionOccurrence The IRPInteractionOperand interface represents interaction IRPInteractionOperand operands in Rational Rhapsody models. IRPInteractionOperator The IRPInterfaceItem interface represents the features shared by IRPInterfaceItem operations, events, and event receptions in Rational Rhapsody models. IRPInternalOEMPlugin IRPJavaPlugins The IRPLink interface represents links in Rational Rhapsody IRPLink models. The IRPLiteralSpecification interface is used in contexts where a IRPLiteralSpecification single value must be stored. IRPMatrixLayout The IRPMatrixView interface represents Matrix View elements in IRPMatrixView Rhapsody models. IRPMessage IRPMessagePoint The IRPModelElement interface represents an element in a IRPModelElement Rational Rhapsody model, and its methods reflect the behavior shared by the various types of model elements. IRPModule IRPNode The IRPObjectModelDiagram interface represents object model IRPObjectModelDiagram diagrams in Rational Rhapsody models. The IRPObjectNode interface represents Object Node elements in IRPObjectNode activity diagrams. The IRPOperation interface represents operations of classes in IRPOperation Rational Rhapsody models. IRPowListListener IRPowPaneMgr IRPowTextListener IRPPackage Package com.telelogic.rhapsody.core 4 com.telelogic.rhapsody.core Interface Summary The IRPPackage interface represents packages in Rhapsody models. The IRPPanelDiagram interface represents panel diagrams in IRPPanelDiagram Rational Rhapsody models. The IRPPin interface represents action pins added to actions, or IRPPin activity parameters added to action blocks, in an activity diagram. IRPPlugInWindow The IRPPort interface represents ports in Rational Rhapsody IRPPort models. The IRPProfile interface represents profiles in Rational Rhapsody IRPProfile models. IRPProgressBar IRPProject The IRPProject interface represents Rational Rhapsody projects. IRPRelation Represents a relationship between two classes. The IRPRequirement interface represents requirements in a IRPRequirement Rational Rhapsody model. IRPRhapsodyServer IRPRoundTrip IRPSearchManager is used to carry out a search in a Rhapsody IRPSearchManager model. The IRPSearchQuery interface represents the search criteria IRPSearchQuery objects that are used by IRPSearchManager to carry out searches. IRPSearchResult The IRPSelection interface contains methods for cutting, copying, IRPSelection pasting, and deleting graphic elements on diagrams. The IRPSendAction interface represents Send Action elements in IRPSendAction an activity or statechart. The IRPSequenceDiagram interface represents sequence diagrams IRPSequenceDiagram in a Rational Rhapsody model. IRPState The IRPState interface represents states in a statechart. The IRPStatechart interface represents the statechart elements IRPStatechart underlying a statechart. The IRPStatechartDiagram interface represents statecharts in a IRPStatechartDiagram Rational Rhapsody model. The IRPStateVertex interface represents the characteristics that are IRPStateVertex shared by various statechart elements such as states, join/fork connectors, and condition connectors. Package com.telelogic.rhapsody.core 5 com.telelogic.rhapsody.core Interface Summary The IRPStereotype interface represents sterotypes in Rational IRPStereotype Rhapsody models. The IRPStructureDiagram interface represents structure diagrams IRPStructureDiagram in a Rational Rhapsody model. The IRPSwimlane interface represents swimlanes in an activity IRPSwimlane diagram. The IRPSysMLPort interface represents flowport elements in IRPSysMLPort Rhapsody models. IRPTableLayout The IRPTableView interface represents Table View elements in IRPTableView Rhapsody models. The IRPTag interface represents tags in a Rational Rhapsody IRPTag model. IRPTemplateInstantiation IRPTemplateInstantiationParameter The IRPTemplateParameter interface represents parameters of a IRPTemplateParameter template in Rational Rhapsody models. IRPTimingDiagram IRPTransition The IRPTransition interface represents transitions in a statechart. The IRPTrigger interface represents the trigger of a transition in a IRPTrigger statechart. IRPType The IRPUnit interface represents model elements that can be saved IRPUnit as
Load more

Recommended publications
  • 07 Requirements What About RFP/RFB/Rfis?
    CMPSCI520/620 07 Requirements & UML Intro 07 Requirements SW Requirements Specification • Readings • How do we communicate the Requirements to others? • [cK99] Cris Kobryn, Co-Chair, “Introduction to UML: Structural and Use Case Modeling,” UML Revision Task Force Object Modeling with OMG UML Tutorial • It is common practice to capture them in an SRS Series © 1999-2001 OMG and Contributors: Crossmeta, EDS, IBM, Enea Data, • But an SRS doesn’t need to be a single paper document Hewlett-Packard, IntelliCorp, Kabira Technologies, Klasse Objecten, Rational Software, Telelogic, Unisys http://www.omg.org/technology/uml/uml_tutorial.htm • Purpose • [OSBB99] Gunnar Övergaard, Bran Selic, Conrad Bock and Morgan Björkande, “Behavioral Modeling,” UML Revision Task Force, Object Modeling with OMG UML • Contractual requirements Tutorial Series © 1999-2001 OMG and Contributors: Crossmeta, EDS, IBM, Enea elicitation Data, Hewlett-Packard, IntelliCorp, Kabira Technologies, Klasse Objecten, Rational • Baseline Software, Telelogic, Unisys http://www.omg.org/technology/uml/uml_tutorial.htm • for evaluating subsequent products • [laM01] Maciaszek, L.A. (2001): Requirements Analysis and System Design. • for change control requirements Developing Information Systems with UML, Addison Wesley Copyright © 2000 by analysis Addison Wesley • Audience • [cB04] Bock, Conrad, Advanced Analysis and Design with UML • Users, Purchasers requirements http://www.kabira.com/bock/ specification • [rM02] Miller, Randy, “Practical UML: A hands-on introduction for developers,”
    [Show full text]
  • Communication Diagram.Pdf
    TU2943: Information Engineering Methodology Lab Notes, 2009-2010, Faculty of Technology and Information Science, Universiti Kebangsaan Malaysia LAB 5: Interaction Diagram - UML Communication Diagram OBJECTIVES To understand the role of dynamic models in requirement analysis by reading and constructing UML Communication Diagram. INTRODUCTION Communication Diagram (a.k.a. Collaboration Diagram) Communication Diagram provides another way to model a scenario. Essentially is a part of Interaction Diagram (just like Sequence Diagram). Each object is represented by an object icon, and links are used to indicate communication paths on which messages are transmitted. Messages presented in the same way as those in sequence diagram. Formerly known as Collaboration Diagram in UML 1.x specification. Communication Diagram represents a combination of information taken from Use Case, Class and Sequence Diagrams describing both the static structure and dynamic behavior of the system. Comparing and Contrasting: Collaboration and Sequence Both diagrams show the same information: Objects/classes Messages Sequence Conditional Repetition Messages to self Sequence Diagram and Communication Diagram are two views of the same scenario. Collaboration diagrams emphasize who-is-talking-to-who. But the time-ordering of the messages who gets obscured. Sequence diagrams emphasize time-ordering. But the who-is-talking-to-who gets obscured. Use the diagram that you are most comfortable with. Structure and Notation of Communication Diagram Objects are named <an object name>:< its class> . Nor Samsiah Binti Sani 1 TU2943: Information Engineering Methodology Lab Notes, 2009-2010, Faculty of Technology and Information Science, Universiti Kebangsaan Malaysia Either <an object name> or <a class name> can be removed. Collaborations / communications are shown by lines between objects.
    [Show full text]
  • Uml.Sty, a Package for Writing UML Diagrams in LATEX
    uml.sty, a package for writing UML diagrams in LATEX Ellef Fange Gjelstad March 17, 2010 Contents 1 Syntax for all the commands 5 1.1 Lengths ........................................ 5 1.2 Angles......................................... 5 1.3 Nodenames...................................... 6 1.4 Referencepoints ................................. 6 1.5 Colors ......................................... 6 1.6 Linestyles...................................... 6 2 uml.sty options 6 2.1 debug ......................................... 6 2.2 index.......................................... 6 3 Object-oriented approach 7 3.1 Colors ......................................... 10 3.2 Positions....................................... 10 4 Drawable 12 4.1 Namedoptions .................................... 12 4.1.1 import..................................... 12 5 Element 12 5.1 Namedoptions .................................... 12 5.1.1 Reference ................................... 12 5.1.2 Stereotype................................... 12 5.1.3 Subof ..................................... 13 5.1.4 ImportedFrom ................................ 13 5.1.5 Comment ................................... 13 6 Box 13 6.1 Namedoptionsconcerninglocation . ....... 13 6.2 Boxesintext ..................................... 14 6.3 Named options concerning visual appearance . ......... 14 6.3.1 grayness.................................... 14 6.3.2 border..................................... 14 1 6.3.3 borderLine .................................. 14 6.3.4 innerBorder.................................
    [Show full text]
  • Blurred Lines Between Role and Reality: a Phenomenological Study of Acting
    Antioch University AURA - Antioch University Repository and Archive Student & Alumni Scholarship, including Dissertations & Theses Dissertations & Theses 2019 Blurred Lines Between Role and Reality: A Phenomenological Study of Acting Gregory Hyppolyte Brown Follow this and additional works at: https://aura.antioch.edu/etds Part of the Psychology Commons BLURRED LINES BETWEEN ROLE AND REALITY: A PHENOMENOLOGICAL STUDY OF ACTING A Dissertation Presented to the Faculty of Antioch University Santa Barbara In partial fulfillment of the requirements for the the degree of DOCTOR OF PSYCHOLOGY In CLINICAL PSYCHOLOGY by GREGORY HIPPOLYTE BROWN August 2019 This dissertation, by Gregory Hippolyte Brown, has been approved by the committee members signed below who recommend that it be accepted by the faculty of Antioch University Santa Barbara in partial fulfillment of requirements for the degree of DOCTOR OF PSYCHOLOGY Dissertation Committee: _________________________ Brett Kia-Keating, Ed.D. Chairperson __________________________ Sharleen O‘ Brien, Ph.D. Second Faculty __________________________ Thalia R. Goldstein, Ph.D. External Expert ii Copyright © 2019 Gregory Hippolyte Brown iii Abstract When an actor plays a character in a film, they try to connect with the emotions and behavioral patterns of the scripted character. There is an absence of literature regarding how a role influences an actor’s life before, during, and after film production. This study examined how acting roles might influence an actor during times on set shooting a movie or television series as well as their personal life after the filming is finished. Additionally the study considered the psychological impact of embodying a role, and whether or not an actor ever has the feeling that the performed character has independent agency over the actor.
    [Show full text]
  • Customizing UML with Stereotypes
    Customizing UML with Stereotypes Mirosáaw StaroĔ ii iii Blekinge Institute of Technology Dissertation Series No 2003:06 ISSN 1650-2140 ISBN 91-7295-028-5 Customizing UML with Stereotypes Mirosáaw StaroĔ Department of Software Engineering and Computer Science Blekinge Institute of Technology Sweden iv BLEKINGE INSTITUTE OF TECHNOLOGY Blekinge Institute of Technology, situated on the southeast coast of Sweden, started in 1989 and in 1999 gained the right to run Ph.D programmes in technology. Research programmes have been started in the following areas: • Applied signal processing • Computer science • Computer systems technology • Design and digital media • Human work science with a special focus on IT • IT and gender research • Mechanical engineering • Software engineering • Spatial planning • Telecommunication systems Research studies are carried out in all faculties and about a third of the annual budget is dedicated to research. Blekinge Institute of Technology S-371 79 Karlskrona, Sweden http://www.bth.se v Jacket illustration: © 2003 GillWorth gallery, www.gillworthreptiles.co.uk Publisher: Blekinge Institute of Technology Printed by Kaserntryckeriet, Karlskrona, Sweden 2003 ISBN 91-7295-028-5 vi Abstract The Unified Modeling Language (UML) is a visual modeling language for documenting and specifying software. It is gaining popularity as a language for a variety of purposes. It was designed as a result of a unifying activity in the last decade. Since this general purpose language cannot suit all possible needs, it has built-in mechanisms for providing extensibility for specific purposes. One such mechanism is the notion of stereotype, which is a means of branding the existing model element with a new semantics.
    [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]
  • VI. the Unified Modeling Language UML Diagrams
    Conceptual Modeling CSC2507 VI. The Unified Modeling Language Use Case Diagrams Class Diagrams Attributes, Operations and ConstraintsConstraints Generalization and Aggregation Sequence and Collaboration Diagrams State and Activity Diagrams 2004 John Mylopoulos UML -- 1 Conceptual Modeling CSC2507 UML Diagrams I UML was conceived as a language for modeling software. Since this includes requirements, UML supports world modeling (...at least to some extend). I UML offers a variety of diagrammatic notations for modeling static and dynamic aspects of an application. I The list of notations includes use case diagrams, class diagrams, interaction diagrams -- describe sequences of events, package diagrams, activity diagrams, state diagrams, …more... 2004 John Mylopoulos UML -- 2 Conceptual Modeling CSC2507 Use Case Diagrams I A use case [Jacobson92] represents “typical use scenaria” for an object being modeled. I Modeling objects in terms of use cases is consistent with Cognitive Science theories which claim that every object has obvious suggestive uses (or affordances) because of its shape or other properties. For example, Glass is for looking through (...or breaking) Cardboard is for writing on... Radio buttons are for pushing or turning… Icons are for clicking… Door handles are for pulling, bars are for pushing… I Use cases offer a notation for building a coarse-grain, first sketch model of an object, or a process. 2004 John Mylopoulos UML -- 3 Conceptual Modeling CSC2507 Use Cases for a Meeting Scheduling System Initiator Participant
    [Show full text]
  • Rational Rhapsody Frameworks and Operating Systems Reference
    Rational Rhapsody Frameworks and Operating Systems Reference Before using the information in this manual, be sure to read the “Notices” section of the Help or the PDF available from Help > List of Books. This edition applies to IBM® Rational® Rhapsody® 7.5 and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright IBM Corporation 1997, 2009. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. ii Contents Frameworks and Operating Systems . 1 Real-Time Frameworks . 1 Rational Rhapsody Statecharts . 2 The Object Execution Framework (OXF). 3 Working with the Object Execution Framework . 3 The OXF Library. 4 Rational Rhapsody Applications and the RTOS. 5 Operating System Abstraction Layer (OSAL). 5 Threads . 7 Stack Size . 7 Synchronization Services . 8 Message Queues . 8 Communication Port. 9 Timer Service . 10 Real-time Operating System (RTOS) . 11 AbstractLayer Package (OSAL) . 11 Classes . 12 OSWrappers Package . 12 Adapting Rational Rhapsody for a New RTOS . 13 Run-Time Sources . 13 Adding the New Adapter . 13 Creating the Batch File and Makefiles. 14 Sample <env>build.mak File . 15 Creating New Makefiles . 16 OXF Versions . 16 Animation Libraries. 16 Implementing the Adapter Classes . 18 Modifying rawtypes.h . 19 Other Operating System-Related Modifications . 19 Building the Framework Libraries . 20 Rational Rhapsody i Table of Contents Building the C or C++ Framework for Windows Systems . 20 Building the Ada Framework . 21 Building the Java Framework . 22 Building the Framework for Solaris Systems . 22 Creating Properties for a New RTOS . .24 Modifying the site<lang>.prp Files .
    [Show full text]
  • Justice XML Data Model Technical Overview
    Justice XML Data Model Technical Overview April 2003 WhyWhy JusticeJustice XMLXML DataData ModelModel VersionVersion 3.0?3.0? • Aligned with standards (some were not available to RDD) • Model-based Æ consistent • Requirements-based – data elements, processes, and documents • Object-oriented Æ efficient extension and reuse • Expanded domain (courts, corrections, and juvenile) • Extensions to activity objects/processes • Relationships (to improve exchange information context) • Can evolve/advance with emerging technology (RDF/OWL) • Model provides the basis for an XML component registry that can provide • Searching/browsing components and metadata • Assistance for schema development/generation • Reference/cache XML schemas for validation • Interface (via standard specs) to external XML registries April 2003 DesignDesign PrinciplesPrinciples • Design and synthesize a common set of reusable, extensible data components for a Justice XML Data Dictionary (JXDD) that facilitates standard information exchange in XML. • Generalize JXDD for the justice and public safety communities – do NOT target specific applications. • Provide reference-able schema components primarily for schema developers. • JXDD and schema will evolve and, therefore, facilitate change and extension. • Best extension methods should minimize impact on prior schema and code investments. • Implement and represent domain relationships so they are globally understood. • Technical dependencies in requirements, solutions, and the time constraints of national priorities and demands
    [Show full text]
  • Object Query Language Reference Version: Itop 1.0
    Object Query Language Reference Version: Itop 1.0 Overview OQL aims at defining a subset of the data in a natural language, while hiding the complexity of the data model and benefit of the power of the object model (encapsulation, inheritance). Its syntax sticks to the syntax of SQL, and its grammar is a subset of SQL. As of now, only SELECT statements have been implemented. Such a statement do return objects of the expected class. The result will be used by programmatic means (to develop an API like ITOp). A famous example: the library Starter SELECT Book Do return any book existing in the Database. No need to specify the expected columns as we would do in a SQL SELECT clause: OQL do return plain objects. Join classes together I would like to list all books written by someone whose name starts with `Camus' SELECT Book JOIN Artist ON Book.written_by = Artist.id WHERE Artist.name LIKE 'Camus%' Note that there is no need to specify wether the JOIN is an INNER JOIN, or LEFT JOIN. This is well-known in the data model. The OQL engine will in turn create a SQL queries based on the relevant option, but we do not want to care about it, do we? © Combodo 2010 1 Now, you may consider that the name of the author of a book is of importance. This is the case if should be displayed anytime you will list a set of books, or if it is an important key to search for. Then you have the option to change the data model, and define the name of the author as an external field.
    [Show full text]
  • Unified Modeling Language 2.0 Part 1 - Introduction
    UML 2.0 – Tutorial (v4) 1 Unified Modeling Language 2.0 Part 1 - Introduction Prof. Dr. Harald Störrle Dr. Alexander Knapp University of Innsbruck University of Munich mgm technology partners (c) 2005-2006, Dr. H. Störrle, Dr. A. Knapp UML 2.0 – Tutorial (v4) 2 1 - Introduction History and Predecessors • The UML is the “lingua franca” of software engineering. • It subsumes, integrates and consolidates most predecessors. • Through the network effect, UML has a much broader spread and much better support (tools, books, trainings etc.) than other notations. • The transition from UML 1.x to UML 2.0 has – resolved a great number of issues; – introduced many new concepts and notations (often feebly defined); – overhauled and improved the internal structure completely. • While UML 2.0 still has many problems, current version (“the standard”) it is much better than what we ever had formal/05-07-04 of August ‘05 before. (c) 2005-2006, Dr. H. Störrle, Dr. A. Knapp UML 2.0 – Tutorial (v4) 3 1 - Introduction Usage Scenarios • UML has not been designed for specific, limited usages. • There is currently no consensus on the role of the UML: – Some see UML only as tool for sketching class diagrams representing Java programs. – Some believe that UML is “the prototype of the next generation of programming languages”. • UML is a really a system of languages (“notations”, “diagram types”) each of which may be used in a number of different situations. • UML is applicable for a multitude of purposes, during all phases of the software lifecycle, and for all sizes of systems - to varying degrees.
    [Show full text]
  • Artifact-Centric Modeling of Business Processes Using UML Diagrams
    Proceedings of The 20th World Multi-Conference on Systemics, Cybernetics and Informatics (WMSCI 2016) Artifact-Centric Modeling of Business Processes Using UML Diagrams David Grünert, Thomas Keller, and Elke Brucker-Kley ZHAW School of Management and Law Institute of Business Information Technology 8401 Winterthur, Switzerland {grud, kell, brck}@zhaw.ch Abstract and hidden in the process model. Accordingly, the positioning of information at the center of modeling was termed data- or infor- The modeling of business processes to date has focused on an mation-centric process modeling [2], [3], [4], [5]. Information activity-based perspective while business artifacts associated with entities are modeled by state charts. Transitions are triggered by the process have been modeled on an abstract and informal level. activities. Associated roles are defined by means of use case Ad hoc, dynamic business processes have recently emerged as a diagrams. In [5], the term opportunistic BPM (oBPM) was intro- requirement. Subsequently, BPMN was extended with ad hoc duced for this kind of approach. The duality between activity- sub-processes and a new standard, Case Management Modeling and information-centric models was shown in [6]. and Notation (CMMN), has been created by the Object Manage- Many artifact-centric approaches defined new or extended model ment Group (OMG). CMMN has an information-centric ap- syntax [6]. However, a new or extended modeling syntax increas- proach, whereas the extension of BPMN adheres to an activity- es complexity for all parties involved in designing, reading, and based perspective. The focus on BPMN and on processes in gen- implementing the modeled process and requires adapted model- eral has caused UML to fade into the background.
    [Show full text]