Process Models from Software Engineering

According software process models for the description of an adequate design procedure are state of the art in the field of software engineering. No matter what process model is used - object oriented design procedures, the V-model, Extreme Programming, Agile Models, or simular - the crucial fact is the order of the process steps for

  • requirements analysis
  • concept development
  • implementation
  • integration
  • operation

The main difference between the various process models mainly is given by the detailing of the steps and the recommended iteration loops. But they always start first with the requirements analysis and not by a predetermined solution. (This may sound trivial, but as our engineering experience in numerous projects still show, it is not!)

ANDATA is using these process models not only for the software development but also for the functional design.

For example in the case of mechatronic systems not only the software (the electronic part) will be attacked with an adequate process model but also the functional (mechanic) part. For that purpose the functional (mechanic) requirements of the system will be represented in form of examples coming from tests and/or (stochastic) simulations and train the system to behave according to that requirements. That way the requirement analysis becomes an active procedure, which is mathematically operational and can grasp the requirements with the usage of DataMining- and SoftComputing-methods. Conflicts in the requirements between the desired actions and the available sensor signals can than be sorted out and solved instantly, normally resulting in fundamentally less complex solutions.