Software Público Brasileiro

\section{Conclusion}
\label{sec:conclusion}

In this paper we present and discuss issues experienced during a government-
funded project, in partnership with University of Brasilia and University of
São Paulo, to evolve the Brazilian Public Software portal. 

The contributions of this paper are twofold. First, we present how an unprecedent
platform was developed and delivered to Brazilian government. This 
platform - developed by an heterogenous team of professors, masters and 
undergraduate  students, IT professionals and governmental managers - provides 
several modern features from the integration of more than 10 FLOSS systems.

Second, the thirty-month long project in which the SPB platform was developed points
out that it is possible to mitigate issues seen as conflicting to the IT
development environment and between industry and academy. The team was engaged in
providing a friendly working environment as well as in showing to governmental agents
another way to interact with the FLOSS community and the university. In the paper,
we try to show that, as long as the institution can provide a healthy and challenging
environment to its students, one may conciliate studies and professional training
in universities. After the end of the project, some students successfully
embraced opportunities in public and private sectos, within national borders
and abroad. Some others went further and started their own companies.
We also demonstrate that, with some adaptations/"translation processes", it is feasible
to conciliate agile methodologies and FOSS practices in order to develop software to 
governmental organizations with functional hierarchical structures that use 
traditional development paradigm.

Future work should use the many data produced by the project to validate and evaluate
how the used FLOSS and Agile practices have impacted the students and also the
governmental development process. For this, we would conduce a \textit{post-mortem}
analyse using the project open data and a survey targeted the involved actors.


The portal is available at \url{softwarepublico.gov.br}. All
documentation, including detailed architecture and operation manuals are
also available\footnote{\url{https://softwarepublico.gov.br/doc/}
(in Portuguese only at the moment)}).
%
All the integrated tools are FOSS and our contributions were published
in open repositories, available on the SPB Portal itself. We also
contributed these features back to the respective communities: that
benefits those communities, as well as us since we can share future
development and maintenance effort with other organizations that
participate in their projects.

%===========
% Conclusion
%===========

% * Gestão dos recursos: Fizemos mais por menos (2.6M de 3.2M) --- sem os dados
%% (escopo, custo, tempo e qualidade) bem discutidos é difícil sustentar essa
%% afirmação, embora eu e Paulo consigamos perceber isso.


%* utilização do projeto para formação de recursos humanos (alunos)

%* dados da verificação dos repositório para a análise da qualidade dos código via Mezuro e CodeClimate

%* o que achamos que irá acontecer com o SPB no futuro breve (acabar)

%* 69 projetos marcados como SPB, de 81 no total na plataforma.

%* 47\% é desenvolvido em PHP.

% foi constatado que aproximadamente 75\% dos softwares \textbf{não} possuem seus códigos-fonte versionados nesta ferramenta. Realizado algumas pesquisas, foi encontrado o código-fonte em outros serviços (Github, Bitbucket).

% Foram adicionados 31 softwares do SPB em ambas as ferramentas (Mezuro e Code Climate), desenvolvidos em PHP e Python. Estas adições resultaram na análise descrita nos próximos parágrafos. No Mezuro, dos 31 softwares adicionados, somente 4 obtiveram sucesso na avaliação. No Code Climate, 16 softwares realizaram a \textit{build} da avaliação com sucesso. Nos que falharam, alguns dos erros foram encontrados em três das \textit{engines}: ora em \textit{duplication}, ora na \textit{phpmd}, ora na \textit{eslint}.

% também foram inseridos no Mezuro para avaliação, 5 projetos dos 17 desenvolvidos em Java, com o intuito de ser um contraponto ao Code Climatepor esta não compreender a análise de projetos em Java, C, ou C++. Infelizmente nenhuma das \textit{builds} resultou em resultados concretos.

%* Debater economia de recursos em orgão públicos