http://sedici.unlp.edu.ar:80/handle/10915/134652 Thu, 12 Nov 2026 07:46:21 GMT 2026-11-12T07:46:21Z http://sedici.unlp.edu.ar:80/handle/10915/135182 Contribucion a revista Electronic Journal of SADIO; vol. 14 Nota sobre el contenido del volumen 14 del Electronic Journal of SADIO. Thu, 04 Jun 2015 00:00:00 GMT http://sedici.unlp.edu.ar:80/handle/10915/135182 2015-06-04T00:00:00Z Nota sobre el contenido del volumen 14 del Electronic Journal of SADIO. http://sedici.unlp.edu.ar:80/handle/10915/135177 Articulo XLIII Jornadas Argentinas de Informática e Investigación Operativa (43JAIIO)-XV Simposio Argentino de Ingeniería de Software (Buenos Aires, 2014); Electronic Journal of SADIO; vol. 14; https://sedici.unlp.edu.ar/handle/10915/41666 The development of mobile applications that combine Web Services from different providers --also referred as mashup applications-- is growing as a consequence of the ubiquity of bandwidth connections and the increasing number of available Web Services. In this context, providing higher maintainability to Web Service applications is a worth of matter, because of the dynamic nature of the Web. EasySOC solves this problem by decoupling mashups from application components. However, mobile devices have energy constraints because of the limitations in the current battery capacities. This work proposes a model that builds on the benefits of the EasySOC approach and improves this latter by assisting developers to select Web Service combinations that reduce energy consumption. We evaluated the feasibility of the model through a case study in which we compare the estimations provided by the model against real energy measurements and two handsets. The results indicated that our model had an efficacy of 81-85% for the analyzed case study. Thu, 04 Jun 2015 00:00:00 GMT http://sedici.unlp.edu.ar:80/handle/10915/135177 2015-06-04T00:00:00Z The development of mobile applications that combine Web Services from different providers --also referred as mashup applications-- is growing as a consequence of the ubiquity of bandwidth connections and the increasing number of available Web Services. In this context, providing higher maintainability to Web Service applications is a worth of matter, because of the dynamic nature of the Web. EasySOC solves this problem by decoupling mashups from application components. However, mobile devices have energy constraints because of the limitations in the current battery capacities. This work proposes a model that builds on the benefits of the EasySOC approach and improves this latter by assisting developers to select Web Service combinations that reduce energy consumption. We evaluated the feasibility of the model through a case study in which we compare the estimations provided by the model against real energy measurements and two handsets. The results indicated that our model had an efficacy of 81-85% for the analyzed case study. http://sedici.unlp.edu.ar:80/handle/10915/135176 Articulo Electronic Journal of SADIO; vol. 14 Stakeholders play an important role to establish the requirements of a software system. In fact, systems are built to meet the needs of some stakeholders. They are also source of key requirements; not reaching to all the stakeholders of a system jeopardizes its completeness since the requirements are not detected. In Requirement Engineering, the matter has not been dealt with the required depth and consistency, thus the notion of “stakeholders” remained ambiguous as well as their associated processes. Especially, there is a lack of clear concepts regarding their role in Web applications, a subject that seems controversial (as confirmed by literature). We made ourselves the following question: who are the web application stakeholders and how should we manage them? Our special interest focuses on the local web applicationsdevelopment organizations. For this, we have conducted some field research that covered not only the stakeholder-related aspects, but also other areas of the requirement processes. This field research is a first approach to the problem and provides some answers, but also raises questions and suggests possible answers to some others. Thu, 04 Jun 2015 00:00:00 GMT http://sedici.unlp.edu.ar:80/handle/10915/135176 2015-06-04T00:00:00Z Stakeholders play an important role to establish the requirements of a software system. In fact, systems are built to meet the needs of some stakeholders. They are also source of key requirements; not reaching to all the stakeholders of a system jeopardizes its completeness since the requirements are not detected. In Requirement Engineering, the matter has not been dealt with the required depth and consistency, thus the notion of “stakeholders” remained ambiguous as well as their associated processes. Especially, there is a lack of clear concepts regarding their role in Web applications, a subject that seems controversial (as confirmed by literature). We made ourselves the following question: who are the web application stakeholders and how should we manage them? Our special interest focuses on the local web applicationsdevelopment organizations. For this, we have conducted some field research that covered not only the stakeholder-related aspects, but also other areas of the requirement processes. This field research is a first approach to the problem and provides some answers, but also raises questions and suggests possible answers to some others. http://sedici.unlp.edu.ar:80/handle/10915/135170 Articulo Electronic Journal of SADIO; vol. 14 The costing of a product is a key factor in the marketing process. Its proper calculation can attract customers, which will ensure a company’s life and its business expansion. These considerations have driven the Centre for the Study of software Engineering at Universidad de la Frontera (CEIS-UFRO) to develop a method to define the cost of a web software product, based on use cases and productivity. This method is adaptable to the particular characteristics of any development process, any development team, any product and any company.This article describes the method and performs an initial validation by describing a quasi-experiment designed for Web applications developed by groups of three to five people. We have proved that: a. the method may be reproduced,b. effort estimation is sensitive to the definition of productivity, c. the subjectivity introduced by the estimators does not invalidate the method. For a complete validation of this method, different web products and a larger number of estimatorswith different levels of experience should be incorporated in a future replication. Thu, 04 Jun 2015 00:00:00 GMT http://sedici.unlp.edu.ar:80/handle/10915/135170 2015-06-04T00:00:00Z The costing of a product is a key factor in the marketing process. Its proper calculation can attract customers, which will ensure a company’s life and its business expansion. These considerations have driven the Centre for the Study of software Engineering at Universidad de la Frontera (CEIS-UFRO) to develop a method to define the cost of a web software product, based on use cases and productivity. This method is adaptable to the particular characteristics of any development process, any development team, any product and any company.This article describes the method and performs an initial validation by describing a quasi-experiment designed for Web applications developed by groups of three to five people. We have proved that: a. the method may be reproduced,b. effort estimation is sensitive to the definition of productivity, c. the subjectivity introduced by the estimators does not invalidate the method. For a complete validation of this method, different web products and a larger number of estimatorswith different levels of experience should be incorporated in a future replication. http://sedici.unlp.edu.ar:80/handle/10915/135166 Articulo Electronic Journal of SADIO; vol. 14 Cloud Computing is the dynamic provisioning of physical and virtual resources as services offering by providers, to optimize performance and utilization of their resources. Consumers contract Cloud services and negotiate service level agreements. Some consumers plan to migrate functionality of their legacy systems to Cloud Computing, to minimize investment on their own infrastructure and to obtain new software solutions that rapidly adapt to changes in the system environment. Therefore, the contribution of this work is to classify different types of migration of legacy systems to Cloud Computing, according to the characteristics of the applications and the deployment models of Cloud Computing. Thus, a workflow for functionality migration is proposed, based on the experience in system conversion projects and the analyzed characteristics of Cloud environments. Finally, some security risks are evaluated in the migration process and some recommendations are listed. Thu, 04 Jun 2015 00:00:00 GMT http://sedici.unlp.edu.ar:80/handle/10915/135166 2015-06-04T00:00:00Z Cloud Computing is the dynamic provisioning of physical and virtual resources as services offering by providers, to optimize performance and utilization of their resources. Consumers contract Cloud services and negotiate service level agreements. Some consumers plan to migrate functionality of their legacy systems to Cloud Computing, to minimize investment on their own infrastructure and to obtain new software solutions that rapidly adapt to changes in the system environment. Therefore, the contribution of this work is to classify different types of migration of legacy systems to Cloud Computing, according to the characteristics of the applications and the deployment models of Cloud Computing. Thus, a workflow for functionality migration is proposed, based on the experience in system conversion projects and the analyzed characteristics of Cloud environments. Finally, some security risks are evaluated in the migration process and some recommendations are listed.