[Fiware-opencall-help] Advanced UI GE Open Call

[Nick Allott]

Final question: can I confirm my understanding for the protocols for
filling in the form



The deliverables table for 1.2b. I assume given only the delivery months
are highlighted yellow and the delivery text is not italicised  - that
deliverable tables remain almost untouched (delivery dates inseted and
PU/PP clarified) Example text as below

The significant work to do is to detail the tasks for each WorkPackage.
Where there is a one to one relationship between task and Epic.



Note also we have identified some potential Tasks that do not map one:one
with an Epic) but are pertinent to many/all. Is it reasonable to add a new
Task for these type of items.



Sorry for the many questions, but I want to ensure I fill in the form
according to expectations



Thanks









Following there is a list of deliverables and delivery dates for this WP.
Deliverables follow numbering D.<i>.<j>.<n> where <i> designates the WP,
<j> designates the deliverable within that WP and <n> identifies the
release of the deliverable. Documents are tagged as (R) while software for
experimentation is tagged as (P). Deliverables will have also internal
delivery dates.



Deliverable Number

Deliverable Title / Description

Nature

Dissem.
Level

Delivery Month

D.3.1.{1,2}

*FI-WARE GE Open Specifications*. (*)

This deliverable describes the open specifications linked to GEs (and their
corresponding components) being developed in this WP.  A draft of this
deliverable will be published three months ahead of the actual delivery of
a complete and integrated FI-WARE SW release so that Use Case projects may
have early access to them for the development of their proof-of-concept
prototypes.

Strong emphasis will be given to the adoption of specifications defined by
standardisation bodies and initiatives, as well as to defining particularly
innovative and relevant specifications that the WP will propose for
adoption by those bodies.

R

PU

4, 12

D.3.2.{1,2}

*SW Release (version of components delivered for integration in testbed)*.

This deliverable is the software implementation of FI-WARE components that
have been developed in each release of FI-WARE. The software linked to a
component will be accompanied with a document (release notes) describing
the features of the corresponding backlog that have been covered in the
release. Components targeted in the first release of FI-WARE will be
initially identified in the first release of the FI-WARE Architecture.  The
FI-WARE Architecture and Roadmap documents will be updated with each
FI-WARE release to keep consistency. The second and third release of
FI-WARE will include the adoptions originated by the feedback by the Usage
Areas, as well as the fixing of bugs emerged through testing of components.

P

PU[1] <#_ftn1>

7, 15

D.3.3.{1,2}

*Installation and Administration Guide*.

This document comes along with the SW implementation of components, each
release of the document referring to the corresponding SW release to
facilitate the users/adopters in the installation (if any) and
administration of components (including configuration, if any).

R

PU[2] <#_ftn2>

7, 15

D.3.4.{1,2}

*User and Programmers Guide*.

This document comes along with the SW implementation of components, each
release of the document being referred to the corresponding SW release, to
document to the users/adopters the features offered by the components and
interfaces and the way they can be exploited in their developments.

R

PU

7, 15

D.3.5.{1,2}

*Unit Testing Plan and Report*.

This deliverable provides the description of the test plans and the report
on the unit test and validation activities performed for the components
defined and implemented in this WP.

R

PP

7, 15





*From:* Nick Allott [mailto:nick at ubiapps.com]
*Sent:* 03 November 2012 15:49
*To:* 'fiware-opencall-help at lists.fi-ware.eu'
*Subject:* RE: Advanced UI GE Open Call



Secondary question: is the template and the evaluation framework set up to
assess the quality/qualifications of the companies and principle
invdividuals behind the project







*From:* Nick Allott [mailto:nick at ubiapps.com <nick at ubiapps.com>]
*Sent:* 02 November 2012 11:30
*To:* 'fiware-opencall-help at lists.fi-ware.eu'
*Subject:* Advanced UI GE Open Call



We are in the final stages of preparing a response to the open call



I have one question regarding 1.2b form



*Each RTD Work Package should address a number of Epics linked to the topic
you target in your submission*





Seems to imply that there will be a number of workpackages. Is the
expectation that we shall cluster related epics so that there may be 4 WP
addressing the full epic list



Second question the example D3.1 : relates to a single WP=3



If more wp are required – do we count then 4,5,6….



Thanks







*[image: cid:image001.jpg at 01CD7408.A5C390B0]*

*Dr. Nick Allott*

*UbiApps*

+44(0)7714145711

nick at ubiapps.com

skype: nallott

www.linkedin.com,/in/nickallott



Southampton Science Park,

2 Venture Road, Chilworth

Southampton

Hampshire

SO16 7NP, United Kingdom

http://www.ubiapps.com





------------------------------

[1] <#_ftnref1> Depending on the business model of the owner of the
software components developed, parts of this deliverable (i.e. software
components) will have dissemination level  'PU' or 'PP'.

[2] <#_ftnref2> Dissemination level of this deliverable follows the chosen
dissemination level of the accompanying software release (i.e. Dx.2)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-opencall-help/attachments/20121105/1fe10c11/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 2637 bytes
Desc: not available
URL: <https://lists.fiware.org/private/fiware-opencall-help/attachments/20121105/1fe10c11/attachment.jpg>