PENGUKURAN PRESTASI DAN IMPAK PELAKSANAAN ......mentransformasikan perkhidmatan Kerajaan ke arah...

BENGKEL PENGURUSAN PERUBAHAN SIRI KETIGAKEMENTERIAN DAN AGENSI SEKTOR AWAM

BAGIPEMBANGUNAN ENTERPRISE ARCHITECTURE (EA) SEKTOR AWAM

23 OKTOBER 2016 HINGGA 25 OKTOBER 2016

PENGUKURAN PRESTASI DAN IMPAK PELAKSANAAN ENTERPRISE ARCHITECTURE (EA) DI AGENSI SEKTOR AWAM

LOKASIHotel Hatten, Melaka

Objektif Bengkel

Meningkatkan kefahaman pelaksanaan

Enterprise Architecture Sektor Awam dan

mengupayakannya dalam

mentransformasikan perkhidmatan Kerajaan

ke arah perkhidmatan digital bersepadu

CONFIDENTIAL Page 2 of 50

Objektif Pengurusan Perubahan

Meningkatkan keberkesanan

dan kecekapan pengurusan dan

kefungsian organisasi

Memantapkan amalan

Pengurusan Perubahan bagi melaksanakan

Enterprise ArchitectureSektor Awam

Memantapkan kepimpinan dan

tadbir urus perancangan

serta koordinasi inisiatif digital


Aturcara Bengkel


BENGKEL PERTAMA

Metodologi 1GovEA


1GovEA Notation


What is ArchiMate®?ArchiMate® is a modelling technique

(“Language") for describing Enterprise Architectures

It presents a clear set of concepts within and relationships between architecture domains, and offers a simple and uniform structure for describing the contents of BDAT

The standard notation that will be used during 1GovEA development within Public Sector

1GovEA Notation (Samb.)


ArchiMate® Viewpoints in 1GovEAMotivation Viewpoint

Organization Viewpoint

Business Function Viewpoint

Business Process Viewpoint

Service Realization Viewpoint*

Information Structure Viewpoint

Application Usage Viewpoint

Application Co-operation Viewpoint*

Infrastructure Usage Viewpoint

Infrastructure Viewpoint

Introductory Viewpoint*

Implementation & Migration Viewpoint *

* - For Transition 1, these viewpoints will be used for Target Architecture

1GovEA Notation (Samb.)


When Will It be Used?Motivation Viewpoint Organization Viewpoint

Business Function ViewpointBusiness Process Viewpoint

Service Realization Viewpoint

Information Structure ViewpointApplication Usage Viewpoint

Application Co-operation Viewpoint

Infrastructure Usage ViewpointInfrastructure Viewpoint

Implementation & Migration Viewpoint

Introductory Viewpoint

Peringkat 1 - Initiate


Key activities:• Information gathering• Establish architecture

team• Key Stakeholders

interview

Principal outcomes:• 6 template 1GovEA

Stage 1

Initiate

1.1 Define Architecture

Scope

1.2 Confirm Governance & Stakeholders

1.3 Define Architecture Vision and

Requirements

Peringkat 1 – Initiate (Samb.)


ArchiMate® Viewpoints in 1GovEA

Motivation Viewpoint




Stage 1 Deliverables in 1GovEAS0-R001 Architecture Repository

S1-R004 Architecture Requirements

R004-01 Statement of Architecture Work

S1-R005 Communication Plan

S1-R005 Request for Architecture Work

S1-R006 Architecture Vision



S0-R001 Architecture Repositorythe Architecture Repository acts as a holding area

for all architecture-related projects within the agency

to document the Architecture Repository used, the architecture content stored within, the connection methods and contact details for those responsible of maintaining the Architecture Repository

allows projects to manage their deliverables, locate re-usable assets, and publish outputs to stakeholders and other interested parties



S1-R004 Architecture RequirementsSpecification provides a set of quantitative

statements that outline what an implementation project must do in order to comply with the architecture

a companion to the Architecture Definition Document (ADD)

provides a quantitative view of the solution and stating measurable criteria that must be met during the implementation of the architecture



S1-R005 Request for Architecture WorkThe Request for Architecture Work document

initiates the architecture work to be undertaken, provides the reasons for the architecture work (the business case) and supports confirmation of the project scope

The Request for Architecture Work is intended to be submitted to the agency’s Office of the Architect Architecture Team to review the request and determine if changes in the architecture are required

Peringkat 1 – Initiate (Samb.))


R004-01 Statement of Architecture Workprovides a documented response to the Request

for Architecture Work

this document is written to define the agreed scope of the architecture work accepted, aims and objectives, stakeholders and key deliverables expected to be output by the agency’s Enterprise Architecture Team as a result of this work



S1-R005 Communication Plandescribes Communications Plan for the project to

implement Enterprise Architecture in the agency

a guideline and tool to ensure communication of information sets are carried out within a planned and managed process



S1-R006 Architecture VisionThe Architecture Vision is essentially a high-level

overview of the long-term architectural goal that an agency aspires to achieve in the future

The aim of the vision is to paint a picture of the end architecture product early on in the project so that it can act as a reference point and boundary for architects when customising the finer details to realise this vision/ target architecture.

facilitates stakeholder communication by providing an executive summary of the end architecture solution.



Stakeholder

Driver

Assessment Goal

Requirement /

Constraint

Principle

Represented using Motivation Viewpoint

to articulate an Architecture Vision that enables the business goals, responds to the strategic drivers, conforms with the principles, and addresses the stakeholder concerns and objectives

