cgi3: current status 2007-09-271 common goals and infrastructures cgi3: infrastructure jonas mellin

CGI3: Current Status 2007-09-27 1

Common Goals and Infrastructures

CGI3: Infrastructure

Jonas Mellin


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

ApplicationInformation fusion common features


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


Emphasis

• Tools, techniques, methods, and architectural issues – for information fusion application

• execution• (development) • (maintenance)

• In particular– active distributed real-time database

management systems


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


Information fusion

infrastructure

?

Information fusionresearch as well asexisting applications andinfrastructures

Databaseresearch

Real-time systemsresearch

Dependabilityresearch

Distributedsystemsresearch

data must havetemporal validity

(information fusion)

updating transactionsmust be timely

(real-time databases)

require

real-timescheduling

strategy(real-time systems)

require

fault avoidancestrategy

(dependability)

is a

correctnessproperty

(information fusion)

require otherrequirements

Example


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


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


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

ApplicationInformation fusion common features

cgi3: current status 2007-09-271 common goals and infrastructures cgi3: infrastructure jonas mellin

Documents