Learning Zone: Component Reuse - Contents

This paper develops a component definition that is concise and robust in all circumstances for our purposes by investigating dictionary definitions and comparing the use of components in other industries with that in the software development industry. In addition, we will discuss the potential advantages and common pitfalls of using such technology for software development. We will discuss component concepts in a technology and development process free manner; the reader should understand that when comparing the terminology and concepts expressed in this paper with those used in specific implementation technologies and software development processes, a mapping exercise between the two may well be necessary.

Component management is not just about organizations with thousands of components. It is a useful engineering concept whatever the scale or complexity of the software project at hand. This is because it enables a process for parallel working and breaking large problems into smaller chunks. You may be involved in a small team using technical components and need a process and tool to simplify communication. Alternatively, you may be involved in a large multi-site, complex, component-based environment with hundreds of developers, and need real power from your process and supporting tools.

This document examines the differences in terminology and architecture in the component-based and web service schools. It discusses how the differences – particularly the terminological differences – can be reconciled. The result is a new, more powerful view of the provision of business solutions in the context of a homogeneous, service-oriented architecture.

This document discusses the sources of the ROI that can be achieved through the use of components and services to deliver business solutions in a service-oriented architecture. It examines the use and benefits derived from the adoption of appropriate tools and processes for their delivery. The scope of the white paper is specific to the gains achieved through the adoption of SCBD, or where SCBD can significantly raise the level of benefit above that which can be achieved with other architecture, processes or technology.