Complex Systems1

transcript

1 © Emmanuel FUCHS. THALES ATM© Emmanuel FUCHS. THALES ATM

Complex System

Large Distributed Complex System (LDCS) Example: Air Traffic Control Complexity Illustration

Simple Item Combination Exponential Increase Avalanche Effect

Reduce Complexity by Raising Abstraction Using Object Middleware to Reduce Complexity

2 © Emmanuel FUCHS. THALES ATM

Large Distributed Complex Systems

Safety Critical and Real Time Computing Large Distributed Control And Command System

Transportation Control: Rail, Air, Sea Energy: Oil, Nuclear

VersuS Trading System Real Time Operation

VS Enterprise Computing Sales, Accounting Manufacturing Billing

Large Distributed Control and Command System Figures

Safety Critical Reliability : five nines 99.999%

No interruption Integration of several complex domain

skills : Sensors Controls Commands

Size effects: Million of lines of code (Mloc) Life cycle 10 to 20 years.

Complex System

Air Traffic Control

Air Traffic Management System Complexity Several Sub Domains (Complex)

Navigations and guidance RADAR (sensor) Control Centre (control) Air Flow Management (operation) Radio Communication (actuator)

Important Size (Large) Scope: Country Wide, Europe Wide Controller (operator) : 50 to 100 Computer: 50 to 500 2 to 4 Million of Ada and C lines of code 10 to 20 years life cycle

Real Time Computing : ATC center Architecture

Flight PlanProcessingFlight Plan

Processing

SupervisoryControlSupervisory

Control

SimulatorSimulator

RecordingReplayRecording

Replay

controllerWorkingPosition

Radar Data ProcessingRadar Data

Processing

Radar FrontProcessingRadar Front

Processing

Intranet

ATC Internet

controllerWorkingPosition

2 000 KLOCRADAR

Real Time Computing VS Enterprise Computing

ManufacturingManufacturing

Shipping/ ReceivingShipping/

Receiving

AccountingAccounting

Payables/ ReceivablesPayables/

Receivables

InventoryInventory

SalesSales

Intranet

Shipping/ ReceivingInventory

Engineering

Manufacturing

Accounting

Payables/ Receivables

Complex System

Sub system integration

Sub system integration, first evolution

Sub system integration, second evolution

Sub system integration third evolution

Sub system integration composition evolution

Sub system integration after Evolution

Sub system integration after Evolution : Spaghetti plate syndrome

Spaghetti Plate

System Architect System Integrator

Complex System

Complex System Changes Avalanche Effect. In large and complex systems each evolution

increases the system complexity. Each evolution increases the code size, thus increasing

the complexity. Repeated modification has a cumulative effect on system

complexity. The compound impact of many changes is greater

than the sum of the individual changes due to the erosion effect on the conceptual integrity of the system:

Creating avalanche effect then the changes development cost become exponential.

By raising abstraction level Middleware use reduces the system complexity (developed code size reduction).

Complex System

Complex System Product Management

Functional Changes Cost

System Complexity

Functional Changes Code Size

Complexity

Functional upgrade Code Size

Functional upgrade Cost

Complexity avalanche effect

Complex System Product Management

Functional Changes

System Complexity

Functional Changes Code Size

Complexity avalanche effect

Complexity

Functional upgrade Code Size

Functional upgrade Cost

Complex System

Middleware use to decrease Complexity

System Complexity

Complexity

Code Size

Middleware use to decrease ComplexityComplexity

Code Size

Increases Abstraction Level

DecreasesComplexity

DecreasesCode Size

System Complexity

Middleware use decreases ComplexityComplexity

Code Size

DecreasesCode Size

Increases Abstraction Level

DecreasesComplexity

System Complexity

Complex System

Sub system integration with Middleware

Middleware

Sub system integration with software bus

Software Bus

Sub system integration with software bus

Software Bus

Reusable Software components

Complex Systems1

Technology