accompanying measure in system dependability fp5.8 kaii roadmapping project june 2002 - may 2003

Accompanying Measure in Accompanying Measure in System DependabilitySystem Dependability

Accompanying Measure in Accompanying Measure in System DependabilitySystem Dependability

FP5.8 KAII Roadmapping project

June 2002 - May 2003

Adelard ARCS CNUCE JRC LAAS Newcastle Univ

PartnersPartnersPartnersPartners

Univ. Newcastle Co-ordinator

Adelard Overall roadmap

ARC Seibersdorf DES Roadmap & workshop

CNUCE/ISTI - Univ. Pisa Partner

JRC Workshops

CNRS/LAAS Partner


ObjectivesObjectivesObjectivesObjectives

• Overall Dependability Roadmap– consult and synthesize from other

roadmapping workshops

• Dependable Embedded System Roadmap• Constituency and Consensus-Building, for • ISDI (Information Society Dependability

Initiative)


DDSI Dependability

policy support

AMSD PositioningAMSD PositioningAMSD PositioningAMSD Positioning

Others…..

AMSDOverall dependability

AMSD dependable embedded

systems

RESETsmartcards

PAMPASmobile

privacy &security

BVNbiometrics

RAPIDprivacy/IdentityMgmt

ACIPcritical

infrastruct.protection

STORKcrypto

ARTISTadvncd.

RT


Achieving Dependable SystemsAchieving Dependable SystemsAchieving Dependable SystemsAchieving Dependable Systems

• The subject of System Dependability needs to be treated holistically, to:• cover all potentially relevant dependability attributes, since a

balance is invariably needed• allow for all types of faults — e.g. intermittent h/w faults, s/w

specification and design faults, human-machine interaction faults including intrusions

• make use of all major means for achieving dependability means (rigorous design, fault tolerance, verification and validation, system evaluation)

• cope with dependability threats (fault/error/failure) “chains” between systems, via system interaction, composition and creation

• overcome various linguistic and cultural divides (e.g. dependability/ security/survivability/trustworthiness) - without necessarily imposing a common culture and terminology


Overall Dependability RoadmapOverall Dependability RoadmapOverall Dependability RoadmapOverall Dependability Roadmap

• Aims to cover both technical and socio-technical issues, and a broad range of systems.

• Material from all the more-focussed road-maps will be consolidated, so as to identify commonalities, tensions, and contradictions (as well as opportunities for synergy)

• This will use the taxonomies and classifications of dependability developed by IFIP WG 10.4 (Dependability and Fault Tolerance) as the conceptual framework


Target domainsTarget domainsTarget domainsTarget domains

Autonomic, self healing systemsBiometricsConsumer, network enabled devicesCryptography Critical systemsFault Tolerance Dependable Embedded Systems Early Warning and Information Sharing Evidence/ForensicsHuman FactorsInterdependencies (technological and sociological)

IT & Law (European and International)

Large scale bounded systems (enterprise) Large scale unbounded (infrastructure)Middleware for critical systemsMobile computing, Grid, P2PNanotechnologyPrivacy and Identity ManagementReliability, etc.SafetySmart CardsSurvivabilityTrust in e-BusinessSecurity


Dependable Embedded Dependable Embedded System RoadmapSystem Roadmap

Dependable Embedded Dependable Embedded System RoadmapSystem Roadmap

• application assessment (analysis of the different application domains)

• technology assessment (study of the available performance and cost predictions of the enabling technologies, namely semiconductors, communications, dependability, and real-time system and software development)

• analysis of the resulting technology/application matrix to identify which fields particularly merit further work, leading to

• establishment of a research agenda


Roadmap progress and Roadmap progress and plansplans

Roadmap progress and Roadmap progress and plansplans

DES RoadmapJul 02 Initial working doc

(structure & method)

Nov/Dec Draft roadmap

Feb 03 Final roadmapMay Final report

Overall RoadmapSep 02 Elicitation

frameworkOct Strawman

roadmap

Dec Draft roadmap(full distribution)

Jan03 ConsultationMar Final roadmapMay Final report


WorkshopsWorkshopsWorkshopsWorkshops

• R&D in Information Infrastructure and Dependability– Sept 19-20, Brussels (with DDSI, ACIP)

• Dependable Embedded Systems– Oct 3, Grenoble (with ARTIST)

• Privacy and Identity Management – Oct 17-18, Zurich (with RAPID)

• Trust and Security in e-business Processes– Dec 5-6, Brussels (with PAMPAS, RESET)

• AMSD cross-sector workshop - Feb 2003– Feb 2003 (with other roadmaps - technology & applications)


