Domain Model as UML Class Diagram with Superimposed World Diagram
for WUIM

• the information in the WUIM Project Vision Document,
• what you have learned for your Deliverable 1 domain model diagram,
• the criticisms you got on the Deliverable 1 diagram
• what you have learned for your Deliverable 2 list of assumptions, exceptions, variations and questions,
• what you have learned from the distributed list of assumptions, exceptions, variations and questions<,
• any updates to the vision document,
• what you have learned for your Deliverable 3 use case model, and
• any good ideas that come to your minds,

expressing it as a UML class diagram (see UML tools), as on page 21 of the slides for Classes & Concepts. Your classes are not required to have attributes or operations (methods) other than those corresponding to the use cases identified for your WUIM Use Case Model. That is, a box with only a class name suffices for most classes. Some classes will have operations for the use cases. If, since handing in your use case model, you have determined the need for other, i.e., additional or different, use cases, then you may show them in the appropriate places in the class diagram.

Then divide these entities into the environment and the system. Superimpose this division on to the UML-class-model-expressed domain model. You can do this superimposition by drawing a shape enclosing the environment entities and another shape enclosing the system entities; then label each shape as ENV or SYS as the case may be, as on page 21 of the slides for Classes & Concepts. Alternatively, you could just mark each domain model entity with ``ENV'', ``SYS'', or both, as the case may be, as on page 47 of the same slides.

If you have done this superimposition correctly, you should be able to see clearly which entities are in the interface.

The use case diagram and the class diagram should be consistent in that,

• Each actor in the use case diagram appears as a class with stereotype ``<<actor>>'' in the class diagram, and vice versa.
• Except for the other use cases mentioned above, each use case in the use case diagram should appear as an operation in a class in the class diagram, and vice versa.

You will need to submit both a hard copy AND and an electronic copy of this deliverable:

• The hard copy should be placed in the designated drop box for CS445/SE463.
• The electronic copy should be emailed to the course account with the subject "CS445 Deliverable 4 Group XX" where XX is your group number, with a leading zero if it's less than 10. The file name for the same deliverable should be "D4-GXX.pdf" where XX is your group number as before. PLEASE use this subject line and file name; otherwise it is difficult for us to organize all of the submissions. Deliverable 4 must be in PDF format.