uml - Difference between a 'class diagram' and a 'design class diagram' -
i have assignment states following criteria:
for view may use truncated version of design class diagram (dcd) including architecturally significant classes.
for context, logical view of 4 + 1 architectural view. how design class diagram (dcd) differ regular class diagram? uml diagram without functions or variables included (i.e. names of classes , interactions each other)?
most of time, people model code. that's good! in case, class diagram modeling used graphically represent structure of (object-oriented) classes: class, method, attribute, annotations stereotypes. imagine jpa, spring, whatever annotations in class diagram of jpa-j2ee based architecture...
as it's said above, "design class diagram" should design domain model, architecture level. basic entities structural system rely on? no details programming language, no "dto", "dao" or technical stuff that. here's example use: online shopping cart domain model. contains architecturally significant classes.
hth, tom
Comments
Post a Comment