M.2 Additional Diagram Types
The following are the seven diagram types that we chose not to use in our Software Engineering Case Study.
Object diagrams model a “snapshot” of the system by modeling a system’s objects and their relationships at a specific point in time. Each object represents an instance of a class from a class diagram, and there may be several objects created from one class. For our ATM system, an object diagram could show several distinct
Accountobjects side by side, illustrating that they’re all part of the bank’s account database.Component diagrams model the artifacts and components—resources (which include source files)—that make up the system.
Deployment diagrams model the runtime requirements of the system (such as the ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access