Externalizing component manners to achieve greater maintainability through a highly re-configurable architectural style

The maintenance and evolution of distributed, heterogeneous software components; including both legacy and green-field subsystems is described through a highly re-configurable architectural style. It is shown how this architectural style is realized through identification, separation and externalization of a formal specification of the manners of the application domain and its components. The approach is based on the notion of enterprise component (EC). An enterprise component is defined as an architectural pattern that is leveraged to provide a uniform mechanism for management of component boundaries between otherwise entropic systems consisting of multiple legacy systems coexisting with newer, object and component-based application programs. EC's are identified through a domain decomposition that includes mapping business architecture onto component-based software architecture. Extensions to current methodologies and architectural practices to support and realize such a style are presented.

[1]  D. L. Parnas,et al.  On the criteria to be used in decomposing systems into modules , 1972, Software Pioneers.

[2]  Martin L. Griss.  Product-line architectures , 2001 .

[3]  Harold Ossher,et al.  Multi-Dimensional Separation of Concerns and the Hyperspace Approach , 2002 .

[4]  Joachim Hans Fröhlich,et al.  Prototype of a Run-Time Adaptable, Object-Oriented System , 1996, Ershov Memorial Conference.

[5]  Bertrand Meyer,et al.  Object-Oriented Software Construction, 2nd Edition , 1997 .

[6]  Trygve Reenskaug,et al.  System Design by Composing Structures of Interacting Objects , 1992, ECOOP.

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

[8]  Bradley P. Allen,et al.  Simplifying the construction of domain-specific automatic programming systems: The NASA automated software development workstation project , 1988 .

[9]  簡聰富,et al.  物件導向軟體之架構(Object-Oriented Software Construction)探討 , 1989 .

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

[11]  Reza Razavi,et al.  Adaptive Object-Models 1 , 2000 .

[12]  D. W. McDavid,et al.  A Standard for Business Architecture Description , 1999, IBM Syst. J..

[13]  Ali Arsanjani.  Patterns of Symmetry and Stability In Software Architecture , 2004 .

[14]  David Lorge Parnas,et al.  Review of David L. Parnas' "Designing Software for Ease of Extension and Contraction" , 2004 .

[15]  Kent L. Beck.  Smalltalk best practice patterns , 1996 .

[16]  David Lorge Parnas,et al.  On the Design and Development of Program Families , 2001, IEEE Transactions on Software Engineering.

[17]  D. Batory,et al.  Product-Line Architectures , 1998 .

[18]  David Notkin,et al.  Decoupling change from design , 1996, SIGSOFT '96.

[19]  Ralph Johnson,et al.  Architecture and design of adaptive object-models : Intriguing Technology from OOPSLA by John Vlissides and Doug Lea , 2001 .

[20]  Mark A. Ardis,et al.  Domain engineered configuration control , 2000, SPLC.

[21]  Don Batory,et al.  A Domain Model for Avionics Software * * ADAGE-UT-93-03 May 1993 , 1993 .

[22]  Fangzhe Chang,et al.  Automatic configuration and run-time adaptation of distributed applications , 2000, Proceedings the Ninth International Symposium on High-Performance Distributed Computing.

[23]  G. Arango.  Domain analysis: from art form to engineering discipline , 1989, IWSSD '89.

[24]  Ali Arsanjani,et al.  Grammar-Oriented Object Design: Creating Adaptive Collaborations and Dynamic Configurations with Self-Describing Components and Services , 2001, TOOLS.

[25]  Charles Consel,et al.  Domain-Specific Languages: From Design to Implementation Application to Video Device Drivers Generation , 1999, IEEE Trans. Software Eng..

[26]  Dewayne E. Perry.  Proceedings International Conference on Software Maintenance , 1997, 1997 Proceedings International Conference on Software Maintenance.