DOCSLIB.ORG

Tutorial at Caise'2003, Velden, Austria

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Tutorial at Caise'2003, Velden, Austria CAiSE 2003 Tutorial 23-April-2003 This presentation is based on: Developing Maintainable Systems – This presentation is based on: Roundtrip Engineering with Metrics Maciaszek, L.A. (2001): Requirements Analysis and System Design. Developing Information Systems with UML, Addison-Wesley, 378p. {translated to Chinese, Russian and Italian} forthcoming 2nd edition of the above: Tutorial Maciaszek, L.A. (2004): Requirements Analysis and The 15th Conf. on Advanced Information Systems Engineering CAiSE’03 Systems Design, 2nd ed., Addison-Wesley, ~500p. Velden, Austria, 17-June-2003 forthcoming new textbook: Leszek A. Maciaszek, Bruc Lee Liong Maciaszek, L.A. Liong, B.L. and Bills, S. (2004): Macquarie University, Sydney, Australia Practical Software Engineering. A Case-Study Approach, Addison-Wesley, ~600p. © L.A.Maciaszek, B.L.Liong & Addison-Wesley © Addison-Wesley CAiSE 2003 Tutorial 2 Topics The tutorial themes Application design objectives - PCMEF “Applications come and go. Databases stay for ever.” Tutorial case study – Email Management System Bob Epstein, Sybase (quoted from memory) Dependency management “Enterprise applications often have complex data – Generic architectural patterns and lots of it – to work on, together with business Architectural patterns for business objects rules that fail all tests of logical reasoning.” The supportability metrics “The architectural pattern I like the most is that of Conclusions layers…” Martin Fowler (in “Patterns of Enterprise Information Architecture”) © Addison-Wesley CAiSE 2003 Tutorial 3 © Addison-Wesley CAiSE 2003 Tutorial 4 Application design objectives MVC a hierarchical layering of software modules that reduces complexity and enhances Application Program understandability of module dependencies by disallowing direct object View intercommunication between non- Database and Web Services neighboring layers, and Model an enforcement of programming standards Persistent that make module dependencies visible in Data compile-time program structures and that Controller forbid muddy programming solutions utilizing just run-time program structures © Addison-Wesley CAiSE 2003 Tutorial 5 © Addison-Wesley CAiSE 2003 Tutorial 6 © L.A.Maciaszek, B.L. Liong & Addison- Wesley 1 CAiSE 2003 Tutorial 23-April-2003 PCMEF application packages <<layer>> Meaning of P-C-M-E-F presentation The Presentation package • classes that define UI objects <<layer>> The Control package control • classes responsible for the program’s logic, algorithmic solutions, and main computations The Mediator package <<layer>> • creates a level of independence between entity and foundation domain and between control and foundation PCMEF entity mediator • responsible for object caching Database and Web The Entity package Services • classes representing “business objects” <<layer>> Persistent The Foundation package foundation Data • responsible for all communications with the persistent data store © Addison-Wesley CAiSE 2003 Tutorial 7 © Addison-Wesley CAiSE 2003 Tutorial 8 Consider non-PCMEF design ...and PCMEF design CControl EEntity CControl MMediator PPresentation MMediator PPresentation EEntity FFoundation FFoundation © Addison-Wesley CAiSE 2003 Tutorial 9 © Addison-Wesley CAiSE 2003 Tutorial 10 PCMEF principles PCMEF+ Downward Dependency Principle (DDP) Upward Notification Principle (UNP) Neighbor Communication Principle (NCP) Explicit Association Principle (EAP) Cycle Elimination Principle (CEP) Class Naming Principle (CNP) Acquaintance Package Principle (APP) © Addison-Wesley CAiSE 2003 Tutorial 11 © Addison-Wesley CAiSE 2003 Tutorial 12 © L.A.Maciaszek, B.L. Liong & Addison- Wesley 2 CAiSE 2003 Tutorial 23-April-2003 Tutorial case study Display email messages EM – Email Management system • part of an Electronic Document Management System • capture, indexing, classification and retrieval of all email business correspondence Composing and emailing of messages stored in the database and scheduled to be sent to contacts (customers) • a Java application that accesses an Oracle database via JDBC • upon employee’s login to the database, the application can retrieve from the database and display the list of messages to be emailed to contacts • the employee can then email chosen messages • after a successful email, the database is updated accordingly • the employee can create, update, delete messages • messages can be sorted and filtered © Addison-Wesley CAiSE 2003 Tutorial 13 © Addison-Wesley CAiSE 2003 Tutorial 14 Update email message Email received © Addison-Wesley CAiSE 2003 Tutorial 15 © Addison-Wesley CAiSE 2003 Tutorial 16 Conceptual class model Relational database model © Addison-Wesley CAiSE 2003 Tutorial 17 © Addison-Wesley CAiSE 2003 Tutorial 18 © L.A.Maciaszek, B.L. Liong & Addison- Wesley 3 CAiSE 2003 Tutorial 23-April-2003 Class Let’s slow down and revisit… model for EM Architectural design is an exercise in managing module dependencies • Module A depends on module B if changes to module B may necessitate changes to module A It is important that dependencies do not cross dependency firewalls (Martin, 2003) • In particular, dependencies should not propagate across non-neighboring layers and must not create cycles © Addison-Wesley CAiSE 2003 Tutorial 19 © Addison-Wesley CAiSE 2003 Tutorial 20 Proactive and reactive approach Packages Architectural design takes a proactive approach to dependency relationship B owns X A depends on B managing dependencies in software. • This is a forward-engineering approach – from design to Package B Package E implementation. Package A Class X • The aim is to deliver a software design that minimizes dependencies by imposing an architectural solution on + package with no members revealed programmers. circle-plus notation Package F Proactive approach must be supported by the Package C E owns F reactive approach that aims at measuring F owns Y and Z dependencies in implemented software. Package D + • This is a reverse-engineering approach – from implementation to design. • The implementation may or may not conform to the Class Y Class Z desired architectural design. C owns D © Addison-Wesley CAiSE 2003 Tutorial 21 © Addison-Wesley CAiSE 2003 Tutorial 22 Cycles between packages Eliminating cycles between packages Package A Package B Package A Package B circularly-dependable Package A2 elements of Package A extracted into Package A2 Package C Package D Package E Package C Package D Package E circularly-dependable Package C2 elements of Package C extracted into Package C2 © Addison-Wesley CAiSE 2003 Tutorial 23 © Addison-Wesley CAiSE 2003 Tutorial 24 © L.A.Maciaszek, B.L. Liong & Addison- Wesley 4 CAiSE 2003 Tutorial 23-April-2003 <<layer>> <<layer>> Layer Layer 1 Layer 1 Package A Package B dependencies Package A Package B Class X Class Y Layer 1 Package A depends on depends on Package B because Class Layer 2 X depends on ClassY <<layer>> Layer 2 Class <<layer>> Layer 2 Layer 1 depends on Layer 2 because Class X Package C Package D depends on Class Y depend- Package C Package D encies Class Z Package E Package E © Addison-Wesley CAiSE 2003 Tutorial 25 © Addison-Wesley CAiSE 2003 Tutorial 26 Method dependencies Method dependencies and delegation control control public class EOutMessage { EEmployee emp; CActioner CActioner p ubl ic void d o2() { emp.do3(); do1() entity } public class EOutMessage { EOutMessage EEmployee emp; do1() } public void do2() { public class CActioner { emp.do3(); 0..1 EEmployee emp; do2() } public void do1() { } emp.do3(); } public class EEmployee { public class CActioner { entity } EEmployee MBroker brk; EEmployee emp; public void do3() { public void do1() { brk.do3(); do3() } emp.do3(); Act Emp EOutMessage 0..1 mediator } } } do2() MBroker 0..n OutEmp do3() foundation EEm ployee public class MBroker { public class FUpdater { FUpdater upd; FUpdater public void do3() { 0..n public void do3() { // code for do3 do3() upd.do3(); do3() } } } } © Addison-Wesley CAiSE 2003 Tutorial 27 © Addison-Wesley CAiSE 2003 Tutorial 28 Interfaces UML notations In the UML 2.0, interface is a declaration of a set of features that is not directly instantiable, i.e. no objects of it can be directly created. The object that implements interface provides “a public façade that conforms to the interface specification” (UML, 2002, p.123). <<Interface>> In UML 2.0 interface can declare attributes, not just Interface1 Interface3 operations. Interface2 • By contrast, in Java an interface can contain data members but they must be constants (defined as static and final). An abstract class is a class that contains at least one method, which is not (or cannot be) implemented by that class, and therefore it cannot be instantiated. • A class is a class is a class. In languages that support only single AbstractClass1 Class1 implementation inheritance, like Java, a class can only extend one base class (abstract or concrete), but it can implement multiple interfaces. This is a huge practical difference. • The related difference is that interfaces allow passing objects typed as interfaces in method calls. © Addison-Wesley CAiSE 2003 Tutorial 29 © Addison-Wesley CAiSE 2003 Tutorial 30 © L.A.Maciaszek, B.L. Liong & Addison- Wesley 5 CAiSE 2003 Tutorial 23-April-2003 Implementation dependency Usage dependency This is permitted in UML 2.0, but not in Java, which only allows extension inheritance between interfaces public interface Interface1 { private int a1; Interface1 Interface2 public void o1(); a1 a2 } Interface1 <<uses>> Interface2 o1() o2() a1 a2 public class Class1
Load more

