soa readiness assessment checklist

Iowa Department ofAdministrative Services

IT Enterprise Service-OrientedArchitecture

SOA Readiness Assessment Checklist Version 1.0

This document was prepared by Integrated Software Specialists, Inc. (“ISS”) and is to be considered confidential and proprietary to ISS and Iowa Department of Administrative Services.

IT ENTERPRISE SERVICE-ORIENTED ARCHITECTURESOA READINESS ASSESSMENT CHECKLIST

4/18/2006VERSION 1.0

Document Control

DOCUMENT INFORMATION

©

InformationDocument IdDocument Owner Guillermo TantachucoIssue Date 5/05/2006Last Saved Date 5/05/2006File Name IowaSOA_IRRA.doc

DOCUMENT HISTORY

Version Issue Date Changes0.8 5/05/2006 “Draft” Internal Review 0.81 5/10/2006 Initial Review

DOCUMENT APPROVALS

Role Name Signature DateProject Sponsor

Project Review Group

Project Manager

ISS Project Manager

ISS Quality Assurance

CONFIDENTIAL 2023 INTEGRATED SOFTWARE SPECIALISTS, INC. PAGE 2 OF 15


4/18/2006VERSION 1.0

Table of Contents

1 INTRODUCTION..........................................................................................................................5

1.1 Purpose........................................................................................................................................5

1.2 Scope...........................................................................................................................................5

1.3 Definitions, Acronyms and Abbreviations.................................................................................5

1.4 References...................................................................................................................................5

2 IT READINESS ASSESSMENT..................................................................................................6

2.1 benefits........................................................................................................................................6

2.2 SOA governance.........................................................................................................................6

2.3 Software Development Life Cycle..............................................................................................6

2.3.1 Methodology..........................................................................................................................6

2.3.2 Software Development Processes..........................................................................................7

2.3.3 Modeling techniques..............................................................................................................7

2.3.4 Tool Usage.............................................................................................................................8

2.4 architecture..................................................................................................................................8

2.4.1 General..................................................................................................................................8

2.4.2 SOA Reference Architecture..................................................................................................8

2.4.3 Security..................................................................................................................................9

2.4.4 Quality of Service..................................................................................................................9

2.5 infrastructure services.................................................................................................................9

2.6 application portfolio....................................................................................................................9

2.7 skills..........................................................................................................................................10

2.7.1 Understanding of SOA.........................................................................................................10

2.7.2 SOA Experience...................................................................................................................10

2.8 common domain model (data)..................................................................................................10

2.9 organizational alignment...........................................................................................................10

2.10 metrics....................................................................................................................................11



4/18/2006VERSION 1.0

2.11 cost.........................................................................................................................................11

2.12 large-scale IT initiatives.........................................................................................................11

3 BUSINESS READINESS ASSESSMENT.................................................................................13

3.1 benefits......................................................................................................................................13

3.2 business sponsorship.................................................................................................................13

3.3 business processes.....................................................................................................................14

3.4 strategy......................................................................................................................................14

3.5 SOA Awareness........................................................................................................................14

3.6 large-scale initiatives................................................................................................................15



4/18/2006VERSION 1.0

1 INTRODUCTION

1.1 PURPOSE

The purpose of this document is to facilitate the assessment of several key organizational and technology aspects that are essential to both mitigate risks and maximize opportunities for business benefits from a service-oriented architecture (SOA). As a result, the assessment will help provide a better understanding of the current situation and, consequently, it will establish the basis for the development of a phased SOA adoption plan that delivers early, measurable, and incremental business benefits while avoiding major disruptions.

1.2 SCOPE

The SOA readiness assessment checklist will be used during the “Initial Readiness and Risks Assessment” session which is part of the VIEW™ (Vision Engineering Workshop) phase of the project.

1.3 DEFINITIONS, ACRONYMS AND ABBREVIATIONS

SOA: Service-Oriented Architecture

ViEW™: Vision Engineering Workshop

SDLC: Software Development Life Cycle

1.4 REFERENCES

None



4/18/2006VERSION 1.0

2 IT READINESS ASSESSMENT

2.1 BENEFITS

Please indicate the degree of importance that your IT organization will give to each of the following IT benefits:

IT Benefits Importance

(1=- Low, 2 = Medium, 3= High)

