default search action
DSM@SPLASH 2013: Indianapolis, IN, USA
- Jeff Gray, Steven Kelly, Jonathan Sprinkle:
Proceedings of the 2013 ACM workshop on Domain-specific modeling, DSM@SPLASH 2013, Indianapolis, Indiana, USA, October 27, 2013. ACM 2013, ISBN 978-1-4503-2600-1
Experience and application
- Md. Abdullah Al Mamun, Christian Berger, Jörgen Hansson:
MDE-based sensor management and verification for a self-driving miniature vehicle. 1-6 - Timo Wegeler, Friederike Gutzeit, Aurèle Destailleur, Bernhard Dock:
Evaluating the benefits of using domain-specific modeling languages: an experience report. 7-12 - Patrick Morley, Alex Warren, Ethan Rabb, Sean Whitsitt, Matt Bunting, Jonathan Sprinkle:
Generating a ROS/JAUS bridge for an autonomous ground vehicle. 13-18
Tools
- Steven Kelly, Risto Pohjonen:
Dynamic symbol templates and ports in MetaEdit+. 19-20 - Faruk Caglar, Kyoungho An, Shashank Shekhar, Aniruddha S. Gokhale:
Model-driven performance estimation, deployment, and resource management for cloud-hosted services. 21-26 - Ioannis N. Athanasiadis, Ferdinando Villa:
A roadmap to domain specific programming languages for environmental modeling: key requirements and concepts. 27-32 - Steven Kelly:
Empirical comparison of language workbenches. 33-38
Looking forward
- Bart Meyers, Manuel Wimmer, Hans Vangheluwe, Joachim Denil:
Towards domain-specific property languages: the ProMoBox approach. 39-44 - Lars Ackermann, Bernhard Volz:
model[NL]generation: natural language model extraction. 45-50 - Bastian Roth, Matthias Jahn, Stefan Jablonski:
On the way of bottom-up designing textual domain-specific modelling languages. 51-56 - David Méndez-Acuña, Rubby Casallas, Anne Etien:
On the customization of model management systems for file-centric IDEs. 57-62
manage site settings
To protect your privacy, all features that rely on external API calls from your browser are turned off by default. You need to opt-in for them to become active. All settings here will be stored as cookies with your web browser. For more information see our F.A.Q.