Design fragments make using frameworks easier

Authors:
George Fairbanks;David Garlan;William Scherlis
Affiliations:
Carnegie Mellon University, Pittsburgh, PA;Carnegie Mellon University, Pittsburgh, PA;Carnegie Mellon University, Pittsburgh, PA
Venue:
Companion to the 21st ACM SIGPLAN symposium on Object-oriented programming systems, languages, and applications
Year:
2006

Citing 6
Cited 1

Frameworks = (components + patterns)

Communications of the ACM
Acme: architectural description of component-based systems

Foundations of component-based systems
Annotating Reusable Software Architectures with Specialization Patterns

WICSA '01 Proceedings of the Working IEEE/IFIP Conference on Software Architecture
Contributing to Eclipse: Principles, Patterns, and Plugins

Contributing to Eclipse: Principles, Patterns, and Plugins
What Can Programmer Questions Tell Us About Frameworks?

IWPC '05 Proceedings of the 13th International Workshop on Program Comprehension
Observations on the assured evolution of concurrent Java programs

Science of Computer Programming - Special issue: Concurrency and synchronization in Java programs

Checking semantic usage of frameworks

LCSD '07 Proceedings of the 2007 Symposium on Library-Centric Software Design

Quantified Score

Hi-index	0.00

Visualization

Abstract

Object oriented frameworks impose new burdens on programmers that libraries did not, such as requiring the programmer to understand the method callback sequence, respecting behavior constraints within these methods, and devising solutions within a constrained solution space. To overcome these burdens, we express the repeated patterns of engagement with the framework as a design fragment. Design fragments give programmers immediate benefit through tool-based conformance assurance and long-term benefit through expression of design intent.