Abstract
Usually, the development of a product does not start from scratch, but parts of a product developed previously are used as a starting basis. In the latter case, the system requirements must be selected carefully to avoid missing system requirements and to avoid the implementation of not intended system requirements. The presented examples “Clone and Own” and “Linking” are approaches supporting reuse and some selection criteria and best practices supplement these examples. Mapping the customer requirements to the system requirements provides evidences for fulfillment of the customer’s needs.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
References
Dreves, R., Hällmayer, F., Haunert, L., Sechser, B., Rieß, A.: A method to realize traceability in development processes. J. Softw. Evol. Process 28, 1011–1019 (2016). https://doi.org/10.1002/smr.1828
VDA QMC: Automotive SPICE® process reference model process assessment model, version 3.1 (2017)
The SPI Manifesto: EuroSPI 2009, Alcala (2009) http://2019.eurospi.net/images/eurospi/spi_manifesto.pdf
Author information
Authors and Affiliations
Corresponding author
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2019 Springer Nature Switzerland AG
About this paper
Cite this paper
Dreves, R., Haunert, L., Karner, C., Mayer, R., Mergen, S., Sechser, B. (2019). Traceability Between Customer Projects and Platform Projects. In: Walker, A., O'Connor, R., Messnarz, R. (eds) Systems, Software and Services Process Improvement. EuroSPI 2019. Communications in Computer and Information Science, vol 1060. Springer, Cham. https://doi.org/10.1007/978-3-030-28005-5_27
Download citation
DOI: https://doi.org/10.1007/978-3-030-28005-5_27
Published:
Publisher Name: Springer, Cham
Print ISBN: 978-3-030-28004-8
Online ISBN: 978-3-030-28005-5
eBook Packages: Computer ScienceComputer Science (R0)