Search

Los sistemas software son cada vez más multidisciplinares y complejos. Su implementación de forma satisfactoria se ha convertido en un desafío continuo para cualquier tipo de empresa u organismo. Llevar a cabo la “transformación digital” de una empresa u organización implica, entre otras cosas, la adopción de tecnologías digitales avanzadas al objeto de mejorar su funcionamiento, eficiencia, productos y servicios. Es decir, para las empresas y organizaciones supone la aceptación e integración de tecnologías como internet, la nube y los servicios en línea, el internet de las cosas, la automatización de procesos, el análisis masivo de datos, la inteligencia artificial, y otros avances tecnológicos. En este contexto, hace ya unos años, apareció la tecnología blockchain. Ésta constituye también una de esas tecnologías que están impulsando la comentada “transformación digital”, gracias a sus características únicas y su potencial para abordar ciertas limitaciones de los sistemas tradicionales. Además, dado su carácter transversal1, esta tecnología está permitiendo la disrupción en la economía y en la empresa más allá de las conocidas criptomonedas. Solo habría que realizar una búsqueda rápida por internet para evidenciar que estamos asistiendo a una importante apuesta del mercado hacia los desarrollos basados en esta tecnología disruptiva. Esto es debido, fundamentalmente, a su capacidad para transformar la forma en que se registran las transacciones y la manera en que se almacenan y recuperan los datos. En la tecnología blockchain, los llamados smart contracts (contratos inteligentes) podrían actuar como complemento o sustituto de los contratos legales, ya que pueden automatizar y ejecutar acuerdos de manera eficiente y transparente. Estos “contratos digitales” se registran en un lenguaje informático que es desplegado y ejecutado en una plataforma blockchain. Estos scripts contienen una serie de reglas y condiciones preestablecidas y, cuando se cumplen las mismas, el sma

El control y trazabilidad de muestras biológicas es un problema a resolver en un gran número de ámbitos, pero en lo que se refiere a laboratorios de reproducción humana asistida, existen una serie de factores ambientales y del propio contexto de trabajo que hace que la práctica esté expuesta a múltiples posibles incidentes. En este contexto, se ha colaborado en un proyecto de transferencia tecnológica denominado “TRABIS - TRAzabilidad de muestras BIológicaS de reproducción humana asistida”. TRABIS es una solución tecnológica e innovadora que permite la ejecución y la monitorización de procesos de reproducción humana asistida, de manera integrada con dispositivos físicos de laboratorio para mejorar el control, salvaguarda y trazabilidad de muestras biológicas de paciente. Para verificar y validar la solución tecnológica, se ha realizado el pilotaje de la solución en Inebir (clínica privada de Reproducción Asistida).

Teaching in Software Engineering involves learning strategies to address so ft- ware discovery, development and operations. However, in the literature we can find strategies that are defined based on constructs that can even vary between similar strategies, which makes it difficult to learn these strategies. Here it is proposed a technique consisting of a canvas that organizes knowledge into a set of basic constructs that allow it to be applied to any soft- ware strategy to describe it. Post-its can be included on the canvas in an agile way to conceptually define any software strategy taught in class. It is intended to improve the experience ofstudents during learning, so that they are active participants instead ofpassive observers, thus facilitatingmeaningful learning that endows the student with the ability to acquire concepts and establish re- lationships on the knowledge acquired. To validate the proposal, an evaluation of the student's experience during learning with the UEQ (User Experience Questionnaire) technique has been carried out. The results show that the tech- nique is perceived by students as a novel, stimulating and attractive learning technique., La enseñanza en Ingeniería del Software implica el aprendizaje de estrategias que permitan abordar el descubrimiento, desarrollo y operaciones software. Sin embargo, en la literatura podemos encontrar estrategias que son definidas en base a constructos que pueden incluso variar entre estrategias similares, lo que dificulta el aprendizaje de dichas estrategias. El presente trabajo propone una técnica consistente en un lienzo que organiza el conocimiento en un conjunto de constructos básicos y que permiten ser aplicados a cualquier estrategia software para describirla. En el lienzo pueden incluirse post-its de forma ágil para definir conceptualmente cualquier estrategia software que se enseñe en clase. Se pretende mejorar la experiencia de los alumnos durante el aprendizaje, para que sean participantes activos en lugar de observadores pasivos, facilitando así un aprendizaje significativo que dote al alumno de la capacidad de adquirir conceptos y establecer relaciones sobre el conocimiento adquirido. Para validar la propuesta, se ha realizado una evaluación de la experiencia del alumno durante el aprendizaje con la técnica UEQ (User Experience Questionnaire). Los resultados muestran que la técnica es percibida por los alumnos como una técnica de aprendizaje novedosa, estimulante y atractiva.

One of the key benefits of blockchain technology is its ability to keep a per manent, unalterable record of transactions. In business environments, where companies interact with each other without a centralized authority to ensure trust between them, this has led to blockchain platforms and smart contracts being proposed as a means of implementing trustworthy collaborative pro cesses. Software engineers must deal withthem to ensure the quality of smart contracts in all phases of the smart contract lifecycle, from requirements spec ifications to design and deployment. This broad scope and criticality of smart contracts in business environments means that they have to be expressed in a language that is intuitive, easy-to-use, independent of the blockchain platform employed, and oriented towards software quality assurance. In this paper we present a key component: a first outline of a UML-based smart contract meta-model that would allow us to achieve these objectives. This meta-model will be enriched in future work to represent blockchain environments and automated testing.

The advance in the digital world has caused a growth of complexity in innovation. Traditional approaches to innovation, based on reductionism, face greater difficulties. That is why we have witnessed the growth of those known as System of Systems (SoS). There is a wide variety of methodologies and domains of application in the literature to form framed solutions in the context of SoS, but there is no unified c onsensus f or i ts u se a nd e ven l ess when it comes to agile environments of continuous integration and deployment in which traceability requirements are critical. In recent years, the need to have traceability software that continuously records and monitors the trace of the entities that interact with it has become an essential feature. In addition, over the years there has been evidence of errors caused by poor traceability control. Therefore, this document presents an agile framework that aims to guarantee the traceability of a SoS from the early stages. This framework unifies the discovery, development and operations, providing full coverage in the conformation of the solution. Finally, we present a case study as future work, which is based on the application of our framework on smart laboratories for assisted reproduction.

Blockchain technology is a chain of cryptographically linked blocks. It was designed to be immutable, so that the identity and traceability of the information entered would be guaranteed. After analyzing several traceability solutions, in the context of a Spanish company project, it was found that in order for a traceability solution to be efficient and agile, an additional layer is necessary in the blockchain. Since this need originated in the industrial sector, the subject has awakened considerable interest in the research community. This paper explains why the extra layer is essential and why it should ideally be totally independent of the information that is recorded on the blockchain network. Although data in a blockchain network is immutable, the paper also outlines the need for additional verification mechanisms capable of determining whether the raw data was correct. Finally, it includes planned future work.

ERP systems are composed of different functional modules on which each one addresses a different business area. Developments on these modules are managed independently on each one, which allow to handle and address the management of many related information requirements. In this context the startup G7Innovation works for its product iMEDEA. In this study we have combined two methodologies, Design Sprint and NDT 4.0; and systematized the development of ERP system modules. This combination allows you to use Design Sprint to generate and validate prototyping, and NDT 4.0 to do the study, analysis, and design of the software to be developed. In addition, according to the specifications defined in NDT, the code generation of the ERP module can be automated. This proposal has been validated in a case study in collaboration with the startup G7Innovation, where we have applied both methodologies on Odoo, an open source ERP system based in Python language. Thanks to the use of these two methodologies we have produced a module related to the needs of the clinic by reducing costs, times and human failures.

In recent years, agile methodologies have been consolidated and extended in organizations that develop software in Web environments. For this reason, the development methodology of these organizations will not only be related to Services, but also to the Web Engineering paradigm. These organizations are heading for incorporating software development methodologies whose paradigm can allow integration, naturally and in the earlier stages of Web applications develop with the services of the organization that described and published in the Services Portfolio. The aim of this study will be to analyze the current state of the art in the process of discovering services in early stages of agile software development with focus on those identified requirements that could be covered with the services included in the Service Portfolio. We have identified 20 relevant papers through conducting a double systematic literature review (SLR). It is concluded that no study has been found that can solve the entire process of discovering candidate services within an organization that cover the requirements of a new application developed with agile methodologies. At the same time, guidelines have been found to formalize the solution to this problem and fill in that gap of knowledge by proposing in a single process, the formalization of a requirement based on agile techniques, which can be managed against a Services Portfolio

