TABLE OF CONTENTS LUIS IRIBARNE
Department of Lenguajes y Computaci n, University of Almer a
Ctra Sacramento s/n, 04120 Almer a, Spain
liribarne@ual.es
JOS M.TROYA and ANTONIO VALLECILLO
Department of Lenguajes y Ciencias de la Computaci n, University of M laga
Campus de Teatinos, M laga, Spain
{troya,av}@lcc.uma.es
Abstract. Currently there is an increasing interest in the use of COTS components for building software applications. One of the key aspects in the construction of COTS-based applications is the definition of software architecture prototypes from visual notations and reusable components (commercial components). These specifications must comply with some related aspects of COTS components, such as the quality of service (QoS), or the non-functional and functional information of the component. However, the possible benefits of COTS software architecture development, such as low cost, low risk, and high quality, cannot be satisfactorily achieved due to inadequate and/or incomplete proposals for commercial component, specification and architecture definition. This chapter discusses an approach for describing specifications and architectural requirements of COTS components. It uses an extended UML-RT notation by means of notes, tagged values and restrictions to accommodate component information. A small GIS system example of a COTS-based software application is also used to illustrate the approach.
[*]This work has been partially supported by the projects: WEST: Web-oriented Software Technology (CYTED subproject VII, code VII.18) and Indalog (CICYT project, Ref. TIC2002 03968).
In Component-based Software Engineering (CBSE) a common practice known as buy, don t build , promoted by Fred Brooks [Brooks (1987)], discusses the use of prefabricated components without having to...
