A Traceability-based Method to Support Conceptual Model Evolution

Renewing software systems is one of the most cost-effective ways to protect software investment, which saves time, money and ensures uninter- rupted access to technical support and product upgrades. There are several mo- tivations to promote investment and scientific effort for specifying systems by means of conceptual models and supporting its evolution. As an example, the software engineering community is addressing solutions for supporting model traceability, continuous improvement of business process, organisational reen- gineering, information system maintenance, etc. Model-driven techniques have been developed in order to analyse systems raising the abstraction level of its specification. However, a support for conceptual model evolution by means of model-driven techniques is still needed. This thesis proposes a traceability- based method that involves model-driven capabilities for designing and provid- ing guidelines, techniques, and tools to support conceptual model evolution. The main idea is to support information system analysts in the tasks related to: justify why the conceptual models have evolved, report and specify what ele- ments have evolved, and guide how to carry out evolution in certain predefined organisational contexts. We plan to apply our method to guide the evolution of an E-shopping software. This way, we also provide mechanism to facilitate in- dustrial adoption.This PhD project has been supported by the Spanish Generalitat Valenciana ORCA (PROMETEO/2009/015); the FPI grant of the Universitat Politècnica de València (3146); the European Commission FP7 Project CaaS (611351); and the ERDF structural funds.Ruiz Carmona, LM. (2014). A Traceability-based Method to Support Conceptual Model Evolution. CEUR Workshop Proceedings. http://hdl.handle.net/10251/73841

A Practical Environment to Apply Model-Driven Web Engineering

The application of a model-driven paradigm in the development of Web Systems has yielded very good research results. Several research groups are defining metamodels, transformations, and tools which offer a suitable environment, known as model-driven Web engineering (MDWE). However, there are very few practical experiences in real Web system developments using real development teams. This chapter presents a practical environment of MDWE based on the use of NDT (navigational development techniques) and Java Web systems, and it provides a practical evaluation of its application within a real project: specialized Diraya.Ministerio de Educación y Ciencia TIN2007-67843-C06-03Ministerio de Educación y Ciencia TIN2007-30391-

A design recording framework to facilitate knowledge sharing in collaborative software engineering

This paper describes an environment that allows a development team to share knowledge about software artefacts by recording decisions and rationales as well as supporting the team in formulating and maintaining design constraints. It explores the use of multi-dimensional design spaces for capturing various issues arising during development and presenting this meta-information using a network of views. It describes a framework to underlie the collaborative environment and shows the supporting architecture and its implementation. It addresses how the artefacts and their meta-information are captured in a non-invasive way and shows how an artefact repository is embedded to store and manage the artefacts

Adaptive development and maintenance of user-centric software systems

A software system cannot be developed without considering the various facets of its environment. Stakeholders – including the users that play a central role – have their needs, expectations, and perceptions of a system. Organisational and technical aspects of the environment are constantly changing. The ability to adapt a software system and its requirements to its environment throughout its full lifecycle is of paramount importance in a constantly changing environment. The continuous involvement of users is as important as the constant evaluation of the system and the observation of evolving environments. We present a methodology for adaptive software systems development and maintenance. We draw upon a diverse range of accepted methods including participatory design, software architecture, and evolutionary design. Our focus is on user-centred software systems

Crosscutting, what is and what is not? A Formal definition based on a Crosscutting Pattern

Crosscutting is usually described in terms of scattering and tangling. However, the distinction between these concepts is vague, which could lead to ambiguous statements. Sometimes, precise definitions are required, e.g. for the formal identification of crosscutting concerns. We propose a conceptual framework for formalizing these concepts based on a crosscutting pattern that shows the mapping between elements at two levels, e.g. concerns and representations of concerns. The definitions of the concepts are formalized in terms of linear algebra, and visualized with matrices and matrix operations. In this way, crosscutting can be clearly distinguished from scattering and tangling. Using linear algebra, we demonstrate that our definition generalizes other definitions of crosscutting as described by Masuhara & Kiczales [21] and Tonella and Ceccato [28]. The framework can be applied across several refinement levels assuring traceability of crosscutting concerns. Usability of the framework is illustrated by means of applying it to several areas such as change impact analysis, identification of crosscutting at early phases of software development and in the area of model driven software development

Economic Evaluation of Food Traceability Systems through Reference Models

Food supply chains complexity present a real challenge to perform economic evaluation of food traceability systems and their innovation/upgrades. In order to perform a supply chain wide economic evaluation a conceptual framework is developed using food traceability reference models. Reference models allow interaction with chain members’ requirements that come from legal and/or customer sources. The paper demonstrates how the requirements will have a definite effect on the costs and design of food traceability systems through the resources they demand. Even though this is a first step into addressing the challenge, more investigation is needed to clarify the boundaries of the two requirements and their economic effects on food traceability systems and their innovations/upgrades.Food traceability, Food traceability systems, Reference models, Economic evaluation., Agribusiness, Agricultural and Food Policy, Farm Management, Food Consumption/Nutrition/Food Safety, Industrial Organization,

<i>Trace++</i>: A Traceability Approach for Agile Software Engineering

Agile methodologies have been introduced as an alternative to traditional software engineering methodologies. However, despite the advantages of using agile methodologies, the transition between traditional and agile methodologies is not an easy task. There are several problems associated with the use of agile methodologies. Examples of these problems are related to (i) lack of metrics to measure the amount of rework that occurs per sprint, (ii) interruption of a project after several iterations, (iii) changes in the requirements, (iv) lack of documentation, and (v) lack of management control. In this paper we present Trace++, a traceability technique that extends traditional traceability relationships with extra information in order to support the transition between traditional and agile software development. The use of Trace++ has been evaluated in two real projects of different software development companies to measure the benefits of using Trace++ to support agile software development

Semantics of trace relations in requirements models for consistency checking and inferencing

Requirements traceability is the ability to relate requirements back to stakeholders and forward to corresponding design artifacts, code, and test cases. Although considerable research has been devoted to relating requirements in both forward and backward directions, less attention has been paid to relating requirements with other requirements. Relations between requirements influence a number of activities during software development such as consistency checking and change management. In most approaches and tools, there is a lack of precise definition of requirements relations. In this respect, deficient results may be produced. In this paper, we aim at formal definitions of the relation types in order to enable reasoning about requirements relations. We give a requirements metamodel with commonly used relation types. The semantics of the relations is provided with a formalization in first-order logic. We use the formalization for consistency checking of relations and for inferring new relations. A tool has been built to support both reasoning activities. We illustrate our approach in an example which shows that the formal semantics of relation types enables new relations to be inferred and contradicting relations in requirements documents to be determined. The application of requirements reasoning based on formal semantics resolves many of the deficiencies observed in other approaches. Our tool supports better understanding of dependencies between requirements