I see the risk to end up with something too big and complex for been easily maintained We need, anyway, separate and detailed diagrams per WP task to include into the DevComE tech. desc. (like the one you produced) the general architecture (Matteo) will be a higher level diagram to give the overall idea Davide On 02/02/2012 15:01, Jonischkat, Tim wrote: > > Hey Davide, > > how about the following solution: > > You take the updated diagram attached and merge it with the > architectural components from T9.1 and T9.2. Then we have that > integrated diagram Matteo spoke of. One for the whole chapter. > > What do you think? > > Tim > > *Von:*Davide Dalle Carbonare [mailto:davide.dallecarbonare at eng.it] > *Gesendet:* Donnerstag, 2. Februar 2012 14:54 > *An:* Jonischkat, Tim > *Cc:* fiware-tools at lists.fi-ware.eu > *Betreff:* Re: [Fiware-tools] T9.3 Architecture (updated) > > Tim, > the architecture is fine. > Maybe I would rename the "FI-WARE Instance" in "FI-WARE Testbed". > Once it's ready you can upload it into the SVN repository, I'm storing > all the diagrams into > trunk/design/diagrams > > I'm going to produce the general diagram and the one for T9.1 > > @EAB > please provide the T9.2 (Catalogue) update architecture diagram by > February 6th > you can easily find the FMC notation on the already created diagrams > into the SVN ... > they are in grapgml, I'm using yEd > http://www.yworks.com/en/products_yed_about.html > > Me and Matteo are inserting the tickets and the tasks into the forge > but there are still some > platform problems ... we close this activity as soon as possible. > > ciao > Davide > > > On 02/02/2012 11:59, Matteo Melideo wrote: > > Thanks Tim. > The idea is to provide a general architecture embracing the all > DevCommE then we can enter into the details of each specific part > where and if necessary. > > Concerning the second question, I will leave Davide to provide you and > answer. > > Best, > > M. > > > Il 01/02/2012 18:04, Jonischkat, Tim ha scritto: > > Dear partners, > > please review the attached architecture draft for T9.3 -- > > Please let me know -- especially for the deployment tool -- if there > is any misconception. > > @Matteo/Davide: would you propose to make one diagram for all tasks? > And: could you please check if that format is editable for you? > > Cheers > > Tim > > --- > > Tim Jonischkat > > paluno - The Ruhr Institute for Software Technology > > University of Duisburg-Essen > > Gerlingstraße 16 > > 45127 Essen, Germany > > T: +49 201 183 4659 > > F: +49 201 183 4699 > > E: tim.jonischkat at paluno.uni-due.de > <mailto:tim.jonischkat at paluno.uni-due.de> > > http://www.paluno.uni-due.de <http://www.paluno.uni-due.de/> / > > http://www.sse.uni-due.de <http://www.sse.uni-due.de/> > > VAT ID: DE811272995 > > > > > _______________________________________________ > Fiware-tools mailing list > Fiware-tools at lists.fi-ware.eu <mailto:Fiware-tools at lists.fi-ware.eu> > http://lists.fi-ware.eu/listinfo/fiware-tools > > > > > _______________________________________________ > Fiware-tools mailing list > Fiware-tools at lists.fi-ware.eu <mailto:Fiware-tools at lists.fi-ware.eu> > http://lists.fi-ware.eu/listinfo/fiware-tools -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.fiware.org/private/old-fiware-tools/attachments/20120202/cd91f39b/attachment.html>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy