By Peter Bell

A parable on Intent Driven Design

Interestingly, this blog posting's description of the "four benches" is a pretty good example of the iterative approach we use when implementing Intent Driven Design to figure out the requirements for a project. If you haven't already, check out the CFDJ article on the topic.

My Second CFDJ Article: On Simplifying the Specification Process.

There isn't much point in being able to generate an application in minutes if it still takes you months to specify it. Intent Driven Design is the process we use to simplify the process of iteratively developing functional specifications for moderately complex web applications.

It is optimized for UI heavy applications and we’ve found it to be a simple but lightweight way to go from business objectives through use cases to detailed functional requirements in a meaningful way. Of course, it isn’t a silver bullet and is heavily influenced by everything from use cases to feature driven development, but we’re getting great results with it over at SystemsForge. Check out the article and let me know what you think!

Right Sizing Your Use Cases

Although I haven't blogged about it much yet, about half of what we're working on at SystemsForge relates to improving the process of specifying applications. There is no point generating an application in a day if it still takes six months to specify what it should do!

I'll be posting more about our Intent Driven Design process later this year. In the meantime, I just caught a nice blog post on right-sizing user stories.

BlogCFC was created by Raymond Camden. This blog is running version 5.005.