Please enable JavaScript.
Coggle requires JavaScript to display documents.
Use Case Realization, Multi-Layer, Design Patterns, Packaging Design…
Use Case Realization
Interaction Diagrams
Communication Diagram
-
-
Components
-
Object: instantiated class object, sends/receive messages.
-
-
-
-
Sequence Diagram
-
-
-
-
Assumptions
-
-
-
Separation of Concerns
All classes has a primary focus such as UI, DAO and domain classes
Any classes that are listed in either the preconditions or postconditions of a use case should be included in the design
Other classes to include are those that are created, updated and provide information used in the use case.
Return values and passed parameters from messages can be parameters but they may also be objects from classes
-
Multi-Layer
-
-
-
-
-
-
Data access is not always required but recommended for each domain class, add a data access class to get and save data about an instance.
-
-