Contract oriented development of component software

Abstract

We present a model for component software. We describe how components are specified at the interface level, design level and how they are composed. From its external view, a component consists a set of interfaces, provided to or required from its environment. From its internal view, a component is an executable code that can be coupled with other components via its interfaces. The developer has to ensure that the specification of a component is met by its design and implementation. We also combine component-based and objectoriented techniques in component-based software development. © 2004 Springer Science + Business Media, Inc.