🗊Презентация Agile аrchitecture scketches - 4C approach

Категория: Устройства и комплектующие
Нажмите для полного просмотра!
Agile аrchitecture scketches - 4C approach, слайд №1Agile аrchitecture scketches - 4C approach, слайд №2Agile аrchitecture scketches - 4C approach, слайд №3Agile аrchitecture scketches - 4C approach, слайд №4Agile аrchitecture scketches - 4C approach, слайд №5Agile аrchitecture scketches - 4C approach, слайд №6Agile аrchitecture scketches - 4C approach, слайд №7Agile аrchitecture scketches - 4C approach, слайд №8Agile аrchitecture scketches - 4C approach, слайд №9Agile аrchitecture scketches - 4C approach, слайд №10Agile аrchitecture scketches - 4C approach, слайд №11Agile аrchitecture scketches - 4C approach, слайд №12
Скачать
Вы можете ознакомиться и скачать презентацию на тему Agile аrchitecture scketches - 4C approach. Доклад-сообщение содержит 12 слайдов. Презентации для любого класса можно скачать бесплатно. Если материал и наш сайт презентаций Mypresentation Вам понравились – поделитесь им с друзьями с помощью социальных кнопок и добавьте в закладки в своем браузере.

Слайды и текст этой презентации

Слайд 1


Agile architecture sketches «4C» approach Sergey Denisov Data Architect & Modeler Salym Petroleum Development 11.03.2014
Описание слайда:
Agile architecture sketches «4C» approach Sergey Denisov Data Architect & Modeler Salym Petroleum Development 11.03.2014

Слайд 2


Agenda
Описание слайда:
Agenda

Слайд 3


Designing software
Описание слайда:
Designing software

Слайд 4


problems SA HLD documents in current format is not useful. It takes much time and power, is coming elder before finished. There is no single “materialized” view on solution as a whole. We have troubles in communication of business requirements and architecture decisions: what and how should we build IT- solutions. New staff on-boarding to project is complicated and chaotic. Painful handover to support process and scattered support documentation. Trash in meta.
Описание слайда:
problems SA HLD documents in current format is not useful. It takes much time and power, is coming elder before finished. There is no single “materialized” view on solution as a whole. We have troubles in communication of business requirements and architecture decisions: what and how should we build IT- solutions. New staff on-boarding to project is complicated and chaotic. Painful handover to support process and scattered support documentation. Trash in meta.

Слайд 5


«4C» Diagram sketching
Описание слайда:
«4C» Diagram sketching

Слайд 6


1C: context diagram
Описание слайда:
1C: context diagram

Слайд 7


2C: Container diagram
Описание слайда:
2C: Container diagram

Слайд 8


3C: Component diagram
Описание слайда:
3C: Component diagram

Слайд 9


4C: Class diagram ()
Описание слайда:
4C: Class diagram ()

Слайд 10


SA HLD on META
Описание слайда:
SA HLD on META

Слайд 11


Is this enough? SA HLD – is not just “word document somewhere in SP”, but power tool which help to: - assess, collaborate and communicate BRs and technical decisions - present high-level view on the solution and help to navigate throughout the solution - provides relevant levels of abstraction for different contributors during full product life-cycle (requirements-design- development-testing-deploy-support-decomission). This is not a complete set of project/tech. documents – this is SA HLD. (Process diagram, data-models, mapping, detailed design, Deployment diagram etc.)
Описание слайда:
Is this enough? SA HLD – is not just “word document somewhere in SP”, but power tool which help to: - assess, collaborate and communicate BRs and technical decisions - present high-level view on the solution and help to navigate throughout the solution - provides relevant levels of abstraction for different contributors during full product life-cycle (requirements-design- development-testing-deploy-support-decomission). This is not a complete set of project/tech. documents – this is SA HLD. (Process diagram, data-models, mapping, detailed design, Deployment diagram etc.)

Слайд 12


For all projects: SA HLD should be published on meta in “4C”-format. Workshops Arch-PM-BA-(BUS) to collaborate requirements and high-level vision. Deliverables: C1 and C2. “Architecture checkbox” on ABP when C1-C4 is published on meta.
Описание слайда:
For all projects: SA HLD should be published on meta in “4C”-format. Workshops Arch-PM-BA-(BUS) to collaborate requirements and high-level vision. Deliverables: C1 and C2. “Architecture checkbox” on ABP when C1-C4 is published on meta.

Скачать

Похожие презентации
Mypresentation.ru
Загрузить презентацию