From goals to systems via technical requirements and physical models design of an intelligent cash handling system

In the development of intelligent mechatronic systems, a gap of tools and methodologies exists, when technical requirements meet physical behavior modeling. Consistency and pervasiveness between requirements, development and modeling is not fully achieved and more sophisticated methods are needed. In a first step, the meaning of requirements in terms of intelligent mechatronic systems is pointed out. Challenges in obtaining technical requirements are worked out. A demand for action is derived and an approach to tackle these challenges is then presented. A consistent development process is described with the help of an application example - the development of a robotic system is displayed. Particularly for multidisciplinary systems, design methodologies are needed. Complexity in those systems is on a superior level and needs to be handled effectively and efficiently. We therefore enrich a design method for intelligent mechatronic systems with a more detailed integration of physical models. Our approach starts with a given system goal. It is shown how to derive technical requirements of the system. A simulation model is worked out systematically via the combination of physical modeling and the utilization of partial models. A possibility to gather the gained information is shown at the end with the help of a N3 chart. The N3 chart is easily modifiable and intelligible by a wide range of developers. The approach increases consistency from early development phases to technical requirements. The utilization of partial and physical models shows the potential for symbiosis. The approach is evaluated at the end.

[1]  Herbert Birkhofer,et al.  The Future of Design Methodology , 2011 .

[2]  Jürgen Gausemeier,et al.  Studie: Systems Engineering in der industriellen Praxis , 2013 .

[3]  Betty H. C. Cheng,et al.  Research Directions in Requirements Engineering , 2007, Future of Software Engineering (FOSE '07).

[4]  Jeffrey C. Carver,et al.  A systematic literature review to identify and classify software requirement errors , 2009, Inf. Softw. Technol..

[5]  Michael Jackson,et al.  Four dark corners of requirements engineering , 1997, TSEM.

[6]  P. Gawthrop,et al.  Bond-graph modeling , 2007, IEEE Control Systems.

[7]  H. Habrias,et al.  A Comparison of the Specification Methods , 2000 .

[8]  Ansgar Trächtler,et al.  Model-Based Design of Mechatronic Systems by Means of Semantic Web Ontologies and Reusable Solution Elements , 2012 .

[9]  Tetsuo Tomiyama,et al.  Supporting conceptual design based on the function-behavior-state modeler , 1996, Artificial Intelligence for Engineering Design, Analysis and Manufacturing.

[10]  Jeff A. Estefan,et al.  of Model-Based Systems Engineering ( MBSE ) Methodologies , 2008 .

[11]  Max Jacobson,et al.  A Pattern Language: Towns, Buildings, Construction , 1981 .

[12]  Ansgar Trächtler,et al.  CHALLENGES IN REQUIREMENTS ENGINEERING FOR MECHATRONIC SYSTEMS-PROBLEM ANALYSIS AND FIRST APPROACH , 2015 .

[13]  Marc Frappier,et al.  19 - A Comparison of the Specification Methods , 2010 .

[14]  Nelly Bencomo,et al.  A Goal-Based Modeling Approach to Develop Requirements of an Adaptive System with Environmental Uncertainty , 2009, MoDELS.

[15]  B. Chandrasekaran,et al.  Functional representation: A brief historical perspective , 1994, Appl. Artif. Intell..

[16]  Claes Wohlin,et al.  Engineering and Managing Software Requirements , 2005 .

[17]  Tetsuo Tomiyama,et al.  Towards automation of control software: A review of challenges in mechatronic design , 2010 .