[Fiware-finodex-coaching] Fiware-finodex-coaching Digest, Vol 2, Issue 8

[Pasquale Vitale]

Hi Miika,
in the 3.1 Architecture section you have to describe the general 
architecture of project. You can use modules/blocks to describe your 
functionalities in the project.
In the 3.4 Architecture Diagram you have to describe all functionalities 
of components (GEs or other software components that you'll use), their 
interactions;
here you have to use the graphic description to explain in detail the 
interactions.

For example in 3.1 you can use an "Authentication" module to provide the 
autehtication in your system,
and in the 3.4 you can explain it with some GEs (IdM KeyRock and PEP 
Proxy) and interaction between GEs-GEs and GEs-your other component system.

I hope now it is clear.
Pasquale

Il 14/04/2015 16:54, Miika Hakala ha scritto:
> Hi Pasquale,
>
> Viewing your discussion with Tania, I wondered what is the distinction 
> is between section "3.1 Architecture" and "3.4 Architecture Diagram"?
> Care to elaborate on what is expected in each section? It just seems 
> like two sections about the same thing. Where you are either repeating 
> our self or you are splitting the overall description into two 
> separate sections.
>
> Thank you for your help.
>
> Best regards,
> Miika Hakala
>
> On 14.4.2015 17:27, fiware-finodex-coaching-request at lists.fi-ware.org 
> wrote:
>> the architecture diagram section, you also have to describe (in
>> detail) the diagram, the interactions between components (GEs and/or
>> software system), the usage of GEs (why, how) and other component.
>
> _______________________________________________
> Fiware-finodex-coaching mailing list
> Fiware-finodex-coaching at lists.fi-ware.org
> https://lists.fi-ware.org/listinfo/fiware-finodex-coaching
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-finodex-coaching/attachments/20150414/d081c3cf/attachment.html>