The document discusses enabling mobility through continuous delivery. It describes challenges with past integration projects due to lack of version control and dependencies. Continuous delivery is presented as enabling agility, reducing time to market, and increasing quality through automation of testing, deployment, and other processes. Continuous delivery is proposed as a way to prepare organizations for increasing mobile needs by saving time and money while improving quality.

1. 1
©Connecta -ConfidentialEnabling mobilitythrough Continuous Delivery
Connecta
Stockholm, 2013-11-20

2. 2
©Connecta -ConfidentialDEVELOPERCONTINUOUSMICHAEL MEDINdeliveryOUTSIDE THE BOX

3. 3
©Connecta -ConfidentialPlatinumGoldSilverRemarketer2009201020112012Fusion MiddleWare: Partner of the year20122013Fusion MiddleWare: Most Certified Implementation SpecialistsSpeaker and Keynoteat many Conferences and Partner Events

4. © Connecta - Confidential 4
Service Oriented Architecture
Application Integration Architecture
WebLogic/Application Grid
Siebel CRM
CRM On Demand

5. 5
©Connecta -ConfidentialMatts JöhnckeICA ABInfrastructure ServicesTeam lead -developmentConfiguration manager

6. 6
©Connecta -ConfidentialMOBILE

7. 7
©Connecta -ConfidentialMOBILEIs hereTime To MarketCompetitionInternetOut-sourced

8. 8
©Connecta -ConfidentialMOBILEIs hereWill happen to YOUBePrepared10x traffic

9. 9
©Connecta -ConfidentialMOBILEAgility is keyTime To MarketBePreparedNo time to think

10. 10
©Connecta -ConfidentialMOBILEPrestige projectsCompetitionKey stakeholdersBePrepared

11. 11
©Connecta -ConfidentialMOBILESecurity nightmareInternet24x7 uptimeBePrepared

12. 12
©Connecta -ConfidentialMOBILENew technologyOutsourcedNew requirementsBePrepared

13. 13
©Connecta -ConfidentialYour mission: Cloud provider… …in 3o days… …tomorrowNo won’t be an optionBePrepared

14. 14
©Connecta -ConfidentialArchitectureSOACloudRestMobile

15. © Connecta - Confidential 15
Mobile Enablement
SERVICE VIRTUALIZATION & MEDIATION
MAINFRAME
Oracle Service Bus Oracle API Gateway
Web Desktop Servers B2B Cloud Mobile
access management
security
API rest
soap service Web-

16. © Connecta - Confidential 16
What’s behind the box?
SERVICE VIRTUALIZATION & MEDIATION
MAINFRAME
Oracle Service Bus Oracle API Gateway
Web Desktop Servers B2B Cloud Mobile
API GW
Service bus
SOA BPM AIA ???
Repository
Security
DMZ, Security, Control
Virtualization, Versioning, Transformation
Services, Composite Applications
Common Security Framework
Reuse, Governance

17. 17
©Connecta -ConfidentialDELIVERYCONTINUOUSTHEORY

18. 18
©Connecta -Confidential1990: Classic software developmentGather RequirementsWrite SpecificationBuild softwareTest softwareDeliver SoftwareAcceptance TestDone

19. 19
©Connecta -Confidential2000: Iterative projects
Gather Requirements
Write Specification
Build software
Test software
Deliver Software
Acceptance Test

20. 20
©Connecta -Confidential2000: Modularized architectureFrontendBusiness logicBackend

21. 21
©Connecta -Confidential2000: Agile projectsnot code
Gather Requirements
Write Specification
Build software
Test software
Deliver Software
Acceptance Test

22. 22
©Connecta -Confidential2000: Waterfall WaterfallsFrontendBusiness logicBackend

23. 23
©Connecta -ConfidentialINTEGRATIONCONTINUOUS

24. 24
©Connecta -ConfidentialCONTINUOUSINTEGRATION

25. 25
©Connecta -ConfidentialContinuous Integration
Code
Integrate
Build
Test

26. 26
©Connecta -Confidential2010: Enterprise Development
Code
Integrate
Build
Test
Code
Integrate
Build
Test
Code
Integrate
Build
Test
Code
Integrate
Build
TestMobileIntegrationERPCRM

27. 27
©Connecta -Confidential2020: Agile Enterprise Software development
Code
Integrate
Build
Test
Code
Integrate
Build
TestMobileERP
Code
Integrate
Build
Test
Code
Integrate
Build
TestCRM
Code
Integrate
Build
TestIntegration

28. 28
©Connecta -ConfidentialDELIVERYCONTINUOUS

29. 29
©Connecta -ConfidentialContinuous Delivery
Code
Integrate
Build
Unit-test
Deploy
Acceptance/ Integrationtest
Release

30. 30
©Connecta -ConfidentialHow about mobility?
Mobile client
Oracle API GW
Service bus
SOA
System A
System B
Code
Integrate
Build
Test
Code
Integrate
Build
Test
Code
Integrate
Build
Test
Code
Integrate
Build
Test
Code
Integrate
Build
Test
Code
Integrate
Build
Test

31. 31
©Connecta -ConfidentialDELIVERYCONTINUOUSPRACTICE

32. 32
©Connecta -ConfidentialAUTOMATECodeTestReleaseInstallConfigurationDeployAcc. TestMigrationEverything

