wörk (fix #2)

master
Clemens Klug 2018-06-08 18:23:47 +02:00
parent 81658f579a
commit 6096d4cf7c
2 changed files with 28 additions and 38 deletions

View File

@ -17,7 +17,7 @@ To proceed in the games narrative story, the caches are to be completed.
The players have to complete a task with context of the caches' location. The players have to complete a task with context of the caches' location.
\image{.5\textwidth}{../../PresTeX/images/gg2}{Geogame map view}{img:gg2} \image{.5\textwidth}{../../PresTeX/images/gg2}{Geogame map view}{img:gg2}
\section{Research with location based games} \section{Research with location based games}\label{sec:gg-res}
Usually, when the effectiveness of location based educational games is to be measured, the following pattern is applied: Usually, when the effectiveness of location based educational games is to be measured, the following pattern is applied:
After a mission statement has been defined and approved, a fitting statistical framework has to be developed. After a mission statement has been defined and approved, a fitting statistical framework has to be developed.

View File

@ -1,46 +1,36 @@
\label{sec:scope} \label{sec:scope}
\section{Goal definition} \section{Goal definition}\label{sec:require}
A Framework for the Analysis of Spatial Game Data To provide a ground truth to findings derived from questionnaires about geogames (like described in \autoref{sec:gg-res}), a \emph{Framework for the Analysis of Spatial Game Data} is the goal of this work.
\begin{itemize} This framework shall rely on geogame log files providing both real world data (location and locomotion) and ingame data (game process, game actions).
\item Framework for analysis From these logs, the framework shall support the creation of different analysis reports.
\item Two target groups: To be a true framework, a tight coupling to any specific game is out of bounds.
\begin{itemize} For an holistic solution, the integration of external data (e.g. questionnaire results) allows the framework to compute an overall result.
\item Expert users/researchers
\item Staging/designing staff
\end{itemize}
\item Integration of external data (questionnaire results)
\item Adaptable for multiple games
\end{itemize}
\subsection{Target groups}
With researches extracting influences of games into the players' behaviour, the first target group of the analysis framework is clear.
A second user group are the game staging and game designing staff.
They require feedback about difficult sections in the game, hard to reach locations, or overcrowded situations to improve the game emjoyment of the players.
Additionally they need statistics to conclude the game session with a review of the game round.
With spatial trajectories of possibly individual players, some basic privacy protection needs to restrict the access to the log files to a minimal amount of people.
Additionally, a user interface for the creation of predefined analysis settings with custom logs provides the stagers and designers a reasonable information basis.
\section{Components} \section{Components}
Prerequisites: Game log \subsection{Prerequisites}
\begin{itemize} Out of scope for this work is the creation of the geogame logs, they are a prerequisite for the application of the framework for any (geo-)game.
\item Creation Obviously, game sessions without logs have no data basis for an evaluation left.
\item Storage Not only the creation but also the storage of the game logs is not to be considered here.
\end{itemize} As long as an interface to access the logs is provided, an access client belongs to the scope of the framework.
New components
\begin{itemize}
\item Per-game importer (Web client, File loader, …)
\item Analyzer modules (number crunching)
\item Output \& Visualization (CSV, [Geo]JSON, KML, Graphs, …)
\item Interface (Configuration)
\item Cross-game comparisons
\end{itemize}
\section{Requirements}\label{sec:require} %TODO \subsection{New components}
Wait, what did I want to do again? The framework can be defined by the follwing components:
\begin{itemize} \begin{itemize}
\item Per-game importer (Web client, File loader, …) \item Per-game importer (Web client, File loader, …) to load log files for analysis
\item Analyzer modules (number crunching) \item Analyzer modules to perform the number crunching and extraction of information
\item Output \& Visualization (CSV, [Geo]JSON, KML, Graphs, …) \item Output \& Visualization export the derived information for storage, interpretation or further analysis, e.g. into CSV, [Geo]JSON, KML, Graphs, …
\item Interface (Configuration) \item User Interface for the configuration of the analysis run and the selection of processed game logs
\begin{itemize}
\item Expert users/researchers
\item Staging/designing staff
\end{itemize}
\item Cross-game comparisons
\item Integration of external data (questionnaire results)
\end{itemize} \end{itemize}