Applying product line Use case modeling in an industrial automotive embedded system: Lessons learned and a refined approach

Hajri, Ines; Göknil, Arda; Briand, Lionel C.; Stephany, Thierry

doi:10.1109/models.2015.7338265

Cited by 20 publications

(34 citation statements)

References 24 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…We addressed the first challenge in our previous work [44] with the Product line Use case modeling Method (PUM). In the remainder of this paper, we focus on how to best address the second challenge in a practical manner, in the context of use case-driven development, while relying on PUM to minimize the modeling overhead.…”

Section: Sensorsmentioning

confidence: 99%

“…This activity is based on the Product line Use case modeling Method (PUM) which we present in our previous paper [44]. The artifacts of PUM is a PL use case diagram using product line extensions proposed by Halmans and Pohl [45,23], PL use case specifications using RUCM extensions which we propose, and a PL domain model using stereotypes provided by Ziadi and Jezequel [82].…”

Section: Elicitation Of Variability In Use Casesmentioning

confidence: 99%

“…Therefore, in our previous work [44], which this paper extends, we proposed and assessed the Product line Use case modeling Method (PUM), which enables the analysts to capture and document variability in PL use case diagrams, use case specifications, and domain models. For PL use case diagrams, we employ the diagram extensions proposed by Halmans and Pohl [45].…”

Section: Introductionmentioning

confidence: 99%

“…RUCM was a clear choice since it reduces ambiguity and facilitates automated analysis of use cases [78,80,73,74]. However, since it was not originally meant to model variability, we introduced some PL extensions to capture variability in use case specifications [44]. To be able to capture variability in PL domain models, we rely on the stereotypes (i.e., variation, variant and optional), proposed by Ziadi and Jezequel [82] for UML class diagrams.…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Configuring use case models in product families

et al. 2016

Self Cite

View full text Add to dashboard Cite

In many domains such as automotive and avionics, the size and complexity of software systems is quickly increasing. At the same time, many stakeholders tend to be involved in the development of such systems, which typically must also be configured for multiple customers with varying needs. Product Line Engineering (PLE) is therefore an inevitable practice for such systems. Furthermore, because in many areas requirements must be explicit and traceability to them is required by standards, use cases and domain models are common practice for requirements elicitation and analysis. In this paper, based on the above observations, we aim at supporting PLE in the context of use casecentric development. Therefore, we propose, apply, and assess a use case-driven configuration approach which interactively receives configuration decisions from the analysts to generate Product Specific (PS) use case and domain models. Our approach provides the following: (1) a use case-centric product line modeling method (PUM), (2) automated, interactive configuration support based on PUM, and (3) an automatic generation of PS use case and domain models from Product Line (PL) models and configuration decisions. The approach is supported by a tool relying on Natural Language Processing (NLP), and integrated with an industrial requirements management tool, i.e., IBM Doors. We successfully applied and evaluated our approach to an industrial case study in the automotive domain, thus showing evidence that the approach is practical and beneficial to capture variability at the appropriate level of granularity and to configure PS use case and domain models in industrial settings.

show abstract

Section: Sensorsmentioning

confidence: 99%

Section: Elicitation Of Variability In Use Casesmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Configuring use case models in product families

et al. 2016

Self Cite

View full text Add to dashboard Cite

show abstract

“…PUMConf builds on our previous work [9] where we proposed a use case-centric product line modeling method (PUM). Using PUM, variability is directly captured in the PL use case diagram, specifications and domain model without any feature model, at a level of granularity enabling precise communication with various stakeholders.…”

Section: Introductionmentioning

confidence: 99%

PUMConf: a tool to configure product specific use case and domain models in a product line

Hajri

Göknil

Briand

et al. 2016

Proceedings of the 2016 24th ACM SIGSOFT International Symposium on Foundations of Software Engineering

Self Cite

View full text Add to dashboard Cite

We present PUMConf, a tool for supporting configuration that currently focuses on requirements and enables effective product line management in the context of use case-driven development. By design, it relies exclusively on variability modeling for artifacts that are commonly used in such contexts (i.e., use case diagram, specifications and domain model). For given Product Line (PL) use case and domain models, PUMConf checks the consistency of the models, interactively receives configuration decisions from analysts, automatically checks decision consistency, and generates Product Specific (PS) use case and domain models from the PL models and decisions. It has been evaluated on an industrial case study in the automotive domain.

show abstract

An Effective Verification Strategy for Testing Distributed Automotive Embedded Software Functions: A Case Study

Chunduri

Feldt

Adenmark

2016

Product-Focused Software Process Improvement

View full text Add to dashboard Cite

Context. The share and importance of software within automotive vehicles is growing steadily. Most functionalities in modern vehicles, especially safety related functions like advanced emergency braking, are controlled by software. A complex and common phenomenon in today's automotive vehicles is the distribution of such software functions across several Electronic Control Units (ECUs) and consequently across several ECU system software modules. As a result, integration testing of these distributed software functions has been found to be a challenge. The automotive industry neither has infinite resources, nor has the time to carry out exhaustive testing of these functions. On the other hand, the traditional approach of implementing an ad-hoc selection of test scenarios based on the tester's experience, can lead to test gaps and test redundancies. Hence, there is a pressing need within the automotive industry for a feasible and effective verification strategy for testing distributed software functions. Objectives. Firstly, to identify the current approach used to test the distributed automotive embedded software functions in literature and in a case company. Secondly, propose and validate a feasible and effective verification strategy for testing the distributed software functions that would help improve test coverage while reducing test redundancies and test gaps. Methods. To accomplish the objectives, a case study was conducted at Scania CV AB, Södertälje, Sweden. One of the data collection methods was through conducting interviews of different employees involved in the software testing activities. Based on the research objectives, an interview questionnaire with open-ended and close-ended questions has been used. Apart from interviews, data from relevant artifacts in databases and archived documents has been used to achieve data triangulation. Moreover, to further strengthen the validity of the results obtained, adequate literature support has been presented throughout. Towards the end, a verification strategy has been proposed and validated using existing historical data at Scania. Conclusions. The proposed verification strategy to test distributed automotive embedded software functions has given promising results by providing means to identify test gaps and test redundancies. It helps establish an effective and feasible approach to capture function test coverage information that helps enhance the effectiveness of integration testing of the distributed software functions.

show abstract

Applying product line Use case modeling in an industrial automotive embedded system: Lessons learned and a refined approach

Cited by 20 publications

References 24 publications

Configuring use case models in product families

Configuring use case models in product families

PUMConf: a tool to configure product specific use case and domain models in a product line

An Effective Verification Strategy for Testing Distributed Automotive Embedded Software Functions: A Case Study

Contact Info

Product

Resources

About