Reeves multimedia design model: Difference between revisions
m (using an external editor) |
m (→References) |
||
(6 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
== Definition == | == Definition == | ||
The '''Reeves Multimedia Design Model'' is a typical [[instructional systems design]] (ISD) model for education and training. It includes four major functions: 1) analysis, 2) design, 3) production, and 4) evaluation, i.e. a typical variant of [[ADDIE]]. Each | The '''Reeves Multimedia Design Model'' is a typical [[instructional systems design]] (ISD) model for education and training. It includes four major functions: 1) analysis, 2) design, 3) production, and 4) evaluation, i.e. a typical variant of [[ADDIE]]. Each phase implies a set specific activities performed by a set of team members and that will lead to certain products. | ||
See also: [[multimedia]], [[multimedia animation]], [[interactive multimedia]], etc. | |||
== The Model == | == The Model == | ||
Disclaimer: This model seems to have been published by Thomas Reeves some now dead Georgia Tech Web Site. Since [[User:DSchneider|DSchneider]] found the model ((c) Reeves, 1994) on an other Georgia Tech site, we assume that Thomas Reeves is the author of it. However, we do not claim that this is what T. Reeves believes to be the best design method. We are not even sure that Reeves is Thomas Reeves :) | Disclaimer: This model seems to have been published by Thomas Reeves on some now dead Georgia Tech Web Site. Since [[User:DSchneider|DSchneider]] found the model ((c) Reeves, 1994) on an [http://www.ceismc.gatech.edu/MM_Tools/MMDM.html other Georgia Tech site], we assume that Thomas Reeves is the author of it. However, we do not claim that this is what T. Reeves believes to be the best design method. We are not even sure that Reeves is Thomas Reeves :) | ||
<table border="1"> <tr> <td><b>Process</b></td> | <table border="1"> <tr> <td><b>Process</b></td> | ||
<td> <span style="font-weight: bold;">Team</span></td> | <td> <span style="font-weight: bold;">Team members</span></td> | ||
<td> <b> | <td> <b>Products</b></td> | ||
</tr> | </tr> | ||
<tr><th colspan="3" rowspan="1">Analysis phase</th> | <tr><th colspan="3" rowspan="1">Analysis phase</th></tr> | ||
</tr> | <tr> | ||
<tr | <td> | ||
< | * Conducting Needs Assessment | ||
* Preparing Audience Assessment | |||
* Specifying Content and Objectives | |||
* Selecting Authoring Systems | |||
* Selecting Delivery Systems | |||
* Planning Project | |||
* Planning Evaluation Strategies | |||
</td> | |||
<td> | <td> | ||
* Project Manager | |||
* Subject Matter Expert(s) | |||
* Instructional Designer(s) | |||
* Project Evaluator(s) | |||
* Programmer(s) | |||
</td> | |||
<td> | |||
* Needs Assessment Report | |||
<td> | * Learner Profile | ||
* Content Outline | |||
* Learning Hierarchy | |||
* Instructional Objectives | |||
* Authoring System Specs. | |||
* Delivery System Specs. | |||
* PERT Chart | |||
* Project Timetable | |||
* Evaluation Plan | |||
</td> | |||
</tr> | </tr> | ||
<tr><th colspan="3" rowspan="1">Design phase</th> </tr> | <tr><th colspan="3" rowspan="1">Design phase</th> </tr> | ||
<tr><td> Creating | <tr> | ||
<td> | |||
* Creating Treatment Specifications | |||
* Specifying Instructional Interactions | |||
* Screen Design | |||
* Flow charting | |||
* Prototyping | |||
* Writing Scripts Specifications | |||
* Formatting Screens | |||
<td> | * Conducting Formative Reviews | ||
</td> | |||
<td> | |||
* Project Manager | |||
* Subject Matter Expert(s) | |||
* Instructional Designer(s) | |||
* Project Evaluator(s) | |||
* Programmer(s) | |||
* Graphic Artist(s) | |||
* Video Producer(s) | |||
</td> | |||
<td> | |||
* Treatment Description | |||
* Instructional Archetypes | |||
* Flowcharts | |||
* Scripts | |||
* Format Sheets | |||
< | * Interactive Multimedia (IMM) Prototypes | ||
* Improvement Specifications | |||
</td> | |||
</tr> | </tr> | ||
<tr><th colspan="3" rowspan="1">Production phase</th> | <tr><th colspan="3" rowspan="1">Production phase</th></tr> | ||
<tr> | |||
<tr><td> Authoring Interactions | <td> | ||
* Authoring Interactions | |||
* Creating Graphics | |||
* Preparing Adjunct Materials | |||
* Conducting Preproduction | |||
* Conducting Production | |||
* Conducting Postproduction | |||
* Mastering Optical Media | |||
* Integrating Optical Media and Authoring Code | |||
<td> | </td> | ||
<td> | |||
* Project Manager | |||
* Subject Matter Expert(s) | |||
* Instructional Designer(s) | |||
* Project Evaluator(s) | |||
* Programmer(s) | |||
* Graphic Artist(s) | |||
* Video Producer(s) | |||
* Video Editor(s) | |||
* Talent | |||
</td> | |||
<td> | |||
* Interactive Code | |||
* Graphics | |||
* Adjunct Materials | |||
* Program Documentation | |||
* Shot Lists | |||
* Video/Film | |||
* Audio | |||
* Edited Video Masters | |||
<td> | * Videodisc/CD-ROM | ||
* IMM Program | |||
</td> | |||
</tr> | </tr> | ||
<tr><th colspan="3" rowspan="1">Evaluation phase</th> </tr> | <tr><th colspan="3" rowspan="1">Evaluation phase</th> </tr> | ||
<tr | <tr> | ||
< | <td> | ||
* Documenting Project | |||
* Testing IMM | |||
* Validating IMM | |||
* Conducting Impact Evaluation | |||
< | </td> | ||
<td> | |||
* Project Manager | |||
* Subject Matter Expert(s) | |||
* Instructional Designer(s) | |||
* Project Evaluator(s) | |||
* Programmer(s) | |||
</td> | |||
<td> | <td> | ||
* Project Documentation | |||
* Functionally Valid IMM | |||
* Instructionally Valid IMM | |||
* Formative Evaluation Report | |||
* Effectiveness Eval.Report | |||
* Impact Evaluation Report | |||
</td> | |||
</tr> | </tr> | ||
</table> | </table> | ||
== Critique and discussion == | == Critique and discussion == | ||
As presented, this model | As presented, this model could be interpreted as a linear "waterfall" model. However, you should, before implementing it, think about important "milestones" that should lead to inspection of what has been done, what needs to be changed, etc. and include revision loops (at least at the end of each phase). [[User:DSchneider|DSchneider]] therefore thinks that this is rather a "checklist", i.e. a components model. | ||
In [[User:DSchneider|DSchneider]]'s opinion, such design methods are very well suited for lower designs that are concerned by lower [[learning level]]s. | In [[User:DSchneider|DSchneider]]'s opinion, such design methods are very well suited for lower designs that are concerned by lower [[learning level]]s. | ||
Line 168: | Line 145: | ||
{{quotation | The objective based design tradition presumes that knowledge exists in its perfect form in the world outside the user and that each user possesses a more or less perfect understanding of that perfect form Pedagogic practises based on this view often incorporate behavioural learning theory whereby learning was viewed as primarily dependent upon the arrangement of stimuli and the reinforcement provided for various responses. Most computer based training has been designed from such a behaviourist perspective. Reeves (1992) observes that generally these instructional technologies have had disappointing results. "Although there is some evidence that these programs are effective for learning concepts and procedural knowledge, their efficacy in the development of the higher order learning required in most education and many training contexts has been limited".}} (Litchfield, 1994). | {{quotation | The objective based design tradition presumes that knowledge exists in its perfect form in the world outside the user and that each user possesses a more or less perfect understanding of that perfect form Pedagogic practises based on this view often incorporate behavioural learning theory whereby learning was viewed as primarily dependent upon the arrangement of stimuli and the reinforcement provided for various responses. Most computer based training has been designed from such a behaviourist perspective. Reeves (1992) observes that generally these instructional technologies have had disappointing results. "Although there is some evidence that these programs are effective for learning concepts and procedural knowledge, their efficacy in the development of the higher order learning required in most education and many training contexts has been limited".}} (Litchfield, 1994). | ||
On a side note, Reeves is today rather known for eclectic views, e.g. | On a side note, Thomas Reeves is today rather known for eclectic views, e.g. search this Wiki for "Reeves". | ||
== Links == | == Links == | ||
Line 181: | Line 158: | ||
== References == | == References == | ||
Litchfield, A. (1994). Interface communication management: A user centred multimedia design model. In C. McBeath and R. Atkinson (Eds), Proceedings of the Second International Interactive Multimedia Symposium, 298-303. Perth, Western Australia, 23-28 January. Promaco Conventions. http://www.aset.org.au/confs/iims/1994/km/litchfield.html | * Litchfield, A. (1994). Interface communication management: A user centred multimedia design model. In C. McBeath and R. Atkinson (Eds), Proceedings of the Second International Interactive Multimedia Symposium, 298-303. Perth, Western Australia, 23-28 January. Promaco Conventions. http://www.aset.org.au/confs/iims/1994/km/litchfield.html | ||
Reeves, T. C. (1992). Research foundations for interactive multimedia. In Promaco Conventions (Ed.), Proceedings of the International Interactive Multimedia Symposium, 177-190. Perth, Western Australia, 27-31 January. Promaco Conventions. [http://www.aset.org.au/confs/iims/1992/reeves.html] | * Reeves, T. C. (1992). Research foundations for interactive multimedia. In Promaco Conventions (Ed.), Proceedings of the International Interactive Multimedia Symposium, 177-190. Perth, Western Australia, 27-31 January. Promaco Conventions. [http://www.aset.org.au/confs/iims/1992/reeves.html] | ||
[[Category: Instructional design | [[Category: Design methodologies]] | ||
[[Category:Instructional design methods]] |
Latest revision as of 14:30, 29 September 2006
Definition
The 'Reeves Multimedia Design Model is a typical instructional systems design (ISD) model for education and training. It includes four major functions: 1) analysis, 2) design, 3) production, and 4) evaluation, i.e. a typical variant of ADDIE. Each phase implies a set specific activities performed by a set of team members and that will lead to certain products.
See also: multimedia, multimedia animation, interactive multimedia, etc.
The Model
Disclaimer: This model seems to have been published by Thomas Reeves on some now dead Georgia Tech Web Site. Since DSchneider found the model ((c) Reeves, 1994) on an other Georgia Tech site, we assume that Thomas Reeves is the author of it. However, we do not claim that this is what T. Reeves believes to be the best design method. We are not even sure that Reeves is Thomas Reeves :)
Process | Team members | Products |
Analysis phase | ||
---|---|---|
|
|
|
Design phase | ||
|
|
|
Production phase | ||
|
|
|
Evaluation phase | ||
|
|
|
Critique and discussion
As presented, this model could be interpreted as a linear "waterfall" model. However, you should, before implementing it, think about important "milestones" that should lead to inspection of what has been done, what needs to be changed, etc. and include revision loops (at least at the end of each phase). DSchneider therefore thinks that this is rather a "checklist", i.e. a components model.
In DSchneider's opinion, such design methods are very well suited for lower designs that are concerned by lower learning levels.
“The objective based design tradition presumes that knowledge exists in its perfect form in the world outside the user and that each user possesses a more or less perfect understanding of that perfect form Pedagogic practises based on this view often incorporate behavioural learning theory whereby learning was viewed as primarily dependent upon the arrangement of stimuli and the reinforcement provided for various responses. Most computer based training has been designed from such a behaviourist perspective. Reeves (1992) observes that generally these instructional technologies have had disappointing results. "Although there is some evidence that these programs are effective for learning concepts and procedural knowledge, their efficacy in the development of the higher order learning required in most education and many training contexts has been limited".” (Litchfield, 1994).
On a side note, Thomas Reeves is today rather known for eclectic views, e.g. search this Wiki for "Reeves".
Links
The model presented here can be found (at least) on these web sites:
- Original dead link: http://mime1.marc.gatech.edu/MM_Tools/MMDM.html
References
- Litchfield, A. (1994). Interface communication management: A user centred multimedia design model. In C. McBeath and R. Atkinson (Eds), Proceedings of the Second International Interactive Multimedia Symposium, 298-303. Perth, Western Australia, 23-28 January. Promaco Conventions. http://www.aset.org.au/confs/iims/1994/km/litchfield.html
- Reeves, T. C. (1992). Research foundations for interactive multimedia. In Promaco Conventions (Ed.), Proceedings of the International Interactive Multimedia Symposium, 177-190. Perth, Western Australia, 27-31 January. Promaco Conventions. [1]