[Fiware-security] FI-WARE - WP8 -

[BISSON Pascal]

Dear All,

You will find hereafter some important messages received from Juanjo (also discussed at the audio conf CA-WPL/WPA I had with him yesterday) and that I wanted to relay you and more specifically to task leaders since important to have in mind in the context of the work undertaken with respect to finalization of their inputs to WP8 input document to D2.1a.



1.       FI-WARE High-level Description document
M2 deliverable (aka FI-WARE High-level Description document) would be a sort of "Product vision" document in line with what the Agile methodology proposes.

 Notice that the true consolidated "Product Vision" document is the one we expect to deliver by end of month 5, i.e., end of September.   Once we get that "Product Vision" ready, we should start materializing our vision in subsequent Sprints (duration of our Sprints should be two months).     By end of month 5 we should also have a first release of our FI-WARE features backlog, made up of the features we have identified ourselves and plan to implement for each and every GE in FI-WARE.   We should be able to develop that backlog independently of the input by UC projects, I mean, we should have a plan/roadmap ready for each and every GE by end of month 5.

What we are going to deliver in month 2 should be considered an early draft of this "Product Vision".   It's something that is helpful for starting the dialogue with the UC projects.  Kind of: "you know, this is an early description of what we are planning to deliver, your feedback is welcome".    But doesn't need to be a) complete, i.e., meaning there might be things we will declare "work under progress and expected to be finished by end of month 5"  nor b) as exhaustive as it will be by end of month 5.   Indeed, I want only to provide the description of GEs we are rather confident about in our release in month 2.   Anything that we don't considered yet closed should go to the "Question Marks" section (which I'm considering to retitle as "Question marks and work still under progress" or simply "Work still under progress").

[This is something I would suggest NSN to consider for what concerns GE on Auditing (this in view of what exists so far and what we discussed during our audio conf on Friday. ]
As for other GE owners/Task leads please check your input accordingly


  From month 2 until month 5, UC projects will be entitled to generate "request for inclusion" of features to our backlog.   We will see how many of these feature request will finally be accepted and how accepted features will be prioritized against the features we have already identified on our own.   Analysis and management of feature requests coming from UC projects is something we will carry out from month 5 to month 7.



Deadline to have input document coming from Technical WP was set mid of June but could be extended (although not yet confirmed - will let you know) so I can only encourage each of the task lead to finalize and send me asap their finalized and polished version of their sections in view of the above.



2.       Workplan updates



Deadline to have input document coming from Technical WP was set mid of June but could be extended (although not yet confirmed - will let you know) so I can only encourage each of the task lead to finalize and send me asap their finalized and polished version of their sections in view of the above.


>From June 22 until June 30 TID will try to make a complete integration of all contributions as to deliver a first consolidated draft of the document.    On June 22 TID will come with a proposal on what precise tasks we will carry out during that period and how we are going to manage things. The following anticipated tasks  will be included in the plan:
*         TID will plan peer reviews of those chapters we may consider closer to a final version.   Concrete partners will be assigned this task.
*         TID will setup a number of task forces, typically one per WP, to analyze security issues with regard to each WP.
This is of concern to us as it means that WP8 will have to participate to these task forces and review each of the input document produced by other WPs (for this we will rely primarily although not uniquely on people appointed by WP8 to monitor  activities of each other Technical WPs - see attached slide). When discussing this topic with TID Juanjo I called to consider first not to start from scratch (make use of initial input produced by each of the WPs) and second to have for these task forces mixed team made of representatives of WP8 and of representatives (having preferably some background on Security) of the WP at hands.
This was agreed by TID since:  The task force corresponding to a given WP would involve people from that WP and people from the Security WP.
                                I can only encourage WP8 partners appointed to monitor activities of each of the other Technical WP (as per slide attached) to be prepared to answer this demand (being said input documents from other WPs are available on the repository - D2.2 contribs folder).

Obviously all these topics and other would be discussed at our next audio conf (17/06/11 - 10am-12am - details will follow)
Best Regards,

Pascal



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/old-fiware-security/attachments/20110614/46048028/attachment.html>