Flexibility and reusability

Nov 24, 2012

Hi All,

I’m about to start a huge eLearning project on air Operation Regulation. Developing will not be an issue, it is the organizing of the modules that will be.

The Air Regulation is a set of paragraphs (300-350) that all deal with Air operations but which are not interlinked with one another.

We are planning to extract more than 1 training from this regulation (approx. 10-15). Each training course will cover a specific aspect of the regulation, this will be done by grouping different paragraphs. This is where the tricky bit is. Some paragraphs can be used in different training modules.

So my idea was to develop the different paragraphs in separate .Storyline files, I might end up with 300-350 storyline files? When a training course is needed I then import All necessary .storyline files into a course .story file that then will be published on our LMS. It gives a lot of flexibility, What do you think of this approach?

I will not be the only developer on this project, so keeping the size of the modules small should prevent us from having to wait on each other…

Thanks

4 Replies
Geert De Rycke

Thanks Phil

I thought of this as well. The issue is that from those 300-350 paragraphs, basically only 8-10% could be put into scenes (20-25).

The rest of the paragraphs are singletons (mostly max 4 to 7 slides would cover them).

Eventually I'll create the real training course by importing the relevant singleton files into appropriate scenes

Once done I'll put on the course cosmetics & navigation

Our team consists of 5 developers, working on the same .story file would be difficult.

All logistics, like, which paragraph will be put in what training course are managed in a matrix in Excel. It has as an advantage that we can quickly identify when a paragraph in a rule has changed, which training courses will be affected.

Cheers

Geert     

This discussion is closed. You can start a new discussion or contact Articulate Support.