Adapting COTS products. (bibtex)
by David S. Wile, Robert Balzer, Neil M. Goldman, Marcelo Tallis, Alexander Egyed, Tim Hollebeek
Abstract:
COTS products can play various architectural roles in software systems: as interfaces to problem-specific functionality, as components that provide such functionality itself, and as intermediary connectors and components in more complex systems. In doing so, COTS products impose their own, unique constraints on organization and functionality. Over the last ten years, we have gained considerable experience with adopting, adapting, and living with the limitations of COTS products. Our goal was to adapt the COTS product to make it fit the application rather than adapting the application needs to make them fit the COTS product - thus, in essence, adapting the COTS product without access to its source code or documentation (a unique form of maintenance). We report on a large set of experiences involving eight COTS products and a wide range of COTS-Based Software Systems - most of which were done with and for industrial partners or government agencies. This experience report attempts to both give a feeling for how applications can be augmented with such COTS interfaces and also tries to tease out the specific architectural issues that anyone adapting COTS products is certain to face.
Reference:
Adapting COTS products. (David S. Wile, Robert Balzer, Neil M. Goldman, Marcelo Tallis, Alexander Egyed, Tim Hollebeek), In Proceedings of the 26th IEEE International Conference on Software Maintenance (ICSM 2010), Timisoara, Romania, IEEE Computer Society, 2010.
Bibtex Entry:
@Conference{DBLP:conf/icsm/WileBGTEH10,
  author    = {David S. Wile and Robert Balzer and Neil M. Goldman and Marcelo Tallis and Alexander Egyed and Tim Hollebeek},
  title     = {Adapting COTS products.},
  booktitle = {Proceedings of the 26th IEEE International Conference on Software Maintenance (ICSM 2010), Timisoara, Romania},
  year      = {2010},
  pages     = {1-9},
  publisher = {IEEE Computer Society},
  abstract  = {COTS products can play various architectural roles in software systems:
	as interfaces to problem-specific functionality, as components that
	provide such functionality itself, and as intermediary connectors
	and components in more complex systems. In doing so, COTS products
	impose their own, unique constraints on organization and functionality.
	Over the last ten years, we have gained considerable experience with
	adopting, adapting, and living with the limitations of COTS products.
	Our goal was to adapt the COTS product to make it fit the application
	rather than adapting the application needs to make them fit the COTS
	product - thus, in essence, adapting the COTS product without access
	to its source code or documentation (a unique form of maintenance).
	We report on a large set of experiences involving eight COTS products
	and a wide range of COTS-Based Software Systems - most of which were
	done with and for industrial partners or government agencies. This
	experience report attempts to both give a feeling for how applications
	can be augmented with such COTS interfaces and also tries to tease
	out the specific architectural issues that anyone adapting COTS products
	is certain to face.},
  doi       = {10.1109/ICSM.2010.5609658},
  file      = {:Conferences\\ICSM 2010 - Adapting COTS Products\\Adapting COTS Applications - The Fine Line between Development and Maintenance-preprint.pdf:PDF},
  keywords  = {},
}
Powered by bibtexbrowser