revisando a introdução

Leonardo Leite
1 parent 072a0f0d
Showing 1 changed file with 58 additions and 56 deletions Show diff stats
opensym2017/content/01-introduction.tex
@@ -2,49 +2,50 @@
 \label{sec:intro}
 The Brazilian Federal Government has been 
-improving its software adoption and development processes. For
+improving its processes for software contracting and development. For
 instance, in 2003, the recommendation to adopt Free/Libre/Open Source
-Software (FLOSS) become a public policy. In 2007, the Brazilian
-Government released a portal named Brazilian Public Software
-(\textit{Software Público Brasileiro} -- SPB, in Portuguese), with the
+Software (FLOSS) became a public policy. In 2007, the Brazilian
+Government released the Brazilian Public Software Portal
+(\textit{Portal do Software Público Brasileiro}, in Portuguese), with the
 goal of sharing FLOSS projects developed by, or for, the Brazilian
 Government.  Additionally, the Brazilian legal instrument on software
-contracting (known as IN 04/2012) mandates that public agents must give
-priority to solutions available on the SPB Portal.  In short, the
+contracting (known as IN 04/2012) mandates that public agents must 
+prioritize solutions available on the SPB Portal. The
 acquisition of a proprietary solution must be explicitly justified by
 demonstrating that there is no suitable alternative on the SPB Portal.
-In 2013, the Brazilian Federal Court issued a ruling document
-(\textit{Acórdão 2314/2013}) about an audit survey regarding the use of
-agile methodologies in software development contracts with the public
-administration.
+In 2013, the Brazilian Federal Court issued a ruling
+(\textit{Acórdão 2314/2013}) about contracts between the public administration
+and suppliers using agile methodologies in software development.
-Despite of that, in practice, free software or agile methodologies, that is,
-collaborative and empirical software development methods are not widely
-practiced and understood by the Brazilian government agents. Thus, the
-hierarchical and traditional processes from the government and the lack
-of expertise in real-world software development of its agents produces a
-situation of inefficient software development contracts and
-unjustifiable expending of taxpayers' money.
+Despite of these legal advancements, in practice, Brazilian government agents
+still do not practice, or even understand, 
+collaborative and empirical software development methods,
+such as free software or agile methodologies. Thus,
+hierarchical and traditional processes and the lack
+of expertise of public agents in real-world software development produce
+inefficiency in software development contracts, besides
+unjustifiable expending of taxpayers money.
-Since 2009, the SPB Portal was having several technical issues. The original
-codebase was not being developed anymore, also, there was a large amount of
-knowingly non-optimal or wrong design decisions to overcome (in other words,
-technical debt \cite{refactoring}). The system was a modified version of an
+Since 2009, the SPB Portal has had several technical issues. The original
+codebase development has stopped, leaving substantial
+technical debt~\cite{refactoring}.
+The system was a modified version of an
 existing FLOSS platform called OpenACS \footnote{\url{http://openacs.org}}, and
-the old SPB portal was not being updated anymore against the official OpenACS
-releases. In this scenario, the portal maintenance has become increasingly
+the old SPB Portal did not receive updates from OpenACS releases.
+In this scenario, the portal maintenance has become increasingly
 difficult.
-After some events and meetings to collect requirements from the federal
-government and from the society, a new platform for the SPB Portal was
-developed, among January 2014 and June 2016, by the University of Brasília
+After collecting requirements from the Federal
+Government and society, a new platform for the SPB Portal was
+developed, between January 2014 and June 2016, by the University of Brasília
 (UnB) and the University of São Paulo (USP) in a partnership with the Brazilian
-Ministry of Budget, Planning, and Management (MP). It was designed as an
-integrated platform for collaborative software development \cite{bobr2003}, and
-includes functionality for social networking, mailing lists, version control
+Ministry of Planning, Budget, and Management (MP). It was designed as an
+integrated platform for collaborative software development \cite{bobr2003},
+including social networking, mailing lists, version control
 system, and source code quality monitoring. To coordinate and develop this
-project during 30 months, UnB received from the Brazilian Federal Government a
-total of 2,619,965.00 BRL (about 750,000.00 USD in June 2016).
+project during 30 months, UnB was funded by a grant
+of 2,619,965.00 BRL (about 750,000.00 USD in June 2016)
+from the Federal Government.
 \begin{figure*}[hbt]
   \centering
@@ -53,44 +54,45 @@ total of 2,619,965.00 BRL (about 750,000.00 USD in June 2016).
   \label{fig:spb}
 \end{figure*}
-The project was developed by a team of 3 professors, 2 masters students, and
-approximately 50 undergraduate students (not all of them at the same time,
-though -- graduations and other events triggered changes in the team) together
-with 2 professional designers and 6 senior developers from free software
-communities. The professors and all undergraduate student were from UnB, and
-the master students were from USP. Regarding the designers and senior
-developers, 7 of 8 they were living outside of Brasília: Curitiba/Brazil, São
-Paulo/Brazil, Ribeirão Preto/Brazil, Salvador/Brazil, Santo Domingo/Dominican
-Republic, and Montreal/Canada. In other words, we had a team working in
-distributed collaborative virtual environment. This diversity of actors and the
-relationships between industry, academy and government also made the project a
+The project was developed by a team of three professors, two masters students,
+about fifty undergraduate students (not all of them at the same time,
+since the team changed along the time),
+two professional designers, and six senior developers from free software
+communities. Professors and undergraduate students were from UnB and
+master students were from USP. Regarding the designers and senior
+developers, seven of eight were living outside Brasília, the UnB location.
+Two of them were abroad at Dominican Republic and Canada.
+In other words, we had a distributed team working in a
+collaborative virtual environment. This diversity of actors and the
+relationships between industry, academy, and government also made the project a
 valued opportunity to explore the benefits and challenges of using
-FLOSS\cite{kon2011,deKoenigsberg2008, fagerholm2013, fagerholm2014} and
-Agile\cite{steghofer2016, harzl2017} practices for Software Engineering
+FLOSS~\cite{kon2011,deKoenigsberg2008, fagerholm2013, fagerholm2014} and
+Agile~\cite{steghofer2016, harzl2017} practices for Software Engineering
 education.
 Figure \ref{fig:spb} shows the home page of this integrated platform.
-All development was done in the open, and the changes we needed in the
-FLOSS tools were contributed back to their respective communities. Our
+All the code was developed as open source. The changes we needed in the
+FLOSS tools were implemented by ourselves and
+contributed back to their respective communities. Our
 process was based on agile practices and FLOSS communities interaction.
-We defined development cycles and released 5 versions of the new SPB
+We incrementally released five versions of the new SPB
 Portal. The first release (beta) was in September 2014, only 9 months
 from the beginning of the project. The old portal was shut down in
 September 2015. Finally, the last version, illustrated in Figure 1, was
 released in June 2016.
-In this paper, we present an overview of this new generation of the SPB Portal.
-The paper shares the methodology employed to develop this project, in
-partnership with the Brazilian Federal Government, to comply with its
-requirements at the same time to be as faithful as possible to FLOSS
-development \cite{mockus2002, tosi2015}. Moreover, we discuss several lessons
-learned to provide a distributed collaborative virtual environment involving
-alarge undergraduate student team and remote senior developers. Lastly, we
-released an unprecedented platform for the Brazilian government applying
+In this paper, we present an overview of the new SPB Portal.
+The paper shares the methodology employed to develop this project.
+This methodology has the goals of satisfying Government 
+requirements and adhering as much as possible to FLOSS and agile
+practices~\cite{mockus2002, tosi2015}. Moreover, we discuss lessons
+learned in providing a distributed and collaborative virtual environment involving
+a large undergraduate students team and remote senior developers. Finally, we
+released an innovative platform for helping the Brazilian government to apply
 empirical software development methods. This case can help other projects to
 overcome similar software engineering challenges in the future, as well as to
 illustrate how universities can improve the real-world experience of their
-students by means of this kind of project.
+students.
 The remainder of this work is organized as follows.
 Section \ref{sec:spb}...