Recommended publications
  • Mastering JEE Design Patterns
    "Charting the Course ... ... to Your Success!" Mastering JEE Design Patterns Course Summary Description Geared for experienced enterprise Java (JEE) developers, Mastering JEE Design Patterns is a lab- intensive Java / JEE design patterns training course which explores the many sophisticated JEE-oriented design patterns and how to use these patterns to develop solid, robust and reusable JEE applications. Technologies such as JPA and EJB3, as well as frameworks such as Spring, web services and rich interfaces, have significantly impacted previous generations of design patterns. Many of these technologies were heavily influenced by the very problems that previous design patterns addressed. While the basic patterns still ring true, the more advanced patterns have evolved into more robust solutions for secure, stable and scalable enterprise applications. Working in a hands-on environment, developers will explore key patterns in each of the different JEE layers and how they are used most effectively in building robust, reusable JEE applications. Objectives Working in a dynamic, interactive discussion and hands-on programming environment, let by our JEE expert team, students will explore the following pattern categories: Crosscutting Business Tier Presentation Tier Integration Tier Topics Introduction to Design Patterns Integration Tier Patterns “Gang of Four” Design Patterns Presentation Tier Patterns Base Patterns Crosscutting Patterns Business Tier Patterns Working with Patterns Audience This is an intermediate level Java EE (JEE) developer course, designed for experienced Java developers, new to JEE, that need to further extend their skills in web development and Struts. Prerequisites Attendees should have an extensive working knowledge in developing basic Java applications. Duration Five days Due to the nature of this material, this document refers to numerous hardware and software products by their trade names.
    [Show full text]
  • Design Optimizations of Enterprise Applications – a Literature Survey
    Design Optimizations of Enterprise Applications – A Literature Survey Willie (Phong) Tu Dept. of Computer Science, University of Calgary [email protected] Abstract Another dimension is the performance improvement for the single user versus multiple users, in other words, Software design patterns have been defined as scalability. The design optimization patterns noted here possible solutions to reoccurring problems. One aspect will focus on actual running time of operations for of the problems is performance. This can be arguably single user performance and multi-user scalability true in high volume enterprise applications. This paper improvements. will explore the current discussions and research in The organization of the findings is categorized utilization of software design patterns to optimize through the usage of an architectural pattern, which is enterprise applications. defined as layer [5]. The layers used are the primary three-layer architecture for information systems [10,21], which includes the data access layer, domain layer, and 1. Introduction presentation layer. Design optimization patterns that spans layers will be elaborated first, then a bottom up First, let’s define what is design optimization. In this approach starting with the data access layer, followed by context, design optimization is the improvement of an the domain layer, and finally the presentation layer. We application’s design and performance using software will then continue on with findings from different design patterns. Design improvements can be subjective, enterprise applications. After which, we will summarize thus the main qualifier is the utilization of software the current state in design optimizations of enterprise design patterns to improve the performance of an applications based on the findings.
    [Show full text]
  • Enterprise Application Design Patterns: Improved and Applied
    Enterprise Application Design Patterns: Improved and Applied Stuart Thiel A Thesis in The Department of Computer Science and Software Engineering Presented in Partial Fulfillment of the Requirements for the Degree of Master of Computer Science at Concordia University Montreal, Quebec, Canada January 2010 © Stuart Thiel, 2010 i CONCORDIA UNIVERSITY School of Graduate Studies This is to certify that the thesis prepared By: Stuart Thiel Entitled: Enterprise Application Design Patterns: Improved and Applied and submitted in partial fulfillment of the requirements for the degree of Master of Computer Science complies with the regulations of the University and meets the accepted standards with respect to originality and quality. Signed by the final examining committee: ______________________________________________Chair Dr. Nematollaah Shiri ______________________________________________Examiner Dr. Greg Butler ______________________________________________Examiner Dr. Yuhong Yan ______________________________________________Supervisor Dr. Patrice Chalin Approved by __________________________________________ Chair of Department or Graduate Program Director _____________________________________ Dr. Robin Drew, Dean Faculty of Engineering and Computer Science Date ______________________________________________ i ii Abstract Enterprise Application Design Patterns: Improved and Applied Stuart Thiel Providing developers with proper tools is of ever increasing importance as software integrates itself further into all aspects of our lives. Aside from conventional hardware and software tools, architectural and design patterns have been identified over the years as a means to communicate knowledge of known problems and their solutions. In this thesis, we present several refinements and additions to these patterns, building primarily on Martin Fowler’s Patterns of Enterprise Application Architecture (2003). We present a practical implementation approach to using these patterns and discuss a framework that we have developed to aid practitioners in following this methodology.
    [Show full text]
  • A Solution to the Object-Relational Mismatch
    Universidade do Minho Escola de Engenharia Miguel Esteves CazDataProvider: A solution to the object-relational mismatch Outubro de 2012 Universidade do Minho Escola de Engenharia Departamento de Informática Miguel Esteves CazDataProvider: A solution to the object-relational mismatch Dissertação de Mestrado Mestrado em Engenharia Informática Trabalho realizado sob orientação de Professor José Creissac Campos Outubro de 2012 To my parents... \Each pattern describes a problem which occurs over and over again in our environment, and then describes the core of the solution to that problem, in such a way that you can use this solution a million times over, without ever doing it the same way twice." Christopher Alexander Abstract Today, most software applications require mechanisms to store information persistently. For decades, Relational Database Management Systems (RDBMSs) have been the most common technology to provide efficient and reliable persistence. Due to the object-relational paradigm mismatch, object oriented applications that store data in relational databases have to deal with Object Relational Mapping (ORM) problems. Since the emerging of new ORM frameworks, there has been an attempt to lure developers for a radical paradigm shift. However, they still often have troubles finding the best persistence mechanism for their applications, especially when they have to bear with legacy database systems. The aim of this dissertation is to discuss the persistence problem on object oriented applications and find the best solutions. The main focus lies on the ORM limitations, patterns, technologies and alternatives. The project supporting this dissertation was implemented at Cachapuz under the Project Global Weighting Solutions (GWS). Essentially, the objectives of GWS were centred on finding the optimal persistence layer for CazFramework, mostly providing database interoperability with close-to-Structured Query Language (SQL) querying.
    [Show full text]
  • Architects and Architecture Today
    PUBLISHED BY Microsoft Press A Division of Microsoft Corporation One Microsoft Way Redmond, Washington 98052-6399 Copyright © 2009 by Andrea Saltarello and Dino Esposito All rights reserved. No part of the contents of this book may be reproduced or transmitted in any form or by any means without the written permission of the publisher. Library of Congress Control Number: 2008935425 Printed and bound in the United States of America. 1 2 3 4 5 6 7 8 9 QWT 3 2 1 0 9 8 Distributed in Canada by H.B. Fenn and Company Ltd. A CIP catalogue record for this book is available from the British Library. Microsoft Press books are available through booksellers and distributors worldwide. For further infor mation about international editions, contact your local Microsoft Corporation office or contact Microsoft Press International directly at fax (425) 936-7329. Visit our Web site at www.microsoft.com/mspress. Send comments to [email protected]. Microsoft, Microsoft Press, Access, ActiveX, IntelliSense, MS, MSDN, MS-DOS, PowerPoint, Silverlight, SQL Server, Visio, Visual Basic, Visual C#, Visual Studio, Windows, and Windows Vista are either registered trademarks or trademarks of the Microsoft group of companies. Other product and company names mentioned herein may be the trademarks of their respective owners. The example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. This book expresses the author’s views and opinions.
    [Show full text]
  • Doctrine 2 ORM Documentation Release 2
    Doctrine 2 ORM Documentation Release 2 Doctrine Project Team June 11, 2015 Contents 1 Getting Help 3 2 Getting Started 5 3 Mapping Objects onto a Database7 4 Working with Objects 9 5 Advanced Topics 11 6 Tutorials 13 7 Changelogs 15 8 Cookbook 17 9 Welcome to Doctrine 2 ORM’s documentation! 19 9.1 Tutorials................................................. 19 9.2 Reference Guide............................................. 60 9.3 Cookbook................................................ 278 i ii Doctrine 2 ORM Documentation, Release 2 The Doctrine documentation is comprised of tutorials, a reference section and cookbook articles that explain different parts of the Object Relational mapper. Doctrine DBAL and Doctrine Common both have their own documentation. Contents 1 Doctrine 2 ORM Documentation, Release 2 2 Contents CHAPTER 1 Getting Help If this documentation is not helping to answer questions you have about Doctrine ORM don’t panic. You can get help from different sources: • There is a FAQ with answers to frequent questions. • The Doctrine Mailing List • Internet Relay Chat (IRC) in #doctrine on Freenode • Report a bug on JIRA. • On Twitter with #doctrine2 • On StackOverflow If you need more structure over the different topics you can browse the table of contents. 3 Doctrine 2 ORM Documentation, Release 2 4 Chapter 1. Getting Help CHAPTER 2 Getting Started • Tutorial: Getting Started with Doctrine • Setup: Installation & Configuration 5 Doctrine 2 ORM Documentation, Release 2 6 Chapter 2. Getting Started CHAPTER 3 Mapping Objects onto a Database • Mapping: Objects| Associations| Inheritance • Drivers: Docblock Annotations| XML| YAML| PHP 7 Doctrine 2 ORM Documentation, Release 2 8 Chapter 3. Mapping Objects onto a Database CHAPTER 4 Working with Objects • Basic Reference: Entities| Associations| Events • Query Reference: DQL| QueryBuilder| Native SQL • Internals: Internals explained| Associations 9 Doctrine 2 ORM Documentation, Release 2 10 Chapter 4.
    [Show full text]
  • SAMPLE CHAPTER Nhibernate in Action
    SAMPLE CHAPTER NHibernate in Action Pierre Henri Kuaté Tobin Harris Christian Bauer Gavin King Chapter 1 Copyright 2009 Manning Publications brief contents PART 1DISCOVERING ORM WITH NHIBERNATE............................. 1 1 ■ Object/relational persistence in .NET 3 2 ■ Hello NHibernate! 24 PART 2NHIBERNATE DEEP DIVE ................................................. 49 3 ■ Writing and mapping classes 51 4 ■ Working with persistent objects 100 5 ■ Transactions, concurrency, and caching 134 6 ■ Advanced mapping concepts 166 7 ■ Retrieving objects efficiently 207 PART 3NHIBERNATE IN THE REAL WORLD.................................. 257 8 ■ Developing NHibernate applications 259 9 ■ Writing real-world domain models 286 10 ■ Architectural patterns for persistence 319 1 Part 1 Discovering ORM with NHibernate The first part of the book provides insights into what ORM is, why it exists, and how it fits in a typical .NET application. We then introduce NHibernate, using a clear and simple example to help you understand how the various pieces of an NHibernate application fit together. Object/relational persistence in .NET This chapter covers ■ .NET persistence and relational databases ■ Layering .NET applications ■ Approaches to implementing persistence in .NET ■ How NHibernate solves persistence of objects in relational databases ■ Advanced persistence features Software development is an ever-changing discipline in which new techniques and technologies are constantly emerging. As software developers, we have an enor- mous array of tools and practices available, and picking the right ones can often make or break a project. One choice that is thought to be particularly critical is how to manage persistent data—or, more simply, how to load and save data. Almost endless options are available. You can store data in binary or text files on a disk.
    [Show full text]
  • Microsoft .NET: Architecting Applications for the Enterprise Ebook
    PUBLISHED BY Microsoft Press A Division of Microsoft Corporation One Microsoft Way Redmond, Washington 98052-6399 Copyright © 2009 by Andrea Saltarello and Dino Esposito All rights reserved. No part of the contents of this book may be reproduced or transmitted in any form or by any means without the written permission of the publisher. Library of Congress Control Number: 2008935425 Printed and bound in the United States of America. 1 2 3 4 5 6 7 8 9 QWT 3 2 1 0 9 8 Distributed in Canada by H.B. Fenn and Company Ltd. A CIP catalogue record for this book is available from the British Library. Microsoft Press books are available through booksellers and distributors worldwide. For further infor mation about international editions, contact your local Microsoft Corporation office or contact Microsoft Press International directly at fax (425) 936-7329. Visit our Web site at www.microsoft.com/mspress. Send comments to [email protected]. Microsoft, Microsoft Press, Access, ActiveX, IntelliSense, MS, MSDN, MS-DOS, PowerPoint, Silverlight, SQL Server, Visio, Visual Basic, Visual C#, Visual Studio, Windows, and Windows Vista are either registered trademarks or trademarks of the Microsoft group of companies. Other product and company names mentioned herein may be the trademarks of their respective owners. The example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. This book expresses the author’s views and opinions.
    [Show full text]
  • Design Patterns and Coldfusion Sean a Corfield Chief Systems Architect Broadchoice, Inc
    Design Patterns and ColdFusion Sean A Corfield Chief Systems Architect Broadchoice, Inc. Patterns describe problems and solutions “Each pattern describes a problem which occurs over and over again in our environment, and then describes the core of the solution to that problem, in such a way that you can use this solution a million times over, without ever doing it the same way twice.” -- Christopher Alexander, architect Alexander is not a software architect - he is a building architect! 1. Hierarchy of Open Space - big space in front, small space behind 2. Intimacy Gradient - enter into public areas, navigate into private areas Who am I? VP Engineering, Broadchoice Previously: Mgr, Adobe Hosted Services Sr Architect, Macromedia IT Sr Consultant, various web co. Architect / Developer: ColdFusion since 2001 Java since 1997 (Groovy since 2008!) Also manager of Bay Area ColdFusion User Group! What is this about? Common problems Common solutions Trade offs Show of hands: 1. Who’s using ColdFusion 8? 7? 6.1? 5 or earlier? 2. Who’s using CFCs? Who thinks they’re writing OO code? Patterns? I want to remove some of the mystery around patterns by showing you how pervasive they are - you're probably already using some patterns without even realizing it. I hope that you will come out of this session with a better understanding of what patterns are how they can help you in your day-to-day programming work - and that you will be inspired to learn more about patterns and extend yourself to become a better developer. Our roadmap Some simple, common patterns Patterns and languages Selecting and using patterns Frameworks and patterns Recommended reading Simple, common pattern examples A common problem My web site has the same stuff at the top and bottom of each page and I don't want to duplicate that in every page! A common solution Put the common stuff in separate files (header.cfm and footer.cfm) and include them on every page.
    [Show full text]
  • Migration of Applications Across Object-Oriented Apis
    Migration of Applications across Object-Oriented APIs by Thiago Tonelli Bartolomei A thesis presented to the University of Waterloo in fulfillment of the thesis requirement for the degree of Doctor of Philosophy in Electrical and Computer Engineering Waterloo, Ontario, Canada, 2012 c Thiago Tonelli Bartolomei 2012 I hereby declare that I am the sole author of this thesis. This is a true copy of the thesis, including any required final revisions, as accepted by my examiners. I understand that my thesis may be made electronically available to the public. ii Abstract Software developers often encapsulate reusable code as Application Programming Inter- faces (APIs). The co-evolution of applications and APIs may motivate an API migration: the replacement of application dependencies to an original API by dependencies to an alternative API that provides similar functionality and abstractions. In this dissertation, we investigate issues associated with API migration in object- oriented systems, with special focus on wrapping approaches. We present two studies and a set of developer interviews that elicit issues in the process and techniques used in API migration in practice. The results suggest that the most pressing issues relate to discovery and specification of differences between APIs, and to assessment of migration correctness. This dissertation introduces techniques and a method to address these issues. We propose the use of design patterns to support the specification of API wrappers. API wrapping design patterns encode solutions to common wrapping design problems. We present an initial catalog of such patterns that were abstracted from programming idioms found in existing API wrappers. We introduce the concept of compliance testing for API migration, a form of automated testing.
    [Show full text]
  • Patterns for API Migration by Wrapping
    Swing to SWT and Back: Patterns for API Migration by Wrapping Thiago Tonelli Bartolomei and Krzysztof Czarnecki Ralf Lammel¨ University of Waterloo University of Koblenz-Landau Waterloo, Canada Koblenz, Germany Abstract—Evolving requirements may necessitate API migra- In terms of their interfaces, the chosen APIs are very similar, tion—re-engineering an application to replace its dependence on but the actual implementations differ systematically in the one API with the dependence on another API for the same contracts for many methods. Our study was meant to measure domain. One approach to API migration is to replace the original API by a wrapper-based re-implementation that makes reuse of the effort needed to develop a sufficiently compliant wrapper the other API. Wrapper-based migration is attractive because in such a situation. The overall result of that work is twofold: application code is left untouched and wrappers can be reused a) wrappers need to involve a lot of tuning in order to achieve across applications. The design of such wrappers is challenging semantical equivalence in terms of pre- and post-conditions; though if the two involved APIs were developed independently, b) full compliance of the wrapper’s implementation with the in which case the APIs tend to differ significantly. We identify the challenges faced by developers when designing wrappers original API may be impractical; compliance relative to an for object-oriented APIs, and we recover the solutions used in ‘application of interest’ is achievable though. practice. To this end, we analyze two large, open-source GUI In this paper, we address a different aspect of API migration wrappers and compile a set of issues pervasive in their designs.
    [Show full text]
  • Software Architecture Design Architectural Patterns Readings
    Software Architecture Design Architectural Patterns Matthew Dailey Computer Science and Information Management Asian Institute of Technology Matthew Dailey (CSIM-AIT) Patterns 1 / 193 Readings Readings for these lecture notes: - Fowler (2002), Patterns of Enterprise Application Architecture, Addison-Wesley, Ch. 1–3, 9–11. Some material c Fowler (2002). Matthew Dailey (CSIM-AIT) Patterns 2 / 193 Outline 1 Introduction 2 Domain logic patterns 3 Mapping to relational databases 4 Web presentation 5 Concurrency 6 Session state 7 Distribution strategies Matthew Dailey (CSIM-AIT) Patterns 3 / 193 Introduction Fowler (2002) opens with a quote from Christopher Alexander: Each pattern describes a problem which occurs over and over again in our environment, then describes the core of the solution to that problem, in such a way that you can use this solution a million times over, without ever doing it the same way twice. Alexander was actually a (building) architect, but the same idea is relevant in software system architecture. Patterns represent best practices we can apply to ensure we don’t make the same mistakes the pioneers did. Matthew Dailey (CSIM-AIT) Patterns 4 / 193 Introduction In software architecture as in building architecture, patterns are references forming a common vocabulary for design. Patterns are not recipes! You can never blindly apply them, since they are always incomplete to some degree. Matthew Dailey (CSIM-AIT) Patterns 5 / 193 Introduction We begin with Fowler’s (2002) patterns, which share a common structure: Each pattern has a carefully chosen name. Each pattern has an intent summing up the pattern in a sentence or two. Each pattern has a sketch representing it visually, in UML or otherwise.
    [Show full text]