Download as
Browse Code »

Commit 970dcb1e85c09281ddc2f7fa9fa0436062a56d72

Authored by Melissa Wen
1 parent 810c2a28
Exists in master and in 3 other branches oss_2018, oss_2018_siqueira, rework_case_study

[i3eSW] adding references

Showing 1 changed file with 9 additions and 3 deletions   Show diff stats
ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
  Diff comments   View file @970dcb1
@@ -218,7 +218,7 @@ leader resulted in requirements and priorities changes, most of them motivated @@ -218,7 +218,7 @@ leader resulted in requirements and priorities changes, most of them motivated
218 by political needs. We believed that if we took too long to attend their 218 by political needs. We believed that if we took too long to attend their
219 demands, the government would use undelivered requirements as a means to 219 demands, the government would use undelivered requirements as a means to
220 justify the lack of financial support and the end of the project. 220 justify the lack of financial support and the end of the project.
221 -% 221 +
222 CD helped us keep the production environment up-to-date, even with partial 222 CD helped us keep the production environment up-to-date, even with partial
223 versions of a feature. That way, we always had something to show on meetings, 223 versions of a feature. That way, we always had something to show on meetings,
224 reducing anxiety to get the platform concluded. For our team, it made the 224 reducing anxiety to get the platform concluded. For our team, it made the
@@ -263,7 +263,7 @@ analysts group and its superiors. Before using CD, analysts had access to the @@ -263,7 +263,7 @@ analysts group and its superiors. Before using CD, analysts had access to the
263 features developed only at the end of the release, usually every four months. 263 features developed only at the end of the release, usually every four months.
264 However, this periodicity did not meet the requirements of their leaders, who 264 However, this periodicity did not meet the requirements of their leaders, who
265 demanded monthly reports on the progress of the project. 265 demanded monthly reports on the progress of the project.
266 -% 266 +
267 With the implementation of CD, intermediate and candidate versions became 267 With the implementation of CD, intermediate and candidate versions became
268 available, allowing analysts to perform small validations over time. The 268 available, allowing analysts to perform small validations over time. The
269 constant monitoring of the development work brought greater security to the 269 constant monitoring of the development work brought greater security to the
@@ -293,7 +293,7 @@ team. The benefits of these movements were twofold: mitigating the difficulty @@ -293,7 +293,7 @@ team. The benefits of these movements were twofold: mitigating the difficulty
293 to pass the knowledge from developers who had already understood the CD to the 293 to pass the knowledge from developers who had already understood the CD to the
294 others who were dedicated to the development of features of the platform, and 294 others who were dedicated to the development of features of the platform, and
295 evolving the process on-the-fly. 295 evolving the process on-the-fly.
296 -% 296 +
297 Building a CD pipeline was hard in the beginning. We believe that more tools 297 Building a CD pipeline was hard in the beginning. We believe that more tools
298 to provide out-of-the-box standardized CD pipelines would be of great help for 298 to provide out-of-the-box standardized CD pipelines would be of great help for
299 inexperienced teams. Tools that track each step of the pipeline and organize 299 inexperienced teams. Tools that track each step of the pipeline and organize
@@ -330,4 +330,10 @@ We thank our colleagues, Lucas Kanashiro and Rafael Manzo, and this article's re @@ -330,4 +330,10 @@ We thank our colleagues, Lucas Kanashiro and Rafael Manzo, and this article's re
330 1. G. Booch, A. W. Brown, "Collaborative Development Environments", in Advances in Computers, vol. 59, 2003, pp. 1–27. 330 1. G. Booch, A. W. Brown, "Collaborative Development Environments", in Advances in Computers, vol. 59, 2003, pp. 1–27.
331 2. L. Chen, "Continuous Delivery: Huge Benefits, but Challenges Too", in IEEE Software, vol. 32, no. 2, 2015, pp. 50-54. 331 2. L. Chen, "Continuous Delivery: Huge Benefits, but Challenges Too", in IEEE Software, vol. 32, no. 2, 2015, pp. 50-54.
332 3. Davis, Jennifer and Daniels, Katherine, Effective DevOps: building a culture of collaboration, affinity, and tooling at scale, 2016, " O'Reilly Media, Inc." 332 3. Davis, Jennifer and Daniels, Katherine, Effective DevOps: building a culture of collaboration, affinity, and tooling at scale, 2016, " O'Reilly Media, Inc."
  333 +4. Humble, J. and Farley, D., 2010. Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation. Pearson Education.
  334 +5. Savor, T., Douglas, M., Gentili, M., Williams, L., Beck, K. and Stumm, M., 2016, May. Continuous deployment at Facebook and OANDA. In Proceedings of the 38th International Conference on Software Engineering Companion (pp. 21-30). ACM.
  335 +6. Anthopoulos, L., Reddick, C.G., Giannakidou, I. and Mavridis, N., 2016. Why e-government projects fail? An analysis of the Healthcare. gov website. Government Information Quarterly, 33(1), pp.161-173.
  336 +7. Chen, L., 2015, May. Research opportunities in continuous delivery: reflections from two years' experiences in a large bookmaking company. In Proceedings of the Third International Workshop on Release Engineering (pp. 2-2). IEEE Press.
  337 +8. Chen, L., 2015, May. Towards architecting for continuous delivery. In Software Architecture (WICSA), 2015 12th Working IEEE/IFIP Conference on (pp. 131-134). IEEE.
  338 +
333 339