Professional Documents
Culture Documents
toolate!
PostedinProjectManagementtagged4UMLdiagramsat2:08pmbyMolly
UMLUnifiedModellingLanguage
Why?Tocommunicateandunderstandatthesamelevel.Why?Toavoidmisconceptions!
CLASSDIAGRAMS
capturestaticrelationshipsofsoftware
capturethephysicalstructureofasystem
understandwhatclassesreferenceotherclasses
understandwhichclassownsanotherclass
aCLASSrepresentsagroupthathascommonstatesandbehaviours
theRELATIONSHIPSinclude:dependencies,associations,aggregations,compositions,generalisations,
associatedclassesandassociatedqualifiers.
classdiagramexample
USECASEDIAGRAMS
captureanddefinefunctionalrequirements
auserstoryandausecasedescribeONETHINGONLYthatthesoftwareneedstodo.
usecaseexample
ACTIVITYDIAGRAMS
thehowdoessomethingtosomethingelse
derivedfromworkflowsandflowcharts,becausetheylookverysimilar
definesthebehaviourofthemodelbeingdescribed.
activitydiagramexample
SEQUENCEDIAGRAMS
definesobjectinteractionatruntimetobringsoftwarefunctionalitytolifeinanexecutedorder/sequence
usedfordynamicmodelling.
sequencediagramexample
USECASENARRATIVES(nondiagram,textonly)
usedtodescribetheusecaseinmorenarrativeterms
contains:usecasename,iteration,summary,preconditions,triggers,courseofeventsalternatepaths
postconditionbusinessrulesnotesauthor&date.