Diagramming Architecture: according to the Principle Based Enterprise Architecture method

Автор: literator от 26-11-2019, 16:04, Коментариев: 0

Категория: КНИГИ » ПРОГРАММИРОВАНИЕ

Название: Diagramming Architecture: according to the Principle Based Enterprise Architecture method
Автор: Ian Koenig
Издательство: Amazon Digital Services LLC
Год: 2019
Страниц: 220
Язык: английский
Формат: epub
Размер: 17.1 MB

The Principle Based Enterprise Architecture (PBEA) Method is a proven approach for implementing an enterprise-wide architecture practice in large- and medium-sized technology organizations. These diagramming guidelines guidelines facilitate the documentation and communication of technology architecture. Clear communication is necessary both as a part of an enterprise architecture governance process and in the flow of information from business requirements to systems architecture to technical design to implementation to live operations.

Whatever the reason, communicating architecture is important in any technology organization and core to any enterprise architecture process. To communicate a concept, particularly a complicated one, both the presenter and the audience must speak the same language and that language should be flexible enough to be used in any scenario, yet descriptive enough and precise enough to get the point across with little or no ambiguity.

They say that “a picture is worth a thousand words” and where technology architecture is concerned, the adage is very much true. As opposed to inventing something brand new, these guidelines start with an existing, widely used diagramming language called the UML [1] (Unified Modelling Language) version 2.0.

UML is both extensible and flexible. But with flexibility comes a degree of imprecision. In addition, UML is generally used as a language for communicating design rather than architecture and many of its constructs move in the direction of model driven engineering [2] .
Architecture on the other hand is more abstract than design, which is more abstract than implementation. As such, we use diagrams to draw out the larger relationships between systems and reproducible patterns, rather than designs and implementations. We can use the flexibility inherent in UML quite effectively if we clearly define which UML constructs we intend to use, how we intend to use them and what they mean in our context.

Скачать Diagramming Architecture: according to the Principle Based Enterprise Architecture method




ОТСУТСТВУЕТ ССЫЛКА/ НЕ РАБОЧАЯ ССЫЛКА ЕСТЬ РЕШЕНИЕ, ПИШИМ СЮДА!


Нашел ошибку? Есть жалоба? Жми!
Пожаловаться администрации
Уважаемый посетитель, Вы зашли на сайт как незарегистрированный пользователь.
Мы рекомендуем Вам зарегистрироваться либо войти на сайт под своим именем.
Информация
Посетители, находящиеся в группе Гости, не могут оставлять комментарии к данной публикации.