DOCSLIB.ORG

A Model Driven Approach for Service Based System Design Using Interaction Templates

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
A Model Driven Approach for Service Based System Design Using Interaction Templates Toni Reichelt A Model Driven Approach for Service Based System Design Using Interaction Templates Wissenschaftliche Schriftenreihe EINGEBETTETE, SELBSTORGANISIERENDE SYSTEME Band 10 Prof. Dr. Wolfram Hardt (Hrsg.) Toni Reichelt A Model Driven Approach for Service Based System Design Using Interaction Templates Chemnitz University Press 2012 Impressum Bibliografische Information der Deutschen Nationalbibliothek Die Deutsche Nationalbibliothek verzeichnet diese Publikation in der Deutschen Nationalbibliografie; detaillierte bibliografische Angaben sind im Internet über http://dnb.d-nb.de abrufbar. Zugl.: Chemnitz, Techn. Univ., Diss., 2012 Technische Universität Chemnitz/Universitätsbibliothek Universitätsverlag Chemnitz 09107 Chemnitz http://www.bibliothek.tu-chemnitz.de/UniVerlag/ Herstellung und Auslieferung Verlagshaus Monsenstein und Vannerdat OHG Am Hawerkamp 31 48155 Münster http://www.mv-verlag.de ISBN 978-3-941003-60-6 URL: http://nbn-resolving.de/urn:nbn:de:bsz:ch1-qucosa-85986 Preface to the scientific series “Eingebettete, selbstorganisierende Systeme” The tenth volume of the scientific series Eingebettete, selbstorganisierende Systeme (Em- bedded, self-organised systems) devotes itself to the model driven design of service-oriented systems. Fields of application for such systems, amongst others, range from large scale, distributed enterprise solutions down to modularised embedded systems. The presented work was moti- vated by the complex design process of avionics for unmanned systems, where the increased demand for enhanced system autonomy implies high levels of system collaboration and infor- mation exchange. For such system designs a clear separation between the application logic implemented by system components, the means of interaction between them and finally the realisation of such communication on target platforms is essential. In particular, this sep- aration leads to simplification of the complex design processes and increases the individual components’ re-use potential. With the presented work, Dr. Reichelt provides a holistic model driven design process for such systems. The design of service oriented systems and their target platform independent modelling with respect to component interaction stay in the focus of his work. The concrete semantics of individual interactions are condensed into interaction templates collected in an extensible model library. In turn, this library then provides the building blocks for service and system modelling by means of template instantiation. Dr. Reichelt reflects his formal concepts in a comprehensive UML profile and presents an encapsulating design process. This new design process is validated with a representative case study based on a prototyped tooling environment comprising model transformation and code generation techniques. I am glad that Dr. Reichelt publishes his research in this scientific series and wish you an interesting insight to the field of model driven design of service-oriented systems. Prof. Dr. Wolfram Hardt Chair of Computer Engineering Dean of the Faculty of Computer Science Scientific Director of Computing Center Chemnitz University of Technology, Germany April 2012 A Model Driven Approach for Service Based System Design Using Interaction Templates Dissertation Submitted in partial fulfilment of the requirements for the degree of Doktoringenieur (Dr.-Ing.) presented to the Faculty of Computer Science Chemnitz University of Technology Submitted by Toni Reichelt Assessor: Prof. Dr. Wolfram Hardt Prof. Dr.-Ing. Martin Gaedke Acknowledgements This thesis would not exist without the extensive support and encouragement by many people. First of all I am grateful to my mentor Prof. Dr. Wolfram Hardt who supported me in pursuing a PhD degree. Within fruitful discussions he helped shaping and organising many of the ideas of this thesis. And as this thesis was prepared in an industrial environment I am especially thankful because he always welcomed me in academia and allowed me to stay in touch with the scientific world. I would also like to thank Prof. Dr.-Ing. Martin Gaedke for his interest in this thesis and very constructive feedback in structuring and improving the presented work. It is an honour for me to thank some personal friends with whom I had the pleasure to work with at Cassidian. In particular I am indebted to Dr. André Windisch and Dr. Norbert Oswald. André, thank you for introducing me to Cassidian and the world of avionics. Norbert, I am thankful for given me the opportunity to join the EPAS (Engineering Platform for Autonomous Systems) team which provided an ideal framework for developing my ideas and test driving solution concepts. Also, I thank my friends Dr.-Ing. Stefan Förster and Herwig Moser for their almost end- less willingness to discuss many ideas compiled into this work as well as proof-reading and commenting on its final version. Finally, I would also like to thank my family, especially my wife Conny. Without their continous support this work would not have been possible. Thank you. Toni Reichelt Munich, August, 2011 i ii Abstract Based on the increasing complexity of modern avionics, the associated system design pro- cesses moved towards Model Driven Architecture (MDA) based processes. Additionally, the demand for higher system autonomy features requires means to further modularise mission systems and to define and establish interactions among the systems’ individual components. Therefore, the ideas of service-oriented computing are currently adapted to established, model driven design processes. With respect to modelling interactions for service com- ponents, current approaches are limited to only a fixed set of communication primitives, restricting a service designer’s expressiveness to specify service interaction. In consequence, interaction patterns not included in this basic set have to be reflected in application code, mangling application and communication logic. Furthermore, when service functionality relies on communication semantics which are not provided by the underlying set of prim- itives, additional emulation behaviour has to be added to the service which makes this mangling even worse. Platform independence is reduced as services can not easily be ported to platforms not natively supporting the selected primitives which contradicts the ideas of model-driven development. Addressing these limitations, this thesis proposes a new model-driven service development process based on Interaction Templates (ITs), promoting interactions among service partic- ipants to first class modelling entities. The process focuses on modelling the interactions among service participants. Interaction semantics are explicitly specified in models, be- yond pure stereotyping, and gain increased platform independence for services with respect to communication. The process exploits automated Model-to-Model (M2M ) and Model-to- Text (M2T) transformations to assist service implementation and to automatically derive interaction realisations on concrete target platforms. This allows for easy replacement and inter-mixing of communication middleware to realise a service’s interactions. This way, ser- vices become independent of the underlying communication primitives by only relying on ITs and not platform primitives which are hidden behind ITs. In turn, realising ITs on concrete platforms is not affected by their utilisation for service interaction. Beside the novel modelling process itself, the presented work defines a Unified Modeling Language (UML) profile, referred to as UML Profile for Interaction-centric Services (UP4IS), which directly supports the adaptation of standard UML language constructs and tools for the proposed modelling approach. The whole development process is demonstrated via the iii specification of a simple video recording systems consisting of two services. The services themselves are based on a representative IT library which forms an essential part of the presented case study. Using these service and IT models, the thesis emphasises the necessary model transformation and code generation steps to derive service implementations based on the abstract models. iv Contents Abstract iii Contents v List of Tables xi List of Figures xiii List of Listings xvii List of Acronyms xix 1 Introduction 1 1.1 Motivation and Application Context . .1 1.2 Problem Description . .2 1.3 Solution Requirements and Contributions . .4 1.4 Outline . .5 I Foundations 7 2 Related Work 9 2.1 Modelling Service Oriented Systems . .9 2.1.1 Formal Frameworks . .9 2.1.2 Architectural Frameworks . 12 2.1.3 Modelling Services with UML . 13 2.1.4 Discussion . 15 2.2 Service Interactions . 15 2.2.1 Interaction Patterns . 15 2.2.2 Catalogues for Service Interaction . 17 2.2.3 Modelling Service Interactions . 17 2.2.4 Service Adaptors . 19 v Contents 2.2.5 Discussion . 21 2.3 Discussion . 21 3 Model Driven Architecture 23 3.1 Methodology . 23 3.2 The Model in the Model Driven Architecture . 24 3.2.1 The Modelling Hierarchy . 24 3.2.2 Platform Independence of Models . 25 3.3 Model Transformations . 26 3.3.1 Source and Target Models . 27 3.3.2 Transformation Strategies . 28 3.3.3 Transformation Languages . 29 4 The Unified Modeling Language 33 4.1 Component Diagram . 33 4.1.1 Description . 33 4.1.2 Visualisation . 33 4.2 Composite Structure Diagram . 35 4.2.1 Description . 35 4.2.2 Visualisation . 36 4.3 Collaboration Diagram . 36 4.3.1 Description . 36 4.3.2 Visualisation . 38 4.4 Sequence Diagrams . 38 4.4.1 Description . 38 4.4.2 Visualisation . 41 4.4.3 Relation to Message
Load more