Over last decade, Assisted Reproductive Treatment (ART) has become a very used health service by more and more people around the world because of problems such as the delay in the maternity age, singleparent couples, etc. In this context, health agencies have performed innovations to improve healthcare processes of ARTs, to optimize the performance of health professionals who work in fertilization laboratories and to improve Biological Sample Management (BSM) and sample traceability in ART. However, there are important handicaps in ART processes from the point of view of quality, safety and management. On the one hand, these processes are mainly based on manual execution tasks and manual control tasks. This excess of manual tasks could lead to fatal traceability and safety errors during BSM. On the other hand,ART processes require real, interoperable and traceable communications between different software systems that have to collaborate together (health information systems, biological sample management systems, patient management systems, etc.), but, at present, it is possible to identify some limitations in this domain, that is, the domain of systems of systems (SoS). This paper aims to conduct an exhaustive study was carried out both in the research community and in the commercial field to identify and analyze SoS solutions and theoretical proposals forBSM in ART processes. We have applied the Systematic Literature Review (SLR) methodology to carry out our study and we conclude it is a very young research line that shows a growing trend and that in the actuality there are very few technologies that deal with the problem of the BSM in ART.After analyzing the results, this paper presents as future work an initial Model-Driven conceptual solution to improve BSM in ART.

Currently, it is difficult to find platforms connected to health systems that exploit data in a coherent way and that allow, on the one hand, to send sanitary warnings and on the other, to validate the performance of medical specialists according to the models set by the best practices of the specialty. This chapter aims to explain the CIPHER project, a decision support system (DSS), based on machine-learning (ML) and big data technologies, capable of alerting a clinician when a situation of risk is detected in a patient suffering from a certain pathology, so that could be able to carry out the appropriate measures. CIPHER, is a project born from scratch. For its development, different methodologies, such as design sprint (for product prototyping), navigational development techniques (for product analysis and testing) or SCRUM (for product development), have been applied. In addition, this product has been defined in direct contact with medical specialists and under the umbrella of international standards and models such as ISO 13606, SNOMED, REGICOR or CHADS2. As a result of the development of this product, we have obtained a DSS, which offers health professionals the possibility of receiving alerts from patientswhomay be at risk of suffering from a specific pathology, based on a series of criteria defined by international standards. Moreover, health professionals would be able to find hidden symptomatology of the pathology mentioned above, which, a priori, are not known.

The validation of any new methodological proposal demands several real-life implementations. However, organizations are reluctant to invest without the firm guarantee that they will be returned the entire expended amount of money. For this purpose, expert judgment techniques are very useful to provide a less-costly initial validation that, when positive, may encourage organizations to use these new proposals. Therefore, the primary goal of the paper will be to assess how expert judgment techniques based on the Delphi method can be applied to Web Engineering field and, more in particular, to assess the validity of the NDT-Agile framework. NDT-Agile is a framework that combines Agile and Web Engineering techniques to meet Capability Maturity Model Integration development goals. The paper presents a real example of an application of a Delphi-based expert judgment method to assess NDT-Agile framework validity, explaining the design as well as the selection and usage of the different techniques it involves. The application of the method will allow assessing benefits and limitations of use in Web Engineering. As a main conclusion, we will state the utility of the proposed methods to obtain a low-resource initial validation of a certain proposal. Finally, we will identify further lines of research related to the analyzed topics.

Value delivery is becoming an important asset for an organization due to increasing competition in industry. Therefore, companies apply Agile Software Development (ASD) to be more competitive and reduce time to market. Using ASD for the development of systems implies that established approaches of Requirements Engineering (RE) undergo some changes in order to be more flexible to changing requirements. To this end, the field of agile RE is emergent and different process models for agile RE have arisen. The aim of this paper is to build an abstract layer about the variety of existing process models by means of a metamodel for agile RE. It has been created in several iterations and relies on the evaluation of related process models. Furthermore, we have derived process models for agile RE in industry by presenting instances of the metamodel in two different cases: one is based on Scrum whereas the other is based on Kanban. This paper contributes to the software development body of knowledge by delivering a metamodel for agile RE that supports researchers and practitioners modeling and improving their own process models. We can conclude that the agile RE metamodel is highly relevant for the industry as well as for the research community, since we have derived it following empirical research in the field of ASD.

