Architecture-vision: различия между версиями

Материал из togaf-modeling.org.ru
Перейти к навигации Перейти к поиску
(Новая страница: « {| class="wikitable" |+ Caption text |- ! Текст заголовка !! Текст заголовка |- | Architecture Vision || Architecture Vision |- |...»)
 
Строка 1: Строка 1:
 
== Архитектурное видение ==




Строка 7: Строка 7:
! Текст заголовка !! Текст заголовка
! Текст заголовка !! Текст заголовка
|-
|-
| Architecture Vision || Architecture Vision
| Архитектурное видение || Architecture Vision
|-
|-
| Картинка || Текст ячейки
| [[Файл:Solution-concept-diagram.png]] || Текст ячейки
|-
|-
| Текст ячейки || Solution concept diagrams
| Текст ячейки || Solution concept diagrams

Версия 19:34, 7 сентября 2021

Архитектурное видение

Caption text
Текст заголовка Текст заголовка
Архитектурное видение Architecture Vision
Solution-concept-diagram.png Текст ячейки
Текст ячейки Solution concept diagrams
Текст ячейки A solution concept diagram provides a high-level orientation of the solution that is envisaged in order to meet the objectives of the architecture engagement. In contrast to the more formal and detailed architecture diagrams developed in the following phases, the solution concept represents a pencil sketch of the expected solution at the outset of the engagement. This diagram may embody key objectives, requirements and constraints for the engagement, and also highlight work areas to be
Картинка Текст ячейки
Value chain diagrams
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