13.07.2015 Views

System Architecture Design

System Architecture Design

System Architecture Design

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

pSHIELD<strong>System</strong> <strong>Architecture</strong> <strong>Design</strong>PU7 ConclusionD2.3 represents consortium’s effort to conclude on a preliminary, as complete as possible though, systemarchitecture. Special care was given, to include all system design relating factors impact, as explained inthe Executive Summary of this document. A formalization methodology was followed, to derive thearchitecture, from a cooperation of known pre-defined components and functions (that we call legacy) withmodules that possess features and capabilities representative of pSHIELD project application domain. Inthis hierarchy of adding functionalities and value, three main subsystems were introduced: the LegacyEmbedded <strong>System</strong> Device (L-ESD), the pSHIELD Embedded <strong>System</strong> Device (pS-ESD) and the pSHIELDSPD Embedded <strong>System</strong> Device (pS-SPD-ESD). The pSHIELD <strong>System</strong> <strong>Architecture</strong>, from the view ofEmbedded <strong>System</strong> Device (ESD) types, is practically consisted from the possible networking versions ofthe aforementioned subsystems. pSHIELD team has been working towards refining the architectureproposal and present an optimized system solution with the deliverance of D2.3.2.PUD2.3.2Issue 5 Page 120 of 122

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!