The tale of three ATAMs ... Dr. Andrzej J. Knafel Stage & - - PowerPoint PPT Presentation
The tale of three ATAMs ... Dr. Andrzej J. Knafel Stage & Prologue: Scenery, Actors, Use Cases, History Act 1: ATAM of the "Old System" Act 2: ATAM of the "Reference Architecture" Act 3: ATAM of the "Implementation
2
Business applications at Roche enterprise as sources or destinations of data and interactions … … connect through Roche intranet, services, Internet and customer ´s IT with … … Roche medical systems (devices) located at clinical laboratories worldwide.
3
Person icon made by Freepik from www.flaticon.com 4
1. Device locations – Worldwide
– Various maturity of IT environment
2. Connectivity – Number of connected devices: n x 106 – Data volume exchanged:
5
Transfer of data from Roche enterprise applications to the devices
Transfer of data from devices to Roche enterprise applications
Gateway Device Business Applications End-to-End Processes Remote Service Remote Service Apps
⇔ Registration & configuration ← Download data & SW → Upload data ⇔ Remote interaction 6
Epilogue Act 3 Act 2 Act 1 Prologue
ATAM 1 of
+ AIW Improvement of Current Systems “Homegrown”
C
“Commercial”
D
Elaboration of Reference Architecture ATAM 2 of “Reference Architecture” Pre-Selection of Solution and Service Providers ATAM 3 of “Implementation Architecture” Proof-of-Concept Implementation start Months N N+4 N+16 “Homegrown” “Commercial” ATAM – Architecture Tradeoff Analysis Method AIW – Architecture Improvement Workshop
7
Homegrown (2000)
Roche until 2007
>7x original specifications
Commercial (2008)
2014
Future demand
increase load of data
Attribute measures
8
9
# Quality Attributes Risks in System 1 Availability Commercial 2 Reliability Commercial 3 Accuracy 4 Performance / Scalability Commercial Homegrown 5 Interoperability 6 Extensibility / Modifiability Homegrown 7 Maintainability 8 Security
70 Risks
Evaluated 32 scenarios
10
architecture
11
12
– The old “Homegrown” system can handle load ~18x higher than specification – Expanded time window for finding good solution
– Not resolved risks and limitations
13
Business Applications Integration Interfaces to Instrument Applications Cross-cutting Concerns, e.g., Fault handling, Authenticity, Integrity, …
Gateway Device Business Applications End-to-End Processes Remote Service Remote Service Apps
⇔ Registration & configuration ← Download data & SW → Upload data ⇔ Remote interaction
– Patterns solving all major risks from ATAM1 – Technology agnostic – Used in solution & vendors evaluation (part of RFP)
– Organization – Strict governance of
conformance
end-to-end xfer protocol
Response behavior with sender-controlled, time-constrained, multi-level acknowledgment
Gateway - Devices
channels
models for connectivity 14
# Quality Attributes Risks 1 Availability
2 Reliability
3 Accuracy
4 Performance / Scalability
5 Interoperability
6 Extensibility / Modifiability
7 Maintainability
8 Security
23 Risks
Evaluated 38 scenarios
15
– Define “required” SLAs for service provider based on the Quality Attributes – Distribute to pre-selected candidates – Quality Attributes (incl. scenarios) – Reference Architecture – Required SLAs – Commercial requirements (responsibility outside of Architecture dept.) – Assess implementation architecture based on pre-defined evaluation criteria
16
17
1. Connection performance of the “last mile” to the customer latency based connection node location 2. Exchange of data with Roche Business Applications deployed – in the same cloud – in the different cloud –
3. SLAs based on Remote Service use cases and not individual services of cloud provider 4. Global availability – conformance to regional & country regulations
18
The Availability, Reliability and Performance of connectivity and data processing are well supported by Cloud technology, if the architecture properly utilizes its capabilities
Apply best cloud practices
Use cloud design patterns
19
– Sequence of events to detect anomalies
– Multi-level commands-response tracking – Time-out tracking
– Real-time security breach detection – Data and identity protection services – Degradation of customer experience
– Multi-alert pattern analysis – Automatic service scheduling
– Notification when diagnostics process is degraded – On-line calculation of statistical parameters
20
Setup 1. Devices (n x 105) simulated by VMs in one cloud environment 2. Prototype of Remote Service in another cloud environment (different technology, different provider) 3. Evaluation of data logs with measurements Results 1. All scenarios fulfilled the required Quality Attributes 2. Some results exceeded the expectations
21
# Quality Attributes Risks 1 Availability
2 Reliability
3 Accuracy
4 Performance / Scalability
5 Interoperability
6 Extensibility / Modifiability
7 Maintainability
8 Security
23 Risks
Evaluated 64 scenarios
22
23
– ATAM1 (“Old System”): Serious technical deficiencies and organizational issues – ATAM2 (“Reference Architecture”): Many unknowns and vendor management – ATAM 3 (“Implementation target architecture”): Migration and Operations
24
ATAM 1 of
+ AIW Improvement of Current Systems “Homegrown”
C
“Commercial”
D
Elaboration of Reference Architecture ATAM 2 of “Reference Architecture” Pre-Selection of Solution and Service Providers ATAM 3 of “Implementation Architecture” Proof-of-Concept Implementation start Months N N+4 N+16 “Homegrown” “Commercial”
ATAM used as evaluation of system development & organizational change
25
26