agile development life cycle and soa testing

© CMC Media 2008© CMC Media 2008

Test, Validate & Virtualize for Agile SOA

Moderator

Patrick Egan - Publisher – Agile Journal

Speakers

John Michelsen - Founder and Chief Scientist of iTKO LISA

Zach Nies - Vice President, Products Rally Software

Agile Business Webcast

© CMC Media Inc. 2008© CMC Media Inc. 2008

John Michelsen

Founder and Chief Scientist of iTKO LISA, an automated SOA software testing and virtualization company. John has more than 15 years of high-level enterprise development experience, as a chief architect of development teams and as an executive in designing, developing, and managing large-scale, object-oriented solutions in traditional and network architectures. He is the chief architect of iTKO's LISA automated testing and virtualization product, and a leading industry advocate for software quality, with several published articles and speaking appearances at technology conferences under his belt.


Zach Nies

Zach Nies brings close to 20 years of engineering and product development experience to Rally’s innovative products. Prior to joining Rally, Zach served as Principal Architect and Director of Systems Architecture for Level 3 Communications and founded a small start up which was quickly acquired by the publicly traded Creo, Inc, now a division of Kodak. He also served as Chief Software Architect at Quark, where he provided the overarching technological vision for the company. Zach’s product vision has won numerous industry awards, including Jolt Product Excellence awards, Seybold HotPicks and the prized MacWorld Best of Show. Zach has served on standards bodies such as the W3C's HTML working group and currently serves on the board of directors for Agile Denver.

At the age of 13, Zach began commercially publishing software and, at age 16, started a successful consulting business. A Boettcher Scholar, Zach received his BS with distinction in Computer Science Engineering from the University of Colorado at Boulder. He spends his spare time tuning his golf swing and spending time with his family.

4

Rally Perspective

Zach Nies – Rally Software

₋ Vice President, Products

5

Rally – The #1 Agile Provider

∙ #1 On-Demand Tool

₋ 900 customers, 20,000 projects and 35,000 users across 50 countries

and three-time JOLT Product Excellence awards

₋ Preferred provider for the large enterprise by Trail Ridge Consulting independent survey in 2007

∙ #1 Training Services for Agility

₋ World’s largest source for Agile training with 90 expert trainers and

2,500 students trained

₋ Leading the forefront of Agile knowledge – more than 100,000 downloads of white papers, articles and webinars

∙ #1 Community for Collaboration

₋ Largest online community dedicated to advancing all aspects of software agility with more than 3,300 members

₋ Industry-disrupting Rally User Community includes a product backlog

that is prioritized by customers

6

Thesis and Agenda

∙ Software can be delivered faster, with higher

quality, when automation and lean thinking are

applied to the development cycle.

∙ Agenda₋ Cycles and Feedback – Lessons from Lean

₋ Short, Time-Boxed Development

₋ Automation and Visibility

Cycles and Feedback

Lessons from Lean

8

Improving Cycle Times

∙ Limit work to capacity

∙ Even out the arrival of work

∙ Minimize the number of Things-in-Process

∙ Minimize the size of the Things-in-Process

∙ Establish a regular cadence

∙ Use pull scheduling

Poppendieck, Mary and Tom. “Managing the Pipeline.” Poppendieck.LLC. 7 Oct 2007.

http://www.poppendieck.com/pipeline.htm.

http://www.poppendieck.com/pipeline.htm

9

Cycle Times and Going Faster

Cycle Time as a Function of Utilization and Batch Size

0

5

10

15

20

25

30

35

40

45

10% 20% 30% 40% 50% 60% 70% 80% 90% 100%

Cycle

Tim

e (

hou

rs)

Small Batches

Medium Batches

Large Batches

©2003 Poppendieck.LLC

Poppendieck, Mary and Tom. Lean Software Development, An Agile Toolkit. Boston: Addison-Wesley, 2003.

10

Development Cycle

11

Reduce Batching & Queuing

12

By Improving Your Automation

AUTOMATION

Short, Time-Boxed Development

14

Traditional Software Development

Long, Large, Linear, Late

Lifecycle

Deliverable

s

Time to

Market

Define Test

Train

Code

12 to 36 months

PRDTest

planMRD

Tech

specCode

Funct

test

Deploy

Doc

15

Agile Software Development

Iterate, Increment and Innovate

Deliverable

s

Time to

Market

LifecycleWaterfall

test

1 to 6 months Waterfall 12 to 36 months

Waterfall

deploy

Working, tested code on short cycles Waterfall documentation

16

Working in a Time-Box

Release Backlog

Fixed Time(Iteration)

Story Card A

Story Card B

Story Card C

Story Card D

Story Card …

Define

Develop

