4 ms·
I usually start with a pretty rough mental image of what I want, maybe draw a few rough sketches / diagrams / whatever on paper or on the whiteboard, then just
by mindcrime 16y ago
I usually start with a pretty rough mental image of what I want, maybe draw a few rough sketches / diagrams / whatever on paper or on the whiteboard, then just start building and let it evolve. Once I have enough built to feel comfortable showing it to people, I start showing it around and soliciting feedback.
As things evolve, I may start writing down use cases or capability cases on paper (well not literally paper, but an OO.org document or a text file, whatever.) And since all of the stuff I'm working on now (outside of $DAYJOB) is open source, this stuff usually winds up on a blog somewhere for the world to see. Here's an example of my first stab at using Capability Cases to describe something:
http://www.jroller.com/openqabal/entry/so_what_s_a_capability http://www.jroller.com/openqabal/entry/so_what_s_a_capabilit...
Note: I don't claim this "system" is the best - or even particularly good - it's just how I happen to work.