Merge branch 'master' of https://github.com/MusesProject/Muses-Developer-Guide

Author: unintendedbear

MUSESDevGuide.tex

@@ -27,12 +27,12 @@ \chapter{Introduction}
 
 This guide describes everything a developer needs to know to start developing for the MUSES system.
 
-The MUSES System \cite{deliverable21} has been developed following a client-server architecture.
+The MUSES System \cite{deliverable21} has been developed based on the client-server architecture. 
 
-The client or device side is related to the end user, usually an employee who uses a mobile or portable, and possibly
-personal, device to access enterprise resources. From the enterprise security point of view, the system should prevent the user from using the device incorrectly. Therefore, MUSES monitors the user's context and behaviour, and controls their actions, allowing or forbidding them depending on those policies.
+The client or device is related to the end user, usually an employee who uses a mobile or a portable device possibly
+personal device to access enterprise resources. From the enterprise security point of view, the system should prevent the user from using the device incorrectly and make sure that the employee follows the company policees. Therefore, MUSES monitors the user's context and behaviour, and controls their actions, allowing or forbidding them depending on company policies.
 
-The MUSES server side is controlled by an enterprise security manager, the Chief Security Officer (CSO), who defines the security policies to be considered in the system. The security policies are used by the MUSES server to identify which behaviour is allowed and which one is not. The server then receives, stores, and processes all the gathered information from users' devices. After that, it analyses the data, performing a real-time risk and trust analysis. In addition, the system detects policy violations through event correlation techniques, adapting to changes in the environment, as well as non-secure user behaviours.
+The MUSES server is controlled by an enterprise security manager, the Chief Security Officer (CSO), who defines the security policies to be considered in the MUSES system. The security policies are used by the MUSES server to identify which behaviour is allowed and which one is not. The server then receives, stores, and processes all the gathered information from users' devices. After that, it analyzes the data, performing a real-time risk and trust analysis. In addition, the system detects policy violations through event correlation techniques, adapting to changes in the environment, as well as non-secure user behaviours.
 
 \section{MUSES on Github}
 \label{sec:musesgit}
@@ -42,7 +42,7 @@ \section{MUSES on Github}
 \begin{description}
   \item[Muses-Developer-Guide] Repository with the TeX files which consist of a manual for users that may want to develop for the MUSES project.
   \item[Muses-Security-Quiz]
-  \item[MusesCommon] 
+  \item[MusesCommon] This repository contain the java classes common in client and server projects to reduce duplication of classes in projects.
   \item[MusesServer] This repository contains all the files in the Java-Maven MUSES server project.
   \item[MusesClient] Repository containing the first prototype of the MUSES client, developed for Android.
   \item[MusesSituationPredictionStudy]