Semi-automatic establishment and maintenance of valid traceability in automotive development processes

Fockel, Markus; Holtmann, Jörg; Meyer, Jörg

doi:10.1109/sees.2012.6225489

Cited by 10 publications

(5 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The logical (Fockel et al, 2012) and physical architecture results described above are compatible with the system description results of AUTOSAR development methodology described in Figure 17 of section 2.3.…”

Section: Example Of Logical Architecture and Physical Architecturesupporting

confidence: 77%

“…In our approach, the activities corresponding to the SEBOK functional decomposition architecture are not considered as logical blocks, rather these are potentially decomposable activities of SysML activity diagrams (refer to Figure 24). The logical (Fockel et al, 2012) and physical architectural blocks and interfaces in the last layer can be thought of as a description of AUTOSAR SWCs and AUTOSAR SWC interfaces, respectively.…”

Section: Layered Model Managementmentioning

confidence: 99%

See 1 more Smart Citation

A generic hierarchical System of Systems Engineering (SOS) Approach for Model based System Engineering (MBSE) Projects

Pandey¹

2022

INCOSE International Symp

View full text Add to dashboard Cite

Model based systems engineering (MBSE) has been accepted worldwide by many industries, including the automotive industry, for several years. Hundreds of projects have already been developed and deployed using MBSE approaches. MBSE is gaining importance because it provides systems advantageous life cycle processes, such as returns of investments and meeting the demands of global marketplaces, as they become increasingly complex. Consequently, the number and pace of deployment using MBSE approaches will increase in the future.Our current work objective is to define a generic MBSE methodology compatible with Systems Engineering Body of Knowledge (SEBOK) functional decomposition principles, 'Automotive open systems architecture' (AUTOSAR) developments and compliant to 'Automotive software performance improvement and capability determination' (ASPICE) processes using the 'systems modelling language' (SysML). We have proposed a generic SysML process framework, a hierarchical system of systems (SOS) engineering approach and automation solutions. We have shown that the proposed solution helps meet the defined objectives. The work is targeted and relevant for automotive industry MBSE practitioners. In general, the research, apart from transportation and mobility industries, can also be used in other industries.

show abstract

Section: Example Of Logical Architecture and Physical Architecturesupporting

confidence: 77%

Section: Layered Model Managementmentioning

confidence: 99%

A generic hierarchical System of Systems Engineering (SOS) Approach for Model based System Engineering (MBSE) Projects

Pandey¹

2022

INCOSE International Symp

View full text Add to dashboard Cite

show abstract

“…1 In recent years, studies have been conducted in various contexts of software traceability, such as traceability approaches, 16 traceability deployment, and maintenance of traceability links. 17,18 2.2 | Software maintenance and evolution Software maintenance and evolution is a critical software development phase. The IEEE Standard 1219 19 defines software maintenance as "the modification of a software product after delivery to correct faults, to improve performance or other attributes, or to adapt the product to a modified environment".…”

Section: Software Traceabilitymentioning

confidence: 99%

The impact of traceability on software maintenance and evolution: A mapping study

Tian

Wang

Liang

et al. 2021

J Software Evolu Process

View full text Add to dashboard Cite

show abstract

“…Holtmann et al proposed a CNL, which describes the requirements of embedded software in automobile areas. CNL can reduce the ambiguity of natural language; it can also detect inconsistency and incompleteness of requirements, as well as support the automate verification of requirements [48], [49]. CNL is mainly used to describe system requirements of automotive systems.…”

Section: A Requirement Specifications In Restricted Natural Languagementioning

confidence: 99%

An Approach to Generate the Traceability Between Restricted Natural Language Requirements and AADL Models

Wang¹,

Yang²,

Huang³

et al. 2020

IEEE Trans. Rel.

View full text Add to dashboard Cite

Requirements traceability is broadly recognized as a critical element of any rigorous software development process, especially for building safety-critical software (SCS) systems. Modeldriven development (MDD) is increasingly used to develop SCS in many domains, such as automotive and aerospace. MDD provides new opportunities for establishing traceability links through modeling and model transformations. Architecture Analysis and Design Language (AADL) is a standardized architecture description language for embedded systems, which is widely used in avionics and aerospace industries to model safety-critical applications. However, there is a big challenge to automatically establish the traceability links between requirements and AADL models in the context of MDD, because requirements are mostly written as free natural language texts, which are often ambiguous and difficult to be processed automatically. To bridge the gap between natural language requirements (NLRs) and AADL models, we propose an approach to generate the traceability links between NLRs and AADL models. First, we propose a requirement modeling method based on the restricted natural language, which is named as RM-RNL. The RM-RNL can eliminate the ambiguity of NLRs and barely change engineers' habits of requirement specification. Second, we present a method to automatically generate the initial AADL models from the RM-RNLs and to automatically establish traceability links between the elements of the RM-RNL and the generated AADL models. Third, we refine the initial AADL models through patterns to achieve the change of requirements and traceability links. Finally, we demonstrate the effectiveness of our approach with industrial case studies and evaluation experiments.

show abstract

Semi-automatic establishment and maintenance of valid traceability in automotive development processes

Cited by 10 publications

References 7 publications

A generic hierarchical System of Systems Engineering (SOS) Approach for Model based System Engineering (MBSE) Projects

A generic hierarchical System of Systems Engineering (SOS) Approach for Model based System Engineering (MBSE) Projects

The impact of traceability on software maintenance and evolution: A mapping study

An Approach to Generate the Traceability Between Restricted Natural Language Requirements and AADL Models

Contact Info

Product

Resources

About