Terms and Conditions
Agreement
By enrolling in and participating in this course you agree to abide by the terms described on this page. Read them before your first class.
Participation
Lectures follow an active learning format — pre-reading is expected. Each class session assumes you have read the assigned material in advance and are ready to discuss, question, and apply it.
| Expectation | Details |
|---|---|
| Pre-reading | Review assigned sections before each class |
| Engagement | Ask questions, participate in discussions, help peers |
| Lab sessions | Bring a laptop with the development environment configured (see Prerequisites) |
Academic Integrity
Plagiarism
Submitting someone else's work — whether from a peer, a public repository, or an AI tool — as your own is plagiarism and results in a zero for the activity. Repeated violations are referred to the university's academic integrity committee.
What constitutes plagiarism in this course:
- Copying code, text, or diagrams from another student's submission (even with minor modifications)
- Submitting output from an AI tool without understanding, editing, and crediting it
- Reusing your own work from a previous course edition without disclosure
- Copying from a public GitHub repository without attribution
What is not plagiarism:
- Using official documentation, Stack Overflow, and tutorials — provided they are cited
- Using AI tools as a learning aid — provided you follow the AI policy
- Discussing design approaches with classmates before implementing independently
Deliverable Format
All deliverables must be published on GitHub Pages.
No other format is accepted. A delivery template is provided: documentation template
Requirements for every submission:
| Requirement | Standard |
|---|---|
| Hosting | GitHub Pages — public repository |
| Theme | MkDocs Material |
| Repository name | Professional and descriptive (e.g., platform, cloud-native-ecommerce) |
| Git authorship | Commits must be linked to GitHub accounts (git config user.email) |
| Language | English |
Deadlines
Deadlines are not extended.
Late submissions receive a grade of zero, with no exceptions. Plan around this: start early, push incremental progress, and do not wait for a "finished" version before your first commit.
If a technical failure on the submission platform occurs (not on your side), contact the instructor immediately with evidence — before the deadline, not after.
Individual Activities
Individual activities include quizzes, microservice exercises, and other tasks assigned to each student personally.
- Work must be completed independently. Discussion of concepts with peers is permitted; sharing code or answers is not.
- Quizzes are open-book but not open-peer. You may consult notes and documentation; you may not discuss with classmates during the quiz window.
- Re-grading requests must be submitted within 5 business days of the grade being posted. Requests must identify the specific item contested and the justification; general "I deserve more points" requests are not considered.
Team Project
Team projects simulate a real engineering team delivering a cloud-native platform over a semester.
Group formation deadline
Groups must be registered by the date specified in the course overview. After that date, unregistered students are assigned to groups by the instructor.
Rules:
- Teams have 2 to 3 members. Solo submissions are not accepted.
- All members receive the same grade. There is no individual adjustment within the team unless a member is found not to have contributed (see below).
- Contribution must be visible in git history. A team member with zero commits to the repository at delivery time may receive a reduced or zero grade, regardless of what teammates report.
- Code must live in the team's repository. Do not use a personal fork as the delivery repository.
Code of conduct within the team
Teams are expected to divide work equitably and communicate proactively. If a team member is not contributing, notify the instructor early — not on delivery week. Late complaints about team dynamics after submission do not change grades retroactively.
Communication
| Channel | Use | Response time |
|---|---|---|
| Office hours | Design questions, architectural doubts, grade disputes | During the session |
| GitHub Issues on the course repo | Content errors, broken links, unclear instructions | Best-effort |
| Personal/administrative matters only | 2 business days |
Do not send solutions or code by email asking for a grade review. Use office hours.
Code of Conduct
This course covers professional-grade engineering practice. The same standards apply to how we treat each other.
- Critique ideas, not people. Disagreement about technical choices is healthy; personal attacks are not.
- Do not share another student's work, environment credentials, or AWS account details outside the team.
- Treat all participants — students, assistants, instructor — with respect in all channels (classroom, GitHub, messaging apps).
Violations of this code of conduct are reported to the institution's student conduct office.
Changes to These Terms
The instructor reserves the right to update these terms during the semester. Changes are announced in class and reflected here with a revision date. Substantial changes affecting grading will not be applied retroactively.
Last updated: 2026.