Selecting software components with multiple interfaces

Component-based software development is gaining recognition as the key technology for the construction of high-quality, evolvable, large software systems in a timely and affordable manner. Component search and service matching have become two of the key issues involved in this process. However current proposals addressing these issues are based on the simplistic assumptions that components present only one interface with the services they offer. This work presents an extension of those approaches in which components may offer and require several interfaces, extending the traditional component "substitutability" operator. In addition, an algorithm for selecting COTS components with multiple interfaces from a repository in order to implement a given software architecture is presented.

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

[2]  Jeannette M. Wing,et al.  Specification matching of software components , 1995, TSEM.

[3]  Luqi,et al.  Software component search , 1996, J. Syst. Integr..

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

[5]  Ali Mili,et al.  Reusing Software: Issues and Research Directions , 1995, IEEE Trans. Software Eng..

[6]  Jun Han,et al.  Semantic and Usage Packaging for Software Components , 1999, ECOOP Workshops.

[7]  Antonio Vallecillo,et al.  Trading for COTS components in open environments , 2001, Proceedings 27th EUROMICRO Conference. 2001: A Net Odyssey.

[8]  Alan W. Brown,et al.  The Current State , 2016 .

[9]  Chang Jun.  CORBA Component Model , 2003 .

[10]  Daniel M. Yellin,et al.  Protocol specifications and component adaptors , 1997, TOPL.

[11]  Cornelius Ncube.  COTS Software Selection: The Need to make Tradeoffs between System Requirements, Architectures and COTS/Components , 2000 .

[12]  Murali Sitaraman,et al.  Foundations of component-based systems , 2000 .

[13]  Bashar Nuseibeh,et al.  Weaving Together Requirements and Architectures , 2001, Computer.

[14]  Jeannette M. Wing,et al.  Signature matching: a tool for using software libraries , 1995, TSEM.

[15]  Proceedings Of The 26 Th Euromicro Conference , 2000, Proceedings of the 26th Euromicro Conference. EUROMICRO 2000. Informatics: Inventing the Future.

[16]  Pierre America,et al.  Designing an Object-Oriented Programming Language with Behavioural Subtyping , 1990, REX Workshop.

[17]  Clemens A. Szyperski,et al.  Component software - beyond object-oriented programming , 2002 .

[18]  Grace A. Lewis,et al.  Building systems from commercial components , 2002, ICSE '02.

[19]  Gary T. Leavens,et al.  Forcing behavioral subtyping through specification inheritance , 1996, Proceedings of IEEE 18th International Conference on Software Engineering.

[20]  Clemens Szyperski,et al.  Component software , 1997 .

[21]  Antonio Vallecillo,et al.  New Issues in Object Interoperability , 2000, ECOOP Workshops.

[22]  Philippe A. Palanque,et al.  Formal Specification and Prototyping of CORBA Systems , 1999, ECOOP.

[23]  Clemens A. Szyperski.  Emerging component software technologies — a strategic comparison , 1998, Softw. Concepts Tools.

[24]  Arvinder Kaur,et al.  Component Based Software Engineering , 2010 .

[25]  Anna Mikhajlova,et al.  Ensuring Correctness of Object and Component Systems , 1999 .

[26]  Lidia Fuentes,et al.  Extending CORBA interfaces with /spl pi/-calculus for protocol compatibility , 2000, Proceedings 33rd International Conference on Technology of Object-Oriented Languages and Systems TOOLS 33.

[27]  Robert C. Seacord,et al.  K-BACEE: knowledge-based automated component ensemble evaluation , 2001, Proceedings 27th EUROMICRO Conference. 2001: A Net Odyssey.

[28]  Colette Rolland,et al.  Requirements engineering for COTS based systems , 1999, Inf. Softw. Technol..