UniversAAL - Part I - Task 2.1 report (Rapporti progetti di ricerca)

  • UniversAAL - Part I - Task 2.1 report (Rapporti progetti di ricerca) (literal)
  • 2011-01-01T00:00:00+01:00 (literal)
Alternative label
  • Furfari F., Lenzi S., Oligeri G. (2011)
    UniversAAL - Part I - Task 2.1 report
  • Furfari F., Lenzi S., Oligeri G. (literal)
  • DISCIPLINA DI RIFERIMENTO: Information Technology & Communications Systems; AREA DI VALUTAZIONE: 15a - Scienze e tecnologie per una società dell'informazione e della comunicazione (literal)
  • PuMa (literal)
  • Altro (literal)
  • CNR-ISTI, Pisa, Italy; CNR-ISTI, Pisa, Italy; CNR-ISTI, Pisa, Italy (literal)
  • UniversAAL - Part I - Task 2.1 report (literal)
  • This is a subpart of the deliverable D2.1-A that reports about the work done to deliver the actual prototype. Hence, it provides information that should help to justify the effort reported in the context of Task 2.1. Apart from the standard Section 1, which defines the scope and the role of this part in the context of the whole D2.1, this report consists of the following important information: . Since the whole development work in WP2 is divided among seven expert groups, the scope of D2.1 is defined to be equivalent to the scope of the following expert groups: Middleware, Local Device Discovery and Integration (LDDI), and Security. Therefore, the requirements to be covered by D2.1 are equivalent to the requirements covered by those expert groups. . The consolidation method used for the reuse of software inherited from the input projects towards the alpha releases of the first set of software artefacts in D2.1 has been based on the general consolidation method described in Part I of D1.3: gathering info (here, about reusable software modules) in a harmonized way (here, in a certain table with predefined columns), while categorizing them (here, assigning modules to one of the seven expert groups); each expert group could then extract the related design decisions of each of the input projects based on the related bunch of software modules and compare them with its own design decisions so that, at the end, the software modules of the one input project with the nearest design decisions could be selected as the initial software to be further developed based on the group's own design decisions and the experience from all of the input projects. . The last section summarizes the result of the above consolidation process for the three expert groups in the scope of D2.1 by providing info about the imported software artefacts, the first development tasks done during this importing phase, the corresponding development agenda in universAAL, and the time and resource planning for the implementation of the agenda. Important Note: In this document, there are many references to stuff accessible under the URL http://depot.universaal.org/. In order to access them, you might need to create an own account by clicking a provided link and filling in the form that will open. The rules are: to access compiled code in the maven repository (mostly JARs), there is no need to have any account; for accessing the wiki pages of the expert groups, you only need to have an account and read access will be granted to you automatically; to access the SVN repository of an expert group and its associated issue tracking, you must request to be added as a guest using a provided link. (literal)
Prodotto di
Autore CNR
Insieme di parole chiave

Incoming links:

Autore CNR di
Insieme di parole chiave di