Roles and responsibilities for COTS components selection processes
Information systems tend nowadays to be designed by integrating or customizing Commercial Off-The-Shelf (COTS) components acquired or licensed from the marketplace. There are currently many methods that contribute to select these components. The application of COTS selection methods result in proces...
| Autores: | , , |
|---|---|
| Tipo de recurso: | informe técnico |
| Fecha de publicación: | 2006 |
| País: | España |
| Institución: | Universitat Politècnica de Catalunya (UPC) |
| Repositorio: | UPCommons. Portal del coneixement obert de la UPC |
| Idioma: | inglés |
| OAI Identifier: | oai:upcommons.upc.edu:2117/85933 |
| Acceso en línea: | https://hdl.handle.net/2117/85933 |
| Access Level: | acceso abierto |
| Palabra clave: | Commercial off-the-shelf COTS COTS selection Interaction roles Soft Àrees temàtiques de la UPC::Informàtica::Sistemes d'informació |
| Sumario: | Information systems tend nowadays to be designed by integrating or customizing Commercial Off-The-Shelf (COTS) components acquired or licensed from the marketplace. There are currently many methods that contribute to select these components. The application of COTS selection methods result in processes that are different from usual development processes, yielding to new activities and responsibilities that should be covered by interactions of specialized roles. However it may be observed that these methods do not put emphasis neither on the identification of these roles, nor on their subsequent interactions, nor on their combination to form a selection team. The contribution of this work is based on identifying and defining the roles that take place in COTS selection processes, their interactions and their responsibilities. We use a goal-oriented approach, the i* notation, and a framework to model the engineering process, the OPEN Process Framework (OPF), with the purpose of issuing a well-defined work team that can adapt itself to the internal processes of a particular organization. We apply our generic proposal to a particular case, a COTS-based development life-cycle based on the agile principles and individuals interactions as defined in eXtreme Programming (XP). |
|---|