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

Going through the numbers: what kind of scope can your agile delivery platform handle anyway?

Today a manager asked what kind off scope and effort the Accelerated Delivery Platform could handle on a project expressed in function points. I find this a very odd question and I have always been resilient to function point analyses as an estimation technique which tries to best guess the end state of a software solution based on and determine by the number of interfaces, screens, reports etcetera. Often this happens upfront at a point in time there is only a vague idea for a perceived solution for specific problem which still needs to be analyzed in detail. Very old school thinking if you would ask me, which is not helpful for providing agile ICT support for business development and transformation. Asking for the ADP platform’s project delivery capabilities expressed in scope and effort is a weird measure for suitability for a software development platform. Given infinite time any scope and effort can be handled by any approach. But then again every project is always about time and