The Model-Driven Engineering (MDE) has been used in recent years to promote better results in the development of Web Applications, in the field that has been called Model-Driven Web Engineering (MDWE). One of the advantages of applying MDWE is that it offers a solution to reduce the cost of the tests without affecting their quality execution. This paper presents the application of a MDWE methodology (Navigational Development Techniques, NDT) that provides support for all the phases of the lifecycle of a software project development proposing transformations between these phases, to manage the test phase of a real-world case study named ADAGIO. This project, among other goals, proposes the development of a web application whose main objective is to offer researchers the possibility of integrating and consolidating heterogeneous data sources, showing a unified vision of them, allowing to simplify the search task in different repositories as well as the relationship between the sources found.

Today's world economic situation is ruled by issues such as reducing cost, improving quality, maximizing profit, and improving and optimizing processes at organizations. In this context, business process management can be an essential strategy, but it is not usually consolidated at software organizations because software process properties involve a complex business process management application on software lifecycle. Consequently, software organizations often focus on Software Process Modeling (SPM), and each involved role performs process execution and orchestration independently and manually. This fact makes software processes maintenance, monitoring, and measurement become difficult tasks. This paper proposes a model‐based approach for SPM taking into account concepts related to process execution, orchestration, and monitoring. It is framed into a model‐driven engineering‐based and toolbased framework: Process Lifecycle Management for Business Software (PLM4BS). We present a SPM metamodel and its concrete syntax (through Unified Modeling Language profiles) that lays the foundation for extending PLM4BS. Its underlying metamodel allows managing processes automatically. Furthermore, PLM4BS improves current state‐of‐the‐art proposals in 6 dimensions: expressiveness, understandability, granularity, measurability, orchestrability, and business variables and rules. Also, PLM4BS has been evaluated in a multiple‐case study, in which the 6 mentioned dimensions were already validated.

Within the development of software systems, the development of web applications may be one of the most widespread at present due to the great number of advantages they provide such as: multiplatform, speed of access or the not requiring extremely powerful hardware among others. The fact that so many web applications are being developed, makes enormous the volume of information that it is generated daily. In the management of all this information, the entity reconciliation (ER) problem occurs, which is to identify objects referring to the same real-world entity. This paper proposes to give a solution to this problem through a web perspective based on the Model-Driven Engineering paradigm. To this end, the Navigational Development Techniques (NDT) methodology, that provides a formal and complete set of processes that bring support to the software lifecycle management, has been taken as a reference and it has been extended adding new activities, artefacts and documents to cover the ER. All these elements are defined by a process named Model-Driven Entity ReconcilIAtion (MaRIA), that can be integrated in any software development methodology and allows one to define the ER problem from the early stages of the development. In addition, this proposal has been validated in a real-world case study helping companies to reduce costs when a software product that must give a solution to an ER problem has to be developed

El Trabajo Fin de Grado (TFG) juega un papel muy im portante en el proceso formativo de los grados en Inge niería Informática, ya que, a través de la ejecución sa tisfactoria de un proyecto, se pretende que el alumno/a tenga su primera experiencia profesional tutorada co mo ingeniero/a en proyectos de ingeniería y tecnología del Software. En este artículo se presenta una propues ta de metodología de trabajo seguida por nuestro grupo de investigación a la hora de tutorar, dirigir y ejecutar los TFG de las titulaciones de grado relacionadas con la Ingeniería Informática. Esta metodología, está com puesta por tres fases principales: la fase de diseño del producto (basada en metodología Design Sprint), la fa se de análisis de la solución (basada en la metodología NDT) y el diseño, implementación y pruebas de la so lución (basada en metodologías ágiles de desarrollo). Gracias a esta forma de trabajo, el alumno es capaz de ejecutar el TFG de una forma sistemática, ordenada y teniendo una visión clara del producto y solución que debe desarrollar., The final project plays a very important role in the for mative process of the degrees in Computer Enginee ring, because, the satisfactory execution of a project, intends that the student has his first professional tuto red experience as real engineer in projects of software engineering and technology. In this paper we present a proposal of work methodology followed by our re search group when it comes to tutoring, directing and executing the final project in the degree programs re lated to Computer Engineering. This methodology is composed of three main phases: the design phase of the product (based on Design Sprint methodology), the solution analysis phase (based on the NDT methodo logy) and the design, implementation and testing of the solution phase (based on in agile development metho dologies). Thanks to this kind of working, the student is able to execute the final project in a systematic and orderly way, having a clear vision of the product and solution to be developed.

