OSAMI-D
Encyclopedia
The research project OSAMI-D is the German subproject of the European ITEA 2 project OSAMI
OSAMI
The European research project OSAMI targets open source common foundations for a dynamic service-oriented platform which is able to personalize itself in large diversity of cooperating Software Intensive Systems .According to the vision of this project the relationship between humans, computers...

 (Open Source AMbient Intelligence).

The aim of the international project OSAMI is the design of a basic, widely applicable SOA
Service-oriented architecture
In software engineering, a Service-Oriented Architecture is a set of principles and methodologies for designing and developing software in the form of interoperable services. These services are well-defined business functionalities that are built as software components that can be reused for...

-oriented component platform, its development, test and its provision as open source
Open source
The term open source describes practices in production and development that promote access to the end product's source materials. Some consider open source a philosophy, others consider it a pragmatic methodology...

 software. The project consists of a number of national subprojects, each focussing on a certain field of application. The German subproject OSAMI-D, funded by the BMBF, the German ministry of education and research, under reference number 01 IS 08003, contributes to the e-Health
EHealth
eHealth is a relatively recent term for healthcare practice supported by electronic processes and communication, dating back to at least 1999...

 domain. The main objectives are interoperability, maintainability, reliability, as well as automated configuration and management of medical devices and services to provide new forms of healthcare to diseased and convalescent people. The advantages of these technical contributions will be demonstrated by means of an e-Health application which supports ambulant cardiologic rehabilitation.

The software component platform specified by the OSGi
OSGi
The Open Services Gateway initiative framework is a module system and service platform for the Java programming language that implements a complete and dynamic component model, something that does not exist in standalone Java/VM environments...

 Alliance forms the technical basis of the OSAMI platform. It provides lifecycle management for software components as well as local service interactions as defined in service-oriented architectures and will be combined with the Web Services approach, in particular DPWS
Devices Profile for Web Services
The Devices Profile for Web Services defines a minimal set of implementation constraints to enable secure Web Service messaging, discovery, description, and eventing on resource-constrained devices....

 / WS4D in order to implement distributed, dynamically configurable, vendor-neutral and device-independent solutions.
Project data
Support programme: BMBF IKT2020
Duration: 01.07.2008 - 30.06.2011

General information

The main objective of OSAMI is to connect technologically vertical markets on the basis of open source components and, hence, to facilitate the market entry for small and medium-sized enterprises (SME).

Technical and Scientific Objectives of OSAMI-D

  1. Establishment of the interoperability of medical devices' ensemble
  2. Establishment of the interoperability of medical devices and services for the integrated healthcare in service oriented environments
  3. Policy based configuration and management of adaptive OSAMI-based service systems
  4. Infrastructure for intelligent management and service concepts in OSAMI-based systems

Participants


Work Packages and Tasks

  • WP 1: Coordination and Dissemination
  • WP 2: Business, Trust and Processes (without participation of German subproject)
  • WP 3: Organisation, Tools and Training (without participation of German subproject)
  • WP 4: Vertical Domains - Analysis and Design
    The aim of WP 4 of the German subproject is the requirements analysis particularly for the use of the OSAMI-based services and systems in the application domain "IT in Healthcare" and design of the domain specific components for the OSAMI architecture. The intra-domain "horizontal" architecture design and the actual software implementation take place in WP 5.
  • WP 5: OSAMI Interface & Architecture
    WP 5 concentrates on defining the intra-domain OSAMI architecture considering SOA-principles for distributed, device-based systems and their realization under the Open Source licence model. The architecture is the basis of the implementation of components for the healthcare domain specified in WP 4. Complementary proprietary components and the policy-based management system are produced (ref. e.g. WS-Policy
    WS-Policy
    WS-Policy is a specification that allows web services to use XML to advertise their policies and for web service consumers to specify their policy requirements.WS-Policy is a W3C recommendation as of September 2007....

    ).
  • WP 6: Security, Assets and User interface issues
    Data security, easy integration and management of the external components as well as multimodal and plainly defined user interfaces are important for the acceptance and wide applicability of OSAMI applications. These features set the stage for processing sensitive data and reduce the barriers for deployment.
    The German subproject focuses on the data security for e-Health applications. These applications handle with sensitive, personal data and thus must be reliable. Therefore there are distinct data security requirements, which are to be considered representatively for the requirements for the more sophisticated general applications.
  • WP 7: Demonstrators
    In WP 7 the components of the e-Health demonstrator on the basis of the OSAMI architecture and the results of WPs 4 - 6 are to be integrated. The integrated hard- and software components are to be well tried and proven in a realistic scenario. The evaluation covers the acceptance of the new technologies by end users in addition to the technical requirements.
    The development and the validation of the demonstrator occur in three successive phases. The first phase is intended for the implementation of a so called „mock-up“ with an initial design of the user interface and primary implementation of the corresponding hardware and software components. These form among others the basis for the following phases of the overall project's work plan.

External links

The source of this article is wikipedia, the free encyclopedia.  The text of this article is licensed under the GFDL.
 
x
OK