I think the layering approach could work well. Indeed, it would really enable the models as a means of communication. If a model can be simple enough for the business to sign off, but descriptive enough to fill in the technical details the app or developer needs then we are talking about an ideal scenario. This would also allow project teams to pick and choose the approach they take on a project-by-project basis. Sometimes a quick and dirty model might be the way to go, where a concept needs to be quickly proved or disproved. On the other hand, on bigger projects it might be more appropriate to spend more time on the model, and ensure that communication between analysis and development teams is crystal clear. One caveat: I have seen situations where the delivery of a solution takes a back seat and modelling becomes an end in itself. Perhaps this is something that should be thought about as part of BPM project methodology rather than the notation, but it would be great if the notation could limit such extravagance. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992735#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...