Functional Requirements

From wiki.gpii
Jump to: navigation, search

Note: The page is part of the Matchmaking activity.

Warning: This page is outdated and is only kept here because other pages still reference it. The content of this page has been integrated into (and updated in) Cloud4all deliverable D204.1 (October 2012).


The following Table (status: ongoing) summarizes requirements for the matchmaker framework based on collected information from the matchmaker meetings, the output of the architecture group as well as research of the existing projects on personalization and matching systems (A204.1).

Number

Description

A
Matchmaker Framework

A.1.

The matchmaker framework contains a Input API for receiving input (see Input and Output).

A.2.

The matchmaker framework contains a Output API for sending output (see Input and Output).

A.3.

The matchmaker framework contains a Translation API for executing value/range transformationsof settings.

A.4.

The matchmaker framework contains a Registration API for matchmakers. 

A.5.

The matchmaker framework contains a Configuration API for common configurations issues. (i.e exiting configuration file?)

A.6.

The matchmaker framework do not contain a configuration API for matchmakers specific issues. (i.e. no rule editor)

A.7.

The matchmaker framework contains a Ontology API for retrieving semantical information (ontology, semantic framework).

A.8.

The matchmaker framework contains a Solution Registry API for retrieving solutions and settings.

A.9.
The matchmaker framework contains a Process Strategy Unit for selecting Matchmakers based on different factors (i.e. matching problem, data source, types of preferences sets, user choice, etc.)

B

Matchmakers

B.1.

Matchmakers can implement different matching techniques adressing different matching problems.

B.2.
 ??? Matchmaker can be is a cloud-based service (from the DOW) ???
B.3

Matchmakers should be general-purpose engines for finding the best solutions to a given user's needs. 

B.4

Matchmakers will be trusted. They will need to be reviewed and vetted by the community prior to be introduced into the system. 

B.5.
??? The matchmaker supports matching techniques performed by external services in case of privacy obligations. (from the DoW) ???
B.6.

Matchmakers infers from preferences to settings and vice versa.  

C

Input of the Matchmaker

C.1

The input of the matchmakers is the full preference set of a user.

C.2.

A Matchmaker will provided with information about the user`s environment (device specification, solution specification, context information).

C.3.
A matchmaker can access the preverence server in case of statistical analysis. Requirement: The matchmaker has to be entitled.

C.4

The inputs of the Matchmaker are User changed settings and confirmed settings.??? is this still the case? for which sceanios ???

C.5

The system considers that profiles could be moved. ???

D

Output of the matchmaker

D.1

The output of the Matchmaker is a set of appropriate settings that are suitable for setting handler(s).

D.2

The outputs of the Matchmaker are preferences that have been transformed from user changed settings.??? => is this still the case? for which scenario ???