Value-chain-diagrams: различия между версиями

Текущая версия на 22:47, 18 октября 2024

Данная страница является адаптированным переводом "Value chain diagrams" https://www.togaf-modeling.org Дата проверки актуальности:

Home	Models	Downloads	About

Тут будет перевод.	A value chain diagram provides a high-level orientation view of an enterprise and how it interacts with the outside world. In contrast to the more formal functional decomposition diagram developed within Phase B (Business Architecture), the value chain diagram focuses on presentational impact. The purpose of this diagram is to quickly on-board and align stakeholders for a particular change initiative, so that all participants understand the high-level functional and organizational context of the architecture engagement. A usual practice consists in showing a simplified business process diagram, and for each task defining its value factors and changes needed.

@@ Строка 8: / Строка 8: @@
 |-
 | Тут будет перевод.
-|| A value chain diagram provides a high-level orientation view of an enterprise and how it interacts with the outside world. In contrast to the more formal functional decomposition diagram developed within Phase B (Business Architecture), the value chain diagram focuses on presentational impact. The purpose of this diagram is to quickly on-board and align stakeholders for a particular change initiative, so that all participants understand the high-level functional and organizational context of the architecture engagement. A usual practice consists in showing a simplified business process diagram, and for each task defining its value factors and changes needed.
+|| A '''value chain diagram''' provides a high-level orientation view of an enterprise and how it interacts with the outside world. In contrast to the more formal functional '''decomposition diagram''' developed within Phase B ('''Business Architectur'''e), the '''value chain diagram''' focuses on presentational impact. The purpose of this diagram is to quickly on-board and align stakeholders for a particular change initiative, so that all participants understand the high-level functional and organizational context of the architecture engagement. A usual practice consists in showing a simplified '''business process diagram''', and for each task defining its value factors and changes needed.
 |-
 |}