First off, I have to address something I didn’t pick up on until this morning – last week was one year of Terminology Tuesday posts. Sure, I didn’t hit every single Tuesday as I had intended, but there have been 52 terms discussed (53 today), and that’s just bananas!
This week, I wanted to talk a bit about the concept of reusability in e-learning, and perhaps veer from the traditional concept discussion that’s often related to SCORM.
Reusability in E-Learning
When I think about reusability in e-learning, I think about objects and content that can be reused in a variety of contexts. Developers often run into this when working on large projects or in industries that involve trade-specific courseware development. My first experience with reusable assets was working with clients in the Defence sector. Often times we were working on projects for the same aircraft (although perhaps several years between projects), and it became quickly beneficial. For instance, one client had provided us with a 3D model of the aircraft, whereas another client several years later did not have access to this same model. We were able to reuse the initial model to suit the needs of the new project. Reusability also came in handy when developing component installation courses and then removal courses (we simply had to reverse the interaction, but could use the same objects).
Being mindful of reusability is critical as it can save you time and money in the long run. Reusing previously established assets (for the same client, of course – in the Defence sector example, the end client was the same, whereas the contractor may have been different, so the end client ‘owned’ all of the assets) will reduce the amount of development various departments and/or individuals have to spend.
Best practices for reusability might include creating your own content repository and defining a file naming convention that will make it easy for you to find what you’re looking for. If you’re extra savvy, you can create a coded database, but that might require a lot more effort than you have time for.
If you work in a specific authoring tool, it may save you time on a new project to have a repository of developed themes and/or interactions; this can help shave time off in the initial prototyping phase, and provides you with an arsenal of ideas for what you might be able to do from a design perspective, and can prove invaluable if design is not your forte.
Leave a Reply