By Topic

A standard for architecture description

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$31 $31
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

4 Author(s)
Youngs, R. ; IBM United Kingdom Ltd., 1 New Square, Bedfont Lakes, Feltham, TW14 8HB England ; Redmond-Pyle, D. ; Spaas, P. ; Kahan, E.

A profitable information technology (IT) services organization is dependent on widespread asset harvesting (from previous engagements) and scalable asset deployment (into current and future engagements). This activity demands consistency of terminology and notation in the creation and use of engagement artifacts, including work products. This paper presents a standard for architecture description in which a set of conventions for terminology and notation is used to describe and to express the organization of the architecture for an IT system. This standard, the Architecture Description Standard (ADS), is intended to be used by the IBM architecture community. The emphasis is on a minimal set of shared concepts that can be effectively taught to a broad range of IT architects with different skills and that is usable in practice.

Note: The Institute of Electrical and Electronics Engineers, Incorporated is distributing this Article with permission of the International Business Machines Corporation (IBM) who is the exclusive owner. The recipient of this Article may not assign, sublicense, lease, rent or otherwise transfer, reproduce, prepare derivative works, publicly display or perform, or distribute the Article.  

Published in:

IBM Systems Journal  (Volume:38 ,  Issue: 1 )