Mike Kolar, Integrated GDS Deputy Section Manager

IND Architecture Modernization, Deep Space Information Services Architecture

(DISA), A Business Case for SOA-Based Modernization

Mike Kolar, Integrated GDS Deputy Section Manager

Learning Objectives Increase awareness of the DISA initiative and motivations

2 May 2009IND Architecture Modernization

The Problem SOA isMeant to Solve and its Benefits

Expensive and slow IT response to changing business needs

Duplicative IT investments and corresponding infrastructure

Expensive integration due to interoperability problems, including no canonical data models

Funding of IT projects that are not adequately aligned with business goals

Lack of sharing across organizational boundaries

Increased budget for new development Eliminating duplicative capabilities Spending development effort on true

domains of expertise and not middleware

Reducing overall system complexity Increasing automation Improving design practices Improving planning practices Increased system flexibility


Example Architecture Drivers for the DSN


The Notion of a Service

A service is a means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. - ITIL Service Design

“From a business perspective, a service is a well defined, encapsulated, reusable, business aligned capability.” - A. Arsanjani et al.

A SOA application service is a reusable and functionally cohesive software capability designed for third party composition that is exposed through a remotely accessible implementation agnostic interface. - Steven Fonseca


What is SOA?High-Level/Abstract Perspective

SOA is first and foremost a paradigm* It’s a paradigm for organizing and utilizing distributed

capabilities that may be under the control of different ownership domains†

It’s about working across boundaries, especially ownership boundaries Different people or organizations may provide (“own”) the service

and its underlying capability than the entities accessing it It’s a uniform means to offer, discover, interact with and use

capabilities to produce desired effects consistent with measurable preconditions and expectations†

*Paradigm: “A set of assumptions, concepts, values, and practices that constitutes a way of viewing reality for the community that shares them, especially in an intellectual discipline.” (Source: New American Heritage Dictionary)

†Source: OASIS Reference Model for Service Oriented Architecture 1.0


SOA: The Basic Idea

• Reuse of services across organizational boundaries

• Efficient construction of software through service composition

• Remote offering of software capabilities• Facilitation of interoperability and integration• Use of software architecture to achieve high

levels of maintainability and extensibility/adaptability

7

ServiceService

Client 1

Service

Client 2

Organization A2

Organization A1

Software Element Service Provider

Registry as a Service Address Book (Yellow Pages)

Registry as an Information Repository

Software Element

Software Element

Function

Data

register service lookup service

service description

execute service

information request

information

information request

information

May 2009IND Architecture Modernization

GDS Modernization DoDAF OV-1


DISA Modernization Framework

SOA Solution Elements Infrastructure Runtime

Management Enterprise

Architecture Software

Architecture Information

Architecture Organizational

Design Governance Best Practices


AS-IS Versus TO-BEMaturity Assessment

SOA practice areas based on the Oracle SOA Maturity Model


Anecdotal Business Casefor Software Reuse Initiatives

Nippon Electric Company: Achieved 6.7 times higher productivity and 2.8 times better quality through 17% reuse. They improved software quality 5-10 times over a 7-year period through the use of unmodified reuse components in the domain of basic system software development and in the domain of communication switching systems.

GTE Corporation: Saved $14 million in costs of software development with reuse levels of 14%. GTE Data Services benefited from $1.5M in cost savings in 1988 for 20-50% reuse

Multiple Ada Projects: A study of 75 Ada projects in 15 firms totaling 30M LOC found reuse resulted in 10 times higher quality with reuse levels of 10-18%

Toshiba saw a 20-30% reduction in defects per line of code with reuse levels of 60%

DEC reported cycle times that were reduced by a factor of 3-5 through reuse levels of 50-80% and an increase of 25% in productivity through software reuse

Hewlett-Packard (HP) cited quality improvement on two projects of 76% and 24% defect reduction, 50% and 40% increases in productivity, and a 43% reduction in time to market with reuse levels up to 70%. ROI ranged from 215% for one development to 410% for the otherA study of nine companies showed reuse led to 84% lower project costs, cycle time reduction of 70%, and reduced defects

NASA Report: Reduction of 75% in overall development effort and cost

Reuse Experience References: http://www.goldpractices.com/practices/arrc/index.php


The Business Casefor Software Architecture

The question, is an architecture-centric approach to software development valuable, is generally believed to have been answered about 10 years ago ~ Kazman

“The return on investment of systems engineering (SE-ROI) from an analysis of the 161 software projects in the COCOMO II database... The analysis shows that, after normalizing for the effects of other cost drivers, the cost difference between projects doing a minimal job of software systems engineering – as measured by the thoroughness of its architecture definition and risk resolution – and projects doing a very thorough job was 18% for small projects and 92% for very large software projects as measured in lines of code.” 12~ Boehm

“… greater emphasis on the system design creates easier, more rapid integration and test. The overall result is a saving in both time and cost, with a higher quality system product. The primary impact of the systems engineering concepts is to reduce risk early…” ~ Honour

“Analysis of project defect tracking cost-to-fix data (a major source of rework costs) showed that 20% of the defects accounted for 80% of the rework costs, and that these 20% were primarily due to inadequate architecture definition and risk resolution.” ~ Boehm

Understanding the Value of Systems Engineering, Honour


Example Implementation Architecture Models

13

From Objects to Services: A Journey in Search of Component Reuse Nirvana, Mahesh H. Dodani, IBM Software, U.S.A., The Enterprise Service Bus, http://www.jot.fm/issues/issue_2004_09/column5/

SOA Governance Reference Model, Integrated SOA Governance InfrastructureSOA Software, Inc, http://www.soa.com/index.php/solutions/reference_model/

May 2009IND Architecture Modernization

Mike Kolar, Integrated GDS Deputy Section Manager

Documents

Transcript of Mike Kolar, Integrated GDS Deputy Section Manager