A rational design process: How and why to fake it
IEEE Transactions on Software Engineering
Software architecture in industrial applications
Proceedings of the 17th international conference on Software engineering
Practical guidelines for the readability of IT-architecture diagrams
Proceedings of the 20th annual international conference on Computer documentation
The 4+1 View Model of Architecture
IEEE Software
Documenting Software Architectures: Views and Beyond
Documenting Software Architectures: Views and Beyond
A rationale-based architecture model for design traceability and reasoning
Journal of Systems and Software
Stakeholder identification and quality attribute prioritization for a global Vehicle Control System
Proceedings of the Fourth European Conference on Software Architecture: Companion Volume
Defining and documenting execution viewpoints for a large and complex software-intensive system
Journal of Systems and Software
Hi-index | 0.00 |
With the growing impact of information technology the proper understanding of IT-architecture designs is becoming ever more important. Much debate has been going on about how to describe them. In 2000, the IEEE Std 1471 proposed a model of an architecture description and its context. In this paper we propose a lightweight method for modeling architectural information after (part of) the conceptual model of IEEE Std 1471 and defining IEEE Std 1471 viewpoints. The method gives support by outlining in textual form and in diagram form the relation of the concerns of the stakeholders to the architectural information. The definition of viewpoints can then be done with insight from these relations. The method has four steps: (1) creating stakeholder profiles, (2) summarizing internal design documentation, (3) relating the summary to the concerns of the stakeholders, and (4) defining viewpoints. We have conducted a round of discussion and testing in practice in various settings. In this paper we present the feedback we received and propose improvements.