Recommended publications
  • 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]
  • Model-Driven Engineering, the System Under Development Is Described and Analyzed Using Models
    X perf =1.00 X loss =0.01 SDSoftware Design and Quality A Declarative Language for Bidirectional Model Consistency Master’s Thesis of Dominik Werle at the Department of Informatics Institute for Program Structures and Data Organization (IPD) Reviewer: Prof. Dr. Ralf H. Reussner Second reviewer: Jun.-Prof. Dr.-Ing. Anne Koziolek Advisor: Dipl.-Inform. Max E. Kramer Second advisor: M.Sc. Michael Langhammer 09. October 2015 – 08. April 2016 Karlsruher Institut für Technologie Fakultät für Informatik Postfach 6980 76128 Karlsruhe I declare that I have developed and written the enclosed thesis completely by myself, and have not used sources or means without declaration in the text. Karlsruhe, 08. April 2016 .................................... (Dominik Werle) Abstract In model-driven engineering, the system under development is described and analyzed using models. Dierent models provide dierent abstractions of the system for dierent purposes. If multiple modeling languages are used, their models can contain overlapping informa- tion about the system. Then, they can become inconsistent after changes and need to be synchronized. The complexity of synchronizing models can be reduced by specifying consistency relationships in specialized languages and by automating the synchronization based on this specication. The languages can hide complexity that is not specic to the domain of the modeling languages, for example by deriving the operations needed for propagating changes from a model to another model for all pairs of models instead of requiring explicit specication for each pair and direction. In the course of this thesis, we designed the mapping language for specifying these consistency relationships and implemented a framework that maintains consistency based on the specication.
    [Show full text]
  • Chicago Board Options Exchange Annual Report 2001
    01 Chicago Board Options Exchange Annual Report 2001 cv2 CBOE ‘01 01010101010101010 01010101010101010 01010101010101010 01010101010101010 01010101010101010 CBOE is the largest and 01010101010101010most successful options 01010101010101010marketplace in the world. 01010101010101010 01010101010101010 01010101010101010 01010101010101010 01010101010101010 01010101010101010ifc1 CBOE ‘01 ONE HAS OPPORTUNITIES The NUMBER ONE Options Exchange provides customers with a wide selection of products to achieve their unique investment goals. ONE HAS RESPONSIBILITIES The NUMBER ONE Options Exchange is responsible for representing the interests of its members and customers. Whether testifying before Congress, commenting on proposed legislation or working with the Securities and Exchange Commission on finalizing regulations, the CBOE weighs in on behalf of options users everywhere. As an advocate for informed investing, CBOE offers a wide array of educational vehicles, all targeted at educating investors about the use of options as an effective risk management tool. ONE HAS RESOURCES The NUMBER ONE Options Exchange offers a wide variety of resources beginning with a large community of traders who are the most experienced, highly-skilled, well-capitalized liquidity providers in the options arena. In addition, CBOE has a unique, sophisticated hybrid trading floor that facilitates efficient trading. 01 CBOE ‘01 2 CBOE ‘01 “ TO BE THE LEADING MARKETPLACE FOR FINANCIAL DERIVATIVE PRODUCTS, WITH FAIR AND EFFICIENT MARKETS CHARACTERIZED BY DEPTH, LIQUIDITY AND BEST EXECUTION OF PARTICIPANT ORDERS.” CBOE MISSION LETTER FROM THE OFFICE OF THE CHAIRMAN Unprecedented challenges and a need for strategic agility characterized a positive but demanding year in the overall options marketplace. The Chicago Board Options Exchange ® (CBOE®) enjoyed a record-breaking fiscal year, with a 2.2% growth in contracts traded when compared to Fiscal Year 2000, also a record-breaker.
    [Show full text]
  • A Model-Driven Engineering Approach to Support the Verification of Compliance to Safety Standards
    A Model-Driven Engineering Approach to Support the Verification of Compliance to Safety Standards Rajwinder Kaur Panesar-Walawege, Mehrdad Sabetzadeh, Lionel Briand Simula Research Laboratory, Lysaker, Norway University of Oslo, Norway Email: {rpanesar,mehrdad,briand}@simula.no Abstract—Certification of safety-critical systems according to system development. This means that they will have to well-recognised standards is the norm in many industries where reconstruct the missing evidence after the fact. Doing so the failure of such systems can harm people or the environment. is often very expensive, and the outcomes might be far Certification bodies examine such systems, based on evidence that the system suppliers provide, to ensure that the relevant from satisfactory. On the certifier side, poorly structured and safety risks have been sufficiently mitigated. The evidence is incomplete evidence often leads to significant delays and aimed at satisfying the requirements of the standards used loss of productivity, and further may not allow the certifier for certification, and naturally a key prerequisite for effective to develop enough trust in the system that needs to be collection of evidence is that the supplier be aware of these certified. It is therefore very important to devise a systematic requirements and the evidence they require. This often proves to be a very challenging task because of the sheer size of the methodology, which is amenable to effective automated standards and the fact that the textual standards are amenable support, to specify, manage, and analyze the safety evidence to subjective interpretation. In this paper, we propose an ap- used to demonstrate compliance to standards.
    [Show full text]
  • UML Notation Guide 3
    UML Notation Guide 3 This guide describes the notation for the visual representation of the Unified Modeling Language (UML). This notation document contains brief summaries of the semantics of UML constructs, but the UML Semantics chapter must be consulted for full details. Contents This chapter contains the following topics. Topic Page “Part 1 - Background” “Introduction” 3-5 Part 2 - Diagram Elements “Graphs and Their Contents” 3-6 “Drawing Paths” 3-7 “Invisible Hyperlinks and the Role of Tools” 3-7 “Background Information” 3-8 “String” 3-8 “Name” 3-9 “Label” 3-10 “Keywords” 3-11 “Expression” 3-11 “Type-Instance Correspondence” 3-14 Part 3 - Model Management March 2003 OMG-Unified Modeling Language, v1.5 3-1 3 UML Notation Guide Topic Page “Package” 3-16 “Subsystem” 3-19 “Model” 3-24 Part 4 - General Extension Mechanisms “Constraint and Comment” 3-26 “Element Properties” 3-29 “Stereotypes” 3-31 Part 5 - Static Structure Diagrams “Class Diagram” 3-34 “Object Diagram” 3-35 “Classifier” 3-35 “Class” 3-35 “Name Compartment” 3-38 “List Compartment” 3-38 “Attribute” 3-41 “Operation” 3-44 “Nested Class Declarations” 3-48 “Type and Implementation Class” 3-49 “Interfaces” 3-50 “Parameterized Class (Template)” 3-52 “Bound Element” 3-54 “Utility” 3-56 “Metaclass” 3-57 “Enumeration” 3-57 “Stereotype Declaration” 3-57 “Powertype” 3-61 “Class Pathnames” 3-61 “Accessing or Importing a Package” 3-62 “Object” 3-64 “Composite Object” 3-67 “Association” 3-68 “Binary Association” 3-68 3-2 OMG-Unified Modeling Language, v1.5 March 2003 3 UML Notation Guide
    [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]
  • Transformations of Software Process Models to Adopt Model-Driven Architecture
    Transformations of Software Process Models to Adopt Model-Driven Architecture Vladimirs Nikulsins Riga Technical University, Meza 1/3, LV-1048 Riga, Latvia Abstract. This paper proposes a solution on how to adopt software develop- ment process and make it compliant with the Model Driven Architecture by OMG. Process modeling languages helps to formalize the knowledge about the software development life cycle expressed in tasks, activities, phases, workflows and roles. SPEM (Software Process Engineering Meta-Model) is OMG standard used to describe a software development process within an or- ganization. The proposed solution is to transform any so called “traditional” software development life cycle model into the model-driven with the help of model transformations written in Query/View/Transformation (QVT) language. This approach has been partially approbated in one of the Latvian IT compa- nies. 1 Introduction MDA (Model Driven Architecture) is OMG (Object Management Group) paradigm that focuses on the software development process using modeling and model trans- formations. Within MDA the software development process is driven by modeling the software system rather than producing the code: models are transformed into the working code through the various automated and semi-automated transformations. No specific software development methodology is proposed by OMG and so MDA can fit into any software development process. This allows a certain flexibility, and at the same time, a lack of formalized knowledge on adapting the model-driven devel- opment to the software development methodologies used in practice. Process model- ing activity helps to describe the appropriate software development activities and their relations in the software development life cycle (SDLC).
    [Show full text]
  • Contract Number: 4400016179
    Page 1 of 2 FULLY EXECUTED Contract Number: 4400016179 Original Contract Effective Date: 12/13/2016 Valid From: 01/01/2017 To: 12/31/2018 All using Agencies of the Commonwealth, Participating Political Subdivision, Authorities, Private Colleges and Universities Purchasing Agent Name: Millovich Joseph Your SAP Vendor Number with us: 102380 Phone: 717-214-3434 Fax: 717-783-6241 Supplier Name/Address: IBM CORPORATION P.O. Box 643600 PITTSBURGH PA 15264-3600 US Please Deliver To: To be determined at the time of the Purchase Order unless specified below. Supplier Phone Number: 7175477069 Contract Name: Payment Terms IBM Software & Related Services NET 30 Solicitation No.: Issuance Date: Supplier Bid or Proposal No. (if applicable): Solicitation Submission Date: This contract is comprised of: The above referenced Solicitation, the Supplier's Bid or Proposal, and any documents attached to this Contract or incorporated by reference. Item Material/Service Qty UOM Price Per Total Desc Unit 2 Licenses/Appliances/Subscriptions/SaaS 0.000 0.00 1 0.00 Item Text Software: includes, but is not limited to, commercially available licensed software, software appliances, software subscriptions and software as a service (SaaS). Agencies must develop and attach the Requirements for Non-Commonwealth Hosted Applications/Services when purchasing SaaS (see Appendix H). -------------------------------------------------------------------------------------------------------------------------------------------------------- 3 Services/Support/Maintenance 0.000 0.00
    [Show full text]
  • Java and Z/OS (And Rdz)
    ® IBM Software Group Java and z/OS (and RDz) Jon Sayles – [email protected] © 2016 IBM Corporation IBM Software Group | Rational software Merrill Class . They’ll have RDz exposure . Terms & Concepts & Vocabulary Remove fear of Java Analogies – Procedural vocabulary 20 – 30 students - mix of young + old (mostly old) dudes . Call COBOL from Java Java doesn’t create an .exe Objects . z/OS Java Standard z/OS environment JCL – pointing to Unix Aware of JVM – can call COBOL http://www.s390java.com/index.htm IBM Software Group | Rational software Trademarks Trademarks The following are trademarks of the International Business Machines Corporation in the United States and/or other countries. For a complete list of IBM Trademarks, see www.ibm.com/legal/copytrade.shtml: AS/400, DBE, e-business logo, ESCO, eServer, FICON, IBM, IBM Logo, iSeries, MVS, OS/390, pSeries, RS/6000, S/30, VM/ESA, VSE/ESA, Websphere, xSeries, z/OS, zSeries, z/VM The following are trademarks or registered trademarks of other companies Lotus, Notes, and Domino are trademarks or registered trademarks of Lotus Development Corporation Java and all Java-related trademarks and logos are trademarks of Sun Microsystems, Inc., in the United States and other countries LINUX is a registered trademark of Linux Torvalds UNIX is a registered trademark of The Open Group in the United States and other countries. Microsoft, Windows and Windows NT are registered trademarks of Microsoft Corporation. SET and Secure Electronic Transaction are trademarks owned by SET Secure Electronic Transaction LLC. Intel is a registered trademark of Intel Corporation * All other products may be trademarks or registered trademarks of their respective companies.
    [Show full text]
  • Annual Report 2011
    ANNUAL REPORT 2011 TO OUR STOCKHOLDERS: I am pleased to report that KLA-Tencor performed at record levels on several fronts in fi scal year 2011. We achieved company records in our most critical fi nancial metrics, including revenues, net income, earnings per share and profi t margins, and our year-over-year revenue growth signifi cantly exceeded that of our peer group and our industry. At the same time, we generated record free cash fl ow and continued to deliver meaningful returns to our stockholders in the form of dividends and stock repurchases. This performance was the result of our unwavering focus on develop- ing market-leading technology, addressing our customers’ most critical needs and driving operational effi ciency. Though our industry has seen a recent slowdown in demand, we remain very excited about KLA-Tencor’s prospects for the future. The long-term demand drivers for KLA-Tencor and our industry remain intact, and we are well positioned to grow as demand for semiconductor capital equipment recovers. Our record results in fi scal year 2011 demonstrate that our strategies are working. Looking back over our 35-year history, we have established a pattern of achievement and leadership, which has enabled us to create the strong foundation from which we now look ahead to the future. Our accomplishments during fi scal year 2011 in each of our four strategic objectives (Customer Focus, Growth, Operational Excellence and Talent Development) are highlighted below: CUSTOMER FOCUS: MARKET LEADERSHIP Our customer focus strategic objective is measured in customer satisfaction and market share. We maintained our market leadership positions among our foundry and logic customers in fi scal year 2011 and improved our market position in memory, as evidenced by achieving record new order levels across all our end markets during the year.
    [Show full text]
  • UML 2001: a Standardization Odyssey
    UML 2001: A Standardization Odyssey As the UML reaches the ripe age of four, both its proponents and its critics are scanning the recent changes in the UML 1.3 revision. CRIS KOBRYN In a relatively short period of time the Unified Modeling Language has emerged as the software industry’s dominant modeling language. UML is not only a de facto modeling language standard; it is fast becoming a de jure standard. Nearly two years ago the Object Management Group (OMG) adopted UML as its standard modeling language. As an approved Publicly Available Specification (PAS) submitter to the International Organization for Standardization (ISO), the OMG is proposing the UML specification for international timescales of standards usually conflict with the standardization. It is anticipated that the “fast competitive need to use the latest technology as track” PAS process will complete sometime next early as possible. From a technical perspective, the year, at which time UML will be formally recog- need to achieve consensus encourages “design by nized as an international standard for information committee” processes. In this sort of environment, technology. sound technical tradeoffs are often overridden by The major benefits of international standardiza- inferior political compromises. Too frequently the tion for a specification include wide recognition and resulting specifications become bloated with patches acceptance, which typically enlarge the market for in a manner similar to the way laws become fattened products based on it. However, these benefits often with riders in “pork belly” legislation. demand a high price. Standardization processes are This article explores how the UML is faring in typically formal and protracted, seeking to accom- the international standardization process.
    [Show full text]