This document discusses iterative architecture and its benefits for on-time delivery. It defines software architecture and iterative architecture, noting that iterative architecture breaks a system into parts that can be developed and tested incrementally. It then outlines an iterative architecture process, starting with business architecture and requirements before developing solution, application, and runtime architectures through multiple iterations.

1. Itera&ve Architecture :
Your Path to On-Time Delivery
Asanka Abeysinghe
Vice President, Solu&ons Architecture
WSO2, Inc

2. The structure of component, their
interrela&onships, and the principles
and guidelines governing their design
and evolu&on over&me.
Architecture

3. SoGware architecture
The highest-level breakdown of a system into its
parts; the decisions that are hard to change; there
are mul&ple architectures in a system; what is
architecturally significant can change over a system's
life&me.
Mar$n Fowler – Pa.erns of Enterprise Applica$on Architecture
h.p://amzn.to/1pQe39r

4. Highest-level breakdown of a system
h.p://wso2.com/whitepapers/a-reference-architecture-for-the-internet-of-things/

5. Itera&ve architecture from yesterday
Iterative

7. Scrum
h.p://scrumreferencecard.com/scrum-reference-card/

8. Itera&ve architecture: process

9. SAFe : Scaled Agile Framework
h.p://www.scaledagileframework.com

10. Star&ng point : business architecture
Requirements
Current
applica1ons/
systems
Δ Delta

11. Architecture approach
Business
Architecture
Solu1on
Architecture
• Level 0
• Level 1
Applica1on
Architecture
• Integra1on
• Datamodels
• APIs
Run1me
Architecture
• Capacity Planning
• Deployment
• Security

12. Level 0/1

13. What enterprises look like

14. Iden&ty/access control

15. Services

16. Registry, repository, governance

17. Integra&on : internal

18. Integra&on : external

19. APIs and analy&cs

20. Integra&on : pub/sub, even&ng, workflows

21. Filling the blanks

24. Thank You