UML use some diagrams.
They are classified as follows.
- Structure Diagram
- Behabior Diagram
- Interaction Diagram
This can be classified more.
"Class Diagram"
Class is like "Car".
It is not specified.
I will consider it as an actual object.
It contains Name, Attriblute and Operation.
For example the car, Name is "Car"
Attribute is like "coler", "model" and so on..
Operation is like "to accel".
"Object Diagram"
Object is like "The First Car"
The difference with the Class is that Object can be specified.
"Component Diagram"
Component means one functional part of software.
or set which collects some classes and objects.
It can be identified with module, but component is often used in something large.
"Composite Structure Diagram"
??????
"Package Daiagram"
Object should belong to correct class.
Tokyo have to belong to Japan.
It is wrong Tokyo belong to Korea.
so, we have to express obviously how the object is packaged.
"Deployment Diagram"
This shows how the component or objects are arranged in the system.
We will also see the relation and the place the component work.
- Behavior Diagram -
"Use case Diagram"
Use case means what the actor can do in the system.
Actor is sometimes customer and anybody who influence the system.
"Activity Diagram"
This diagram shows the process which the component works in high level.
We often show how user acts in the process.
"State machine Diagram"
This diagram shows the transition of the state of the object in low level.
The object can be the system component and user interface, etc...
- Interaction Diagram -
Interaction Diagrams show the interaction among the objects
"Sequence Diagram"
This diagram shows also when the object act to the other object in the entire process of the system.
"Comunication Diagram"
This diagram shows especially how the objects relate and collaborate.
These are the UML diagrams.
When we model the system, we should use them.
That's it.
0 件のコメント:
コメントを投稿