Hla Scorm Prototype

711 views
644 views

Published on

Published in: Education, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
711
On SlideShare
0
From Embeds
0
Number of Embeds
6
Actions
Shares
0
Downloads
12
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • This brief will provide the background for this project, introduce the components that make up the prototype, share some stories about our journey, and show you the final product.
  • Hla Scorm Prototype

    1. 1. HLA/SCORM PROTOTYPE FINAL REPORT
    2. 2. PROJECT REVIEW <ul><li>Background </li></ul><ul><ul><li>5,100 active duty Marine Captains </li></ul></ul><ul><ul><li>Reserve Captains and some SNCOs </li></ul></ul><ul><ul><li>EWS schoolhouse can only accommodate 190 students each year </li></ul></ul><ul><ul><li>Remaining students use Seminar or Individual Guided Study (IGS) distance education program (DEP) </li></ul></ul>
    3. 3. PROJECT GOAL <ul><li>Provide a richer, more robust learning environment to DEP student </li></ul>
    4. 4. PROJECT TEAM <ul><li>Anteon – SCORM 2004 content </li></ul><ul><li>mGen – SCORM 2004 LMS </li></ul><ul><li>MAK Technologies – MAGTF-XXI </li></ul>
    5. 5. PROJECT COMPONENTS <ul><li>SCORM 2004 conformant instruction </li></ul><ul><li>SCORM 2004 conformant LMS </li></ul><ul><li>HLA-compliant MAGTF-XXI simulation </li></ul>
    6. 6. Distance Learning <ul><li>ISD vs. Simulation  ISD and Simulation </li></ul><ul><li>Three SCOs excerpted from the schoolhouse MCPP curriculum </li></ul><ul><li>Practical exercises and Assessments </li></ul><ul><li>Cooperative instruction </li></ul><ul><li>SCORM 2004 conformant </li></ul>
    7. 7. Delivery <ul><li>Simulation data </li></ul><ul><ul><li>Huge volumes of data </li></ul></ul><ul><ul><li>Proprietary encoding </li></ul></ul><ul><li>Runtime data availability to groups of students </li></ul><ul><li>Solution: </li></ul><ul><ul><li>Create a repository location with read/write access for students </li></ul></ul><ul><ul><li>Store the location as a session variable </li></ul></ul>
    8. 8. Simulation <ul><li>HLA-compliant MAGTF-XXI simulation </li></ul><ul><ul><li>Virtual multi-player capability </li></ul></ul><ul><li>Additional requirements: </li></ul><ul><ul><li>Record parameters for game – Host vs. Client </li></ul></ul><ul><ul><li>Transfer/download scenario files </li></ul></ul><ul><ul><li>Launch into a scenario from a web page </li></ul></ul><ul><ul><li>Collect data from game </li></ul></ul><ul><ul><li>Read XML and ‘Save on Exit’ added to MAGTF v2.8 </li></ul></ul>
    9. 9. Achievements <ul><li>Launched simulation in multi-player environment from a SCO </li></ul><ul><li>Captured data from simulation </li></ul><ul><li>Sequenced content </li></ul><ul><li>Demonstrated collaborative training using simulation </li></ul><ul><li>Transferred scenarios for a variety of PEs </li></ul><ul><li>Implemented mGen’s SCORM 2004 LMS with simulation capability </li></ul>
    10. 10. DEMO <ul><li>mGen LMS </li></ul><ul><li>Content </li></ul><ul><li>Simulation </li></ul>
    11. 11. Next steps <ul><li>Develop paper for I/ITSEC 2006 </li></ul><ul><li>Demos </li></ul><ul><ul><li>I/ITSEC 2005 </li></ul></ul><ul><ul><li>Seminar EWS Distance Education Program </li></ul></ul><ul><ul><li>Independent Guided Study </li></ul></ul><ul><li>More research </li></ul><ul><ul><li>Student roles </li></ul></ul><ul><ul><li>Use of AARs </li></ul></ul><ul><ul><li>Upload Log files </li></ul></ul>
    12. 12. Questions / Feedback / Ideas
    13. 13. IMPLEMENTATION PLAN <ul><li>Introduction </li></ul><ul><ul><li>Identification </li></ul></ul><ul><ul><li>System overview </li></ul></ul><ul><ul><li>Document overview </li></ul></ul><ul><li>Applicable Documents </li></ul><ul><li>Version Description </li></ul><ul><ul><li>Installation </li></ul></ul><ul><ul><li>Recommended Environment </li></ul></ul><ul><ul><li>Launching </li></ul></ul>
    14. 14. REVIEW SOW <ul><li>Prototype </li></ul><ul><li>Sharable Content Objects </li></ul><ul><ul><li>Contractor shall repurpose portions of an existing course following the Instructional Systems Design model. Content shall be of sound instructional design and include engaging multimedia. At a minimum, the development of a Sharable Content Object (SCO) that conforms to the specifications of SCORM 1.2 is required. The use of draft SCORM 2004 is encouraged if an LMS can be identified to support it. </li></ul></ul><ul><ul><li>Deliverables: Instructional Design Plan, storyboards, source code and/or files for the instructional content including SCORM content packaging manifest and support files. </li></ul></ul><ul><li>Simulation/Scenario </li></ul><ul><ul><li>Contractor shall develop a scenario that emphasizes learning objectives taught in the SCOs. The scenario shall allow students to practice and apply concepts and processes as an extension of the training. Contractor shall employ an existing credible HLA-compliant simulation asset in the development of this prototype. </li></ul></ul><ul><ul><li>Deliverables: MAGTF-XXI executable with the associated scenario files. </li></ul></ul><ul><li>Learning Management System </li></ul><ul><ul><li>Contractor shall employ an existing Learning Management System (LMS) that minimally conforms to Sharable Content Object Reference Model (SCORM) version 2004 as described in the appropriate documents at www.ADLnet.org. </li></ul></ul><ul><ul><li>Deliverables: Source code and/or files for any middleware or other software specifically developed for demonstration of the prototype. </li></ul></ul>
    15. 15. REVIEW SOW <ul><li>Shared Assets </li></ul><ul><li>Contractor shall design and develop shared assets to facilitate communication between the SCORM and HLA. The shared assets shall be capable of initializing a simulation, launching a scenario, and returning performance criteria on the student. This/these assets shall be capable of receiving and sending data in a format compatible with both HLA and SCORM. </li></ul><ul><li>Deliverables: Launcher and Collector applications and any required meta-data necessary for launching simulations or defining evaluation criteria. </li></ul><ul><li>Implementation Plan </li></ul><ul><li>Contractor shall develop an implementation plan to capture installation instructions, the recommended training environment, and instructions on launching the SCOs within an LMS. </li></ul><ul><li>Deliverable: Implementation Plan </li></ul>
    16. 16. REVIEW SOW <ul><li>Prototype Demonstration </li></ul><ul><li>Contractor shall provide all licenses, software and hardware necessary to establish the final prototype demonstration in the Joint ADL Co-Lab. Contractor shall document the actions and outcomes of the prototype demonstration. </li></ul><ul><li>Deliverable: Meeting minutes within one week of prototype demonstration </li></ul><ul><li>Documentation </li></ul><ul><li>At the conclusion of the HLA/SCORM prototype development, delivery, and testing, a final analysis document shall be provided which captures all relevant processes, decision points, considerations, and conclusions that resulted from this effort. Recommendations and lessons learned will be described. This documentation is intended to provide insight and information to further the process of integrating HLA-compliant simulations with SCORM-conformant courseware. </li></ul><ul><li>Deliverable: Final Technical Report </li></ul>
    17. 17. TECHNICAL REPORT <ul><li>ADL/HLA Integration Research Blueprint </li></ul><ul><ul><li>“ The prospect of integrating ADL SCORM courseware and HLA simulations raises a number of technological, instructional and programmatic issues:” </li></ul></ul><ul><ul><ul><li>Will a simple technical approach work for all cases? </li></ul></ul></ul><ul><ul><ul><li>Can the use case be supported from an instructional perspective without changing the SCORM or HLA specification? </li></ul></ul></ul><ul><ul><ul><li>If specifications changes are required, what are they and how long will they take to vet through the standards communities? </li></ul></ul></ul><ul><ul><ul><li>Are the use cases realistic? </li></ul></ul></ul>
    18. 18. TECHNICAL REPORT <ul><li>Project Summary </li></ul><ul><ul><li>Purpose </li></ul></ul><ul><ul><li>Background </li></ul></ul><ul><li>Prototype Use Case </li></ul><ul><li>Technical Report </li></ul><ul><ul><li>SCORM 2004 Conformant Courseware </li></ul></ul><ul><ul><li>Shared Assets </li></ul></ul><ul><ul><li>Simulation and Scenarios </li></ul></ul><ul><ul><li>SCORM 2004 Learning Management System </li></ul></ul><ul><li>Lessons Learned </li></ul><ul><li>Future activities </li></ul><ul><li>Conclusion </li></ul>
    19. 19. LESSONS LEARNED <ul><li>True R&D has known and unknown schedule risks. </li></ul><ul><li>Stay use case focused </li></ul><ul><ul><li>Use Case needs to be referred at each stage of development. </li></ul></ul><ul><li>Keep the Warfighter in mind </li></ul><ul><ul><li>MAGTF-XXI instruction is a prerequisite to this course. </li></ul></ul><ul><ul><li>The learner environment and target audience must be considered when introducing this technology. </li></ul></ul>
    20. 20. LESSONS LEARNED <ul><li>Minimize collateral impact </li></ul><ul><ul><li>Extending the data model for this project would have reduced the impact of the technical achievements. </li></ul></ul><ul><ul><li>Simulation data requirements need to be analyzed using instructional design methods </li></ul></ul><ul><ul><li>Several group instructional strategies exist. To focus on extending the data model for cooperative-based training only would be too narrow </li></ul></ul>
    21. 21. FAILURES <ul><li>Future Requirement – Uploading the scenario files after each practical exercise or after the COA game </li></ul>
    22. 22. FUTURE <ul><li>Group coordination : </li></ul><ul><li>A future version of the prototype would investigate ways to manage and link the group members in a more coordinated fashion. LMS group assignment, a multi-player lobby, and coordinated launch of a simulation or SCOs would enrich and simplify the distance learning experience. </li></ul><ul><li>There needs to be more work performed in the area of requesting a shared URL for a specific group of learners within a simulation. </li></ul><ul><ul><li>I.E. Request a shared URL repository for. </li></ul></ul><ul><ul><li>Section: HLA Simulation 101 </li></ul></ul><ul><ul><li>Content: Red-Blue Simulation </li></ul></ul><ul><ul><li>Specific Users: Joe, Mary, Larry, Mike </li></ul></ul>
    23. 23. FUTURE <ul><li>Simulation data variables . </li></ul><ul><li>The Launcher and Collector assets could be extended to enable a variable set of objectives and measurements to be sent to the simulation and more detailed assessment data to be returned. </li></ul><ul><li>Extended data model prototype . </li></ul><ul><li>Establishing a prototype environment which included extensions would allow prototype research and development to more quickly discover benefits and limitations. </li></ul>
    24. 24. FUTURE <ul><li>Data model extensions: </li></ul><ul><li>Simulation data . Mapping HLA specifications to instructional design methodologies may be a first step toward a closer linking of the two standards. </li></ul><ul><li>Performance metrics . The SCORM standard needs to have the capability to record performance metrics in a more detailed cross learner nature. SCORM has no support for comparing learner’s performance and content effectiveness with a trending model. </li></ul>
    25. 25. FUTURE <ul><li>Data model extensions: </li></ul><ul><li>Course evaluation . Provide a way to evaluate the learning activity as a whole unit of instruction and supply valuable trending feedback to an evaluator. </li></ul><ul><li>Content evaluation . This cluster could instruct the LMS on what sections of the activity tree will record detailed learner performance information: Pass, Fail, or Score. </li></ul><ul><li>Expected activity data . Provide information about the type of data produced by each activity, i.e. time, score, pass/fail, or none. </li></ul>
    26. 26. FUTURE <ul><li>Data model extensions: </li></ul><ul><li>Extend SCORM Standards by adding API Calls </li></ul><ul><ul><li>The simulation required a repository for runtime data and common data between users. </li></ul></ul><ul><ul><ul><li>New API call to request a unique repository URL based upon “User-Content-Section” of learning </li></ul></ul></ul><ul><ul><ul><li>New API call to request a shared repository URL based upon “Content-Section” of learning </li></ul></ul></ul><ul><ul><ul><li>New API call to request a shared repository URL based upon “Section” of learning </li></ul></ul></ul><ul><li>Server response to the API would create a new folder on the server and with permissions to allow for HTTP – PUT, WEB DAV writes and HTTP GETs to the folder. </li></ul>

    ×