Steve > What would you describe as the "objects" in a military scenario who > state determines the next step? I'd have a similar questions in other > scenarios (e.g. American Footbal coaching with its fixed plays called > from the side lines).
I'm afraid I don't know. But these were your examples, not mine. I was thinking of situations involving things like orders, claims, resources, projects, mandates, cases, etc. These kind of things have data and state associated with them. > Controlled action is sometimes required, this requires very specific > modelling and messaging approaches and very strict compliance > procedures. This isn't something that is needed all the time but my > point was that one size doesn't fit all. I agree. One size doesn't fit all. > Fair enough then I mis-read it, but the paper is extremely technical > in nature, and you did say its as technical as a "class diagram" > (which IMO is technical). I said "domain model class diagram", by which I meant a depiction of the types of object in the business. I don't regard this as "technical", in the sense of being related to any particular kind of IT based solution. > The key question therefore is what real business scenario would this > work for, and to answer this you need something that works at a > higher level of abstraction. I didn't really understand this. Can you elucidate? Rgds Ashley
