CHALLENGES IN REQUIREMENTS ENGINEERING FOR MECHATRONIC SYSTEMS–PROBLEM ANALYSIS AND FIRST APPROACH
DOI:
https://doi.org/10.11113/jt.v76.5475Keywords:
Requirements, goals, hierarchy of functions, mechatronic systems, domain knowledge, modeling, continuous models, design methodologiesAbstract
In the development of intelligent mechatronic systems, a gap of tools and methodologies appears to exist, when technical requirements meet physical behavior modeling. Consistency between requirements, development and modeling is not fully achieved and more sophisticated methods seem to be needed. The meaning of requirements in terms of intelligent mechatronic systems is pointed out. Challenges in obtaining technical requirements are worked out by literature review. The influence, identified as most crucial, is domain knowledge. This challenge of the right assumptions considering domain knowledge is reinforced by the, in literature, predominantly applied discrete models. An approach for a solution of these challenges is presented at the end of this paper.
References
Hull, E., Jackson, K., and Dick, J. 2011. Requirements Engineering. Springer London Dordrecht Heidelberg New York.
The Standish Group International Incorporated. 2013. Chaos Manifesto 2013 Think Big, Act Small.
The Institute of Electrical and Electronics Engineers, Inc. 1998. IEEE Std 830-1998: IEEE Recommended Practice for Software Requirements Specifications, ISBN 0-7381-0332-2.
Lamsweerde, A. V. 2001. Goal-Oriented Requirements Engineering: A Guided Tour. Proceedings RE’01, 5th IEEE International Symposium on Requirements Engineering, Toronto. August 2001. 249-263.
Ahrens, G. 2000. Das Erfassen und Handhaben von Produktanforderungen. Berlin.
Alexander, C., Ishikawa, S., Silverstein, M., Jacobson, M., Fiksdahlking, I. and Angel, S. 1977. A Pattern Language – Towns, Buildings, Construction. 1st edition. Oxford University Press.
National Aeronautics and Space Administration. 2007. NASA Systems Engineering Handbook. ISBN 978-0-16-079747-7. Washington, D.C.
Estefan, J. A. 2008. Survey of Model-Based Systems Engineering (MBSE)Methodologies. INCOSE MBSE Initiative.
Walia, G. S. and Carver, J. C. 2009. A Systematic Literature Review to Identify and Classify Software Requirements Errors. Information and Software Technology. 51: 1087-1109.
Zave, P. and Jackson, M. 1997. Four Dark Corners of Requirements Engineering. ACM Transactions on Software Engineering and Methodology. 6(1): 1-30.
Friedenthal, S., Griego, R., Sampson, M. 2007. ICOSE Model Based Systems Engineering (MBSE) Initiative, INCOSE 2007, San Diego, USA.
Gausemeier, J., Dumitrescu, R., Steffen, D. 2013. Systems Engineering in der industriellen Praxis, Paderborn.
Frappier, M. and Habrias, H. 2006. A Comparison of the Specification Methods. Software Specification Methods: an Overview Using a Case Study. ISTE. Hermes Science Publishing.
Cheng, B. H. C., Atlee, J. M. 2007. Research Directions in Requirements Engineering. Future of Software Engineering (FOSE'07), IEEE.
Birkhofer, H. 2011. The Future of Design Methodology. Springer, London.
Jung, C. 2006. Anforderungsklärung in interdisziplinärer Entwicklungsumgebung. München.
Niknafs, A. and Berry, D. M. 2012. The Impact of Domain Knowledge on the Effectiveness of Requirements Idea Generation during Requirements Elicitation, Requirements Engineering Conference 2012 (RE 2012). Chicago, USA.
Downloads
Published
Issue
Section
License
Copyright of articles that appear in Jurnal Teknologi belongs exclusively to Penerbit Universiti Teknologi Malaysia (Penerbit UTM Press). This copyright covers the rights to reproduce the article, including reprints, electronic reproductions, or any other reproductions of similar nature.
