Applying QAW, ADD and ATAM to conduct the architecture s evolu;on to Service Oriented Architecture. Marcelo Luna Liveware IS Buenos Aires - Argen7na

Transcription

1 Applying QAW, ADD and ATAM to conduct the architecture s evolu;on to Service Oriented Architecture Marcelo Luna Liveware IS Buenos Aires - Argen7na

2 Perito Moreno s Glaciar Patagonia - Argen4na Warming up

3 A really big system 5000 ATM s 14 Million of users Worldwide opera7on through partnerships More than 55 sohware apps Million transac7ons a year

4 Moderniza7on Mo7va7on Solve current problems Build a more adequate Architecture Reduce the gap between Business and Technology Adopt some interna7onal standards

5 THOSE ques7ons How adequate is the current architecture for the business? Which one would be an appropriate architecture for our business expecta7ons? What is the precise scope of architectural changes? How can we build that architecture?

6

7 A complex system a simple strategy Define the Quality Model Capture Architectural Drivers Capture findings Priori7ze problems Future work Understand Evaluate Design Reference Architecture Evolve Understand the Business Mo7va7on Understand the current Architecture Capture Business Objec7ves Define the Reference Define a lifecycle Establish a roadmap

8 Iguazú Falls Misiones- Argen4na Exploring

9 Business Mo7va7on Model

10 Architecture documenta7on

11 archeologized documenta7on

12 Women s Bridge Buenos Aires - Argen4na Crossing bridges

13 Use of QAW - Focus on Business Mo7va7on Coverage Analysis Quality Model

14 BMM Analysis Business Mo;va;on Analysis with Scenarios Scenarios by Goal Tac7cs by Goal Strategies by Goal Quan;ty of Scenarios G02 - Strategic Business Goal G01 - Strategic Business Goal G04 - Strategic Business Goal G03 - Strategic Business Goal

15 Quality Model Time to Market Auditability Reliability Projected Life;me Diagnosability Security 5 0 Availability Reusability Correctness Performance Modifiability Conceptual Integrity

16 Detailed analysis

17 Evalua7on - ATAM

18 Evalua7on findings 16% 13% Documentary Risks 22% 10% Non- Risks Risks Trade- offs 39% Sensi7ve Points

19 The architectural objec7ves Define a Reference Architecture to sa7sfy the detected Architectural Drivers for the General Solu7on Define an Architectural approach for an specific part of de Solu7on, considering a different priority for the Drivers

20 Climbing the Mountain Aconcagua Mountain Mendoza - Argen4na

21 Design - ADD Servicios)de) Front6End Servicios)de) Información Servicios)Core Plataforma)de)Integración Servicios)de)Ruteo Servicios)de) Back6End Servicios)Legacy Seguridad Monitoreo Backup)&)Recovery Reference Architecture Servicios)de)Infraestructura

22 The roadmap to SOA Structure Front0End* Services Informa(on* Services Core* Services Integra(on*Pla-orm Rou(ng *Services Back0End Services Legacy* Services Security Monitoring Backup*&*Recovery Infrastructure*Services

23 The roadmap to SOA - Lifecycle Models Conceptual Governance Architecture Materializa7on Analysis Incep;on Modeling Build Assembly Deploy Business Integra;on Logic Design SoMware Architecture Standardized Contracts SOA Principles Loose Coupling Abstrac;on Reusability Autonomy Stateletssess Discoverability Composability

24 Offline Services alterna7ves Alimentación(de(Información Espacio((Contenedor(Manejado(por(SLA) Unidad(de( procesamiento(a Unidad(de( procesamiento(a Unidad(de( procesamiento(a Datos Mensajería Datos Mensajería Datos Mensajería Master Base(de(datos( externa Porción(de( datos(0 Porción(de( datos(1 Porción(de( datos(2 Instancia(de( función(map(1 Instancia(de( función(map(2 Instancia(de( función(reduce Datos(de(salida Porción(de( datos(n Instancia(de( función(map(n Datos(de(Entrada Fase)map Datos( intermedios Fase)reduce Datos(de(salida

25 Reconver7ng Apps to SOA Reference Architecture Business Services Catalog Expansion Generaliza7on Apps Specializa7on Contrac7on

26 Lighthouse at the End of the World Ushuaia- Argen4na And at the End

27 QAW Current Architecture ATAM ADD BMM Reference Architecture

28 Some conclusions Using the methods in a big and complex business context was really useful The business stakeholders were introduced in architectural ac7vi7es seamlessly The results and the proposed architecture were robustly argued Concepts and principles were introduced to the organiza7on early

29

30 Marcelo H. Luna is a Senior Consultant, specialized on SoHware Engineering prac7ces. He has been working on Liveware IS for 9 years, par7cipa7ng on several projects in Argen7na, Brazil and United Kingdom. As part of Project teams, he have worked on evaluate, design and develop large system s architectures in different domains. Also, he has been teaching SoHware Engineering lectures in different universi7es for 20 years.