Fandom

VroniPlag Wiki

Quelle:Saa/Eisenhauer et al 2007

< Quelle:Saa

31.340Seiten in
diesem Wiki
Seite hinzufügen
Diskussion0

Störung durch Adblocker erkannt!


Wikia ist eine gebührenfreie Seite, die sich durch Werbung finanziert. Benutzer, die Adblocker einsetzen, haben eine modifizierte Ansicht der Seite.

Wikia ist nicht verfügbar, wenn du weitere Modifikationen in dem Adblocker-Programm gemacht hast. Wenn du sie entfernst, dann wird die Seite ohne Probleme geladen.

Angaben zur Quelle [Bearbeiten]

Autor     Markus Eisenhauer, Christian Prause, Alexander Schneider, Marius Scholten, Andreas Zimmermann
Titel    Contract No. IST 2005-034891; Hydra; Networked Embedded System middleware for Heterogeneous physical devices in a distributed architecture
Jahr    2007
Anmerkung    "Dissemination Level: Confidential"
URL    http://www.hydramiddleware.eu/hydra_documents/D3.4_Initial_Architectural_Design_Specification.pdf
Webcite    http://www.webcitation.org/6SPHDUL2d

Literaturverz.   

nein
Fußnoten    nein
Fragmente    2


Fragmente der Quelle:
[1.] Saa/Fragment 044 08 - Diskussion
Zuletzt bearbeitet: 2014-09-21 21:45:07 Hindemith
Eisenhauer et al 2007, Fragment, Gesichtet, SMWFragment, Saa, Schutzlevel sysop, Verschleierung

Typus
Verschleierung
Bearbeiter
Hindemith
Gesichtet
Yes.png
Untersuchte Arbeit:
Seite: 44, Zeilen: 8-17
Quelle: Eisenhauer et al 2007
Seite(n): 17, Zeilen: 13ff
Application Elements

Application Elements describe components that are usually deployed on hardware which is performance-wise capable of running the application that the solution provider creates. This means these components are meant to be running on powerful machines. They have been put together and configured to work together with other software in order to support a specific application such as building automation by a specific developer, e.g. system integrator.

Device Elements

Device Elements describe components that are usually deployed inside HYDRA-enabled devices, so that they could be deployed in small devices as well which have limited [resources in terms of e.g. processing power or battery life.]

Application elements describe components that are usually deployed on hardware which is performance-wise capable of running the application that the solution-provider creates. This means these components are meant to be run on powerful machines. They have been put together and configured to work together with other software in order to support a specific application such as building automation by a specific developer e.g. system integrator.

Device elements describe components that are usually deployed inside Hydra-enabled devices so we take into account that they could be deployed in small devices which have limited resources in terms of e.g. processing power or battery life.

Anmerkungen

Ein Verweis auf die Quelle fehlt.

Sichter
(Hindemith) Schumann

[2.] Saa/Fragment 045 01 - Diskussion
Zuletzt bearbeitet: 2014-09-21 21:45:11 Hindemith
Eisenhauer et al 2007, Fragment, Gesichtet, SMWFragment, Saa, Schutzlevel sysop, Verschleierung

Typus
Verschleierung
Bearbeiter
Hindemith
Gesichtet
Yes.png
Untersuchte Arbeit:
Seite: 45, Zeilen: 1-17
Quelle: Eisenhauer et al 2007
Seite(n): 17, 18, Zeilen: 17: 20ff; 18: 1ff
These components have a limited set of functionality but could also be deployed on another machine acting as a proxy for e.g. a mote where it would be highly unlikely that those managers would ever be deployed on such a resource-limited device. They have been put on the device by a device manufacturer to provide certain functions irrespective of which application is using the device.

The HYDRA middleware elements are enclosed by the physical and the application layer shown at the bottom and at the top of the diagram respectively. The physical layer realizes several network connections like ZigBee, Bluetooth or WLAN. The application layer contains user applications which could contain modules like workflow management, user interface, custom logic and configuration details. These two layers are not part of the HYDRA middleware. The middleware itself consists of three layers - the network, service and semantic layer, where each layer holds elements according to their functionality and purpose. It is to be noted that some device elements have similar and thus likewise named, counterparts among the application elements. Both, device and application elements, have a Security Manager, which is an orthogonal service and depicted as vertical to cover all three middleware layers.

Those components have a limited set of functionality but could also be deployed on another machine acting as a proxy for e.g. a mote where it would be highly unlikely that those managers would ever be deployed on such a resource-limited device. They have been put on the device by a device manufacturer to provide certain functions irrespective of which application is using the device.

[Seite 18]

The Hydra middleware elements are enclosed by the physical, operating system and the application layer shown at the bottom and at the top of the diagram respectively. The physical layer realizes several network connections like ZigBee, Bluetooth or WLAN. The operating system layer provides functionality to access the physical layer and manages many other hardware and software resources and provides methods to access these resources. The application layer contains user applications which could contain modules like workflow management, user interface, custom logic and configuration details. These two layers are not part of the Hydra middleware. The middleware itself consists of three layers - the network, service and semantic layer. Each layer holds elements according to their functionality and purpose. Note, that some device elements have similar and thus similar named, counterparts among the application elements. Both, device and application elements, have a Security Manager. To express, that this manager is an orthogonal service, it is depicted vertical and covers all three middleware layers.

Anmerkungen

Ein Verweis auf die Quelle fehlt.

Sichter
(Hindemith) Schumann

Auch bei Fandom

Zufälliges Wiki