![]() |
|
||
|
|
|||
![]() |
| Report Summary |
| Title: | Towards Component Rigor | ||
| Author: | Richard Veryard | ||
| Publication Date: | 1 November 2000 | ||
| Report Type: | |||
| Abstract: | Component-based software engineering today is largely dependent upon imprecise methods of communication or specification. System architectures and software procurement contracts are largely based on informal descriptions of the required functionality and quality of service of each component. This dependence on informal specification constrains automation and creates barriers to the widespread adoption of component concepts. The next leap of automation in software reuse will be dependent upon rigorous notations for component specifications. For example widespread adoption of certification will probably not be practical without rigorous specification and Web services will require comprehensive description of the component interface in order to be self-describing. Within the world of software components, various tools and methods have appeared, claiming to offer “rigorous” and “precise” specifications of components and services. In this article, we’re going to look at these claims, and evaluate some of the leading methods in terms of the rigor on offer. | ||
| Report Access Type: |
|
||
| Available for separate purchase | Single copies of recent CBDI Journals may be purchased | ||
| Login |
|
| © Everware-CBDI Inc 1999-2008 |