IPM: An Incremental Process Model for Distributed Component-Based Software Development

In spite of recent and constant researches in the Component-Based Development (CBD) area, there is still lack of patterns, process model and methodologies that effectively support as much the development “for reuse” as “with reuse”. Considering the accelerated growth of the Internet over the last decade, where distribution has become an essential non-functional requirement of most applications, the problem becomes bigger. This paper proposes a novel Incremental Process Model (IPM) that integrates the concepts of Component-Based Software Engineering (CBSE), frameworks, patterns, and distribution. This process model is divided into two stages: the development “for reuse”, and the development “with reuse”. A CASE tool is the main mechanism to apply this process model, supporting inclusively, the code generation of components and applications. A distributed components environment is proposed for accomplishing the results of this process model. Through a case study it is shown how the process model works on a given

[1]  George T. Heineman,et al.  Component-Based Software Engineering: Putting the Pieces Together , 2001 .

[2]  Gary Cornell,et al.  Core Java 1.1 Volume II Advanced Features , 1998 .

[3]  Björn Regnell,et al.  Development of Object-Oriented Frameworks , 1995 .

[4]  Desmond D'Souza,et al.  Objects, Components, and Frameworks with UML: The Catalysis Approach , 1998 .

[5]  Gary Cornell,et al.  Core Java(TM) 2, Volume II--Advanced Features (7th Edition) , 2004 .

[6]  Ajantha Dahanayake,et al.  A Methodology Framework for Component-Based System Development Support , 2001 .

[7]  Ralph Johnson,et al.  Connecting Business Objects to Relational Databases , 1998 .

[8]  Ralph Johnson,et al.  design patterns elements of reusable object oriented software , 2019 .

[9]  Dan Harkey,et al.  Client/Server programming with Java and Corba , 1997 .

[10]  Colin Atkinson,et al.  Component-Based Software Engineering : The KobrA Approach , 2000 .

[11]  John Daniels,et al.  UML Components: A Simple Process for Specifying Component-Based Software , 2000 .

[12]  하수철,et al.  [서평]「Component Software」 - Beyond Object-Oriented Programming - , 2000 .

[13]  Douglas T. Ross,et al.  Structured Analysis (SA): A Language for Communicating Ideas , 1977, IEEE Transactions on Software Engineering.

[14]  Vander Alves,et al.  Distributed Adapters Pattern: A Design Pattern for Object-Oriented Distributed Applications , 2002 .

[15]  Cristina V. Lopes,et al.  Aspect-oriented programming , 1999, ECOOP Workshops.

[16]  Pedro J. Clemente,et al.  Modeling with UML Component-based and Aspect Oriented Programming Systems , 2002 .

[17]  Ivar Jacobson,et al.  The Unified Software Development Process , 1999 .

[18]  Ivar Jacobson,et al.  The unified modeling language reference manual , 2010 .

[19]  Ivar Jacobson,et al.  Software Reuse: Architecture, Process And Organization For Business Success , 1998, Proceedings. Technology of Object-Oriented Languages. TOOLS 26 (Cat. No.98EX176).

[20]  Antônio Francisco do Prado,et al.  Distributed Component-Based Software Development Strategy Integrated By MVCase Tool , 2002, JIISIC.

[21]  Henk Jonkers,et al.  Evaluation of Component-Based Development Methods , 2005, Information Modeling Methods and Methodologies.