Software composition refers to the construction of software
applications from components that implement abstractions pertaining to
a particular problem domain. Raising the level of abstraction is a
time-honored way of dealing with complexity, but the real benefit of
composable software systems lies in their increased flexibility:
a system built from components should be easy to recompose to address
new requirements. A certain amount of success has been achieved in
some well-understood application domains, as witnessed by the
popularity of user-interface toolkits, fourth generation languages and
application generators. But how can we generalize this?
%0 Journal Article
%1 nierstrasz1995c
%A Nierstrasz, Oscar
%A Meijler, Theo Dirk
%D 1995
%J ACM Computing Surveys
%K fnrs95 olit jb95 scg-coord scg-pub
%N 2
%P 262--264
%T Research Directions in Software Composition
%U ftp://ftp.iam.unibe.ch/pub/scg/Papers/scResearch.ps.gz
%V 27
%X Software composition refers to the construction of software
applications from components that implement abstractions pertaining to
a particular problem domain. Raising the level of abstraction is a
time-honored way of dealing with complexity, but the real benefit of
composable software systems lies in their increased flexibility:
a system built from components should be easy to recompose to address
new requirements. A certain amount of success has been achieved in
some well-understood application domains, as witnessed by the
popularity of user-interface toolkits, fourth generation languages and
application generators. But how can we generalize this?
@article{nierstrasz1995c,
abstract = {{\it Software composition} refers to the construction of software
applications from components that implement abstractions pertaining to
a particular problem domain. Raising the level of abstraction is a
time-honored way of dealing with complexity, but the real benefit of
composable software systems lies in their increased {\it flexibility}:
a system built from components should be easy to recompose to address
new requirements. A certain amount of success has been achieved in
some well-understood application domains, as witnessed by the
popularity of user-interface toolkits, fourth generation languages and
application generators. But how can we generalize this?},
added-at = {2006-03-09T08:15:35.000+0100},
author = {Nierstrasz, Oscar and Meijler, Theo Dirk},
biburl = {https://www.bibsonomy.org/bibtex/236b648d68d0019de7e650fe0b22d5847/snowball},
interhash = {99bef9a17a4f5d44358f3120158fe13e},
intrahash = {36b648d68d0019de7e650fe0b22d5847},
journal = {ACM Computing Surveys},
keywords = {fnrs95 olit jb95 scg-coord scg-pub},
month = {June},
number = 2,
pages = {262--264},
timestamp = {2006-03-09T08:15:35.000+0100},
title = {Research Directions in Software Composition},
url = {ftp://ftp.iam.unibe.ch/pub/scg/Papers/scResearch.ps.gz},
volume = 27,
year = 1995
}