Moving to UX section

Paulo Meireles
1 parent 70ac3cc8
Showing 3 changed files with 47 additions and 42 deletions Show diff stats
OSS-2017/03-architecture.tex
OSS-2017/03-ux.tex
OSS-2017/spb.tex
@@ -1,39 +0,0 @@
-\section{Architecture}
-
-%TODO: Kanashiro
-
-The SPB platform was deployed in 7 virtual machines with different functions,
-as we can see in Figure \ref{fig:architecture}.
-
-\begin{figure}[hbt]
-  \centering
-    \includegraphics[width=\textwidth]{figures/arquitetura.png}
-  \caption{SPB Architecture.}
-  \label{fig:architecture}
-\end{figure}
-
-The \textit{reverseproxy} handles the HTTP requests and redirects them to the
-\textit{integration}, the \textit{email} sends and receives e-mails on behalf
-of the platform and the \textit{monitor} keeps the entire environment tracked.
-These three \textit{VMs} mentioned - \textit{reverseproxy}, \textit{email} and
-\textit{monitor} - are accessible via Internet and the other ones are only
-available in the local network created between them.
-
-\textit{Integration} works as a second layer of proxy beneath
-\textit{reverseproxy}, any request to the platform will be handled by it. The
-Colab service provides interface, authentication and search engine integration
-among all the services. When a request is received to a specific service,
-Colab authenticates the user in the target tool, sends the request and makes a
-visual transformation in the HTML page, which is the content of the response.
-Another user-oriented feature is the integrated search engine, when the user
-want to find something in the platform Colab will perform the search in the
-whole databases. Colab itself provides a web interface for GNU Mailman and we
-have two others integrated tools in \textit{integration}: Gitlab and Prezento.
-Gitlab provides web interface for Git repositories and issues tracker, and
-Prezento is a front-end for source code static analysis.
-
-The source code static analysis is performed by \textit{mezuro}. It runs some
-static analysis tools on source code stored in repository and provides this data
-to Prezento. A social network and CMS (Content Management System) is provided by
-Noosfero in \textit{social}, and the databases of all tools with a cache
-service are in \textit{database}.
@@ -0,0 +1,44 @@
+\section{User Experience evolution}
+
+The integration of collaborative environments goes beyond functional aspects.
+Offering the population an unified experience across these environments has
+been the key to encourage the use of the platform as it reduces the perception
+of the complexity.
+
+Thus, the portal information architecture was redesigned to provide a
+transparent navigation and to reach users with different profiles.  A process
+of harmonization has been employed on the interaction models of each tool in
+order to reduce the learning curve.  At the same time, a new visual style was
+created to unify the navigation experience and to comply with the guidelines of
+the digital communication identity pattern established by the Federal
+Government.
+
+With the increase of the system features and the addition of new tools, the
+visual style has steadily evolved in order to keep the navigation unified.
+Moreover, tools from different backgrounds, which in many cases run
+functionalities with similar concepts, made us face the challenge of developing
+a transparent interface that unifies various context.  For each required
+feature, we often have to conciliate data with distinct structure and
+information pattern from each used tool. The interface was the meeting point
+for this data with links that users will not notice.  The most common features
+(i.e. search, display and edition of profile information and content) have been
+brought in line with the structure and other existing features of the portal.
+
+The other challenge is related to responsive web design.  The portal interface
+and each of its pages were designed following the bounds of responsiveness
+provided or supported by each tools.  In particular, in the case of Noosfero,
+which do not have any official branch dedicated to improve its responsiveness,
+our project needed to engage with the expansion of this platform, where we made
+a lot of contributions and dialogues with the community and maintainers.  All
+the project members got involved in the study, design and development of the
+Noosfero's new interface which support a responsive web design and that have
+not yet been completed.
+
+Users are part of the process.  In 2014, a survey among users of the existing
+platform was conducted to identify usability problems and to measure their
+satisfaction with the system.  After the release of the new SPB platform,
+several validations activities were implemented in 2015 and 2016, and the data
+collected during this phase helped to channel our efforts to identify and to
+improve the main fields of the new system.  The aim was to bring the users
+closer to features that they have more interest and designing a navigation
+which deepens in accordance with the user's depth of knowledge.
@@ -40,10 +40,10 @@
 \input{00-abstract}
 \input{01-introduction}
 \input{02-platform}
-\input{03-architecture}
+\input{03-ux}
 \input{04-finals}
 %------------------------------------------------------------------------------
