Over years I have seen developers do things backward. For example decades ago I have seen folks do flow charts after the code was developed and tested. Never quite understood why. In today’s world of agile development using “use cases” is a very acceptable form of defining user requirements that is visual and can be easily understood by business analysts and even management.
Have you encountered a situation where you have spent more than a few minutes trying to come up with graphical use case diagrams to represent your requirements? I have been guilty of that and pondered about it and reached out to a UML reference book to understand if there is anything I can do to make it faster and more right.
The answer my friends is pretty simple: It is very important to first write a use case text based description of the requirement before trying to come up with the use case diagram. Most of us jump the gun and try to forget this very basic step.
Do write and let us know if you have been encountered this. Have you done anything differently to make it faster for you and your team to come up with use case diagrams ?