Integrated and iterative systems engineering and software requirements engineering for technical systems

The development of software‐intensive technical systems involves several engineering disciplines like mechanical, electrical, control, and particularly software engineering. Model‐based Systems Engineering (MBSE) coordinates these disciplines throughout the development by means of discipline‐spannin...

Ausführliche Beschreibung

Gespeichert in:
Bibliographische Detailangaben
Veröffentlicht in:Journal of software : evolution and process 2016-09, Vol.28 (9), p.722-743
Hauptverfasser: Holtmann, Jörg, Bernijazov, Ruslan, Meyer, Matthias, Schmelter, David, Tschirner, Christian
Format: Artikel
Sprache:eng
Schlagworte:
Online-Zugang:Volltext
Tags: Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
container_end_page 743
container_issue 9
container_start_page 722
container_title Journal of software : evolution and process
container_volume 28
creator Holtmann, Jörg
Bernijazov, Ruslan
Meyer, Matthias
Schmelter, David
Tschirner, Christian
description The development of software‐intensive technical systems involves several engineering disciplines like mechanical, electrical, control, and particularly software engineering. Model‐based Systems Engineering (MBSE) coordinates these disciplines throughout the development by means of discipline‐spanning processes and a system model. Such a system model provides a common understanding of the system under development and serves as a starting point for the discipline‐specific development. An integral part of MBSE is the requirements engineering on the system level. However, these requirements need to be refined for the discipline‐specific development to start, for example, into specific requirements for the embedded software. Because existing MBSE approaches lack support for this refinement step, we conceived in previous work a systematic transition from MBSE to model‐based software requirements engineering. We automated the steps of the transition where possible, in order to avoid error‐prone and time‐consuming manual tasks. In this paper, we extend this approach with support for subsequent process iterations and provide an algorithm for the automated steps. We illustrate the approach and perform a case study with an example of an automotive embedded system. Copyright © 2016 John Wiley & Sons, Ltd. The development of software‐intensive technical systems involves several engineering disciplines. Model‐based systems engineering (MBSE) coordinates these disciplines throughout the development by means of a discipline‐spanning system model. An integral part of MBSE is the requirements engineering on the system level. However, these requirements need to be refined for the discipline‐specific development to start, for example, into specific requirements for the embedded software. In this paper, we present a systematic, semi‐automatic, and iterative transition from MBSE to model‐based software requirements engineering.
doi_str_mv 10.1002/smr.1780
format Article
fullrecord <record><control><sourceid>proquest_cross</sourceid><recordid>TN_cdi_proquest_journals_1820521324</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><sourcerecordid>4186090931</sourcerecordid><originalsourceid>FETCH-LOGICAL-c3310-2fe4784012da133abdfb9d8f50c505959e7ad9f1a046871c8268f9fe62c13d3</originalsourceid><addsrcrecordid>eNp10N9LAkEQB_AjChIT-hMOeunlbH_d7d5jSJqgBRkEvizr3ayueXu6e2b-961ZgQ_ty-zAhxnmG0XXGHUxQuTOV66LuUBnUYsgxhPOBD7_-3N6GXW8X6LwMoJSlraixdA2MHeqgTJWtoxNA6ExHxD7vW-g8jHYubEAztj5t_C1bnbKQexgszUOKrDNqdK1ixsoFtYUavU75yq60GrlofNT29Gk__Dae0xGz4Nh736UFJRilBANjAuGMCkVplTNSj3LS6FTVKQozdMcuCpzjRVimeC4ECQTOteQkQLTkrajm-PUtas3W_CNXNZbZ8NCiUU4mWBKWFC3R1W42nsHWq6dqZTbS4zkIUgZgpSHIANNjnRnVrD_18nJ-OXUm3D1559X7l1mnPJUvj0NJB_1x32GpnJKvwCGOYVT</addsrcrecordid><sourcetype>Aggregation Database</sourcetype><iscdi>true</iscdi><recordtype>article</recordtype><pqid>1820521324</pqid></control><display><type>article</type><title>Integrated and iterative systems engineering and software requirements engineering for technical systems</title><source>Wiley Online Library Journals Frontfile Complete</source><creator>Holtmann, Jörg ; Bernijazov, Ruslan ; Meyer, Matthias ; Schmelter, David ; Tschirner, Christian</creator><creatorcontrib>Holtmann, Jörg ; Bernijazov, Ruslan ; Meyer, Matthias ; Schmelter, David ; Tschirner, Christian</creatorcontrib><description>The development of software‐intensive technical systems involves several engineering disciplines like mechanical, electrical, control, and particularly software engineering. Model‐based Systems Engineering (MBSE) coordinates these disciplines throughout the development by means of discipline‐spanning processes and a system model. Such a system model provides a common understanding of the system under development and serves as a starting point for the discipline‐specific development. An integral part of MBSE is the requirements engineering on the system level. However, these requirements need to be refined for the discipline‐specific development to start, for example, into specific requirements for the embedded software. Because existing MBSE approaches lack support for this refinement step, we conceived in previous work a systematic transition from MBSE to model‐based software requirements engineering. We automated the steps of the transition where possible, in order to avoid error‐prone and time‐consuming manual tasks. In this paper, we extend this approach with support for subsequent process iterations and provide an algorithm for the automated steps. We illustrate the approach and perform a case study with an example of an automotive embedded system. Copyright © 2016 John Wiley &amp; Sons, Ltd. The development of software‐intensive technical systems involves several engineering disciplines. Model‐based systems engineering (MBSE) coordinates these disciplines throughout the development by means of a discipline‐spanning system model. An integral part of MBSE is the requirements engineering on the system level. However, these requirements need to be refined for the discipline‐specific development to start, for example, into specific requirements for the embedded software. In this paper, we present a systematic, semi‐automatic, and iterative transition from MBSE to model‐based software requirements engineering.</description><identifier>ISSN: 2047-7473</identifier><identifier>EISSN: 2047-7481</identifier><identifier>DOI: 10.1002/smr.1780</identifier><language>eng</language><publisher>Chichester: Blackwell Publishing Ltd</publisher><subject>development process ; model transformations ; requirements engineering ; systems engineering ; technical systems</subject><ispartof>Journal of software : evolution and process, 2016-09, Vol.28 (9), p.722-743</ispartof><rights>Copyright © 2016 John Wiley &amp; Sons, Ltd.</rights><lds50>peer_reviewed</lds50><woscitedreferencessubscribed>false</woscitedreferencessubscribed><citedby>FETCH-LOGICAL-c3310-2fe4784012da133abdfb9d8f50c505959e7ad9f1a046871c8268f9fe62c13d3</citedby><cites>FETCH-LOGICAL-c3310-2fe4784012da133abdfb9d8f50c505959e7ad9f1a046871c8268f9fe62c13d3</cites></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><linktopdf>$$Uhttps://onlinelibrary.wiley.com/doi/pdf/10.1002%2Fsmr.1780$$EPDF$$P50$$Gwiley$$H</linktopdf><linktohtml>$$Uhttps://onlinelibrary.wiley.com/doi/full/10.1002%2Fsmr.1780$$EHTML$$P50$$Gwiley$$H</linktohtml><link.rule.ids>314,776,780,1411,27903,27904,45553,45554</link.rule.ids></links><search><creatorcontrib>Holtmann, Jörg</creatorcontrib><creatorcontrib>Bernijazov, Ruslan</creatorcontrib><creatorcontrib>Meyer, Matthias</creatorcontrib><creatorcontrib>Schmelter, David</creatorcontrib><creatorcontrib>Tschirner, Christian</creatorcontrib><title>Integrated and iterative systems engineering and software requirements engineering for technical systems</title><title>Journal of software : evolution and process</title><addtitle>J. Softw. Evol. and Proc</addtitle><description>The development of software‐intensive technical systems involves several engineering disciplines like mechanical, electrical, control, and particularly software engineering. Model‐based Systems Engineering (MBSE) coordinates these disciplines throughout the development by means of discipline‐spanning processes and a system model. Such a system model provides a common understanding of the system under development and serves as a starting point for the discipline‐specific development. An integral part of MBSE is the requirements engineering on the system level. However, these requirements need to be refined for the discipline‐specific development to start, for example, into specific requirements for the embedded software. Because existing MBSE approaches lack support for this refinement step, we conceived in previous work a systematic transition from MBSE to model‐based software requirements engineering. We automated the steps of the transition where possible, in order to avoid error‐prone and time‐consuming manual tasks. In this paper, we extend this approach with support for subsequent process iterations and provide an algorithm for the automated steps. We illustrate the approach and perform a case study with an example of an automotive embedded system. Copyright © 2016 John Wiley &amp; Sons, Ltd. The development of software‐intensive technical systems involves several engineering disciplines. Model‐based systems engineering (MBSE) coordinates these disciplines throughout the development by means of a discipline‐spanning system model. An integral part of MBSE is the requirements engineering on the system level. However, these requirements need to be refined for the discipline‐specific development to start, for example, into specific requirements for the embedded software. In this paper, we present a systematic, semi‐automatic, and iterative transition from MBSE to model‐based software requirements engineering.</description><subject>development process</subject><subject>model transformations</subject><subject>requirements engineering</subject><subject>systems engineering</subject><subject>technical systems</subject><issn>2047-7473</issn><issn>2047-7481</issn><fulltext>true</fulltext><rsrctype>article</rsrctype><creationdate>2016</creationdate><recordtype>article</recordtype><recordid>eNp10N9LAkEQB_AjChIT-hMOeunlbH_d7d5jSJqgBRkEvizr3ayueXu6e2b-961ZgQ_ty-zAhxnmG0XXGHUxQuTOV66LuUBnUYsgxhPOBD7_-3N6GXW8X6LwMoJSlraixdA2MHeqgTJWtoxNA6ExHxD7vW-g8jHYubEAztj5t_C1bnbKQexgszUOKrDNqdK1ixsoFtYUavU75yq60GrlofNT29Gk__Dae0xGz4Nh736UFJRilBANjAuGMCkVplTNSj3LS6FTVKQozdMcuCpzjRVimeC4ECQTOteQkQLTkrajm-PUtas3W_CNXNZbZ8NCiUU4mWBKWFC3R1W42nsHWq6dqZTbS4zkIUgZgpSHIANNjnRnVrD_18nJ-OXUm3D1559X7l1mnPJUvj0NJB_1x32GpnJKvwCGOYVT</recordid><startdate>201609</startdate><enddate>201609</enddate><creator>Holtmann, Jörg</creator><creator>Bernijazov, Ruslan</creator><creator>Meyer, Matthias</creator><creator>Schmelter, David</creator><creator>Tschirner, Christian</creator><general>Blackwell Publishing Ltd</general><general>Wiley Subscription Services, Inc</general><scope>BSCLL</scope><scope>AAYXX</scope><scope>CITATION</scope><scope>7SC</scope><scope>8FD</scope><scope>JQ2</scope><scope>L7M</scope><scope>L~C</scope><scope>L~D</scope></search><sort><creationdate>201609</creationdate><title>Integrated and iterative systems engineering and software requirements engineering for technical systems</title><author>Holtmann, Jörg ; Bernijazov, Ruslan ; Meyer, Matthias ; Schmelter, David ; Tschirner, Christian</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-LOGICAL-c3310-2fe4784012da133abdfb9d8f50c505959e7ad9f1a046871c8268f9fe62c13d3</frbrgroupid><rsrctype>articles</rsrctype><prefilter>articles</prefilter><language>eng</language><creationdate>2016</creationdate><topic>development process</topic><topic>model transformations</topic><topic>requirements engineering</topic><topic>systems engineering</topic><topic>technical systems</topic><toplevel>peer_reviewed</toplevel><toplevel>online_resources</toplevel><creatorcontrib>Holtmann, Jörg</creatorcontrib><creatorcontrib>Bernijazov, Ruslan</creatorcontrib><creatorcontrib>Meyer, Matthias</creatorcontrib><creatorcontrib>Schmelter, David</creatorcontrib><creatorcontrib>Tschirner, Christian</creatorcontrib><collection>Istex</collection><collection>CrossRef</collection><collection>Computer and Information Systems Abstracts</collection><collection>Technology Research Database</collection><collection>ProQuest Computer Science Collection</collection><collection>Advanced Technologies Database with Aerospace</collection><collection>Computer and Information Systems Abstracts – Academic</collection><collection>Computer and Information Systems Abstracts Professional</collection><jtitle>Journal of software : evolution and process</jtitle></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext</fulltext></delivery><addata><au>Holtmann, Jörg</au><au>Bernijazov, Ruslan</au><au>Meyer, Matthias</au><au>Schmelter, David</au><au>Tschirner, Christian</au><format>journal</format><genre>article</genre><ristype>JOUR</ristype><atitle>Integrated and iterative systems engineering and software requirements engineering for technical systems</atitle><jtitle>Journal of software : evolution and process</jtitle><addtitle>J. Softw. Evol. and Proc</addtitle><date>2016-09</date><risdate>2016</risdate><volume>28</volume><issue>9</issue><spage>722</spage><epage>743</epage><pages>722-743</pages><issn>2047-7473</issn><eissn>2047-7481</eissn><abstract>The development of software‐intensive technical systems involves several engineering disciplines like mechanical, electrical, control, and particularly software engineering. Model‐based Systems Engineering (MBSE) coordinates these disciplines throughout the development by means of discipline‐spanning processes and a system model. Such a system model provides a common understanding of the system under development and serves as a starting point for the discipline‐specific development. An integral part of MBSE is the requirements engineering on the system level. However, these requirements need to be refined for the discipline‐specific development to start, for example, into specific requirements for the embedded software. Because existing MBSE approaches lack support for this refinement step, we conceived in previous work a systematic transition from MBSE to model‐based software requirements engineering. We automated the steps of the transition where possible, in order to avoid error‐prone and time‐consuming manual tasks. In this paper, we extend this approach with support for subsequent process iterations and provide an algorithm for the automated steps. We illustrate the approach and perform a case study with an example of an automotive embedded system. Copyright © 2016 John Wiley &amp; Sons, Ltd. The development of software‐intensive technical systems involves several engineering disciplines. Model‐based systems engineering (MBSE) coordinates these disciplines throughout the development by means of a discipline‐spanning system model. An integral part of MBSE is the requirements engineering on the system level. However, these requirements need to be refined for the discipline‐specific development to start, for example, into specific requirements for the embedded software. In this paper, we present a systematic, semi‐automatic, and iterative transition from MBSE to model‐based software requirements engineering.</abstract><cop>Chichester</cop><pub>Blackwell Publishing Ltd</pub><doi>10.1002/smr.1780</doi><tpages>22</tpages></addata></record>
fulltext fulltext
identifier ISSN: 2047-7473
ispartof Journal of software : evolution and process, 2016-09, Vol.28 (9), p.722-743
issn 2047-7473
2047-7481
language eng
recordid cdi_proquest_journals_1820521324
source Wiley Online Library Journals Frontfile Complete
subjects development process
model transformations
requirements engineering
systems engineering
technical systems
title Integrated and iterative systems engineering and software requirements engineering for technical systems
url https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2025-01-24T12%3A04%3A47IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-proquest_cross&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft.genre=article&rft.atitle=Integrated%20and%20iterative%20systems%20engineering%20and%20software%20requirements%20engineering%20for%20technical%20systems&rft.jtitle=Journal%20of%20software%20:%20evolution%20and%20process&rft.au=Holtmann,%20J%C3%B6rg&rft.date=2016-09&rft.volume=28&rft.issue=9&rft.spage=722&rft.epage=743&rft.pages=722-743&rft.issn=2047-7473&rft.eissn=2047-7481&rft_id=info:doi/10.1002/smr.1780&rft_dat=%3Cproquest_cross%3E4186090931%3C/proquest_cross%3E%3Curl%3E%3C/url%3E&disable_directlink=true&sfx.directlink=off&sfx.report_link=0&rft_id=info:oai/&rft_pqid=1820521324&rft_id=info:pmid/&rfr_iscdi=true