AI curriculum
Course outline for Software Engineering Foundations for AI Engineers
Follow a software change from an initial requirement to a maintained release. Learn how teams plan work, use version control, review code, test changes, and automate delivery. Distinguish development, QA, staging, and production environments and understand how releases, monitoring, and feedback connect the software development lifecycle. The course concerns delivering software, not programming paradigms.
Software Engineering Foundations for AI Engineers Course Objectives
- Explain the software development lifecycle and its feedback loops.
- Turn a requirement into planned work with acceptance criteria.
- Use Git and a code review to integrate a small change.
- Explain test levels, delivery pipelines, environments, release, and maintenance.
Pre-requisites
- Read and make small changes to a program.
- Use files, a code editor, and basic terminal commands.
- No Git, CI/CD, cloud, or AI experience is required.
Before this course
Complete the required courses or bring equivalent experience. Recommended courses add useful depth; they are not enrolment gates.
No prerequisite course is required. The entry skills above still apply.
Readiness checks
- Read and make small changes to a program.
- Use files, a code editor, and basic terminal commands.
- No Git, CI/CD, cloud, or AI experience is required.
Can read and make small program changes and use files, an editor, and basic terminal commands; no Git, CI/CD, cloud, or AI experience is required.
Find your place in the learning mapLab Setup
Delivery requirements: the following environment, materials, access, and exercise timing must be prepared and verified before delivery. This outline does not certify that a lab package is ready.
A prepared small repository, Git, a code editor, a supported runtime, and a local build/test command. A hosted repository service is optional. Environment promotion uses local or simulated targets; this course does not require cloud accounts or access to production. Lab materials must be prepared before delivery.
Detailed Course Outline
Module 1: From a need to a delivery plan (2 hours)
- Software development lifecycle: Requirements, design, implementation, testing, deployment, operations, and maintenance.
- Sequential and iterative delivery: Sequential and iterative delivery; Agile principles and incremental feedback.
- Stakeholders and requirements: Identify stakeholder roles and distinguish functional from non-functional requirements.
- Scope and acceptance criteria: Scope, user stories, acceptance criteria, and a definition of done.
- Planning the work: Tasks, estimates, dependencies, risks, and a simple project board.
Practical outcome: Plan a small change with acceptance criteria and a testable completion condition.
Module 2: Version control and collaborative development (2 hours)
- Git repositories and history: Git repositories, working changes, commits, branches, and history.
- Review and integration: Pull requests, merges, conflicts, and reverting a change.
- Short-lived branches: Short-lived branches and the cost of delayed integration.
- Code review: Code review for correctness, readability, tests, and scope.
- Test levels: Distinguish unit, integration, system/end-to-end, and acceptance tests for a change.
- Automated and human checks: Automated checks and human review as complementary quality controls.
Practical outcome: Commit a change, review a diff, resolve a small conflict, and run tests.
Module 3: From an integrated change to a maintained release (2 hours)
- Continuous integration: Continuous integration and repeatable build and test steps.
- Delivery and deployment: Compare continuous delivery with continuous deployment and their release decisions.
- Environment purposes: Explain the purposes of development, QA/test, staging, and production environments.
- Environment configuration: Distinguish configuration, secrets, test data, and differences between environments.
- Artifacts and release recovery: Versioned artifacts, promotion, release checks, and rollback limits.
- Operations and maintenance: Logs, monitoring, incident response, fixes, and maintenance feedback.
Practical outcome: Run a small local pipeline and explain a release and recovery path.
Practical exercise
- Take one small change through a prepared repository. Write acceptance criteria and a task plan, create a branch, implement the change, and run tests. Review a separate diff, revise the change, and resolve a controlled conflict. Execute a local build/test pipeline and describe how the same artifact moves through QA, staging, and production with environment-specific configuration. Plan a failed-release response without assuming every database change can be rolled back.
What you will produce
Take a small software change from requirements through version control, review, testing, and a local delivery pipeline.
How the work is checked
- The work plan connects the requirement, tasks, acceptance criteria, and tests.
- Git history and the reviewed diff show a bounded, understandable change.
- The learner identifies a real defect or missing test during review.
- The pipeline fails on a deliberate test failure and passes after correction.
- The release plan distinguishes environments, configuration, promotion, and recovery.
Six guided hours, including demonstrations, practice, feedback, and questions. Breaks and pre-course setup are outside the total. This lifecycle introduction uses one small delivery exercise. Project-management certification, advanced Git administration, production CI/CD platform setup, and cloud operations are outside scope. Environments represent different purposes and controls; teams need not use four separately named deployments. Programming paradigms belong in Programming Language Concepts for AI Engineers. Detailed architecture, design-pattern catalogs, and distributed systems require later specialist work. Lab materials and timing must be prepared and verified before delivery.
When another approach is better
- Use a programming-design course to learn object-oriented and functional approaches.
- Use specialist delivery or cloud training for production CI/CD platform administration.
How we train
Contact us for full course details, including duration, delivery options and lab requirements.
Ask about exercises, instructor feedback and the prior knowledge you need. Tool-specific courses marked provisional may become modules in a broader course.
Discuss your learning goalsRelated Courses
These courses list this course as preparation.