eTMAs in Computing

1. eTMAs in Computing Pete Thomas

2. Overview • Case Study: M301 • Case Study: M883 • Some remarks about the eTMA system • The future? • How did we get to where we are now?

3. M301 • Software Systems and their Development • 60 points • Presented from 2000 to 2007 • 10,000 students and up to 100 tutors • Teaches • Java, Design by Contract • Concurrency, uses simulations in Java • OO Software Development with UML • Class, sequence, activity diagrams • Managing … the Software Development Process • Patterns, architecture, metrics, testing, COCOMO, HCI • Case Study: uses UML and Java

4. M301 Student Activities • Write Java code using JBuilder IDE • Draw UML diagrams using Rational Rose • [Testing using Rational Test] • [Design by Contract with Java] • Unit testing with JUnit • Execute Java simulations and Case Study

5. M301 Assignments • Word document for textual answers • Java files and JBuilder project files • Rational Rose mdl files • Screen dumps from executing Java code

6. Issues for students • Time to learn different systems • Time to use a system – particularly when drawing (it takes longer than a free-hand sketch) • Managing multiple files • Complexity

7. Issues for ALs • Managing multiple files • Context switching between files when marking • Using multiple systems when marking

8. Consequences • A single document (Word) used for communication between student and AL • Students cut and paste from other applications into the Word document • ALs do not normally run applications other than Word

9. M883, Software Requirements for Business Systems • Volere Requirements Process • Requirements gathering tool • Uses a Java application to produce e-Snow Cards • Exports in a form that can be handled by eTMA system • But Tutors still have to run the application to read and mark the output • VLE for access to online facilities • eTMA system • Forum • Quizzes • Wiki for collaborative activities

10. M883 (2006 to present) • Still the same issues:- • Multiple independent software applications • Learning overhead for students and ALs • Multiple independent files • Managing files (where is anything?) • Swapping between systems (time) • Same solution: • Use single Word document, and • Cut and paste from the different applications

11. Other behaviours • In the late 1990s we looked at AL marking habits • Many ALs provided more feedback using eTMAs than previously on paper • We provided more materials for use by ALs (to cut and paste into student documents) • We still have some ALs who do not use the (e)TMA system effectively

12. eTMA System • The eTMA tool is essentially a file manager with the capability of recording marks and comments • The file handler tool is separate from the Word processor used to capture TMA answers

13. The Future? • The eTMA filer integrated with the word processor. • An assessment software environment in which the eTMA filer, word processor and additional software applications are integrated (what a VLE is for?)

14. The Past (10 years ago) • The original eTMA system was first used in 1996 when the Computing Department offered M252 as an online course, MZX252

17. The Old Tutor Tool • Integrated into Word through macros • Provided pop-ups for marking actions • Placed (part-)marks onto the student’s document • Copied (automatically) to the PT3 document (part of the integrated document).

19. So, what’s wrong with Integration? • The development cost • The maintenance cost • The reliance on third-party software (MS Word)