Grading Rubric

Prerequisites:

Availability: Project is online / available through app store / available through expo
Stability: project is fully functional, no errors, no dead links, no missing assets in normal usage
Integrity: project contains only meaningful content (text + images), no „Lorem Ipsum“ or “fill in later”
Scope: size of the project is appropriate for ECTS and team size
Security: project is secure, no trivial problems like SQL Injection, XSS, missing Authorization, (see OWASP)
Feedback: Evidence of incorporating critique from coaching sessions.
Legal: Imprint, GDPR, transparency obligations in Article 50 of the EU AI Act are met (if applicable)
A technical aspect of the project was presented as a talk during WebDevMeetup on June 2nd (or other event)

Aspect	Sufficient	good	excellent
UX	The interface is functional and aligns with the core concept. MVP user flows are implemented with consistent UI. Feedback is provided during interactions using comprehensible UI copy.
Accessible WCAG Level A.	The project offers a seamless journey, addressing user flows beyond the "happy path." State-of-the-art patterns and consistent visual storytelling - through transitions and animations - enhance the experience. Coherent guidance and refined copywriting assist the user in achieving specific objectives.	The system proactively anticipates user intent and gracefully handles edge cases or errors. It demonstrates sophisticated polish through a cohesive design system. Micro-copy and -interactions are in line with the product's overall character and support the construction of a cohesive mental model of the app's structure.
Code Quality + Git	Hosted on GitLab; complete commit history; consistent use of feature branches merged into the main branch, no secrets in code, .gitignore.	Systematic use of GitLab Merge Requests and peer code reviews. Linters / Code Formatters enforced through commit hooks.	Well chosen conventions (commits/naming) were followed; consistent application of "Definition of Ready" and "Definition of Done". Red-Green-Refactor cycle visible in git history.
Testing	Implementation of fundamental unit and system tests, core business logic is covered by unit tests.	Defined testing strategy appropriate to scale; Proactive risk-based testing prioritized by feature risk levels.	Comprehensive coverage (edge cases, performance, security); active feedback loops for continuous process improvement.
Continuous Delivery	Automated Build: Basic GitLab pipeline triggered by commits to ensure code compiles and builds without errors.	Full Pipeline: Automated build, testing, and deployment to staging or production environments within GitLab.	Containerisation / Infrastructure as Code used.
Demo and Presentation	During the "Creative Technologies Showcase" the project was demoed. The technical talk showed some aspect of the project.	The Project was tested with users before or during "Create Technologies Showcase". The technical talk successfully highlighted the achievements of the project team.	The Project was tested under realistic conditions / with the appropriate users before or during "Creative Technologies Showcase". The technical talk offered a deep dive into a current topic, while also being approachable for beginners in web development.