Health information systems are increasingly complex, and their development is presented as a challenge for software development companies offering quality, maintainable and interoperable products. HL7 (Health level 7) International, an international non-profit organization, defines and maintains standards related to health information systems. However, the modelling languages proposed by HL7 are far removed from standard languages and widely known by software engineers. In these lines, NDT is a software development methodology that has a support tool called NDT-Suite and is based, on the one hand, on the paradigm of model-driven engineering and, on the other hand, in UML that is a widely recognized standard language. This paper proposes an extension of the NDT methodology called MoDHE (Model Driven Health Engineering) to offer software engineers a methodology capable of modelling health information systems conforming to HL7 using UML domain models.

Business Processes Management (BPM) is a widely consolidated business strategy to improve and optimize the internal operation of any company. However, BPM is not usually simple to apply in software organizations because Software Processes (SPs) involve high degree of creativity, abstraction and rework, among other aspects. This situation provokes that these companies usually focus on modeling their processes but later, the orchestration and execution are manually and/or unilaterally performed by each involved role. This situation makes each SP difficult to maintain, monitor, evolve and measure. At present, there are model-based proposals to model SPs, but most of them fail to define the execution context of the process. This paper presents PLM4BS, a model-driven framework to support modeling, execution and orchestration of SPs. It has been successfully validated in different real environments, what has returned us valuable feedback to improve PLM4BS in the near future.

Gherkin scenarios are examples of the behavior of the system under development. They maybe part of the requirement specification, they may be part of the test suite and they are an excellenttool for gathering information among stakeholders, testers and developers. However,little work have been done formalizing Gherkin scenarios and modelling them as part of UMLdiagrams. This paper introduces an abstract syntax and concrete syntax for modeling Gherkinscenarios in UML Use Case diagrams. This paper also introduces a tool for running Gherkinscenarios from UML Use Case diagrams as test cases

En los últimos años la importancia de la Web y los desarrollos Web en la vida de ciudadanos y empresas ha aumentado significativamente. Desde sus inicios, la comunidad investigadora intentó definir aproximaciones metodológicas para los entornos Web. De ese modo, mientras que los sistemas Web eran desarrollados inicialmente sin seguir una aproximación estructurada que pudiera garantizar resultados de calidad, aparecieron diferentes propuestas que ayudaron a establecer la Ingeniería Web como una rama diferenciada dentro de la Ingeniería del Software con líneas de investigación específicas. Podemos por tanto afirmar que los Sistemas Web, aquellos desarrollados para ser publicados y consumidos en Internet, son el sujeto de estudio de la Ingeniería Web, , la cual puede definirse como la aplicación sistemática, cuantificable y estructurada al desarrollo, evolución y mantenimiento de aplicaciones Web. Los sistemas Web se caracterizan, entre otros aspectos, por una aproximación flexible a los requisitos y por la necesidad de ciclos cortos de feedback, con el fin de adaptarse y ajustarse a nuevas necesidades de clientes y usuarios. Además, los Sistemas Web incorporan características especiales como estructuras navegacionales complejas, necesidad de reducir el tiempo de desarrollo y puesta en producción, o la importancia de los requisitos de seguridad y mantenimiento. Aunque algunas de estas características aparecen también en sistemas de otro tipo, es en los entornos Web donde se manifiestan de manera conjunta e intensa. Por otro lado, uno de los principios de las metodologías Ágiles es abrazar el cambio, por lo que las aproximaciones Ágiles podrían ofrecer un marco adecuado para algunas de las características específicas de los sistemas Web Como es sabido, las aproximaciones clásicas a los requisitos, que incluyen una fase inicial de definición e introducción de los mismos, demandan un entorno estable y no cambiante. En general, este no es el caso de los entornos Web, donde

