INFORMATION SOCIETY TECHNOLOGIES _IST_

Document Sample
INFORMATION SOCIETY TECHNOLOGIES _IST_ Powered By Docstoc
					ASK-IT D4.3.1                                      Public                   Contract N. 5112981


          INFORMATION SOCIETY TECHNOLOGIES (IST)
                       PROGRAMME




                                                  511298


                        D4.3.1 Site Status Report
Deliverable No. (use the number indicated         D4.3.1
on technical annex)
SubProject No.             SP4                    SubProject Title   Accessible Europe
Workpackage No.            WP4.3                  Workpackage        Site Installation and Preparation
                                                  Title
Activity No.               A4.3.1, A4.3.2,        Activity Title     Site Infrastructure Development
                           A4.3.3                                    Installation & Integration at Site
                                                                     Functional Testing & Optimisation
Authors (per company, if more than one            Simon Edwards (UNEW), Jurgen Wagner (UNEW),
company provide it together)                      Michal Jeziorowski (COMARCH), Mathias Ringler (NIK),
                                                  Corneliu Milos (ATCRom), Mary Panou, Kostas
                                                  Kalogirou (CERTH/HIT), Daniel de la Hoz (UPM), Valeria
                                                  Schiavone (La Cruna), Toine Molenschot (Den Haag),
                                                  Elina Aittoniemi (VTT), Yannis Orthopoulos (Netsmart),
                                                  Cornelia Hipp (USTUTT)
Status (F: final; D: draft; RD: revised draft):   F
File Name:                                        ASK-IT_D4.3.1_Final.doc
Project start date and duration                   01 October 2004, 48 Months




October 2007                                            i                                UNEW
ASK-IT D4.3.1                             Public                  Contract N. 5112981


Version history table
 Version
           Details
   No.
    1      August 2007
           First version ready with information from ID4.3.1 inserted along with
           additional chapters on server, device and module integration, and
           testing/optimisation. Circulation to all SP4 partners.

    2      26th October 2007
           Penultimate draft updated following actions arising from plenary meeting
           in Crete (Sept. ‘07) and circulated to SP2/SP3 partners for input.

    3      2nd November 2007
           Final draft for peer review.

    4      23rd November 2007
           Final version after peer review.




October 2007                                  ii                                   UNEW
ASK-IT D4.3.1                                                   Public                               Contract N. 5112981




TABLE OF CONTENTS
List of Figures ............................................................................................................................ iv
List of Tables ............................................................................................................................. iv
Abbreviations.............................................................................................................................. v
Executive Summary .................................................................................................................... 6
1 Infrastructure & Equipment at Pilot Sites................................................................................ 7
   1.1 Objectives and Methodology ............................................................................................ 7
      1.1.1 Workplan.................................................................................................................... 7
      1.1.2 Template of Existing and Required Infrastructure and Equipment at Pilot Sites ...... 8
   1.2 Infrastructure and Equipment at Pilot Sites ...................................................................... 8
      1.2.1 Infrastructure Existing at Sites................................................................................... 8
      1.2.2 Specialist Infrastructure Existing at Sites ................................................................ 10
      1.2.3 Infrastructure Required at Sites ............................................................................... 11
      1.2.4 Equipment Existing at Sites ..................................................................................... 12
      1.2.5 Equipment Required at Sites.................................................................................... 14
   1.3 Assessment of Infrastructure and Equipment at Pilot Sites ............................................ 15
   1.4 Infrastructure and Equipment at Pilot Sites (September 2007) ...................................... 16
      1.4.1 Wireless Interoperability.......................................................................................... 16
      1.4.2 Equipment at Sites ................................................................................................... 16
2 Installation & Integration at Sites .......................................................................................... 22
   2.1 Server (ASK-IT and Local) - Approach & Status .......................................................... 22
   2.2 Integration of Mobile Devices - Approach & Status ...................................................... 25
      2.2.1 Mobile devices ......................................................................................................... 25
      2.2.2 PDA and PC integration........................................................................................... 25
   2.3 Integration of ASK-IT Modules – Approach & Status................................................... 26
      2.3.1 Localisation.............................................................................................................. 26
      2.3.2 Navigation................................................................................................................ 26
      2.3.3 e- Commerce............................................................................................................ 27
      2.3.4 Domotics .................................................................................................................. 27
      2.3.5 In-Car ....................................................................................................................... 27
      2.3.6 e-Health.................................................................................................................... 28
      2.3.7 Word Prediction ....................................................................................................... 28
      2.3.8 Kiosk Interface......................................................................................................... 28
      2.3.9 e-Learning & e-Working.......................................................................................... 28
      2.3.10 User Interfaces ....................................................................................................... 28
3 Plans for Functional Testing & Optimisation ........................................................................ 32
   3.1 The Testing Process ........................................................................................................ 32
      3.1.1 Unit and Component Testing ................................................................................... 33
      3.1.2 Integration Testing ................................................................................................... 34
      3.1.3 Regression Testing and Optimization...................................................................... 35
   3.2 Bugzilla – Bug-Tracking System.................................................................................... 36
      3.2.1 Anatomy of a Bug.................................................................................................... 37
      3.2.2 Life Cycle of a Bug.................................................................................................. 40
      3.2.3 Plans for Bugzilla in ASK-IT .................................................................................. 40
4 Integration Plan...................................................................................................................... 42
5 Summary ................................................................................................................................ 44
6 Annex 1: Templates of existing and required infrastructure and equipment......................... 45


October 2007                                                          iii                                                UNEW
ASK-IT D4.3.1                                                  Public                              Contract N. 5112981


6 Annex: Helpdesk Contacts..................................................................................................... 47
7 References.............................................................................................................................. 49



List of Figures
Figure 1.1 CERTH/HIT Lancia Thesis                                                                                                   10
Figure 1.2 Immersive Video at Newcastle-Gateshead                                                                                    11
Figure 3.1 The Testing Process                                                                                                       33
Figure 3.2 Top-Down Testing                                                                                                          34
Figure 3.3 Bottom-Up Testing                                                                                                         35
Figure 3.4 Optimisation Testing: the Four-Phase Cycle                                                                                36
Figure 3.5 Bugzilla Screen                                                                                                           37
Figure 3.6 Products and Components                                                                                                   38
Figure 3.7 Life Cycle of a Bug                                                                                                       40



List of Tables
Table 1.1 Gaps in Infrastructure and Equipment at Sites (October 2007)                                                               6
Table 1.2 Infrastructure existing at sites (February 2007)                                                                           9
Table 1.3 Infrastructure required at sites (based on site feedback)                                                                  12
Table 1.4 Equipment existing at sites (February 2007)                                                                                13
Table 1.5 Equipment required at sites (based on site feedback)                                                                       14
Table 1.6 Assessment of infrastructure and equipment at sites                                                                        15
Table 1.7 Equipment in Athens-Thessaloniki                                                                                           18
Table 1.8 Equipment in Bucharest                                                                                                     18
Table 1.9 Equipment in Genoa                                                                                                         18
Table 1.10 Equipment in Helsinki                                                                                                     19
Table 1.11 Equipment in Madrid                                                                                                       19
Table 1.12 Equipment in Newcastle-Gateshead                                                                                          20
Table 1.13 Equipment in Nuremberg                                                                                                    21
Table 1.14 Equipment in The Hague                                                                                                    21
Table 2.1 Users’ Database Schema                                                                                                     23
Table 2.2 Server Hardware and Software Requirements                                                                                  23
Table 2.3 Server Ports                                                                                                               24
Table 2.4 Site Server Status Report (October 2007)                                                                                   24
Table 2.5 Server Integration: Responsibilities                                                                                       24
Table 3.1 Ranking of Severity                                                                                                        39
Table 4.1 Gantt chart showing expected phased integration process                                                                    43




October 2007                                                         iv                                                UNEW
ASK-IT D4.3.1                        Public                 Contract N. 5112981




Abbreviations
ADAS/IVICS      Advanced Driver Assistance System / In-Vehicle Information
                Communication System
AIA             Athens International Airport
OS              Operating System
PDA             Personal Digital Assistant
UMTS            Universal Mobile Telecommunications System
WLAN            Wireless Local Area Network
GPS             Global Positioning System
GSM             Global System for Mobile Communications
GPRS            General Packet Radio Service
NFC             Near-Field Communication
WiFi            Wireless Fidelity (IEEE 802.11b wireless networking)
MI              Mobility Impaired
POI             Point of Interest
RFID            Radio Frequency Identification
HSDPA           High Speed Downlink Packet Access
LBS             Location-based services
I/O             Input/Output
LCD             Liquid crystal display
GUI             Graphical user interface




October 2007                             v                               UNEW
ASK-IT D4.3.1                               Public                   Contract N. 5112981



   Executive Summary
This deliverable relates to work carried out in the activities of WP4.3 Site Installation
and Preparation: A4.3.1 ‘Site Infrastructure Development’, A4.3.2 ‘Installation and
Integration at Sites’, and A4.3.3 ‘Functional Testing and Optimisation’. It builds on
the Internal Deliverable 4.3.1 ‘Site Infrastructure Development’ (February 2007).

D4.3.1 is aimed at WP4.3 partners, the ASK-IT pilot site managers and technical
integrators. It presents a status report of the ASK-IT pilot sites in October 2007,
immediately prior to commencement of full trial activities.

Chapter 1 recaps the methodology, results and recommendations of the site
installation and preparation work, in terms of infrastructure and equipment at the sites.
This work was carried out in A4.3.1 and reported in an Internal Deliverable ID4.3.1.
Chapter 2 focuses on the installation and integration of ASK-IT modules and client
devices taking place through the work of A4.3.2. An overview is provided of the
installation of servers at pilot sites, selection and installation of modules and the
installation of mobile client devices and other required computer hardware. Chapter 3
reports on the programme of testing and de-bugging, including selection of
appropriate de-bugging software. This relates to the work of A4.3.3. The final chapter
presents a revised integration plan with Gantt chart.

