A coherent description of architectures provides insight, enables communication among different stakeholders and guides complicated (business and ICT) change processes. Unfortunately, so far no architecture description language exists that fully enables integrated enterprise modeling. In this paper we focus on the requirements and design of such a language. This language defines generic, organization-independent concepts that can be specialized or composed to obtain more specific concepts to be used within a particular organisation. It is not our intention to re-invent the wheel for each architectural domain: wherever possible we conform to existing languages or standards such as UML. We complement them with missing concepts, focusing on concepts to model the relationships among architectural domains. The concepts should also make it possible to define links between models in other languages. The relationship between architecture descriptions at the business layer and at the application layer (business-IT alignment) plays a central role.
%0 Conference Paper
%1 jonkers_towards_2003
%A Jonkers, H.
%A van Burren, R.
%A Arbab, F.
%A de Boer, F.
%A Bonsangue, M.
%A Bosma, H.
%A ter Doest, H.
%A Groenewegen, L.
%A Scholten, J. G
%A Hoppenbrouwers, S.
%A Iacob, M. -E
%A Janssen, W.
%A Lankhorst, M.
%A van Leeuwen, D.
%A Proper, E.
%A Stam, A.
%A van der Torre, L.
%A van Zanten, G. V
%B Enterprise Distributed Object Computing Conference, 2003. Proceedings. Seventh IEEE International
%D 2003
%I IEEE
%K Application Architecture Architecture; Business Computer Description Instruments; Language; Software Unified Visualization; Wheels alignment; analysis; application architectural architecture architecture; business change coherent communication; complicated concepts; corporate data description description; descriptions; design; domain; enterprise formal generic language; languages; layer; modeling modeling; modelling; organization-independent processes; processing; requirements science; software; specification specification; systems systems; uml; {business-IT}
%P 28-- 37
%R 10.1109/EDOC.2003.1233835
%T Towards a language for coherent enterprise architecture descriptions
%X A coherent description of architectures provides insight, enables communication among different stakeholders and guides complicated (business and ICT) change processes. Unfortunately, so far no architecture description language exists that fully enables integrated enterprise modeling. In this paper we focus on the requirements and design of such a language. This language defines generic, organization-independent concepts that can be specialized or composed to obtain more specific concepts to be used within a particular organisation. It is not our intention to re-invent the wheel for each architectural domain: wherever possible we conform to existing languages or standards such as UML. We complement them with missing concepts, focusing on concepts to model the relationships among architectural domains. The concepts should also make it possible to define links between models in other languages. The relationship between architecture descriptions at the business layer and at the application layer (business-IT alignment) plays a central role.
%@ 0-7695-1994-6
@inproceedings{jonkers_towards_2003,
abstract = {A coherent description of architectures provides insight, enables communication among different stakeholders and guides complicated (business and {ICT)} change processes. Unfortunately, so far no architecture description language exists that fully enables integrated enterprise modeling. In this paper we focus on the requirements and design of such a language. This language defines generic, organization-independent concepts that can be specialized or composed to obtain more specific concepts to be used within a particular organisation. It is not our intention to re-invent the wheel for each architectural domain: wherever possible we conform to existing languages or standards such as {UML.} We complement them with missing concepts, focusing on concepts to model the relationships among architectural domains. The concepts should also make it possible to define links between models in other languages. The relationship between architecture descriptions at the business layer and at the application layer {(business-IT} alignment) plays a central role.},
added-at = {2013-02-28T11:13:35.000+0100},
author = {Jonkers, H. and van Burren, R. and Arbab, F. and de Boer, F. and Bonsangue, M. and Bosma, H. and ter Doest, H. and Groenewegen, L. and Scholten, J. G and Hoppenbrouwers, S. and Iacob, M. {-E} and Janssen, W. and Lankhorst, M. and van Leeuwen, D. and Proper, E. and Stam, A. and van der Torre, L. and van Zanten, G. V},
biburl = {https://www.bibsonomy.org/bibtex/2e10aab52a8a6d91a80630342886386a5/fritzsolms},
booktitle = {{Enterprise Distributed Object Computing Conference, 2003. Proceedings. Seventh {IEEE} International}},
doi = {10.1109/EDOC.2003.1233835},
interhash = {5299eb0a158b7c9e188ba853e4ad2ee3},
intrahash = {e10aab52a8a6d91a80630342886386a5},
isbn = {0-7695-1994-6},
keywords = {Application Architecture Architecture; Business Computer Description Instruments; Language; Software Unified Visualization; Wheels alignment; analysis; application architectural architecture architecture; business change coherent communication; complicated concepts; corporate data description description; descriptions; design; domain; enterprise formal generic language; languages; layer; modeling modeling; modelling; organization-independent processes; processing; requirements science; software; specification specification; systems systems; uml; {business-IT}},
month = sep,
pages = {28-- 37},
publisher = {{IEEE}},
timestamp = {2013-02-28T11:13:52.000+0100},
title = {{Towards a language for coherent enterprise architecture descriptions}},
year = 2003
}