Studying the evolution of the Eclipse Java editor
Proceedings of the 2007 OOPSLA workshop on eclipse technology eXchange
Taxonomy of architectural style usage
Proceedings of the 2006 conference on Pattern languages of programs
A DVB-MHP web browser to pursue convergence between Digital Terrestrial Television and Internet
Multimedia Tools and Applications
Using systematic mapping to explore software architecture knowledge
Proceedings of the 2010 ICSE Workshop on Sharing and Reusing Architectural Knowledge
Empirically-grounded reference architectures: a proposal
Proceedings of the joint ACM SIGSOFT conference -- QoSA and ACM SIGSOFT symposium -- ISARCS on Quality of software architectures -- QoSA and architecting critical systems -- ISARCS
An aspect-oriented reference architecture for Software Engineering Environments
Journal of Systems and Software
A framework for analysis and design of software reference architectures
Information and Software Technology
SP 800-28 Version 2. Guidelines on Active Content and Mobile Code
SP 800-28 Version 2. Guidelines on Active Content and Mobile Code
Enhancing OSGi with explicit, vendor independent extra-functional properties
TOOLS'12 Proceedings of the 50th international conference on Objects, Models, Components, Patterns
Information and Software Technology
Hi-index | 0.00 |
A reference architecture for a domain captures the fundamental subsystems common to systems of that domain as well as the relationships between these subsystems. Having a reference architecture available can aid both during maintenance and at design time: it can improve understanding of a given system, it can aid in analyzing tradeoffs between different design options, and it can serve as a template for designing new systems and re-engineering existing ones. In this paper, we examine the history of the web browser domain and identify several underlying phenomena that have contributed to its evolution. We develop a reference architecture for web browsers based on two well known open source implementations, and we validate it against two additional implementations. Finally, we discuss our observations about this domain and its evolutionary history; in particular, we note that the significant reuse of open source components among different browsers and the emergence of extensive web standards have caused the browsers to exhibit "convergent evolution."