Towards an Interface Description Template for AI-enabled Systems

Reuse is a common system architecture approach that seeks to instantiate a system architecture with existing components. However, reusing components with AI capabilities might introduce new risks as there is currently no framework that guides the selection of necessary information to assess their portability to operate in a system different than the one for which the component was originally purposed. We know from SW-intensive systems that AI algorithms are generally fragile and behave unexpectedly to changes in context and boundary conditions. The question we address in this paper is, what type of information should be captured in the Interface Control Document (ICD) of an AI-enabled system or component to assess its compatibility with a system for which it was not designed originally. We present ongoing work on establishing an interface description template that captures the main information of an AI-enabled component to facilitate its adequate reuse across different systems and operational contexts. Our work is inspired by Google's Model Card concept, which was developed with the same goal but focused on the reusability of AI algorithms. We extend that concept to address system-level autonomy capabilities of AI-enabled cyber-physical systems.

[1]  Shaukat Ali,et al.  U-Test: Evolving, Modelling and Testing Realistic Uncertain Behaviours of Cyber-Physical Systems , 2015, 2015 IEEE 8th International Conference on Software Testing, Verification and Validation (ICST).

[2]  Alexander Kossiakoff,et al.  Systems Engineering Principles and Practice , 2020 .

[3]  John Leonard,et al.  Systems Engineering Fundamentals , 1999 .

[4]  Alexey Tsymbal,et al.  The problem of concept drift: definitions and related work , 2004 .

[5]  Dominique Ernadote.  Ontology-Based Pattern for System Engineering , 2017, 2017 ACM/IEEE 20th International Conference on Model Driven Engineering Languages and Systems (MODELS).

[6]  Imane Lamrani,et al.  Toward Operational Safety Verification Via Hybrid Automata Mining Using I/O Traces of AI-Enabled CPS , 2020, SafeAI@AAAI.

[7]  Zhitao Gong,et al.  Strike (With) a Pose: Neural Networks Are Easily Fooled by Strange Poses of Familiar Objects , 2018, 2019 IEEE/CVF Conference on Computer Vision and Pattern Recognition (CVPR).

[8]  Bernhard Schätz,et al.  Integrated CPS Research Agenda and Recommendations for Action , 2015 .

[9]  Harini Suresh,et al.  A Framework for Understanding Unintended Consequences of Machine Learning , 2019, ArXiv.

[10]  Jun Han.  A comprehensive interface definition framework for software components , 1998, Proceedings 1998 Asia Pacific Software Engineering Conference (Cat. No.98EX240).

[11]  Gary Marcus,et al.  The Next Decade in AI: Four Steps Towards Robust Artificial Intelligence , 2020, ArXiv.

[12]  Martin Törngren,et al.  How to Deal with the Complexity of Future Cyber-Physical Systems? , 2018, Designs.

[13]  Bran Selic,et al.  Understanding Uncertainty in Cyber-Physical Systems: A Conceptual Model , 2016, ECMFA.

[14]  Julia Rubin,et al.  Fairness Definitions Explained , 2018, 2018 IEEE/ACM International Workshop on Software Fairness (FairWare).

[15]  Leonard E. Miller,et al.  NASA systems engineering handbook , 1995 .

[16]  Inioluwa Deborah Raji,et al.  Model Cards for Model Reporting , 2018, FAT.

[17]  Manfred Broy,et al.  Engineering Cyber-Physical Systems: Challenges and Foundations , 2012, CSDM.

[18]  Rajkumar Buyya,et al.  Mastering Cloud Computing: Foundations and Applications Programming , 2013 .

[19]  Bob Lightsey,et al.  Systems Engineering Fundamentals , 2001 .

[20]  Jim Smith,et al.  An Alternative to Technology Readiness Levels for Non-Developmental Item (NDI) Software , 2005, Proceedings of the 38th Annual Hawaii International Conference on System Sciences.

[21]  Barbara J. Grosz,et al.  Collaborative Systems (AAAI-94 Presidential Address) , 1996 .

[22]  Daniel E. Hastings,et al.  Defining changeability: Reconciling flexibility, adaptability, scalability, modifiability, and robustness for maintaining system lifecycle value , 2008, Syst. Eng..

[23]  Iyad Rahwan,et al.  Cooperating with machines , 2017, Nature Communications.

[24]  James N Martin.  3.1.2 The Seven Samurai of Systems Engineering: Dealing with the Complexity of 7 Interrelated Systems , 2004 .

[25]  Lisa Brownsword,et al.  The Opportunities and Complexities of Applying Commercial-Off-the-Shelf Components , 1998 .

[26]  Andrea Omicini,et al.  Design Patterns for Self-organising Systems , 2007, CEEMAS.

[27]  Razvan Pascanu,et al.  Overcoming catastrophic forgetting in neural networks , 2016, Proceedings of the National Academy of Sciences.

[28]  Danny B. Lange,et al.  Agent design patterns: elements of agent application design , 1998, AGENTS '98.

[29]  Tom De Wolf,et al.  Design Patterns for Decentralised Coordination in Self-organising Emergent Systems , 2006, ESOA.

[30]  Steven D. Eppinger,et al.  Patterns of Product Development Interactions , 2002 .

[31]  Paul Wach,et al.  Constructing True Model-Based Requirements in SysML , 2019, Syst..

[32]  S. Kolassa.  Two Cheers for Rebooting AI: Building Artificial Intelligence We Can Trust , 2020 .

[33]  Walter R. Beam.  Systems Engineering: Architecture and Design , 1990 .

[34]  Daniel E. Hastings,et al.  3.4.1 A Framework for Understanding Uncertainty and its Mitigation and Exploitation in Complex Systems , 2005 .