Forum Discussion
Calling all Software Simulationists
There are several options here and depending on the stakeholder's requirement I will do one of these.
Option 1. I will build a storyline project on one function. Make sure it works, test and have the stakeholder review and approve. This can now be used as a standalone project. Quick and can be used as a review by learners when needed.
Option 2. Use the above project as a scene and import these slides into a bigger project. I keep it as standalone for changes as needed down the road.
Option 3. Take all my standalone projects and put them in a learning path on the LMS.
A lot depends on your stakeholder's and what they want. In reading your post, I think option 2 will work the best.
Good luck.
Thanks Pete. I appreciate the depth you've gone into here. Cheers.
Steve, I do a lot of software simulation. Unlike most people, I don't use Articulates screen capture. I prefer the way Adobe Captivate captured a slide for every click. Articulate saves short videos and a lot of automatic layers that are not to my preference. So, import an image for every click. I always user workflow scenarios to teach the topic which are in separate scenes. The separate scenes for topics makes it easy to set up the table of contents to allow users to jump to a specific workflow. The separate scenes are all in one big continuous workflow.
To Pete's point, you often don't want a whole section to be a Show Me or Try Me. I always use a Release of Responsibility approach. If something is brand new, the user has helpful boxes so they know exactly where to click. The second topic will build on the first. Only new content will have red boxes. If the user clicks in the wrong spot a hint layer displays. Keep in mind the second scene is doing something new, but there is some overlaying content. I want the user to immediately practice what they learned for a different example and build on it. It forces the learner to stay engaged throughout. It may be a bit more tedious recording my simulation separately, but the end product makes it worth it because the end product acts exactly like the software I'm simulating (except for red boxes and hints if a mistake is made).
Thanks Stephanie. You're not the only one as we use Captivate for the captures. But we may move to SL for that too. Certainly doing the captures in separate SL files before bringing them into what will be the player shell as a separate scene makes sense.
Not sure how easy it is to replace the content. One assumes the Scene stays even with all the slides removed, if deleting old capture and updating with a new one.
Yeah, I mix and match sometimes within the same capture, depending on the situation - some clickables, some carried out with inserted mouse interactions.
The organisation I am in want everything short as possible - probably like everywhere these days - so it's a tightrope on the deliverables.