The framework life span

Brugali, Davide; Menga, Giuseppe; Aarsten, Amund

doi:10.1145/262793.262806

Cited by 29 publications

(19 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Thus, API developers have a delicate balance to strike between providing configurable functionality and simple interfaces [6]. Inevitably, the wrong balance is sometimes chosen, as the actual usage is different from the expected usage; APIs need to evolve or to be re-documented to rectify this disparity [21,2,4]. Finding the right balance is difficult for API producers because they cannot directly see how their APIs are being used; API consumers can also benefit from seeing how other developers have used the APIs they are interested in.…”

Section: Introductionmentioning

confidence: 99%

Informing Eclipse API production and consumption

Holmes

Walker

2007

Proceedings of the 2007 OOPSLA Workshop on Eclipse Technology eXchange

View full text Add to dashboard Cite

Application programming interfaces (APIs) inform application developers as to the functionality provided by a library and how to interact with it. APIs are a double-edged sword: if they do not permit the needed functionality to be accessed and adapted as needed, they are obstructing; if they permit all things to all people, they are complex, leading application developers to have difficulty understanding how to use them correctly. Thus, the developers of APIs have a delicate balance to strike between providing configurable functionality and simple interfaces. Inevitably, the wrong balance is sometimes chosen, as the actual usage is different from the expected usage; APIs need to evolve, or to be re-documented to account for this disparity. In this paper we propose a simple technique for quantitatively determining how existing APIs are used, and demonstrate its application to Eclipse. This technique would enable application developers to more easily understand how others have used the APIs and would allow API developers to more easily understand how their APIs are being used.

show abstract

Section: Introductionmentioning

confidence: 99%

Informing Eclipse API production and consumption

Holmes

Walker

2007

Proceedings of the 2007 OOPSLA Workshop on Eclipse Technology eXchange

View full text Add to dashboard Cite

show abstract

“…These patterns can serve as a Lingua Franca for design (Erickson, 2000) that helps end-users and developers in communication. Johnson (1997) and Brugali et al (1997) pointed out that the power of pattern languages lies in its potential for serving as an educational and communicative vehicle.…”

Section: Introductionmentioning

confidence: 99%

Groupware development support with technology patterns

Lukosch

Schümmer

2006

International Journal of Human-Computer Studies

View full text Add to dashboard Cite

“…Very often, a new application builds 30 on legacy systems. The architecture of this kind of systems consists in a hierarchy of component layers [42]. A higher-level component (e.g., a shop controller or a cell controller in Figure 11), acting as a client, integrates lower-level components, which act as servers (e.g., the cell controller, the machines, transports, and buffers).…”

mentioning

confidence: 99%

Enterprise frameworks: issues and research directions

et al. 2002

Self Cite

View full text Add to dashboard Cite

SUMMARY 5Enterprise frameworks are a special class of application frameworks. They are distinguished from other application frameworks in terms of scale and focus. In terms of focus, application frameworks typically cover one particular aspect of an application, either a domain-dependent aspect (e.g., billing in a web-based customer-to-business ordering system), or a computational infrastructure aspect such as distribution, manmachine interface, or persistence, etc. Generally, an application framework alone delivers no useful end-10 user function. With infrastructure frameworks, we still have to plug in domain functionalities, while with domain frameworks, we need to set-up the infrastructure. In contrast, enterprise frameworks embody a reference architecture for an entire application, covering both the infrastructure aspects of the application, and much of the domain-specific functionality. Instantiating an enterprise framework is nothing short of application engineering, where the architecture and many of the components are reusable. While creativity 15 and continual improvement may be the major ingredients for building a good application framework, anything related to enterprise frameworks, be it building, documenting, or instantiating them, is complex and requires careful design and planning. In this paper, we identify the issues involved in building, using, and maintaining enterprise frameworks, both from research and practical perspective.

show abstract

The framework life span

Cited by 29 publications

References 7 publications

Informing Eclipse API production and consumption

Informing Eclipse API production and consumption

Groupware development support with technology patterns

Enterprise frameworks: issues and research directions

Contact Info

Product

Resources

About