Hostname: page-component-6bf8c574d5-vmclg Total loading time: 0 Render date: 2025-02-28T22:04:01.062Z Has data issue: false hasContentIssue false
  • English
  • Français

A Semi-automated Requirements Reuse and Recycling Process for Autonomous Transportation Systems R&D

Part of: Systems Engineering

Published online by Cambridge University Press:  26 July 2019

Youssef Damak ,
Marija Jankovic ,
Yann Leroy  and
Karim Chelbi
Youssef Damak*
Affiliation:
CentraleSupélec; AKKA Technologies
Marija Jankovic
Affiliation:
CentraleSupélec;
Yann Leroy
Affiliation:
CentraleSupélec;
Karim Chelbi
Affiliation:
AKKA Technologies
*
Contact: Damak, Youssef, CentraleSupélec, Laboratoire Génie Industriel, France, youssef.damak@centralesupelec.fr

Abstract

Core share and HTML view are not available for this content. However, as you have access to this content, a full PDF is available via the ‘Save PDF’ action button.

The R&D of Autonomous Transportation Systems (ATS) is hindered by the lack of industrial feedback and client's knowledge about technological possibilities. In addition, because of intellectual properties (IP) issues, technology consulting companies can't directly reuse developed functionalities with different clients. In this context, requirements reuse technics presents a good way to capitalize on their knowledge while avoiding IP issues. However, the literature review on requirements reuse processes doesn't propose methods to the application of reuse processes with little information about the system's operational context. In this paper, we present a semi-automated requirement reuse and recycle process for ATS R&D. The process helps designers’ copes with the lack of inputs from the clients. Requirements candidates are retrieved from a database using Natural Language Processing and traceability propagation. It is applied to 3 use cases with inputs less than 5 concepts from the client's needs. The results validate its efficiency through number requirements retrieved and the analysis time consumption

Keywords

