HomeHomeHomeArchiteturMiddlewareMDSDBeratungCoachingTrainig
header
homemailbacksearchimpressum

go back go up Publications :: Architecture As Language

dotted Line
dotted Line
menu not Selected Home
dotted Line
menu not Selected Services
dotted Line
menu not Selected Experience
dotted Line
menu not Selected Conferences
dotted Line
menu selected Publications
   menu not Selected Books
   menu not Selected Patterns
   menu not Selected Papers
   menu not Selected Podcasts
   menu not Selected Videos
   menu not Selected Articles
   menu not Selected Position Papers
dotted Line
menu not Selected Vorlesungen
dotted Line
menu not Selected Site
dotted Line
dotted Line

magic Pixel banner 0

magic Pixel banner 1

magic Pixel banner 2

magic Pixel banner 3

magic Pixel banner 4 		magic Pixel

Architecture As Language

March/April 2010 (vol. 27 no. 2) Architecture is typically either a very non-tangible, conceptual aspect of a software system that can primarily be found in Word documents, or it is entirely driven by technology (“we use an XML architecture”). Both are bad: the former makes it hard to work with, and the latter hides architectural concepts behind technology hype. What can be done? As you develop the architecture, evolve a language that allows you to describe systems based on this architecture. Based on my experience in a number of real-world projects, this makes the architecture tangible and provides an unambiguous description of the architectural building blocks as well as the concrete system while still staying away from technology decisions (which then can be made consciously in a separate step).

[Artikel]
15.05.2010
Details... Details... Abstract... Abstract... 		Architecture As Language
Published in: IEEE Software, May/June 2010