DOCSLIB.ORG

Design Patterns Design Pattern

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Design Patterns Design Pattern Enrico Vicario - AA 18/19 Enrico Vicario - AA 18/19 Design Patterns SW Engineering SW Engineering Software Engineering - A.A. 18/19 . Design pattern: a reusable solution scheme for some recurrent problem . a name, a problem, alternative solutions, known consequences, … . term first made explicit in Architecture by Christopher Alexander Design Patterns in Java . like a handbook of electronics schemes (amplifiers push-pull, totem-pole, …) from the original [GOF] c++ version . ProducerConsumer or Monitor are also patterns in operating systems with a certain regard for Java implementation . Patterns in OO Design . Advanced use of OO programming schemes . Substitutability and polymorphism, inheritance, composition, … . Override, method look-up or dynamic binding and virtual methods, … . Basically agnostic, but differently mapped to different languages Enrico Vicario Dipartimento di Ingegneria dell'Informazione Laboratorio Tecnologie del Software – stlab.dinfo.unifi.it Università di Firenze [email protected], stlab.dinfo.unifi.it/vicario 1/98 2/98 Enrico Vicario - AA 18/19 The Observer pattern Enrico Vicario - AA 18/19 The Observer pattern SW Engineering SW Engineering . The problem . one step ahead . (an object of type) Subject has a state variable whose value . assign to Subject is necessary also to (objects of type) Observer_A and Observer_B the responsibility of . (this might occur in the transition from specification to implementation, notifying Observers or in refactoring for separation of main concerns) (inversion of responsibility) . Much about . after any change of its state, maintaining consistence Subject invokes notify() across decoupling which in turn invokes update() on each Observer . a naive solution . (naive is a positive attribute, in the beginning) . Subject provides a public method that Observer invokes to get the value . But, when shall the Observer unpdate its copy of the state? … might be before using it … but, intermediate states could be relevant as well (e.g. Computing interest on a banking current account) . Yet, the Subject must be aware of all the types and instances of Observer 3/98 4/98 1 Enrico Vicario - AA 18/19 The Observer pattern Enrico Vicario - AA 18/19 The Observer pattern SW Engineering SW Engineering . Some further steps ahead . Dynamic registration of Observers on the Subject . get the Subject rid off the responsibility to register Observers: . attach() and detach() invoked by the Observer or someone else attach() and detach() to be used by the Observers, or by their creators . Subject notifies to AbstractSubject (same object) through notify() (one more inversion of responsibility) . notify() invokes update() on each registered Observer . Decouple the inherent business of a Subject from being observable . Each Observer may call-back on getState() to get the state (using inheritance to reuse the methods for observability) (pull vs push mode) . Abstract Observers under a common interface for homogenous collection . Call this Observer . define a one to many dependency so that when an object changes state all its dependents are notified . Also Known As: Publish & Subscribe (enterprise scale) 5/98 6/98 Enrico Vicario - AA 18/19 The Observer pattern Enrico Vicario - AA 18/19Patterns are often supported or applied by classes n standard APIs SW Engineering SW Engineering . Amplification of interaction :-( . class java.util.Observable . In principle might even be unbounded (call-backs) . Can be reduced by registering Observers on specific Topics, at the attach() . usual in the enterprise scale publish&subscribe . Pull vs puh mode . Pull: the Subject notifies that a change happened, and the Observer calls-back, if needed, accordind to its policy . Push: Notification from the Subject carries the state change some parameter to distinguish among multiple subjects . A matter of: efficiency, robustness, coupling . State consistency . When the update() is performed, the state must be “stable”, but, some action might trigger multiple "atomic" state changes . A change manager (Mediator pattern) may get responsibility of coordination . interface java.util.Observer 7/98 8/98 2 Enrico Vicario - AA 18/19 Notes on java.util.Observable Enrico Vicario - AA 18/19 Observer: examples of code SW Engineering SW Engineering notifyObservers() is public, setChanged() is protected . TBD: show here the piece of code . notification will not be effected unless setChanged has been invoked based on java.util.Observable class and java.util.Observer interface. Observable and ConcreteObservables are not in the same package Stress the fact that the state is a primitive but it must be boxed into an Integer . notifyObservers() is provided with 2 different signatures to pass the reference needed for the push mode. No arguments for pull-mode, an Object for the State in push-mode Stress also the fact that the Observers shall be aware of the type passed in the Object reference received in the push mode notifcation. TBD: A possible exercise: the state is a reference type (not a primitive int); in the push mode implementation, the subject erroneously passes the reference to the state without making a defensive copy; the observer modifies the state of the subject, though this was supposed to be private. TBD: a thought experiment: what about separating responsibilities by composition rather than subclassing; notification trigger cannot be protected, multiple observers lists can be . update() in java.util.Observer receives an Observable and an Object maintainedand switched, … more dynamic, more functional, more complex dependency installation, more error prone, more test demanding, … as usual in the confrontation of composition versus subclassing 9/98 10/98 Enrico Vicario - AA 18/19 Enrico Vicario - AA 18/19 Design Patterns [GOF] SW Engineering SW Engineering . TBD: a ottobre 18 e’ venuto bene descrivere tutto questo cosi’: . A system of 23 Design Patterns . inizia che c’e una calsse che gioca il ruolo di concrete subject e una . [GOF95] Erich Gamma, Richard Helm, Ralph Johnson, John Vlissides, quella di observer, con un constraint "Design Patterns, elements of reusable Object-Oriented software" . Si arriva facilmenet a dire che la resposnabilita’ di enorce the constraint e’ in capo al subject. Sviluppo oluzioen naïve con deu classi, di cui discutiamo limiti (e.g. notificare a piu’ oggetti e di tipo diverso, mescolare il business specific con la conoscenza di chi osserva, … e dettagli, in modo push o pull. Si arriva a un intent: vorremmo che l’observer dipende da subject m anon viceversa . Partiziona du resposnabilita’ ortogonali: ilbusiness specific e farsi osservare, e decidi di partizionare epr subclassing (open issue: potresti epr composizione?). La base class e’ quella riusata e quindi quelloc he serve a farsi osservare, e sta in un package separato. Descrivi le resposnabilita’d elel tre classi; pe rimplementare l’abstract subject non puoi invocare direttamente il concrete observer perche’ sta in un package esterno; deve essere generalizzato il concrete observer, che potrebeb avere tipi diversi, epr identificare l’interfaccia di chi osserva, e introduce l’interfaccia observer . In the next few slides: . emphasis on how a pattern is described, . Concludere con la discussion di chi dipende da chi. not on the pattern itself 11/98 12/98 3 Enrico Vicario - AA 18/19 description of a pattern (Observer) : WHEN Enrico Vicario - AA 18/19 description of a pattern (Observer) : HOW 1/3 SW Engineering SW Engineering . Intent . Structure . Define a one-to-many dependency between objects so that . Described through a class diagram (in a partially superseded notation) when one object changes state, . Close enough, c++ biased, but basically agnostic all its dependents are notified and updated automatically. Also known as . Publish & subscribe, Dependents, (Listener) . Motivation: . <a situation where the problem may occur> . A common side-effect of partitioning is the need to maintain consistency between related objects, without making the classes tightly coupled, so as because that preserve reusability. A User Interface based on the Model View Controller . Applicability . When a change to one object requires changing others, and you don't know how many objects need to be changed. 13/98 14/98 Enrico Vicario - AA 18/19 description of a pattern (Observer) : HOW 2/3 Enrico Vicario -1 AA page 18/19 aside on: Class, Responsibility, and Collaborations (CRC) cards SW Engineering SW Engineering . Participants . Subject: knows its observers; any number of Observer objects may observe a subject; provides an interface for attaching and detaching Observer objects. Observer: defines an updating interface for objects that should be notified of changes in a subject. ConcreteSubject: stores state of interest to ConcreteObserver objects; sends a notification to its observers when its state changes. ConcreteObserver: maintains a reference to a ConcreteSubject object; stores state that should stay consistent with the subject's; implements the Observer updating interface to keep its state consistent with the subject's. Collaborations . ConcreteSubject notifies its observers whenever a change occurs . After being informed of a change in the concrete subject, a ConcreteObserver object may query the subject for information. ConcreteObserver uses this information to reconcile its state with that of the subject. 15/98 16/98 4 Enrico Vicario - AA 18/19 description of a pattern (Observer) : HOW 3/3 Enrico Vicario - AA 18/19 description of a pattern (Observer) : CONSEQUENCES
Load more

