Posts tagged as:

specification

How many degrees of separation are there between your developers and users?

July 15, 2009

James Governor of Redmonk shared a great tweet today (he is @monkchips)
@dhague: 6 degrees of separation between developers and end-users is 3 too many. It’s hard to keep users happy with that disconnect
Now here’s one way to think about the degrees of separation between your users and your developers:

Users tell an analyst what they want
The [...]

Read the full article →

RuleSpeak – some useful guidelines for writing rules

April 9, 2009

The folks at BR Solutions launched a new website that makes some of the RuleSpeak guideliness for writing good rules available for download at www.RuleSpeak.com. It offers basic RuleSpeak 2.0 guidelines in English, Spanish, German and (soon) Dutch. Ron Ross wrote an article about this in the April issue of the Business Rules Journal eUpdate.
I [...]

Read the full article →

Keeping business rules out of your use cases with decisions

April 2, 2009

Syndicated from ebizQ
Adrian Marchis had a nice article on Use Case Recycling by Extracting Business Rules. Now making sure decisions are identified explicitly in use cases avoids one of the seven deadly sins of decision management and is something I think is critical. Indeed I wrote an article on the topic on the same network [...]

Read the full article →

Decision Management and software development I – Agile

February 13, 2009

Last week I posted Focusing on decisions to improve the software end product and I decided that this week’s posts would be a series of follow-ups on how decision management can and should impact software development. Today on how it should impact/be a part of Agile, tomorrow on Model-Drive Engineering and Thursday on DSLs (Domain [...]

Read the full article →

If IT can’t get you there, perhaps decision management can

December 18, 2008

Dick Lee had an interesting post titled We Know Where We’re Going, But IT Can’t Get Us There. He made a number of points of which three stood out: Business often fails to communicate effectively to IT Poor process definition…

Read the full article →

First Look – Erudine Behaviour Engine

September 15, 2008

Erudine is a British company a few years old and has released some new technology in a new process context – the Erudine Behaviour Engine (yes, the British spelling). Like many technologies, Erudine is targeting the business-IT divide, focusing on problems like those of translating requirements into systems, integrating the expertise of lots of people [...]

Read the full article →

Scope <> Business Rules

April 24, 2008

Jeff Jonas wrote an interesting post – Custom Software Scope Changes (Not) – that reminded me of my ongoing battle to argue that rules are not requirements. Jeff argues that we take far too little time designing custom software before we start to build it. A summary quote from his post illustrates his point:
I am [...]

Read the full article →