By Topic

Similar software systems

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 $13
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

1 Author(s)
Ekdahl, B. ; Comput. Sci. Dept., Lund Univ., Helsingborg, Sweden

During the last ten years or so, much effort has been spent on developing software architecture by analogy with hardware architecture from where the idea seems to originate. Much of the work has been devoted to specifying standard program units, called components, and their connections. The architecture is then the specific organization of these components and connections. In this paper, I suggest a completely different way of defining software architecture that does not take its influence from the hardware industry but from the fact that software systems are formal systems and that their formal models could be used not only to characterize systems but, may be more important, to categorize software systems.

Published in:

Information Reuse and Integration, 2003. IRI 2003. IEEE International Conference on

Date of Conference:

27-29 Oct. 2003