[Fiware-iot] [GE splitting]

[thierry.nagellen at orange.com]

I think the best place is the Architecture description but I will discuss the point with Juanjo to be sure of the approach.

BR
Thierry

De : Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu]
Envoyé : lundi 26 novembre 2012 16:43
À : NAGELLEN Thierry OLNC/OLPS; fiware-iot at lists.fi-ware.eu; Juanjo Hierro
Objet : RE: [GE splitting]

Dear Thierry,

Thank you for the prompt reply.
Having a short introduction like you described is fine for me. Do you think this should go into the backlog, or rather into the architecture description? Maybe we put in on a dedicated page, and on each other page (backlog, architecture, technical roadmap) we put a pointer to that dedicated page?

Best
Tobias

From: thierry.nagellen at orange.com<mailto:thierry.nagellen at orange.com> [mailto:thierry.nagellen at orange.com]
Sent: Montag, 26. November 2012 16:39
To: Tobias Jacobs; fiware-iot at lists.fi-ware.eu<mailto:fiware-iot at lists.fi-ware.eu>; Juanjo Hierro
Subject: RE: [GE splitting]

Hi Tobias,

Thanks for this first todo list and references. How people are aware of Backend Things Management GE? First of all we have PO and reviewers and for them it is easy to explain that we split the GE in two new GEs.

But for UC projects which are trying to analyse and maybe use the TM GE, it is difficult to delete everything as if TM GE did never exist. I think we have to provide a short introduction to explain that because of NGSI interface and to enhance modularity, the architecture evolves to a new one where components from TM GE are becoming GEs. Providing a short but consistent description of their role in the architecture should allow readers to understand the process; Then a list of dedicated features per GE will completely support this approach and re-design the new GEs.

In that way we would be able to keep the Technical Roadmap for the first release and maintain consistency, at least till the end of Phase 1 and projects in phase 2 will be aware only of the new GEs.

BR
Thierry

De : Tobias Jacobs [mailto:Tobias.Jacobs at neclab.eu]
Envoyé : lundi 26 novembre 2012 16:28
À : fiware-iot at lists.fi-ware.eu<mailto:fiware-iot at lists.fi-ware.eu>; Juanjo Hierro; NAGELLEN Thierry OLNC/OLPS
Objet : [GE splitting]

Dear all,

We are about to start implementing the split between the Things Management GE and the Configuration Management GE. What we have done up to now is to create an overview of the places where there are changes that need to be done:
https://forge.fi-ware.eu/plugins/mediawiki/wiki/fi-ware-private/index.php/Things_Management_GE_splitting_page

The page also contains placeholders for the modified pages.

The question now is how much of the old Things Management GE to leave in these pages.
What we would propose is to bring everything into a status which simulates that the TM GE has never existed, and only mention at certain places that the TM GE now is actually two GEs. Although this might create some confusion, the alternative would be to have some things described in terms of the old GE and other things described in terms of the new GE - where the confusion would be considerably greater, I think.

In particular.

-          All tracker items become associated to one of the new GEs, or both

-          All Things Management GE features/epics/... become features of one of the new GEs, or of both

-          In the technical roadmap the release 1 could stay like it is, but the linked features are changed to the new features.

-          In the catalogue the old TM GE will stay at least until the 2nd release, but the documentation links need to be updated.

Please let me know your opinion.

Best regards
Tobias

_________________________________________________________________________________________________________________________



Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.



This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified.

Thank you.

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
France Telecom - Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, France Telecom - Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-iot/attachments/20121126/9bc5c206/attachment.html>