% these lines need to be commented out in order for this file to
% compile as part of the same document as everyone else
%\documentclass[12pt]{article}
%\begin{document}
\begin{frame}[allowframebreaks]{unschool}

\begin{enumerate}

    \item \textbf{Load Test} \\
    Analyze the behaviour of server under heavy user load.
    Test environment with many concurrent users as well as projects with dependencies among large number of documents.
    \item \textbf{Unison Integration} \\
	Since Unison can be used for file synchronization, it can be used to substitute Git for file duplication and synchronization since many of the features in Git (such as branching, diff, merge, etc) are not necessary for the project.
    \item \textbf{User Study - Commit Frequency} \\
    Hypothesis: When using version control systems, users will commit less freqently if some detailed/meaningful comment must be included.
    Procedure: Two groups of people working on the same project using the same version control system, for one group, they don't have to include comments in their commits; for the other, all commits must include detailed comments. In order to elimate "coincident" factors, either both groups have to be large, or it has too be repeated for multiple times.
	\item \textbf{Adaptive Interface} \\
	The application could record and learn from user behaviour to refine its interface structure. This could be private (user-only), local (all users in the same organization) and global (all users of the application) in scale. It will also provide good insight on the common actions of users and provide tips for how the application should evolve.

	\item \textbf{Overload: Model Application State under Multiple Interaction}
	Use Alloy to model (at a high level) multiple users using your application to modify a common document under multiple scenarios to ensure that the state of both the document and the application remains consistent.
	
\end{enumerate}

\end{frame}
%\end{document}
