Showing papers on "V-Model (software development) published in 2012"
1 Jan 2012
TL;DR: A process model on the basis of the known V model of the guideline VDI 2206 is developed whereas weight reduction is no longer seen as optimization task at the end of product development, instead it will be integrated into the process itself and will be evaluated within several analysis steps which are distributed over the design procedure.
Abstract: Existing process models for the development of mechatronic systems do not consider the task for weight reduction and its positive effects for the manufacturing and usage phase of systems, e.g. savings in resources and energy. Lightweight design only often represents an optimization step after the product development which leads to problems like restricted functionality, increase of development costs and development time or quality. In this paper, a process model on the basis of the known V model of the guideline VDI 2206 is developed whereas weight reduction is no longer seen as optimization task at the end of product development. Instead, it will be integrated into the process itself and will be evaluated within several analysis steps which are distributed over the design procedure.
6 citations
TL;DR: A model-based design approach for real-time applications in the telescope area is explored, and for a specific axis controller application the result is successfully integrated into the legacy platform of the existing VLT software.
Abstract: Most of the real-time control systems at the existing ESO telescopes were developed with "traditional" methods, using
general purpose VMEbus electronics, and running applications that were coded by hand, mostly using the C
programming language under VxWorks
As we are moving towards more modern design methods, we have explored a model-based design approach for real-time
applications in the telescope area, and used the control algorithm of a standard telescope main axis as a first example
We wanted to have a clear work-flow that follows the "correct-by-construction" paradigm, where the implementation is
testable in simulation on the development host, and where the testing time spent by debugging on target is minimized It
should respect the domains of control, electronics, and software engineers in the choice of tools It should be a targetindependent
approach so that the result could be deployed on various platforms
We have selected the Mathworks tools Simulink, Stateflow, and Embedded Coder for design and implementation, and
LabVIEW with NI hardware for hardware-in-the-loop testing, all of which are widely used in industry We describe how
these tools have been used in order to model, simulate, and test the application We also evaluate the benefits of this
approach compared to the traditional method with respect to testing effort and maintainability
For a specific axis controller application we have successfully integrated the result into the legacy platform of the
existing VLT software, as well as demonstrated how to use the same design for a new development with a completely
different environment
5 citations