Add a comment

 

Re: The delivery mechanism is an annoying detail

For me, one of the most important uses of models is communicating over time. The need for communication only ends when all development on a system ends. And I don't particularly believe in separating "development" and "maintenance" (the latter is were most of the effort is, anyway!)

Even when a lot of effort is focused on producing good code, too many programming details have to be mixed in to allow the code to communicate overall system design and architecture well enough. Good models can do that -- as long as they do stay in sync with the code. You can do that through process discipline or tooling support -- or even by making your models executable so they become the code.

But if you can't keep your models in sync and they end up communicating the wrong information, then that's worse than not having them.


Re: The delivery mechanism is an annoying detail


Title
Body
HTML : b, strong, i, em, blockquote, br, p, pre, a href="", ul, ol, li, sub, sup
Name
E-mail address
Website
Remember me Yes  No 

E-mail addresses are not publicly displayed, so please only leave your e-mail address if you would like to be notified when new comments are added to this blog entry (you can opt-out later).