A framework for information systems architecture
IBM Systems Journal
Object-oriented development in an industrial environment
OOPSLA '87 Conference proceedings on Object-oriented programming systems, languages and applications
N degrees of separation: multi-dimensional separation of concerns
Proceedings of the 21st international conference on Software engineering
UMTS Networks: Architecture, Mobility and Services
UMTS Networks: Architecture, Mobility and Services
Documenting Software Architectures: Views and Beyond
Documenting Software Architectures: Views and Beyond
The 4+1 View Model of Architecture
IEEE Software
"Talk to Paula and Peter - They Are Experienced" - The Experience Engine in a Nutshell
SEKE '99 Proceedings of the 11th International Conference on Software Engineering and Knowledge Engineering, Learning Software Organizations, Methodology and Applications
Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives
Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives
The many faces of architectural descriptions
Information Systems Frontiers
Enterprise Ontology: Theory and Methodology
Enterprise Ontology: Theory and Methodology
Journal of Systems and Software - Special issue: Quality software
Moving architectural description from under the technology lamppost
Information and Software Technology
A general model of software architecture design derived from five industrial approaches
Journal of Systems and Software
Ontology-based modelling of architectural styles
Information and Software Technology
Guest Editorial: Telecommunications and UML languages
Computer Networks: The International Journal of Computer and Telecommunications Networking - Telecommunications and UML languages
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
Hi-index | 0.00 |
Contemporary model driven development tools only partially support the abstractions occurring in complex embedded systems development. This article presents an interpretive case study in which architectural concerns important to seven engineers in a large product developing organization were compared to the views actually provided by the organization's models. The paper's main finding is an empirically grounded catalogue of architectural concerns for a large, complex embedded systems project, and an assessment of the degree to which the studied organization has managed to realize support for these concerns within economical and organizational constraints. In the studied case, 114 different architectural concerns were found to be important to the interviewed engineers. Of this sample, 75% were documented in models, structured text, or informal documentation, whereas 47% of all documented concerns were modeled. The paper's conclusion is that current modeling languages and methods inadequately address the full set of concerns that are important to engineers in base station development.