E-Learning Development Project Lifecycle 1: Introduction
In 2009, I wrote frequently and at length about the “twin pillars” of e-learning, that is,
learning theory and content development, bridged as it were, by instructional design (ID).
I also discussed open source and free-to-use applications for learning content development. In my first series of articles in 2010, I will focus on using these strands to actually create courseware in an open environment.
Now read on…
As you know if you’re a regular reader, I set myself the challenge of compiling a set of tools that enable learning professionals to undertake their courseware and content development activities according my Six Principles of Open E-Learning Environments:
1. Open source or free-to-use (libre or gratis)
2. Fit for purpose
3. Have utility
4. A genuine alternative to a commercially available application
5. Platform/OS-independent
6. Not a hosted service provided by a third-party vendor
The key to developing courseware in an open environment is to use a production model that liberates instructional design and content authoring from your final media outputs. In my view, this means taking a primarily, but not exclusively, XML-based approach to your e-learning development environment. The toolkit – categorized by function – is composed of:
- Instructional & Content Design Tools
- Content & Media Creation and Integration: OSS Tools
- Media Creation and Integration: Free-to-use Proprietary Tools
- Content Delivery Platform
- Content Packaging Tools
So strap in: we begin Next Time!
–
January 07 2010 03:30 pm | e-learning
Ken Allan on 07 Jan 2010 at 10:32 pm #
Kia ora e Michael!
Kia hari te tau hou!
I like what you are saying here. Many genuine alternatives to commercially available applications are already showing up. We need to keep driving these and supporting them.
Catchya later
Michael Hanley on 11 Jan 2010 at 12:25 pm #
We do, Ken. Also, some OSS tools are as goods as, or even better than, their commercially-available equivalents. I think that it’s important to combat the perception that OSS apps are in some way “difficult” to install and use (who wouldn’t be scared off the first time they see a message like “Install Binary from tar.gz” for example).
If neophytes can move past the sometimes initially steep learning curve associated with OSS programs, they usually find them very powerful, adaptable and satisfying tools.
–