| Home | About LETSI | Calendar & Events | Join LETSI | Contact LETSI |
| Architecture | Runtime Web Services | Strategic Communications | Technical Roadmap | [Joint CMI Study Group] |
| Content as a Service | Namesets | [LET Activity Description] | Orchestration | SCORM 2.0 |
Domain Enhanced Sequencing
Domain enhanced sequencing and scenario generation in a web based environment
Author: Ohad Bukai, Jacqueline A. Haynes, Thomas Wason, Bob Pokorny
Summary
This paper proposes STENV (Scenario based Training Environment), which is aiming to ease the implementation of "learning by doing" scenario for certain training domains such as aircraft training or medical treatment. STENV has layered architecture consisting of TCA (Technical control of activities), DCA (Domain specific control of activities), and ICA (instructional control of activities). TCA is a technical platform to provide a control mechanism and variable maintenance like current SCORM 2004. ICA provides generic instructional strategies based on pedagogical knowledge. DCA provides domain specific procedures/protocols as well as UI component. Based on this architecture. this paper also proposes outline of implementation consisting of sequencing language, MVC model, and UI definition.
Comments (5)
Aug 19, 2008
Mike Rustici says:
There are some good thoughts in here that make a lot of sense and could add a lo...There are some good thoughts in here that make a lot of sense and could add a lot of value. This vision is probably a good long term goal, but perhaps a bit too ambitious for the next iteration of SCORM. How will we decide how ambitious to be in this next version?
Aug 19, 2008
Tom Wason says:
Agreed that we need to think both long term and short term. It would seem,...Agreed that we need to think both long term and short term. It would seem, as suggested today on the TWG meeting, that we need a development plan. We should also think about the risks and rewards of being or not being ambitious. What does our community need? When do we get to the point of diminishing returns tweaking SCORM 2004?
Sep 08, 2008
Kiyoshi NAKABAYASHI says:
The layered architecture described in this paper separating d...The layered architecture described in this paper separating domain specific knowledge and generic instructional knowledge is quite attractive and worth to be investigated. There are, however, researches in the same line since more than ten years ago. Following references might be relevant:
Ritter, S., Blessing, S. and Wheeler, L. (2003) Authoring tools for component based learning
environments. in Authoring Tools for Advanced Technology Learning Environments,
Murray, T., Blessing, S. and Ainsworth, S. (Eds.), 467-489, Kluwer Academic
Publishers, Dordrecht.
Roschelle, J., Kaput, J., Stroup, W. and Kahn, T.M. (1998) Scalable integration of Educational
Software: Exploring the promise of component architectures. Journal of Interactive Media
in Education, 98(6), 1-31.
Anyway the idea represented in the paper is worth to be discussed as one of the SCORM 2.0 features.
Oct 10, 2008
Jason Haag says:
The "librarian - to - SCORM focus areas" analogy is an excellent one...The "librarian - to - SCORM focus areas" analogy is an excellent one! This paper addresses both pedagogical and technical issues, and points to two critical types of associations that are missing from the current IMS simple sequencing spec in SCORM 2004: instructional segments and domain related segments. The authors also point out some areas that could be better addressed in SCORM such as the following:
This paper proposes an interesting change to the current implementation of sequencing with the introduction of 3 conceptual layers for sequencing: Technical control of activities(TCA), Instructional control of activities (ICA), and Domain specific control of activities(DCA). I believe this paper and the thoughts behind it will be a huge contribution to how we think about and shape sequencing in SCORM 2.0. The concept of abstracting sequencing into these 3 layers makes alot of sense. I also agree w/ seperating the UI and making a seperate UI spec, but I would add that it should address more than just the UI of the sequencing experience. I believe a UI spec should be independent of everything else (content, sequencing, LMS, etc) since the user interface experience impacts everything else. This could lead into other discussions relating to UI as well: Should the UI stand alone from both the LMS and the content?
Oct 11, 2008
Mark Ewer says:
I think that CORE SCORM should focus in on what this paper calls the TCA but do ...I think that CORE SCORM should focus in on what this paper calls the TCA but do it in a way that each user can build on and extend the core features with libraries of domain specific logic. If we combine the thought presented here with the ECMAScript based sequencing paper I submitted I think we create an infrastructure that you can build on to implement DCAs or ICAs.
This is a great paper! Thanks!