Sep 14, 2005 5:41:55 PM |
Package Summary | |||
![]() |
|||
![]() |
|||
![]() |
The Problem Domain diagram is where business-level classes reside. | ||
![]() |
This top-level requirements diagram is used to help readers walk through the various requirements artifacts available for review. | ||
![]() |
This is the initial analysis model. | ||
![]() |
|||
![]() |
|||
![]() |
Package Diagram Summary | |||
![]() |
|||
![]() |
This is the initial analysis model. | ||
![]() |
|||
![]() |
The Problem Domain diagram is where business-level classes reside. | ||
![]() |
This top-level requirements diagram is used to help readers walk through the various requirements artifacts available for review. | ||
![]() |
|||
![]() |
|||
![]() |
Class Diagram Summary | ||
![]() |
This diagram is designed to highlight the overall simple architecture of: | |
![]() |
The Object Diagram can help unwind what the state of the system might look like in a specific scenario. | |
![]() |
This diagram is used to show new users how to navigate through the Cash Sales example. | |
![]() |
This logical diagram walks you through the architectural views. |
Use-Case Diagram Summary | ||
![]() |
This use case documents the requirements for how the system needs to make a sale. | |
![]() |
This is the next level of information for a higher-level use case. |
Component Diagram Summary | ||
![]() |
The Component Diagram can be used to help lay out the various parts of the system; their components, and the inerfaces that are supported and used. |
Sequence Diagram Summary | |||
![]() |
This sequence diagram was generated automatically by Together based on existing source code. | ||
![]() |
|||
![]() |
|||
![]() |
This sequence diagram illustrates how a product is scanned and priced. | ||
![]() |
Collaboration Diagram Summary | |||
![]() |
Robustness Diagram Summary | ||
![]() |
A sample robustness diagram. |
ER Diagram Summary | ||
![]() |
Here is the schema for the Cash Sales system. |