The TRY system -or- how to avoid testing student programs
SIGCSE '89 Proceedings of the twentieth SIGCSE technical symposium on Computer science education
A software infrastructure to support introductory computer science courses
SIGCSE '96 Proceedings of the twenty-seventh SIGCSE technical symposium on Computer science education
Laboratory-style teaching of computer science
SIGCSE '90 Proceedings of the twenty-first SIGCSE technical symposium on Computer science education
Document Formatting Systems: Survey, Concepts, and Issues
ACM Computing Surveys (CSUR)
DocBook: The Definitive Guide with CD-ROM
DocBook: The Definitive Guide with CD-ROM
The effect of closed labs in computer science I: an assessment
Journal of Computing Sciences in Colleges
| Hi-index | 0.00 |
Well-designed laboratory experiments in computer science take experience and hard work. Unfortunately, deploying these labs is also a lot of work. Web pages or hard copies of instructions must be set up, grading guidelines and scoring sheets need to be created, etc. Later, if the lab changes or is redeployed in another course, many of these artifacts must be individually edited. This paper presents one approach to simplifying laboratory artifact production. The approach is based on the idea that all files, configurations, scripts, etc. should be generated from a small set of non-redundant documents that can easily be modified.