Download as
Browse Code »

Commit e470b92518848e153ea16a6ff4221463b613ec1a

Authored by Paulo Meireles
1 parent 0fb96723
Exists in master and in 3 other branches oss_2018, oss_2018_siqueira, rework_case_study

[opensym] minor improvements

Showing 2 changed files with 17 additions and 17 deletions   Show diff stats
opensym2017/content/05-requirements.tex
  Diff comments   View file @e470b92
... ... @@ -2,22 +2,22 @@
2 2 \label{sec:requirements}
3 3  
4 4 By preparing the evolution the SPB Portal, the Brazilian Government executed
5   -three steps to collect the requirements, in particular from society point of
6   -view. The first step consisted in order to collect proposals using an online
7   -tool called Pligg \footnote{\url{https://pligg.com}} and share them openly on
8   -the Internet. The citizens were able to write proposals as well as vote on
9   -those that most interested them. At the end of this step. the Brazilian
10   -Government collected about 100 proposals and the initial perspective was to
11   -prioritize the most voted of them to be implemented for the new SPB Portal.
  5 +three steps to collect the requirements. The first step consisted in order to
  6 +collect proposals using an online tool called Pligg
  7 +\footnote{\url{https://pligg.com}} and share them openly on the Internet. The
  8 +citizens were able to write proposals as well as vote on those that most
  9 +interested them. At the end of this step, the Brazilian Government collected
  10 +about 100 proposals and the initial perspective was to prioritize the most
  11 +voted of them to be implemented for the new SPB Portal.
12 12  
13 13 The second step was two open face-to-face meetings that aimed to discuss ideas
14 14 (not necessarily based on the proposals collect during the first step) to
15 15 improve the SPB Portal and its specific environments. At the first day, the
16 16 participants were divided in two groups to discuss (i) features and
17 17 technologies as well as (ii) user experience and ideas in general regarding to
18   -SPB. Each group generated a mind map to summarize and correlated its ideas.
19   -During the second day, the participants were allocated in three groups to
20   -discuss features related to (i) the process of software evaluation and
  18 +SPB Portal. Each group generated a ``mind map'' to summarize and correlate its
  19 +ideas. During the second day, the participants were allocated in three groups
  20 +to discuss features related to (i) the process of software evaluation and
21 21 acceptance in the SPB Portal, (ii) the approaches to share the SPB projects,
22 22 and (iii) how to attract universities and students to collaborate to SPB
23 23 projects.
... ... @@ -27,10 +27,10 @@ the Government and public organizations. One more time, the objective was to
27 27 collect proposals to evolute the SPB Portal, but the discussions was not
28 28 necessarily related to the ideas provided during the first and second steps.
29 29  
30   -After these uncoated 3 steps, the Brazilian government listed 145 requirements
31   -for us. By trying to mitigate the lack of focus from the requirement list, we
32   -propose to release an initial version that would replace the old SPB portal,
33   -prioritizing the following features:
  30 +After these uncoated three steps, the Brazilian government generated a list of
  31 +145 requirements. By trying to mitigate the lack of focus from the requirement
  32 +list, we propose to release an initial version that would replace the old SPB
  33 +portal, prioritizing the following features:
34 34  
35 35 \begin{enumerate}
36 36 \item An organized public software catalog;
... ... @@ -45,7 +45,7 @@ authentication to use the provided features. Additionally, a unified interface
45 45 was an important non-functional requirement to have a better user experience in
46 46 the new platform.
47 47  
48   -Other requirements, such as an integrated search engine and a web-based source
49   -code static analysis monitor, were in the wishlist. By analyzing all of these
  48 +Other requirements were in the wishlist such as an integrated search engine and
  49 +a web-based source code static analysis monitor. By analyzing all of these
50 50 requirements, we have designed the SPB evolution project based on existing
51 51 FLOSS tools.
... ...
opensym2017/content/06-architecture.tex
  Diff comments   View file @e470b92
... ... @@ -159,7 +159,7 @@ network created between them.
159 159  
160 160 \begin{figure*}[hbt]
161 161 \centering
162   - \includegraphics[width=.8\linewidth]{figures/arch3.png}
  162 + \includegraphics[width=\linewidth]{figures/arch3.png}
163 163 \caption{Instanciation view of the SPB architecture.}
164 164 \label{fig:architecture2}
165 165 \end{figure*}
... ...