Challenges in developing a software architecture evolution tool as a plug-in

International Workshop on Developing Tools as Plug-Ins, TOPI

Volumn , Issue , 2013, Pages 13-18

  Barnes, Jeffrey M ^a   Garlan, David ^a  

^a CARNEGIE MELLON UNIVERSITY   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

EVOLUTION MODELING; EXISTING ARCHITECTURES; PLUG-IN DEVELOPERS; PROTOTYPE ARCHITECTURE; RECENT RESEARCHES; SOFTWARE ARCHITECTS; SOFTWARE ARCHITECTURE EVOLUTION; TOOLS FOR ARCHITECTURE;

ARCHITECTURE; SOFTWARE ARCHITECTURE;

TOOLS;

EID: 84889040013     PISSN: 23270748     EISSN: 23270772     Source Type: Conference Proceeding    
DOI: 10.1109/TOPI.2013.6597188     Document Type: Conference Paper

References (23)

1. J. M. Barnes, D. Garlan, and B. Schmerl, "Evolution styles: Foundations and models for software architecture evolution," Softw. & Syst. Model., in press. [Online]. Available: http://dx.doi.org/10.1007/s10270- 012-0301-9
2. O. Le Goaer et al., "Evolution styles to the rescue of architectural evolution knowledge," in Proc. SHARK'08, 2008, pp. 31-36.
3. M. Wermelinger and J. L. Fiadeiro, "A graph transformation approach to software architecture reconfiguration," Sci. Comput. Program., vol. 44, no. 2, pp. 133-155, Aug. 2002.
4. L. Grunske, "Formalizing architectural refactorings as graph transformation systems," in Proc. SNPD'05, 2005, pp. 324-329.
5. N. Brown et al., "Analysis and management of architectural dependencies in iterative release planning," in Proc. WICSA'11, 2011, pp. 103-112.
6. D. Garlan and B. Schmerl, "Ævol: A tool for defining and planning architecture evolution," in Proc. ICSE'09, May 16-24, 2009.
7. J. M. Barnes, "NASA's Advanced Multimission Operations System: A case study in software architecture evolution," in Proc. QoSA'12, 2012, pp. 3-12.
8. D. Tamzalit and T. Mens, "Guiding architectural restructuring through architectural styles," in Proc. ECBS'10, 2010, pp. 69-78.
9. P. Clements et al., Documenting Software Architecture: Views and Beyond, 2nd ed. Upper Saddle River, NJ: Addison-Wesley, 2010.
10. D. Garlan, R. Monroe, and D. Wile, "Acme: An architecture description interchange language," in Proc. CASCON'97, 1997, pp. 169-183.
11. B. Schmerl and D. Garlan, "AcmeStudio: Supporting style-centered architecture development," in Proc. ICSE'04, 2004, pp. 704-705.
12. MagicDraw Open API Version 17.0.1 User Guide, No Magic, Inc., 2011. [Online]. Available: http://nomagic.com/files/manuals/ MagicDraw%20OpenAPI%20UserGuide.pdf
13. H. P. Breivold, I. Crnkovic, and M. Larsson, "A systematic review of software architecture evolution research," Inform. & Software Tech., vol. 54, no. 1, pp. 16-40, Jan. 2012.
14. P. Jamshidi et al., "A framework for classifying and comparing architecturecentric software evolution research," in Proc. CSMR'13, 2013, to appear.
15. J. Bloch, "How to design a good API and why it matters," in Proc. OOPSLA'06, 2006, pp. 506-507.
16. K. Cwalina and B. Abrams, Framework Design Guidelines: Conventions, Idioms, and Patterns for Reusable.NET Libraries, 2nd ed. Upper Saddle River, NJ: Addison-Wesley, 2009.
17. M. P. Robillard, "What makes APIs hard to learn? Answers from developers," IEEE Software, vol. 26, no. 6, pp. 27-34, 2009.
18. M. F. Zibran, F. Z. Eishita, and C. K. Roy, "Useful, but usable? Factors affecting the usability of APIs," in Proc. WCRE'11, 2011, pp. 151-155.
19. C. Jaspan and J. Aldrich, "Checking framework interactions with relationships," in Proc. ECOOP'09, 2009, pp. 27-51.
20. D. S. Eisenberg, J. Stylos, and B. A. Myers, "Apatite: A new interface for exploring APIs," in Proc. CHI'10, 2010, pp. 1331-1334.
21. S. Roy Choudhary et al., "Platform support for developing testing and analysis plug-ins," in Proc. TOPI'11, 2011, pp. 16-19.
22. L. Prechelt and K. Beecher, "Four generic issues for tools-as-plugins illustrated by the distributed editor Saros," in Proc. TOPI'11, 2011, pp. 9-11.
23. M. Abi-Antoun et al., "Differencing and merging of architectural views," in Proc. ASE'06, 2006, pp. 47-58.