From 970dcb1e85c09281ddc2f7fa9fa0436062a56d72 Mon Sep 17 00:00:00 2001 From: Melissa Wen Date: Sat, 11 Nov 2017 01:58:28 -0200 Subject: [PATCH] [i3eSW] adding references --- ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md index 49f7528..3d2ea3b 100644 --- a/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md +++ b/ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md @@ -218,7 +218,7 @@ leader resulted in requirements and priorities changes, most of them motivated by political needs. We believed that if we took too long to attend their demands, the government would use undelivered requirements as a means to justify the lack of financial support and the end of the project. -% + CD helped us keep the production environment up-to-date, even with partial versions of a feature. That way, we always had something to show on meetings, 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 features developed only at the end of the release, usually every four months. However, this periodicity did not meet the requirements of their leaders, who demanded monthly reports on the progress of the project. -% + With the implementation of CD, intermediate and candidate versions became available, allowing analysts to perform small validations over time. The 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 to pass the knowledge from developers who had already understood the CD to the others who were dedicated to the development of features of the platform, and evolving the process on-the-fly. -% + Building a CD pipeline was hard in the beginning. We believe that more tools to provide out-of-the-box standardized CD pipelines would be of great help for 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 1. G. Booch, A. W. Brown, "Collaborative Development Environments", in Advances in Computers, vol. 59, 2003, pp. 1–27. 2. L. Chen, "Continuous Delivery: Huge Benefits, but Challenges Too", in IEEE Software, vol. 32, no. 2, 2015, pp. 50-54. 3. Davis, Jennifer and Daniels, Katherine, Effective DevOps: building a culture of collaboration, affinity, and tooling at scale, 2016, " O'Reilly Media, Inc." +4. Humble, J. and Farley, D., 2010. Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation. Pearson Education. +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. +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. +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. +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. + -- libgit2 0.21.2