Backward Compatibility of customer artifacts
Text/HTML
Backward Compatibility of customer artifacts
| Startdate |
Around summer of 2010 |
| Company name |
Cannibal Game Studios |
| Internship name |
Backward Compatibility of customer artifacts |
| Description |
Users of our custom middleware solutions use that middleware to create their own artifacts. When a new version of the middleware is released, there exists a possibility that compatibility with current artifacts will be broken.
How do we ensure that we cause no harm to the end-users artifacts when we make changes to our components and framework? In other words: how can we (automatically) transform the end-user artifacts so that he experiences no errors (no syntactical incompatibility) and have them retains its meaning (no semantic incompatibility)?
|
| Internship period |
~9 months |
| Number of days/week |
4-5 |
| Internship type |
MSc / Graduation |
| Preferred faculty intern |
EEMCS, or you will need serious Computer Science knowledge |
| Contact information |
Cannibal Game Studios
Jeroen Dobbe | COO
jobs (atDOMAIN) cannibalgamestudios.com
TU Delft
Andy Zaidman | SERG
a.e.zaidman (atDOMAIN) tudelft.nl
(replace "atDOMAIN" -- added to mislead web spiders)
|