Hooking into object-oriented application frameworks

Froehlich, Gary K.; Hoover, H. James; Liu, Ling; Sorenson, Paul

doi:10.1145/253228.253432

Cited by 80 publications

(64 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…In [10], Froelich et al resort to a Hooks-model to describe the framework customization points and use it to instantiate the SEAF (Size Engineering Application Framework). Their approach is similar to this as is relies on documentation describing the customization points (hooks) and uses it to know where to instantiate the framework.…”

Section: What Do You Need To Learn About a Framework In Order To Instmentioning

confidence: 99%

See 1 more Smart Citation

Patterns for understanding frameworks

Flores¹,

Aguiar²

2008

Proceedings of the 15th Conference on Pattern Languages of Programs

View full text Add to dashboard Cite

Learning and understanding a framework is usually a major obstacle to its effective reuse. Before being able to use a framework successfully, users often need to surpass a steep learning curve by spending a lot of effort understanding its underlying architecture and design principles. This is mainly due to users having to understand not only single isolated classes, but also complex designs of several classes whose instances collaborate for many different purposes, and using many different mechanisms. In addition, frameworks are also full of delocalized plans, and use inheritance and delegation intensively, which makes their design more difficult to grasp at a first glance. How to obtain the necessary information from the framework itself and its accompanying documentation is the main problem with framework understanding. Considering its importance, this paper presents an initial attempt to capture, in the pattern form, a set of proven solutions to recurrent problems of understanding frameworks. The fundamental objective of this work is to help non-experts on being more effective when trying to learn and understand object-oriented frameworks.The introduction of reuse in a software development process implies splitting the traditional software life cycle into two interrelated cycles: one focused on developing reusable assets, and another focused on searching and reusing reusable assets already developed.A framework is a reusable design together with an implementation. It consists of a collection of cooperating classes, both abstract and concrete, which embody an abstract design for solutions to problems in an application domain [15][16] [17].In the particular case of framework-based application development, the traditional life cycle can be organized in: a framework development life cycle devoted to build frameworks, corresponding to the abstraction phase of software reuse; and an application development life cycle (also known as framework usage) devoted to develop applications based on frameworks, corresponding to the selection, specialization, and integration phases of software reuse.Although the activities of framework development and application development are often separate and assigned to different teams, the knowledge to be shared between them is large, as the design of a framework for a domain requires considerable past experience in designing applications for that domain.In application development, frameworks act as generative artefacts as they are used as a foundation for several applications of the framework's domain. This contrasts with the traditional way of developing applications, where each application is developed from scratch. The most distinctive difference between the traditional and the framework-based development of applications is the need to map the structure of the problem to be solved onto the structure of the framework, thereby forcing the application to reuse the design of the framework. The positive side of this is that we don't need to design the application from scratch. But, on th...

show abstract

Section: What Do You Need To Learn About a Framework In Order To Instmentioning

confidence: 99%

“…The more mature a framework is, the more design patterns will it encompass. Design patterns aggregate these "hot spots" or CUSTOMIZATION POINTS [4]: areas of flexibility we can "hook" [10] into and take full advantage of the framework's reusability.…”

Section: How Do You Understand the Design Internals Of A Framework?mentioning

confidence: 99%

Patterns for understanding frameworks

Flores¹,

Aguiar²

2008

Proceedings of the 15th Conference on Pattern Languages of Programs

View full text Add to dashboard Cite

show abstract

“…Other research projects [18,19,20,21] help plugin developers by finding or encoding known good patterns for using frameworks. The proposed work differs significantly in that it does not suggest a way to complete the task, but it finds defects once a task has been started.…”

Section: Related Workmentioning

confidence: 99%

Checking semantic usage of frameworks

Jaspan

Aldrich

2007

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

View full text Add to dashboard Cite

Software frameworks are difficult for plugin developers to use, even when they are well designed and documented. Some of these difficulties stem from the many constraints that frameworks impose on plugin code. These constraints might restrict operations from being called on certain objects, or they might restrict how long an object is available. Additionally, the constraints are relative to the current context of the plugin, and they can involve multiple, interacting framework objects. This paper proposes a lightweight specification system and analysis to check plugins from a semantic perspective, rather than a purely structural view.

show abstract

“…Froehlich, Hoover, Liu, and Sorenson suggest semiformal templates for describing specialization points of frameworks [13] in the form of hooks. A hook presents a recipe as an imperative algorithm.…”

Section: Tool Support For Framework Specializationmentioning

confidence: 99%

“…Ideologically, FRED is a descendant of the "cookbook" concept [8,3,9,10,11]. Related approaches include also motifs [12] and hooks [13]. The current implementation of FRED aims at supporting frameworks written in Java, but in principle the approach is not tied to any particular language.…”

Section: Introductionmentioning

confidence: 99%

Annotating reusable software architectures with specialization patterns

Hakala

Hautamäki²,

Koskimies³

et al.

Proceedings Working IEEE/IFIP Conference on Software Architecture

View full text Add to dashboard Cite

An application framework is a collection of classes implementing the shared architecture of a family of applications. It is shown how the specialization interface ("hot spots") of a framework can be annotated with specialization patterns to provide task-based guidance for the framework specialization process. The specialization patterns define various structural, semantic, and coding constraints over the applications derived from the framework. We also present a tool that supports both the framework development process and the framework specialization process, based on the notion of specialization patterns. We will outline the basic concepts of the tool and discuss techniques to identify and specify specialization patterns as required by the tool. These techniques have been applied in realistic case studies for creating programming environments for application frameworks.

show abstract

Hooking into object-oriented application frameworks

Cited by 80 publications

References 13 publications

Patterns for understanding frameworks

Patterns for understanding frameworks

Checking semantic usage of frameworks

Annotating reusable software architectures with specialization patterns

Contact Info

Product

Resources

About