I am worried! Is there a danger that the suggested change in epic naming cascades to all documents, backlog items, materializing items etc. (features, user stories, and work items) due to *inconsistencies that will be subsequently found by "C4 - Valid and Consistent Hierarchy" checks*? What is the estimated amount of work before everything is settled? What risks correcting these 11 identifiers introduces to the real goals of the project? BR Ari On 2014-06-26 12:26, Marti Christof (mach) wrote: > Dear WP13 GEi owners > > The problem with the naming of the epics is, that we need to add an > EpicId. > Schema: FIWARE.Epic.Chapter.Enabler[.EpicId]*.EpicId > > At the moment many WP13-epics are only named after the GE itself. e.g. > - FIWARE.Epic.MiWi.2D-UI > So we either need to add a generic EpicId (see below) or split up the > Epics in multiple meaningful peaces. > - FIWARE.Epic.MiWi.2D-UI.FunctionalityX > - FIWARE.Epic.MiWi.2D-UI.FunctionalityY > Because some of the Epic Description are also to long (see report "All > issues") and need to be shortened, this might be a good possiblity to > fix these issues too. > > Please let me know ASAP [today before EOB] if and how it would be > possible to split your current GEs Epic. > > Best regards > Christof > > > > Anfang der weitergeleiteten Nachricht: > >> *Von: *"Marti Christof (mach)" <mach at zhaw.ch <mailto:mach at zhaw.ch>> >> *Betreff: * *Aw: [Fiware-ge-owners] Backlog content: updated reviews* >> *Datum: *26. Juni 2014 [26] 11:05:08 MESZ >> *An: *MANUEL ESCRICHE VICENTE <manuel.escrichevicente at telefonica.com >> <mailto:manuel.escrichevicente at telefonica.com>> >> *Kopie: *MIGUEL CARRILLO PACHECO <mcp at tid.es <mailto:mcp at tid.es>> >> >> Hi Manuel >> >> The problem is, that in OpenCall 2 more or less the WebUI GEs have >> been based on the defined Epics. So the epics where available before >> the GEs. >> The problem did not show up before, because they were named >> FIWARE.Epic.MiWi.AdvWebUI.2D-UI, but AdvWebUI is not a GE, so we got >> the error there and had to rename them to the correct GE-names. >> >> I do not care to rename the Epics, but is there a rule or a schema in >> other WPs how to extend the name in such a case? >> - FIWARE.Epic.MiWi.2D-UI.2D-UI (repeating the GE name) >> or >> - FIWARE.Epic.MiWi.2D-UI.Basis (for implementation of the basis) >> or >> - FIWARE.Epic.MiWi.2D-UI.Basic (for basic functionality) >> or >> - FIWARE.Epic.MiWi.2D-UI.BaseFunctionality >> or >> - ... >> >> We can schedule a call to discuss this. I am available from 13:00 to >> 13:45 and then again from 16:00-... >> >> Best regards >> Christof >> >> Am 26.06.2014 um 10:44 schrieb MANUEL ESCRICHE VICENTE >> <manuel.escrichevicente at telefonica.com >> <mailto:manuel.escrichevicente at telefonica.com>>: >> >>> Hi Christof, >>> >>> Rules haven't changed. >>> It doesn't make sense to have an Epic named as the GEI. Epics are >>> organising items, it should add some organising value to the items >>> added below. >>> If you wish, we can do some research to the past to check how it was >>> at some definite time. >>> Let me know and we schedule a meeting. >>> >>> Kind regards, >>> Manuel >>> >>> *From:*Marti Christof (mach) [mailto:mach at zhaw.ch] >>> *Sent:*jueves, 26 de junio de 2014 10:24 >>> *To:*MANUEL ESCRICHE VICENTE >>> *Cc:*MIGUEL CARRILLO PACHECO >>> *Subject:*Re: [Fiware-ge-owners] Backlog content: updated reviews >>> >>> Hi Manuel >>> >>> I am working on fixing the problems with the backlog. >>> One point I have problems to fix is the Epic naming error, because >>> you expect an EpicId at the end, but most of our Epics are similar >>> to the GEs itself. So for the following GEs the Epics and the GE are >>> identical: >>> - FIWARE.Epic.MiWi.2D-UI >>> - FIWARE.Epic.MiWi.3D-UI >>> - FIWARE.Epic.MiWi.AugmentedReality >>> - FIWARE.Epic.MiWi.CloudRendering >>> - FIWARE.Epic.MiWi.DisplayAsAService >>> - FIWARE.Epic.MiWi.GISDataProvider >>> - FIWARE.Epic.MiWi.POIDataProvider >>> - FIWARE.Epic.MiWi.InterfaceDesigner >>> - FIWARE.Epic.MiWi.RealVirtualInteraction >>> - FIWARE.Epic.MiWi.Synchronization >>> - FIWARE.Epic.MiWi.VirtualCharacters >>> >>> To accomplish the rules we would have to add some artificial EpicId >>> like .Basic oder .BaseFunctionality >>> Is this really intended? >>> >>> I also wonder, why this errors did not show up earlier, when we >>> fixed the last round of bugs. >>> >>> Best regards >>> Christof >>> >>> Am 26.06.2014 um 10:02 schrieb MANUEL ESCRICHE VICENTE >>> <manuel.escrichevicente at telefonica.com >>> <mailto:manuel.escrichevicente at telefonica.com>>: >>> >>> >>> Dear Partners, >>> >>> Please, find below updated reports. >>> >>> REVIEWS: >>> https://forge.fi-ware.org/docman/view.php/27/4224/FIWARE.backlog.apps.review.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4225/FIWARE.backlog.cloud.review.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4226/FIWARE.backlog.iot.review.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4227/FIWARE.backlog.data.review.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4228/FIWARE.backlog.i2nd.review.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4229/FIWARE.backlog.security.review.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4230/FIWARE.backlog.miwi.review.20140626.xlsx >>> >>> DASHBOARDS: >>> https://forge.fi-ware.org/docman/view.php/27/4231/FIWARE.backlog.apps.dashboard.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4232/FIWARE.backlog.cloud.dashboard.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4233/FIWARE.backlog.iot.dashboard.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4234/FIWARE.backlog.data.dashboard.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4235/FIWARE.backlog.i2nd.dashboard.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4236/FIWARE.backlog.security.dashboard.20140626.xlsx >>> https://forge.fi-ware.org/docman/view.php/27/4237/FIWARE.backlog.miwi.dashboard.20140626.xlsx >>> >>> If any support were required, please, don't hesitate to let me know. >>> >>> Kind regards, >>> Manuel >>> >>> ---------------------------- >>> Manuel Escriche Vicente >>> Agile Project Manager/Leader >>> FI-WAREInitiative >>> Telefónica Digital >>> Parque Tecnológico >>> C/ Abraham Zacuto, 10 >>> 47151 - Boecillo >>> Valladolid - Spain >>> Tfno: +34.91.312.99.72 >>> Fax: +34.983.36.75.64 >>> http://www.tid.es <http://www.tid.es/> >>> >>> ------------------------------------------------------------------------ >>> >>> Este mensaje y sus adjuntos se dirigen exclusivamente a su >>> destinatario, puede contener información privilegiada o >>> confidencial y es para uso exclusivo de la persona o entidad de >>> destino. Si no es usted. el destinatario indicado, queda >>> notificado de que la lectura, utilización, divulgación y/o copia >>> sin autorización puede estar prohibida en virtud de la >>> legislación vigente. Si ha recibido este mensaje por error, le >>> rogamos que nos lo comunique inmediatamente por esta misma vía y >>> proceda a su destrucción. >>> >>> The information contained in this transmission is privileged and >>> confidential information intended only for the use of the >>> individual or entity named above. If the reader of this message >>> is not the intended recipient, you are hereby notified that any >>> dissemination, distribution or copying of this communication is >>> strictly prohibited. If you have received this transmission in >>> error, do not read it. Please immediately reply to the sender >>> that you have received this communication in error and then >>> delete it. >>> >>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu >>> destinatário, pode conter informação privilegiada ou >>> confidencial e é para uso exclusivo da pessoa ou entidade de >>> destino. Se não é vossa senhoria o destinatário indicado, fica >>> notificado de que a leitura, utilização, divulgação e/ou cópia >>> sem autorização pode estar proibida em virtude da legislação >>> vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos >>> o comunique imediatamente por esta mesma via e proceda a sua >>> destruição >>> _______________________________________________ >>> Fiware-ge-owners mailing list >>> Fiware-ge-owners at lists.fi-ware.org >>> <mailto:Fiware-ge-owners at lists.fi-ware.org> >>> https://lists.fi-ware.org/listinfo/fiware-ge-owners >>> >>> >>> ------------------------------------------------------------------------ >>> >>> Este mensaje y sus adjuntos se dirigen exclusivamente a su >>> destinatario, puede contener información privilegiada o confidencial >>> y es para uso exclusivo de la persona o entidad de destino. Si no es >>> usted. el destinatario indicado, queda notificado de que la lectura, >>> utilización, divulgación y/o copia sin autorización puede estar >>> prohibida en virtud de la legislación vigente. Si ha recibido este >>> mensaje por error, le rogamos que nos lo comunique inmediatamente >>> por esta misma vía y proceda a su destrucción. >>> >>> The information contained in this transmission is privileged and >>> confidential information intended only for the use of the individual >>> or entity named above. If the reader of this message is not the >>> intended recipient, you are hereby notified that any dissemination, >>> distribution or copying of this communication is strictly >>> prohibited. If you have received this transmission in error, do not >>> read it. Please immediately reply to the sender that you have >>> received this communication in error and then delete it. >>> >>> Esta mensagem e seus anexos se dirigem exclusivamente ao seu >>> destinatário, pode conter informação privilegiada ou confidencial e >>> é para uso exclusivo da pessoa ou entidade de destino. Se não é >>> vossa senhoria o destinatário indicado, fica notificado de que a >>> leitura, utilização, divulgação e/ou cópia sem autorização pode >>> estar proibida em virtude da legislação vigente. Se recebeu esta >>> mensagem por erro, rogamos-lhe que nos o comunique imediatamente por >>> esta mesma via e proceda a sua destruição >> > > > > _______________________________________________ > Fiware-miwi mailing list > Fiware-miwi at lists.fi-ware.org > https://lists.fi-ware.org/listinfo/fiware-miwi -- Ari Okkonen CIE, University of Oulu -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/fiware-miwi/attachments/20140626/f1fc449f/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy