Commit 6dd0b9766791422f65d361f47c92efb5ef0dddc7
Exists in
master
and in
3 other branches
Merge branch 'master' of softwarepublico.gov.br:softwarepublico/articles
Showing
3 changed files
with
12 additions
and
13 deletions
Show diff stats
opensym2017/content/01-introduction.tex
| 1 | \section{Introduction} | 1 | \section{Introduction} |
| 2 | \label{sec:intro} | 2 | \label{sec:intro} |
| 3 | 3 | ||
| 4 | -The Brazilian Government released in the year 2000 the Eletronic Government | 4 | +In the year 2000, the Brazilian Government released the Eletronic Government |
| 5 | program (eGov) aiming at democratizing information access and improving the | 5 | program (eGov) aiming at democratizing information access and improving the |
| 6 | -public provision quality of service and information. | 6 | +quality of public provision of service and information. |
| 7 | % | 7 | % |
| 8 | In 2003, the Federal Government created a committee for implementation of | 8 | In 2003, the Federal Government created a committee for implementation of |
| 9 | Free/Libre/Open Source Software (FLOSS)\footnote{Free Software, Open Source, or | 9 | Free/Libre/Open Source Software (FLOSS)\footnote{Free Software, Open Source, or |
| @@ -73,7 +73,7 @@ the methodology employed to develop this project. This methodology has the | @@ -73,7 +73,7 @@ the methodology employed to develop this project. This methodology has the | ||
| 73 | goals of satisfying Government requirements and adhering as much as possible to | 73 | goals of satisfying Government requirements and adhering as much as possible to |
| 74 | FLOSS and agile practices~\cite{mockus2002, tosi2015}. Moreover, we discuss | 74 | FLOSS and agile practices~\cite{mockus2002, tosi2015}. Moreover, we discuss |
| 75 | lessons learned in providing a distributed and collaborative virtual | 75 | lessons learned in providing a distributed and collaborative virtual |
| 76 | -environment involving a large undergraduate students team and remote senior | 76 | +environment involving a large team of undergraduate students and remote senior |
| 77 | developers. In short, we released an innovative platform for helping the | 77 | developers. In short, we released an innovative platform for helping the |
| 78 | Brazilian government to apply empirical software development methods. This case | 78 | Brazilian government to apply empirical software development methods. This case |
| 79 | can help other projects to overcome similar software engineering challenges in | 79 | can help other projects to overcome similar software engineering challenges in |
opensym2017/content/02-spb.tex
| @@ -41,16 +41,16 @@ social networking environments. | @@ -41,16 +41,16 @@ social networking environments. | ||
| 41 | 41 | ||
| 42 | Initially, the purpose of the portal was only to share the software developed | 42 | Initially, the purpose of the portal was only to share the software developed |
| 43 | in the Brazilian government to reduce the costs of hiring software. However, it | 43 | in the Brazilian government to reduce the costs of hiring software. However, it |
| 44 | -was observed that when softwares were released, their communities were formed | ||
| 45 | -around those software with several people collaborating and sharing the results | 44 | +was observed that when a software was released, a community was formed |
| 45 | +around it, with several people collaborating and sharing the results | ||
| 46 | obtained through the use of those solutions, as commonly occurs in FLOSS | 46 | obtained through the use of those solutions, as commonly occurs in FLOSS |
| 47 | \cite{ducheneaut2005}. In this way, some software development cooperatives and | 47 | \cite{ducheneaut2005}. In this way, some software development cooperatives and |
| 48 | private companies have shown an interest in making their software available on | 48 | private companies have shown an interest in making their software available on |
| 49 | the SPB Portal. | 49 | the SPB Portal. |
| 50 | 50 | ||
| 51 | -The concept of SPB goes beyond FLOSS \cite{freitas2008}. In addition to being | ||
| 52 | -licensed under a FLOSS license, a SPB needs to have explicit guarantees that it | ||
| 53 | -is a public good, and that project must be available on the SPB portal. Being a | 51 | +The concept of Brazilian Public Software goes beyond FLOSS \cite{freitas2008}. In addition to being |
| 52 | +licensed under a FLOSS license, this software needs to have explicit guarantees that it | ||
| 53 | +is a public good, and its project must be available on the SPB portal. Being a | ||
| 54 | true public good assumes requirements that can not be met solely by means of | 54 | true public good assumes requirements that can not be met solely by means of |
| 55 | FLOSS licensing. For example, there must be a relaxed trademark usage policy by | 55 | FLOSS licensing. For example, there must be a relaxed trademark usage policy by |
| 56 | the original vendor that does not stop eventual competitors from advertising | 56 | the original vendor that does not stop eventual competitors from advertising |
opensym2017/content/04-researchdesign.tex
| @@ -27,14 +27,13 @@ Government. For the majority of the students, this was a first professional | @@ -27,14 +27,13 @@ Government. For the majority of the students, this was a first professional | ||
| 27 | experience. Even though, our development process defined a central role on | 27 | experience. Even though, our development process defined a central role on |
| 28 | students participation. | 28 | students participation. |
| 29 | 29 | ||
| 30 | -\textbf{Q3:} \textit{How to introduce collaborative and agile practices typical | ||
| 31 | -in FLOSS environments in the governmental development process?} | 30 | +\textbf{Q3:} \textit{How to introduce typical FLOSS collaborative and agile practices in the governmental development process?} |
| 32 | % | 31 | % |
| 33 | -The software development on Brazilian government is based on a very traditional | 32 | +The software development in Brazilian government is based on a very traditional |
| 34 | way, frequently focusing documentation deliveries. We had to convince them to | 33 | way, frequently focusing documentation deliveries. We had to convince them to |
| 35 | accept the idea of open scope and empirical development. They had certain | 34 | accept the idea of open scope and empirical development. They had certain |
| 36 | -expectations about the project development according to RUP (Rational Unified | ||
| 37 | -Process) and PMBOK (Project Management Body of Knowledge) approaches, which | 35 | +expectations about the project development according to the Rational Unified |
| 36 | +Process (RUP) and the Project Management Body of Knowledge (PMBOK) approaches, which | ||
| 38 | mismatched our work style based on agile and FLOSS practices. So we created | 37 | mismatched our work style based on agile and FLOSS practices. So we created |
| 39 | strategies to conciliate these different organizational cultures within the | 38 | strategies to conciliate these different organizational cultures within the |
| 40 | project. | 39 | project. |