Applying System Families Concepts to Requirements Engineering Process Definition

In this paper, some experiences gained during the definition of a unified, common software development process for several companies in Telvent are presented. Last year, Telvent made the decision of developing a unique software development process which was flexible enough to be adapted to specific practices and needs of the different companies. In this paper we focus mainly on the experiences gained during the definition of the requirements engineering process, al-though many of them are also applicable to other software development processes. One of the most interesting experiences from our point of view is that, al-though the definition process was started using a top-down approach and well-know techniques like data flow diagrams, we eventually end up applying requirements engineering techniques like glossaries, scenarios or conflict resolu-tion for the definition of the requirements engineering process itself. On the other hand, the need of having adaptable processes for the different companies in Tel-vent made us adopt a process family approach, i.e. adopting an approach similar to the system families development, thus defining a core process that could be adapted to specific needs of specific companies in a predefined, controlled man-ner. The experiences gained in the definition of the process family were applied to the definition of requirements engineering process for product line development, which is briefly presented in this paper.Comisión Interministerial de Ciencia y Tecnología TIC 2000–1106–C02–01Ministerio de Energía, Turismo y Agenda Digital ITEA ip00004Ministerio de Economía y Competitividad Eureka Σ! 202

Developing modular product family using GeMoCURE within an SME

Companies adopt the strategy of producing variety of products to be competitive and responsive to market. Product variation is becoming an important factor in companies' ability to accurately meet customer requirements. Ever increasing consumer options mean that customers have more choices than ever before which put commercial pressures on companies to continue to diversify. This can be a particular problem within Small to Medium Enterprises (SMEs) who do not always have the level of resources to meet these requirements. As such, methods are required that provide means for companies to be able to produce a wide range of products at the lowest cost and shortest time. This paper details a new modular product design methodology that provides a focus on developing modular product families. The methodology's function is described and a case study detailed of how it was used within an SME to define the company's product portfolio and create a new Generic Product Function Structure from which a new family of product variants can be developed. The methodology lends itself to modular re-use which has the potential to support rapid development and configuration of product variants

Shape exploration in design : formalising and supporting a transformational process

The process of sketching can support the sort of transformational thinking that is seen as essential for the interpretation and reinterpretation of ideas in innovative design. Such transformational thinking, however, is not yet well supported by computer-aided design systems. In this paper, outcomes of experimental investigations into the mechanics of sketching are described, in particular those employed by practising architects and industrial designers as they responded to a series of conceptual design tasks,. Analyses of the experimental data suggest that the interactions of designers with their sketches can be formalised according to a finite number of generalised shape rules. A set of shape rules, formalising the reinterpretation and transformations of shapes, e.g. through deformation or restructuring, are presented. These rules are suggestive of the manipulations that need to be afforded in computational tools intended to support designers in design exploration. Accordingly, the results of the experimental investigations informed the development of a prototype shape synthesis system, and a discussion is presented in which the future requirements of such systems are explored

Applying model-driven paradigm: CALIPSOneo experience

Model-Driven Engineering paradigm is being used by the research community in the last years, obtaining suitable results. However, there are few practical experiences in the enterprise field. This paper presents the use of this paradigm in an aeronautical PLM project named CALIPSOneo currently under development in Airbus. In this context, NDT methodology was adapted as methodology in order to be used by the development team. The paper presents this process and the results that we are getting from the project. Besides, some relevant learned lessons from the trenches are concluded.Ministerio de Ciencia e Innovación TIN2010-20057-C03-02Junta de Andalucía TIC-578

Composition and Self-Adaptation of Service-Based Systems with Feature Models

The adoption of mechanisms for reusing software in pervasive systems has not yet become standard practice. This is because the use of pre-existing software requires the selection, composition and adaptation of prefabricated software parts, as well as the management of some complex problems such as guaranteeing high levels of efficiency and safety in critical domains. In addition to the wide variety of services, pervasive systems are composed of many networked heterogeneous devices with embedded software. In this work, we promote the safe reuse of services in service-based systems using two complementary technologies, Service-Oriented Architecture and Software Product Lines. In order to do this, we extend both the service discovery and composition processes defined in the DAMASCo framework, which currently does not deal with the service variability that constitutes pervasive systems. We use feature models to represent the variability and to self-adapt the services during the composition in a safe way taking context changes into consideration. We illustrate our proposal with a case study related to the driving domain of an Intelligent Transportation System, handling the context information of the environment.Work partially supported by the projects TIN2008-05932, TIN2008-01942, TIN2012-35669, TIN2012-34840 and CSD2007-0004 funded by Spanish Ministry of Economy and Competitiveness and FEDER; P09-TIC-05231 and P11-TIC-7659 funded by Andalusian Government; and FP7-317731 funded by EU. Universidad de Málaga. Campus de Excelencia Internacional Andalucía Tec

A Product Line Systems Engineering Process for Variability Identification and Reduction

Software Product Line Engineering has attracted attention in the last two decades due to its promising capabilities to reduce costs and time to market through reuse of requirements and components. In practice, developing system level product lines in a large-scale company is not an easy task as there may be thousands of variants and multiple disciplines involved. The manual reuse of legacy system models at domain engineering to build reusable system libraries and configurations of variants to derive target products can be infeasible. To tackle this challenge, a Product Line Systems Engineering process is proposed. Specifically, the process extends research in the System Orthogonal Variability Model to support hierarchical variability modeling with formal definitions; utilizes Systems Engineering concepts and legacy system models to build the hierarchy for the variability model and to identify essential relations between variants; and finally, analyzes the identified relations to reduce the number of variation points. The process, which is automated by computational algorithms, is demonstrated through an illustrative example on generalized Rolls-Royce aircraft engine control systems. To evaluate the effectiveness of the process in the reduction of variation points, it is further applied to case studies in different engineering domains at different levels of complexity. Subject to system model availability, reduction of 14% to 40% in the number of variation points are demonstrated in the case studies.Comment: 12 pages, 6 figures, 2 tables; submitted to the IEEE Systems Journal on 3rd June 201