Traceability for Model Driven, Software Product Line Engineering

Traceability is an important challenge for software organizations. This is true for traditional software development and even more so in new approaches that introduce more variety of artefacts such as Model Driven development or Software Product Lines. In this paper we look at some aspect of the interaction of Traceability, Model Driven development and Software Product Line

Using problem descriptions to represent variabilities for context-aware applications

This paper investigates the potential use of problem descriptions to represent and analyse variability in context-aware software products. By context-aware, we refer to recognition of changes in properties of external domains, which are recognised as affecting the behaviour of products. There are many reasons for changes in the operating environment, from fluctuating resources upon which the product relies, to different operating locations or the presence of objects. There is an increasing expectation for software intensivedevices to be context-aware which, in turn, adds further variability to problem description and analysis. However, we argue in this paper that the capture of contextual variability on current variability representations and analyses has yet to be explored. We illustrate the representation of this type of variability in a pilot study, and conclude with lessons learnt and an agenda for further work

Product line architecture recovery with outlier filtering in software families: the Apo-Games case study

Software product line (SPL) approach has been widely adopted to achieve systematic reuse in families of software products. Despite its benefits, developing an SPL from scratch requires high up-front investment. Because of that, organizations commonly create product variants with opportunistic reuse approaches (e.g., copy-and-paste or clone-and-own). However, maintenance and evolution of a large number of product variants is a challenging task. In this context, a family of products developed opportunistically is a good starting point to adopt SPLs, known as extractive approach for SPL adoption. One of the initial phases of the extractive approach is the recovery and definition of a product line architecture (PLA) based on existing software variants, to support variant derivation and also to allow the customization according to customers’ needs. The problem of defining a PLA from existing system variants is that some variants can become highly unrelated to their predecessors, known as outlier variants. The inclusion of outlier variants in the PLA recovery leads to additional effort and noise in the common structure and complicates architectural decisions. In this work, we present an automatic approach to identify and filter outlier variants during the recovery and definition of PLAs. Our approach identifies the minimum subset of cross-product architectural information for an effective PLA recovery. To evaluate our approach, we focus on real-world variants of the Apo-Games family. We recover a PLA taking as input 34 Apo-Game variants developed by using opportunistic reuse. The results provided evidence that our automatic approach is able to identify and filter outlier variants, allowing to eliminate exclusive packages and classes without removing the whole variant. We consider that the recovered PLA can help domain experts to take informed decisions to support SPL adoption.This research was partially funded by INES 2.0; CNPq grants 465614/2014-0 and 408356/2018-9; and FAPESB grants JCB0060/2016 and BOL2443/201

Methods of representing the structure of complex industrial products on computer files, to facilitate planning, costing and related management tasks : a thesis presented in fulfilment of the requirements for the degree of Master of Technology in Manufacturing and Industrial Technology at Massey University

When the original concepts for the computerisation of product structures were developed in the late 1960's the available computer power was very limited. A modularisation technique was developed to address the situation in which a number of similar products were being manufactured. This technique tried to rationalise these products into family groups. Each member of the family differed from the others due to the possession of different features or options. However there was also a high degree of commonality to give the product membership of the family. Modularisation involved the identification of the options and features providing the variability. Those parts remaining tended to be common to all members of the family and became known as the common parts. Separate Bills of Material (BOMs) were set up for each of the identified options or features. Another BOM was set up for the common parts. The simple combination of the required options and/or features BOMs with the common parts BOM specified a product. Computer storage requirements and redundancy were reduced to a minimum. The Materials Requirements Planning (MRP) system could manipulate these option and feature BOMs to over plan product variability without over planning the parts common to all members. The modularisation philosophy had wide acceptance and is the foundation of MRP training. Modularisation, developed for MRP, is generally parts orientated. An unfortunate side effect tends to be the loss of product structure information. Most commercial software would list 6 resistors, Part No. 123, in the common parts BOM without concern as to where the resistors are fitted. This loss of product structure information can hide the fact that two products using these 6 resistors 'in common' are in fact different as they do not use the resistors in the same 6 places. Additional information must be consulted to enable the correct assembly of the 'common' portion of these products. The electronics industry is especially affected by this situation. This industry has changed considerably since the late 1960's. Product variability can be very high. Changes and enhancements are a constant factor in products having a relatively short life span. The modularisation technique does not have a good mechanism for the situation where an option itself has options or features. This situation can exist down a number of layers of the family tree structure of an electronics product. Maintenance of these BOMs is difficult. Where there are options within options the designers and production staff need to know the inter-relationship of parts between options to ensure accuracy, compatibility and plan assembly functions. The advent of computerised spreadsheets has made the maintenance of this type of product structure information easier. This matrix is another separate document which must be maintained and cross checked. It will inevitably differ from the BOMs periodically. This thesis develops a product structure Relational BOM based on the matrix for the family of products. The processing power of the 1990's computer is fully utilised to derive the common parts for any or all of the selected products of the family. All product structure information is retained and the inter-relationship of parts is highly visible. The physical maintenance of the BOMs is simple. The BOM serves all purposes without the need for supplementary information. It is fully integrated into the Sales Order Entry , MRP, Costing, Engineering Design and Computer Aided Manufacturing (CAM) systems. This technique has been proven by being the only system used in one Electronics Design and Manufacturing organisation for over 1 year without any major problems. As described in Section 1.6 user satisfaction has been high. The response of the users to the suggestion 'lets buy an "off the shelf" package' is very negative, as it would not incorporate this BOM system. Users have expressed the opinion that EXICOM could not continue, with present staffing levels, using the traditional BOM structure

A Systematic Review of Tracing Solutions in Software Product Lines

Software Product Lines are large-scale, multi-unit systems that enable massive, customized production. They consist of a base of reusable artifacts and points of variation that provide the system with flexibility, allowing generating customized products. However, maintaining a system with such complexity and flexibility could be error prone and time consuming. Indeed, any modification (addition, deletion or update) at the level of a product or an artifact would impact other elements. It would therefore be interesting to adopt an efficient and organized traceability solution to maintain the Software Product Line. Still, traceability is not systematically implemented. It is usually set up for specific constraints (e.g. certification requirements), but abandoned in other situations. In order to draw a picture of the actual conditions of traceability solutions in Software Product Lines context, we decided to address a literature review. This review as well as its findings is detailed in the present article.Comment: 22 pages, 9 figures, 7 table

Impact of template backbone heterogeneity on RNA polymerase II transcription.

Variations in the sugar component (ribose or deoxyribose) and the nature of the phosphodiester linkage (3'-5' or 2'-5' orientation) have been a challenge for genetic information transfer from the very beginning of evolution. RNA polymerase II (pol II) governs the transcription of DNA into precursor mRNA in all eukaryotic cells. How pol II recognizes DNA template backbone (phosphodiester linkage and sugar) and whether it tolerates the backbone heterogeneity remain elusive. Such knowledge is not only important for elucidating the chemical basis of transcriptional fidelity but also provides new insights into molecular evolution. In this study, we systematically and quantitatively investigated pol II transcriptional behaviors through different template backbone variants. We revealed that pol II can well tolerate and bypass sugar heterogeneity sites at the template but stalls at phosphodiester linkage heterogeneity sites. The distinct impacts of these two backbone components on pol II transcription reveal the molecular basis of template recognition during pol II transcription and provide the evolutionary insight from the RNA world to the contemporary 'imperfect' DNA world. In addition, our results also reveal the transcriptional consequences from ribose-containing genomic DNA