[Fiware-data] FMC modeling software [Was:Fwd: RV: [tid-fiware] Fwd: GUIDELINE: FI-WARE Architecture Specifications: proposed solution for some of the pending questions]

[Grant Croker]

As discussed in the Arch meeting in Madrid on 25/1

-------- Mensaje original --------
Asunto:         RV: [tid-fiware] Fwd: GUIDELINE: FI-WARE Architecture
Specifications: proposed solution for some of the pending questions
Fecha:  Thu, 26 Jan 2012 16:06:27 +0100
De:     Croker, Grant <grant.croker at tecsidel.es>
Para:   e.fiware1 <e.fiware1 at tid.es>



*De:*fiware-bounces at tid.es [mailto:fiware-bounces at tid.es] *En nombre de
*Juanjo Hierro
*Enviado el:* miércoles, 07 de diciembre de 2011 10:39
*Para:* fiware at tid.es
*Asunto:* [tid-fiware] Fwd: GUIDELINE: FI-WARE Architecture
Specifications: proposed solution for some of the pending questions


FYI

-------- Original Message --------

*Subject: *



GUIDELINE: FI-WARE Architecture Specifications: proposed solution for
some of the pending questions

*Date: *



Wed, 07 Dec 2011 08:55:25 +0100

*From: *



Juanjo Hierro <jhierro at tid.es> <mailto:jhierro at tid.es>

*To: *



fiware-wpl at lists.fi-ware.eu <mailto:fiware-wpl at lists.fi-ware.eu>
<fiware-wpl at lists.fi-ware.eu> <mailto:fiware-wpl at lists.fi-ware.eu>,
fiware-wpa at lists.fi-ware.eu <mailto:fiware-wpa at lists.fi-ware.eu>
<fiware-wpa at lists.fi-ware.eu> <mailto:fiware-wpa at lists.fi-ware.eu>



Hi all,

On Nov 30th, I sent a detailed email describing how I think we should
approach development of the next major deliverable, i.e., the
deliverable on FI-WARE Architecture Specifications. I hope that all of
you had already read carefully its contents so that we all are on the
same page.

There were two questions that were pending to solve before starting the
actual writing of the deliverable on the Wiki. I elaborate on the
proposed approach for both of them here.

1. Conventions for figures to include in Architecture Specifications

In order to get an harmonized set of specifications a convention for
figures describing aspects of the Functional Architecture linked to a GE
has to be adopted.

After some analysis, Thomas and me have decided to propose following FMC
conventions for "Block Diagrams - Compositional Structures" defined in
[1]. Note that the adoption of FMC conventions is limited to these Block
Diagrams. Rest is not mandatory at all (nor indeed needed for this
deliverable).

Unless we hear about any objection, this will be the adopted
recommendation you should forward to your teams.

The gallery of basic elements used in FMC Block Diagrams is pretty
simple, so I'm sure you could use any of your favorite editing tools for
creating Architecture Description Diagrams, even powerpoint. For those
who may not want to use powerpoint but a drawing tool that is better
tailored to draw Diagrams, we may recommend yED (see [2])


2. Uploading contents on the Wiki

As already explained in one of my previous mails in response to a
question made by Torsten, we will definitively go for developing
contents of this deliverable on the Wiki. Therefore, one of the
questions we should answer first is where on the Wiki.

Here you are a list of points that describe the approach I suggest we
should follow:

   * A new entry on the main home page of the FI-WARE Wiki will be
     created titled "FI-WARE Architecture". This will lead to a Wiki page
     were we will provide:
       o a short introduction of the goal of the Architecture Specifications
       o links to specific Wiki pages, one per chapter of FI-WARE. Each
         of these Wiki pages will be structured so that it includes an
         Introduction section (we will decide what comes here later) and
         a section per GE who should follow the structure we described in
         the email I sent on Nov 30 (note that the CORBA Event Service
         example I provided would map to the concept of a single GE in
         FI-WARE like the Pub/Sub Broker GE)
       o a link to a Wiki page to be titled "Bringing all pieces
         together", were we will elaborate on the description of how the
         different chapters will connect together from an architectural
         point of view, serving example (but generic) use case scenarios.
   * We should include a section titled "Open Specifications" at each of
     the GE sections we have under the "Materializing the FI-WARE Vision"
     part of the Wiki. This section will contain a bullet list of two
     items, each one linking to a Wiki page. The first one will be titled
     "Architecture Specification" and the second one will be titled
     "Detailed Interface Specifications". The first one will be a direct
     link to the section dedicated to the GE under the "FI-WARE
     Architecture" part of the Wiki described in the point above (note
     this will allow to navigate to concrete GE Architecture
     Specifications from the "Materializing the FI-WARE Vision" part of
     the Wiki, but that is precisely something we want to achieve). The
     second one will be where the detailed description of what remains
     regarding the complete set of Open Specifications linked to a GE,
     that is, the detailed description (signature and behaviour
     description of provided APIs, definition of protocols,
     non-functional mandatory features, etc) of interfaces introduced in
     the Architecture Specification.

A draft of the guidelines, based on the above descriptive text, will be
made soon available on the FI-WARE Project Handbook available on the
Wiki. Please don't hesitate to make any question or formulate any doubt
so that answers can help to enrich the guidelines.

Please share this email with members of your team.

Cheers,

-- Juanjo

References:

[1] - http://www.fmc-modeling.org/notation_reference
[2] - http://www.yworks.com/en/products_yed_about.html


Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ATT00001.txt
URL: <https://lists.fiware.org/private/old-fiware-data/attachments/20120126/609ee682/attachment.txt>