Software are not the only Fruit: Modelling Mechatronic Systems
This presentation and discussion explores how we use modelling in mechatronic systems. Traditionally modelling has been used to describe requirements and systems and to predict performance in all areas of engineering, including mechanical, chemical, and electrical. Later electronics was added to this list, and more recently (within the last 40 years) software. Currently, there seems to be a fashion to consider modelling in software engineering to the exclusion of more traditional disciplines.
Good methods used for years have been collected together under the umbrella of Agile. Many people think agile is just for software, however a great example of agile's wider application is Joe Justice using these methods to develop and build a car in one week.
Software is not the only show in town.
Nutzen für den Teilnehmer:
The audience will appreciate that modelling techniques add value and increase quality for all disciplines of systems engineering.
The presentation will allow the audience to profit from the opinions of their peers.
Models developed for mechatronic systems need to be understandable by mechanical, electronic, and software engineers. The interaction between different engineering disciplines needs to be modelled.
Some software engineers and their managers do not realise, or value, that modelling is advantageous for all engineering disciplines.
Some organisations concentrate on modelling software to the exclusion of the whole system and its component parts.
Unternehmen: Colin Hood Systems Engineering Ltd
Zielgruppe: Requirements Engineers, System Architects, Developers, System Engineers