On most companies the UML is a fairy tale. Their employees are required to know it but they never get to use it.
This happens because on small and medium business the complete and traditional usage of UML becomes an enemy when you realize that no one know it well enough to apply it in their process. And even if there is an specialist on UML the fact of using it would increase de development time. An important detail which is not easily accepted by the project managers.
Considering the fact above some members of the development team on these companies ask themselves: Should I use the UML?
The answer to that leads to another question: Are you using it correctly?
Unless you have a development process based on generate code from UML diagrams (otherwise UML usage should not be a problem for you) you should consider start using the UML to your own benefit.
You can do that using the diagrams, concepts and resources from UML the way you think is best for you. It does not matter if you mixed diagrams (even if you mix UML diagrams with workflow diagrams) or if you mix its symbols on a specific diagram. As long as you and your team understand it well it's ok to use it.
Make sure your diagrams show clearly whatever you want to represent. It does not matter if is a business rule, a workflow, development stages or even all together.
On this scenario, don't forget that a diagram is only a representation of what is still to be documented.
Don't get me wrong. If you know how to use the UML and your job demands it usage in the traditional way you should do it so.
No comments:
Post a Comment