In recent years hybrid approaches focusing on user needs by integrating Agile methodologies (e.g. Scrum, Kanban or Extreme Programming) with Human-Centered Design (HCD) have proven to be particularly suitable for the development of Web systems. On the one hand, HCD techniques are used for requirements elicitation and, on the other hand, they can be utilized to elicit navigation relationships in Web projects. Navigation is one of the basic pillars of Web systems and also a fundamental element for the methodologies within the Model-Driven Web Engineering (MDWE) field. This paper presents an approach to model Agile requirements by means of integrating HCD techniques into Agile software development. We contribute to the software development body of knowledge by creating the concept of a Context-based Persona Story (CBPS) and formalizing it through a metamodel. Our approach covers the modelling of users and stakeholders by personas as well as the visualization of the context of use by storyboards. The attributes of the context of use enable us to elicit acceptance criteria for describing the scope of an Agile requirement.

El objetivo principal de la presente Tesis Doctoral será proponer en un único proceso, la formalización de un requisito, fundamentándolo en técnicas ágiles (debido a su agilidad y completitud), que pueda ser gestionado contra un Catálogo de Servicios, a fin de descubrir qué Servicios dentro del contexto, son susceptibles de ser incorporados en el desarrollo de la nueva aplicación para dar cobertura a ese requisito. El cuerpo de esta Tesis Doctoral pues, se cimenta sobre la definición de una serie de metamodelos. Para ello, se define un metamodelo en el que se formalizarán los Servicios pertenecientes al Catálogo de Servicios de dicha organización, que contendrá la funcionalidad identificada y viva, en el contexto, de forma normalizada. A su vez, se define un metamodelo de requisitos que permita la formalización ágil, temprana y completa de los nuevos requisitos. Para este punto será necesario el uso de las nuevas técnicas y metodologías ágiles que se han usado con buen resultado, precisamente, para disponer de un conjunto homogéneo de requisitos funcionales y no funcionales, completo y ágil. Como resultado de la presente Tesis Doctoral, obtenemos un proceso sistemático y coherente para el descubrimiento de los Servicios Candidatos, definiendo la relación entre los metamodelos que nos permita descubrir qué Servicios dentro del Catálogo de Servicios dan cobertura a un conjunto total o parcial de los requisitos, es decir, identificar los Servicios Candidatos para su análisis, mediante la propuesta de un algoritmo que realice las consultas entre los diferentes campos de los metamodelos basada en la puntuación de dichas búsquedas, a partir de esa correspondencia. Así mismo se plantea una arquitectura tecnológica capaz de soportar dicho proceso, el framework DS4aRE. En conclusión, esta Tesis Doctoral plantea una solución a un problema específico: realizar el proceso sistemático y coherente para el descubrimiento de los Servicios Candidatos dentro del contexto de una organ

Agile and Web Engineering show important synergies, making Agile a common approach for Web development. Besides, several initiatives emerged to support CMMI-DEV within Agile, where CMMI-DEV aims to improve organizations’ software development process. An approach integrating Agile, Web and CMMI-DEV might be of great value, since they might allow Web development teams to use Agile, as well as progress through CMMI-DEV maturity levels. For this purpose, we developed NDT-Agile, an NDT-based Agile framework to achieve the goals of CMMI-DEV in the context of Web Engineering. It was developed by mapping Agile practices to the goals of CMMI-DEV so as to identify existing gaps. Next, we searched for suitable Agile practices to cover the gaps and integrated them into a framework called NDTAgile, which was validated using an expert-judgment technique: the Delphi method. This paper describes how we integrated Agile and CMMI-DEV into a Web Engineering framework. Besides, it also analyzes its initial evaluation, together with a first tool developed to support it.

