SCEA之路--3. UML

Elements Used in UML
Class
As mentioned, a class is any uniquely identified abstraction that models a single thing, and the term object is synonymous with instance. Classes have attributes and methods.

Interface
An interface is a collection of operations that represent a class or that specify a set of methods that must be implemented by the derived class. An interface typically contains nothing but virtual methods and their signatures.

Package
A package is used to organize groups of like elements.

Collaboration
Collaboration defines the interaction of one or more roles along with their contents, associations, relationships, and classes.

Use Case
A use case is a description that represents a complete unit of functionality provided by something as large as a system or as small as a class. The result of this functionality is manifested by a sequence of messages exchanged among the system (or class) and one or more outside actors combined with actions performed by another system (or class).
There are two types of use cases: essential and real. Essential use cases are expressed in an ideal form that remains free of technology and implementation detail. The design decisions are abstracted, especially those related to the user interface. A real use case describes the process in terms of its real design and implementation. Essential use cases are important early in the project. Their purpose is to illustrate and document the business process. Real use cases become important after implementation.

Component
The component represents a modular and deployable system part. It encapsulates an implementation and exposes a set of interfaces. The interfaces represent services provided by elements that reside on the component. A component is typically deployed on a node.

Node
The node is a physical element object that represents a processing resource, generally having memory and processing capability—such as a server.

State
The state is a condition that can occur during the life of an object. It can also be an interaction that satisfies some condition, performs some action, or waits for some event.

Relationship in UML
Generalization (aka Inheritance) A specialized version of another class Solid line with a closed arrowhead pointing to the more general class

Association Uses the services of another class Solid line connecting the associated classes, with an optional open arrowhead showing direction of navigation.

Aggregation A class “owns” another class A form of association with an unfilled diamond
at the “owner” end of the association

Composition A class is composed of another class; refers to an aggregation within which the component parts and the larger encompassing whole share a lifetime A form of aggregation, shown with either a filled diamond at the? “composite” end, or with the composite graphically containing the “component”

Refinement A refined version of another class; refinement within a given model can be shown as a dependency with
the stereotype < > or one of its more specific forms, such as < > Dashed line with a closed hollow arrowhead pointing to the more refined class

Dependency A class dependent on another class. Dashed line with an open arrowhead pointing
to the dependency.

Diagrams in UML

Use Case Diagram

Class Diagram

Package Diagram

State Diagram

Activity Diagram

Sequence Diagram

Collaboration Diagram

Deployment Diagram