Table 1.1 summarises the gaps in infrastructure and equipment at sites in October
2007. Sites are working towards eliminating gaps and obtaining a minimum number
of client devices. Sites are recommended to supply as many client devices as their
budget will permit.

                   Gaps in Infrastructure and Equipment at Sites
                                    (October 2007)
Infrastructure              No gaps in infrastructure at sites
Equipment (client               Bucharest reports purchase of 3 smart phones and 4
devices)                        PDAs, compared to a required purchase of 10 smart
                                phones and 10 PDAs in February 2007;
                                The situation in Genoa awaits confirmation of
                                collaboration with the MAPPED project, so no up-to-
                                date info is available;
                                Newcastle-Gateshead should purchase at least two
                                extra PDAs;
                                Nuremberg should continue with their stated purchase
                                programme;
                                Elsewhere no gaps are identified and device
                                requirements appear to have been met
        Table 1.1 Gaps in Infrastructure and Equipment at Sites (October 2007)

Further reporting on equipment at pilot sites will be carried out through WP4.6.




October 2007                               6                                       UNEW
ASK-IT D4.3.1                              Public                   Contract N. 5112981




1 Infrastructure & Equipment at Pilot Sites

1.1 Objectives and Methodology

The main objectives of A4.3.1 ‘Site Infrastructure Development’ were:

       To ensure pilot sites have the necessary infrastructure and equipment to
       receive the ASK-IT system and services and to carry out their proposed
       Application Scenarios (see D4.1.1, November 2006);
       To identify any gaps in infrastructure and equipment, or any adaptations
       needed to existing infrastructure and equipment, based on proposed
       Application Scenarios.

The Application Scenarios for each pilot site require an appropriate technical
infrastructure. This includes satellite, mobile and wireless networks, and equipment
such as mobile phones, personal digital assistants (PDAs), and general computing
capability. Where sites are demonstrating domotic or in-vehicle applications, specific
infrastructure must be available.

The pilot sites developed their Application Scenarios with technical constraints in
mind. Even so, several sites have taken the opportunity to add to existing
infrastructure and equipment through selective purchase and installation, in order to
provide more ambitious coverage of ASK-IT technologies and applications.

The A4.3.1 methodology consisted of an activity workplan and a template for the
collection of site-related information. The output was the recommendation of limited
(demo-style) purchase of additional infrastructure and equipment, to be carried out by
the sites themselves. The purchase of additional infrastructure and equipment was a
very carefully considered process as it had to be achieved within the sites’ equipment
budgets and recommendations on specification provided by ASK-IT technical
partners.


1.1.1 Workplan

The A4.3.1 workplan identified the following tasks:

       To catalogue infrastructure and equipment existing at pilot sites;
       To identify infrastructure and equipment required at pilot sites to fulfil A4.1.3
       ‘Application Scenarios’;
       To list missing infrastructure and equipment required to fulfil aims and
       objectives of each pilot site;
       To oversee purchase and/or installation of recommended infrastructure and
       equipment.




October 2007                               7                                      UNEW
ASK-IT D4.3.1                               Public                   Contract N. 5112981


A4.3.1 was a desk-based exercise carried out using a specially designed template (see
section 1.1.2).


1.1.2 Template of Existing and Required Infrastructure and
Equipment at Pilot Sites

Two templates were distributed to the pilot sites in November 2006. Site managers
were encouraged to provide specific numbers of devices existing or required, along
with specifications (e.g. functionality, etc.). They were also asked to provide a
summary of available satellite, mobile telecommunications and wireless
infrastructure. The relevant tables are presented in Annex 1.


1.2 Infrastructure and Equipment at Pilot Sites

This section presents findings from the completed A4.3.1 template shown in section
1.1.2.

Infrastructure can be described as the networks by which communication can take
place. These networks are satellite, mobile, or wireless-based.


1.2.1 Infrastructure Existing at Sites

The following table presents availability of infrastructure at each pilot site in terms of
satellite, mobile and wireless-based technologies, according to feedback from the
sites.




October 2007                                8                                      UNEW
ASK-IT D4.3.1                          Public                  Contract N. 5112981




                Athens-        Bucharest        Genoa      The Hague      Helsinki       Madrid      Newcastle-   Nuremberg
                Thessaloniki                                                                         Gateshead
GPS                  X             X               X            X              X              X           X          X
3G (UMTS)            X             X               X            X              X              X           X          X
GSM                  X                             X            X              X              X           X          X
GPRS                 X                                          X              X              X           X          X
RFID/NFC             X             X                            X
WiFi                 X             X               X                           X               X          X          X
Motes                X                                                                                    X
Bluetooth                                          X                                          X           X          X
Edge                               X                                                                                 X
Tetra                                                                                         X
Smartcard                                                                                     X           X
HSDPA                                             X
                                        Table 1.2 Infrastructure existing at sites (February 2007)




October 2007                                                        9        UNEW
ASK-IT D4.3.1                               Public                   Contract N. 5112981



1.2.2 Specialist Infrastructure Existing at Sites

Several ASK-IT pilot sites have specialist (non-network) infrastructure which they
intend to utilise in their activities. The main specialist infrastructure is houses (plus
appliances) for the domotic use cases, and a vehicle.


1.2.2.1 Smart House
Three sites reported that they would be conducting Application Scenarios involving
smart houses. These are Athens-Thessaloniki, Madrid, and Nuremberg (Volmarstein).

The Athens smart house will include μProcessor units with I/O, Media PC with
Operating System, touch-screen displays, microphones, Network Video Camera, LCD
TV, Oven, Microwave, and various sensors (fire, flood, gas, movement, temperature
and light).

The Madrid house includes lights, home alarm and various sensors, air conditioning,
network video camera using OSGi and Web Services as software architecture, and the
EIB protocol for communication.

The German smart house at Volmarstein includes three different types of
windows/jalousie (a special window covering like a shutter), lights, consumer
electronics (audio/video), and a special bed, and it implements Siemens EIB instabus,
InfraRed, Phone line and Wireless radio technology.


1.2.2.2 Smart Car
Only the Athens-Thessaloniki site is proposing trial activities utilising a research car:
a Lancia Thesis.
                 Lane
             Sensor
                                                                  Eye Sensor


   Distance
   Sensor

                                                                    Blind spot
                                                                      sensor



                                                              Steering-wheel
    Black Box                                                     sensor


                       Figure 1.1: CERTH/HIT Lancia Thesis.




October 2007                               10                                      UNEW
ASK-IT D4.3.1                               Public                   Contract N. 5112981




1.2.2.3 Other Infrastructure
Other specialist infrastructure at the pilot sites include a dedicated UMTS testbed in
Nuremberg, and an immersive video facility in Newcastle-Gateshead which can be
used for requirements capturing, training, and as an additional evaluation tool (see
Figure 1.1).




                Figure 1.2: Immersive Video at Newcastle-Gateshead


1.2.3 Infrastructure Required at Sites

The following table lists further infrastructure identified by each pilot site in February
2007 for purchase and installation, or adaptation.

Athens-            Upgrade of WiFi network to a centralised managed network, with
Thessaloniki       additional access points if required;
                   Indoor LBS module for WiFi network;
                   For the smart house: μProcessor units with I/O, Media PC with
                   Operating System, touch-screen displays, microphones, Network
                   Video Camera, LCD TV, Oven, Microwave, and various sensors
                   (fire, flood, gas, movement, temperature and light)
Bucharest          Upgrade the system software and server used for the ASK-IT
                   services;
                   Adapt M-PROMOTE content delivery module to support
                   entertainment and POI web services
Genoa              Purchase of WI-MAX Technology by Municipality of Genoa
The Hague          The Hague OS will be converted from Windows Mobile to
                   Symbian;
                   20 Bluetooth-enabled speaker/microphone sets;
                   A mobile media platform is being developed for service providers
Helsinki        None


October 2007                               11                                      UNEW
ASK-IT D4.3.1                               Public                   Contract N. 5112981


Madrid           Network 1-3 relevant buildings for indoor localisation and
                 guidance, using motes, WIFI and/or RFID infrastructure (one
                 transportation hub, one cultural centre and one sport facility). The
                 Madrid site would require technical support for this from ASK-IT
                 partners
Newcastle-       Network one local building for indoor localisation and guidance
Gateshead        using motes
Nuremberg        Nuremberg local wireless networks (either provided by
                 stakeholders or an ASK-IT partner);
                 Wireless radio gateway for home and car scenarios provided by a
                 stakeholder;
                 Optional additional localisation components provided by a
                 stakeholder
      Table 1.3 Infrastructure required at sites (based on site feedback)


1.2.4 Equipment Existing at Sites

Equipment may also be referred to as the client devices which the test volunteer will
use to carry out the Application Scenarios. For the purpose of this document, a client
device is a mobile computing device. However, a client device might also be (for
example) a PC Card or WiFi networking card, or a piece of fixed position computing
hardware (e.g. an office PC, or an info-kiosk), or any other accessory that enables a
piece of equipment to communicate with a network.

Each pilot site will need at least one PC as a server. Some sites will be carrying out
trials which will involve info-kiosks. However, the most important devices will be
portable, primarily smart phones or PDAs, and variations on tablet/laptop computers,
including newer technology such as the Ultra Portable PC.

Carrying out an inventory of the number of devices available, and noting their
specification, is an important function of the site status report. In particular the way
each site manages its site activities from day-to-day - i.e. how it allocates its devices
to individual test users - will dictate how many devices are required, whilst the fine
detail of the Application Scenarios will determine the applications required on each
device.

