Week 08 ToDos
1. Watch Lecture Videos
Watch the week 08 lecture videos in advance of your team meeting.
Lecture References:
See Resources→References for instructions on how to access lecture references.
- Craig Larman, Applying UML and Patterns, 3ed, Prentice Hall, 2004.
- Chapter 9: Domain Models
2. Specification Domain Model
Your team is to produce a (specification-level) Domain Model for your course project. Your Domain Model should include all of the Environmental Phenomena needed to describe the Requirements of your project (e.g., actors; adjacent systems; real-world entities, events, and information that are external to your system and that your system senses, tracks, controls, etc.), plus any Interface Phenomena (e.g., interface entities or devices of your system; or information that is shared between the system and the real world via the system’s interface, like inputs, outputs, accounts, records, input requests, notifications, reports, query results, and so on) and are used to describe the Specifications of your project. If your project is a cyber system, then the entities in your Domain Model are likely to be all (1) actors, (2) adjacent systems, and (3) interface information that are known by both actors/adjacent systems and your system. Whereas if your project is a cyber-physical system, then it is likely that your Domain Model has (1) actors, (2) adjacent systems, and (3) domain entities/information that reside in the real world and that can be sensed or controlled by the system only through introduced (4) interface devices (sensors, actuators).
As with the other models you have created this term, use a diagram or modelling tool like LucidChart to create your Domain Model. To help us understand your model, provide short descriptions of the entities in your model and provide a short description of each of the associations in your model. Put your Domain Model and supplementary descriptions in a PDF file named «TeamName»_D8.pdf and submit it to LEARN.
This week’s lectures include examples of non-trivial Domain Models for Olympic Tickets and Elevator. In addition, here is the Specification Domain Model and descriptions from the Modern Family project. The Modern Family domain model shows how to decompose a large domain model into separate mutually consistent sub-models, one for each use case – this makes sense if a domain model will be too small to be legible when displayed on a single page.
Grading Scheme: This writeup will be marked on the basis of (1) the Completeness and Correctness of your Domain Model, (2) its Level of Detail, (3) Adherence to Domain Model syntax and modelling conventions, and (4) descriptions of entities and relationships. Most marks will be associated with (1). See the Week 8 rubric for details.