Designing a joint program between METU NCC Computer Engineering and DigiPen.
A full joint-program design study between METU NCC Computer Engineering and DigiPen Institute of Technology's Computer Science in Real-Time Interactive Simulation — the program behind DigiPen's reputation in game development. nutshell handled the end-to-end design: course equivalencies, prerequisite resolution, and coverage calculation of the joint diploma against each side's original program.
Joint programs sound great in principle and are punishing in practice. Two curricula, two accreditation contexts, two faculties — and a hundred small decisions about what is genuinely equivalent, what is complementary, and what needs to be rebuilt.
This study focuses on a joint degree between METU Northern Cyprus's Computer Engineering program and DigiPen Institute of Technology's Computer Science in Real-Time Interactive Simulation (RTIS) — the track that has made DigiPen one of the most recognized names in game development education worldwide.
Why this pairing
DigiPen's curriculum is purpose-built for games: real-time rendering, game engine architecture, physics for interactive simulation, gameplay programming, and the full production pipeline behind shipping a playable title. METU NCC brings a strong classical CE foundation — systems, algorithms, mathematics — that pairs naturally with a specialization that is both highly applied and genuinely technical.
The goal was a joint diploma that lets students graduate as credible game-tech engineers without either side giving up what it already does best.
What nutshell handled
We ran the full design loop for the joint program — not just a mapping exercise. Specifically:
- Course equivalencies between METU NCC CE and DigiPen CS-RTIS, drafted automatically on a shared ontology and reviewed by both faculties.
- Prerequisite resolution across institutions — checking that chained prerequisites stay intact when courses come from different programs.
- Coverage calculation of the joint diploma against each of the two original diplomas, so both sides could see exactly what a joint graduate would carry from their side of the program.
- Gap identification — topics the joint program would miss relative to either original, flagged for new courses or mutual prerequisites.
- Draft joint curriculum assembled from existing courses plus the minimum number of new ones needed to close gaps.
Why it matters
Without a shared structural view, joint-program design devolves into catalog wrangling: matching course titles, arguing about credit counts, and hoping the prerequisites don't break. With a shared ontology, the conversation shifts from "is this the same course?" to "does a student who completes this track actually cover the competencies we both care about?"
Detailed coverage charts, the full equivalency table, and the resulting joint-curriculum draft are being finalized with both departments. Full write-up coming — reach out if you'd like the brief early.