Table 1.4 summarises the client devices to be found at each pilot site in February
2007. Where possible, each site identified an actual number of devices required, and
provided a brief specification (i.e. model, functionality, etc.).




October 2007                               12                                     UNEW
ASK-IT D4.3.1                                                          Public                                                   Contract N. 5112981




             Athens-         Bucharest           Genoa          The Hague        Helsinki         Madrid          Newcastle-      Nuremberg
           Thessaloniki                                                                                           Gateshead
Smart                                               1         HP 67xx /
Phones                                                        Fujitsu Pocket
                                                              Loox T830

                                                              (number not
                                                              yet specified)

PC               1          8 desktop PCs           1                                1
                            (INTEL)
                            3 server PCs
                            (INTEL)
Tablet                      4 lap top PCs           2                                                           1 OQO ‘ultra
PC/                         (Toshiba)                                                                           mobile’ PC
laptop                                                                                                          (XP tablet
                                                                                                                edition)
PDA              2                                  1                                                                  6
Kiosk            4                                  1                                                                  3
Other
                                              Table 1.4 Equipment existing at sites (February 2007)

Clearly at the time of reporting several sites either did not have equipment available, or at least were unable to carry out a detailed inventory for
this activity. On the basis of these findings, each pilot site suggested future device purchases (section 1.2.5).




October 2007                                                             13                                                                  UNEW
ASK-IT D4.3.1                                                       Public                                                  Contract N. 5112981




1.2.5 Equipment Required at Sites

The following table lists the equipment identified by each pilot site for purchase. Where possible, each site has identified an actual number of
devices required, and a brief specification (i.e. make, functionality, etc.).

             Athens-        Bucharest         Genoa         The Hague        Helsinki        Madrid          Newcastle-         Nuremberg
          Thessaloniki                                                                                       Gateshead
Smart     23 (20 for      10 smart               2                                        10 (compatible     6 (with GPS    15 T-Mobile MDA
Phones    HIT, 3 for      phones for                                                      with                and WiFi)     III compact
          AIA)            user testing                                                    J2ME/MIDP
                                                                                          2.0)
PC                                               1                                        3 (servers)
Tablet    2 laptops       2 laptop PCs           1                                        3 tablet-pc                       1 Sub-Notebook
PC/                                                                                                                         Sony
laptop
PDA       4 with RFID     10 PDAs with 6 mini-PDAs         10                             10 (with      6 mini-PDAs
          (2 for AIA, 2   GPS and                          HP iPAQ                        communication
          for HIT)        Indoor LBS                       6515                           capabilities:
                          module for                                                      GPS,
                          the WI-FI                                                       Bluetooth,
                          network                                                         WiFi)
                          6 PDAs for
                          data
                          collection and
                          user testing
Kiosk
Other
                                            Table 1.5 Equipment required at sites (based on site feedback)




October 2007                                                          14                                                                 UNEW
ASK-IT D4.3.1                              Public                  Contract N. 5112981




1.3 Assessment of Infrastructure and Equipment at Pilot Sites

The information provided by the ASK-IT pilot sites relating to the infrastructure and
equipment existing, and the infrastructure and equipment required, was compared
with the Application Scenarios per site (D4.1.1). An assessment of the sites’ technical
capability was then carried out, based on the minimum infrastructure and equipment
required to fulfil the Application Scenarios. Further recommendations were made
where necessary. A summary of the assessment is presented in the table below.


      Pilot Site                                 Assessment
Athens-Thessaloniki    Plans for the smart house and smart car are well advanced
                       The scenarios in the airport (AIA) will require further
                       purchase of wireless motes or a similar system
Bucharest              Existing infrastructure and planned purchase of client
                       devices is the minimum required to perform the trial
                       activities
Genoa                  The proposed purchases of equipment will be the minimum
                       required to fulfil the scenarios. Synergies with MAPPED
                       project need to be established to finalise device requirement
Helsinki               Helsinki must report their planned purchases of devices
                       before an assessment can be made
Madrid                 Madrid’s planned purchases are sufficient to operate this
                       pilot site
Newcastle-Gateshead    Purchase of SDIO ZigBee cards to connect PDAs direct to
                       motes, along with purchase of additional motes (if required)
                       and further devices
Nuremberg              Nuremberg’s planned purchases are sufficient to operate this
                       pilot site
The Hague              A PC will need to be made available for one of the scenarios
           Table 1.6 Assessment of infrastructure and equipment at sites




October 2007                              15                                     UNEW
ASK-IT D4.3.1                               Public                   Contract N. 5112981




1.4 Infrastructure and Equipment at Pilot Sites (September
2007)


1.4.1 Wireless Interoperability

WLAN is much more appropriate for fast information transfer, especially if maps or
similar bulky data are downloaded. Though wireless does not provide full coverage it
will still support MI users in areas where other technologies (e.g. mobile
technologies) are not appropriate.


1.4.2 Equipment at Sites

A simple template was circulated to the pilot sites on 13th August 2007 in order to
catalogue the sites’ devices available for trial activities. This enabled the A4.3.2 team
to see whether the gaps identified in February 2007 (Table 1.5) had been addressed.
The resulting information is reported in the tables below.

Site: Athens-Thessaloniki
Device                 Specification                 Number           Date of
                                                                     Purchase
Smart Phones      Nokia N73                             3         March ‘07
Smart Phones      Nokia N93                             2         February ‘07
Smart Phones      Palm Treo 680                         1         February ‘07
Smart Phones      Samsung SGH-D830 Ultra                1         February ‘07
                  Edition 9.9
Smart Phones      HTC P3300 GPS-enabled                 1         February ‘07
                  Pocket PC
Smart Phones      HTC Qtek 9100 Pocket PC               1         February ‘07
                  Phone
Smart Phones      Nokia N95                             2         October ‘07
Smart Phones      Samsung X820                          1         February ‘07
Smart Phones      Nokia N72                             3         February ‘07
Smart Phones      Nokia 7360                            1         February ‘07
Smart Phones      Nokia 7390                            2         February ‘07
Smart Phones      Nokia 8800 Sirocco                    2         February ‘07
PDA               Fujitsu Siemens LOOX                  4         March ‘07
                  T830 Pocket PC, Phone
                  with GPS
PDA/smart         HTC TyTN II                           1         October ‘07
phone
Notebook          SONYTX3 XP, 1,2 GHz,                  1         March ‘07
                  16B
Notebook          Toshiba Satelite 0200-182             1         March ‘07
Notebook          Sony V.E.N. CIS/H                     1         March ‘07


October 2007                               16                                      UNEW
ASK-IT D4.3.1                            Public              Contract N. 5112981


Site: Athens-Thessaloniki
Device                 Specification              Number      Date of
                                                             Purchase
GPS bluetooth     Fortuna Clip-on bluetooth         1      March ‘07
device            GPS receiver
(external)
PC                HP XW6400DUO, HP                 1+1     August ‘07
                  DC7700M
Tablet            Fujitsu-Siemens Lifebook          1      August ‘07
PC/laptop         P-series
Media centre      Fujitsu-Siemens Scaleo C          1      August ‘07
IP camera         Axis 207(w), Linksys PTZ         1+1     August ‘07
Monitors          LG L1900E-BF, LG                 1+1     August ‘07
                  L1919S-SF
TV LCD            LG 42” 42LC3R                     1      August ‘07
Wireless router   ROUTER LINKSYS                    1      September ‘07
                  ADSL2+ SPEEDBO
                  WAG54GS-E1
Oven              TOYOTOMI WP700LI7                 1      To be
                                                           purchased asap
Refrigerator      PITSOS KTC 14005, 144lt           1      To be
                                                           purchased asap
Temperature       ELV JCU 10 TFS                    1      March ‘07
Sensor
Humidity          ELV JCU 10 TFS                    1      March ‘07
Sensor
Light Sensor      ELV HS485 LX1                     1      July ‘07
(Photometer)
Closure Probe     BKS Janus SE                      1      October ‘06
for Door
Movement          ELV FS20 PIRA                     1      July ‘07
Detector
RF Gateway        ELV FHZ1000 PC                    1      July ‘07
(FS20 System)
Wired Gateway     ELV HS485 PCI                     1      October ‘06
(HS485
System)
PC Gateway        Compaq Deskpro                    1      February ‘07
7” TFT with       CAR-DP 700T                       1      August ‘07
Touch Panel
Front Door        BKS Janus SE                      1      October ‘06
Locking
Mechanism
Power Supply      12V / 1A                          1      October ‘06
for BKS Janus
SE
Switched          ELV HS485 IO127                   1      August ‘07
Lights
Dimmed Lights     ELV HS485 D                       1      October ‘06


October 2007                            17                                  UNEW
ASK-IT D4.3.1                             Public                  Contract N. 5112981


Site: Athens-Thessaloniki
Device                 Specification               Number          Date of
                                                                  Purchase
Control unit for   ELV HS485 IO127                    3         August ‘07
wall-mounted
plugs
RF-controlled      ELV FS20 ST                       3          October ‘07
plugs
RF Power           ELV FS20 FMS                      1          August ‘07
Detector Plug
Washing            Simulation Module                 1          Developed in
Machine                                                         July ‘07
Oven               Simulation Module                 1          Developed in
                                                                July ‘07
Other              ORA Power Accessoires            2+1         2 pieces in
                   UK-EU Continental Power                      March ’07, 1
                   Adaptor                                      more in October
                                                                ‘07
                   ORA Memory 1GB Mini              4           March ‘07
                   Secure Digital
                   Card+Adapter
                   Klear Screen Wet/Dry             4         March ‘07
                   Klear Kloths
                   ORA Nokia Car Charger-           4         March ‘07
                   DC-4 Compatible
                   Western Digital Passport         1         February ‘07
                   80GB USB 2.0 2,5 E
                     Table 1.7 Equipment in Athens-Thessaloniki