33. 33
©Connecta -ConfidentialPIPELINEDEPLOY
WORKFLOW

34. 34
©Connecta -ConfidentialORACLEWLSTANTMavenTemplatesSilent Installers(Maven)

35. 35
©Connecta -ConfidentialDELIVERYCONTINUOUSCOST

36. 36
©Connecta -ConfidentialFREEPays it selfThere is a free lunch!

37. 37
©Connecta -ConfidentialAccumulated cost for delivery
0
20
40
60
80
100
120
140
1
2
3
4
5
6
Automated
Manual

38. 38
©Connecta -ConfidentialProject cost after implementing Continuous Delivery
0
50
100
150
200
250
300
350
400
Project A
Project B
Project C
Project D
Project E
Hours

39. 39
©Connecta -Confidential
Practice
Build management and CI
Environments and deployment
Release management
Testing
Data management
Configuration Management
Level 3 – Optimizing: Focus on process improvement
Teamsregularly meet to discuss integration problems and resolve them with automation, faster feedback, and better visibility
All environmentsmanaged effectively. Provisioning fully automated. Virtualization used if applicable.
Operations and delivery teams regularly collaborate to manage risks and reduce cycle time.
Productionrollbacks rare. Defects found and fixed immediately.
Release to release feedback loop of database performance and deployment process
Regular validation that CM policy supports effective collaboration, rapid development, and auditable change management processes.
Level 2 – Quantitatively managed: Processmeasured and controlled
Build metrics gathered, made visible, and acted on. Build s are not left broken.
Orchestrated deployments managed. Release and rollback processes tested.
Environment and application health monitored and proactively managed. Cycle time monitored.
Quality metrics and trends tracked. Non functional requirements defined and measured.
Database upgradesand rollbacks tested with every deployment. Database performance monitored and optimized.
Developers check in to mainlined at least once a day. Branchingonly used for releases.
Level 1 –ConsistentAutomated processes applied across whole applicationlifecycle
Automated build and test cycle very time a change is committed. Dependenciesmanaged, Re-use of scripts and tools.
Fully automated,self- service push-button process for deploying software. Same process to deploy to every environment.
Changemanagement and approvals processes defined and enforced. Regulatory and compliance conditions met.
Automated unitand acceptance tests, the latter written with testers. Testing part of development process.
Database changes performed automatically as part of deployment process.
Libraries and dependenciesmanaged. Version control usage policies determined by change management process.
Level0 – Repeatable: Process documented and partly automated
Regular automated build and testing. Any build can be re- created from source control using automated process.
Automated deployment to some environments. Creation of new environments is cheap. All configuration externalized / versioned
Painful and infrequent, but reliable,releases. Limited traceability from requirements to release.
Automated tests written as part of story development.
Changes to databases done with automated scripts versioned with application.
Version control in use for everything required to recreate software: source code, configuration, build and deploy scripts, data migrations.
Level-1 – RegressiveProcesses unrepeatable, poorly controlled, and reactive
Manual process for building software. No management of artifacts and reports.
Manual process for deploying software. Environment-specificbinaries. Environments provisioned manually
Infrequent and unreliable releases.
Manual testing after development.
Data migration unversionedand performed manually.
Version control either not used, or check-in happens infrequently. Capability Maturity ModelLevel Dependenciesmanaged, Re-use process for deploying Process automated process.
environments is cheap. All provisioned manuallyLevel 1
ConsistentAutomated processes applied across whole applicationlifecycle
Automated build and test cycle very time a change is committed. of scripts and tools.
Fully automated,self- service push-button software. Same process to deploy to every environment. Level0
Repeatable: documented and partly automated
Regular automated build and testing. Any build can be re- created from source control using Automated deployment to some environments. Creation of new configuration externalized / versionedLevel-1
RegressiveProcesses unrepeatable, poorly controlled, and reactive
Manual process for building software. No management of artifacts and reports.
Manual process for deploying software. Environment-specificbinaries. Environments manually

40. 40
©Connecta -ConfidentialTHE JOURNEY

41. 41
©Connecta -ConfidentialFusion2011: The beginning of a long integration journeyOracleMiddlewareODIAIAFileOSBOAGOERHarvester

42. 42
©Connecta -ConfidentialChallengesVersion “control”Ill suitedRace conditionsAIAWorkbenchProcessDependenciesPoint-to-pointNorwaySwedenFinlandIndiaExpertise

43. 43
©Connecta -ConfidentialFLOWNOT PRODUCTPROCESS

44. 44
©Connecta -ConfidentialDELIVERYCONTINUOUSBENEFITS

45. 45
©Connecta -ConfidentialAgilityTime To MarketIterativeStressincreasedreduceddevelopmentfreeQualityincreased

46. 46
©Connecta -ConfidentialTHROUGHMOBILITYENABLINGDELIVERYCONTINUOUS

47. 47
©Connecta -Confidential
Time
Money
QualityAUTOMATESAVEMONEYSAVETIMEINCREASEQUALITY

48. 48
©Connecta -Confidential
Time
Money
QualityYES WE CAN

49. 49
©Connecta -ConfidentialBePreparedFOR MOBILE

50. 50
©Connecta -ConfidentialTHANK YOU

51. 51
©Connecta -ConfidentialOur job is to automatebusiness processes. Why do we do thismanually?