The document discusses agile architecture and its importance in driving business innovation, distinguishing between evolutionary, revolutionary, and disruptive innovation. It emphasizes the need for a well-defined architecture to reduce risks, improve transparency, and facilitate collaboration between business and IT through a structured design process. Agile architecture is framed as a continuous iterative process focused on simplicity, efficiency, and adaptability in response to changing business needs.

1. Click to add Title
Agile Architecture
e-Infochips Institute of Training Research and Academics Limited
Prepared By:
Monika Sanghani
Nirali Savani

2. Motivation
Design Process
Construction Flavor
Conclusion
Takeaways

3. Innovation Drives Business…
• Evolutionary Innovation keeps your business running only and is
not in focus of the business nowadays (e.g. VW Beetle).
• Revolutionary Innovation guarantees nowadays the business success
(e.g. electric car)
• Disruptive Innovation changes existing or creates new markets
causing old business to die (e.g. digital camera).
…and requires supporting IT.
Motivation

4. Revolutionary or Disruptive Driven Business…
• Architecture is the fundamental organization of a system embodied
in its components, their relationships to each other, and to the
environment and the principles guiding its design and evolution.
• Architecture represents the significant design decisions that shape a
system, where significant is measured by cost of change.
• Architecture is non-functional. Architecture is about Quality.
…needs Architecture, Agile Architecture.

5. Architecture Empowers…
• Declarative knowledge is the type of knowledge that is, by its very
nature, expressed in declarative sentences or indicative propositions.
• Declarative knowledge focuses on the answer to the question “why
am I able to do it”.
• Procedural knowledge in opposition focuses on the answer to the
question “how to do it”.
…Declarative Knowledge.

6. The Promise of the Agile Architecture
• Reduction of risks throughout transparency, abstractions and
partitioning.
• Precise definition and understanding of your business.
• Active collaboration of the domain and IT experts on the software
design.
• Clean definition of the boundaries around abstractions.
• Better organization of your enterprise architecture.

7. Agile Architecture Focuses On Simplicity using Transparency,
Abstractions and Partitioning
• Transparency investigates the “as-is” architectural state.
• Abstractions focus using models on the essential architectural
challenges.
• Partitioning creates taxonomy for grouping architectural elements.
…Complexity is the Disease , Simplicity is the Cure

8. Transparency Helps to Define As-Is and Desired State.

9. Abstractions Help to Find Solutions to the Real World Problems.

10. Partitioning Helps to Structure the
Functionality of a Software System
• Reduces complexity of any system.
• Closely related to a mathematical
concept known as equivalence
relations.
• The most important equivalence
relation, from the perspective of
enterprise architecture, is synergy.
• Two functions are synergistic when
each requires the other to be effective.
• Synergy is closely related to an inverse
equivalence relation called autonomy.

11. Interaction Between Business and IT Architectures
Design Process

12. Functional Domains Represent the Glue between Business and IT
Architectures

13. Agile Architecture is Based on the Lean Process Principles
• Defer commitment and decide as late as possible
• Deliver as fast as possible
• See and optimize the whole
• Work iterative and incremental

14. How Much Architecture Remains Agile?

15. Agile Architecture in 10 Steps
Are From Design Process :
Step 1: Identification of the Business Domains
Step 2: Creation of a Business Entity Model
Step 3: Creation of the Ubiquitous Language
Step 4: Definition of the Initial Process Architecture
Step 5: Modelling of the Core Business Processes
Step 6: Definition of Vertical Requirements Based on Process Models

16. Are From Construction flavor :
Step 7: Definition of the Bounded Contexts
Step 8: Definition of the BD/QA(Business Domain/Quality Attribute)
Relevancy Matrix
Step 9: Definition of the Solution Strategies
Step 10: Definition of the Building Blocks

17. Agile Architecture is Business Centric
Construction Flavor

18. Agile Architecture Uses Core Concepts of Domain Driven Design
• At the heart of DDD (Domain Driven Design) lies the concept of the
domain model.
• Domain models are typically composed of elements such as entities,
value objects, aggregates, and described using terms from a
ubiquitous language.
• A bounded context is the context for one particular domain model
and defines implementation boundaries.

19. Quality(non-Functional) Attributes that Drive Agile Architecture
• Performance and Scalability -ability of asystem to predictably
execute within its mandated performance profile and to handle
increased processing volumes in the future.
• Availability and Resilience -ability of a system to be fully or partly
operational as and when required and to effectively handle failures
that could affect system availability.
• Evolution-ability of a system to be flexible in the face of the
inevitable change that all systems experience after deployment,
balanced against the costs of providing such flexibility.
• Security-ability of the system to reliably control, monitor, and audit
who can perform what actions on which resources and the ability to
detect and recover from security breaches.

20. Solution Strategies Are Backbone of the Agile Architecture
• Solution strategies are core concept of the agile architecture due their
focus on business value delivered by the solution.
• Solution strategies allow proper reasoning about architecture
describing internal structure of the elements and collaboration
between them.
• Best created using composite UML diagram type.

21. Building Blocks Make Business Architecture Part of IT
• Building Blocks are counterparts to the Solution Strategies
• They focus on the technical design used where it should have most
pay-off
• Similar to the solution strategies, building blocks describe elements
and their relations
• Best created using components UML diagram type

22. Agile Architecture Process Summary Review, Refine & Extend,
Repeat

23. Agile Architecture : Takeaways

24. Thank you