Site: Bucharest
Device                   Specification             Number           Date of
                                                                   Purchase
Smart Phones       Nokia N95                          3         September 2007
PC                 Intel Core 2 Duo                   1         August 2007
Tablet             HP7200                             1         April 2007
PC/laptop
PDA                HTC P4350                         4          May 2007
Other
                          Table 1.8 Equipment in Bucharest


Site: Genoa
Device                   Specification             Number           Date of
                                                                   Purchase
Info currently not available as synergies with MAPPED project are still to be
confirmed
                             Table 1.9 Equipment in Genoa




October 2007                             18                                     UNEW
ASK-IT D4.3.1                           Public               Contract N. 5112981


Site: Helsinki
Device                 Specification             Number        Date of
                                                              Purchase
Smart Phones     Nokia N91                       10        2007
Smart Phones     Qtek 8310                        1        2005
Smart Phones     Nokia 6681                       1        2005-2006
Smart Phones     Nokia 6630                       1        2005-2006
Smart Phones     Nokia 6670                       1        2005-2006
Smart Phones     Nokia 3230                       1        2005-2006
PC               Modern office PC                 1        2006
Tablet           HP Compaq 6715b                  1        2007
PC/laptop        WinXP, 2 GB Ram
PDA              Qtek 2020                        1        2004
Other:           HP Jornada 568 64 MB,            5        2002
                 wlan card
                        Table 1.10 Equipment in Helsinki

Site: Madrid
Device                 Specification             Number         Date of
                                                               Purchase
Smart Phones     WLAN/GPS/UMTS                     10      1 available for
                 multimedia mobile phones                  testing (Nokia
                 CLDC 1.1/MSA                              N95, including
                 compliant:                                SIM card)
                    - Nokia E60, N73,                      Rest: Dec’07
                        N80, N91, N92,
                        N93, N95
                    - Sony Ericsson
                        M600, Z750, P990i
PC               Multimedia desktop PC              2      Dec’07
Tablet           Multimedia handheld               3       1 UMTS
PC/laptop        computer with                             modem and 2
                 WLAN/GPS/UMTS                             SIM cards
                 capabilities:                             available for
                    - Fujitsu-Siemens                      testing
                        Stylistic ST5022,                  Rest: Dec’07
                        Lifebook P1510,
                        Flybook
PDA              PDA with                          10      1 available for
                 WLAN/GPS/UMTS:                            testing (HTC
                    - HTC S710, Meteor,                    P3300,
                        Advantage, P3300                   including SIM
                    - QTEK 9000, 9090,                     card)
                        S200                               Rest: Dec’07
                    - Fujitsu-Siemens
                        Pocket Loox T830
Other:           Wearable emergency                2       Dec’07
                 devices
                          Table 1.11 Equipment in Madrid



October 2007                           19                                    UNEW
ASK-IT D4.3.1                            Public                  Contract N. 5112981



 Site: Newcastle-Gateshead
 Device                 Specification             Number        Date of
                                                               Purchase
 Smart Phones      O2 xda Orbit with 12             4        August 2007
                   month contracts (400min;
                   20.5MB data; 250 texts)
 Smart Phones      HTC P3300 Premium                1        May 2007
                   64MB RAM with
                   GSM/GPRS/EDGE,
                   Bluetooth, WiFi, mic +
                   speaker/headphone,
                   trackball and trackwheel
 PC                Local ASK-IT server              1        August 2007
 Tablet            OQO ‘ultra mobile’ PC            1        December
 PC/laptop         (XP tablet edition)                       2006
 PDA               HP iPAQ hw6500 with              6        2005
                   integrated
                   GSM/GPRS/EDGE
                   wireless radio, Bluetooth,
                   GPS navigation
 WiFi Router       Belkin Wireless G+ MIMO          1        December
                   Router                                    2006
 Infrared Beacon   Eyeled Infrarot-Baken            5        2006
 Motes             Crossbow ZigBee Motes           ~30       2005-6
 Sensorboard       MTS 300/310 Sensor board         6
                   (light, temperature, noise,
                   acceleration, magnetism)
 Bluetooth         O2 blue wireless headset         2        August 2007
 headset
 RFID reader       Inside Contactless Long          2        2006
                   Range Kit
 RFID reader       Inside Contactless               1
                   Proximity Kit
 Other:            SanDisk 2GB Micro SD             5        All October
                   Card memory cards                         2007

                   ORA Micro SD Card                1
                   Reader

                   3 Axis Digital Compass           1
                   (USB + serial)

                   3 Axis Accelerometer              1
                   Table 1.12 Equipment in Newcastle-Gateshead




October 2007                            20                                    UNEW
ASK-IT D4.3.1                            Public             Contract N. 5112981


 Site: Test Site Nuremberg
 Device                 Specification             Number        Date of
                                                              Purchase
 Smart Phones      T-Mobile MDA III                 3-4     August 2007
                                                            further
                                                            devices
                                                            November
                                                            2007
 Smart Phones      Nokia 6630                       2-3     November
                                                            2007
 PC                Fujitsu Siemens Primergy          1      August 2007
                   TX150 S5 as local ASK-IT
                   Server
 Tablet            Fujitsu Siemens Lifebook          2      August 2007
 PC/laptop         S6120
                   Fujitsu Siemens Lifebook
                   Si 1520
 PDA
 Other:            Fujitsu Siemens Pocket            1      August 2007
                   Loox T830

                   Nokia phones (TBC)               2-3     November
                                                            2007

                   Emtac CRUXII Bluetooth            2      September
                   GPS Receiver                             2007

                   Fujitsu Siemens                   1      October 2007
                   BLUETOOTH V2.0 USB-
                   Stick

                   Others (not yet confirmed)       1-2     November
                                                            2007

                       Table 1.13 Equipment in Nuremberg

 Site: The Hague
 Device                  Specification            Number        Date of
                                                               Purchase
 Smart Phones      HTC P3600                        4       Oct. 2007

 PC                HP Server                        1       Oct. 2007
 PDA
 Other             Headsets Bluetooth/Bone          2       Oct. 2007

 RFID              Readers                          4       Oct. 2007
                   Tag                            50-60     Oct. 2007

                        Table 1.14 Equipment in The Hague



October 2007                             21                                UNEW
ASK-IT D4.3.1                               Public                   Contract N. 5112981



2 Installation & Integration at Sites
This chapter provides an overview of the process of integrating the different
components of ASK-IT into local servers at the pilot sites. By following this approach
each component can be tested on a stand alone basis. Following successful stand
alone tests the fully integrated system can be tested by the end user volunteers.

Development and integration of the ASK-IT components involves a great many
project partners, and thus requires excellent management and co-ordination of
activities in order to carry out the work thoroughly and to time. To assist in this, a
technical task force has been set up comprising Netsmart, Comarch, Singular,
CERTH/ITI, UPM and PTV.

This chapter presents the status of each component, with contributions from key
technical partners. It begins in section 2.1 by describing the rationale behind installing
local servers at the pilot sites, along with a description of the technical specification
and the current installation status. Section 2.2 provides a short overview of the
integration of mobile devices, in particular how compatibility issues have been
solved. Finally, section 2.3 provides a short description and status report of the
individual modules that have been developed for ASK-IT in SP2 Tools for All.


2.1 Server (ASK-IT and Local) - Approach & Status

Each pilot site that is involved in the ASK-IT project will have assigned its own local
server. There are two main reasons for the existence of a local server in each pilot
site:

       To maintain a database for the local users.
       To maintain a database for the available ASK-IT servers.

The reason for holding the users’ database is to speed up the authentication procedure,
as if all the ASK-IT users were held under one database it would be a very time
consuming procedure.

On the other hand, a database of the available ASK-IT servers is needed to perform
the remote authentication of a user. For example, assume that a user registered in the
English ASK-IT server is travelling abroad, say in Spain. The Spanish ASK-IT server
must have all the required information for the English ASK-IT server in order to
require the authentication of the travelling user.

The database schema for the users and the ASK-IT nodes is shown in the table below:

     Users’ database schema                       ASK-IT nodes database schema
HomeAddress_Country                           Country
HomeAddress_Postal code                       Town
HomeAddress_City                              Node IP location
HomeAddress_District                          Latitude


October 2007                               22                                      UNEW
ASK-IT D4.3.1                              Public                   Contract N. 5112981


         Users’ database schema               ASK-IT nodes database schema
HomeAddress_Street name                    Longitude
HomeAddress_Street number
Username
Password
Home telephone
Mobile telephone
Office telephone
OfficeAddress_Country
OfficeAddress_Postal code
OfficeAddress_City
OfficeAddress_District
OfficeAddress_Street name
OfficeAddress_Street number
First name
Last name
Email
                         Table 2.1 Users’ Database Schema

Each ASK-IT server will be completely different from any other in terms of the
services that it provides. This means that if the pilot site in Bucharest is required to
provide the e-working and e-booking services, these will be installed only in that
particular server.

The hardware and software requirements of the ASK-IT servers are shown in the table
below:
                      Software/Hardware Requirements
CPU at least 2.8 MHz
RAM at least 1GB
HDD at least 80GB
Network card 10/100/1000
Microsoft Windows 2003 – Service Pack 1 with the latest Java version installed

Knoplerfish OSGI
SUNOne Directory Server 5.2
SUNOne Application Server 9
VNC viewer for remote management
              Table 2.2 Server Hardware and Software Requirements

