Функциональный компонент «Проектирование услуги» Service Design Functional Component

Простыми словами

Компонент — система записи по всем логическим услугам: он берёт концептуальную услугу и элементы портфельного бэклога из потока S2P вместе с требованиями и выпускает логическую услугу и её блюпринт, описывая структуру и поведение услуги с учётом и системы услуги, и предложения услуги. Отвечает на вопрос «как будет устроено то, что мы обещали, и откуда оно возьмётся»: здесь же выбирается модель поставки — своими силами, аутсорсинг и прочее. Отличать от Enterprise Architecture Functional Component потока S2P: тот строит долгосрочный целевой ландшафт и план инвестиций, а этот проектирует конкретную услугу под конкретное соглашение об объёме и ИТ-инициативу. Обязанность, которую легко упустить: ставить инструментирование, чтобы ИТ получало эмпирические данные о работе услуг, а не полагалось только на отзывы пользователей.

Определение из первоисточника

Основные параметры

Атрибуты этой сущности по справочнику источника.

• Функциональные критерии стандарта: Shall be the system of record (authoritative source) for all Logical Services. Shall identify the new or existing services required to meet the needs of the Scope Agreement and IT Initiative, including both service systems and service offers. Shall leverage the Conceptual Service and Portfolio Backlog Items from the S2P Value Stream along with Requirements to produce a Logical Service that describes the service structure and behavior considering both the service system and the service offer. Shall create various architectural artifacts (data flow diagrams, technical schematics, etc.) that comply with the IT Initiative specifications and boundaries. Shall create service design specification document (Logical Service Blueprint). Shall identify the service delivery model (in-source, outsource, etc.). May identify service suppliers to meet the Requirements within the chosen delivery model. Shall enable interaction with IT operations to develop support plan/requirements for an IT service. Shall ensure that the architecture and Logical Service Blueprint are compliant with all standards and policies, including security standards and policies. Shall ensure that the architecture and Logical Service Blueprint meet all Requirements, including security requirements, to ensure the confidentiality, integrity, and availability of the service. Shall put instrumentation in place so that IT can capture empirical data about how IT services are performing, rather than relying only on anecdotal input from the user community. Shall ensure that the service is architected to meet the KPIs and SLAs. Shall ensure output of the Service Design functional component is used by the Source data object to source, create, and secure the service. Shall ensure traceability is done through the Requirement functional component. Can receive the Conceptual Service specification and design several Logical Services that represent it if a Service Portfolio functional component exists. Shall receive the development spend from the Project functional component and pass it to the Service Portfolio functional component if a Service Portfolio functional component exists. Can receive IT Initiative information which includes the scope and some content based on which the service is designed if a Project functional component exists. Can receive Requirement information from the Requirement functional component used to design the Logical Service and create design specifications if a Requirement functional component exists. Объекты данных компонента: Logical Service, Logical Service Blueprint.

Связанные понятия