These motivations will influence, guide, and constrain the design of the Target Architecture





• A stakeholder is defined as the role of an individual, team, or organization (or classes thereof) that represents their interests in, or concerns relative to, the outcome of the architecture

• A driver is defined as something that creates, motivates and fuels the change in an organization. Drivers may be internal, in which case they are usually associated with a stakeholder. Internal drivers are often referred to as stakeholder “concerns”. Drivers of change may also be external; e.g., economic changes or changing legislation

• An assessment is defined as the outcome of some analysis of some driver i.e. issues or problems that impact and contribute directly to the drivers.



Motivation Viewpoint• A goal is defined as the end state that a stakeholder intends to achieve and are generally expressed

using qualitative words; e.g., “increase”, “improve”, or “easier”

• A principle is defined as a normative property of all systems in a given context, or the way in which they are realized. A principle defines a general property that applies to any system in a certain context. Principles are strongly related to goals and requirements. A principle is motivated by some goal. Each principle provides a means to realize its motivating goal, generally formulated as a guideline

• A requirement is defined as a statement of need that must be realized by a system that represents the “means” to realize goals.

• A constraint is a restriction on the way in which a system/ goal is realized



(Group Activity)




Represented using:

◦ Organization Viewpoint

To articulate

◦ How a service is provided to the end user

◦ Which organizational structure function that realizes the service

◦ What are the processes involved that realizes the service and which role is involved during each of the process

◦ What kind of information is required/produced by each of the process



Translating Organization Chart into Organization View Diagram

Verify the Organization Chart

Identify Roles associated with the

organization structure

Draw the Organization View



Step #1 – Verify the Organization Chart

Verify that the Organization Chart provided is up-to-date, and actually reflects the current organization structure

If its not, request for the actual information



Step #2 – Identify Roles Associated with The Organization Structure

Identify what are the roles are available in the organization

One job position may perform several business role, thus DO NOT get confused between them



Step #3 – Draw The Organization View

Provide brief description of each of the object created in the diagram

Only associate the role available in each structure

DO NOT draw complicated diagram –separate into multiple pages to avoid diagram from being too crowded

Ensure that proper object relationships are used


High-Level Organization

Viewpoint

(Group Activity)


Rumusan Peringkat 1

(Initiate)

BENGKEL KEDUA

METODOLOGI 1GOVEA


1GovEA Notation













Implementation & Migration Viewpoint


Peringkat 2 - Assess

Key activities:• Gather / document

existing artefacts (diagrams, matrices, documents) across architecture domains

Principal outcomes:• Current Architecture

Definition Document

Stage 2

Assess

2.1 Assess Current Architecture

Business Architecture

Data Architecture

ApplicationArchitecture

Technology Architecture

2.2 Gap and Opportunities

Peringkat 2 – Assess (Samb.)


ArchiMate® Viewpoints in 1GovEAOrganization Viewpoint









Business Architecture

Represented using:

◦ Organization Viewpoint

◦ Business Function Viewpoint

◦ Business Process Viewpoint

To articulate

◦ How a service is provided to the end user

◦ Which organizational structure function that realizes the service

◦ What are the processes involved that realizes the service and which role is involved during each of the process

◦ What kind of information is required/produced by each of the process



Translating Organization Chart into Organization View Diagram

Verify the Organization Chart

Identify Roles associated with the

organization structure

Draw the Organization View



Step #1 – Verify the Organization Chart

Verify that the Organization Chart provided is up-to-date, and actually reflects the current organization structure




Step #2 – Identify Roles Associated with The Organization Structure

Identify what are the roles are available in the organization

One job position may perform several business role, thus DO NOT get confused between them



Step #3 – Draw The Organization View







(Group Activity)



Translating Functional Chart into Business Function View Diagram

Verify the Functional Chart

Identify The Service Realized by

the Functions

Draw the Business Function View



Step #1 – Verify the Functional Chart

Verify that the Organization Chart provided is up-to-date, and actually reflects the current organization’s functions




Step #2 – Identify The Service Realized by the Functions

Identify what are the business service realized by the business function

Identify the business service type (i.ecore services, operation services, supporting services, etc)



Step #3 – Draw The Business Function View






Business Function

Viewpoint

(Group Activity)



Re-visit the EA development scope for the current transition

The CRITICAL stage to ensure that whole Enterprise Architecture development does not stray away from the EA transition scope

Revise Architecture Requirements Document (if necessary)

1GovEA Notation













Implementation & Migration Viewpoint*


RUMUSAN & PENUTUP


KesedaranTerhadap

MentransformasiPerkhidmatan

Kerajaan

↑ PenyampaianPerkhidmatan,

KoleborasiBisnes, Cross

Agencies

PengukuranPrestasi & Impak

Pelaksanaan

PengukuhanPengurusan

Bakat

Pelaksanaan danKelestarian

Inisiatif

1 2 3 4 5

We are here!

THANK YOUAll information incorporated within this slide is created for

Malaysian Administrative Management and Planning Unit (MAMPU), Prime Minister’s Department, Malaysia.

All information is the property of MAMPU and any unauthorisedreproduction is prohibited.

PENGUKURAN PRESTASI DAN IMPAK PELAKSANAAN ......mentransformasikan perkhidmatan Kerajaan ke arah...

Documents

Transcript of PENGUKURAN PRESTASI DAN IMPAK PELAKSANAAN ......mentransformasikan perkhidmatan Kerajaan ke arah...