Recommended publications
  • The Future of Embedded Software
    The Future of Embedded Software Edward A. Lee Professor, Chair of EE, and Associate Chair of EECS UC Berkeley ARTEMIS 2006 Annual Conference Graz, Austria May 22-24, 2006 Why Embedded Software? Why Now? “Information technology (IT) is on the verge of another revolution. Driven by the increasing capabilities and ever declining costs of computing and communications devices, IT is being embedded into a growing range of physical devices linked together through networks and will become ever more pervasive as the component technologies become smaller, faster, and cheaper... These networked systems of embedded computers ... have the potential to change radically the way people interact with their environment by linking together a range of devices and sensors that will allow information to be collected, shared, and processed in unprecedented ways. ... The use of [these embedded computers] throughout society could well dwarf previous milestones in the information revolution.” National Research Council Report Embedded Everywhere Lee, Berkeley 2 The Key Obstacle to Progress: Gap Between Systems and Computing | Traditional dynamic systems theory needs to adapt to better account for the behavior of software and networks. | Traditional computer science needs to adapt to embrace time, concurrency, and the continuum of physical processes. Lee, Berkeley 3 The Next Systems Theory: Simultaneously Physical and Computational The standard model: Embedded software is software on small computers. The technical problem is one of optimization (coping with limited resources). The Berkeley model: Embedded software is software integrated with physical processes. The technical problem is managing time and concurrency in computational systems. Lee, Berkeley 4 Obstacles in Today’s Technology: Consider Real Time Electronics Technology Delivers Timeliness… … and the overlaying software abstractions discard it.
    [Show full text]
  • Framework Overview with UML Diagrams
    Framework Overview with UML Diagrams Learn to Build Robust, Scalable and Maintainable Applications using PureMVC Framework Overview This document discusses the classes and interfaces of the PureMVC framework; illustrating their roles, responsibilities and collaborations with simple UML (Unified Modeling Language) diagrams. The PureMVC framework has a very narrow goal. That is to help you separate your application’s coding concerns into three discrete tiers; Model, View and Controller. In this implementation of the classic MVC design meta-pattern, the application tiers are represented by three Singletons (a class where only one instance may be created). A fourth Singleton, the Façade, simplifies development by providing a single interface for communications throughout the application. The Model caches named references to Proxies, which expose an API for manipulating the Data Model (including data retrieved from remote services). The View primarily caches named references to Mediators, which adapt and steward the View Components that make up the user interface. The Controller maintains named mappings to Command classes, which are stateless, and only created when needed. The Façade initializes and caches the Core actors (Model, View and Controller), and provides a single place to access all of their public methods. AUTHOR: Cliff Hall <[email protected]> LAST MODIFIED: 3/05/2008 Façade and Core The Façade class makes it possible for the Proxies, Mediators and Commands that make up most of our final application to talk to each other in a loosely coupled way, without having to import or work directly with the Core framework actors. When we create a concrete Façade implementation for our application, we are able to use the Core actors ‘out of the box’, incidental to our interaction with the Façade, minimizing the amount of API knowledge the developer needs to have to be successful with the framework.
    [Show full text]
  • Object-Oriented Analysis, Design and Implementation
    Undergraduate Topics in Computer Science Brahma Dathan Sarnath Ramnath Object-Oriented Analysis, Design and Implementation An Integrated Approach Second Edition Undergraduate Topics in Computer Science Undergraduate Topics in Computer Science (UTiCS) delivers high-quality instruc- tional content for undergraduates studying in all areas of computing and information science. From core foundational and theoretical material to final-year topics and applications, UTiCS books take a fresh, concise, and modern approach and are ideal for self-study or for a one- or two-semester course. The texts are all authored by established experts in their fields, reviewed by an international advisory board, and contain numerous examples and problems. Many include fully worked solutions. More information about this series at http://www.springer.com/series/7592 Brahma Dathan • Sarnath Ramnath Object-Oriented Analysis, Design and Implementation An Integrated Approach Second Edition 123 Brahma Dathan Sarnath Ramnath Department of Information and Computer Department of Computer Science Science and Information Technology Metropolitan State University St. Cloud State University St. Paul, MN St. Cloud, MN USA USA Series editor Ian Mackie Advisory Board Samson Abramsky, University of Oxford, Oxford, UK Karin Breitman, Pontifical Catholic University of Rio de Janeiro, Rio de Janeiro, Brazil Chris Hankin, Imperial College London, London, UK Dexter Kozen, Cornell University, Ithaca, USA Andrew Pitts, University of Cambridge, Cambridge, UK Hanne Riis Nielson, Technical University of Denmark, Kongens Lyngby, Denmark Steven Skiena, Stony Brook University, Stony Brook, USA Iain Stewart, University of Durham, Durham, UK A co-publication with the Universities Press (India) Private Ltd., licensed for sale in all countries outside of India, Pakistan, Bhutan, Bangladesh, Sri Lanka, Nepal, The Maldives, Middle East, Malaysia, Indonesia and Singapore.
    [Show full text]
  • The Problem with Threads
    The Problem With Threads Edward A. Lee Robert S. Pepper Distinguished Professor and Chair of EECS UC Berkeley -and - Senior Technical Adviser, director, and co-founder of BDTI Class #: ESC-211 Embedded Systems Conference (ESC) Tuesday, 3 April 2007 Concurrency in Software Practice, As of 2007 | Component technologies z Objects in C++, C#, or Java z Wrappers as service definitions | Concurrency z Threads (shared memory, semaphores, mutexes, …) z Message Passing (synchronous or not, buffered, …) | Distributed computing z Distributed objects wrapped in web services, Soap, CORBA, DCOM, … Lee, Berkeley & BDTI 2 z1 Observations Threads and objects dominate SW engineering. z Threads: Sequential computation with shared memory. z Objects: Collections of state variables with procedures for observing and manipulating that state. Even distributed objects create the illusion of shared memory through proxies. z The components (objects) are (typically) not active. z Threads weave through objects in unstructured ways. z This is the source of many software problems. Lee, Berkeley & BDTI 3 The Buzz “Multicore architectures will (finally) bring parallel computing into the mainstream. To effectively exploit them, legions of programmers must emphasize concurrency.” The vendor push: “Please train your computer science students to do extensive multithreaded programming.” Lee, Berkeley & BDTI 4 z2 Is this a good idea? Lee, Berkeley & BDTI 5 My Claim Nontrivial software written with threads, semaphores, and mutexes are incomprehensible to humans. Lee, Berkeley & BDTI 6 z3 To Examine the Problems With Threads and Objects, Consider a Simple Example “The Observer pattern defines a one-to-many dependency between a subject object and any number of observer objects so that when the subject object changes state, all its observer objects are notified and updated automatically.” Design Patterns, Eric Gamma, Richard Helm, Ralph Johnson, John Vlissides (Addison-Wesley Publishing Co., 1995.
    [Show full text]
  • Design Patterns in Ocaml
    Design Patterns in OCaml Antonio Vicente [email protected] Earl Wagner [email protected] Abstract The GOF Design Patterns book is an important piece of any professional programmer's library. These patterns are generally considered to be an indication of good design and development practices. By giving an implementation of these patterns in OCaml we expected to better understand the importance of OCaml's advanced language features and provide other developers with an implementation of these familiar concepts in order to reduce the effort required to learn this language. As in the case of Smalltalk and Scheme+GLOS, OCaml's higher order features allows for simple elegant implementation of some of the patterns while others were much harder due to the OCaml's restrictive type system. 1 Contents 1 Background and Motivation 3 2 Results and Evaluation 3 3 Lessons Learned and Conclusions 4 4 Creational Patterns 5 4.1 Abstract Factory . 5 4.2 Builder . 6 4.3 Factory Method . 6 4.4 Prototype . 7 4.5 Singleton . 8 5 Structural Patterns 8 5.1 Adapter . 8 5.2 Bridge . 8 5.3 Composite . 8 5.4 Decorator . 9 5.5 Facade . 10 5.6 Flyweight . 10 5.7 Proxy . 10 6 Behavior Patterns 11 6.1 Chain of Responsibility . 11 6.2 Command . 12 6.3 Interpreter . 13 6.4 Iterator . 13 6.5 Mediator . 13 6.6 Memento . 13 6.7 Observer . 13 6.8 State . 14 6.9 Strategy . 15 6.10 Template Method . 15 6.11 Visitor . 15 7 References 18 2 1 Background and Motivation Throughout this course we have seen many examples of methodologies and tools that can be used to reduce the burden of working in a software project.
    [Show full text]
  • Design Pattern Implementation in Java and Aspectj
    Design Pattern Implementation in Java and AspectJ Jan Hannemann Gregor Kiczales University of British Columbia University of British Columbia 201-2366 Main Mall 201-2366 Main Mall Vancouver B.C. V6T 1Z4 Vancouver B.C. V6T 1Z4 jan [at] cs.ubc.ca gregor [at] cs.ubc.ca ABSTRACT successor in the chain. The event handling mechanism crosscuts the Handlers. AspectJ implementations of the GoF design patterns show modularity improvements in 17 of 23 cases. These improvements When the GoF patterns were first identified, the sample are manifested in terms of better code locality, reusability, implementations were geared to the current state of the art in composability, and (un)pluggability. object-oriented languages. Other work [19, 22] has shown that implementation language affects pattern implementation, so it seems The degree of improvement in implementation modularity varies, natural to explore the effect of aspect-oriented programming with the greatest improvement coming when the pattern solution techniques [11] on the implementation of the GoF patterns. structure involves crosscutting of some form, including one object As an initial experiment we chose to develop and compare Java playing multiple roles, many objects playing one role, or an object [27] and AspectJ [25] implementations of the 23 GoF patterns. playing roles in multiple pattern instances. AspectJ is a seamless aspect-oriented extension to Java, which means that programming in AspectJ is effectively programming in Categories and Subject Descriptors Java plus aspects. D.2.11 [Software Engineering]: Software Architectures – By focusing on the GoF patterns, we are keeping the purpose, patterns, information hiding, and languages; D.3.3 intent, and applicability of 23 well-known patterns, and only allowing [Programming Languages]: Language Constructs and Features – the solution structure and solution implementation to change.
    [Show full text]
  • The Mvc-Web Design Pattern
    THE MVC-WEB DESIGN PATTERN Ralph F. Grove and Eray Ozkan Department of Computer Science, James Madison University, Harrisonburg, VA, U.S.A. Keywords: Web, Web framework, Design patterns, Model view controller pattern. Abstract: The Model-View-Controller design pattern is cited as the architectural basis for many web development frameworks. However, the version of MVC used for web development has changed as it has evolved from the original Smalltalk MVC. This paper presents an analysis of those changes, and proposes a separate Web-MVC pattern that more accurately describes how MVC is implemented in web frameworks. 1 INTRODUCTION 2 SMALLTALK MVC The Model-View-Controller (MVC) design pattern The MVC design pattern was introduced with the is cited as the basis for the architecture of several Smalltalk programming environment as a way to web application frameworks, such as ASP .Net, structure interactive applications in a modular Rails, and Struts. The MVC pattern was originally fashion (Krasner and Pope, 1988). As the name implemented in the Smalltalk-80 programming implies, the MVC design pattern decomposes environment developed at Xerox PARC (Goldberg functionality into three major components. and Robson, 1985). As it has been adapted for web The model component encapsulates the domain- frameworks the MVC pattern has evolved in specific structure and functionality of the different ways, resulting in implementations that application. This essentially includes the state of the differ significantly from each other and from the application and operations that can change state. The original Smalltalk implementation. model also maintains dependencies of view and The first goal of this paper is to present the MVC controller components, which it notifies in the event design pattern, both in its original form (section 2) of changes in state.
    [Show full text]
  • Java Design Patterns I
    Java Design Patterns i Java Design Patterns Java Design Patterns ii Contents 1 Introduction to Design Patterns 1 1.1 Introduction......................................................1 1.2 What are Design Patterns...............................................1 1.3 Why use them.....................................................2 1.4 How to select and use one...............................................2 1.5 Categorization of patterns...............................................3 1.5.1 Creational patterns..............................................3 1.5.2 Structural patterns..............................................3 1.5.3 Behavior patterns...............................................3 2 Adapter Design Pattern 5 2.1 Adapter Pattern....................................................5 2.2 An Adapter to rescue.................................................6 2.3 Solution to the problem................................................7 2.4 Class Adapter..................................................... 11 2.5 When to use Adapter Pattern............................................. 12 2.6 Download the Source Code.............................................. 12 3 Facade Design Pattern 13 3.1 Introduction...................................................... 13 3.2 What is the Facade Pattern.............................................. 13 3.3 Solution to the problem................................................ 14 3.4 Use of the Facade Pattern............................................... 16 3.5 Download the Source Code.............................................
    [Show full text]
  • Functional Programming at Work in Object-Oriented Programming
    Functional Programming at Work in Object-Oriented Programming Narbel version 2010 Narbel Functional Programming at Work in Object-Oriented Programming 1 A Claim about Programming Styles Claim: Adding functional programming capabilities to an object-oriented language leads to benefits in object-oriented programming design. Narbel Functional Programming at Work in Object-Oriented Programming 2 Existing Languages with a FP-OOP Mix Some old and less old languages with FP+OOP: For instance, Smalltalk, Common Lisp (CLOS). More recently, Python or Ruby. Notations: FP, Functional programming; OOP, Object-oriented programming, Narbel Functional Programming at Work in Object-Oriented Programming 3 FP techniques emulated in OOP Practices in OOP languages include emulations of FP techniques: C++ programmers: function pointers and overloadings of the () operator, i.e. “object-functions” or functors. Java programmers: anonymous classes and introspection/reflexion. Narbel Functional Programming at Work in Object-Oriented Programming 4 Existence of FP-OOP Comparison Points The idea of using FP to enrich OOP is old, see e.g. the discussions about the problem of the user-defined datatype extension: User-defined types and procedural data structures as complementary approaches to data abstraction. Reynolds. 1975. The Expression Problem. Wadler. 1998. Narbel Functional Programming at Work in Object-Oriented Programming 5 A Trend: FP Extensions for OO Languages A recent trend: to propose and include typed FP extensions in mainstream static OO languages. Extensions for C++ (see e.g. Laufer, Striegnitz, McNamara, Smaragdakis), and work in progress in the C++ standard committees. Java 7 expected to include FP constructs. C# offers FP constructs (even more in its 3.0 version).
    [Show full text]
  • Design Patterns Mock Test
    DDEESSIIGGNN PPAATTTTEERRNNSS MMOOCCKK TTEESSTT http://www.tutorialspoint.com Copyright © tutorialspoint.com This section presents you various set of Mock Tests related to Design Patterns Framework. You can download these sample mock tests at your local machine and solve offline at your convenience. Every mock test is supplied with a mock test key to let you verify the final score and grade yourself. DDEESSIIGGNN PPAATTTTEERRNNSS MMOOCCKK TTEESSTT IIII Q 1 - Which of the following describes the Composite pattern correctly? A - This pattern builds a complex object using simple objects and using a step by step approach. B - This pattern is used where we need to treat a group of objects in similar way as a single object. C - This pattern hides the complexities of the system and provides an interface to the client using which the client can access the system. D - This pattern is primarily used to reduce the number of objects created and to decrease memory footprint and increase performance. Q 2 - Which of the following describes the Decorator pattern correctly? A - This pattern allows a user to add new functionality to an existing object without altering its structure. B - This pattern is used where we need to treat a group of objects in similar way as a single object. C - This pattern hides the complexities of the system and provides an interface to the client using which the client can access the system. D - This pattern is primarily used to reduce the number of objects created and to decrease memory footprint and increase performance. Q 3 - Which of the following describes the Facade pattern correctly? A - This pattern allows a user to add new functionality to an existing object without altering its structure.
    [Show full text]
  • Developing GUI Applications. Architectural Patterns Revisited
    Developing GUI Applications: Architectural Patterns Revisited A Survey on MVC, HMVC, and PAC Patterns Alexandros Karagkasidis [email protected] Abstract. Developing large and complex GUI applications is a rather difficult task. Developers have to address various common soFtware engineering problems and GUI-speciFic issues. To help the developers, a number of patterns have been proposed by the software community. At the architecture and higher design level, the Model-View-Controller (with its variants) and the Presentation-Abstraction- Control are two well-known patterns, which specify the structure oF a GUI application. However, when applying these patterns in practice, problems arise, which are mostly addressed to an insuFFicient extent in the existing literature (iF at all). So, the developers have to find their own solutions. In this paper, we revisit the Model-View-Controller, Hierarchical Model-View- Controller, and Presentation-Abstraction-Control patterns. We first set up a general context in which these patterns are applied. We then identiFy Four typical problems that usually arise when developing GUI applications and discuss how they can be addressed by each of the patterns, based on our own experience and investigation oF the available literature. We hope that this paper will help GUI developers to address the identified issues, when applying these patterns. 1 Introduction Developing a large and complex graphical user interface (GUI) application for displaying, working with, and managing complex business data and processes is a rather difficult task. A common problem is tackling system complexity. For instance, one could really get lost in large number of visual components comprising the GUI, not to mention the need to handle user input or track all the relationships between the GUI and the business logic components.
    [Show full text]
  • Observer Pattern Using Aspect-Oriented Programming∗
    Observer Pattern using Aspect-Oriented Programming∗ Eduardo Kessler Piveta Laborat´oriode Banco de Dados e Engenharia de Software (LBDES) Centro Universit´arioLuterano de Palmas Universidade Luterana do Brasil 77054-970, Palmas, TO [email protected] Luiz Carlos Zancanella Laborat´oriode Seguran¸caem Computa¸c˜ao(LabSEC) Universidade Federal de Santa Catarina Campus Universit´ario 88040-900 Florian´opolis, SC [email protected] Abstract This paper discusses the representation and implementation of the Observer design pattern using aspect-oriented techniques. 1 Introduction Several object-oriented design techniques have been used to specify and implement design patterns efficiently. However there are several patterns that affect system modularity, where base objects are highly affected by the structures that the pattern requires. In other cases we want to apply a pattern to classes that already belong to a hierarchy. This could be hard depending on the pattern. ∗Copyright c 2003. Permission is granted to copy for the SugarloafPLoP 2003 Con- ference. All other rights are reserved. Observer Pattern using Aspect-Oriented Programming 2 Several patterns crosscut the basic structure of classes adding behav- ior and modifying roles in the classes relationship. As an example you could see the Observer pattern. When you have to implement the pat- tern, you should provide implementation to the Subject and Observer roles. The implementation of this roles adds a set of fields (Subject.observers, Observer.subject) and methods (Attach, Detach, Notify) to the concrete classes or to its superclasses, modifying the original structure of the subject and observer elements. Another example is the Visitor pattern. It’s main goal is to provide a set of operations to a class hierarchy without chang- ing the structure of the underlying classes.
    [Show full text]