Abstract
Architectural designs are an important means to manage the development and deployment of information technology (IT). Much debate has been going on about a proper definition of architecture in IT and about how to describe it. In 2000, the IEEE Std 1471 proposed a model of an architecture description and its context, which has been greeted with a warm welcome by many professionals in IT, but has not been applied much yet. In this paper the distance between IEEE Std 1471 and current practice is investigated. We have studied four real-life architecture descriptions from the practice of a bank and consultancy firm. These documents propose strategic decisions about application portfolios and were compiled without reference to IEEE Std 1471. Our research questions were: which parts of the document are, in the perception of the authors of those documents, relevant to which concerns of stakeholders? And, does this `relevancy pattern' suggest an alternative organization in concern-related views? In other words, can the existing documents be (manually) re-engineered to IEEE Std 1471 documents? The answers to these questions enable authors to communicate more effectively to the stakeholders and can be input to future automated document generation.
We found that the `relevancy pattern' is very scattered, and that an alternative organization is not evident. Most concerns are addressed by a relatively small, but each time very different, subset of the document. So re-engineering these documents to IEEE Std 1471 documents would incur an almost complete rewrite. Our research makes it very understandable that readers complain about too much information. Some stakeholders might well have difficulty finding the information of their interest.
The authors of the architecture documents found this investigation a worthwhile exercise, one which they think could be developed further into an evaluation instrument for this type of documentation. Conversely, authors of architecture documents do well to make their stakeholders and their concerns explicit up front.
Similar content being viewed by others
References
Avison, D., Lau, F., Myers, M.D., and Nielsen P.A. 1999. Action research. Communications of the ACM, 42(1):94–97.
Baskerville, R. 1999. Investigating Information Systems with Action Research. Communications of the Association for Information Systems, 2(19):1–31.
Bernhard, H. Boar. 1998. Constructing Blueprints for Enterprise IT Architectures. Wiley.
Clements, P., Bachman, F., Bass, L., Garlan, D., Ivers, J., Little, R., Nord, R., and Stafford, J. 2003. Documenting Software Architectures: Views and Beyond.Addison-Wesley, Boston.
Dennis Smith, Thomas, Bill, Tilley, Scott. Documentation for software engineers: What is needed to aid system understanding. workshop at SIGDOC 2001, Annual ACM Conference on Systems Documentation, http://doi.acm.org/10.1145/501516.501570
Fowler, M. 1999. UML Distilled: A Brief Guide to the Standard Object ModelingLanguage. Addison-Wesley, Reading, Massachusetts.
Hargis, Gretchen. 2000. Readability and computer documentation, ACM Journal ofComputer Documentation. 24(3).
Hilliard, R. 1999. Using the UML for architectural description, proceedings of ≪UML≫ ′99 The Unified Modeling Language, Second International Conference, Lecture Notes inComputer Science volume 1723, Springer.
Hilliard, R. 2000. Views as modules, position paper for the Fourth InternationalSoftware Architecture Workshop (ISAW-4), Limerick, Ireland
Hofmeister, C., Nord, R., and Soni, D. 1999. Applied Software Architecture.Addison-Wesley, Reading, Massachusetts.
IEEE, 2000. IEEE recommended practice for architecture description. IEEE Standard1471.
Kotonya, G. and Sommerville, I. 1998. Requirements Engineering. Chichester:John Wiley&Sons, ISBN 0 471 97208 8
Kruchten, P.B. 1995. The 4+1 view model of architecture. IEEE Software. 12(6):42–50.
de With, Peter H.N., van Dijk, Gert-Jan. 2002. Architecture assessment for practicalmanagement of system architectures. paper to Landelijk Architectuur Congres, Zeist, The Netherlands,http://www.serc.nl/lac/track6_software_en_embedded.htm
Software Engineering Institute. 2001. Workshop on Software ArchitectureRepresentation, Special Report CMU/SEI-2001-SR-010, http://www.sei.cmu.edu/publications/documents/01.reports /01sr010.html
Smolander, K. and Päivärinta, T. 2002. Practical Rationale forDescribing Software Architecture, Beyond Programming-in-The-Large. proceedings of 3rdWorking IEEE/IFIP Conference on Software Architecture (WICSA3), 2002, Montreal,Québec, Canada, Jan Bosch et.al., ISBN 1-4020-7176-0, pp. 113–125.
Soni, D., Nord R.L., and Hofmeister, C. 1995. Software architecture in industrialapplications. In: Proceedings 17th International Conference on SoftwareEngineering, ACM, pp. 196–207.
Susman, G. and Evered, R. 1978. An Assessment of the Scientific Merits of Action Research. Administrative Science Quarterly, 23(4):582–603.
TOGAF webpage Frequently Asked Questions,http://www.opengroup.org/public/arch/p1/ togaf_faq.htm
van Vliet, H. 2000. Software Engineering: Principles and Practice, Chichester:John Wiley&Sons.
van Welie, M. 2001. Task-based User Interface Design. Ph.D. Thesis, VrijeUniversiteit, Amsterdam,http://www.cs.vu.nl/$\sim $martijn
Author information
Authors and Affiliations
Corresponding author
Rights and permissions
About this article
Cite this article
Koning, H., Vliet, H.v. Real-life IT architecture design reports and their relation to IEEE Std 1471 stakeholders and concerns. Autom Software Eng 13, 201–223 (2006). https://doi.org/10.1007/s10515-006-7736-6
Issue Date:
DOI: https://doi.org/10.1007/s10515-006-7736-6