I have added multiplicities, association name and roles and also gave considerate thought to both the attributes and operations of the classes depicted. Once I clarified the attributes and operations I had to then tweak the sequence diagram to ensure the operation names related to the class diagram, or more appropriately, that both diagrams related to the revised Data Dictionary for the project.
I reviewed the marking requisites for the blog; am I correct we do not have to provide a data dictionary? I may just because.
Here are the revised class and sequence diagrams:
Still to come for Green St. Car Park:
State Diagram
Activity Diagram
Ah! Data dictionary - should you provide one for the blog? Well, there is no explicit requirement - but working through the exercises you will all need to develop data dictionaries as part of the UML process. This is exactly your main point about UML, Helene, each method in the toolkit is dependent on the others and the bedrock of compatibility and consistency of terminology is an accurate and complete data dictionary. I'm confident that in the restaurant scenario you have all found that the data dictionary is vital to fitting the UML methods together into a well sysnthesised whole.
ReplyDelete