The software development ecosystem exists in a state of dynamic equilibrium, where any new tool, framework, or technique leads to disruption and the establishment of a new equilibrium. Predictability is impossible when the foundation architects plan against is constantly changing in unexpected ways. It’s no surprise many CIOs and CTOs are struggling to adapt, in part because their architecture isn’t equipped to evolve. This webinar will discuss what’s at stake if companies continue to use long term architecture plans.

1. BuildingEvolvable
Architectures
Dr. Rebecca Parsons
Chief Technology Officer
@rebeccaparsons

2. WhyshouldIcare
aboutevolutionary
architecture?

3. We’reactuallypretty good
atrequirementschange.
But….

4. Whatabout
ecosystemchange?

5. Howdowemaintainthis
dynamicequilibrium?

6. Whatisevolutionary
architecture?

7. Anevolutionaryarchitecture
supportsguidedincremental
changeacrossmultiple
dimensions.

8. Anevolutionaryarchitecture
supportsguidedincremental
changeacrossmultiple
dimensions.

9. Anevolutionary
architecturesupportsguided
incrementalchangeacross
multipledimensions.

10. Anarchitecturalfitness
functioncharacterizeshow
closeasystemistothedesired
architecturalcharacteristics.

11. Anevolutionary
architecturesupportsguided
incrementalchangeacross
multipledimensions.

12. Twoaspectsof
incrementalchange-
applicationsand
operations

13. Anevolutionary
architecturesupportsguided
incrementalchangeacross
multipledimensions.

14. -ilities
accessibility
accountability
accuracy
adaptability
administrability
affordability
agility
auditability
autonomy
availability
compatibility
composability
configurability
correctness
credibility
customizability
debugability
degradability
determinability
demonstrability
dependability
deployability
discoverability
distributability
durability
effectiveness
efficiency
reliability
extensibility
failure
transparency
fault-tolerance
fidelity
flexibility
inspectability
installability
integrity
interchangeabilit
y
interoperability
learnability
maintainability
manageability
mobility
modifiability
modularity
operability
orthogonality
portability
precision
predictability
process
capabilities
producibility
provability
recoverability
relevance
repeatability
reproducibility
resilience
responsiveness
reusability
robustness
safety
scalability
seamlessness
self-sustainability
serviceability
supportability
securability
simplicity
stability
standards
compliance
survivability
sustainability
tailorability
testability
timeliness
traceability
transparency
ubiquity
understandability
upgradability
usability
evolvability

15. Principles

16. PRINCIPALS OF EVOLUTIONARY ARCHITECTURE
• Last responsible moment
• Architect and develop
for evolvability
• Postel’s Law
• Architect for testability

17. Lastresponsiblemoment.

18. Architectanddevelop
forevolvability.

19. Postel’sLaw

20. Architectfortestability.

21. Techniques

22. TECHNIQUES OF EVOLUTIONARY ARCHITECTURE
• Database refactoring
• Choreography
• Contract testing
• Continuous Delivery

23. Databaserefactoring

24. Choreography

25. Contracttesting

26. ContinuousDelivery

27. AddressingTechnical
Debt

28. Variesbyformof
debt….

29. …butfundamentally
aboutsafechanges

30. Specific Approach to Legacy Tech Debt
• Define your architectural fitness function
• Select a dimension you’re most worried about
• Start improving on that dimension
• Focus on what matters most
• Monitor trends, adapt and repeat

31. Different
architectureshave
differentevolvability

32. TeamStructure

33. Conway’sLaw

34. Governance

35. Fitnessfunction
driven

36. Outcomesnot
implementations

37. Thankyou.
Dr. Rebecca Parsons
Chief Technology Officer
@rebeccaparsons