Telos: representing knowledge about information systems
ACM Transactions on Information Systems (TOIS)
ConceptBase—a deductive object base for meta data management
Journal of Intelligent Information Systems - Special issue: deductive and object-oriented databases
Modelling strategic relationships for process reengineering
Modelling strategic relationships for process reengineering
Embedded Software Engineering: The State of the Practice
IEEE Software
Challenges in automotive software engineering
Proceedings of the 28th international conference on Software engineering
Requirements Engineering for Control Systems Development in Small and Medium-Sized Enterprises
RE '08 Proceedings of the 2008 16th IEEE International Requirements Engineering Conference
Graphical definition of in-place transformations in the eclipse modeling framework
MoDELS'06 Proceedings of the 9th international conference on Model Driven Engineering Languages and Systems
Hi-index | 0.00 |
When developing control systems software, mathematically based modelling tools such as Matlab/Simulink are used for design, simulation, and implementation. Thus, a continuous model-based approach does not need to map requirements to, for example, UML class diagrams but to this mathematical representation. In this paper, we build on previous work that has applied the requirements formalism i* to the development of control systems software and present a mapping from i* models to Matlab/Simulink models. During a first manual transformation step, design alternatives are resolved. The second, automated step generates a Matlab/Simulink skeleton model from the i* model. Finally, an interactive step allows incorporating existing hardware and platform components into the skeleton. As a running example, we consider the development of a parking assistant.