V-Models for Interdisciplinary Systems Engineering

Graessler, Iris; Hentze, Julian; Brückmann, Tobias

doi:10.21278/idc.2018.0333

Cited by 51 publications

(33 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Trends like digitalization and increasing complexity lead to changes in the working environment, engineering approaches and required competencies (Gräßler et al, 2018b;Gräßler et al, 2018a;Boston Consulting Group, 2015;BMWi, 2015). This demands for more Systems Engineering application, but also affects the approach of how to apply the methodology of Systems Engineering to industrial projects.…”

Section: Motivationmentioning

confidence: 99%

“…This role is based on the following references: (INCOSE UK, 2010;BKCASE Editorial Board, 2017;NASA, 2009;INCOSE, 2018;Sheard, 1996;Gräßler et al, 2018a;VDI, 2004). Basis for the role…”

Section: System Architectmentioning

confidence: 99%

“…The System Architect is involved in high-level design decision, but does not extensively perform detailed domain specific design. This is responsibility of the domain-experts, following the decomposition of the V-model (Gräßler et al, 2018a;VDI, 2004). Holding such a core role, it is required to closely interact with the Requirement Engineer and ensure that the system architecture and design will allocate and fulfil all requirements.…”

Section: Iced19mentioning

confidence: 99%

See 2 more Smart Citations

Role Model for Systems Engineering Application

Grã‡ler¹,

Oleff²,

Hentze³

2019

Proc. Int. Conf. Eng. Des.

Self Cite

View full text Add to dashboard Cite

Twenty-three years ago, Sheard published a very well-known description of Systems Engineering roles. Each role represents and defines activities and tasks to be taken into account for performing Systems Engineering through the entire system life cycle. As today's more and more complex systems require different considerations and approaches, these activities and tasks have changed and thereby the description of the role model need to be updated. This work introduces the “Role Model for Systems Engineering Application”, which is adapted to today's circumstances, with the intention to give practitioners guidance in applying Systems Engineering. For this purpose, results from literature as well as from research projects and industrial applications experience were analyzed and combined to an updated role description.

show abstract

Section: Motivationmentioning

confidence: 99%

“…This role is based on the following references: (INCOSE UK, 2010;BKCASE Editorial Board, 2017;NASA, 2009;INCOSE, 2018;Sheard, 1996;Gräßler et al, 2018a;VDI, 2004). Basis for the role…”

Section: System Architectmentioning

confidence: 99%

Section: Iced19mentioning

confidence: 99%

See 1 more Smart Citation

Role Model for Systems Engineering Application

Grã‡ler¹,

Oleff²,

Hentze³

2019

Proc. Int. Conf. Eng. Des.

Self Cite

View full text Add to dashboard Cite

show abstract

“…Increasing complexity and shorter time-to-market heavily influence the New Product Development (NPD) of mechanical and mechatronic products (Pahl et al, 2007). To meet these challenges, a need exists to develop methods for industrial practices to respond to these challenges (Gräßler et al, 2018). Different and well established industry based methodologies in NPD have proven useful (Albers et al, 2016), but most are not focused on the generation of artefacts as a development of a minimum viable product.…”

Section: Introductionmentioning

confidence: 99%

A Scrum Agile Integrated Development Framework

Thiele

Weber

Reichwein

et al. 2020

Proc. Des. Soc.: Des. Conf.

View full text Add to dashboard Cite

With design methodologies, as Integrated Product Development, industry is continuously looking to improve their product development processes. Staying ahead concurrence forces them to deliver new and more complex products in shorter time. When it comes to fast delivery and requirement changes, product development can be inspired by agile methods. Although the application is difficult, the idea to implement these methods for development of products other than software comes out. To ease its implementation, this paper proposes to use IPD as a framework for agile product development.

show abstract

“…Historically, the so-called V-model (Forsberg and Mooz 1998) has been usefully employed as a reference model for the development of technical systems, including automotive (Graessler et al 2018;Pfeffer et al 2019), with the left side of the V-model being based on the hierarchical cascade of functional requirements from the top-level system to the component level. However, the V-model has limitations with highly complex systems and features, as exemplified by the autonomous vehicles, where it is often difficult to provide a full specification of requirements due to complexity and operational uncertainty.…”

Section: Introductionmentioning

confidence: 99%

Functional modelling of complex multi-disciplinary systems using the enhanced sequence diagram

Yildirim

Campean

2020

Res Eng Design

View full text Add to dashboard Cite

This paper introduces an Enhanced Sequence Diagram (ESD) as the basis for a structured framework for the functional analysis of complex multidisciplinary systems. The ESD extends the conventional sequence diagrams (SD) by introducing a rigorous functional flow-based modelling schemata to provide an enhanced basis for model-based functional requirements and architecture analysis in the early systems design stages. The proposed ESD heuristics include the representation of transactional and transformative functions required to deliver the use case sequence, and fork and join nodes to facilitate analysis of combining and bifurcating operations on flows. A case study of a personal mobility device is used to illustrate the deployment of the ESD methodology in relation to three common product development scenarios: (i) reverse engineering, (ii) the introduction of a specific technology to an existent system; and (iii) the introduction of a new feature as user-centric innovation for an existing system, at a logical design level, without reference to any solution. The case study analysis provides further insights into the effectiveness of the ESD to support function modelling and functional requirements capture, and architecture development. The significance of this paper is that it establishes a rigorous ESD-based functional analysis methodology to guide the practitioner with its deployment, facilitating its impact to both the engineering design and systems engineering communities, as well as the design practice in the industry.

show abstract

V-Models for Interdisciplinary Systems Engineering

Cited by 51 publications

References 8 publications

Role Model for Systems Engineering Application

Role Model for Systems Engineering Application

A Scrum Agile Integrated Development Framework

Functional modelling of complex multi-disciplinary systems using the enhanced sequence diagram

Contact Info

Product

Resources

About