[opensym] backing the deploy section

Paulo Meireles
1 parent cda07a26
Showing 2 changed files with 28 additions and 43 deletions Show diff stats
opensym2017/content/05-requirements.tex
opensym2017/content/06-architecture.tex
 \section{Requirements}
 \label{sec:requirements}
+\begin{comment}
 In 2013, the SPB Portal had more than 600 thousand unique visitors, generating
 more than 16 million page views with about 50 million hits. By evaluating only
 the main projects, there were more than 15 thousand downloads and 4 thousand
 messages exchanged in their forums. These data illustrates the potential of the
 SPB Portal, even with several limitations in the past.
+\end{comment}
 By preparing the evolution project described in this paper, the Brazilian
 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
 government and public organizations.
 After these 3 rounds discussing the new SPB platform, the Brazilian government
-listed about 145 requirements and developed a ``mind
-map''\footnote{\url{https://softwarepublico.gov.br/social/spb/gallery/mapaconceitual.png}}
-to guide the SPB portal evolution. In this scenario, the 10 most voted
-requirements were:
+listed about 145 requirements. The 10 most voted requirements were:
+(i) Source code repository with public access;
+(ii) Visit community pages without login;
+(iii) Distributed version control system;
+(iv) Scores of users and developers collaboration;
+(v) Search software by features;
+(vi) Integration with social networks;
+(vii) Repository for future ideas and requirements;
+(viii) Friendly URL to access a public software community page;
+(ix) User feedback about a public software;
+(x) Report of the experience about the use of a public software.
-\begin{enumerate}
-
-\item Source code repository with public access;
-\item Visit community pages without login;
-\item Distributed version control system;
-\item Scores of users and developers collaboration;
-\item Search software by features;
-\item Integration with social networks;
-\item Repository for future ideas and requirements;
-\item Friendly URL to access a public software community page;
-\item User feedback about a public software;
-\item Report of the experience about the use of a public software;
-
-\end{enumerate}
-
-\begin{figure}[hbt]
-  \centering
-    \includegraphics[width=\linewidth]{figures/technological-requirements.png}
-  \caption{Technological requirements.}
-  \label{fig:requirements}
-\end{figure}
+%\begin{figure}[hbt]
+%  \centering
+%    \includegraphics[width=\linewidth]{figures/technological-requirements.png}
+%  \caption{Technological requirements.}
+%  \label{fig:requirements}
+%\end{figure}
 There were other requirements based on the experience of the IT
@@ -54,23 +48,16 @@ user experience in the new platform.
 At the first moment, we desired to release an initial version that could
 replace the old SPB portal. For that, the first version should have
 features such as:
-
-\begin{enumerate}
-
-\item An organized public software catalog;
-\item Social network environment (profiles for users, software pages, and community pages);
-\item Content Management Systems (CMS) features;
-\item Web-based Git repository manager with wiki and issue tracking features;
-\item Mailing lists and discussion forums;
-
-\end{enumerate}
+(i) An organized public software catalog;
+(ii) Social network environment (profiles for users, software pages, and community pages);
+(iii) Content Management Systems (CMS) features;
+(iv) Web-based Git repository manager with wiki and issue tracking features;
+(v) Mailing lists and discussion forums;
 Other requirements were also planned during the conception phase of the
 SPB evolution project, such as an integrated search engine and a
 web-based source code static analysis monitor. By analyzing all of these
-requirements, we proposed the technological requirements
-illustrated in Figure \ref{fig:requirements} to guide the development of
-the new SPB platform. In other words, we have designed the SPB evolution
+requirements, we have designed the SPB evolution
 project based on existing FLOSS tools. However, the integration of
 several existing systems that were already implemented in different
 programming languages and frameworks, adding features such as a
@@ -108,7 +108,7 @@ accordingly to their own context.
 \begin{figure}[hbt]
   \centering
-    \includegraphics[width=\linewidth]{figures/arch.png}
+    \includegraphics[width=.8\linewidth]{figures/arch.png}
   \caption{SPB architecture overview.}
   \label{fig:architecture}
 \end{figure}
@@ -148,8 +148,6 @@ interface had to adapt for each individual scenario. In particular
 Noosfero did not yet have a responsive design; we engaged in its
 development and contributed towards that goal.
-\begin{comment}
-%FALTA DE ESPAÇO
 \subsection{Deploy}
 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}.
 \begin{figure*}[hbt]
   \centering
-    \includegraphics[width=\linewidth]{figures/arch3.png}
+    \includegraphics[width=.8\linewidth]{figures/arch3.png}
   \caption{Instanciation view of the SPB architecture.}
   \label{fig:architecture2}
 \end{figure*}
@@ -187,4 +185,4 @@ static analysis tools on source code stored in repository and provide this data
 to Prezento. A social network and CMS (Content Manager System) is provided by
 Noosfero in \textit{social}, and the databases of all tools with a cache
 service are in \textit{database}.
-\end{comment}
+