Abstract
A preliminary and relevant step of the whole process includes a complete collection of customer needs and a suitable elicitation of requirements. This activity is never trivial and requires to be suitably formalized. This is done by resorting to the test cases of this handbook. In the meanwhile, the role of stakeholders is even investigated and defined. Requirements are then defined, classified and categorized for a better implementation of the MBSE. A direct implementation of requirements analysis is performed for the two examples.
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
Notes
- 1.
Scientific American, September 1994 and Standish Group 1995, 1996.
References
Michelli, J. A. (2016). Driven to delight. New York: McGraw Hill.
Pyster, A., Olwell, D., Hutchison, N., Enck, S., Anthony, J., Henry, D., et al. (2012). Guide to the Systems Engineering Body of Knowledge (SEBoK). Hoboken, NJ, USA: The Trustees of the Stevens Institute of Technology.
Walden, D., Roedler, G., Forsberg, K., Hamelin, D., & Shortell, T. (2015). Systems engineering handbook of INCOSE (4th ed.). Wiley.
Author information
Authors and Affiliations
Corresponding author
Rights and permissions
Copyright information
© 2018 Springer International Publishing AG
About this chapter
Cite this chapter
Brusa, E., Calà, A., Ferretto, D. (2018). Systems, Customer Needs and Requirements. In: Systems Engineering and Its Application to Industrial Product Development. Studies in Systems, Decision and Control, vol 134. Springer, Cham. https://doi.org/10.1007/978-3-319-71837-8_4
Download citation
DOI: https://doi.org/10.1007/978-3-319-71837-8_4
Published:
Publisher Name: Springer, Cham
Print ISBN: 978-3-319-71836-1
Online ISBN: 978-3-319-71837-8
eBook Packages: EngineeringEngineering (R0)