In doing some research online, I re-read a post by Paul Hartley (Intentional Software) that brought up Use Cases.
His basic premise is that the practice of law specifically relating to the drafting of contracts is very similar to the practice of software engineering in the implementation of code. This seems like one of those things that should be obvious, seeing as how we use the word contract to describe interface relationships often enough. Once you've finished the article however, it's obvious that the challenges extend beyond just component interactions.
Specifically, his illustrations in how Use Cases are a tool to help in both practices were enlightening. I now have yet another tool when explaining the value and approach for Use Cases.
Post a Comment