A further requirement is that some particular ports are opened for the correct
operation of the ASK-IT server. These are shown in the next table along with the
explanation of each port:

                   Port                                       Reason
1389                                         Directory Server
1390                                         Directory Server Administration
80                                           Web server
8080                                         Secure Web server
4848                                         Administration port for Application


October 2007                              23                                       UNEW
ASK-IT D4.3.1                               Public                   Contract N. 5112981


                   Port                                        Reason
                                            server
1099                                        MAS server bundle
20 and 21                                   FTP
3389                                        Remote Desktop
6837                                        Leap Jade
9999                                        TSF bundle
6969                                        VNC viewer
                                Table 2.3 Server Ports

In the next table the status of availability of the ASK-IT server in the predefined pilot
sites, at the time of writing this report, is shown:

                   Sites        Server           Windows         IP
                               available?         2003        available
                Athens-
                Thessaloniki
                Bucharest
                Genoa
                Helsinki
                Madrid
                Newcastle-
                Gateshead
                Nuremberg
                The Hague
                  Table 2.4 Site Server Status Report (October 2007)

The methodology for the integration of a single ASK-IT server is shown in the table
below, along with the responsible entity:

No. Description                                                        Responsible
1   Purchase of the server                                              Pilot site
2   Installation of the operating system and the latest                 Pilot site
    service pack
3   Installation of VNC software (required for the remote                 Pilot site
    installation of the remaining software)
4   Installation of the OSGI framework                                    NetSmart
5   Installation of SunOne Directory server (required to                  NetSmart
    hold the databases for the users and the ASK-IT nodes)
6   Installation of SunOne application server (required for               NetSmart
    the administration interface of the ASK-IT server)
7   Installation of the required bundles for the OSGI in                  NetSmart
    order to provide the services needed at the specific pilot
    site
                    Table 2.5 Server Integration: Responsibilities




October 2007                                24                                         UNEW
ASK-IT D4.3.1                             Public                  Contract N. 5112981


2.2 Integration of Mobile Devices - Approach & Status


2.2.1 Mobile devices

The devices listed in section 1.4.2 must be compatible with the underlying ASK-IT
technical approach in order to be used effectively at the pilot sites. Moreover, any
type of mobile device that supports the CLDC 1.1 configuration and MIDP 2.0 profile
is compatible with ASK-IT technical requirements.

Mobile devices that had been tested by September 2007 were Nokia N73, Nokia N93,
Nokia N90, Nokia 6630, Sony Ericsson K510i, and the Sony Ericsson P990i. The
above devices support CLDC 1.1 and MIDP 2.0.

However, any other device can test the ASK-IT MIDP application. There is a demo
available at the project internal ftp that can be downloaded for self-testing. Also, a
short description about the steps that must be followed in order to test the
compatibility of this device is included.

This demo verifies:
       Connectivity issues (send/receive processes between MASClient connection
       and MASServer under GPRS and Internet). It can also be tested under WLAN
       connection
       HTTP connection, concerning receiving maps as URL
       J2ME graphical issues
       o The size of form is independent for each device.
       o Display map as image

The current version of MIDP application is the vg2.0 is available and uploaded at the
project internal ftp.

This folder contains:
       The ASKIT_MIDP_vg2.0.jar, which is the MIDP application version
       vg2.0
       README_Installation.txt; contains instructions about the installation
       procedure
       README_To_Run_vg2.0.txt; describes what function the current
       development supports. It also provides feedback of examples for the user in
       order to test the application


2.2.2 PDA and PC integration

The devices listed in section 1.4.2 must be compatible with the underlying ASK-IT
technical approach in order to be used effectively at the pilot sites.

The ASK-IT technical specifications for PDA platform include a Windows Mobile
2005+ operating system and JVM WebSphere Everyplace Micro Environment
(WEME-J9) personal Java from IBM.


October 2007                             25                                     UNEW
ASK-IT D4.3.1                              Public                   Contract N. 5112981



For the PC platform the Windows XP OS and Windows Vista OS are appropriate.
Thus, Java SDK and runtime must be installed in the computer. For the time being,
Java version 1.6.02-b06 has been used.

More information can be obtained from the Internal Deliverable 3.3.4 ‘ASK-IT Client
Integration’ (Oct 2007).


2.3 Integration of ASK-IT Modules – Approach & Status
2.3.1 Localisation

This module provides enhanced localisation accuracy in order to achieve the overall
project objective of flexible geo-referenced services. This was a relatively complex
task as the localisation technologies have to support citizens with different types (and
varying degrees) of impairment. The levels of accuracy required were defined by the
user needs and application requirements and reported in ASK-IT D2.2.1 ‘Localisation
Module Specification’ (Sept 2006).

Work has focused primarily on GPS for outdoor localisation and on the synergic use
of GPS, Galileo and EGNOS with other methods (based on other technologies, such
as W-LAN, etc.) for provision of precise, robust navigation.

Furthermore, approaches to enhanced performance in specific circumstances (e.g.
urban canyons, indoor navigation, etc.) have been investigated.

The localisation module has been developed in JAVA. It takes positioning
information from different sources and does a ranking according to the accuracy. For
example, Cell ID has a low accuracy, thus the position of this source will only be
taken if nothing else is available. Motes have a good accuracy, but are not a mature
technology and require gathering of considerable additional data. EGNOS/GPS also
possesses good accuracy (1-2m with optimal reception), but is mainly used outside.

Localisation using motes and RFID has been the subject of research in ASK-IT.
Newcastle-Gateshead is the only site that will use motes for indoor localisation. Some
additional work will be carried out into dead reckoning techniques. The Hague is
using RFID as the Dutch pilot team are able to integrate that technology locally.


2.3.2 Navigation

This module supports flexible geo-referenced route guidance for MI users, taking into
account their specific accessibility requirements. The navigation/route guidance
industry has focused primarily on developing technologies for motorists rather than
pedestrians, for whom the level of fine detail required is greater. ASK-IT has sought
not to develop generic tools but instead tools adapted to the accessibility level that
specific MI user groups require.




October 2007                              26                                      UNEW
ASK-IT D4.3.1                              Public                  Contract N. 5112981


The enhanced localisation module (D2.2.2 Enhanced Accuracy Localisation Module,
Sept 2007) of WP2.2 and the special content gathered within SP1 has been integrated
into a navigation module to provide guidance applications which support the mobility
impaired.

Navigation/route guidance can be regarded as the most important application made
available in ASK-IT. The module development team is helping the pilot sites develop
appropriate digitised maps of certain locations within their demo areas. The routing
algorithm for these maps will run on the server side and the maps will be stored on the
mobile device. Only PC and certain types of PDA will be compatible with the route
guidance software. Sound or voice output will be available where possible.


2.3.3 e- Commerce

The aim of the e-Commerce module is to provide mediation of services and content to
MI volunteers, allowing them to book and pay for services.

ATCRom has developed a common platform providing commercial and payment
functionality for services provided in the test sites through an e-Commerce website.
The platform interfaces with current services using a common functionality and user
interface for required services such as check-out and payment processing. It should
also support the use of an assortment of mobile devices, through a user friendly and
consistent interface. The key requirement for sites integrating this module is a local
data provider.


2.3.4 Domotics

The aim of the domotics module is to provide seamless home environment
management to the MI volunteer as well as seamless infomobility services. The
premise behind this module is that all journeys begin and end at home, whilst
independent living is a key social objective of all research into products and services
for MI people. Planning trips is a crucial activity for MI people and much trip
planning takes place at home. An additional function of this module is the opportunity
for people to access and control their home environment while on the move.

The sites demonstrating the domotics module (Athens-Thessaloniki, Madrid,
Nuremberg) will provide an intelligent home environment with a range of hardware
installations (see section 1.2.2).


2.3.5 In-Car

Advanced Driver Assistance systems (ADAS, such as cruise control, lane departure
warning, collision avoidance, blind-spot warning, etc.) as well as in-vehicle
information and communication systems (IVICS, such as navigation, route guidance,
emergency calls, Internet access, etc.) are becoming a familiar feature of motor
vehicles. Some of these products and services are of special importance to MI drivers,
for instance intersection control, parking manoeuvres support, lane drift avoidance.


October 2007                              27                                     UNEW
ASK-IT D4.3.1                               Public                   Contract N. 5112981


However the workload imposed on the driver creates certain limitations in terms of
the driver’s physical ability and in terms of the technologies that can be utilised.

This module integrated ADAS/IVICS support into the ASK-IT user interface. It has
also provided a strategy to present information to the driver and ways to interact with
the system. The system will be demonstrated only in the Greek pilot site. ASK-IT
services will be offered within the vehicle, but limited to the driving context and
persons’ residual abilities.


2.3.6 e-Health

This module provides mediation of health and social care services to MI volunteers.
The system provides personalised care to MI volunteers, including medical-related
information. A key objective is to provide a feeling of security and confidence for
people to go about their everyday tasks.

Sites utilising this module will work with a local emergency operator. Wearable
health sensors are being purchased in order to receive information.


2.3.7 Word Prediction

This module supports seamless environment management by helping MI people
interact with computer-based systems. The word prediction module supports six
languages.


2.3.8 Kiosk Interface

This module supports seamless environment management by offering the user an
accessible gateway to public terminal systems during a trip. Public kiosks are an often
overlooked and much used facility (e.g. ticket machines, bank terminals, museum
information kiosks, shopping terminals, etc.) which are of great benefit to travellers if
they are fully accessible. This module will only be demonstrated in Den Haag.


2.3.9 e-Learning & e-Working

This module supports seamless environment management by mediating e-Working
and e-Learning services and content through the use of assistive software modules as
well as key assistive devices. This service will be demonstrated in Athens-
Thessaloniki and Bucharest, and will only be available through PDAs.


