http://hdl.handle.net/2117/5874 Wed, 22 May 2013 11:32:44 GMT 2013-05-22T11:32:44Z webmaster.bupc@upc.edu Universitat Politècnica de Catalunya. Servei de Biblioteques i Documentació no http://hdl.handle.net/2117/17924 Title: A reference model for i* Authors: Cares, Carlos; Franch Gutiérrez, Javier; Mayol Sarroca, Enric; Quer Bosor, Maria Carme Abstract: Agent-oriented models are frequently used in disciplines such as agent-oriented requirements engineering, requirements engineering and organizational process modelling. i* is currently one of the most widespread notations used for this purpose. Due to both its dissemination and its highly strategic nature, instead of a single definition, several groups have formulated different variants, which define in a slightly different way the basic concepts of the language, as well as propose particular constructs that fit into the particular interests of these groups. In this chapter we first review these proposals and then we present a reference model that establishes the concepts and relationships that are fundamental in i*. The reference model is expressed as a UML class diagram (with OCL constraints) together with a vocabulary of the presented terms. Most of the included concepts are common to the seminal i* proposal, the GRL and the diverse variations used in the context of the Tropos methodology. For those concepts that are not shared by these analysed variants, the reference model tries to reconcile the different views whenever possible. The reference model allows determining the differences of any existing i* variant with respect to the model, and also to know how much different a new variant would be from the core of i*. The variants can be expressed by applying some refactoring operations on the UML class diagram. We illustrate this situation by applying refactoring to some of the analysed proposals. Fri, 22 Feb 2013 10:23:17 GMT http://hdl.handle.net/2117/17924 2013-02-22T10:23:17Z Cares, Carlos; Franch Gutiérrez, Javier; Mayol Sarroca, Enric; Quer Bosor, Maria Carme no Agent-oriented models are frequently used in disciplines such as agent-oriented requirements engineering, requirements engineering and organizational process modelling. i* is currently one of the most widespread notations used for this purpose. Due to both its dissemination and its highly strategic nature, instead of a single definition, several groups have formulated different variants, which define in a slightly different way the basic concepts of the language, as well as propose particular constructs that fit into the particular interests of these groups. In this chapter we first review these proposals and then we present a reference model that establishes the concepts and relationships that are fundamental in i*. The reference model is expressed as a UML class diagram (with OCL constraints) together with a vocabulary of the presented terms. Most of the included concepts are common to the seminal i* proposal, the GRL and the diverse variations used in the context of the Tropos methodology. For those concepts that are not shared by these analysed variants, the reference model tries to reconcile the different views whenever possible. The reference model allows determining the differences of any existing i* variant with respect to the model, and also to know how much different a new variant would be from the core of i*. The variants can be expressed by applying some refactoring operations on the UML class diagram. We illustrate this situation by applying refactoring to some of the analysed proposals. http://hdl.handle.net/2117/17922 Title: On the Use of i* for COTS components selection: principles and consequences Authors: Franch Gutiérrez, Javier; Mayol Sarroca, Enric; Quer Bosor, Maria Carme Abstract: Commercial Off-The-Shelf (COTS) components selection is an activity that plays an increasingly crucial role in the delivery of software systems. We are using i*, specially Strategic Dependency models, for driving this activity. Software domains are modeled as actors, and the relationships among them and with external actors (people, other software systems, organizations, etc.) are represented using the concept of dependency. While providing some satisfactory findings, our proposal has also given light to some interesting questions that we have tackled or are still dealing with, remarkably: Which are the foundations of COTS components selection? Which are the properties of interest when selecting COTS components and how do we formalize them? How do we build i* models in a consistent way? What is the precise meaning of the i* constructs that we use in our models? How do we organize the knowledge about the marketplace and how do we use this knowledge during selection? What type of tool-support is appropriate? In this chapter, we present our current state of research in the COTS components selection area and provide some partial answers to the questions above. Fri, 22 Feb 2013 10:02:54 GMT http://hdl.handle.net/2117/17922 2013-02-22T10:02:54Z Franch Gutiérrez, Javier; Mayol Sarroca, Enric; Quer Bosor, Maria Carme no Commercial Off-The-Shelf (COTS) components selection is an activity that plays an increasingly crucial role in the delivery of software systems. We are using i*, specially Strategic Dependency models, for driving this activity. Software domains are modeled as actors, and the relationships among them and with external actors (people, other software systems, organizations, etc.) are represented using the concept of dependency. While providing some satisfactory findings, our proposal has also given light to some interesting questions that we have tackled or are still dealing with, remarkably: Which are the foundations of COTS components selection? Which are the properties of interest when selecting COTS components and how do we formalize them? How do we build i* models in a consistent way? What is the precise meaning of the i* constructs that we use in our models? How do we organize the knowledge about the marketplace and how do we use this knowledge during selection? What type of tool-support is appropriate? In this chapter, we present our current state of research in the COTS components selection area and provide some partial answers to the questions above. http://hdl.handle.net/2117/16253 Title: An adaptative user interface for genealogical document transcription Authors: Mayol Sarroca, Enric Abstract: Lately, genealogy has become a hobby not only in the United States, UK or France but also in many other countries where it is now widespread. The main sources of information for genealogists are different kinds of genealogical documents (census, church vital records, wills, …). In fact, and specifically in Spain, several projects to digitalize heritage and genealogical documentation have developed recently, in order to improve its access and to preserve its conservation state. Such digital information is useful, but it would be even more useful to have its transcription in a searchable support like databases or web repositories. This chapter analyses the opportunities and characteristics of such transcription projects and describes a transcription user interface tool. This proposal allows for easy, intuitive and fast design of a user interface to transcript genealogical documentation, in agreement with the contents of each different kind of genealogical documents. Given an XML Schema (XSD) describing a genealogical document structure and contents, this tool allows the user to adapt and personalize a user interface to transcribe the document contents, while obtaining an XML file to be stored in some database management system or to be shared among genealogists. At any moment during the transcription process, user interface may be adapted to the user requirements and to the document characteristics, so, this adaption is dynamic, intuitive and user friendly. Fri, 13 Jul 2012 11:29:20 GMT http://hdl.handle.net/2117/16253 2012-07-13T11:29:20Z Mayol Sarroca, Enric no Lately, genealogy has become a hobby not only in the United States, UK or France but also in many other countries where it is now widespread. The main sources of information for genealogists are different kinds of genealogical documents (census, church vital records, wills, …). In fact, and specifically in Spain, several projects to digitalize heritage and genealogical documentation have developed recently, in order to improve its access and to preserve its conservation state. Such digital information is useful, but it would be even more useful to have its transcription in a searchable support like databases or web repositories. This chapter analyses the opportunities and characteristics of such transcription projects and describes a transcription user interface tool. This proposal allows for easy, intuitive and fast design of a user interface to transcript genealogical documentation, in agreement with the contents of each different kind of genealogical documents. Given an XML Schema (XSD) describing a genealogical document structure and contents, this tool allows the user to adapt and personalize a user interface to transcribe the document contents, while obtaining an XML file to be stored in some database management system or to be shared among genealogists. At any moment during the transcription process, user interface may be adapted to the user requirements and to the document characteristics, so, this adaption is dynamic, intuitive and user friendly. http://hdl.handle.net/2117/16252 Title: Agile approach to business intelligence as a way to success Authors: Fernández González, Jorge; Mayol Sarroca, Enric; Pastor Collado, Juan Antonio Abstract: In this chapter we present an overview of several methodological approaches used in business intelligence (BI) projects, as well as data warehouse projects. This study reveals that some of them reveal weaknesses, since they are not specifically defined for BI projects, and thus they do not fit specific BI project characteristics or user requirements. These may be the main cause explaining that there is not a broadly accepted BI methodology by practitioners. Even though the goal to find the “best BI methodology” is difficult (or impossible) to meet, we think that any best-class BI methodology may follow an agile approach to better fit BI project characteristics and practitioners’ requirements. In this sense, we have analysed BI project characteristics as well as agile principles defined in the Agile Manifesto, and we have identified a strong relationship between these two sources. In this chapter, we show this strong relationship between the so-called critical success factors for BI projects and the Agile principles. Therefore, based on our analysis, we consider that successful BI methodologies must follow an agile approach. Fri, 13 Jul 2012 10:34:39 GMT http://hdl.handle.net/2117/16252 2012-07-13T10:34:39Z Fernández González, Jorge; Mayol Sarroca, Enric; Pastor Collado, Juan Antonio no In this chapter we present an overview of several methodological approaches used in business intelligence (BI) projects, as well as data warehouse projects. This study reveals that some of them reveal weaknesses, since they are not specifically defined for BI projects, and thus they do not fit specific BI project characteristics or user requirements. These may be the main cause explaining that there is not a broadly accepted BI methodology by practitioners. Even though the goal to find the “best BI methodology” is difficult (or impossible) to meet, we think that any best-class BI methodology may follow an agile approach to better fit BI project characteristics and practitioners’ requirements. In this sense, we have analysed BI project characteristics as well as agile principles defined in the Agile Manifesto, and we have identified a strong relationship between these two sources. In this chapter, we show this strong relationship between the so-called critical success factors for BI projects and the Agile principles. Therefore, based on our analysis, we consider that successful BI methodologies must follow an agile approach. http://hdl.handle.net/2117/16112 Title: Selección de componentes Off-The-Shelf Authors: Carvallo Vega, Juan Pablo; Franch Gutiérrez, Javier Abstract: La mayoría de sistemas de software actuales se construyen integrando componentes de software de diferente naturaleza y orígenes. La existencia de un enorme y creciente mercado de componentes desarrollados por terceros ha hecho de esta tecnología “la” forma estándar de desarrollo de software. Estos componentes se denominan componentes OTS, de las siglas inglesas “Off-The- Shelf” (Li et al., 2008), aludiendo a su disponibilidad similar a la de un libro que está disponible en una estantería. Los componentes OTS pueden ser componentes comerciales, llamados componentes COTS, por “Commercial OTS” (Carney and Long, 2000); o software de código abierto, abreviados como OSS, por “Open Source Software” (Madanmohan and Rahul, 2004). Los componentes OTS, una vez personalizados, son integrados utilizando software desarrollado a medida, e incluyendo eventualmente capacidades de interacción con otros subsistemas ya existentes (p.e., sistemas legados). Sin embargo, a pesar de sus beneficios potenciales (especialmente reducción de costes y tiempo de desarrollo), el diseño de software basado en componentes OTS también conlleva nuevos riesgos y retos para la Ingeniería de Software. Uno de sus procesos más críticos es el proceso de selección de componentes a ser integrados: si un componente es seleccionado erróneamente, el riesgo de fracaso de un proyecto se incrementa dramáticamente (Vitharana et al., 2003; Bhuta y Boehm, 2007). Los factores que afectan al proceso de selección son cuantiosos y muy variados, pudiendo ser de naturaleza funcional o técnica, pero también política o legal (Reifer et al., 2003). En este capítulo nos centramos en el estudio de los procesos de selección de componentes OTS. Después de precisar qué entendemos por componente OTS y enumerar las actividades que tienen lugar en su presencia, nos centraremos en el proceso de selección, resumiendo algunas propuestas actuales. A continuación, discutiremos el uso de modelos de calidad del software en la selección de componentes. Seguidamente, incidiremos en un tipo particular de procesos de selección, los procesos conducidos por pliegues de condiciones. Acabaremos el capítulo con una breve discusión de los puntos más relevantes presentados. Thu, 21 Jun 2012 09:10:12 GMT http://hdl.handle.net/2117/16112 2012-06-21T09:10:12Z Carvallo Vega, Juan Pablo; Franch Gutiérrez, Javier no La mayoría de sistemas de software actuales se construyen integrando componentes de software de diferente naturaleza y orígenes. La existencia de un enorme y creciente mercado de componentes desarrollados por terceros ha hecho de esta tecnología “la” forma estándar de desarrollo de software. Estos componentes se denominan componentes OTS, de las siglas inglesas “Off-The- Shelf” (Li et al., 2008), aludiendo a su disponibilidad similar a la de un libro que está disponible en una estantería. Los componentes OTS pueden ser componentes comerciales, llamados componentes COTS, por “Commercial OTS” (Carney and Long, 2000); o software de código abierto, abreviados como OSS, por “Open Source Software” (Madanmohan and Rahul, 2004). Los componentes OTS, una vez personalizados, son integrados utilizando software desarrollado a medida, e incluyendo eventualmente capacidades de interacción con otros subsistemas ya existentes (p.e., sistemas legados). Sin embargo, a pesar de sus beneficios potenciales (especialmente reducción de costes y tiempo de desarrollo), el diseño de software basado en componentes OTS también conlleva nuevos riesgos y retos para la Ingeniería de Software. Uno de sus procesos más críticos es el proceso de selección de componentes a ser integrados: si un componente es seleccionado erróneamente, el riesgo de fracaso de un proyecto se incrementa dramáticamente (Vitharana et al., 2003; Bhuta y Boehm, 2007). Los factores que afectan al proceso de selección son cuantiosos y muy variados, pudiendo ser de naturaleza funcional o técnica, pero también política o legal (Reifer et al., 2003). En este capítulo nos centramos en el estudio de los procesos de selección de componentes OTS. Después de precisar qué entendemos por componente OTS y enumerar las actividades que tienen lugar en su presencia, nos centraremos en el proceso de selección, resumiendo algunas propuestas actuales. A continuación, discutiremos el uso de modelos de calidad del software en la selección de componentes. Seguidamente, incidiremos en un tipo particular de procesos de selección, los procesos conducidos por pliegues de condiciones. Acabaremos el capítulo con una breve discusión de los puntos más relevantes presentados. http://hdl.handle.net/2117/15942 Title: Fostering the adoption of i* by practitioners: some challenges and research directions Authors: Franch Gutiérrez, Javier Abstract: The i* framework is a widespread formalism in the software engineering discipline that allows expressing intentionality of system actors. From the time it was issued, in the mid-nineties, a growing research community has adopted it either in its standard form or formulating variations in order to adapt it to some particular purpose. New methods, techniques and tools have made evolve the framework in a way that it may be currently considered quite mature from the scientific perspective. However, the i* framework has not been transferred to practitioners at the same extent yet: industrial experiences using i* are not many and have been mainly conducted by i* experts that are part of that very research community. Therefore, it may be argued that some steps are needed for boosting the adoption of i* by practitioners. In this chapter, we identify some scientific challenges whose overcoming could represent a step towards this goal. For each challenge, we present the problem that is addressed, its current state of the art and some envisaged lines of research. Wed, 30 May 2012 09:18:16 GMT http://hdl.handle.net/2117/15942 2012-05-30T09:18:16Z Franch Gutiérrez, Javier no The i* framework is a widespread formalism in the software engineering discipline that allows expressing intentionality of system actors. From the time it was issued, in the mid-nineties, a growing research community has adopted it either in its standard form or formulating variations in order to adapt it to some particular purpose. New methods, techniques and tools have made evolve the framework in a way that it may be currently considered quite mature from the scientific perspective. However, the i* framework has not been transferred to practitioners at the same extent yet: industrial experiences using i* are not many and have been mainly conducted by i* experts that are part of that very research community. Therefore, it may be argued that some steps are needed for boosting the adoption of i* by practitioners. In this chapter, we identify some scientific challenges whose overcoming could represent a step towards this goal. For each challenge, we present the problem that is addressed, its current state of the art and some envisaged lines of research. http://hdl.handle.net/2117/11003 Title: Calidad de componentes software Authors: Carvallo Vega, Juan Pablo; Franch Gutiérrez, Javier; Quer Bosor, Maria Carme Abstract: En los últimos años se constata una tendencia creciente por parte de las organizaciones a desarrollar sus sistemas software mediante la combinación de componentes, en lugar de desarrollar dichos sistemas partiendo de cero. Esta tendencia es debida a varios factores. Entre ellos cabe destacar: la necesidad de las organizaciones de reducir los costes y el tiempo dedicados al desarrollo de los sistemas software; el crecimiento del mercado de componentes software; la reducción de la distancia entre clientes y proveedores de software gracias a la creación de nuevos canales de comunicación y marketing (p.e., www.componentsource.com); y la existencia de tecnologías que facilitan el desarrollo de sistemas basados en componentes. Thu, 13 Jan 2011 11:06:48 GMT http://hdl.handle.net/2117/11003 2011-01-13T11:06:48Z Carvallo Vega, Juan Pablo; Franch Gutiérrez, Javier; Quer Bosor, Maria Carme no En los últimos años se constata una tendencia creciente por parte de las organizaciones a desarrollar sus sistemas software mediante la combinación de componentes, en lugar de desarrollar dichos sistemas partiendo de cero. Esta tendencia es debida a varios factores. Entre ellos cabe destacar: la necesidad de las organizaciones de reducir los costes y el tiempo dedicados al desarrollo de los sistemas software; el crecimiento del mercado de componentes software; la reducción de la distancia entre clientes y proveedores de software gracias a la creación de nuevos canales de comunicación y marketing (p.e., www.componentsource.com); y la existencia de tecnologías que facilitan el desarrollo de sistemas basados en componentes. http://hdl.handle.net/2117/6470 Title: Competencias profesionales para el Grado en Ingeniería Informática Authors: Sánchez Carracedo, Fermín; Sancho Samsó, María Ribera; Botella López, Pere; García Almiñana, Jordi; Aluja Banet, Tomàs; Navarro Guerrero, Juan José; Balcázar Navarro, José Luis Abstract: Degrees in the EHEA (European Higher Education Area) must be designed based on professional skills, so that when the students finish their studies they become competent professionals in the labour market. In this paper we propose a weighted list of skills for a undergraduate degree in Informatics Engineering, classified into two groups: technical and generic. Technical skills are divided into five different itineraries:computer engineering, computer science, information systems, information technologies and software engineering. Los planes de Estudios del EEES (Espacio Europeo de Educación Superior) deben ser diseñados a partir de competencias profesionales, de forma que al final de sus estudios el egresado se convierta en un profesional competente en el mercado laboral. En este artículo se propone una lista de competencias ponderada para un título de Grado en Ingeniería Informática clasificadas en dos grupos: transversales y técnicas. Dentro de las técnicas se definen cinco itinerarios distintos: computación, ingeniería de computadores, ingeniería del software, sistemas de información y tecnologías de la Información. Thu, 25 Feb 2010 12:43:01 GMT http://hdl.handle.net/2117/6470 2010-02-25T12:43:01Z Sánchez Carracedo, Fermín; Sancho Samsó, María Ribera; Botella López, Pere; García Almiñana, Jordi; Aluja Banet, Tomàs; Navarro Guerrero, Juan José; Balcázar Navarro, José Luis no Especialidades, Itinerarios, Professional skills, Undergraduate degree in Informatics Engineering, Undergraduate degree in computing, Specialities, Itineraries Competencias profesionales, Grado en Ingeniería Informática Degrees in the EHEA (European Higher Education Area) must be designed based on professional skills, so that when the students finish their studies they become competent professionals in the labour market. In this paper we propose a weighted list of skills for a undergraduate degree in Informatics Engineering, classified into two groups: technical and generic. Technical skills are divided into five different itineraries:computer engineering, computer science, information systems, information technologies and software engineering. Los planes de Estudios del EEES (Espacio Europeo de Educación Superior) deben ser diseñados a partir de competencias profesionales, de forma que al final de sus estudios el egresado se convierta en un profesional competente en el mercado laboral. En este artículo se propone una lista de competencias ponderada para un título de Grado en Ingeniería Informática clasificadas en dos grupos: transversales y técnicas. Dentro de las técnicas se definen cinco itinerarios distintos: computación, ingeniería de computadores, ingeniería del software, sistemas de información y tecnologías de la Información.