|
||
|
|
||
| CODE REPOSITORY | TUTORIALS | GLOSSARY | WHITE PAPERS | GUIDELINES | ||
![]() Using SCOs Advantage: Get to concentrate on instructional design instead of content development Saves time and money by cutting down on content development Disadvantage: Content in repository might be out of date Need more descriptive metadata Type- fact, concept, procedure, rules, principles, etc. Other: Need more descriptive metadata: -Online form -Help function -Generates file -Validates -Shows errors and references Creating SCOs Get team together FIRST – Instructional designer, TPOCS, SMES, project manager, programmers, graphic artists etc. Decompose content to form SCOs and make reusable: SCO titles -Relevant to SCO -Contain Learning objective Use templates to create SCOs Create relevant file names: -7-10 characters -no numbers -limit extension to 3 characters (htm. Rather than html) Create reusable SCOs for repositories along with transition SCOs that are not reusable Transition SCOs can contain raw media graphics that can be put in the repository submitted by: Dr. Ed Jones |
||
|
|