Download as
Browse Code »

Commit 8e6eeb06c846381e6a53ec41a7dbddd8c4a1994d

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

[opensym] backing the deploy section

Showing 2 changed files with 28 additions and 43 deletions   Show diff stats
opensym2017/content/05-requirements.tex
  Diff comments   View file @8e6eeb0
1 1 \section{Requirements}
2 2 \label{sec:requirements}
3 3  
  4 +\begin{comment}
4 5 In 2013, the SPB Portal had more than 600 thousand unique visitors, generating
5 6 more than 16 million page views with about 50 million hits. By evaluating only
6 7 the main projects, there were more than 15 thousand downloads and 4 thousand
7 8 messages exchanged in their forums. These data illustrates the potential of the
8 9 SPB Portal, even with several limitations in the past.
  10 +\end{comment}
9 11  
10 12 By preparing the evolution project described in this paper, the Brazilian
11 13 government promoted 3 events to collect the requirements, in particular from
... ... @@ -15,32 +17,24 @@ SPB concepts and requirements with IT stakeholders from the Brazilian
15 17 government and public organizations.
16 18  
17 19 After these 3 rounds discussing the new SPB platform, the Brazilian government
18   -listed about 145 requirements and developed a ``mind
19   -map''\footnote{\url{https://softwarepublico.gov.br/social/spb/gallery/mapaconceitual.png}}
20   -to guide the SPB portal evolution. In this scenario, the 10 most voted
21   -requirements were:
  20 +listed about 145 requirements. The 10 most voted requirements were:
  21 +(i) Source code repository with public access;
  22 +(ii) Visit community pages without login;
  23 +(iii) Distributed version control system;
  24 +(iv) Scores of users and developers collaboration;
  25 +(v) Search software by features;
  26 +(vi) Integration with social networks;
  27 +(vii) Repository for future ideas and requirements;
  28 +(viii) Friendly URL to access a public software community page;
  29 +(ix) User feedback about a public software;
  30 +(x) Report of the experience about the use of a public software.
22 31  
23   -\begin{enumerate}
24   -
25   -\item Source code repository with public access;
26   -\item Visit community pages without login;
27   -\item Distributed version control system;
28   -\item Scores of users and developers collaboration;
29   -\item Search software by features;
30   -\item Integration with social networks;
31   -\item Repository for future ideas and requirements;
32   -\item Friendly URL to access a public software community page;
33   -\item User feedback about a public software;
34   -\item Report of the experience about the use of a public software;
35   -
36   -\end{enumerate}
37   -
38   -\begin{figure}[hbt]
39   - \centering
40   - \includegraphics[width=\linewidth]{figures/technological-requirements.png}
41   - \caption{Technological requirements.}
42   - \label{fig:requirements}
43   -\end{figure}
  32 +%\begin{figure}[hbt]
  33 +% \centering
  34 +% \includegraphics[width=\linewidth]{figures/technological-requirements.png}
  35 +% \caption{Technological requirements.}
  36 +% \label{fig:requirements}
  37 +%\end{figure}
44 38  
45 39  
46 40 There were other requirements based on the experience of the IT
... ... @@ -54,23 +48,16 @@ user experience in the new platform.
54 48 At the first moment, we desired to release an initial version that could
55 49 replace the old SPB portal. For that, the first version should have
56 50 features such as:
57   -
58   -\begin{enumerate}
59   -
60   -\item An organized public software catalog;
61   -\item Social network environment (profiles for users, software pages, and community pages);
62   -\item Content Management Systems (CMS) features;
63   -\item Web-based Git repository manager with wiki and issue tracking features;
64   -\item Mailing lists and discussion forums;
65   -
66   -\end{enumerate}
  51 +(i) An organized public software catalog;
  52 +(ii) Social network environment (profiles for users, software pages, and community pages);
  53 +(iii) Content Management Systems (CMS) features;
  54 +(iv) Web-based Git repository manager with wiki and issue tracking features;
  55 +(v) Mailing lists and discussion forums;
67 56  
68 57 Other requirements were also planned during the conception phase of the
69 58 SPB evolution project, such as an integrated search engine and a
70 59 web-based source code static analysis monitor. By analyzing all of these
71   -requirements, we proposed the technological requirements
72   -illustrated in Figure \ref{fig:requirements} to guide the development of
73   -the new SPB platform. In other words, we have designed the SPB evolution
  60 +requirements, we have designed the SPB evolution
74 61 project based on existing FLOSS tools. However, the integration of
75 62 several existing systems that were already implemented in different
76 63 programming languages and frameworks, adding features such as a
... ...
opensym2017/content/06-architecture.tex
  Diff comments   View file @8e6eeb0
... ... @@ -108,7 +108,7 @@ accordingly to their own context.
108 108  
109 109 \begin{figure}[hbt]
110 110 \centering
111   - \includegraphics[width=\linewidth]{figures/arch.png}
  111 + \includegraphics[width=.8\linewidth]{figures/arch.png}
112 112 \caption{SPB architecture overview.}
113 113 \label{fig:architecture}
114 114 \end{figure}
... ... @@ -148,8 +148,6 @@ interface had to adapt for each individual scenario. In particular
148 148 Noosfero did not yet have a responsive design; we engaged in its
149 149 development and contributed towards that goal.
150 150  
151   -\begin{comment}
152   -%FALTA DE ESPAÇO
153 151 \subsection{Deploy}
154 152  
155 153 The SPB platform was deployed in 7 virtual machines with different functions,
... ... @@ -157,7 +155,7 @@ as we can see in Figure \ref{fig:architecture2}.
157 155  
158 156 \begin{figure*}[hbt]
159 157 \centering
160   - \includegraphics[width=\linewidth]{figures/arch3.png}
  158 + \includegraphics[width=.8\linewidth]{figures/arch3.png}
161 159 \caption{Instanciation view of the SPB architecture.}
162 160 \label{fig:architecture2}
163 161 \end{figure*}
... ... @@ -187,4 +185,4 @@ static analysis tools on source code stored in repository and provide this data
187 185 to Prezento. A social network and CMS (Content Manager System) is provided by
188 186 Noosfero in \textit{social}, and the databases of all tools with a cache
189 187 service are in \textit{database}.
190   -\end{comment}
  188 +
... ...