From e470b92518848e153ea16a6ff4221463b613ec1a Mon Sep 17 00:00:00 2001 From: Paulo Meirelles Date: Tue, 25 Jul 2017 16:16:49 -0300 Subject: [PATCH] [opensym] minor improvements --- opensym2017/content/05-requirements.tex | 32 ++++++++++++++++---------------- opensym2017/content/06-architecture.tex | 2 +- 2 files changed, 17 insertions(+), 17 deletions(-) diff --git a/opensym2017/content/05-requirements.tex b/opensym2017/content/05-requirements.tex index 9faa509..330d682 100644 --- a/opensym2017/content/05-requirements.tex +++ b/opensym2017/content/05-requirements.tex @@ -2,22 +2,22 @@ \label{sec:requirements} By preparing the evolution the SPB Portal, the Brazilian Government executed -three steps to collect the requirements, in particular from society point of -view. The first step consisted in order to collect proposals using an online -tool called Pligg \footnote{\url{https://pligg.com}} and share them openly on -the Internet. The citizens were able to write proposals as well as vote on -those that most interested them. At the end of this step. the Brazilian -Government collected about 100 proposals and the initial perspective was to -prioritize the most voted of them to be implemented for the new SPB Portal. +three steps to collect the requirements. The first step consisted in order to +collect proposals using an online tool called Pligg +\footnote{\url{https://pligg.com}} and share them openly on the Internet. The +citizens were able to write proposals as well as vote on those that most +interested them. At the end of this step, the Brazilian Government collected +about 100 proposals and the initial perspective was to prioritize the most +voted of them to be implemented for the new SPB Portal. The second step was two open face-to-face meetings that aimed to discuss ideas (not necessarily based on the proposals collect during the first step) to improve the SPB Portal and its specific environments. At the first day, the participants were divided in two groups to discuss (i) features and technologies as well as (ii) user experience and ideas in general regarding to -SPB. Each group generated a mind map to summarize and correlated its ideas. -During the second day, the participants were allocated in three groups to -discuss features related to (i) the process of software evaluation and +SPB Portal. Each group generated a ``mind map'' to summarize and correlate its +ideas. During the second day, the participants were allocated in three groups +to discuss features related to (i) the process of software evaluation and acceptance in the SPB Portal, (ii) the approaches to share the SPB projects, and (iii) how to attract universities and students to collaborate to SPB projects. @@ -27,10 +27,10 @@ the Government and public organizations. One more time, the objective was to collect proposals to evolute the SPB Portal, but the discussions was not necessarily related to the ideas provided during the first and second steps. -After these uncoated 3 steps, the Brazilian government listed 145 requirements -for us. By trying to mitigate the lack of focus from the requirement list, we -propose to release an initial version that would replace the old SPB portal, -prioritizing the following features: +After these uncoated three steps, the Brazilian government generated a list of +145 requirements. By trying to mitigate the lack of focus from the requirement +list, we propose to release an initial version that would replace the old SPB +portal, prioritizing the following features: \begin{enumerate} \item An organized public software catalog; @@ -45,7 +45,7 @@ authentication to use the provided features. Additionally, a unified interface was an important non-functional requirement to have a better user experience in the new platform. -Other requirements, such as an integrated search engine and a web-based source -code static analysis monitor, were in the wishlist. By analyzing all of these +Other requirements were in the wishlist such as an integrated search engine and +a web-based source code static analysis monitor. By analyzing all of these requirements, we have designed the SPB evolution project based on existing FLOSS tools. diff --git a/opensym2017/content/06-architecture.tex b/opensym2017/content/06-architecture.tex index 2b50044..a9c121e 100644 --- a/opensym2017/content/06-architecture.tex +++ b/opensym2017/content/06-architecture.tex @@ -159,7 +159,7 @@ network created between them. \begin{figure*}[hbt] \centering - \includegraphics[width=.8\linewidth]{figures/arch3.png} + \includegraphics[width=\linewidth]{figures/arch3.png} \caption{Instanciation view of the SPB architecture.} \label{fig:architecture2} \end{figure*} -- libgit2 0.21.2