2.3.10 User Interfaces

User Interfaces (UIs) must be available for different MI typologies. Altogether 16 UI-
Prototypes have been developed within the Workpackage 2.10. These are presented


October 2007                               28                                      UNEW
ASK-IT D4.3.1                              Public                  Contract N. 5112981


in Deliverable 2.10.1 ‘Full Set of Interface Concepts and Prototypes’ (Prototype and
Report). D2.10.1 gives a broad overview of the requirements analysis, which was the
basis for the selection of these prototypes. It also gives an overview of the UI
elements and metaphors which were available. Furthermore D2.10.1 describes the
reason for choosing the specific 16 prototypes, the realization of them, and the
underlying objectives of the whole User Interface in ASK-IT.

Development of user interfaces for each of the applications listed in 2.3.1-2.3.9 above
is being carried out by various partners (see annex). Co-ordination of this complex
task is carried out by CERTH/HIT.

The following list gives an overview of the different prototypes and their respective
target group:

       Inter-modal travel planning for wheelchair users
           o Wheelchair users without severe cognitive impairments that are able to
              use a computer with assistive devices if needed.
       Automatic rendering of Web content into audio: Tools for site developers and
       end-users (Weblection)
           o Although WebLection was primarily inspired by research for blind
              users, significant benefits emerge for all, and the potential of
              increasing the uptake of the Web by a variety of potential users is
              offered. In particular, the proposed approach is considered to be useful
              for: the typical, contemporary Internet user characterised by an
              increasing need for mobility and for interchanging between online and
              offline working modes; the very young, the elderly and the
              inexperienced Internet user, who often find it difficult to build
              effective conceptual models of the functionality of browsers or of the
              workings of the Web; people with a disability, in addition to the blind,
              for instance users with impaired memory who experience difficulties in
              exploration activities that involves remembering many combinations of
              actions and outcomes, and users with upper limb impairments who are
              finding user interfaces that require extensive mouse or keyboard usage
              prohibitive.
       Pedestrian navigation on mobile devices
           o Adult users not tailored to a specific handicap (all user groups being
              able to use ordinary mobile graphical user interfaces with text and
              graphical elements). It serves as the conceptual basis for way-finding
              support in ASK-IT and will be adapted to the specific user groups in
              terms of GUI elements and acoustic elements.
       ASK-IT e-commerce and e-payment assistant for visually impaired people
           o Theoretically, all types of user groups can be involved in using the
              different services on the condition that each user is provided with the
              proper interface/application.
       Car-related HMI prototypes /Haptic elements in car – adapted ADAS
       prototype
           o Different groups will be supported, for instance people with hearing or
              vision problems, dyslexic/illiterate, upper limb impaired (stability, use
              of steering knob – one hand steering), neck problems and elderly



October 2007                              29                                     UNEW
ASK-IT D4.3.1                             Public                   Contract N. 5112981


               people (problems in PC using, concentration, memory, combined or
               complex task execution, etc.).
       Car-related HMI prototypes/Adapted HMI for the use of ASK-IT services
       related to IVICS
           o Since the aim was to adapt vehicle electronics and telecommunication
               services, which mostly involve the driver’s senses (voice, sight, touch)
               and upper limb mobility, the selection criteria focused on perception
               related limitations and on upper body impairments (including hearing
               impairment; vision impairment: colour blind; communication
               producing impairment: illiterate /dyslexic; physiological impairment:
               psycho physiological; cognitive impairment; age over 65 (from middle
               old to very old); upper limb impairment; upper body impairment: neck
               problems).
       Assistive devices interface
           o The targeted user groups for this prototype are primarily people with
               motor and locomotive disabilities with emphasis on congenital
               conditions (i.e. cerebral palsy, muscular dystrophy, multiple sclerosis,
               spina bifida, amyotrophic lateral sclerosis, arthritis, etc.). More
               specifically, the ASK-IT iRemote prototype is aimed at users with a
               powered wheelchair without severe cognitive impairments that are able
               to use a computer and / or a mobile phone with the support of assistive
               devices if required. The aim of the prototype overall is to enable a
               person who cannot press the keys of a mobile phone to operate the
               phone with a 5 switch device or the joystick on their powered
               wheelchair.
       Speech user interface
           o Visually impaired and blind users on the move, who are not able to use
               conventional user interfaces without the help of screen readers or
               Braille.
       Acoustic user interface elements
           o Visually impaired people would benefit from an alternative
               information presentation next to the most commonly used interaction
               form, the graphical user interface. Also people without a visual
               impairment benefit from acoustic user interface elements. When
               problems occur with a graphical user interface, for example when
               information is missed because of a visual overload, acoustic user
               interface elements can enhance an existing graphical user interface.
               Also situations of use can impair the utilisation of visual interaction
               elements. Being on the move, the classical GUI supports non-precise
               interaction to only a limited level – many people stop to use their PDA
               or interact with their mobile phone. Therefore, possible target user
               groups can be cognitive impaired people, wheelchair users, deaf and
               blind people.
       Pedestrian navigation for blind
           o The prior target-groups are visually impaired and blind people as the
               prototype concentrates on the non-visual representation of information.
               Furthermore the acoustic information is a convenient interaction
               modality for mobile contexts or other situations in which continuous
               visual attention is not possible.



October 2007                              30                                     UNEW
ASK-IT D4.3.1                            Public                  Contract N. 5112981


       GSLA-based interaction (Greek Sign Language Animation)
          o This Prototype aims to help deaf people, who are able to use the Greek
              Sign Language.
       Domotic control UI
          o In general, the domotic control UI is customized to the special needs of
              elderly & disabled users. Furthermore, it is appropriate for dyslexic
              persons, because the UI concept is based on images instead of text
       Multimodal personal assistant for digital home services.
          o Different MI user groups have been addressed, mainly people with
              physical disabilities. Interaction modalities are being selected
              according to the user profile, available mobile terminal and
              environment circumstances. Input options are tactile (through keypad
              or touch screen); output is provided through graphics, speech or haptic
              elements such as vibration.
       Prototype for elderly people
          o User groups are elderly people, people with small cognitive problems
              (dealing with complex tasks, having problems with memory) and
              people with psychological problems/physiological problems affecting
              stamina.
       Symbol-based interaction for ASK-IT
          o The target user groups for this prototype are people with
              communication producing and receiving difficulties. Further more, it is
              supposed that people with cognitive impairments could also benefit
              from the pictographic approach taken for this prototype, especially if
              they suffer from attention problems or lack the ability of abstract
              reasoning.
       A haptic mobile navigational aid for blind people
          o The device is developed for blind and deaf people.




October 2007                             31                                    UNEW
ASK-IT D4.3.1                               Public                   Contract N. 5112981




3 Plans for Functional Testing & Optimisation
This chapter reviews methodology for testing the ASK-IT system and services prior to
full trials beginning. It also presents the method of debugging which will be
implemented where required.


3.1 The Testing Process

Testing is the process of examining an application to ensure it fulfills the
requirements for which it was designed and meets quality expectations. More
importantly, testing ensures that the application meets end-user expectations. It is the
most important factor in the ASK-IT system, since it is designed to satisfy disabled
peoples’ needs.

As presented in Chapter 2, the ASK-IT system consists of many modules i.e.
Domotics, e-Payment, Route Guidance, Health and Emergency, etc. Each module is
divided into various components:

       The logic component (server side);
       The client application – connection module;
       The client application – GUI layer.

The requirements that guide their implementation are continuously changing.
Consequently, building applications that do what they are supposed to do - and that
continue to do so as changes are made - is not as easy as it might seem from the
outside. In addition, human architects, designers, and developers often make mistakes.
In either case, the results are defective.

By testing an application, defects that arise from these sources and others can be
uncovered. These defects include typographical errors, logic errors, errors introduced
due to insufficient understanding of the problem domain, and errors introduced due to
poor programming practice. The process of uncovering these defects is made more
difficult due to the nature of the software defects themselves: they don’t necessarily
occur where expected. The earlier in the development cycle that testing starts the
better. Planning is crucial to a successful testing programme. Figure 3.1 illustrates
each component in the testing process. The components include:

Test cases: inputs to test the system and the predicted outputs from these inputs. This
set of conditions and variables should help establish whether the system operates
according to its specification. In order to fully test whether all the requirements of an
application are met, there must be at least one (or two in some cases) test cases for
each requirement, unless a requirement has sub-requirements. In that situation, each
sub-requirement must have at least one test case.




October 2007                               32                                      UNEW
 ASK-IT D4.3.1                               Public                       Contract N. 5112981




      Test cases             Test data                Test results              Test reports




Design test        Prepare test               Run                    Compare
  cases               data                component                   results
                                         with test data


                            Figure 3.1 The Testing Process

 Test data: inputs which have been devised to test the system. In this case it should be
 a well-prepared set of parameters, designed to operate within the test environment.

 Test results: the result of invoking some action, for example it can be an output from
 mobile devices. Briefly it is what the tester should see after the test steps have been
 completed.

 Test report: should contain detailed description of any bug, the steps that will trigger
 the bug, and actual results, i.e. what the application did after performing the above
 steps, and what the application should have done if the bug was not present. The aim
 of reporting bugs is to help developers to reproduce the bug, so they can fix them
 properly.

 The testing process in ASK-IT should consist of two phases: component testing and
 integration testing.


 3.1.1 Unit and Component Testing

 Unit and component testing aims to check the building blocks of an application in
 isolation from the application’s other units and components. Units are single classes,
 while components can consists of several units. Several factors contribute to the
 importance of making component testing a high priority of any software development.
 Firstly, finding the error (or errors) in the integrated module is much more
 complicated than first isolating the units, testing each, then integrating them and
 testing the whole. Preparing the environment to run isolated components (drivers,
 stubs) may be cost- and time-consuming, but efforts in that level of development
 process should result in reducing the likelihood of discovering errors contained in
 more complex pieces of the ASK-IT application.

 These tests are derived from developer’s experiences and should start at an early stage
 of the implementation process ready for integration tests. Each relevant partner of the



 October 2007                               33                                           UNEW
