documentation - Do you use UML in Agile development practices? -
it feels artifacts of earlier days, uml sure have use. however, agile processes extreme programming advocates "embracing changes", means should make less documents , uml models well? since gives impression of setting in stone.
where uml belongs in agile development practice? other preliminary spec documents, should use @ all?
edit: found this: potential artifacts agile modeling
breeze through robert martin's agile principles, patterns , practices
- the suggestion use uml communicate designs within team.. shared language ; taking @ diagram can understand solution (faster talking it) , contribute quicker.
- if find team making same diagrams on , on again, make version , store on wiki / source control. overtime the more useful diagrams start collate in place.
- don't spend time on it... don't need detail. models built in architectural / construction realms because building house validate-test design expensive/infeasible. software not - validate design coding in time make uml model of untested design (with bells , whistles).
so says unclebob... concur.
Comments
Post a Comment