Commit d40be3bebba7f578de966338fe8f03ab9d55303d
1 parent
44ea3694
Exists in
master
and in
3 other branches
[i3eSW] improvements in the introduction section
Showing
1 changed file
with
19 additions
and
22 deletions
Show diff stats
ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
@@ -13,30 +13,27 @@ understand how important the CD adoption is to their projects. | @@ -13,30 +13,27 @@ understand how important the CD adoption is to their projects. | ||
13 | 13 | ||
14 | ## Introduction and Context | 14 | ## Introduction and Context |
15 | 15 | ||
16 | -We have worked on a Brazilian government three-year-long project to evolve an | 16 | +We have worked on a Brazilian government three-year-long project to redesign an |
17 | existing platform that had technical issues and a lack of political support. | 17 | existing platform that had technical issues and a lack of political support. |
18 | -The evolution project started in a presidential election year and everyone | 18 | +This evolution project started in a presidential election year and everyone |
19 | involved were under Presidential re-election campaign pressure to show results. | 19 | involved were under Presidential re-election campaign pressure to show results. |
20 | -Even with the re-election of the Brazilian President in 2014, leadership in | ||
21 | -government agencies suddenly changed, what was worsened by corruption scandals | ||
22 | -revealed by the Brazilian Federal police, in particular the "Car-Wash" | ||
23 | -investigation. That reflected on the project’s requirements: each new leader | ||
24 | -wanted to fulfill their political agenda. In this scenario, delivery delays | ||
25 | -could have sunk the project into oblivion. | ||
26 | - | ||
27 | -From 2014 to 2016, our team developed the new platform for the Brazilian Public | ||
28 | -Software (SPB, Portuguese acronym) Portal (www.softwarepublico.gov.br) funded | ||
29 | -by a grant of 2,619,965.00 BRL (about 1.000,000.00 USD in January 2014) from | ||
30 | -the Federal Government. The SPB Portal has evolved to a CDE [1] and this | ||
31 | -evolution has brought important benefits not just to the Brazilian government , | ||
32 | -but also to society as a whole. For the government, the bureaucracy on using | ||
33 | -the same software across government agencies, duplicate works and costs all are | ||
34 | -reduced. The society gains a transparency and collaboration mechanism, since | ||
35 | -anyone can check the government expenses on software and contribute to the | ||
36 | -software communities. To achieve these goals, we have chosen to integrate more | ||
37 | -than free software tools (such as Gitlab (www.gitlab.com), Mailman | ||
38 | -(www.gnu.org/software/mailman), Noosfero (www.noosfero.org), and Colab | ||
39 | -(www.github.com/colab)) rather than write everything from scratch. | 20 | +Even with the re-election of the Brazilian President, leadership in government |
21 | +agencies suddenly changed that reflected on the project’s requirements: each | ||
22 | +new leader wanted to fulfill their political agenda. In this scenario, delivery | ||
23 | +delays could have sunk the project into oblivion. | ||
24 | + | ||
25 | +From 2013 to 2016, our team developed the new platform for the Brazilian Public | ||
26 | +Software (SPB, Portuguese acronym) Portal (www.softwarepublico.gov.br). The SPB | ||
27 | +Portal has evolved to a CDE [1] and this evolution has brought important | ||
28 | +benefits not just to the Brazilian government , but also to society as a whole. | ||
29 | +For the government, the bureaucracy on using the same software across | ||
30 | +government agencies, duplicate works and costs all are reduced. The society | ||
31 | +gains a transparency and collaboration mechanism, since anyone can check the | ||
32 | +government expenses on software and contribute to the software communities. To | ||
33 | +achieve these goals, we have chosen to integrate more than free software tools | ||
34 | +(such as Gitlab (www.gitlab.com), Mailman (www.gnu.org/software/mailman), | ||
35 | +Noosfero (www.noosfero.org), and Colab (www.github.com/colab)) rather than | ||
36 | +write everything from scratch. | ||
40 | 37 | ||
41 | During the entire SPB Portal evolution project, we had to handle three distinct | 38 | During the entire SPB Portal evolution project, we had to handle three distinct |
42 | issues, usual in a software engineering scenario: reaching the goals which have | 39 | issues, usual in a software engineering scenario: reaching the goals which have |