![]() |
|
||
|
|
|||
![]() |
| Report Summary |
| Title: | April 2005 - Editorial - On Componentization | ||
| Author: | David Sprott | ||
| Publication Date: | 20 April 2005 | ||
| Report Type: | Journal | ||
| Report Class: | Editorial | ||
| Abstract: | Back a few years ago the topic of software components was getting a high level of interest in the technical community. The idea of somewhat coarser grained units of functionality and reuse was and is extremely sensible. But it was pretty clear that software components were a technical level matter and that while development managers were very happy for developers to design and build components, it was hard to persuade anyone of the higher order benefits, and even harder to convince managers that it was desirable to invest to develop generalized components for wider reuse. Generally the cost/benefit equation didn’t produce a sufficiently positive result, and components had no obvious connection to business issues. | ||
| Report Size: | 1 Page | ||
| Report Access Type: | |||
| Available for separate purchase | Single copies of recent CBDI Journals may be purchased | ||
| Login |
|
| © Everware-CBDI Inc 1999-2008 |