Improve time to market or IT responsiveness

Reduced total cost of ownership

Reduced vendor lock-in due to standard-based interoperability

Reduced software development and maintenance cost

Incremental deployment to better manage expenses and risks

Establish flexible platform for future expansion

2.2 SOA GOVERNANCE

Please select one of the following options:

No SOA governance model (organization, roles/responsibilities, processes/procedures, standards/best practices, etc) defined

SOA organization and its roles and responsibilities are being (or have been) defined

SOA basic processes and control procedures are being (or were) developed

SOA standards and best practices are being (or were) developed

SOA governance model is being (or has been) implemented at a bureau/program level

SOA governance model is being (or has been) implemented at an agency level

2.3 SOFTWARE DEVELOPMENT LIFE CYCLE

2.3.1 Methodology

Please select all the options that apply to you:



4/18/2006VERSION 1.0

Structured methodology

Rational Unified Process

Agile Methodology

Extreme Programming

Other

2.3.2 Software Development Processes

Please one of the following options:

Documentation of processes and disciplines is currently underway

Processes and disciplines are used repeatedly

Processes are well understood, and are described in standards, procedures, tools, and methods

Processes help effectively control and measure the software development effort

IT organization focus on continually improving process performance through both incremental and innovative technological enhancements

2.3.3 Modeling techniques


Structured analysis and design

Object-oriented analysis and design

Service-oriented modeling with little or no business users’ involvement

Service-oriented modeling with significant business users’ involvement

Model-driven architecture



4/18/2006VERSION 1.0

2.3.4 Tool Usage

List the tools your IT organization utilizes to support the different phases of the software development process for each environment:

SDLC phase Environment

Mainframe Client/Server Web Web services

Analysis

Design/Modeling

Development

Test

Functional

Regression

Performance

Load/Stress

Deployment

2.4 ARCHITECTURE

2.4.1 General


No SOA initiatives currently underway

Early phases of SOA adoption (planning, service definition, governance, etc)

SOA Proof of concept is being (or has been) implemented

Shared service layer is being (or has been) implemented for a given bureau/program

Shared service layer is being (or has been) implemented across the agency

Multi-year state-wide SOA implementation is in progress

2.4.2 SOA Reference Architecture


Reference architecture does not exist

Some layers of the reference architecture are being (or have been) designed

Design of the SOA Reference architecture is complete



4/18/2006VERSION 1.0

2.4.3 Security


SOA security policy does not exist

Only transport security mechanism has been defined

Service provider and consumer authentication mechanism has been designed

Message integrity and confidentiality mechanisms have been designed

Inter-agency security mechanisms have been designed

2.4.4 Quality of Service

Quality of service (a.k.a. non-functional requirements) refers to aspects such as performance, scalability, availability, reliability, management, among others. Please select one of the following options:

“Quality of service” attributes won’t be taken into account at this time

SOA methodology addresses and enforces compliance with “quality of service” attributes

Tools and best practices are in place to support “quality of service” testing efforts

Tools, processes and procedures are in place to support and monitor “quality of service” attributes in production

2.5 INFRASTRUCTURE SERVICES


Infrastructure services won’t be considered at this time

Basic services (connectivity, messaging, routing, transformation, security) are in place

Advanced services (transaction management, metadata management, version resolution, orchestration, policy-based processing) have been deployed

Common management and monitoring components are in place

2.6 APPLICATION PORTFOLIO


Legacy application functionality is not exposed as a service

Identification of potential business services that can be developed from existing applications is in progress

Use of service modeling techniques to service-enable legacy applications

A number of business services have been deployed by service-enabling legacy applications



4/18/2006VERSION 1.0

2.7 SKILLS

2.7.1 Understanding of SOA

Please select the option that best describes your team’s understanding of SOA:

None

Somewhat familiar

Fair

Good

Excellent

2.7.2 SOA Experience

Please select the option that best describes your team’s SOA level of experience:

Limited or no experience

Academic

A few application(s)

Application(s) at a bureau level

Application(s) at an agency level

State-wide application(s)

2.8 COMMON DOMAIN MODEL (DATA)

The Common Domain Model represents the core data (business entities) used in a given business domain. Please select one of the following options:

No standardized data model exists

The basis of a Common Domain Model is in place

