CGI3: Current Status Common Goals and Infrastructures CGI3: Infrastructure Jonas Mellin

CGI3: Current Status Example Developer of information fusion applications Meet requirements –achieve properties of the system, e.g., reliability performance testability … Available artefacts –products operating systems database management systems network communication UML, C++, … –methods OMT, ROOM, SD, … Requirements Artefacts Application Information fusion common features

CGI3: Current Status Impact of infrastructure The infrastructure has an impact on applications Tandem computing (historical example, Borr 1984) –application running across multiple computers different –operating systems –hardware –programming languages –services must be reliable at first, all failures had to be managed by the application then, they switched to transaction processing (databases) –improved »software productivity significantly (as expected) »average throughput, an unexpected result »smaller footprint, an unexpected result

CGI3: Current Status Emphasis Tools, techniques, methods, and architectural issues –for information fusion application execution (development) (maintenance) In particular –active distributed real-time database management systems

CGI3: Current Status Current investigation Purpose –develop architectures for information fusion infrastructures –toolboxes –operating system features –middleware features testable! –e.g., test critical issues in the wireless sensor network testbed Motivation –CGI3 should serve other scenarios; it has been too narrow –JDL model open for interpretation there may be too much freedom!! –a few more detailed architectures exists: match our req’s? –based on existing technologies

CGI3: Current Status Information fusion infrastructure ? Information fusion research as well as existing applications and infrastructures Database research Real-time systems research Dependability research Distributed systems research data must have temporal validity (information fusion) updating transactions must be timely (real-time databases) require real-time scheduling strategy (real-time systems) require fault avoidance strategy (dependability) is a correctness property (information fusion) require other requirements Example

CGI3: Current Status GQM modeling GQM Modeling is employed –Goal (conceptual) e.g., achieve reliable system from a developers’ perspective –Question (operational level) e.g., is reliability an issue in the application scenario? –Metric (quantitative level) e.g., Yes/No Two iterations –develop/refine GQM –measure applications –classify/categorize –validate/prescribe in 2nd iteration, target projects in which infrastructure is significant

CGI3: Current Status Expected results Information fusion system architecture –services (goals, responsibilities, contracts) –critical services has been/can be tested develop/refine toolbox Improved ontology of IF architecture –precise, unambiguous, established concepts –incorporate established ontologies Interesting research problems –in the gaps between information fusion requirements means (e.g., functions) provided by –different research fields –existing architectures of infrastructures

CGI3: Current Status Summary Emphasis –Tools, techniques, methods, and architectural issues for execution of information fusion applications Currently: broadening scope –Developing requirements of infrastructure –GQM modelling »theory »existing systems Expected results –architecture –improved ontology –research problems Requirements Artefacts Application Information fusion common features