Download as
Browse Code »

Commit 7552421d1776570ea5a801b98fe8e4628ed269a1

Authored by Leonardo Leite
1 parent 7ffe5a2d
Exists in master and in 3 other branches oss_2018, oss_2018_siqueira, rework_case_study

revisando conclusão

Showing 2 changed files with 34 additions and 23 deletions   Show diff stats
opensym2017/content/12-conclusion.tex
  Diff comments   View file @7552421
1 1 \section{Conclusion}
2 2 \label{sec:conclusion}
3 3  
4   -In this paper we present and discuss issues experienced during a government-
5   -funded project, in partnership with University of Brasilia and University of
6   -São Paulo, to evolve the Brazilian Public Software portal.
7   -
8   -The contributions of this paper are twofold. First, we present how an unprecedent
9   -platform was developed and delivered to Brazilian government. This
10   -platform - developed by an heterogenous team of professors, masters and
11   -undergraduate students, IT professionals and governmental managers - provides
12   -several modern features from the integration of more than 10 FLOSS systems.
13   -
14   -Second, the thirty-month long project in which the SPB platform was developed points
15   -out that it is possible to mitigate issues seen as conflicting to the IT
16   -development environment and between industry and academy. The team was engaged in
  4 +In this paper we presented and discussed issues experienced during a government-funded
  5 +project, in partnership with the University of Brasilia and the University of
  6 +São Paulo, to evolve the Brazilian Public Software Portal.
  7 +
  8 +The contributions of this paper are twofold. First, we presented how an unprecedented
  9 +platform was developed and delivered to the Brazilian government. This
  10 +platform - developed by a heterogeneous team of professors, masters and
  11 +undergraduate students, IT professionals, and governmental managers - provides
  12 +several modern features for the integration of more than 10 FLOSS systems.
  13 +
  14 +Second, the experience in the SPB Portal project pointed
  15 +out that it is possible to mitigate conflicts in the development environment
  16 +and to conciliate governmental and academy cultures. The team was engaged in
17 17 providing a friendly working environment as well as in showing to governmental agents
18 18 another way to interact with the FLOSS community and the university. In the paper,
19   -we try to show that, as long as the institution can provide a healthy and challenging
  19 +we tried to show that, as long as the institution can provide a healthy and challenging
20 20 environment to its students, one may conciliate studies and professional training
21 21 in universities. After the end of the project, some students successfully
22   -embraced opportunities in public and private sectos, within national borders
23   -and abroad. Some others went further and started their own companies.
  22 +embraced opportunities in public and private sectors, within national borders
  23 +and abroad. Some other students went further and started their own companies.
24 24 We also demonstrate that, with some adaptations/"translation processes", it is feasible
25 25 to conciliate agile methodologies and FOSS practices in order to develop software to
26 26 governmental organizations with functional hierarchical structures that use
27 27 traditional development paradigm.
28 28  
29   -Future work should use the many data produced by the project to validate and evaluate
  29 +\leo{Padronziar uso FOSS vs FLOSS. Qual vcs preferem?}
  30 +
  31 +Future work should use data produced by the project to validate and evaluate
30 32 how the used FLOSS and Agile practices have impacted the students and also the
31   -governmental development process. For this, we would conduce a \textit{post-mortem}
32   -analyse using the project open data and a survey targeted the involved actors.
  33 +governmental development process. For this, we would conduce a \textit{postmortem}
  34 +analysis using the project open data and a survey targeting the involved actors.
33 35  
34 36  
35 37 The portal is available at \url{softwarepublico.gov.br}. All
36 38 documentation, including detailed architecture and operation manuals are
37 39 also available\footnote{\url{https://softwarepublico.gov.br/doc/}
38   -(in Portuguese only at the moment)}).
  40 +(in Portuguese only at the moment)}.
39 41 %
40 42 All the integrated tools are FOSS and our contributions were published
41 43 in open repositories, available on the SPB Portal itself. We also
42   -contributed these features back to the respective communities: that
43   -benefits those communities, as well as us since we can share future
  44 +contributed these features back to the respective communities, which
  45 +benefits both those communities and us, since we can share future
44 46 development and maintenance effort with other organizations that
45   -participate in their projects.
  47 +participate in these projects.
46 48  
47 49 %===========
48 50 % Conclusion
... ...
opensym2017/spb.tex
  Diff comments   View file @7552421
... ... @@ -72,6 +72,13 @@
72 72 % by using the "\todo{...}" command. Make sure to disable the draft
73 73 % option again before submitting your final document.
74 74 \usepackage{todonotes}
  75 +\newcommand{\leo}[2][]{\todo[inline,color=yellow!70, #1]{\emph{Léo:} #2}}
  76 +\newcommand{\paulo}[2][]{\todo[inline,color=yellow!70, #1]{\emph{Paulo:} #2}}
  77 +\newcommand{\melissa}[2][]{\todo[inline,color=yellow!70, #1]{\emph{Melissa:} #2}}
  78 +\newcommand{\terceiro}[2][]{\todo[inline,color=yellow!70, #1]{\emph{Terceiro:} #2}}
  79 +\newcommand{\siqueira}[2][]{\todo[inline,color=yellow!70, #1]{\emph{Siqueira:} #2}}
  80 +\newcommand{\lucas}[2][]{\todo[inline,color=yellow!70, #1]{\emph{Lucas:} #2}}
  81 +\newcommand{\hilmer}[2][]{\todo[inline,color=yellow!70, #1]{\emph{Hilmer:} #2}}
75 82  
76 83 % Paper metadata (use plain text, for PDF inclusion and later
77 84 % re-using, if desired). Use \emtpyauthor when submitting for review
... ... @@ -164,6 +171,8 @@
164 171 }
165 172 }
166 173  
  174 +
  175 +
167 176 \maketitle
168 177 %------------------------------------------------------------------------------
169 178 \input{content/00-abstract}
... ...