Roadmap - proposed outlineRoadmap - proposed outlineRoadmap - proposed outlineRoadmap - proposed outline

• Introduction• Method of working• Vision – user centred• Vision – sector and technology based• Synthesis and discussion• Conclusions• Glossary, acronyms• Bibiliography• Appendices


Method of workingMethod of workingMethod of workingMethod of working

• workshops and other RoadMaps• interviews/consultation• analysis and scenario development of FP6 CEC

documentation (ISTAG, eEurope etc)• appraisal of external Roadmaps (e.g. EWICS,

software engineering, dist computing SOTA ...)• AMSD and other workshop outputs• appraisal of FP5.8 Roadmaps and Embedded

Systems one (draft due month 5)• support for DeFINE and DeSIRE• AMSD cross-sector workshop - Jan 2003


Vision – user centredVision – user centredVision – user centredVision – user centred

• Based on user scenarios from ISTAG and the AMI visions.

• Analysis using conventional dependability notions augmented with concepts from:•home technology (other important dependability attributes like

“fun”, “friendliness”, “flexibility”)•ethnographic insights from grid/group analysis

• This may lead to an abstract description of middleware including abstract services, architecture and attributes.

• Dependability discussion/mapping against technology & sector from other roadmaps


• Vision – sector and technology basedVision – sector and technology based• Vision – sector and technology basedVision – sector and technology based

This is the vision coming from the various workshops and sector based activities. We would expect an outline of:•market and application drivers•technology drivers•existing landscape•summary of 2010 vision and landscape

Progress issues: availability of other (draft) Road maps

Due: ?


SynthesisSynthesisSynthesisSynthesis

• This would include:•the dependability vision

• some unified view of the sector and technology based landscapes – trends, barriers, strategies

•what 2010 might look like (and further afield)

•how to get there – may be supporting SWOT analysis

•Take ERA into account


ISDIISDIISDIISDI

• Ideally, the coherent dependability initiative in FWP6, encompassing a full range of dependability-related activities, e.g. – R&D, and tools/methods etc. on the various aspects of

dependability per se, (reliability, safety, security, survivability, etc.);

– education and training; and – means for encouraging and enabling sector-specific (IST) R&D

projects to use dependability best practice.

• A core IP (DeSIRE) and NoE (DeFINE) , linked through cooperation and overlapping workpackages to other IPs, NoEs (& traditional instruments) with dependability concerns


International Working ConferenceInternational Working ConferenceInternational Working ConferenceInternational Working Conference

• March 2003• Promote inter-community working• Industry, government, academia, policy• EU + accession states• (Some) US, Australia, NZ,...• Establish broad dependability consensus

– working towards a cross-sector dependability culture

• Gain political support for ISDI


AMSD Advisory BoardAMSD Advisory BoardAMSD Advisory BoardAMSD Advisory Board

Prof. Martyn Thomas - Independent Consultant (UK) - ChairmanDaniel Bois, Senior Vice President of Corporate R&D, Gemplus International (F)Guy Carrere, Director of Research, France Telecom R&D (F)Wolfgang Merker, Vice-President, Research Information and Communication,DaimlerChrysler AG (D)Dr Sergio Montenegro, Manager for Embedded and Dependable Systems, GMD Fraunhofer - Institute for Computer Architecture and Software Technology (A)Dr. Michele Morganti, Director Strategic Planning, Siemens (I)VD Dipl.-Ing. Reinhard Petschacher, CTO, Infineon Technologies (A)Gérard Roucairol, Vice-President for Research and Development, Bull (F)Dr. Rob Witty, Chief Technical and Programmes Officer, National Air Traffic Services (UK)


AMSD Technical BoardAMSD Technical BoardAMSD Technical BoardAMSD Technical Board

• Senior technical representatives– industry, academia, government, policy

• Advice on overall position, and specific technical expertise

• Direct consultation• Review of materials produced• Attendance at workshops• > 45 members, by invitation


AMSD AffiliatesAMSD AffiliatesAMSD AffiliatesAMSD Affiliates

• Broad representation• Cross community• Open to all• Review of published/draft materials• >100 members


ContactsContactsContactsContacts

• Coordinator - Newcastle University– <[email protected]> (Scientific)– <[email protected]> (Admin)

• Overall roadmap - Adelard (and apps workshop)– [email protected]

• DES roadmap & workshop - ARCS– [email protected]

• Workshops - JRC– [email protected] (Trust in e-Business, Privacy)– [email protected] (Critical Infrastructure)

accompanying measure in system dependability fp5.8 kaii roadmapping project june 2002 - may 2003

Documents

system interaction

system evaluationcope

system dependabilityfp5

realtime system

design faults

types of faults

intermittent hw faults

broad range of systems