http://abstratt.com/blog/2007/03/31/where-we-are-coming-from-part-i/ A company obsessed with one single goal: stopping people from writing so much code Wed, 08 Sep 2010 17:55:47 +0000 http://wordpress.org/?v=2.5.1 http://abstratt.com/blog/2007/03/31/where-we-are-coming-from-part-i/#comment-572 Where we are coming from - Part II | abstratt: news from the front Mon, 24 Nov 2008 07:59:27 +0000 http://abstratt.com/blog/2007/03/31/where-we-are-coming-from-part-i/#comment-572 [...] development industry, and how we plan to fix it. If you haven’t done it yet, read the first post [...] [...] development industry, and how we plan to fix it. If you haven’t done it yet, read the first post [...]

]]> http://abstratt.com/blog/2007/03/31/where-we-are-coming-from-part-i/#comment-571 Where we are coming from - Part III | abstratt: news from the front Mon, 24 Nov 2008 07:59:08 +0000 http://abstratt.com/blog/2007/03/31/where-we-are-coming-from-part-i/#comment-571 [...] posts. In summary, we should strive for addressing concerns as independently as possible (points #1 and #2), and that depending on the dimension (point #3) the concern lives in we should deploy the [...] [...] posts. In summary, we should strive for addressing concerns as independently as possible (points #1 and #2), and that depending on the dimension (point #3) the concern lives in we should deploy the [...]

]]> http://abstratt.com/blog/2007/03/31/where-we-are-coming-from-part-i/#comment-569 Platform independence in MDA | abstratt: news from the front Mon, 24 Nov 2008 07:58:36 +0000 http://abstratt.com/blog/2007/03/31/where-we-are-coming-from-part-i/#comment-569 [...] MDA promotes platform-independence by adopting a design-centric approach. Models are removed from implementation related concerns and thus are inherently platform independent: a single design can be reused for building the same system for multiple target platforms. The implementation details are taken care of by target platform specific templates. The templates are applied to the user models then generating concrete platform-specific artifacts (running code, documentation, database schema, configuration files). Differently from Java (even if Martin Fowler says so), MDA does not promote another platform. What it does is to promote a clear separation between problem domain concerns and implementation concerns (as covered before here in the inaugural series entitled “Where we are coming from“). [...] [...] MDA promotes platform-independence by adopting a design-centric approach. Models are removed from implementation related concerns and thus are inherently platform independent: a single design can be reused for building the same system for multiple target platforms. The implementation details are taken care of by target platform specific templates. The templates are applied to the user models then generating concrete platform-specific artifacts (running code, documentation, database schema, configuration files). Differently from Java (even if Martin Fowler says so), MDA does not promote another platform. What it does is to promote a clear separation between problem domain concerns and implementation concerns (as covered before here in the inaugural series entitled “Where we are coming from“). [...]

]]>