A framework for information systems architecture
IBM Systems Journal
Documenting Software Architectures: Views and Beyond
Documenting Software Architectures: Views and Beyond
The 4+1 View Model of Architecture
IEEE Software
Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives
Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives
Architectural descriptions as boundary objects in system and design work
MODELS'10 Proceedings of the 13th international conference on Model driven engineering languages and systems: Part II
Collaborative prioritization of architectural concerns
Journal of Systems and Software
| Hi-index | 0.00 |
Contemporary model driven development tools only partially support the abstractions occurring in complex embedded systems development. The paper presents an interpretive case study in which the concerns held by 7 engineers in a large product developing organization were compared to the concerns supported by the modeling tool in use. The paper's main finding is an empirically grounded catalogue of concerns, categorized with respect to visibility in models and other artefacts in use. In the studied case, 26% of the concerns were visible in the models, whereas 38% were visible elsewhere and 36% not visible at all. The catalogue has been presented to several stakeholders in the unit studied, with positive feedback: particularly appreciated were the notion of concern visibility as indicator of degree of implementation of model driven development, and that concerns have traceable connections to experiences of the unit's engineers.