Skip to main content
SpringerLink
Log in

Design of a (Yet Another?) DevOps Course

  • Conference paper
  • First Online:
Software Engineering Aspects of Continuous Development and New Paradigms of Software Production and Deployment (DEVOPS 2018)

Part of the book series: Lecture Notes in Computer Science ((LNPSE,volume 11350))

Abstract

DevOps have received marginal attention inside the higher education level curricula despite of its boom in the industrial sector.

This paper presents the design of an academic master-level course aimed at DevOps. The proposed design is based on earlier experiences in teaching DevOps-related topics. The specification of the course design is provided using the SWEBOK Guide and Bloom’s taxonomy to enhance the quality of the course design specification, and ease its assessment once delivered.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Log in via an institution
Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 39.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Notes

  1. 1.

    Abbreviation for the interactions between Dev (Development) and Ops (Operations).

  2. 2.

    In this paper “master-level” and “graduate” terms are used interchangeably.

  3. 3.

    European Credit Transfer and Accumulation System.

  4. 4.

    Created in 2003 and characterised by its multilingual and intercultural environment.

  5. 5.

    See Learning outcomes at [7].

  6. 6.

    “Means the knowledge and practices described are applicable to most projects most of the time, and there is consensus about their value and usefulness” [6].

  7. 7.

    The work has been revised in [12].

  8. 8.

    The other domains are affective and psychomotor.

  9. 9.

    Paper’s authors are pretty much sure that more courses would match this criteria by the time the paper sees the light of day.

  10. 10.

    This information could not be officially confirmed by the instructor at the writing of the article.

  11. 11.

    Newer versions of the tool were released after this year, as both the methodology and the tool are under continuous improvement.

  12. 12.

    Tools for supporting any single task of the software development project life cycle, workbenches which combine in an integrated way two or more tools to cover a sub-part of the software development project life cycle, and environments which combine tools and workbenches in order to cover the full software development project life cycle.

  13. 13.

    One of the teaching staff members.

  14. 14.

    Average of the given grades.

  15. 15.

    The number of projects was directly proportional to the number of students registered to the course.

  16. 16.

    It is planned to keep using the ISO/IEC 25010:2011 Standard [22] to introduce the notion of product quality model.

  17. 17.

    Tracking times taken from [14].

  18. 18.

    While the conditions would allow it, groups will be made of up to 3 students.

  19. 19.

    Commit, build, automated test cases execution, deploy (if all test cases have passed).

  20. 20.

    Teaching staff composition to deliver the new version of the course.

