Bitte benutzen Sie diese Kennung, um auf die Ressource zu verweisen: http://dx.doi.org/10.18419/opus-14882
Langanzeige der Metadaten
DC ElementWertSprache
dc.contributor.authorMarner, Kristina-
dc.contributor.authorWagner, Stefan-
dc.contributor.authorRuhe, Guenther-
dc.date.accessioned2024-08-28T06:42:33Z-
dc.date.available2024-08-28T06:42:33Z-
dc.date.issued2022de
dc.identifier.issn2073-431X-
dc.identifier.other1901824853-
dc.identifier.urihttp://nbn-resolving.de/urn:nbn:de:bsz:93-opus-ds-149011de
dc.identifier.urihttp://elib.uni-stuttgart.de/handle/11682/14901-
dc.identifier.urihttp://dx.doi.org/10.18419/opus-14882-
dc.description.abstractContext: Today’s vehicle development is focusing more and more on handling the vast amount of software and hardware inside the vehicle. The resulting planning and development of the software especially confronts original equipment manufacturers (OEMs) with major challenges that have to be mastered. This makes effective and efficient release planning that provides the development scope in the required quality even more important. In addition, the OEMs have to deal with boundary conditions given by the OEM itself and the standards as well as legislation the software and hardware have to conform to. Release planning is a key activity for successfully developing vehicles. Objective: The aim of this work is to introduce release planning patterns to simplify the release planning of software and hardware installed in a vehicle. Method: We followed a pattern identification process that was conducted at Dr. Ing. h. c. F. Porsche AG. Results: We introduce eight release planning patterns, which both address the fixed boundary conditions and structure the actual planning content of a release plan. The patterns address an automotive context and have been developed from a hardware and software point of view based on two examples from the case company. Conclusions: The presented patterns address recurring problems in an automotive context and are based on real life examples. The gathered knowledge can be used for further application in practice and related domains.en
dc.language.isoende
dc.relation.uridoi:10.3390/computers11060089de
dc.rightsinfo:eu-repo/semantics/openAccessde
dc.rights.urihttps://creativecommons.org/licenses/by/4.0/de
dc.subject.ddc004de
dc.titleRelease planning patterns for the automotive domainen
dc.typearticlede
dc.date.updated2023-11-14T02:06:57Z-
ubs.fakultaetInformatik, Elektrotechnik und Informationstechnikde
ubs.fakultaetFakultätsübergreifend / Sonstige Einrichtungde
ubs.institutInstitut für Software Engineeringde
ubs.institutFakultätsübergreifend / Sonstige Einrichtungde
ubs.publikation.seiten26de
ubs.publikation.sourceComputers 11 (2022), No. 89de
ubs.publikation.typZeitschriftenartikelde
Enthalten in den Sammlungen:05 Fakultät Informatik, Elektrotechnik und Informationstechnik

Dateien zu dieser Ressource:
Datei Beschreibung GrößeFormat 
computers-11-00089.pdf3,04 MBAdobe PDFÖffnen/Anzeigen


Diese Ressource wurde unter folgender Copyright-Bestimmung veröffentlicht: Lizenz von Creative Commons Creative Commons