Commit 852708ef48578c7f6ff5f0235c9918de75cc6048
1 parent
28f48f19
Exists in
master
and in
3 other branches
[ieeeSW] minor adjustments
Showing
1 changed file
with
5 additions
and
6 deletions
Show diff stats
ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
@@ -101,7 +101,7 @@ the worst political crisis after the re-democratization in Brazil. | @@ -101,7 +101,7 @@ the worst political crisis after the re-democratization in Brazil. | ||
101 | 101 | ||
102 |  | 102 |  |
103 | 103 | ||
104 | -The figure represents our CD pipeline. The pipeline started when new code arrived. | 104 | +The Figure 1 represents our CD pipeline. The pipeline started when new code arrived. |
105 | As it went through each step, it was tested and improved until it finally reached | 105 | As it went through each step, it was tested and improved until it finally reached |
106 | the production environment. At this point we got back to the first stage to release | 106 | the production environment. At this point we got back to the first stage to release |
107 | more new code. | 107 | more new code. |
@@ -218,7 +218,7 @@ constantly updated the VE based on their feedback. This made our relation | @@ -218,7 +218,7 @@ constantly updated the VE based on their feedback. This made our relation | ||
218 | strong and in moments that needed quick action they would rather give us access | 218 | strong and in moments that needed quick action they would rather give us access |
219 | to production. | 219 | to production. |
220 | 220 | ||
221 | -### Shared Responsibility | 221 | +### Shared responsibility |
222 | 222 | ||
223 | Before the adoption of the CD, the developers team could not track what happened to the code | 223 | Before the adoption of the CD, the developers team could not track what happened to the code |
224 | after its delivery, since government technicians were the only responsibles | 224 | after its delivery, since government technicians were the only responsibles |
@@ -236,7 +236,7 @@ order to speed up the process of making available, in the production environment | @@ -236,7 +236,7 @@ order to speed up the process of making available, in the production environment | ||
236 | new features for the platform. | 236 | new features for the platform. |
237 | 237 | ||
238 | 238 | ||
239 | -### Synchronicity between Government and Development | 239 | +### Synchronicity between government and development |
240 | 240 | ||
241 | Despite the positive impacts that the CD pipeline brought to the project, its | 241 | Despite the positive impacts that the CD pipeline brought to the project, its |
242 | implementation was not easy at first. The good performance of the CD pipeline | 242 | implementation was not easy at first. The good performance of the CD pipeline |
@@ -255,9 +255,9 @@ scale of work and to request the access to production in time. | @@ -255,9 +255,9 @@ scale of work and to request the access to production in time. | ||
255 | 255 | ||
256 | Continuous delivery was also a tool that helped to strengthen trust in the | 256 | Continuous delivery was also a tool that helped to strengthen trust in the |
257 | relationship between developers and government analysts, as well as between the | 257 | relationship between developers and government analysts, as well as between the |
258 | -latter group and its superiors.Before using CD, analysts had access to the | 258 | +latter group and its superiors. Before using CD, analysts had access to the |
259 | features developed only at the end of the release, usually every 4 months. | 259 | features developed only at the end of the release, usually every 4 months. |
260 | -However, this periodicity did not meet the requirements of their directors, who | 260 | +However, this periodicity did not meet the requirements of their leaders, who |
261 | demanded monthly reports on the progress of the project. With the | 261 | demanded monthly reports on the progress of the project. With the |
262 | implementation of the CD, intermediate versions became available, allowing | 262 | implementation of the CD, intermediate versions became available, allowing |
263 | analysts to perform small validations over time. The constant monitoring of | 263 | analysts to perform small validations over time. The constant monitoring of |
@@ -310,6 +310,5 @@ between industry and government, specially regarding CD. | @@ -310,6 +310,5 @@ between industry and government, specially regarding CD. | ||
310 | 310 | ||
311 | 1. G. Booch, A. W. Brown, "Collaborative Development Environments", in Advances in Computers, vol. 59, 2003, pp. 1–27. | 311 | 1. G. Booch, A. W. Brown, "Collaborative Development Environments", in Advances in Computers, vol. 59, 2003, pp. 1–27. |
312 | 1. L. Chen, "Continuous Delivery: Huge Benefits, but Challenges Too", in IEEE Software, vol. 32, no. 2, 2015, pp. 50-54. | 312 | 1. L. Chen, "Continuous Delivery: Huge Benefits, but Challenges Too", in IEEE Software, vol. 32, no. 2, 2015, pp. 50-54. |
313 | -1. P. Meirelles, M. Wen, A. Terceiro, R. Siqueira, L. Kanashiro, and H. Neri, "Brazilian Public Software Portal: an integrated platform for collaborative development", in Proceedings of the 13th International Symposium on Open Collaboration, 2017. | ||
314 | 313 | ||
315 | 314 |