More adjustmentsx

Paulo Meireles
1 parent 8ded30d4
Showing 1 changed file with 24 additions and 19 deletions Show diff stats
ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
@@ -55,16 +55,16 @@ Comment: &quot;Generally, the piece comes across as part advertisement for CI and par
 Siqueira/Paulo: Ao meu ver, a introdução deixa bem claro o nosso "punch" e o resto do texto a gente desenrola bem isso
 -->
-We worked on a three-year-long Brazilian government project to evolve an
+We worked on a thirty-month-long Brazilian government project to evolve an
 existing platform that had technical issues and lacked political support.  This
 project, started in 2014, was a partnership between the Ministry of Planning,
 Budget, and Management (MP) and two public universities: University of Brasília
 (UnB) and University of São Paulo (USP), to modernize Brazilian Public Software
-(SPB) portal.
+(SPB) portal (www.softwarepublico.gov.br).
-With this partnership, the SPB portal (www.softwarepublico.gov.br) evolved to a
-Collaborative Development Environment[1], and this evolution brought
-significant benefits not just to the Brazilian government, but also to society
+With this partnership, the SPB portal evolved to a
+Collaborative Development Environment (CDE)[1], and this evolution brought
+significant benefits not just to the government, but also to society
 as a whole.  The government could minimize bureaucracy and costs of software
 development, encouraging the use of the same set of applications across
 different government agencies. The society also gained a mechanism of
@@ -128,13 +128,12 @@ Comment:
 Siqueira/Paulo: Contamos essa história sem ter que entrar em detalhes aqui. Contudo, será preciso fazer a seção de pipeline harmonizar com isso
 -->
-Firstly, to find a system solution wherein MP agents and development team
-agree, we designed the SPB portal as a CDE with additional social features. Due
+To face the first issue, we designed the SPB portal as a CDE with additional social features. Due
 to the complexity of creating such a system from scratch, we decided to adapt
-and integrate existing OSS tools to build a system-of-systems [3]. We created a
+and integrate existing OSS tools to build a system-of-systems[1]. We created a
 solution that orchestrates software and allowed us to smoothly provide a
-unified interface for final users, including single sign-on and global searches
-[4]. On top of that, the new SPB portal was an unprecedented platform to the
+unified interface for final users, including single sign-on and global searches.
+On top of that, the new SPB portal was an unprecedented platform to the
 Brazilian government, with a complicated deployment process.
 <!---
@@ -150,8 +149,7 @@ Comment:
 Siqueira/Paulo: Isso aqui também fica resolvido
 -->
-Secondly, we had to face the widespread belief among MP agents that any project
-in partnership with a University is doomed to fail. Our team was not from a
+Regarding to the second problem, our team was not from a
 typical company, consisting mainly of undergraduate students coordinated by two
 professors. At the first year, we had a group composed of 24 undergraduate
 students, one designer, and two senior developers. In 2015, our team grew to 36
@@ -248,7 +246,7 @@ five reasons:
 1. Packaging makes it easy to manage the software on a given distribution;
 1. Packaging simplifies the deployment;
 1. Packaging follows the distribution's best practices and,
-* Packaging allows configurations and permissions control.
+1. Packaging allows configurations and permissions control.
 After creating a new tag for one component, the developers informed our DevOps
 [6] team, and the packaging process began. A set of scripts fully automated the
@@ -424,11 +422,18 @@ Paulo: Acho que precisamos de algo ligado ao Ha-Ha-moment para fechar o texto aq
 ## References
+1. P .Meirelles, M. Wen, A. Terceiro, R. Siqueira, L. Kanashiro, and H. Neri, "Brazilian Public Software Portal: an integrated platform for collaborative development", Proceedings of the 13th International Symposium on Open Collaboration. ACM, Article 16, 2017, 10 pages.
+1. L. Chen, "Continuous Delivery: Huge Benefits, but Challenges Too", IEEE Software, vol. 32, no. 2, 2015, pp. 50-54.
+1. J. Humble and D. Farley, "Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation", Addison-Wesley Professional, 2010.
+1. J. Davis and K. Daniels, "Effective Devops: Building a Culture of Collaboration, Affinity, and Tooling at Scale", O'Reilly Media, Inc., 2016.
+1. T. Savor, M. Douglas, M. Gentili, L. Williams, K. Beck and M. Stumm, "Continuous Deployment at Facebook and OANDA", 2016 IEEE/ACM 38th International Conference on Software Engineering Companion (ICSE-C), Austin, TX, 2016, pp. 21-30.
+
+
+<!---
+Paulo: Entendo que neste tipo de texto não precisamos de referências para conceituar CDE e SoS
+
 1. G. Booch and A. Brown, A. W. "Collaborative Development Environments", Advances in Computers, vol. 59, 2003, pp. 1-27.
-2. L. Chen, "Continuous Delivery: Huge Benefits, but Challenges Too", IEEE Software, vol. 32, no. 2, 2015, pp. 50-54.
-3. C. B. Nielsen, P. G. Larsen, J. Fitzgerald, J. Woodcock, and J. Peleska, "Systems of Systems Engineering: Basic Concepts, Model-Based Techniques, and Research Directions", ACM Comput. Surv. 48, 2, Article 18, 2015, 41 pages.
-4. P .Meirelles, M. Wen, A. Terceiro, R. Siqueira, L. Kanashiro, and H. Neri, "Brazilian Public Software Portal: an integrated platform for collaborative development", Proceedings of the 13th International Symposium on Open Collaboration (OpenSym '17). ACM, Article 16, 2017, 10 pages.
-5. J. Humble and D. Farley, "Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation", Addison-Wesley Professional, 2010.
-6. J. Davis and K. Daniels, "Effective Devops: Building a Culture of Collaboration, Affinity, and Tooling at Scale", O'Reilly Media, Inc., 2016.
-7. T. Savor, M. Douglas, M. Gentili, L. Williams, K. Beck and M. Stumm, "Continuous Deployment at Facebook and OANDA", 2016 IEEE/ACM 38th International Conference on Software Engineering Companion (ICSE-C), Austin, TX, 2016, pp. 21-30.
+1. C. B. Nielsen, P. G. Larsen, J. Fitzgerald, J. Woodcock, and J. Peleska, "Systems of Systems Engineering: Basic Concepts, Model-Based Techniques, and Research Directions", ACM Comput. Surv. 48, 2, Article 18, 2015, 41 pages.
+
+-->