THE MAGAZINE FOR COMPUTER APPLICATIONS
Circuit Cellar Online offers articles illustrating creative solutions
and unique applications through complete projects, practical
tutorials, and useful design techniques.

UML IN A PRODUCTýS LIFE CYCLE

by Venu Kosuri

Start ý Basic Views ý The Whole Picture ý Use Case View ý Use Case Diagram ý Structural View ý Domain Modeling ý Class Diagram ý Behavioral View ý Sequence Diagram ý Collaboration Diagram ý FSM ý Scalability Limitations ý Lack of Support ý State Charts ý Activity Diagram ý Implementation View ý Environmental View ý Sources and PDF

IMPLEMENTATION VIEW

After domain classification, it is necessary to break the domain into components so that they can be implemented. Here, each component groups a set of activities to fulfill certain requirements of the domain.

For example, driver components provide the interface for the underlying hardware. Each component depends on some other components of the same domain or external domain. External domain communication is already captured in domain communications (i.e., bridge). All internal as well as external communications of a component can be specified in terms of protocols. Each protocol specifies a specific communication. Usually a component diagram captures this information (see Figure 10).

Figure 10ýThis is a basic MPEG encoder. A rectangular box indicates a component. The connecting lines with open (not darkened) or closed (darkened) rectangles show protocols.

PREVIOUS • NEXT