Accept

Fix

ed

Re

so

urc

es

Re

vie

w

Pla

n

Automation and Visibility

18

Code Level Quality Feedback

19

Automated Functional Quality Feedback

20

Manual GUI & Regression Quality

Feedback

21

Visibility from Rally

How Much Faster?

23

37% Faster Time-to-Market

W W W . I T K O . C O M24 © 2008, iTKO, Inc. | PROPRIETARY / CONFIDENTIAL W W W . I T K O . C O M24 © 2008, Interactive TKO, Inc. | PROPRIETARY /

CONFIDENTIAL

Test, Validate & Virtualize

for Agile SOA

John Michelsen

Founder & Chief GeekiTKO LISA

September 23, 2008

W W W . I T K O . C O M25 © 2008, iTKO, Inc. | PROPRIETARY / CONFIDENTIAL

iTKO: Our Ecosystem

Everyone should own quality™.

Customers

Delivery PartnersTechnology Partners

TestCenter

Awards

http://www.sun.com/

http://www.itko.com/site/company/news_23.jsp

http://images.google.com/imgres?imgurl=http://www.loglink.ru/catalog/card/logo/7973.gif&imgrefurl=http://www.loglink.ru/catalog/card7973&h=164&w=201&sz=8&tbnid=TLAzBNJSL-CBBM:&tbnh=80&tbnw=99&hl=en&start=1&prev=/images?q=i2+logo&svnum=10&hl=en&hs=Ddc&lr=&rls=DELA,DELA:2006-06,DELA:en&sa=N

http://www.raytheon.com/

http://www.emc.com/index.jsp

http://www.sun.com/

http://images.google.com/imgres?imgurl=http://www.loglink.ru/catalog/card/logo/7973.gif&imgrefurl=http://www.loglink.ru/catalog/card7973&h=164&w=201&sz=8&tbnid=TLAzBNJSL-CBBM:&tbnh=80&tbnw=99&hl=en&start=1&prev=/images?q=i2+logo&svnum=10&hl=en&hs=Ddc&lr=&rls=DELA,DELA:2006-06,DELA:en&sa=N


Business Initiatives

Agility

Cost Reduction

Globalization

Mergers & Acquisitions

Compliance

Mainframe Client/ServerComposite Applications/SOA

1980 … 1985 … 1990 … 1995 … 2000 … 2005 … 2010 … 2015

Business Trends are Driving a

Major Shift in IT Environments

• IT Initiatives

• SOA

• Outsource/Offshore

• Agile Development

• BPM

• Leverage and Extend


The Goal of Agile SOA

Shorter Time To Market

Reduced Failure Rate

Faster Time To Recovery

Lower Maintenance Cost

Minimize Business Risk inherent in making

Frequent Changes to Complex IT

Environments

A strong collaborativemethodology delivers:

Increasing rate of change in applications & workflows

In

cre

asin

g C

om

ple

xit

y in

th

e I

T

en

vir

on

men

t

High Complexity

High Change

Low

Complexity

Low Change

Client/server

apps

Mainframe /

Packaged

SOA & Composite

Apps

Web

applications


Risk Factors for SOA

Inadequate Testing: Traditional testing techniques cannot

automate testing against component and middleware-based

workflows

Unintended Consequences: Individual components and

technologies are changing at their own pace and can create

severe issues within business processes

Lack of Controls: Governance techniques to dictate

standards may be useless due to inability to enforce policies

Dependency on Constrained Systems: Access and

capacity constraints on key systems reduces agility, and

increases dependencies and costs between teams

W W W . I T K O . C O M29 © 2008, iTKO ( Interactive TKO, Inc.) | PROPRIETARY / CONFIDENTIAL.

Limited smoke testing at assembly

Siloed Tests in the SOA Lifecycle

Unit Tests

Agile Developers

Integration Teams

Functional & UI “Acceptance” tests, manual

scripts

QA/QE Teams

Performance Testing &

Monitoring

Operations Teams

1.2s

What are the constraints that keep

us from collaborating in a more

parallel way for Agile SOA?


Developersunit test

components and jump-start QA with testability

QA expands dev tests and create functional

and load tests for integration

Production tests in deployment and report

issues to support

Support rapidly debugs

SLA or Policy issues and communicates

appropriately

Business Analystsoutline business processes as „not

implemented‟test cases

Agile SOA takes Collaboration


Collaboration at Business Process level


Production

Staging

Co

nti

nu

ou

s S

OA

Test

Pla

tfo

rm

Test Bed

Dev Build

Test Bed

Dev Build

Product Component

QA/QE

Productio

n

Pre-

production

Component/Service Teams

Developmen

t

Product Component

Continuous

Validation