Common Domain Model used by a given bureau/program

Common Domain Model actively managed for a given agency

Common Domain Model supports inter-agency interaction

2.9 ORGANIZATIONAL ALIGNMENT


IT organization is part of a given bureau/program

IT organization serves all bureaus/programs



4/18/2006VERSION 1.0

IT is organized around bureau/programs

IT is organized around services

IT is organized around projects

2.10 METRICS


Service development metrics do not exist

Metrics exist for service creation efforts

Metrics are assessed against key metrics such as development metrics, productivity measures, reuse measures, and external benchmarking

2.11 COST


Cost of a shared service layer has not been estimated

Cost of initial service development has been estimated

Costs to construct and operate SOA solutions are included in the budget

2.12 LARGE-SCALE IT INITIATIVES

IT initiatives are considered large if they meet the following criterion:

It represented a significant shift in agency’s culture (paradigm shift)

It effected a large portion of agency’s partners

It was planned to span a large timeframe

The outcome of IT initiatives can be categorized as:

1 – Successful: It means that initiative met expectation and was delivered on time and within budget

2 – Moderately Successful: It means that initiative met at least two of the three success criterion

3 – Moderately Unsuccessful: It means that initiative met at least one of the three success criterion

4 – Unsuccessful: It means that initiative met none of the three success criterion

Please list the most recent IT large-scale initiatives, their outcome and their reasons for obtaining that outcome:



4/18/2006VERSION 1.0

Large-scale IT initiative Timeframe

(from MM/YYYY to MM/YYYY )

Outcome

(1=Successful, 2=Moderately

Successful ,3= Moderately Unsuccessful, 4 =

Unsuccessful)

Reason(s) for outcome



4/18/2006VERSION 1.0

3 BUSINESS READINESS ASSESSMENT

3.1 BENEFITS

Please indicate the degree of importance that your business community will give to the following business benefits:

Business Benefits Importance

(1=- Low, 2 = Medium, 3= High)

Improve time to market or agency responsiveness to needs

Lower operating costs

Improve customer service and business agility by enhancing, streamlining and automating business operations

Access real time business information accurately and rapidly

End-to-end connectivity both internally and with third parties and consumers

Eliminate manual process errors

3.2 BUSINESS SPONSORSHIP

Which business stakeholder(s) are sponsoring this SOA initiative?

Name Title Agency / Bureau / Program



4/18/2006VERSION 1.0

3.3 BUSINESS PROCESSES

A business process is a set of activities that produce something of value to the organization, its stakeholders and/or its customers. A business process can be part of a larger process and may include other business processes. Examples of business processes are:

Determine applicant’s eligibility for Medicaid benefits (Department of Human Services)

Driver Licensing process (Department of Transportation)

List the business process you feel will largely benefit from an SOA initiative.

Business Process Bureau/Program Reason

3.4 STRATEGY


No SOA strategy has been defined

An SOA strategy is being (or has been) developed

An SOA strategy has been implemented at a bureau/program level

An SOA strategy has been implemented at an agency level

3.5 SOA AWARENESS


Agency’s leadership team is not aware of business impact of SOA

Agency’s leadership team has limited understanding of business impact of SOA

Business benefits are fully understood by agency’s leadership team

Agency’s leadership team is able to quantify business benefits



4/18/2006VERSION 1.0

3.6 LARGE-SCALE INITIATIVES

Business initiatives are considered large if they meet the following criterion:

It represented a significant shift in agency’s culture (paradigm shift)

It effected a large portion of agency’s partners

It was planned to span a large timeframe

The outcome of business initiatives can be categorized as:

1 – Successful: It means that initiative met expectation and was delivered on time and within budget

2 – Moderately Successful: It means that initiative met at least two of the three success criterion

3 – Moderately Unsuccessful: It means that initiative met at least one of the three success criterion

4 – Unsuccessful: It means that initiative met none of the three success criterion

Please list the most recent IT large-scale initiatives, their outcome and their reasons for obtaining that outcome:

Large-scale Business initiative

Timeframe

(from MM/YYYY to MM/YYYY )

Outcome

(1=Successful, 2=Moderately

Successful ,3= Moderately Unsuccessful, 4 =

Unsuccessful)

Reason(s) for outcome


soa readiness assessment checklist

Documents