Organizar excursiones o meriendas, montar un equipo del juego on-line de moda, estudiar en grupo y muchas cosas más son actividades habituales en jóvenes (y no tan jóvenes). Las actividades anteriores pueden enmarcarse en la definición de proyecto, ya que todas cuentan con un marco temporal definido, tienen recursos limitados que es necesario gestionar y plantean objetivos que se desea cumplir. Sin embargo, basándonos en nuestra experiencia docente en asignaturas universitarias relacionadas con la gestión y dirección de proyectos informáticos, la enseñanza de esta materia es difícil. Al ser asignaturas de últimos cursos universitarios los alumnos llegan con malos hábitos adquiridos. El objetivo de este trabajo es doble: 1) Exponer cómo en actividades cotidianas aplicamos conocimientos de gestión de proyectos, aunque muchas veces no somos conscientes de ello. Queremos mostrar a nuestros futuros estudiantes el uso de buenas prácticas de gestión de proyectos tomando como referencia la Guía de los Fundamentos para la Dirección de Proyectos (Guía del PMBOK®) del Project Management Institute (PMI) y aplicándolo a la organización de una barbacoa. Así, el alumnado aprenderá que detrás de cada una de las preguntas que se plantean: ¿dónde lo haremos?, ¿cuántos seremos?, ¿qué llevaremos?, ¿cuándo? y otras tantas preguntas, se esconden buenas prácticas de gestión de proyectos; y 2) Plantear al profesorado, tanto universitario como no universitario, la importancia de ir incorporando en etapas tempranas de la formación de nuestro alumnado conceptos básicos sobre diferentes disciplinas aplicadas de forma amena y motivadora. Nuestros jóvenes saben más de gestión de proyectos de lo que ellos mismos creen y ayudarles a sacar este conocimiento a la luz les ayudará a gestionar un proyecto de forma natural cuando lleguen a la universidad. Para ello expondremos técnicas y herramientas sencillas para que su barbacoa sea un éxito., Organizing excursions or afternoon snacks, putting together a team of the most fashionable online game as well as studying in groups and many other things are common activities among young people. Such activities are framed in a project, since they all have a defined time framework, they have limited resources that need to be managed and they set goals that must be met. However, according to our professional experience in university subjects related to IT projects management, teaching this module is difficult because it is taught in the last courses of their degrees and students may reach this level with bad acquired habits. For this reason, we have set out two objectives to carry out this work: On the one hand, to identify everyday activities where we usually apply project management skills without being aware of it. We aim to show our future students the use of good project management practices, following the Project Management Fundamentals Guide (PMBOK® Guide) of the Project Management Institute (PMI), and how to apply them. In this case, we have taken the organization of a barbecue as an example. Thus, the new university student will learn that questions such as where and when will it take place? how many people will be there? what will we bring? among others, hide good project management practices. Young people know more about project management than they think they know. Therefore, bringing this knowledge to light will help them manage a project, naturally and unconsciously, when they reach university degrees. For this purpose, we will display simple techniques and tools in order to make a barbecue be a successful event. On the other hand, to make teachers, both university and nonuniversity, aware of the importance of incorporating basic concepts related to project management, in an entertaining and motivating way, in the early stages of students’ education.

There is a wide range of enterprise content management (ECM) systems which supports, among other things, document management processes, records management and Web content management. However, each of these systems has many features and some of them can meet organizational needs depending on the scale, sector and workflow of the organization. In addition, it is very common that organizations are unaware of what ECM system best fits their needs, since each company has its particular scope and strategic objectives. This chapter is contextualized within the real project called THOT designed for the Andalusian Public Administration in Spain. The aim of this project is to study in detail ECM systems and propose an objective method to compare them for the specific scope and strategic objective of organizations. Quality evaluation frame‐ work (QuEF) has been adapted for this purpose

Las organizaciones que trabajan en el desarrollo de Sistemas de Infor mación son reacias muchas veces a implantar nuevas metodologías de trabajo sin disponer previamente de ciertas garantías de éxito. Esta reacción es comprensi ble, ya que el éxito o el fracaso de ciertos proyectos puede suponer graves pérdi das económicas o reputacionales para las misma. En este trabajo vamos a presen tar una aplicación práctica del uso de una técnica de juicio de expertos, el método Delphi, para la validación de una propuesta metodológica en el ámbito de la In geniería Web. El uso de estas técnicas puede suponer un buen compromiso en términos de inversión requerida y rápido retorno de la misma, obteniendo un jui cio objetivo sobre una determinada propuesta sin tener que realizar una elevada inversión económica o arriesgar determinados proyectos que pueden ser clave para las organizaciones