ASK-IT D4.3.1                               Public                      Contract N. 5112981


consortium should be responsible for delivering tested components. Integration testing
is a logical extension of component testing


                Component testing                                 Integration testing
                                          TESTING




3.1.2 Integration Testing

Integration tests should assess the integration and communication between the
components and systems that comprise the ASK-IT system. Integration testing
identifies problems between components. There are two main strategies in integration
testing. These are:

3.1.2.1 Top-down testing
Testing should start with a top-level system (application). It allows testing of highest-
level modules (application logic) early in the development process. When needed,
low-level components can be replaced by stubs, but the application can still be tested
and integrated from the top-down. This kind of integration should be done when
integrators don’t have all components, but tests must be started. In case of graphical
user interface module testing this method would be the best solution.


      Top-level                                       Top-level
     component              TESTING                  component                TESTING




                            2 Level          2 Level           2 Level              2 Level
                             Stub          component         component               Stub




                                Figure 3.2 Top-Down Testing

3.1.2.2 Bottom-up testing
In this approach the lowest-level components are integrated, and tested in levels until
a complete system is created. By using this strategy, low-level components are tested
early in the development process. It also minimizes the need to create stubs. The
disadvantage of this kind of approach is poor support for an early release of limited
functionality.




October 2007                               34                                           UNEW
ASK-IT D4.3.1                               Public                     Contract N. 5112981




                                                                                    T
                                                                                    E
                  N Level              N Level              N Level                 S
                component            component            component                 T
                                                                                    I
                                                                                    N
                                                                                    G




                             N-1 Level                     N-1 Level
                            component                     component


                             Figure 3.3 Bottom-Up Testing

3.1.2.3 The best solution
Top-down integration is better at discovering errors in system architecture. It also
allows limited demonstration of a complete system at an early stage of the ASK-IT
development process. On the other hand bottom-up testing allows testing of each
component separately and it has proved its value in a large percentage of defects
identified during its use. It is recommended that in projects where modules or sub-
systems are integrated to create larger systems, a combination of these strategies
should be used.

One other important issue is interface testing. The objective of this is to detect faults
due to interface errors or invalid assumptions about interfaces. Because sub-systems
encapsulate certain services and sets of methods, it is important to avoid
misunderstandings between other sub-systems.


3.1.3 Regression Testing and Optimization

During the development process partners should also consider regression tests.
Whenever modifications are made the development team should rerun tests in order to
test if a new code breaks anything that previously worked properly. Another
important task is to watch for side effects of a new version of a component, module or
complete system.

The optimization process is closely related with testing. It can be described by a four
phase cycle.




October 2007                               35                                       UNEW
ASK-IT D4.3.1                               Public                Contract N. 5112981



                                Collecting data




       Testing                                                 Analyzing data




                                Configuring/Tuning
                              Implementing changes


                 Figure 3.4 Optimisation Testing: the Four-Phase Cycle

Before starting this kind of testing and optimization several issues should be
determined. Firstly services that clients require should be determined. Levels of
demand for these services should also be established. The most common metrics for
load are: number of clients and amount of time between receipt of reply by client
application and submission of request.

After collection of performance data, it should be analyzed to determine bottlenecks.
Results can be compared to baseline performance. Then development teams should
determine which components or units are candidates for change. It is important to
spend some time tracing performance problems. After implementing changes,
partners should rerun tests and check whether these changes improved module
performance. It is also crucial to watch for side effects of a changed component or
unit.

3.2 Bugzilla – Bug-Tracking System

Bugzilla is a defect-tracking software which can help optimise the software
development process. It comprises an open-source software which will be available
for all participants and development teams via the Bugzilla web page located on the
ASK-IT server. Individual development teams will thus be able to track the bugs in
their modules. The main benefits of using defect-tracking software are:

       Improving communication between SP1, 2, and 3 development teams;
       Increasing quality of ASK-IT modules and service;
       Ensuring accountability of development teams for each module.




October 2007                               36                                   UNEW
ASK-IT D4.3.1                               Public                   Contract N. 5112981


3.2.1 Anatomy of a Bug

The core of Bugzilla is the screen which displays a particular bug. It is a good place to
explain some Bugzilla concepts (see Figure 3.5).


3.2.1.1 Product and Component
Bugs are divided up by Product and Component, with a Product having one or more
components in it. For example, the Route Guidance Module (acting as a ‘Product’) is
composed of several Components:


3.2.1.2 Status and Resolution
Status and resolution define exactly what state the bug is in, from not even being
confirmed as a bug, through to being fixed and the fix confirmed by Quality
Assurance. It also gives the different possible values for Status and Resolution. The
status field indicates the general health of a bug. Only certain status transitions are
allowed. These are listed below.




                              Figure 3.5 Bugzilla Screen




October 2007                               37                                      UNEW
ASK-IT D4.3.1                             Public                 Contract N. 5112981




                               Route
       Domotics               Guidance                E-payment           Products
                               Module




   MAS          Geocodin       Navigation          Location    GUI
                                                                       Component
  Service       g Service       Service            Service


                       Figure 3.6 Products and Components

UNCONFIRMED
    This bug has recently been added to the database. Nobody has validated that
    this bug is genuine. Users who have the ‘can confirm’ permission set may
    confirm this bug, changing its state to NEW. Or it may be directly resolved
    and marked RESOLVED.

NEW
       This bug has recently been added to the assignee’s list of bugs and must be
       processed. Bugs in this state may be accepted, and become ASSIGNED,
       passed on to someone else, and remain NEW, or resolved and marked
       RESOLVED.

ASSIGNED
     This bug is not yet resolved, but is assigned to the proper person. From here
     bugs can be given to another person and become NEW or resolved and
     become RESOLVED.

REOPENED
    This bug was once resolved, but the resolution was deemed incorrect. For
    example, a bug is REOPENED when more information shows up and the bug
    is now reproducible. From here bugs are either marked ASSIGNED or
    RESOLVED.

RESOLVED
    A resolution has been taken, and it is awaiting verification by QA. From here
    bugs are either re-opened and become REOPENED, are marked VERIFIED,
    or are closed for good and marked CLOSED.

VERIFIED
     QA has looked at the bug and the resolution and agrees that the appropriate
     resolution has been taken. Bugs remain in this state until the product they were
     reported against actually ships, at which point they become CLOSED.



October 2007                             38                                    UNEW
ASK-IT D4.3.1                              Public                  Contract N. 5112981


CLOSED
    The bug is considered dead, the resolution is correct. Any zombie bugs that
    choose to walk the earth again must do so by becoming REOPENED.

All bugs which are in one of these ‘open’ states (Unconfirmed, New, Assigned,
Reopened) have the resolution set to blank. All other bugs will be marked with one of
the following resolutions:

FIXED
     A fix for this bug is checked into the tree and tested.

INVALID
     The problem described is not a bug.

WONTFIX
    The problem described is a bug which will never be fixed.

DUPLICATE
     The problem is a duplicate of an existing bug. Marking a bug duplicate
     requires the bug# of the duplicating bug and will at least put that bug number
     in the description field.

WORKSFORME
    All attempts at reproducing this bug were futile, and reading the code
    produces no clues as to why the described behaviour would occur. If more
    information appears later, the bug can be reopened.

MOVED
    The problem was specific to a related product whose bugs are tracked in
    another bug database. The bug has been moved to that database.

3.2.1.3 Assigned To
‘Assigned to’ refers to the person responsible for fixing the bug. Each component has
its own default person in charge of resolving the bug assigned during creation of the
component process. Every time this field changes, the status changes to NEW to
make it easy to see which new bugs have appeared on a person’s list.

3.2.1.4 Severity
This indicates how severe the problem is - from blocker (‘application unusable’) to
trivial (‘minor cosmetic issue’). This field describes the impact of a bug.

  Blocker           blocks development and/or testing work
  Critical          crashes, loss of data, severe memory leak
  Major             major loss of function
                    minor loss of function, or other problem where easy workaround is
  Minor
                    present
  Trivial           cosmetic problem like misspelled words or misaligned text
  Enhancement       request for enhancement
                            Table 3.1 Ranking of Severity


October 2007                              39                                    UNEW
ASK-IT D4.3.1                              Public                  Contract N. 5112981




3.2.2 Life Cycle of a Bug

The life cycle, also known as work flow, of a bug is currently hard-coded into
Bugzilla (see Figure 3.7).




                            Figure 3.7 Life Cycle of a Bug


3.2.3 Plans for Bugzilla in ASK-IT

In order to configure Bugzilla for ASK-IT project requirements, several activities
have been performed:




October 2007                              40                                     UNEW
ASK-IT D4.3.1                             Public                  Contract N. 5112981


           The ASK-IT system hierarchy has been defined. The system is divided
           into so-called products (E-learning, Domotics, E-payment, Health and
           Emergency management etc.);
           The partner who is responsible for delivering the defined product defined
           components (e.g. GUI, Service1, Service2, Documentation) of that product
           within Bugzilla;
           Each of these partners defined a person assigned to each component. This
           person has been responsible for fixing that component. Bugs were
           automatically reported to this component assigned person;
           Each partner responsible for developing some parts of the ASK-IT system
           received an administrator user account so new users were created
           individually (initially all users, products, components with assigned users
           were created and configured by the partner Comarch);
           Each partner was able to create their own users in order to report bugs and
           comment on outstanding issues.

