Use Cases for Process and Product
Posted by Kirk on December 17, 2007
What if we took a use-case approach to defining our design and dev processes? Would that give us a different perspective of how we would like to work?
Sometimes a use-case needs to be documenting in text. Other times a workflow does the best. And in still other cases, would a prototype be more appropriate? When something is very well understood, do you need to textually define it or can you just build it?
A nomenclature (meta data) for a use case seems also to be a needed thing. Some are very finite others are at a high level. Some are self contaned (can be completed in one-sitting) others are extended across time and multiple steps.
Use-cases should be able to be used for products as well as software. Anything requiring user-interaction, could use use-cases as a tool.
Thoughts?
