Download as
Browse Code »

Commit e732ed58a86b27b0c63b89470bc6e370d4486688

Authored by Paulo Meireles
1 parent c1aeba3c
Exists in master and in 3 other branches oss_2018, oss_2018_siqueira, rework_case_study

[ieeeSW] Results of Paulo and Melissa's brainstorm

Showing 1 changed file with 23 additions and 31 deletions   Show diff stats
ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
  Diff comments   View file @e732ed5
... ... @@ -97,8 +97,6 @@ the widespread belief among government staff that any project in partnership
97 97 with a University is doomed to fail, and (2) dealing with bureaucracies
98 98 involved in the deployment process.
99 99  
100   -<!-- Melissa: Acho que no segundo, seria bom falar: lidar com a aritmia que as burocracias do governo causavam ao nosso processo de deploy? -->
101   -
102 100 Firstly, our team was not from a typical company, consisting mainly of
103 101 undergraduate students supported senior developers and designers, all
104 102 coordinated by two professors. Accordingly, time and resources allocation,
... ... @@ -130,13 +128,6 @@ department responsible for the deployment routines. With each CD cycle, we
130 128 gradually built a new relationship among all parties and, by the end of the
131 129 project, we became active participants in the deploy operations.
132 130  
133   -<!--
134   -In
135   -the first year, we had a group composed of 24 undergraduate students, one
136   -designer, and two senior developers. In 2015, our team grew to 36 students, two
137   -designers, eight senior developers. In the end, due to budget constraints, our
138   -team shrinked to 20 students, one designer, and two developers.
139   --->
140 131 ## Our Continuous Delivery Pipeline
141 132  
142 133 SPB portal is a CDE with additional social features. We built system-of-systems
... ... @@ -182,7 +173,7 @@ repository. We decided to create separate packages for each system. Packaging
182 173 brings portability, simplifies deployment, and enables configuration and
183 174 permission control.
184 175  
185   -After creating a new tag for a system, the developers informed our DevOps [4]
  176 +After creating a new tag for a system, the developers informed our DevOps
186 177 team, and the packaging process began. A set of scripts fully automated the
187 178 three packaging steps aforementioned. When all of them ran successfully, the
188 179 new packages would be ready and available for our deployment scripts.
... ... @@ -217,23 +208,17 @@ new features and bug fixes were finally available to end users.
217 208  
218 209 ## Benefits
219 210  
220   -Research points out many CD advantages in the industry [2, 5], such as
221   -accelerated time to market, building the right product, productivity and
222   -efficiency improvements, stable releases, and better customer satisfaction. The
223   -charts presented in Figure 2 show these benefits of implementing the CD in our
224   -project and associates them with the creation of a DevOps team.
  211 +CD brings many advantages such as accelerated time to market, building the
  212 +right product, productivity and efficiency improvements, stable releases, and
  213 +better customer satisfaction [2]. The charts presented in Figure 2 show these
  214 +benefits of CD in our project and associates them with the creation of a DevOps
  215 +team. In the time of 30 months, we deployed a total of 84 versions. Over 64% of
  216 +these activities happened in the second half of 2015, with the DevOps team
  217 +creation. Besides these results, working with the government, we noticed the
  218 +following additional benefits.
225 219  
226 220 ![The evolution of SPB releases and the team members distribution in the period.](figures/CDReleaseAndTeamEvolution.png)
227 221  
228   -In the time of 30 months, we deployed a total of 84 versions. Over 64% of these
229   -activities happened in the second half of 2015, with the DevOps team creation.
230   -Even with the reduction of the team as a whole, in the last months of the
231   -project, this pace of deployment was maintained until we finished all our
232   -activities.
233   -
234   -Besides these results, working with the government, we noticed the following
235   -additional benefits.
236   -
237 222 ### Strengthening Trust in the Relationship with the Government
238 223  
239 224 CD helped strengthen trust in the relationship between developers and the
... ... @@ -300,10 +285,6 @@ of our team members did not have CD know-how, and we had few working hours
300 285 available to build the pipeline. The construction and maintenance of the CD
301 286 process were made possible by the key decisions to:
302 287  
303   -<!---
304   -pensar em generalizar/filosofar
305   --->
306   -
307 288 1. _Select the most experienced senior developers and some advanced students of
308 289 the project to work on a specific DevOps team._These senior developers used
309 290 their experience in OSS projects to craft an initial proposal for the
... ... @@ -317,7 +298,7 @@ process on-the-fly.
317 298  
318 299 ### Overcoming Mistrust
319 300  
320   -<!-- Precisa 'dessuavizar' o porque das mudanças de requisitos - a motivação para ela não era tão natural como as que ocorrem em métodos ágeis -->
  301 +<!-- Tente reduzir, indo direto ao ponto para os Takeaways -->
321 302 Adopting an unfamiliar approach requires trust. In the Ministry, traditionally,
322 303 a software was the product delivered at the end of a development contract; they
323 304 expected and were prepared to validate and deploy a single deliverable. This
... ... @@ -356,10 +337,21 @@ both VE, and PE.
356 337 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.
357 338 1. L. Chen, "Continuous Delivery: Huge Benefits, but Challenges Too", IEEE Software, vol. 32, no. 2, 2015, pp. 50-54.
358 339 1. J. Humble and D. Farley, "Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation", Addison-Wesley Professional, 2010.
359   -1. J. Davis and K. Daniels, "Effective Devops: Building a Culture of Collaboration, Affinity, and Tooling at Scale", O'Reilly Media, Inc., 2016.
360   -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.
361 340  
362 341 <!---
  342 +Citadas apenas para definir coisas já disseminadas
363 343 1. G. Booch and A. Brown, A. W. "Collaborative Development Environments", Advances in Computers, vol. 59, 2003, pp. 1-27.
364 344 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.
  345 +1. J. Davis and K. Daniels, "Effective Devops: Building a Culture of Collaboration, Affinity, and Tooling at Scale", O'Reilly Media, Inc., 2016.
  346 +
  347 +Estava citada apenas na introdução dos benefícios
  348 +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.
  349 +
  350 +Considerar:
  351 +
  352 +2017 State of DevOps Report
  353 +https://puppet.com/resources/whitepaper/state-of-devops-report
  354 +
365 355 -->
  356 +
  357 +
... ...