37 lines
2.5 KiB
TeX
37 lines
2.5 KiB
TeX
\label{sec:scope}
|
|
\section{Goal definition}\label{sec:require}
|
|
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.
|
|
This framework shall rely on geogame log files providing both real world data (location and locomotion) and ingame data (game process, game actions).
|
|
From these logs, the framework shall support the creation of different analysis reports.
|
|
To be a true framework, a tight coupling to any specific game is out of bounds.
|
|
For an holistic solution, the integration of external data (e.g. questionnaire results) allows the framework to compute an overall result.
|
|
|
|
\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}
|
|
\subsection{Prerequisites}
|
|
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.
|
|
Obviously, game sessions without logs have no data basis for an evaluation left.
|
|
Not only the creation but also the storage of the game logs is not to be considered here.
|
|
As long as an interface to access the logs is provided, an access client belongs to the scope of the framework.
|
|
|
|
\subsection{New components}
|
|
The framework can be defined by the follwing components:
|
|
\begin{itemize}
|
|
\item Per-game importer (Web client, File loader, …) to load log files for analysis
|
|
\item Analyzer modules to perform the number crunching and extraction of information
|
|
\item Output \& Visualization export the derived information for storage, interpretation or further analysis, e.g. into CSV, [Geo]JSON, KML, Graphs, …
|
|
\item User Interface for the configuration of the analysis run and the selection of processed game logs
|
|
\end{itemize}
|
|
|
|
|
|
|
|
|