-\bibliographystyle{splncs03}
-\bibliography{spb}
+%\bibliographystyle{splncs03}
+%\bibliography{spb}
 \end{document}
	@@ -1,39 +0,0 @@	@@ -1,39 +0,0 @@
1	-\section{Architecture}
2	-
3	-%TODO: Kanashiro
4	-
5	-The SPB platform was deployed in 7 virtual machines with different functions,
6	-as we can see in Figure \ref{fig:architecture}.
7	-
8	-\begin{figure}[hbt]
9	- \centering
10	- \includegraphics[width=\textwidth]{figures/arquitetura.png}
11	- \caption{SPB Architecture.}
12	- \label{fig:architecture}
13	-\end{figure}
14	-
15	-The \textit{reverseproxy} handles the HTTP requests and redirects them to the
16	-\textit{integration}, the \textit{email} sends and receives e-mails on behalf
17	-of the platform and the \textit{monitor} keeps the entire environment tracked.
18	-These three \textit{VMs} mentioned - \textit{reverseproxy}, \textit{email} and
19	-\textit{monitor} - are accessible via Internet and the other ones are only
20	-available in the local network created between them.
21	-
22	-\textit{Integration} works as a second layer of proxy beneath
23	-\textit{reverseproxy}, any request to the platform will be handled by it. The
24	-Colab service provides interface, authentication and search engine integration
25	-among all the services. When a request is received to a specific service,
26	-Colab authenticates the user in the target tool, sends the request and makes a
27	-visual transformation in the HTML page, which is the content of the response.
28	-Another user-oriented feature is the integrated search engine, when the user
29	-want to find something in the platform Colab will perform the search in the
30	-whole databases. Colab itself provides a web interface for GNU Mailman and we
31	-have two others integrated tools in \textit{integration}: Gitlab and Prezento.
32	-Gitlab provides web interface for Git repositories and issues tracker, and
33	-Prezento is a front-end for source code static analysis.
34	-
35	-The source code static analysis is performed by \textit{mezuro}. It runs some
36	-static analysis tools on source code stored in repository and provides this data
37	-to Prezento. A social network and CMS (Content Management System) is provided by
38	-Noosfero in \textit{social}, and the databases of all tools with a cache
39	-service are in \textit{database}.
@@ -0,0 +1,44 @@		@@ -0,0 +1,44 @@
	1	+\section{User Experience evolution}
	2	+
	3	+The integration of collaborative environments goes beyond functional aspects.
	4	+Offering the population an unified experience across these environments has
	5	+been the key to encourage the use of the platform as it reduces the perception
	6	+of the complexity.
	7	+
	8	+Thus, the portal information architecture was redesigned to provide a
	9	+transparent navigation and to reach users with different profiles. A process
	10	+of harmonization has been employed on the interaction models of each tool in
	11	+order to reduce the learning curve. At the same time, a new visual style was
	12	+created to unify the navigation experience and to comply with the guidelines of
	13	+the digital communication identity pattern established by the Federal
	14	+Government.
	15	+
	16	+With the increase of the system features and the addition of new tools, the
	17	+visual style has steadily evolved in order to keep the navigation unified.
	18	+Moreover, tools from different backgrounds, which in many cases run
	19	+functionalities with similar concepts, made us face the challenge of developing
	20	+a transparent interface that unifies various context. For each required
	21	+feature, we often have to conciliate data with distinct structure and
	22	+information pattern from each used tool. The interface was the meeting point
	23	+for this data with links that users will not notice. The most common features
	24	+(i.e. search, display and edition of profile information and content) have been
	25	+brought in line with the structure and other existing features of the portal.
	26	+
	27	+The other challenge is related to responsive web design. The portal interface
	28	+and each of its pages were designed following the bounds of responsiveness
	29	+provided or supported by each tools. In particular, in the case of Noosfero,
	30	+which do not have any official branch dedicated to improve its responsiveness,
	31	+our project needed to engage with the expansion of this platform, where we made
	32	+a lot of contributions and dialogues with the community and maintainers. All
	33	+the project members got involved in the study, design and development of the
	34	+Noosfero's new interface which support a responsive web design and that have
	35	+not yet been completed.
	36	+
	37	+Users are part of the process. In 2014, a survey among users of the existing
	38	+platform was conducted to identify usability problems and to measure their
	39	+satisfaction with the system. After the release of the new SPB platform,
	40	+several validations activities were implemented in 2015 and 2016, and the data
	41	+collected during this phase helped to channel our efforts to identify and to
	42	+improve the main fields of the new system. The aim was to bring the users
	43	+closer to features that they have more interest and designing a navigation
	44	+which deepens in accordance with the user's depth of knowledge.