RequirementsAutonomous Transportation SystemsEarly design phasesProcess modelling
Type
Article
Information
Proceedings of the Design Society: International Conference on Engineering Design , Volume 1 , Issue 1 , July 2019 , pp. 3551 - 3560
Creative Commons
Creative Common License - CCCreative Common License - BYCreative Common License - NCCreative Common License - ND
This is an Open Access article, distributed under the terms of the Creative Commons Attribution-NonCommercial-NoDerivatives licence (http://creativecommons.org/licenses/by-nc-nd/4.0/), which permits non-commercial re-use, distribution, and reproduction in any medium, provided the original work is unaltered and is properly cited. The written permission of Cambridge University Press must be obtained for commercial re-use or in order to create a derivative work.
Copyright
© The Author(s) 2019

References

Adam, S. and Schmid, K., (2013). Effective Requirements Elicitation in Product Line Application Engineering – An Experiment, in: Requirements Engineering: Foundation for Software Quality. Springer Berlin Heidelberg, pp. 362–378. https://doi.org/10.1007/978-3-642-37422-7_26Google Scholar
Alexander, I. and Kiedaisch, F. (2002), “Towards recyclable system requirements”, Proceedings Ninth Annual IEEE International Conference and Workshop on the Engineering of Computer-Based Systems, pp. 9–16. https://doi.org/10.1109/ECBS.2002.999817.Google Scholar
Berkovich, M., Leimeister, J.M. and Krcmar, H. (2011), “Requirements Engineering for Product Service Systems”, Bus. Inf. Syst. Eng, Vol. 3, pp. 369–380. https://doi.org/10.1007/s12599-011-0192-2.Google Scholar
Curcio, K., Navarro, T., Malucelli, A. and Reinehr, S. (2018), “Requirements engineering: A systematic mapping study in agile software development”, J. Syst. Softw, Vol. 139, pp. 32–50. https://doi.org/10.1016/j.jss.2018.01.036.Google Scholar
Damak, Y., Jankovic, M., Leroy, Y. and Yannou, B. (2018), “Analysis of Safety Requirements Evolution in the Transition of Land Transportation Systems Toward Autonomy”, Presented at the 15th International Design Conference, pp. 2845–2854. https://doi.org/10.21278/idc.2018.0448.Google Scholar
Garro, A., Tundis, A., Bouskela, D., Jardin, A., Thuy, N., Otter, M., Buffoni, L., Fritzson, P., Sjölund, M., Schamai, W. and Olsson, H. (2016), “On formal cyber physical system properties modeling: A new temporal logic language and a Modelica-based solution”, 2016 IEEE International Symposium on Systems Engineering (ISSE), pp. 1–8. https://doi.org/10.1109/SysEng.2016.7753137.Google Scholar
Holt, J., Perry, S.A. and Brownsword, M. (2012), Model-based requirements engineering, IET.Google Scholar
Horváth, I. (2014), “What the Design Theory of Social-Cyber-Physical Systems Must Describe, Explain and Predict?”, In: Chakrabarti, A. and Blessing, L.T.M. (Ed.), An Anthology of Theories and Models of Design: Philosophy, Approaches and Empirical Explorations, Springer London, London, pp. 99–120. https://doi.org/10.1007/978-1-4471-6338-1_5.Google Scholar
Irshad, M., Petersen, K. and Poulding, S. (2018), “A systematic literature review of software requirements reuse approaches”, Inf. Softw. Technol, Vol. 93, pp. 223–245. https://doi.org/10.1016/j.infsof.2017.09.009.Google Scholar
Jiao, J.R. and Chen, C.-H. (2006), “Customer Requirement Management in Product Development: A Review of Research Issues”, Concurr. Eng, Vol. 14, pp. 173–185. https://doi.org/10.1177/1063293X06068357.Google Scholar
Kaiya, H. and Saeki, M. (2006), “Using Domain Ontology as Domain Knowledge for Requirements Elicitation”, 14th IEEE International Requirements Engineering Conference (RE'06), pp. 189–198. https://doi.org/10.1109/RE.2006.72.Google Scholar
Knethen, A.v., Paech, B., Kiedaisch, F. and Houdek, F. (2002), “Systematic requirements recycling through abstraction and traceability”, Proceedings IEEE Joint International Conference on Requirements Engineering, pp. 273–281. https://doi.org/10.1109/ICRE.2002.1048538.Google Scholar
Moros, B., Vicente-Chicote, C. and Toval, A. (2008), “REMM-Studio +: Modeling Variability to Enable Requirements Reuse”, Conceptual Modeling - ER 2008, Springer Berlin Heidelberg, pp. 530–531. https://doi.org/10.1007%2F978-3-540-87877-3_46.Google Scholar
Pacheco, C.L., Garcia, I.A., Calvo-Manzano, J.A. and Arcilla, M. (2015), “A proposed model for reuse of software requirements in requirements catalog”, J. Softw. Evol. Process, Vol. 27, pp. 1–21. https://doi.org/10.1002/smr.1698.Google Scholar
Scherer, H., Albers, A. and Bursac, N. (2017), “Model Based Requirements Engineering for the Development of Modular Kits”, Complex Syst. Eng. Dev. Proc. 27th CIRP Des. Conf, Cranfield Univ. UK, 10th – 12th May 2017 60, pp. 145–150. https://doi.org/10.1016/j.procir.2017.01.032.Google Scholar
Sutcliffe, A. (2003), “Scenario-based requirements engineering”, 11th IEEE International Requirements Engineering Conference, 2003, IEEE, pp. 320–329. https://doi.org/10.1109/ICRE.2003.1232776.Google Scholar
Toval, A., Nicolás, J., Moros, B. and García, F. (2002), “Requirements Reuse for Improving Information Systems Security: A Practitioner's Approach”, Requir. Eng, Vol. 6, pp. 205–219. https://doi.org/10.1007/PL00010360.Google Scholar
Winkler, S. and von Pilgrim, J. (2010), “A survey of traceability in requirements engineering and model-driven development”, Softw. Syst. Model, Vol. 9, pp. 529–565. https://doi.org/10.1007/s10270-009-0145-0.Google Scholar
Zhang, Z. (2007), “Effective requirements development-A comparison of requirements elicitation techniques, in: Software Quality Management XV: Software Quality in the Knowledge Society (SQM2007)”, British Computer Society, pp. 225–240.Google Scholar