Hoy en día los sistemas software son cada vez más complejos y su desarrollo se convierte en un desafío continuo para las empresas de software que deben adaptar su forma de trabajar al entorno cambiante, dinámico y globalizado que las caracteriza. En aras de la fabricación de productos software de calidad, en un tiempo de acceso al mercado adecuado y con un coste competitivo, los procesos de software se han convertido en uno de los activos fundamentales de cualquier empresa del sector de las tecnologías de la información y las comunicaciones (TIC). Son muchos los estándares y modelos de referencia, que la industria del software usa y aplica, que establecen la importancia de tener definidos y documentados los procesos de software, estableciendo qué características o requerimientos deberán cumplir, pero no indican cómo definir esos procesos. La búsqueda de la mejor forma de representar y definir los procesos de software dentro de las organizaciones, para garantizar su uso de forma sistemática e institucionalizada, ha sido objeto de estudio desde hace décadas, mediante la creación de diferentes lenguajes de modelado de procesos de software. Desde los años 90 más de una treintena de lenguajes significativos han sido desarrollados con el objetivo de modelar los procesos de software. Cada uno de estos lenguajes era creado para solventar algún problema existente que no estaba resuelto con los anteriores, pero con el mismo objetivo: obtener los modelos de procesos y sistematizar su uso en las empresas de software. Varias han sido las tendencias sobre las tecnologías base para su modelado, desde la creación de nuevos lenguajes de programación específicos para procesos, pasando por la formalidad de las redes de Petri, hasta los más modernos enfoques basados en modelos de acuerdo con el paradigma de la ingeniería dirigida por modelos (Model Driven Engineering, MDE). Sin embargo, a pesar de todos los esfuerzos por generar un lenguaje de modelado de procesos de software que sobre

Context Agile approaches are an alternative for organizations developing software, particularly for those who develop Web applications. Besides, CMMI (Capability Maturity Model Integration) models are well-established approaches focused on assessing the maturity of an organization that develops software. Web Engineering is the field of Software Engineering responsible for analyzing and studying the specific characteristics of the Web. The suitability of an Agile approach to help organizations reach a certain CMMI maturity level in Web environments will be very interesting, as they will be able to keep the ability to quickly react and adapt to changes as long as their development processes get mature. Objective This paper responds to whether it is feasible or not, for an organization developing Web systems, to achieve a certain maturity level of the CMMI-DEV model using Agile methods. Method The proposal is analyzed by means of a systematic literature review of the relevant approaches in the field, defining a characterization schema in order to compare them to introduce the current state-of-the-art. Results The results achieved after the systematic literature review are presented, analyzed and compared against the defined schema, extracting relevant conclusions for the different dimensions of the problem: compatibility, compliance, experience, maturity and Web. Conclusion It is concluded that although the definition of an Agile approach to meet the different CMMI maturity levels goals could be possible for an organization developing Web systems, there is still a lack of detailed studies and analysis on the field.

CMMI (Capability Maturity Model-Integration) model proposes a set of process areas, including suggested practices, with the aim of helping organizations to improve the quality of their products and processes. It is commonly accepted that as an organization progresses through the different levels of CMMI, the quality of its development might improve as well as the overhead of the development process, impeding it to quickly adapt to customers or partners changing needs. Besides, Agile practices allow quick adaptation and early delivery of business value. The specificity of Web environments makes them suitable for Agile approaches. However, as quality requirements for Web systems increase, a combination of Agile practices allowing organizations to achieve higher levels of CMMI-DEV with a limited process overhead can be very interesting to organizations that aim to keep adaptability. This way, they might strengthen their development processes in order to produce high quality results. This paper presents a gap analysis between the most used Agile practices (Scrum and XP) as well as a mapping proposal, including ad-hoc modifications and other Agile practices, to achieve all CMMI-DEV level 4 and 5 specific goals. To conclude, it drafts relevant conclusions and proposes future lines of research