Sequence five exercise types around automatic segmenting, from note taking to translation¶
Strategy · All strategies
Evidence · no claims cited
Description¶
The article describes a working sequence of exercises built on automatically segmented sound: note taking (the "content appropriation" phase), a written open-answer question linked to the sequence, transcription of a passage (or gap-filling, though a transcript on paper proved as effective since the point is to understand why a word was misunderstood), automatic repetition using the default recordable answering time span, and a translation exercise with an answering zone. "Most teachers use this model even if gap-filling or multiple-choice questions are also possible."
Design Implications¶
Context¶
Requirements¶
- An answering text zone linked to the sequence; written answers are immediately recorded on the server for instant retrieval and analysis by the teacher.
Constraints¶
- The repetition task is not so easy for the learner, who must discriminate, understand, remember and pronounce words in a limited time.
Target Learners¶
- Language students working individually or in small groups in a networked lab
Target Learning Goals¶
- Listening comprehension, transcription, pronunciation, and written/oral production
Related Strategies¶
Examples¶
-
Key Sources¶
- Toma, Tony. (2000). Real-Time Courseware Design: The LAVAC Video Sequencer. https://eric.ed.gov/?id=ED444508
Page metadata
| Field | Value |
|---|---|
type |
strategy |
id |
five-exercise-sequence-around-segmenting |
title |
Sequence five exercise types around automatic segmenting, from note taking to translation |
description |
The article describes a working sequence of exercises built on automatically segmented sound: note taking (the "content appropriation" phase), a written open-answer question linked to the sequence, transcription of a... |
status |
review |
generated |
by process:wiki-ingest on 2026-10-02 |
trust |
unverified — no one has confirmed this page's content |
sources |
1 — toma-2000 |
Frontmatter is the page's machine-readable record — see the Schema & Guide.