DCU Home | Our Courses | Loop | Registry | Library | Search DCU

Module Specifications..

Current Academic Year 2023 - 2024

Please note that this information is subject to change.

Module Title Introduction to DevOps
Module Code CA282
School School of Computing
Module Co-ordinatorSemester 1: Denise Freir
Semester 2: Denise Freir
Autumn: Denise Freir
Module TeachersStephen Blott
Denise Freir
Dongyun Nie
Asma Slaimi
NFQ level 8 Credit Rating 5
Pre-requisite None
Co-requisite None
Compatibles None
Incompatibles None
Coursework Only
This module is 100% continuous assessment. Due to the nature of the module, which includes weekly assessed practical work, it will not be possible for students to resit the continuous assessment.
Description

The modern software-development environment involves a variety of tools to support development, building, testing and deployment of software systems. This module introduces learners to those tools, and how they are used in combination in order to support the software-development process.

Learning Outcomes

1. Use of Linux tools in the software-development process.
2. Use tools which underpin distributed development and deployment ('ssh', 'rsync', etc.).
3. Automate software build and deployment.
4. Use established software build systems ('make', 'npm', 'ant', etc.).
5. Build and install third-party software systems on a Linux systems.
6. Use industry-standard version-control systems to manage a software project ('git').
7. Use industry-standard tools for continuous integration (testing and deployment).



Workload Full-time hours per semester
Type Hours Description
Lecture12Most of the course material is available online. However, an amount of lecture time is required to ensure that the students appreciate how various course elements are used together. Lecture hours are weighted towards the start of the semester.
Laboratory24Completion of weekly lab tasks.
Fieldwork36Completion of guided/structured project work.
Fieldwork48Independent learning
Total Workload: 120

All module information is indicative and subject to change. For further information,students are advised to refer to the University's Marks and Standards and Programme Specific Regulations at: http://www.dcu.ie/registry/examinations/index.shtml

Indicative Content and Learning Activities

Unix/Linux tools
A number of the most widely-used standard Unix/Linux tools ('grep', 'cut', 'sort', etc.).

Shell scripting
Basic shell composition mechanisms, including pipelines and control flow.

Build/deploy tools
Compilers, 'make', 'npm' and installation utilities such as 'install' and 'rsync'.

Software/version-control systems
Industry-standard systems such as 'Git'.

Software-development workflow project
An independent (but guided/structured) end-to-end software development project (develop, build, test, deploy, all under the control of 'git' and 'gitlab-runner'). All students execute the same project in parallel.

Assessment Breakdown
Continuous Assessment100% Examination Weight0%
Course Work Breakdown
TypeDescription% of totalAssessment Date
FieldworkWeekly tasks assessing the use of various software tools. Assessment takes place during weeks 7-12.50%Week 6
FieldworkDevelop a small but complete software project using established industry tools and approaches. Assessment takes place during weeks 7-12.50%Week 12
Reassessment Requirement Type
Resit arrangements are explained by the following categories;
1 = A resit is available for all components of the module
2 = No resit is available for 100% continuous assessment module
3 = No resit is available for the continuous assessment component
This module is category 2
Indicative Reading List

    Other Resources

    38877, Website, 0, Git - Book, https://git-scm.com/book/en/v2,
    Change of module titles, as approved at programme board 2/3/20.
    Programme or List of Programmes
    CASEBSc in Computer Applications (Sft.Eng.)
    COMSCIBSc in Computer Science
    ECSAStudy Abroad (Engineering & Computing)
    ECSAOStudy Abroad (Engineering & Computing)
    Archives:

    My DCU | Loop | Disclaimer | Privacy Statement