Automated home: Applying Interaction Design on DSLshttp://savelkoul.net/cs/blogs/antoine/archive/2009/10/03/automated-home-applying-interaction-design-on-dsls.aspxIn my previous posts I have given an impression of the current situation (how the hardware is connected, which software I use). It is very tempting to dig into hardware and software details now, but during previous experiences with designing DSLs I learnedenCommunityServer 2.1 SP2 (Build: 61129.2)re: Automated home: Applying Interaction Design on DSLshttp://savelkoul.net/cs/blogs/antoine/archive/2009/10/03/automated-home-applying-interaction-design-on-dsls.aspx#216Thu, 08 Oct 2009 09:16:57 GMTc85263ac-6350-4393-b21e-03dd809752eb:216Steven Kelly<p>Hi Antoine,</p> <p>You wrote: &quot;A lot of papers and articles about designing DSLs will start with an analysis of the PROBLEM DOMAIN by discussing complete hardware designs and software architectures&quot;</p> <p>I guess you meant &quot;solution domain&quot;: the domain of the concepts, tools, libraries, programming languages and platforms of a developer building a system by coding it.</p> <p>The problem domain is the user's or domain expert's view of the system, precisely the area you talk about in the rest of your post, and by far the best place to look when building a DSM language. </p>