General Comments 1. Requirement template - need some way of creating links\dependencies between requirements. EPICs belong to some Theme and User Story belong to some EPIC - there might be also some dependencies such as must start after etc. 2. Some have specified User stories - but when reading - they sound much more like EPIC and that in order to implement these requirements there would be much more detailed requirements to be listed - i.e. User Stories My way of looking at it - the criteria for User Story is if now a developer in your organization is able to take the requirement and know what exactly needs to be done without breaking it into more specific requirements and delegating to someone else who has responsibilities of other parts of the system\code. BigData 1. EPIC.FIWARE.Data.BigData.Streaming - not clear to me - is the requirement talking about stateful streaming - meaning that when turning back on a stream or another stream - previous calculations \ state can be accessed and adjusted? If this is so then goal and rational need to be better stated. If not - then what does this requirement mean? I think the name of this req is to general 2. EPIC.FIWARE.Data.BigData.MapReduceExtensions - is the extension on for JOIN? If so then maybe give this that name if not then perhaps generalize the goal\rational and not talk only on JOIN 3. EPIC.FIWARE.Data.BigData.Redundancy - usually such systems require fail over as well - since you cant tolerate any loss of processing streaming data 4. EPIC.FIWARE.Data.BigData.API - does the API only cover writing the own library? What about creating the orchestration\flow between nodes? Anything else? Localization 1. A general Data\Context comment - The event management - seems like another source of events - this strengthen the case that there may need to be inter-GE communication. Wouldnt want such an event to be published and then gathered to reach say CEP GE - there should be a method to capture and disseminate events within the GEs of this chapter. MMAnalysis 1. In general - the user storied description sound more like EPICs and there should be much more detailed requirements to each of these - i.e User story. 2. FI-WARE.Story.Data.MultimediaAnalysis.RegisterObserver\ReleaseObserver - isnt this what the Pub\Sub GE is to enable - the MM GE just needs to have a single observer to the Pub\Sub - the rest is handled there. 3. FI-WARE.Story.Data.MultimediaAnalysis.EventDetectionNotification - similar to above - the Pub\Sub can handle the event notification. What does it mean that the "actors can handle this event"? Does this GE specify actors and their logic? Or is this out side of the scope? Semantic Annotation Here too there are User stories requirements that seem like require to be more detailed through multiple requirements to be able to implement - therefore they seem to be more EPIC like requirements Semantic App Again - some Stories there that seem to be EPIC requirements Pub\Sub Again Stories sound more like EPIC here 1. STORY.FIWARE.Data.PublishSubscribe.LanguageOptimisationForMobile - this sounds to be something that needs to go all the way to GEs that support the device communication such as IoT or the App\Eco - is Data\Context Management 'aware' of the consumers\subscribers of the data? What I mean is that this requirement can not stop here it needs to penetrate other chapters 2. STORY.FIWARE.Data.PublishSubscribe.Subsciprion&Notification - is their stateful subscription - i.e. Some subscribes now can get stuff that has been published before? 3. STORY.FIWARE.Data.PublishSubscribe.QueryLanguageEngine and MatchingRulesDefinition - is this query language and engine mechanism associated with a subscription - e,g filtering the published events? Or has this something to do with the Query GE in the chapter? Because if this is the second I am not sure why there should be such a connection between these GEs - also - some of this processing may be done by the Processing GEs so the published information has already been defined such that it meets the criteria of subscription especially when there is statefullness in these matching rules. Thats it for now. Regards, Guy Sharon Manager Event-based Middleware & Solutions Group Event-based Middleware & Solutions phone : +972 4 8296587 mobile : +972 54 6976417 address : IBM R&D Labs in Israel, Haifa University Campus, Mount Carmel, Haifa, 31905, Israel email : guysh at il.ibm.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/old-fiware-data/attachments/20110904/8452aea3/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 2558 bytes Desc: not available URL: <https://lists.fiware.org/private/old-fiware-data/attachments/20110904/8452aea3/attachment.gif>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy