UML notations are the most important elements in modeling. Efficient and appropriate use of notations is very important for making a complete and meaningful model. The model is useless, unless its purpose is depicted properly.
Hence, learning notations should be emphasized from the very beginning. Different notations are available for things and relationships. UML diagrams are made using the notations of things and relationships. Extensibility is another important feature which makes UML more powerful and flexible.
The chapter describes basic UML notations in detail. This is just an extension to the UML building block section discussed in Chapter Two.
Structural Things
Graphical notations used in structural things are most widely used in UML. These are considered as the nouns of UML models. Following are the list of structural things.
Classes
Object
Interface
Collaboration
Use case
Active classes
Components
Nodes
UML은 다이어그램 표기법으로 유명합니다. UML은 소프트웨어 및 비 소프트웨어 시스템의 구성 요소를 시각화하고, 지정하고, 구성하고 문서화하기위한 것입니다. 따라서 시각화는 이해되고 기억되어야 할 가장 중요한 부분입니다.UML 표기법은 모델링에서 가장 중요한 요소입니다. 완벽하고 의미있는 모델을 만들기 위해서는 표기법을 효율적이고 적절하게 사용하는 것이 매우 중요합니다. 이 모델은 그 목적이 적절하게 묘사되지 않는 한 쓸모가 없다.그러므로 학습 표기법은 아주 초기부터 강조되어야합니다. 사물과 관계에 대해 다른 표기법을 사용할 수 있습니다. UML 다이어그램은 사물과 관계의 표기법을 사용하여 작성됩니다. 확장 성은 UML을보다 강력하고 융통성있게 만드는 또 다른 중요한 기능입니다.이 장에서는 기본 UML 표기법에 대해 자세히 설명합니다. 이것은 제 2 장에서 논의 된 UML 빌딩 블록 섹션의 확장 일뿐입니다.구조적 것들구조적으로 사용되는 그래픽 표기법은 UML에서 가장 널리 사용됩니다. 이들은 UML 모델의 명사로 간주됩니다. 다음은 구조적인 것들의 목록입니다.
수업
목적
인터페이스
협동
유스 케이스
활성 수업
구성 요소
노드
Class Notation
UML class is represented by the following figure. The diagram is divided into four parts.
The top section is used to name the class.
The second one is used to show the attributes of the class.
The third section is used to describe the operations performed by the class.
The fourth section is optional to show any additional components.
클래스 표기법
UML 클래스는 다음 그림으로 표현됩니다. 다이어그램은 네 부분으로 나뉩니다.
맨 위 섹션은 클래스의 이름을 지정하는 데 사용됩니다.
두 번째 클래스는 클래스의 속성을 표시하는 데 사용됩니다.
세 번째 섹션은 클래스가 수행 한 작업을 설명하는 데 사용됩니다.
네 번째 섹션은 추가 구성 요소를 표시하기 위해 선택 사항입니다.
Classes are used to represent objects. Objects can be anything having properties and responsibility.
클래스는 객체를 나타내는 데 사용됩니다. 객체는 속성과 책임이있는 모든 것이 될 수 있습니다.
객체 표기법
객체는 클래스와 같은 방식으로 표현됩니다. 유일한 차이점은 아래 그림에서와 같이 밑줄 친 이름입니다.
As the object is an actual implementation of a class, which is known as the instance of a class. Hence, it has the same usage as the class.
객체는 클래스의 인스턴스로 알려져있는 클래스의 실제 구현이므로 따라서 클래스와 동일한 용도로 사용됩니다.
Interface is represented by a circle as shown in the following figure. It has a name which is generally written below the circle.
인터페이스는 다음 그림과 같이 원으로 표시됩니다. 일반적으로 서클 아래에 쓰여지는 이름이 있습니다.
Interface is represented by a circle as shown in the following figure. It has a name which is generally written below the circle.
Interface Notation
Interface is used to describe the functionality without implementation. Interface is just like a template where you define different functions, not the implementation. When a class implements the interface, it also implements the functionality as per requirement.
Collaboration Notation
Collaboration is represented by a dotted eclipse as shown in the following figure. It has a name written inside the eclipse.
Collaboration Notation
Collaboration represents responsibilities. Generally, responsibilities are in a group.
Use Case Notation
Use case is represented as an eclipse with a name inside it. It may contain additional responsibilities.
Use case Notation
Use case is used to capture high level functionalities of a system.
Actor Notation
An actor can be defined as some internal or external entity that interacts with the system.
Actor Notation
An actor is used in a use case diagram to describe the internal or external entities.
Initial State Notation
Initial state is defined to show the start of a process. This notation is used in almost all diagrams.
Initial state Notation
The usage of Initial State Notation is to show the starting point of a process.
Final State Notation
Final state is used to show the end of a process. This notation is also used in almost all diagrams to describe the end.
Final state Notation
The usage of Final State Notation is to show the termination point of a process.
Active Class Notation
Active class looks similar to a class with a solid border. Active class is generally used to describe the concurrent behavior of a system.
Active class Notation
Active class is used to represent the concurrency in a system.
Component Notation
A component in UML is shown in the following figure with a name inside. Additional elements can be added wherever required.
Component Notation
Component is used to represent any part of a system for which UML diagrams are made.
Node Notation
A node in UML is represented by a square box as shown in the following figure with a name. A node represents the physical component of the system.
Node Notation
Node is used to represent the physical part of a system such as the server, network, etc.
Behavioral Things
Dynamic parts are one of the most important elements in UML. UML has a set of powerful features to represent the dynamic part of software and non-software systems. These features include interactions and state machines.
Interactions can be of two types −
Sequential (Represented by sequence diagram)
Collaborative (Represented by collaboration diagram)
Interaction Notation
Interaction is basically a message exchange between two UML components. The following diagram represents different notations used in an interaction.
Interaction Notation
Interaction is used to represent the communication among the components of a system.
State Machine Notation
State machine describes the different states of a component in its life cycle. The notations are described in the following diagram.
State machine Notation
State machine is used to describe different states of a system component. The state can be active, idle, or any other depending upon the situation.
Grouping Things
Organizing the UML models is one of the most important aspects of the design. In UML, there is only one element available for grouping and that is package.
Package Notation
Package notation is shown in the following figure and is used to wrap the components of a system.
package Notation
Annotational Things
In any diagram, explanation of different elements and their functionalities are very important. Hence, UML has notes notation to support this requirement.
Note Notation
This notation is shown in the following figure. These notations are used to provide necessary information of a system.
Note Notation
Relationships
A model is not complete unless the relationships between elements are described properly. The Relationship gives a proper meaning to a UML model. Following are the different types of relationships available in UML.
Dependency
Association
Generalization
Extensibility
Dependency Notation
Dependency is an important aspect in UML elements. It describes the dependent elements and the direction of dependency.
Dependency is represented by a dotted arrow as shown in the following figure. The arrow head represents the independent element and the other end represents the dependent element.
Dependency Notation
Dependency is used to represent the dependency between two elements of a system
Association Notation
Association describes how the elements in a UML diagram are associated. In simple words, it describes how many elements are taking part in an interaction.
Association is represented by a dotted line with (without) arrows on both sides. The two ends represent two associated elem
댓글 없음:
댓글 쓰기