Architecture-driven modelling and analysis

Conferences in Research and Practice in Information Technology Series

Volumn 69, Issue , 2006, Pages 3-17

  Garlan, David ^a   Schmerl, Bradley ^a  

^a Carnegie Mellon University   (United States)

Author keywords

Architecture analysis; Software architecture

Indexed keywords

ARCHITECTURE ANALYSIS; CURRENT PRACTICES; FORMAL APPROACH; GAIN INSIGHT; MODELLING AND ANALYSIS; QUALITY ATTRIBUTES; RESEARCH RESULTS; SOFTWARE QUALITY;

ARCHITECTURAL DESIGN; COMPUTER SOFTWARE SELECTION AND EVALUATION;

SOFTWARE ARCHITECTURE;

EID: 84873679671     PISSN: 14451336     EISSN: None     Source Type: Conference Proceeding    
DOI: None     Document Type: Conference Paper

References (29)

1. Aldrich, J., Chambers, C., and Notkin, D. (2002): ArchJava: Connecting Software Architecture to Im-plementation. Proc. ICSE 24, Orlando, Florida.
2. Allen, R. (1997): A Formal Approach to Software Archi-tecture. Ph.D. Thesis, Carnegie Mellon University School of Computer Science Technical Report CMU-CS-97-144.
3. Allen, R., Garlan, D. (1994): Formalizing Architectural Connection. Proc. the 1994 International Conference on Software Engineering.
4. Allen, R. and Garlan, D. (1997): A Formal Basis for Ar-chitectural Connection. ACM Transactions on Software Engineering and Methodology, 6(3).
5. Allen, R., Garlan, D., and Ivers, J. (1998): Formal model-ing and analysis of the HLA Component Integration Standard. Proc. the 6th International Symposium on the Foundations of Software Engineering (FSE-6), Lake Beuna Vista, Florida.
6. Balasubramaniam, D., Morrison, R., Kirby, G.N.C, Mickan, K., and Norcross, S. (2004): ArchWare ADL Release 1 User Reference Manual. ArchWare Project IST-2001-32360 Report D4.3.
7. Bass, L., Clements, P., and Kazman, R. (2003): Software Architecture in Practice, 2nd Edition, Addison-Wesley.
8. Boehm, B., and Turner, R. (2003): Balancing Agility and Discipline: A Guide for the Perplexed. Addison Wesley Professional.
9. Bosch. J. (2000): Design and Use of Software Architec-tures: Adopting and Evolving a Product Line Ap-proach. Addison Wesley.
10. Brookes, F. (1975): The Mythical Man Month: Essays on Software Engineering. Addison Wesley Professional.
11. Buschmann, F., Meunier, R., Rohnert, H., Sommerlad, P. and Stal. M. (1996): Pattern-Oriented Software Archi-tecture, Volume 1: A System of Patterns, Wiley.
12. Butler, S. (2002): Security Attribute Evaluation Method: A Cost-Benefit Approach. Proc. 24th International Conference on Software Engineering (ICSE2002). Or-lando, Florida, pp. 232-240.
13. Clements, P., Kazman, R., and Klein, M. (2001): Evaluat-ing Software Architectures. Addison Wesley Profes-sional: The SEI Series in Software Engineering.
14. Clements, P. and Northrop, L. (2001): Software Product Lines: Practices and Patterns. Addison Wesley SEI Series in Software Engineering,
15. Clements, P., Bachmann, F., Bass, L., Garlan, D., Ivers, J., Little, R., Nord, R., and Stafford, J. (2002): Docu-menting Software Architectures: Views and Beyond, Addison Wesley.
16. Dashofy, E., van der Hoek, A., and Taylor, R.N. (2002) An Infrastructure for the Rapid Development of XML-based Architecture Description Languages. Proc. 24th International Conference on Software Engineering (ICSE2002). Orlando, Florida.
17. Di Marco, A. and Inverardi, P. (2004): Compositional Generation of Software Architecture Performance QN Models. Proc. the 4th Working IEEE/IFIP Conference on Software Architecture (WICSA'04). Oslo, Norway.
18. Dvorak, D., and Reinholtz, W.K. (2004): Separating Es-sential from Incidentals, An Execution Architecture for Real-Time Control Systems. Proc. 7th IEEE Interna-tional Symposium on Object-Oriented Real-Time Dis-tributed Computing. Austria.
19. Garlan, D., Monroe, R., and Wile, D. (2000)"Acme: Ar-chitectural Description of Component-Based Systems." In Foundations of Component-Based Systems, Cam-bridge University Press.
20. Garlan, D., Allen, R.J., and Ockerbloom, J. (1994): Ex-ploiting Style in Architectural Design, Proc. of ACM SIGSOFT '94 Symposium on the Foundations of Soft-ware Engineering.
21. Garlan, D.; Kompanek, A. J.; & Cheng, S.-W. (2002): Reconciling the Needs of Architectural Description with Object Modeling Notations. Science of Computer Programming 44, 1, pp. 23-49.
22. Garlan, D., Reinholtz, W.K., Schmerl, B., Sherman, N., and Tseng, T. (2005): Bridging the Gap between Sys-tems Design and Space Systems Software. Proc. 29th Annual IEEE/NASA Software Engineering Workshop (SEW-29), Greenbelt, MD.
23. Gorlick, M.M. and Razouk, R.R. (1991): Using Weaves for Software Construction and Analysis. Proc. 13th In-ternational Conference on Software Engineering (ICSE13). IEEE Computer Society Press.
24. Hoare, C.A.R. (1995): Communicating Sequential Proc-esses. Prentice Hall.
25. IEEE. (2000): IEEE Recommended Practice for Architec-tural Description of Software Intensive Systems (IEEE Std 1471-2000).
26. Inverardi, P. and Wolf, A. (1995): Formal Specification and Analysis of Software Architecture Using the Chemical Abstract Machine Model. IEEE Transactions on Software Engineering 21(4).
27. Jackson, D. (2002): Alloy: A Lightweight Object Model-ing Notation. IEEE Transactions on Software Engi-neering and Methodology 11(2).
28. Jensen, K. (1994): An Introduction to the Theoretical Aspects of Coloured Petri Nets. In: J.W. de Bakker, W.-P. de Roever, G. Rozenberg (eds.): A Decade of Concurrency, Lecture Notes in Computer Science vol. 803, Springer-Verlag, pp. 230-272.
29. Kazman, R. and Carriere. S.J. (1999): Playing Detective: Reconstructing Software Architecture from Available Evidence, Journal of Automated Software Engineering 6(2), 1999.