Based on this debugging of ASK-IT components and single services, has been
performed; an activity tat is ongoing, as new services are integrated gradually to the
system.




October 2007                             41                                     UNEW
ASK-IT D4.3.1                              Public                   Contract N. 5112981



4 Integration Plan
This chapter revisits the schedule for integration originally described in Internal
Deliverable 4.3.1 ‘Site Infrastructure Development’ (February 2007). The Gantt chart
below shows the phased integration process based on the latest feedback from the
pilot sites and from the technical partners who are responsible for developing,
integrating and testing the ASK-IT modules.

In the chart, the pale yellow shading denotes tasks which are the sole responsibility of
the relevant work packages. The dark yellow shading denotes tasks which are
achieved jointly between relevant WPs and the sites, or are the sole responsibility of
the sites.




October 2007                              42                                      UNEW
ASK-IT D4.3.1                                                       Public           Contract N. 5112981




Aug 07 Sept 07 Oct 07 Nov 07 Dec 07 Jan 08 Feb 08 Mar 08 Apr 08                            May 08
   Purchase of
   equipment
   Delivery of
ASK-IT modules
 Installation of
  local servers
          Integration of ASK-IT modules
                               Stand alone modules testing
                    Installation of WLAN
                                        Overall integrated system trials and evaluation
                                      (Site manager/technical integrator/WP5.8/WP4.6)
Table 4.1 Gantt chart showing expected phased integration process




October 2007                                                        43                          UNEW
ASK-IT D4.3.1                               Public                   Contract N. 5112981



5 Summary
D4.3.1 has presented information provided by the ASK-IT pilot sites relating to the
infrastructure and equipment existing and required per site, in order to effectively
perform the proposed Application Scenarios (D4.1.1). It has proceeded to explain the
procedure and status of installation and integration of ASK-IT modules and client
devices at the sites.

This report relates to work carried out in A4.3.2 and A4.3.3. These are technical
activities that require the co-ordination of the A4.3.2 leader (Netsmart) and the A4.3.3
leader (Comarch) in collaboration with site technical integrators and the Technical
Task Force.

A4.3.2 ‘Installation and Integration at Sites’ carries out the following tasks:
           The installation of new infrastructure;
           The integration of ASK-IT modules into site equipment;
           Adaptation/customisation of infrastructure/equipment where required (e.g.
           purchase of additional client devices such as WiFi cards, where necessary).

Thus A4.3.2 helps sites deliver the required technical infrastructure based on the sites’
local needs.

A4.3.3 ‘Functional Testing and Optimisation’ carries out the following tasks:
          On-site technical verification and debugging of modules independently as
          they are installed;
          To provide training to site technical integrators to enable local
          maintenance of modules during trial process.




October 2007                               44                                      UNEW
ASK-IT D4.3.1                                Public                   Contract N. 5112981



6 Annex 1: Templates of existing and required
infrastructure and equipment

Site Name__________________________________________________


       TABLE 1: INFRASTRUCTURE AND EQUIPMENT
                       EXISTING

Infrastructure (Existing)                     Details
What infrastructure do you already have       [Please give details]
available at your pilot site?
   • Satellite based technology
            o GPS
            o Other (name)
   • Mobile technology
            o 3G
            o GSM
            o GPRS
            o Other (name)
   • Wireless technology
            o RFID
            o WiFi
            o Motes
            o Smart cards
            o Other (name)

Specific Infrastructure
(Existing)
What specific infrastructure do you           [Please give details]
already have available at your pilot site?
    • Smart house
    • Smart vehicle
    • Other (name)

Equipment (Existing)
What mobile/ fixed equipment do you           [Please give details, including numbers
already have available at your pilot site?    of devices]
    • Mobile phones
    • Fixed PC (at home/office)
    • Tablet PCs/laptops
    • PDAs
    • Fixed info-kiosks
    • Other (name)


October 2007                                 45                                    UNEW
ASK-IT D4.3.1                                Public                   Contract N. 5112981


       TABLE 2: INFRASTRUCTURE AND EQUIPMENT
                      REQUIRED
This table should show what additional/adapted infrastructure and equipment you
think will be needed to fulfil your application scenarios. This could include:

    1) Purchase of new equipment (give numbers of devices)
    2) Installation of new infrastructure
    3) Modification/adaptation of existing infrastructure/ equipment

Infrastructure (Required)                     Details
What infrastructure do you require at         [Please give details]
your pilot site to fulfil your application
scenarios?
   • Satellite based technology
            o GPS
            o Other (name)
   • Mobile technology
            o 3G
            o Other (name)
   • Wireless technology
            o RFID
            o WiFi
            o Motes
            o Smart cards
            o Other (name)

Specific Infrastructure
(Required)
What specific infrastructure do you           [Please give details]
require at your pilot site?
   • Smart house
   • Smart vehicle
   • Other (name)

Equipment (Required)
What mobile/ fixed equipment do you           [Please give details, including numbers
require at your pilot site to fulfil your     of devices]
application scenarios?
   • Mobile phones
   • Fixed PC (at home/office)
   • Tablet PCs/laptops
   • PDAs
   • Fixed info-kiosks
   • Other (name)




October 2007                                 46                                    UNEW
   ASK-IT D4.3.1                                Public                 Contract N. 5112981



   6 Annex: Helpdesk Contacts


   Server           Netsmart        Yannis                iorthop@netsmart.gr
                                    Orthopoulos
   Devices          CERTH/HIT       Kostas Kalogirou      kalogir@certh.gr
   Testing and      Comarch         Michal                Michal.Jeziorowski@comarch.pl
   debugging                        Jeziorowski
   Localisation     PTV             Markus Kauber         Markus.kauber@ptv.de
   Navigation       PTV             Markus Kauber         Markus.kauber@ptv.de
   e-Commerce       ATCRom          Corneliu Milos        corneliu.milos@atcrom.ro
   Domotics         FTB             Helmut Heck           ask-it@ftb-volmarstein.de
   In-Car           CERTH/HIT       Angelos Bekiaris      abek@certh.gr
   e-Health         UPM             Eugenio Gaeta         Eugenio.gaeta@lst.tfo.upm.es
   Word             FTB             Helmut Heck           ask-it@ftb-volmarstein.de
   Prediction
   Kiosk            Microsoft       Robert Sugar          Robert.sugar@microsoft.com
   interface
   e-Learning/      FTB             Helmut Heck           ask-it@ftb-volmarstein.de
   e-Working

   A list of partners responsible for integrating ASK-IT modules with user interfaces for
   various types of device is presented in the table below:

                      Partners       Mobile              PDA        Desktop PC        Deadline
                    Developed by   ITACA           ITACA          ITACA
Log-in, out         Supported by   NETSMART        NETSMART,      NETSMART,
                                                   CERTH/HIT      CERTH/HIT
                    Developed by   ITACA           ITACA          ITACA
Modification
user profile        Supported by   CERTH/HIT,      CERTH/HIT,     CERTH/HIT,
                                   CERTH/ITI       CERTH/ITI      CERTH/ITI
                    Developed by   CERTH/HIT       CERTH/HIT      CERTH/HIT
Domotics
                    Supported by                   UPM            UPM
                    Developed by   N/A             ATCROM         ATCROM
ePayment and
eCommerce           Supported by   N/A             CERTH/ITI,     CERTH/ITI,
                                                   FORTH          FORTH
                    Developed by   ATCROM          ATCROM         ATCROM
e-Learning
                    Supported by                   CERTH/ITI      CERTH/ITI
                    Developed by   ATCROM          ATCROM,        ATCROM
e-Working
                    Supported by                   CERTH/ITI      CERTH/ITI
Health              Developed by   ITACA           UPM            UPM
emergency           Supported by                   ITACA          ITACA
                    Developed by   CERTH/HIT,      CERTH/ITI      CERTH/ITI
User localization
                    Supported by                   PTV            PTV
Route Guidance      Developed by   N/A             COMARCH        COMARCH


   October 2007                               47                                      UNEW
   ASK-IT D4.3.1                                Public              Contract N. 5112981



                       Partners       Mobile              PDA    Desktop PC       Deadline
                     Supported by   N/A             CERTH/ITI   CERTH/ITI
                     Developed by   ITACA           FORTH       FORTH
Adaptation           Supported by   UPM,
                                    CERTH/HIT
Environmental        Developed by   UPM             UPM         UPM
Conditions           Supported by
Guidelines for all   Developed by   USTUTT          USTUTT      USTUTT
modules:             Supported by   FORTH           FORTH       FORTH
Support for
developers
                     Developed by                   FTB??       FTB
Writing support
                     Supported by                               CERTH/ITI




   October 2007                                48                                UNEW
ASK-IT D4.3.1                             Public                  Contract N. 5112981



7 References
ASK-IT D1.1.2 Use Cases (April 2006).

ASK-IT D4.1.1 ASK-IT pilot sites selection and profile (November 2006).

ASK-IT D2.2.1 Localisation Module Specification (September 2006).

ASK-IT D2.2.2_Enhanced Accuracy Localisation Module (September 2007).

ASK-IT ID2.2.1 Existing and Future Localisation Technologies for ASK-IT
(November 2005).

ASK-IT ID4.6.1 Pilot Site Integration Plans (draft) (February 2007).

ASK-IT ID3.3.4 ASK-IT Client Integration (October 2007).

ASK-IT ID2.10.1 Full Set of Interface Concepts and prototypes (Prototype and
report) (October 2007).

ASK-IT ID4.3.1 Site Infrastructure Development (February 2007).




October 2007                             49                                    UNEW

				
DOCUMENT INFO