Course Policies

Professional conduct

Software engineering is collaborative. Students are expected to communicate respectfully, make work visible, review peers constructively, and raise risks early rather than hiding them.

Academic integrity

Unless an activity explicitly allows collaboration, submitted work should represent the student's own understanding. Reusing code, reports, diagrams, or generated text without attribution or without understanding the result undermines the purpose of the course.

AI-assisted tools

AI tools may be useful for brainstorming, explanation, test generation, code review assistance, and documentation. Their use does not transfer responsibility away from the student.

When AI assistance is permitted, students should:

• Verify generated code and technical claims.
• Be able to explain submitted artifacts.
• Test generated changes like any other untrusted contribution.
• Avoid submitting sensitive data or credentials to external services.
• Disclose substantial AI assistance when requested by the instructor.

Generated is not verified

A plausible-looking answer, patch, test, requirement, or architecture diagram is not evidence of correctness.

Repository hygiene

Never commit passwords, API keys, private keys, access tokens, or confidential datasets. Use .gitignore, environment variables, and secret-management mechanisms.

Late work and attendance

Add the official semester-specific late policy, attendance rules, and exception procedure here.

Team contribution

Project teams should distribute work fairly and record contributions through repository evidence: issues, commits, pull requests, reviews, documentation, tests, and presentations. Commit counts alone are not a meaningful measure of contribution.