Skip to main content

Course Requirements

Before adopting EduIDE for a course, a few conditions should be true.

Good prerequisites​

  • the course has a defined toolchain
  • exercise environments can be standardized
  • browser-based development is acceptable for the course format
  • staff are willing to work with a managed shared environment
  • the course team can run a realistic pilot before broad rollout

Artemis​

If the course already uses Artemis, or is evaluating Artemis seriously, that is a good fit for EduIDE.

The reason is not only organizational alignment. EduIDE integrates well with Artemis through the Scorpio extension, which makes the overall workflow more coherent than combining Artemis with a disconnected IDE setup.

This does not automatically mean the course should adopt EduIDE, but it does mean the platform fit is usually stronger in Artemis-centered teaching environments than in unrelated LMS setups.

Questions instructors should answer​

  • Which languages and tools are required?
  • Which exercises need persistence between sessions?
  • How important is local IDE freedom?
  • Do students need access to capabilities that a managed environment may restrict?
  • Is the course willing to adapt some workflows to gain consistency?