Register your product to gain access to bonus material or receive a coupon.
Component Software Engineering is an emerging technology about to take the software industry by storm. Building on existing object-oriented approaches, component technology can be used to deliver reusable, eoff-the-shelf i software components for incorporation into large applications.
Component Software: Beyond Object-Oriented Programming explains the technical foundations of this evolving technology and its importance in the software market place. It provides in-depth discussion of both the technical and the business issues to be considered, then moves on to suggest approaches for implementing component-oriented software production and the organizational requirements for success. The author draws on his own experience to offer tried-and-tested solutions to common problems and novel approaches to potential pitfalls.
Anyone responsible for developing software strategy, evaluating new technologies, buying or building software will find Clemens Szyperskiis objective and market-aware perspective of this new area invaluable.
Helpful Features Include:© Clemens Szyperski 1998
Click below for Web Resources related to this title:
Author's Homepage
Oberon microsystems
I. MOTIVATION: COMPONENTS AND MARKETS.
1. Introduction.Components are for Composition.
Components: Custom-Made Versus Standard Software.
Inevitability of Components.
The Nature of Software and Deployable Entities.
Components are Units of Deployment.
Lessons Learned.
2. Market Versus Technology.Creating a Market.
Fundamental Properties of Component Technology.
Market Forecasts.
Gartner Group (1994-95).
Strategic Focus (January 1995).
Ovum (1995).
Idc (May 1996).
Forrester Research (October 1996).
3. Standards.The Utmost Importance of (Quasi) Standards.
Wiring Standards are Not Enough.
Too Many Competing Standards Are Not Useful.
Where is Software Component Technology Today?
What’s Next?
II. FOUNDATION.
4. What a Component is and is Not.Terms and Concepts.
Components.
Objects.
Components and Objects.
Modules.
Whitebox Versus BlackBox Abstractions and Reuse.
Interfaces.
Explicit Context Dependencies.
Component ’Weight’.
Standardization and Normalization.
Horizontal Versus Vertical Markets.
Standard Component Worlds and Normalization.
5. Components, Interfaces, and Re-Entrance.Components and Interfaces.
Direct and Indirect Interfaces.
Versions.
Interfaces As Contracts.
Contracts and Non-Functional Requirements.
Undocumented ’Features.’
What Belongs to a Contract?
Safety and Progress.
Non-Functional Requirements.
Specifying Time and Space Requirements.
Dresscode: Formal or Informal?
Callbacks and Contracts.