References

  1. LinkedIn Economic Graph Team: LinkedIn’s 2017 U.S. Emerging Jobs Report, December 2017. https://economicgraph.linkedin.com/research/LinkedIns-2017-US-Emerging-Jobs-Report

  2. VersionOne: 11th annual state of agile report (2017). https://explore.versionone.com/state-of-agile/versionone-11th-annual-state-of-agile-report-2

  3. Standard, N.I.: DevOps - standard for building reliable and secure systems including application build, package and deployment (2016). https://standards.ieee.org/develop/project/2675.html

  4. Jabbari, R., bin Ali, N., Petersen, K., Tanveer, B.: What is DevOps?: a systematic mapping study on definitions and practices. In: Proceedings of the Scientific Workshop Proceedings of XP 2016. XP 2016 Workshops, pp. 12:1–12:11. ACM, New York (2016)

    Google Scholar 

  5. DevOps Educator Workshop: First DevOps Educators Workshop, November 2016. https://github.com/devopseducator/2016workshop

  6. Society, I.C., Bourque, P., Fairley, R.E.: Guide to the Software Engineering Body of Knowledge (SWEBOK(R)): Version 3.0, 3rd edn. IEEE Computer Society Press, Los Alamitos (2014)

    Google Scholar 

  7. MiCS: Master in information and computer sciences (2010). https://mics.uni.lu

  8. Pyster, A., et al.: Graduate software engineering 2009 (GSwE2009) curriculum guidelines for graduate degree programs in software engineering. Stevens Institute of Technology (2009)

    Google Scholar 

  9. Joint Task Force on Computing Curricula, Association for Computing Machinery (ACM) and IEEE Computer Society: Computer Science Curricula: Curriculum Guidelines for Undergraduate Degree Programs in Computer Science. ACM, New York (2013). ACM Order Number: 999133

    Google Scholar 

  10. The Joint Task Force on Computing Curricula: Curriculum guidelines for undergraduate degree programs in software engineering. Technical report, New York, NY, USA (2015)

    Google Scholar 

  11. Bloom, B.: Taxonomy of Educational Objectives: The Classification of Educational Goals. Mackay, New York (1956)

    Google Scholar 

  12. Anderson, L., Krathwohl, D., Bloom, B.: A Taxonomy for Learning, Teaching, and Assessing: A Revision of Bloom’s Taxonomy of Educational Objectives. Longman, New York (2001)

    Google Scholar 

  13. IEEE Computer Society: Guide to the software engineering body of knowledge 2004 version. SWEBOK 2004 Guide to the Software Engineering Body of Knowledge (2004)

    Google Scholar 

  14. Bass, L.: DevOps: Modern Deployment (2017). http://mse.isri.cmu.edu/software-engineering/Courses/17-611-DevOps-Modern-Deployment.html

  15. Bass, L., Weber, I.M., Zhu, L.: DevOps: A Software Architect’s Perspective. Addison-Wesley Professional, New York (2015)

    Google Scholar 

  16. Parnin, C.J.: DevOps: modern software engineering practices, August 2017. https://wolfware.ncsu.edu/courses/details/?sis_id=SIS:2018:1:1:CSC:519:001

  17. DEVOPS18: First international workshop on software engineering for continuous development and new paradigms of software production and deployment (2018). https://www.laser-foundation.org/devops/2018/

  18. Mosser, S., Pinna-Déry, A.-M., Collet, P., Molines, G.: Introduction to software architecture and DevOps (2017). https://github.com/mosser/isa-devops

  19. Jones, C.: Continuous delivery and DevOps (2017). https://www.cdm.depaul.edu/academics/pages/classinfo.aspx?Term=20182&ClassNbr=21100&fid=258484

  20. Humble, J., Farley, D.: Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation, 1st edn. Addison-Wesley Professional, New York (2010)

    Google Scholar 

  21. Guelfi, N., Capozucca, A., Ries, B.: Website of the Messir Method and the Excalibur Environment (2014). https://messir.uni.lu

  22. ISO/IEC: ISO/IEC 25010 - Systems and software engineering - Systems and software Quality Requirements and Evaluation (SQuaRE) - System and software quality models. ISO/IEC 13211-1 (2011)

    Google Scholar 

  23. Davis, J., Daniels, K.: Effective DevOps: Building a Culture of Collaboration, Affinity, and Tooling at Scale, 1st edn. O’Reilly Media, Inc., Sebastopol (2016)

    Google Scholar 

  24. Httermann, M.: DevOps for Developers, 1st edn. Apress, Berkely (2012)

    Book  Google Scholar 

Download references

Author information

Authors and Affiliations

  1. Faculty of Science, Technology and Communication, University of Luxembourg, Maison du Nombre, 6, Avenue de la Fonte, 4364, Esch-sur-Alzette, Luxembourg

    Alfredo Capozucca, Nicolas Guelfi & Benoît Ries

Authors
  1. Alfredo Capozucca
    View author publications

    You can also search for this author in PubMed Google Scholar

  2. Nicolas Guelfi
    View author publications

    You can also search for this author in PubMed Google Scholar

  3. Benoît Ries
    View author publications

    You can also search for this author in PubMed Google Scholar

Corresponding author

Correspondence to Alfredo Capozucca .

Editor information

Editors and Affiliations

  1. University of Toulouse, Toulouse, France

    Jean-Michel Bruel

  2. Innopolis University, Innopolis, Russia

    Manuel Mazzara

  3. Innopolis University and Politecnico di Milano, Innopolis, Russia

    Bertrand Meyer

Rights and permissions

Reprints and permissions

Copyright information

© 2019 Springer Nature Switzerland AG

About this paper

Check for updates. Verify currency and authenticity via CrossMark

Cite this paper

Capozucca, A., Guelfi, N., Ries, B. (2019). Design of a (Yet Another?) DevOps Course. In: Bruel, JM., Mazzara, M., Meyer, B. (eds) Software Engineering Aspects of Continuous Development and New Paradigms of Software Production and Deployment. DEVOPS 2018. Lecture Notes in Computer Science(), vol 11350. Springer, Cham. https://doi.org/10.1007/978-3-030-06019-0_1

Download citation

  • DOI: https://doi.org/10.1007/978-3-030-06019-0_1

  • Published:

  • Publisher Name: Springer, Cham

  • Print ISBN: 978-3-030-06018-3

  • Online ISBN: 978-3-030-06019-0

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics

Search

Navigation