Architecture decisions: Demystifying architecture

IEEE Software

Volumn 22, Issue 2, 2005, Pages 19-27

  Tyree, Jeff ^a   Akerman, Art ^a  

^a Capital One Services Inc   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

COMPUTER ARCHITECTURE; DATA WAREHOUSES; DATABASE SYSTEMS; DECISION SUPPORT SYSTEMS; MIDDLEWARE; SYSTEMS ANALYSIS;

ARCHITECTURE DECISIONS; ARCHITECTURE DEVELOPMENT PROCESS; INTERACTIVE APPROVAL PROCESSING; TECHNICAL STAKEHOLDERS;

SOFTWARE ENGINEERING;

EID: 17644408022     PISSN: 07407459     EISSN: None     Source Type: Journal    
DOI: 10.1109/MS.2005.27     Document Type: Article

References (16)

1. J. Putman, Architecting With RM-ODP, Prentice Hall, 2001.
2. P. Kruchten, "The 4+1 View Model of Architecture," IEEE Software vol. 12, no. 6, 1995, pp. 42-50.
3. P. Kruchten, The Rational Unified Process: An Introduction, Addison-Wesley, 2000.
4. R. Malan and D. Bredemeyer, " Less is More with Minimalist Architecture," IEEE IT Professional, vol. 4, no. 5, 2002, pp. 46-48.
5. L. Bass, P. Clements, and R. Kazman, Software Architecture in Practice, Addison-Wesley, 2003.
6. G. Flurry and W. Vicknair, "The IBM Application Framework for e-Business," IBM Systems J., vol. 40, no. 1, 2001, pp. 8-24.
7. P. Louridas and P. Loucopoulos, "A Generic Model for Reflective Design," ACM Trans. Software Eng. and Methodology, vol. 9, no. 2, 2000, pp. 199-237.
8. J.K. Kyaruzi and J. van Katwijk, "Beyond Components-Connections-Constraints: Dealing with Software Architecture Difficulties," Proc. 14th IEEE Int'l Conf. Automated Software Eng. IEEE Press. 1999, pp. 235-242.
9. A. Akerman, J. Tyree, and L. Coglianese, "An Architectural Process for System Evolution," Enterprise Architect Magazine, vol. 2, no. 1, 2004, www.ftponline.com/ea/magazine/spring/features/aakerman.
10. IEEE Std. 1471-2000, Recommended Practice for Architectural Description of Software-Intensive Systems, IEEE, 2000.
11. S. Komiya, "A Model for the Recording and Reuse of Software Design Decisions and Decision Rationale," Proc. 3rd Int'l Conf. Software Reuse: Advances in Software Reusability, IEEE Press, 1994, pp. 200-201.
12. L. Karsenty, "An Empirical Evaluation of Design Rationale Documents," Proc. SIGCHI Conf. Human Factors in Computing Systems: Common Ground (CHI 96), M.J. Tauber, ed., ACM Press. 1996, pp. 150-156.
13. P. Clements et al., Documenting Software Architectures: Views and Beyond, Pearson Education, 2003.
14. J. Savolainen, "Tools for Design Rationale Documentation in the Development of a Product Family," 1999, www.ece.utexas.edu /∼perry/ prof/wicsa1/final/savolainen.pdf.
15. F.M.T. Brazier et al., "Modeling Conflict Management in Design: An Explicit Approach," Artificial Intelligence for Eng. Design, Analysis and Manufacturing (AIEDAM), special issue on conflict management in design, vol. 9, no. 4, 1995. pp. 353-366.
16. R. Malan and D. Bredemeyer, "Software Architecture: Central Concerns. Key Decisions," 2002, www.bredemeyer.com/pdf_files/ ArchitectureDefinition.PDF.