Component-Based Software Development: Case Studies

PEDRO J.CLEMENTE, JUAN HERN NDEZ, JUAN M.MURILLO, MIGUEL A.P REZ and FERNANDO S NCHEZ
Quercus Software Engineering Group
University of Extremadura, Spain
{jclemente, juanher, juanmamu, toledano, fernando}@unex.es
Abstract. Component Based Software Engineering (CBSE) and Aspect Oriented Programming (AOP) are two disciplines of software engineering, which have been generating a great deal of interest in recent years. From the CBSE point of view, the building of applications becomes a process of assembling independent and reusable software modules called components. However, the necessary dependencies description among components and its latter implementation causes the appearance of crosscutting, a problem that AOP resolves adequately. Aspect Oriented Programming allows programmers to express in a separate form the different aspects that intervene in an application. These aspects are composed later adequately. This paper analyses the problem of crosscutting that is produced during component development using one of the latest component-based development platforms, such as the Corba Component Model (CCM), and proposes one extension for this platform. This CCM extension has been named AspectCCM [Clemente et al. (2002a)].
[*]This project has been financed by CICYT, project number TIC02-04309-C02-01.
One of the disciplines of software engineering that, during recent years, has been generating wide concern is component-based software engineering (CBSE), due to CBSE s great potential for software development companies. The building of applications is transformed now into a process of assembling independent and reusable software modules called components. A component is one software composition unit with a set of interfaces and a set of requirements.