Experiences with product line development of embedded systems at Testo AG

Kolb, Ronny; John, Isabel; Knodel, Jens; Muthig, Dirk; Haury, U.; Meier, G.

doi:10.1109/spline.2006.1691589

Cited by 17 publications

(14 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…While Knodel et al [52] and Kolb et al [19] report that violations were addressed in their case study, Rosik et al [20] found that they were not. Other studies have reported that only academic researchers removed identified violations [15,21].…”

Section: Discussionmentioning

confidence: 96%

“…Kolb et al [19] and Knodel et al [52] also report on experiences using SAVE with an industrial partner. In this instance, conformance checking was adopted by the company involved as a standard instrument for ensuring higher quality products at the organisation.…”

Section: Empirical Assessment Of Rm Approachesmentioning

confidence: 99%

“…Specifically, software architects have shown great enthusiasm for the information which it provides [13,19] and have even proactively sought such analysis again [20]. However, most of these studies focus on the ability of RM to identify inconsistencies [21][22] but do not concentrate on how the capabilities and insights provided by RM approaches are utilized by software practitioners and if the violations are subsequently removed.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Real-Time Reflexion Modelling in architecture reconciliation: A multi case study

Buckley

Alí

English

et al. 2015

Information and Software Technology

View full text Add to dashboard Cite

ContextReflexion Modelling is considered one of the more successful approaches to architecture reconciliation. Empirical studies strongly suggest that professional developers involved in real-life industrial projects find the information provided by variants of this approach useful and insightful, but the degree to which it resolves architecture conformance issues is still unclear. ObjectiveThis paper aims to assess the level of architecture conformance achieved by professional architects using Reflexion Modelling, and to determine how the approach could be extended to improve its suitability for this task. MethodAn in-vivo, multi-case-study protocol was adopted across five software systems, from four different financial services organizations. Think-aloud, video-tape and interview data from professional architects involved in Reflexion Modelling sessions were analysed qualitatively. ResultsThis study showed that (at least) four months after the Reflexion Modelling sessions less than 50% of the architectural violations identified were removed. The majority of participants who did remove violations favoured changes to the architectural model rather than to the code. Participants seemed to work off two specific architectural templates, and interactively explored their architectural model to focus in on the causes of violations, and to assess the ramifications of potential code changes. They expressed a desire for dependency analysis beyond static-source-code analysis and scalable visualizations. ConclusionThe findings support several interesting usage-in-practice traits, previously hinted at in the literature. These include 1) the iterative analysis of systems through Reflexion models, as a precursor to possible code change or as a focusing mechanism to identify the location of architecture conformance issues, 2) the extension of the approach with respect to dependency analysis of software systems and architectural modelling templates, 3) improved visualization support and 4) the insight that identification of architectural violations in itself does not lead to their removal in the majority of instances.

show abstract

Section: Discussionmentioning

confidence: 96%

Section: Empirical Assessment Of Rm Approachesmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Real-Time Reflexion Modelling in architecture reconciliation: A multi case study

Buckley

Alí

English

et al. 2015

Information and Software Technology

View full text Add to dashboard Cite

show abstract

“…Their products are developed as an SPL since 2001, as described in [15]. The basis of their SPL is a product-independent framework, with an additional framework layer for each product family.…”

Section: Testo Agmentioning

confidence: 99%

Supporting the Grow-and-Prune Model in Software Product Lines Evolution Using Clone Detection

Mende¹,

Beckwermert²,

Koschke³

et al. 2008

2008 12th European Conference on Software Maintenance and Reengineering

View full text Add to dashboard Cite

Software Product Lines (SPL) can be used to create and maintain different variants of software-intensive systems by explicitly managing variability. Often, SPLs are organized as an SPL core, common to all products, upon which product-specific components are built. Following the so called grow-and-prune model, SPLs may be evolved by copy&paste at large scale. New products are created from existing ones and existing products are enhanced with functionalities specific to other products by copying and pasting code between product-specific code. To regain control of this unmanaged growth, such code may be pruned, that is, identified and refactored into core components upon success. This paper describes tool support for the grow-andprune model in the evolution of software product lines by identifying similar functions which can be moved to the core. These functions are identified in two steps. First, token-based clone detection is used to detect pairs of functions sharing code. Second, Levenshtein distance measures the textual similarity among these functions. Sufficient similarity at function level is then lifted to the architectural level.The approach is evaluated by three case studies, one using an open source email client to simulate the initial creation of an SPL, and two monitoring existing industrial product lines from the embedded domain.

show abstract

“…The embedded systems domain is frequently subject for variability and safety assessment issues [2,9,12]. From an industrial perspective, some papers report on their experience in managing safety in a product line context [3,13].…”

Section: Related Workmentioning

confidence: 99%

Tooling support for variability and architectural patterns in systems engineering

Degueule

Filho

Barais

et al. 2015

Proceedings of the 19th International Conference on Software Product Line

View full text Add to dashboard Cite

In systems engineering, the deployment of software components is error-prone since numerous safety and security rules have to be preserved. Furthermore, many deployments on different heterogeneous platforms are possible. In this paper we present a technological solution to assist industrial practitioners in producing a safe and secure solution out of numerous architectural variants. First, we introduce a pattern technology that provides correct-by-construction deployment models through the reuse of modeling artifacts organized in a catalog. Second, we develop a variability solution, connected to the pattern technology and based on an extension of the common variability language, for supporting the synthesis of model-based architectural variants. This paper describes a live demonstration of an industrial effort seeking to bridge the gap between variability modeling and model-based systems engineering practices. We illustrate the tooling support with an industrial case study (a secure radio platform).

show abstract

Experiences with product line development of embedded systems at Testo AG

Cited by 17 publications

References 10 publications

Real-Time Reflexion Modelling in architecture reconciliation: A multi case study

Real-Time Reflexion Modelling in architecture reconciliation: A multi case study

Supporting the Grow-and-Prune Model in Software Product Lines Evolution Using Clone Detection

Tooling support for variability and architectural patterns in systems engineering

Contact Info

Product

Resources

About