I see how this is simpler than UML, and ostensibly how it's useful for planning systems. With a bit of cleverness, it could also be generated from pre-existing code in certain languages.
It also touts the ability to facilitate going backwards from code to model, not just model to code. But I haven't ever read anything about how well it works in practice.
There is also a book, "Seamless Object-Oriented Software Architecture", that introduced the method and is supposed to be quite good.
Those have been in UML for years. (Google it.) Actually, that's the problem: everything is in UML. I am sure someone pointed out that "X" had it but UML didn't, so they made sure to add it.
BTW, a 20 year old link is not going to present anyone with up to date tech info. You have to make allowances for the progress of rival technology.
6 comments
[ 3.3 ms ] story [ 22.6 ms ] threadWhy have I not heard of this before?
There is also a book, "Seamless Object-Oriented Software Architecture", that introduced the method and is supposed to be quite good.
All those "round trip" model to code, code to model promises were a bust. And this article from the late 90s--talk about stale ideas.
BTW, a 20 year old link is not going to present anyone with up to date tech info. You have to make allowances for the progress of rival technology.