Evolving Systems by Igor Schagaev

www.it-acs.co.uk, info@it-acs.co.uk

Evolving Systems: Fundamental Reasoning from amoeba to human designs

Potential customers :

This is true for amoeba...

Evolving Systems: Fundamental Reasoning from Amoeba to human

This is true for amoeba…

NOT FOR

OUR DESIGNS

!!!!

Case studies Properties required (for design, development, analysis, life cycle) Models, Methods, Tools required, or applicable Gain achievable

What for? : - there is a need to detect paradigm (scientific, technological. moral, social) shifts as

soon as possible,- to define areas of research with high efficiency and outcome and declining ones

Both must be done ASAP, AGAP and ALAP (as soon and as global and local as possible) Importance? See “ The Choice of technology” V Leontieff

Evolving Systems: the essential steps

Potential customers :

Human race Industries Researchers Governments? Not sure…

Fine tuning of human progress Rigor of paradigm shift for new technologies New application domain discoveries Cross-domain discoveries

Reasoning :

Evolving Systems Plan Evolving system science

Aerospace

Monitor of active system safety

Prototype of active system control

Method of ActiveSystem Control

Active black box

Real-time maintenance

Evolving Delivery

Evolving AssessmentEvolving

KnowledgeAggregation

EducationLife?

Definition(s)?

Nature

Repeatability

Redundancy

Evolvement

Recoverability

Economics

Project life cyclemonitor

Analytic

Feedback models:

Full, limited

Simulation

life cycle econometrics

Methods

Application

System software

Interaction fabric

Computer science

Dual stringRecoverable

data structures

Searching & recovery algorithmsLanguage

Run-time system

FT semaphoresNew control operators

Syndrome

PRE monitors

Hardware Active zone Passive zone

System memory

User memory

LU AU

T-logic

Math

Control-Data--Predicate

model Graph-Logic Model

Dependency Matrixes Model

Evolving Systems. Good examples of our ignorance: Aerospace

Evolving Systems: Good examples of our ignorance: Aerospace -1A

Government Industries Investment Funds

Timing :

Leak

Flight data recording(on ground) Leak visual manifestation

Accident

72 seconds

Time for possible emergency reconfiguration and recovery of

Challenger to safe state

FLIGHT(blast off)

Flight able to continue in a safe state after recovery operation

10 seconds

Even available system reconfigurability was not applied when required.

Evolving Systems: Good example of our ignorance: Econometrics & SE

Project phase dependencies became complex, amount of data about project required big data initiatives, data centers and… and we invent … the Agile technology? (39Millions links!)

ba c d

ba c d

this

Due to evolving property of alive object becomes that:

Project life cycle :

Quantitative problem caused qualitative solutions? 30 + properties, mutually exclusive and uncertain can make a project efficient? Whom are we kidding?

NB.” Fresh air” is still available – see WorldComp15 “Quantitative Software Engineering”

And actually that – when phases repeated/evolved internally and project flow looks like that:

Evolving Systems. Good examples of our ignorance: High Education

Handling this in real time – upgrading every year?

https://www.academia.edu/7114207/Essential_Knowledge_Aggregation_Delivery_and_Assessment

Evolving Systems. Good examples of our ignorance: High Education

Brain modeling for the purpose of education? Improvement? Efficient use? Neither EC nor US “superbrain” programs have nothing in common to this picture

https://www.academia.edu/7114207/Essential_Knowledge_Aggregation_Delivery_and_Assessment

Change in size, power, reducing or gaining new properties and functions Cost depends on amount of resources ( redundancies ) spent to implement change Redundancy can be “natural”, i.e. existing in the system for the reason we are not

aware of, RN and “introduced” redundancy RI

For our systems (ICT) RI can be of 3 types Structural, Time, Information: RI (S,T,I)

Evolving Systems at Large - System Level

Natural systems are evolving; how to describe evolvability:

statically (when we design – at project/design phase) dynamically (during operation /functioning – when properties are changing)

How our theories/models must be modified to reflect

The real, physical, chemical properties, not math models we use (cause we know) Can we modify theory accordingly the real need not our convenience…

Evolving Systems at Large: The need of new theory and methods

Potential starting points :

Categories Graph theory Markov processes Control theory Dependency studies (Aristotle, DaVinci)

Redundancy Theory Graph Logic Model Dependency Matrix Model Control-, Data-, Predicate-models

Reasoning :

Evolving Systems at medium –Models: Redundancy& GLM

Real-time GLM:

Design time – Dependency Matrix (DM):

Any new property of a system is a sequence of steps A-G…

Redundancies might be used a-la best fit 4 a step

Link dominates node Leaving ≠ Incoming conditions Each link attributed by LO- and LO+

Evolving Systems at medium – RT Models – Dependency Matrix DM3

Real-time – control loop

FX Y

feedback

Dependency Matrix (DM):(using aircraft as an example)

X now is X (x1,x2,…xN) and {x} are not longer independent

F is changing (evolving as properties of an object modify)

Physical dependencies of an object are also evolving and this process must be detected and addressed in RT

Evolving Systems DM3: aircraft real-time active system control

it works together and active system control with imbedded evolvement is much

closer to reality than existing schemes or theories and as we already wrote:

The power of any theory is in predictions and our abilities to apply them… .

Evolving Systems DM3: measuring a progress

Real time predictions and control before anything happen; gain in efficiency 20%, safety an order of magnitude.

Evolving Concept in Computer Architecture and System Software

Evolving Concept in System Software: Language

Upgrading data and control structures

See more in our book: http://www.springer.com/gb/book/9783319294636

Evolving Concept in System Software: Programming, LanguageRestructuring program schema graphs ( C,D,P)

See more in our book: http://www.springer.com/gb/book/9783319294636

Evolving Concept in System Software User Algorithms - Revamp

See more in our book: http://www.springer.com/gb/book/9783319294636

Making our algorithms evolvable

Evolving Concept in System Software Phases Re-Design

Evolving Concept in Language: Run-Time System Revamp

See more in our book: http://www.springer.com/gb/book/9783319294636

Evolving Architecture: Zones, Interactions, Syndromes

See more : http://www.springer.com/gb/book/9783319150680

Evolving Concept in Computer Architecture:

See more : http://www.springer.com/gb/book/9783319150680

Evolving Systems: Instead of Conclusion

Work done so far: books , patents, papers, prototypes

Next step?: Academia.edu sessions:

https://ec.europa.eu/futurium/en/content/theory-evolving-systems

http://www.springer.com/gb/book/9783319150680

http://www.springer.com/gb/book/9783319294636

https://www.academia.edu/s/4cd5ae8775

Next step?: Future Emerging Technologies Initiative:

https://www.academia.edu/26269108/Principle_of_Active_Condition_Control_Impact_Analysis

https://www.academia.edu/7120548/Method_and_apparatus_of_active_system_safety

What else

?