This material is being posted by Carnegie Mellon University's Software Engineering Institute (SEI) on this Web site as a community service.
| Elsevier Journal of Systems and Software Special IssueComponent-Based Software Engineering:
| ||||||||||
|
Index
BACKGROUND PAPERS SUBMISSION |
|
Components play a critical role in many software systems. A primary reason component-based technologies are adopted is that reasoning about component behaviors can be raised to levels of abstraction relatively independent of hardware platforms, operating systems, programming languages or specific middleware technology. A second useful abstraction lies in the definition hierarchy among components.
However, a number of open issues need to be resolved before a component-based approach can make a significant impact to mission-critical software development. Methods must be developed that allow measurement and prediction of the functional and extra-functional characteristics of a system based on properties of system components. There are many extra-functional properties that developers would like to ensure in the systems they develop, including: reliability, safety, robustness, availability, performance, security, modifiability, adaptability, responsiveness, scalability, and so forth.
Our ability to reason about such properties at the level of assemblies of components is of great concern to modern system developers. System integration and changes in configuration, architecture or core components may have a significant impact on those properties. Frequently small structural changes have a discontinuously large impact on such properties. In this context, models of various system compositions and their differences particularly in view of system properties are of interest to practitioners and researchers alike.
In practice, our ability to understand the functional and extra-functional properties of large component-based systems often suffer from:
Research and practice in the areas of component trust and certification, component technology, and software architecture to date has been conducted largely in isolation and is only beginning to touch on the core issues. Despite recent advances there remain many open problems.
Topics of interest include:
Papers must exhibit practical ideas and include practical evaluations through analysis, simulation and experiments.
In addition they must also address to the following points:
| Paper submission | December 1, 2001 |
| All reviews back | January 25, 2002 |
| Notification of authors | February 15, 2002 |
| Camera-ready manuscript due | March 1, 2002 |
| Approximate publication date | September 2002 |
Authors should format a submission following the instructions for authors and submit an electronic copy of the manuscript in English, in either PDF or Postscript format via electronic mail to hws@monash.edu.au before the submission deadline. Submissions should include authors names, affiliations, addresses, phone numbers and e-mail addresses both on the document cover page and in the email.
Only original manuscripts, which have not been submitted elsewhere, will be considered for publication.
All papers will be subject to a thorough peer review process.
Guest Editors, Elsevier Science, Inc.