Introduction to the SPES Modeling Framework

Broy, Manfred; Damm, Werner; Henkler, Stefan; Pohl, Klaus; Vogelsang, Andreas; Weyer, Thorsten

doi:10.1007/978-3-642-34614-9_3

Cited by 13 publications

(11 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The set of all components and their connections form a component architecture of the entire system (cf. [26]). The vehicle features crosscut this architecture by the set of components that contribute to their realization (see Figure 1).…”

Section: Features and Component Architectures In The Automotive Domainmentioning

confidence: 99%

Feature dependencies in automotive software systems: Extent, awareness, and refactoring

Vogelsang

2020

Journal of Systems and Software

Self Cite

View full text Add to dashboard Cite

Many automotive companies consider their software development process to be feature-oriented. In the past, features were regarded as isolated system parts developed and tested by developers from different departments. However, in modern vehicles, features are more and more connected and their behavior depends on each other in many situations. In this article, we describe how feature-oriented software development is conducted in automotive companies and which challenges arise from that. We present an empirical analysis of feature dependencies in three real-world automotive systems. The analysis shows that features in modern vehicles are highly interdependent. Furthermore, the study reveals that developers are not aware of these dependencies in most cases. For the three examined cases, we show that less than 12% of the components in the system architecture are responsible for more than 90% of the feature dependencies. Finally, we propose a refactoring approach for implicit communal components, which makes them explicit by moving them to a dedicated platform component layer.

show abstract

Section: Features and Component Architectures In The Automotive Domainmentioning

confidence: 99%

Feature dependencies in automotive software systems: Extent, awareness, and refactoring

Vogelsang

2020

Journal of Systems and Software

Self Cite

View full text Add to dashboard Cite

show abstract

“…Der separate Anforderungsraum verdeutlicht hierbei, dass Anforderungen über den gesamten Entwicklungsprozess eingesteuert, erweitert, gepflegt und überprüft werden müssen [16]. In weiteren Ansätze wie dem RFLP-Ansatz [17,18], dem SPES Modeling Framework [19] und der aktualisierten VDI 2221 [21] werden mit variierender Terminologie vier Sichtweisen (SPES) oder Ebenen (RFLP) der Systemmodellierung unterschieden: Anforderungsebene, Funktionsebene, Logische Ebene und Physikalische/ Technische Ebene. Auf der Anforderungsebene erfolgt die Definition und Entwicklung der Produktanforderungen um die erforderlichen Produkteigenschaften festzulegen und um den geforderten Verwendungszweck zu erfüllen [18,19].…”

Section: Bestehende Ansätze Zur Strukturierung Von Modellen In Der Systementwicklungunclassified

Herausforderungen und Anforderungen bei der durchgängigen Architekturmodellierung mechatronischer Systeme

Schumacher¹,

Inkermann²

2020

Proceedings of the 31st Symposium Design for X (DFX2020)

View full text Add to dashboard Cite

Architectural models serve to generate a cross-domain understanding of system behaviour and relationships between subsystems within the development process. Various architectural models are described in literature and used in practice, differing in the level of concretion as well as the modelling purpose and representation. In order to structure these architectural models, a framework is derived from established and modern development models. The analysis of the architectural models using the model morphology indicates that architectural models have a large diversity and are often domain-specific. Consequently, the need of cross-domain architecture models are derived. Based on the analysis result and specific use cases requirements for cross-domain architecture modelling are defined.

show abstract

“…However, few model-driven approaches explicitly include RE [65]. Several proposed modeling frameworks prescribe or encourage the use of models for RE [13,78], fewer have been evaluated with practitioners, e.g., [12,14]. However, the industrial uptake seems to be limited, also because important practitioners' needs are not addressed [36].…”

Section: Model-based Re In Context Of Related Workmentioning

confidence: 99%

The impact of requirements on systems development speed: a multiple-case study in automotive

et al. 2019

View full text Add to dashboard Cite

Automotive manufacturers have historically adopted rigid requirements engineering processes. This allowed them to meet safety-critical requirements when producing a highly complex and differentiated product out of the integration of thousands of physical and software components. Nowadays, few software-related domains are as rapidly changing as the automotive industry. In particular, the needs of improving development speed are increasingly pushing companies in this domain toward new ways of developing software. In this paper, we investigate how the goal to increase development speed impacts how requirements are managed in the automotive domain. We start from a manager perspective, which we then complement with a more general perspective. We used a qualitative multiple-case study, organized in two steps. In the first step, we had 20 semi-structured interviews, at two automotive manufacturers. Our sampling strategy focuses on manager roles, complemented with technical specialists. In the second step, we validated our results with 12 more interviews, covering nine additional respondents and three recurring from the first step. In addition to validating our qualitative model, the second step of interviews broadens our perspective with technical experts and change managers. Our respondents indicate and rank six aspects of the current requirements engineering approach that impact development speed. These aspects include the negative impact of a requirements style dominated by safety concerns as well as decomposition of requirements over many levels of abstraction. Furthermore, the use of requirements as part of legal contracts with suppliers is seen as hindering fast collaboration. Six additional suggestions for potential improvements include domain-specific tooling, model-based requirements, test automation, and a combination of lightweight upfront requirements engineering preceding development with precise specifications post-development. Out of these 12 aspects, seven can likely be addressed as part of an ongoing agile transformation. We offer an empirical account of expectations and needs for new requirements engineering approaches in the automotive domain, necessary to coordinate hundreds of collaborating organizations developing software-intensive and potentially safety-critical systems.

show abstract

Introduction to the SPES Modeling Framework

Cited by 13 publications

References 4 publications

Feature dependencies in automotive software systems: Extent, awareness, and refactoring

Feature dependencies in automotive software systems: Extent, awareness, and refactoring

Herausforderungen und Anforderungen bei der durchgängigen Architekturmodellierung mechatronischer Systeme

The impact of requirements on systems development speed: a multiple-case study in automotive

Contact Info

Product

Resources

About