UML Assignment
Carefully read our customers description of the project (also posted at Blackboard under Project Resources | Product Owner Documents). Then create two UML diagrams:
Use case diagram: There should be two actors in your diagram, Patient and Clinician. There is no need to have <
Class diagram: Your diagram should have classes (three-part boxes) and lines showing relationships between classes. Attempt to show the type of relation (inheritance, aggregation, etc.) and any directionality of the relationship, but do not be concerned about showing multiplicity (number of objects in the relationship). In addition to the textbook, Wikipedia has a reasonably succinct description of the types of relationships in UML class diagrams. Each class box should, to the extent possible, list the names of appropriate properties (instance variables) and methods for the class. Regarding level of detail, my diagram has eight classes, 20 or so properties, and five methods. I made some assumptions and decided to introduce some subclasses to reach this level of detail. Your diagram can have somewhat fewer classes and properties/methods and still receive full credit for detail. But a diagram with just a couple of classes and properties will not receive a good detail grade. Since this is a design diagram, the idea is to use the customer description as a guide to the required features, but to also add some of our own thinking about how the features might best be implemented.
You can draw your diagrams by hand and submit a scan/photo at Blackboard. Alternatively, there are free online tools that can be used to generate UML diagrams. I used draw.io (www.draw.io). If you use an online tool, you should save the drawing as a PDF and submit that (or a screenshot, if PDF generation is difficult/impossible for some reason).
The deadline for this assignment is 11:00 a.m. Friday, not noon. This is because I plan to make all of your submissions publicly available on Friday so that in class we can review them, decide what approaches seem best, and attempt to as a class develop consensus diagrams.
Grading
(5 pts) Use of UML vocabulary
o Attempt to use appropriate symbols for, e.g., relationship ends o Correct semantic use of symbols
(5 pts) Appropriate level of detail
(5 pts) Coherence of the diagrams
o Internally (elements within a single diagram) o Between the two diagrams
o With the customers description of the project
Only logged in customers who have purchased this product may leave a review.
Reviews
There are no reviews yet.