Reconciling the 3-layer architectural style with the eclipse plug-in-based architecture

Authors:
David Ameller;Oriol Collell;Xavier Franch
Affiliations:
Universitat Politècnica de Catalunya, Barcelona, Brazil;Universitat Politècnica de Catalunya, Barcelona, Brazil;Universitat Politècnica de Catalunya, Barcelona, Brazil
Venue:
Proceedings of the 1st Workshop on Developing Tools as Plug-ins
Year:
2011

Citing 5
Cited 0

Software architecture: perspectives on an emerging discipline

Software architecture: perspectives on an emerging discipline
Pattern-oriented software architecture: a system of patterns

Pattern-oriented software architecture: a system of patterns
The 4+1 View Model of Architecture

IEEE Software
Model-Driven Development: A Metamodeling Foundation

IEEE Software
Dealing with Non-Functional Requirements in Model-Driven Development

RE '10 Proceedings of the 2010 18th IEEE International Requirements Engineering Conference

Quantified Score

Hi-index	0.00

Visualization

Abstract

Software architecture construction is the result of a complex decision-making process, in which competing alternatives need to be compared. For example, deciding between a web-based application or a plug-in-based application has a significant impact on the architecture, therefore in order to make the right choice all possible tradeoffs between them must be considered. Decisions need to be made in all architectural views, from the logical view in which architectural styles are chosen, to the development view in which types of modules are decided, to the deployment view where physical allocation is determined. In this paper we analyze the interactions between a 3-layer architecture at the logical view, and a plug-in-based development view implemented in Eclipse, focusing on the difficulties we overcome in a research project in order to make it work.