Steve Thanks for your comments.
> In most organisations I've worked with there is either a controlling party > who dictates > the steps, a co-ordinating party who gets people to do things or the process > is based > on a routing decision in the last received point, this might be based on > information > contained but most of the rules are external to that information/object and > are based > on the service/person that is currently in control of the process. I think if there is "a controlling party" then you are probably not going to use the kind of approach I suggest. You need a "script" for the controlling party. However, I would have to ask whether things are organised this way "in most organisations" because it is the most efficient way of doing things from the business point of view, or because current approaches make a more decentralised approach to business processes difficult to achieve? > But is the solution really to start with a technology implementation approach > or to move away from that towards a more abstract modelling approach that > helps > us to understand the business and then decide on the correct implementation > strategy? I hope you don't think what I am advocating is a "technology implementation approach" because, whatever else it may be, it is not that! This is a "pure" modelling technique, at least as "pure" as a domain model class diagram. > One size won't fit all but there isn't much effort being put into approaches > that help decide > the right way, currently there are lots of people proposing their "one way". I agree. The ideas I am proposing are a contribution to the mix and not a panacea. The question you raise (how to decide which is the right way) is key. But I guess you have to know what the alternatives are before you decide how to choose between them. Rgds Ashley
