Skip to content

Commit 5ebed95

Browse files
Added requirements for installing Android ADT
1 parent f8c570a commit 5ebed95

File tree

2 files changed

+15
-2
lines changed

2 files changed

+15
-2
lines changed

MUSESDevGuide.bib

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,3 +7,10 @@ @article{deliverable61
77
title={D6.1 Conceptual Model of User Observation, Application Monitoring Tools, and Context Actuators},
88
author={Zardosht Hodaie, Natalia Mannov, Sergio Zamarripa, Yung Shin Van Der Sype, Markus Burvall, Walid Maalej}
99
}
10+
11+
@misc{adt:site,
12+
author = {Google Inc.},
13+
title = {Installing the Eclipse Plugin},
14+
url = {http://developer.android.com/sdk/installing/installing-adt.html},
15+
lastaccess = {March, 2015}
16+
}

MUSESDevGuide.tex

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ \chapter{Introduction}
3333

3434
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.
3535

36-
This guide is structured as follows. First, Chapters \label{ch:client} and \ref{ch:server} detail how to build MUSES, in order to be able to star developing and testing the system, either you want to develop for the client (Chapter \ref{ch:client}), the server (Chapter \ref{ch:server}), or both. Then, Chapter \ref{ch:sensors} specifies how to integrate new sensors to the MUSES client, for better monitoring user's actions and making the \textit{context\footnote{Any information that can be used to characterize the situation of the user.\cite{deliverable61}} observation} more complete. Finally, Chapter \ref{ch:installmuses} enumerates the steps to install MUSES in a real company environment.
36+
This guide is structured as follows. First, Chapters \ref{ch:client} and \ref{ch:server} detail how to build MUSES, in order to be able to star developing and testing the system, either you want to develop for the client (Chapter \ref{ch:client}), the server (Chapter \ref{ch:server}), or both. Then, Chapter \ref{ch:sensors} specifies how to integrate new sensors to the MUSES client, for better monitoring user's actions and making the \textit{context\footnote{Any information that can be used to characterize the situation of the user.\cite{deliverable61}} observation} more complete. Finally, Chapter \ref{ch:installmuses} enumerates the steps to install MUSES in a real company environment.
3737

3838
\chapter{Building MUSES Client}
3939
\label{ch:client}
@@ -42,7 +42,13 @@ \chapter{Building MUSES Client}
4242

4343
\section{Installing Android SDK}
4444

45-
As we will use Eclipse for MUSES development, the first step is to install the Android Development Tools (ADT) plugin.
45+
As we will use Eclipse for MUSES development, the first step is to install the Android Development Tools (ADT) plugin. The requiremenst are \cite{adt:site}:
46+
47+
\begin{itemize}
48+
\item Eclipse 3.7.2 (Indigo) or greater.
49+
\item Java Platform (JDK) 6.
50+
\item Eclipse Java Development Tools (JDT) plugin. This can be done in Eclipse by selecting \textit{Help > Install New Software...} and then looking at this reposiroty \url{https://dl-ssl.google.com/android/eclipse/}. After that, selecting \textit{Developer Tools} for installing it (by clicking \textit{Next} and \textit{Finish}), and then restart Eclipse.
51+
\end{itemize}
4652

4753
\chapter{Building MUSES Server}
4854
\label{ch:server}

0 commit comments

Comments
 (0)