Notice the similarity of the notation for both deployment and component diagrams. Deployment diagrams are reasonably simple models that are used to show how the hardware and software units will be configured and deployed for an application. For each component of a deployment diagram, you'll want to document the applicable technical issues such as the required transaction volume, the expected network traffic, and the required response time. Further, each component will be documented by a set of appropriate models. For example, the databases will be described with data models, the application server will be described with a component diagram or class diagram, and the customer service screens will at least be documented by an interface-flow diagram and a prototype.
Some objects do and know more things, or at least more complicated things, than other objects.
Some objects are incredibly complex, so statechart diagrams are drawn to describe how they work, as shown in Figure 6. A Statechart Diagram for a Bank Account Figure 6 shows the statechart diagram for a bank account. The rectangles represent states that are stages in the behavior of an object. States are represented by the attribute values of an object. The arrows represent transitions, which are progressions from one state to another and are represented by the invocation of a method on an object class.