We are featured in two top-tier journals this week. First, Charles is the subject of the InformationWeek “High Five” interview written by Nick Hoover. We especially like Nick’s description of our goals here at Intentional Software, “… aims to commercialize a new form of software development that allows line-of-business employees to help write programs.” 

We want to put the emphasis here on the word “help”. The Intentional Software approach gives line-of-business employees, or, as we like to call them, domain experts, an active role in software creation. But, there is still a vital role for programmers as they must provide the necessary software programming know-how to ultimately deliver the end-user software.

In the second piece, published in Business 2.0 magazine, and on-line by CNN Money, Michael Myser delves deeper into the specifics. The article says that we are making software that “will write its own code.” To be sure, there is a high level of automation as the Intentional Software approach features a heavy dose of code generation. There is still plenty of work for programmers to create these domain specific generators to generate correct code. But it’s higher level work, we believe, avoiding the drudgery of endless  requirement changes.

The analogy to blog software is a good one. Before blog software, anyone who published on the web had to edit HTML code. With blog software, millions of users can now simply use a text editor to author and push a PUBLISH button to publish on the web, correctly and nicely formatted. The PUBLISH button essentially invokes a code generator that integrates the blog text into HTML code that makes up the blog website. Similarly the Intentional Domain Workbench includes an editor domain experts use to edit, in their domain language, and then “just” press a button to invoke the code generator.

Further down in the piece, “Intentional is making software so smart that you can simply tell it what you want to do. Lay down a few basic parameters, and it will write its own code. No programming skills are necessary” might be the view from the domain experts. With Intentional Software, domain experts play a vital role at the front-end of the process when they define their problem in a domain language. But, skilled programmers build a generator that becomes the “engine” to provide interpretations of the domain language. The result is a more flexible, efficient way of creating software. It’s an approach that, we believe, will accelerate innovation within the enterprise by focusing domain experts and programmers on the area of their interest and expertise.

Later, Mike makes this point himself, “Intentional users must still have a software engineer on hand…”  And, our early pilot user, Henk Kolk of Capgemini gives an excellent description based on their work with the Intentional Domain Workbench.

Check out the articles! And thanks to both InformationWeek and CNN Money/Business2.0 for these inside looks at Charles and Intentional Software.

Share →

4 Responses to Intentional Software In The News

  1. Peter Bell says:

    Congratulations on the coverage. A release date at last? I can’t wait – gonna be an exciting fall :->
    http://www.pbell.com/index.cfm/2007/8/29/Intentional-Software-Starts-to-Share

  2. Are there any opportunities still available to be a beta tester?
    I would love to have my guys working on VIOPSYS – Vision Operating System http://www.viopsys.com take a shot at some development utilizing Intentional Software
    Thanks!

  3. Intentional Strategic Modeling, Part 1

    While poking around the web for info on domain-specific modeling, I came across this blog post about Charles Simonyis latest venture, Intentional Software. Simonyi is widely acknowledged as the father of the WYSIWYG word processor (something we …

  4. Dave Dixon says:

    There are interesting parallels/synergies between intentional software and strategic modeling. Intentional software makes it easier for someone to tell information systems what to do, i.e. how to execute a strategy, with an abstraction level which is closer to the way a person thinks about it.
    In strategic modeling, you’re trying to figure out what you should do, based on current information. The technical difficulties are similar, because modeling in a platform like Excel creates a lot of opportunities for mistakes and corner-cutting. Poor abstraction strikes again.
    Why not merge these two tasks? Instead of providing instructions on what to do, you provide your decisions and other information (or instructions on how to obtain info, e.g. from a data warehouse). Decisions translate to actions, and you provide further info on how a choice is executed on your information systems. Solution of the model provides optimal choices based on current info, and then the software performs the actions associated with those choices.
    So not only do you get higher quality software, you simultaneously get a better strategy.
    I blogged on this here: http://blog.provisdom.com/?p=8