Doorgaan naar hoofdcontent

Exploring the Domain-Specific Language Tools

I'm currently familiarize myself with the Microsoft's concept of Domain-Specific Languages. And I must say I'm having a hard time collecting usefull information on the concept. It seems that beside the content in the MSDN Library and a rare presentation on Channel 9 there is not much information out there on the web. Well let's see where the subject takes me. Anyway, this subject should keep be busy this week, before I plunge down in the world of Cordys for 4 weeks.

Reacties

Hi Maurice,

Maybe this will help:

The website of the domain-specific modeling forum: http://www.dsmforum.org

MetaCase's MetaEdit+, the leading environment for modeling and generating code from domain-specific modeling languages: http://www.metacase.com , especially the "Resources" page and the "Download" page should be helpful, also keep your eye open for a series of webcasts they are preparing.

Blog: Steven Kelly on DSM
http://www.metacase.com/blogs/stevek/blogView

Blog: Juha-Pekka on DSM
http://www.metacase.com/blogs/jpt/blogView

Also try the blogs of:
Gareth J, Keith Short, Jack Greenfield, Alan Cameron Wills

A wealth of information from the proceedings of the DSM Workshops at OOPSLA:
http://www.dsmforum.org/events/DSM06/

An extensive list of articles on the topic in leading magazines:
http://www.metacase.com/fs.asp?vasen=press/vasen.html&paa=press/press_coverage.html

I hope (now) you agree with me that, actually, there is an abundance of information on modeling with DSL's :)

You'll be an expert on the topic by the time you've gone through it all!

All the best,

Martijn
Maurice zei…
Marijn,
Thanks for your comment. However, my particular problem is that I'm bound to Microsoft technology and that doesn't make my live as easy as I would like.
Maurice

Populaire posts van deze blog

A Software Developer's Reading Plan

This list describes the reading program a software developer needs to work through to achieve full professional standing. The plan described is a generic baseline plan for a software professional who wants to focus on development. Introductory Level To move beyond "introductory" level, a developer must read the following books: Adams, James L. Conceptual Blockbusting: A Guide to Better Ideas, 4th ed. Cambridge, MA: Perseus Publishing, 2001. Bentley, Jon. Programming Pearls, 2d ed. Reading, MA: Addison-Wesley, 2000. Glass, Robert L. Facts and Fallacies of software Engineering. Boston, MA: Addison-Wesley, 2003. McConnell, Steve. Software Project Survival Guide. Redmond, WA: Microsoft Press, 1998. McConnell, Steve. Code Complete, 2d ed. Redmond, WA: Microsoft Press, 2004. Practitioner Level To achieve "intermediate" status, a programmer needs to read the following additional materials: Berczuk, Stephen P. and Brad Appleton. Software Configuration Manag...

A reading list on Microservices Architecture

When I wanted to dive into and understand Microservices Architecture the following reading list was suggested to me: Life beyond Distributed Transactions:an Apostate’s Opinion by Pat Helland This paper explores and names some of the practical approaches used in the implementations of large-scale mission-critical applications in a world which rejects distributed transactions. It discusses the management of fine-grained pieces of application data which may be repartitioned over time as the application grows. It also discusses the design patterns used in sending messages between these repartitionable pieces of data. Migrating to Microservices by Adrian Cockcroft In this presentation Adrian Cockcroft discusses strategies, patterns and pathways to perform a gradual migration from monolithic applications towards cloud-based REST microservices. Idempotence Is Not a Medical Condition by Pat Helland An essential property for reliable systems. Distributed systems theory for the dis...