skip to main content
10.1145/643603.643618acmconferencesArticle/Chapter ViewAbstractPublication PagesmodularityConference Proceedingsconference-collections
Article

Model-view-controller and object teams: a perfect match of paradigms

Published:17 March 2003Publication History

ABSTRACT

From the early days of object-oriented programming, the model-view-controller paradigm has been pursued for a clear design which separates different responsibilities within an interactive application. In contrast to its untyped implementation in Smalltalk, any implementation in a statically typed language involves certain trade-offs which either blur the clear structure, destroy the intended independence, or introduce undue administrative overhead. Each alternative creates a different caricature of the originally crisp architecture. The programming model Object Teams provides a new modeling unit called Team plus a number of binding mechanisms by which a Team and its contained roles can be bound to existing parts of an application. It turns out that these mechanisms fit nicely for implementing a clear model-view-controller design not only for single elements but also for complex structures of GUI elements plus their binding to complex model structures. We furthermore propose to use the model-view-controller paradigm as a benchmark for AOSD approaches, since it combines a set of typical problems concerning the separation and integration of concerns.

References

  1. Christof Binder. Aspectual Collaborations: Erweiterung des Java-Compilers für verbesserte Modularität durch aspekt-orientierte Techniken. Diploma Thesis (German), TU Berlin, 2002.Google ScholarGoogle Scholar
  2. J. Brichau, W. De Meuter, and K. De Volder. Jumping aspects, position paper at the workshop "Aspects and Dimensions of Concerns", ECOOP 2000, June 2000.Google ScholarGoogle Scholar
  3. R. Cardone, A. Brown, S. McDirmid, and C. Lin. Using mixins to build flexible widgets. In Proc. AOSD, pages 76--85, 2002. ACM Press. Google ScholarGoogle ScholarDigital LibraryDigital Library
  4. E. Gamma, R. Helm, R. Johnson, and J. Vlissides. Design Patterns - Elements of Reusable Object-Oriented Software. Addison Wesley, 1995. Google ScholarGoogle ScholarDigital LibraryDigital Library
  5. S. Herrmann and M. Mezini. Combining composition styles in the evolvable language LAC. In Proc. of ASoC workshop at the 23nd ICSE, 2001.Google ScholarGoogle Scholar
  6. Stephan Herrmann. Object teams: Improving modularity for crosscutting collaborations. In Proc. Net Object Days 2002, www.netobjectdays.org, 2002. Google ScholarGoogle ScholarDigital LibraryDigital Library
  7. Christine Hundt. Bytecode-Transformation zur Laufzeitunterstützung von aspekt-orientierter Modularisierung mit ObjectTeams/Java. Diploma Thesis (German), TU Berlin, 2003.Google ScholarGoogle Scholar
  8. G. E. Krasner and S. T. Pope. A cookbook for using the model-view-controller user interface paradigm in smalltalk-80. JOOP, Aug./Sept. 1988. Google ScholarGoogle ScholarDigital LibraryDigital Library
  9. K. Lieberherr, D. Lorenz, and M. Mezini. Programming with aspectual components. In Technical Report, Northeastern University, April 1999.Google ScholarGoogle Scholar
  10. M. Mezini and K. Ostermann. Integrating independent components with on-demand remodularization. In Proc. of OOPSLA '02, 2002. Google ScholarGoogle ScholarDigital LibraryDigital Library
  11. Object Teams home page. http://www.ObjectTeams.org.Google ScholarGoogle Scholar
  12. R. Taylor and G. Johnson. Separations of concerns in the chiron-1 user interface development and mangagement system. In Proc. of INTERCHI'93, pages 367--374. ACM, 1993. Google ScholarGoogle ScholarDigital LibraryDigital Library
  13. D. Thomas and A. Hunt. Programming Ruby: A Pragmatic Programmer's Guide, Addison Wesley, 2000. Google ScholarGoogle ScholarDigital LibraryDigital Library
  14. Matthias Veit. Evaluierung modularer Software-entwicklung mit "Object Teams" am Beispiel eines Projektmanagementsystems. Diploma Thesis (German), TU Berlin, 2002.Google ScholarGoogle Scholar
  15. Matthias Veit. Ruby Object Teams. http://sourceforge.net/projects/robjectteam.Google ScholarGoogle Scholar
  16. Gimp ToolKit http://www.gtk.org/Google ScholarGoogle Scholar

Index Terms

  1. Model-view-controller and object teams: a perfect match of paradigms

          Recommendations

          Comments

          Login options

          Check if you have access through your login credentials or your institution to get full access on this article.

          Sign in
          • Published in

            cover image ACM Conferences
            AOSD '03: Proceedings of the 2nd international conference on Aspect-oriented software development
            March 2003
            206 pages
            ISBN:1581136609
            DOI:10.1145/643603

            Copyright © 2003 ACM

            Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than ACM must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected]

            Publisher

            Association for Computing Machinery

            New York, NY, United States

            Publication History

            • Published: 17 March 2003

            Permissions

            Request permissions about this article.

            Request Permissions

            Check for updates

            Qualifiers

            • Article

            Acceptance Rates

            Overall Acceptance Rate41of139submissions,29%

          PDF Format

          View or Download as a PDF file.

          PDF

          eReader

          View online with eReader.

          eReader