Evolutionary Development - Design for Change Component Architecture Independence Generic Infrastructure

SANY D2.3.4 Specification of the Sensor Service Architecture V3 Doc.V3.1 Copyright © 2007-2009 SANY Consortium Page 29 of 233

4.1.4 Evolutionary Development - Design for Change

The SensorSA shall be designed to evolve, i.e. it shall be possible to develop and deploy the system in an evolutionary way. The SensorSA shall be able to cope with changes of user requirements, system requirements, organisational structures, information flows and information types in the source systems.

4.1.5 Component Architecture Independence

The SensorSA shall be designed such that a service network and source systems i.e. existing information systems, sensors and sensor networks are architecturally decoupled. This means that the SensorSA shall not impose any architectural patterns on source systems for the purpose of having them collaborate in a service network, and no source system shall impose architectural patterns on a SensorSA. Note: This architectural principle relies on the RM-OA definition of a source system as being a “container of unstructured, semi-structured or structured data andor a provider of functions in terms of services. The source systems are of a very heterogeneous nature and c ontain information in a variety of types and formats”. In the context of a sensor service network, a source system may also be a sensor or a sensor network to be integrated in a service network. Important here is that a source system is seen as a black box, i.e. no assumptions about its inner structure are made when designing a service network.

4.1.6 Generic Infrastructure

The SensorSA services shall be independent of the application domain. This means that the SensorSA services shall be designed in such a flexible and adaptable way that the SensorSA services can be used across different thematic domains and in different organisational contexts, and that the update of integrated components e.g. sensors, applications, systems, ontologies causes little or ideally no changes to the users of the SensorSA services.

4.2. Relationship to the ORCHESTRA Architecture