Changes between Version 2 and Version 3 of Usecases


Ignore:
Timestamp:
04/16/12 15:50:27 (13 years ago)
Author:
hendrikvanantwerpen
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Usecases

    v2 v3  
    11= Usecases =
    22
    3 == Surveys ==
     3== Surveys Construction ==
    44
    5 Survey is a sequence of questions, with possible images, headers
     5A question has a title, a text, some scales and some items. Scale/item pairs can be named or anonymous and indicate in inversion of the used scale.
    66
    7 == Conducting ==
     7A survey is a list of items, among which are headers, texts, images and named or anonymous questions. The same question may appear multiple times.
    88
    9  * Personalized questionnaire. A limited amount of surveys is conducted, instantiated in advance. They can have e.g. unique response URL's.
    10  * Bulk questionnaire. Multiple respondents can fill in one questionnaire.
    11 
    12  * A facilitator can add properties/answers to a survey instance. Any metadata that is relevant for later understanding of the data. E.g. Veerkracht, instantiate a bulkQ for every manager, adding him as metadata. The link for that Q can be send to his lackies.
    13  * Continuate a Q started earlier. Use cookies, generate a continuation URL that people can bookmark or something like that.
     9Questions can be selected from a pre-existing list.
    1410
    1511=== Types of questions ===
    … …  
    2218 * Fixed sum questions (divide amount n over several items)
    2319
    24  * Questions can have multiple items and multiple scales, resulting in a variable matrix (possibly and often size 1x1 though).
     20== Conducting Surveys ==
     21
     22 * Personalized questionnaire. A limited amount of surveys is conducted, instantiated in advance. They can have e.g. unique response URL's.
     23 * Bulk questionnaire. Multiple respondents can fill in one questionnaire.
     24
     25 * A survey can be conducted several times (e.g. different response groups, different year)
     26
     27 * A facilitator can add properties/answers to a survey instance. Any metadata that is relevant for later understanding of the data. E.g. Veerkracht, instantiate a bulkQ for every manager, adding him as metadata. The link for that Q can be send to his lackies.
     28 * Continuate a Q started earlier. Use cookies, generate a continuation URL that people can bookmark or something like that.
     29
     30== Reporting and data export ==
     31
     32Data can be reported or exported for use in a statistics program. Anonymous variables will get random names. Together with an export some description is generated, indicating the questions and the codification of the answers.
     33
     34It should be possible to select a 2D range and show it in a table, or a 1D range and show it in graph. The type of scale can guide the user in available operations on the data.
    2535
    2636== Data unification ==
    2737
    2838An important goal is that survey data and game data are expressed in the same way, so their data series can be used together in statistics and reports. For RDF the Data Cube vocabulary seems fit for that. The system should be able to adapt for different structured game data, unknown in advance.
     39
     40== Data stores ==
     41
     42Data is sometimes collected on tablets, offline sessions etc. Data can be easily merged into the general data store after a session or even during a session?