Modeling Different Views of a System

建模系統的不同檢視

When you model a system from different views, you are in effect constructing your system simultaneously from multiple dimensions. By choosing the right set of views, you set up a process that forces you to ask good questions about your system and to expose risks that need to be attacked. If you do a poor job of choosing these views or if you focus on one view at the expense of all others, you run the risk of hiding issues and deferring problems that will eventually destroy any chance of success.

當你從不同的視點為系統建模的時候，實際上是同時從多個維度上構建系統。通過選擇正確的檢視組建立一個過程，迫使你提出對系統有幫助的問題及免受不必要的攻擊風險。如果你沒有用心地選擇這些檢視或是在一張檢視上花費太多的時間，隱藏問題和拖延問題產生的風險最終會破壞任何成功的機會。

To model a system from different views,

nDecide which views you need to best express the architecture of your system and to expose the technical risks to your project. The five views of an architecture described earlier are a good starting point.

nFor each of these views, decide which artifacts you need to create to capture the essential details of that view. For the most part, these artifacts will consist of various UML diagrams.

nAs part of your process planning, decide which of these diagrams you’ll want to put under some sort of formal or semi-formal control. These are the diagrams for which you

nAllow room for diagrams that are thrown away. Such transitory diagrams are still useful for exploring the implications of your decisions and for experimenting with changes.

從不同的視點建模系統要注意：

n決定哪個檢視最適合表達你係統的架構，清楚專案中所使用技術存在的風險。想要有個良好的開端需要在早期對架構的五個檢視進行描述。

n對於這些檢視的每一個，你都需要決定建立哪個產品以捕獲這些檢視的基本細節。在大多數情況下，這五個產品將組合成各種UML圖。

n決定使用正式的圖還是非正式的圖是你程序規劃的一部分。那些正式的圖將會儲存成文件以便在今後的專案中回顧。

n允許會被丟棄的多餘的圖存在。這些臨時性的圖在探索決定和嘗試改變時還是很有用的。

For example, if you are modeling a simple monolithic application that runs on a single machine, you might need only the following handful of diagrams.

nUse case view

Use case diagrams

nDesign view

Class diagrams (for structural modeling)

nInteraction view

Interaction diagrams (for behavioral modeling)

nImplementation view

Composite structure diagrams

nDeployment view

None required

舉個例子，如果你正在建立一個執行在單個機器上的，簡單且完整的應用模型，你只需要以下幾個圖：

n用例檢視

用例圖

n設計檢視

類圖（為結構建模）

n協作檢視

協作圖（為行為建模）

n實施檢視

複合結構圖

n部署檢視

沒有要求

If yours is a reactive system or if it focuses on process flow, you’ll probably want to include state diagrams and activity diagrams, respectively, to model your system’s behavior.

如果你構建的模型是反應系統或是側重點是過程流，可能需要包含狀態圖和活動圖來分別建模系統的行為。

Similarly, if yours is a client/server system, you’ll probably want to include component diagrams and deployment diagrams to model the physical details of your system.

同樣地，如果構建的是客戶/服務系統，就需要包含元件圖和部署圖以為系統的物理情況建模。

Finally, if you are modeling a complex, distributed system, you’ll need to employ the full range of the UML’s diagrams in order to express the architecture of your system and the technical risks to your project, as in the following.

nUse case view

Use case diagrams

Sequence diagrams

nDesign view

Class diagrams (for structural modeling)

Interaction diagrams (for behavioral modeling)

State diagrams (for behavioral modeling)

Activity diagrams

nInteraction view

Interaction diagrams (for behavioral modeling)

nImplementation view

Class diagrams

Composite structure diagrams

nDeployment view

Deployment diagrams

最後，如果構建的是複雜的分散式系統模型，你需要為了表達系統的架構而採用全方位的UML圖，也會在專案中引進下面的技術風險：

n用例檢視

用例圖

序列圖

n設計檢視

類圖（為結構建模）

協作圖（為行為建模）

狀態圖（為行為建模）

活動圖

n協作檢視

協作圖（為行為建模）

n實施檢視

類圖

複合結構圖

n部署檢視

部署圖