The artifacts of component-based development
It addresses software engineering challenges by promoting reuse and efficiency in development, but is incremental as it reviews existing architectures.
This paper examines component-based development (CBD) architectures like ActiveX, CORBA, RMI, and SOAP, comparing their advantages and disadvantages to support CBD practice, and evaluates adapting an object-oriented process model for CBD.
Component based development idea was floated in a conference name "Mass Produced Software Components" in 1968 [1]. Since then engineering and scientific libraries are developed to reuse the previously developed functions. This concept is now widely used in SW development as component based development (CBD). Component-based software engineering (CBSE) is used to develop/ assemble software from existing components [2]. Software developed using components is called component ware [3]. This paper presents different architectures of CBD such as ActiveX, common object request broker architecture (CORBA), remote method invocation (RMI) and simple object access protocol (SOAP). The overall objective of this paper is to support the practice of CBD by comparing its advantages and disadvantages. This paper also evaluates object oriented process model to adapt it for CBD.