270 likes | 372 Views
This analysis delves into the challenges encountered during the conversion of Authorware courseware from Boeing, covering icon display, interaction, motion, calculation, and more. The document outlines assumptions, limitations, solutions, and conclusions drawn from the process, showcasing the intricacies involved in such conversions.
E N D
Authorware Conversion: Lessons Learned Fred Banks September 30, 2009 READINESS BEGINS WITH TRAINING
Analysis Sample courseware from Boeing: • F/A-18 (multiple projects) • C-17 • F-22 • Foreign customers • Boeing Commercial Aircraft • Multiple programming styles and versions • Lessons with thousands of icons and libraries
Assumptions • Content will be imported into the ForceTen LCMS • Content will be packaged in ForceTen • Media will be in a central repository • Not everything will convert
Authorware Icons Display Interaction Motion Calculation Erase Map Wait Digital Movie Navigate Sound Framework DVD Decision Knowledge Object
Display • Graphics • Text • Lines/Boxes/Circles • Colors • Modes • Fills/Thickness
Interaction • Limited conversion • Branching to other pages? • Reference page • Most were Hot Spots
Interaction page 2 • No examples of CMI nor question types. • No conversion
Motion • One example found • Not tested
Calculation • Don’t move this graphic • i/o • Calculation • No samples of JavaScript • Can be templated • Not cost effective for automated conversion
Erase • Limited usage • Many references to “external” pages • Conversion possibilities very limited Erase example
BEFORE AFTER
Group • Basis for making an HTML page • All effective lessons use group • Creates many non-display pages • Major decision in determining cost-effectiveness
Wait • Limited use • Can get overly complex in conversion • Another reason why we need an authoring language wait example
BEFORE AFTER
Digital Movie • Only one example found • Bitmap Sequence • Probably requires conversion to another format • Bitmap Sequence, FLC/FLI, Director, Director (protected), MPEG, Video for Windows, Windows Media Player
Navigate • Found in framework icon • No examples found to justify writing a conversion routine • Better to ignore • Gets re-done
Sound • Need to convert to be effective multiple formats • AIFF, MP3, PCM, SWA, VOX, WAV • Found WAV
Framework • Ignored • Gets rebuilt in an LCMS • May be heavily dependant on variables
DVD • No test cases to examine • Outside of “Web”
Decision • Some conversion possible • Can become very complex
Knowledge Object • No samples found • May be easier to provide a template
Other • Transitions • Browser issues • Not a 1 for 1 correspondence Example
Summary of Problems • Duplicate Icon and ID names • Erases outside of current page • Overly large pages • Cryptic code • ~90% used databases • Some used 2 or more types • Custom LMS (written in AW) • Alignment of objective information
Solutions • Redo by hand (i.e. Flash) • Write an interpreter • Requires maintaining Authorware for revisions • Cannot reuse • Authorware Web • Problems in VISTA • Conversion routine • 70% Level 1 and Level 2 • Re-do the remaining 30% • Apply templates
Conclusion • Needs analysis • Conversion of media • No magic bullet • Some won’t convert or isn’t practical. • 100% databased • One giant page