Once the web site has been retrieved, the following window will appear (Figure 104). The user interface is web-based. Through direct links and HTML forms, the user is able to: i) retrieve data from the database and view them in a web browser via the search button and ii) login to the restricted area of the web site and have direct access to his/her entries. The introductory page can be seen below:
Figure 104: Login page of the OASIS Database web site.
Using the provided username and password, each user is able to enter to the restricted area of the web site. The figure below shows the functionality of the main page.
Figure 105: Main Page functionality.
At this stage, the user is ready to add a new entry, modify an existing one or delete an entry that is not useful any more. Depending on the entry’s category, the user should choose between the product, service and research project functionality.
As it has been mentioned before, the General Questions form appears each time the user selects to add an entry. The General Questions form is identical for each of the three entry choices. Figure 106 shows the above mentioned form.
A confirmation page appears on the screen (Figure 107) each time the user adds successfully data in the General Questions table of the database. The message reminds the user that he/she has only finished the first part of the data addition and that he/she should continue.
Figure 106: Adding a new entry – General Questions form.
Figure 107: General Question confirmation of correct data insertion.
Figure 108: Products form.
The figure above shows the Products form which follows the General Questions confirmation page (Figure 107). In this form, the user should analytically describe the entity that he/she wants to add in the OASIS database.
Once again, the site is able to inform the user for the correct addition of the data in the database (Figure 109).
Figure 109: Product, Service, Research Project confirmation of correct data insertion.
The user is not only able to add new entities in the database but also to make changes on them (Figure 105– Edit button) and delete them (Figure 105– Delete button). Figure 8 shows the form that enables the user to make changes to his/her existing entries. The user should select the entry that he/she would like to modify using the ID number of the entry.
Figure 110: Selecting the entity which needs modification.
After the selection of the ID, the web site takes the user to the appropriate form where the fields are already filled with the corresponding values (Figure 111). The user is able to make any required changes and then update the database.
Figure 111: Making the actual changed.
At the end of each Update, the web site informs the user for the correct insertion of the data in the database. Figure 112 shows the confirmation page of the successful modification of data.
Figure 112: Confirmation of successful data modification.
The last functionality of the restricted area is the one that enables the user to delete existing entries from the database. On the same way as before, the users should select from the list of his/her entries which one he/she wishes to erase. The ID number should be used once more for identification of the entry that will be erased.
Figure 113: Selecting the entity which will be deleted.
By pressing the Delete button, the web site tries to delete this entry. If this action completed properly, the web site informs the user for the successful deletion of the entry (Figure 12).
Figure 114: Confirmation of successful data deletion.
Except of the restricted area where a registered user is able to add, edit and delete entries, there is another area which has open access to every visitor of the web site. This is the Search area which provides the visitor with a number of searching functions. Depending on the criteria that the visitor would like to use on his/her database search, he/she should be use the corresponding function of the page. This page can be seen below in Figure 115.
The searching criteria of the OASIS database are:
-
Search using a Keyword
-
Search using the Name of the product/service/research project
-
Search using the Name of the manufacturer
-
Search using the End-user category from a drop down menu
-
Search using the Type of aging-related problems that are covered
-
View all entries
-
View all entries which do have a registered ontology.
Figure 115: Search functionality of OASIS Database web site.
-
Title
|
| -
Context of use (aim)
|
| -
Primary actor
|
Young elderly (ages 55-65)
Elderly (ages 65-75)
Old elderly (ages 75+)
| -
Secondary actor(s)
|
Family members
Informal care-givers (i.e. volunteers, neighbours, etc.)
Formal care-givers (both inpatient and outpatient)
Public / private Social security service providers and insurance companies
Service Centre
Health care and emergency support service providers
Home automation service providers
Leisure and re-creation service providers
Infotainment service providers
Telematic service providers
Elderly associations
National, local and regional authorities
Policy makers
Other: …………………………………………………………….
| -
Connected UCs
|
| -
Priority Level
|
Essential Secondary Supportive
| -
Scenario(s)
|
| -
System output
|
| -
Relevant OASIS WP
|
| -
Services involved
|
Transport information
Route guidance
Driver telematic support
Driver comfort support
Tourism support
Leisure and social activities support
Smart workplaces
| -
Devices & restrictions
|
< the devices that are needed for the specific UC, e.g. PDA, mobile phone, …as well as possible limitations>
11a. User Interaction devices & restrictions
|
|
11b. Sensor devices & restrictions
|
|
| -
Critical success parameters
|
Services
|
Success parameters
|
Transport information
|
|
Route guidance
|
|
Driver telematic support
|
|
Driver comfort support
|
|
Tourism support
|
|
Leisure and social activities support
|
|
Smart workplaces
|
|
| -
Environmental restrictions
|
| -
Interaction level
|
Step 2 – the system …>
| -
Personalisation/ adaptation level
|
Yes:
static parameters: …………….….
semi-dynamic parameters: …………………..
dynamic parameters: …………………..
environmental parameters/context of use4: ……………………
No
| -
Quality of service indicators
|
| -
Potential input needed from other UCs (what input and which UCs?)
|
| -
Important accessibility attributes (per UG)
|
| -
Background info/ reason on selection and on assigning the priority level
|
| -
References
|
| -
Comments
|
|
Share with your friends: |