By splitting compound roles your models will provide a clearer and more representative picture of who does what and when.
Simplifying is a hot topic, but Robert Maksimchuk submits that we are already simplifying the UML in our respective projects through self-selection.
Use case maturity depends on a detailed elaboration of your plan.
The UML is not just a great tool for requirements elicitation, analysis and design: it also can help the project manager to effectively plan and direct the development cycle.
Communicating clearly what the business wants and how the requirements stack up are critical for project success.
Avoid overuse and misuse of the "include" and "extend" relationships.
Misconceptions include: UML is only for software development and if you use it, you automatically get software reuse.
Using a common language is about facilitating the team -- resist the urge to create the next Tower of Babel.
Welcome to DevX's new series on the Unified Modeling Language, where we get back to basics and help make modeling more practical and useful for you.
Like the frequent complaint on summer road trips, some software development shops are eager to wear agile development as a badge.