Continuous

Regression

Testing

Team to Team Collaboration


Presentati

on Layer

Service/Proce

ss Layer

Integration

Layer

Data/

Applications

web UI Swing UI web 2.0 UI

CORBA J2EEWeb Service

BPM

ESB

Java

Web Service

RMI CustomBatch Feeds

LegacyCustom Apps

DatabaseFile System

Packaged Apps

Complete SOA Testing - Simplified


OrderingSwing App

Processing Web App

CORBA App

ESB

Business Process App

A

Business Process App

B

Additional Apps Now &

Future

Database

Database

App ServerEJB, WS,

POJO

Problem may not appear for

end usersProblems will not

appear in XML from SOAP

Error in message layer

1

2

3 4

5

6

7

8

9

Validating Complex, Distributed Systems


Contention for Shared Resources

Live services are not always available for dev & testing

Administrators control or prohibit access to prevent overload

and downtime

Multiple dev & test teams create scheduling conflicts for

access to key systems

Traditional Dev & QA =Centralized Control, Longer Cycles

Dev team

Mainframe

Clienttest team

SOA Development = Constrained by Access

Dev & Test teams

Mainframe

IT Ops control

Live or Synthetic Transactions


Some improvement, but dependencies on finished services still limit agility

downtime

downtime

downtime

Dependencies in Development Cycles

Team1

Team2

Integration

Team/QA3

Completed

Completed

Completed

Tested

DeliveredFunctionality

PROJECT TEAM

Define

Conventional “Waterfall” development cycle…

Attempt to break up SOA development to distributed teams


Develop Test Integrate Deploy

Dependency

Dependency

Dependency


Expense of Test Data Creation

Customer Data

Transactional Data

Service Metadata

TestProcess

Yo

ur

Syst

e

m

i

T

KO

L

I

SA

Connect

Gather info

Invoke

Get response

React

Steps

Yo

ur

Syst

e

m

i

T

KO

L

I

SA

Connect

Gather info

Invoke

Get response

React

Steps

Yo

ur

Syst

e

m

i

T

KO

L

I

SA

Connect

Gather info

Invoke

Get response

React

Steps

Yo

ur

Syst

e

m

i

T

KO

L

I

SA

Connect

Gather info

Invoke

Get response

React

Steps

Test Context

• Creating realistic, repeatable test scenarios for SOA represents a huge data maintenance effort

• Changing behavior of services makes test data brittle


Virtualization ExampleEliminating Dependency on Live Apps, Data & Components

Ordering

Swing App

Processing

Web App

CORBA

App

ESB

Business

Process App

A

Business

Process App

B

Additional

Apps Now &

Future

Database

Database

App Server

EJB, WS,

POJO

Load &

Performance

Testers

Component

Developers &

Testers

LISA VSE


Performance Management in SOA requires

Collaboration

Verify

Lookup

QuoteSolution

Test: 4.0

Seconds

Without Component-Level Performance Testing

With Earlier Component-Level Performance Testing, Deliver with Less Risk

Timeline 8 mo. 9 mo. PROJECT DUE

Add more Hardware!

Test3.2

Seconds

SLA2.1 seconds

Verify

Lookup

Quote

Solution

0.5s 0.3s

0.5s

1.2s

Test:2.1

Seconds

0.5s

1.2s1.9s

0.3s


Time saveddowntime

downtime

Agility with Validation & Virtualization

Data Svc

OrderMgmt

Integration/Perf.

PartnerPortal

Completed

Completed

Completed

Tested

Original SOADelivery Date


ConventionalDelivery Date

Team producing a service can provide a Virtual Service

earlier in development to allow earlier access by other

dependent teams

Team consuming a service can capture and model a current

or incomplete Service as a Virtual Service


iTKO: Our Solution - LISA

Testing

• Complete

• Collaborative

• Extensible

Validation• Continuous

• Functional Monitoring

• Policy Validation

• Proactive Alerting

Virtualization

• Constraint Simulations

• Eliminates Dependencies

• Complete Environment

• Supports Load

• Pass thru mode


Summary: iTKO LISA

Complex SOA Dependencies and Rate of Change are

causing Increase in Business Risk

iTKO LISA can help in minimizing this Risk through Best

Practices and Technology

• For more info on LISA‟s SOA Testing, Validation & Virtualization capabilities:• Download Resources:

http://www.itko.com

• John‟s Blog: http://blog.itko.com

• Email: [email protected]

http://www.itko.com/

http://blog.itko.com/


Questions and Answers

Please post your questions now using

the “Ask a Question” box

on left side of the screen

View other Webcasts in the Series at www.cmcrossroads.com/wc

agile development life cycle and soa testing

Documents