DI-SESS-81520B

Instructional Media Design Package

Provides the preparation instructions for the Instructional Media Design Package, which documents the design of courseware, including course content, lesson strategy, and courseware logic flow, for the development and production of training materials.

Approval DateAugust 30, 2001

AMSC NumberN7466

Preparing Activity—

Project Number—

OPRN/AS/PMA205

DTIC ApplicableNo

GIDEP ApplicableNo

Limitation—

Applicable FormsNone

Approval Limitation—

Form Version—

DID Formatfree_text

963C CompliantNo

DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.

Supersedes

DI-ILSS-81520A

—

Description & Purpose

—

Application & Interrelationship

—

Use & Relationship

The Instructional Media Design Package provides the design documentation for the development and production of courseware.

a. This Data Item Description (DID) contains the preparation instructions for the content and format of the Instructional Media Design Package.

b. This DID contains the format, content, and intended use information for the data product resulting from the performance requirements described by 3.2.4 of MIL-PRF-29612B, and is applicable to the acquisition of training data products. Data product performance evaluation criteria are specified in 4.3.4 and 4.3.9 of MIL-PRF-29612B.

c. It is not intended that all the requirements contained herein be applied to every program or program phase. Portions of this DID are subject to deletion tailoring depending upon the program phase in which it is applied in the contract. Any individual data requirement contained in this DID is subject to deletion tailoring.

d. This DID supersedes DI-ILSS-81520A.

Preparation Instructions

1FormatThe format of data contained within this DID is as follows:

1.1Page-based products, for which contractor format is acceptable

1.2Standard digital data in compliance with the contentStandard digital data in compliance with the content and format requirements specified in the DoD Data Architecture (DDA) and the Defense Data Dictionary System (DDDS).

2ContentThe Instructional Media Design Package shall contain the following:

2.1Front matterThe content of front matter shall be in accordance with Appendix A of MIL-PRF-29612B.

2.2Summary description of trainingThe training summary shall provide a brief description of training materials being developed. The summary shall include:

2.2.1Training program title, identifier, and version identifier

2.2.2A brief description of the major topics

2.2.3Number of instructional hours training materials will beNumber of instructional hours training materials will be used.

2.2.4A listing of the methodologies employed in theA listing of the methodologies employed in the design, development, implementation, and presentation of the training program.

2.2.5A listing of the equipment being simulated inA listing of the equipment being simulated in the training program.

2.2.6Location of the training sites

2.2.7Location of the administrative repository for the reportsLocation of the administrative repository for the reports and evaluation materials to include necessary points of contact, addresses, and telephone number(s).

2.2.8Keyword listing

2.2.9A description of the target audience to includeA description of the target audience to include occupational specialty and skill level.

2.2.10Operational equipment designator and nomenclature covered by theOperational equipment designator and nomenclature covered by the training program.

2.2.11Associated course(s) title and identification number

2.2.12Developmental software product name(s), version, vendor name, andDevelopmental software product name(s), version, vendor name, and Government rights code.

2.2.13Operating system name, version, and additional software driversOperating system name, version, and additional software drivers required to operate the training program.

2.2.14Portability standards name and version identifier

2.2.15Delivery system requirements description to include minimum freeDelivery system requirements description to include minimum free system memory, central processing unit type and speed, minimum hard drive storage space, number of disc drives and types, graphics adapter type, and input and output devices.

2.2.16Security requirements code

2.2.17Security classification code and restrictions to distribution code

2.3Courseware design strategyThis data shall provide descriptions of elements required to design the courseware. The data shall also include over-teaching, integrated and isolated practices, front loading, prerequisite skills, combined task practices, media features, branching strategies, learning events, ratio of drill and practice, degree of simulation, and frequency of testing. The required elements shall include:

2.3.1ConventionsThis data shall identify the techniques, practices, principles, or procedures to be used throughout the design and presentation of the module or lesson. Conventions shall define the use of text (e.g., font size, type, color, background, placement), menus, warnings, cautions, procedures, tests, screen direction, placement of cues, touch areas, keys or other input devices, motion, stills, image source, audio configuration, and narration.

2.3.2Course title and descriptionThis data shall provide the title(s) and a brief description of the course(s).

2.3.3Course task dataThe data shall identify the specific tasks being supported and shall include the following:

2.3.3.1Specific tasksThe data shall identify all tasks to be supported by the course and courseware. This information shall be provided as a narrative list and will provide the logical delivery sequence of the course and shall be consecutively numbered.

2.3.3.2Estimated time to completeThe data shall provide an estimated time required for an average trainee to complete each course component.

2.3.3.3RecommendationsThis data shall include the identification of specific technical requirements and source material to enhance the design effort.

2.3.4ReferencesThis data shall include the complete title and number of all reference materials used in course or courseware design.

2.3.5Safety, hazard, or environmental considerationsThis data shall include all safety, hazard, or environmental considerations.

2.3.6Interface design and controlsThis data shall describe interfaces and controls which support the input and pacing of trainee performance. The data to be provided shall include descriptions of the following:

2.3.6.1Practice, remediation or branching as controlled by thePractice, remediation or branching as controlled by the trainee or system instructor.

2.3.6.2Trainee practices (i.e., independent or practice including teamTrainee practices (i.e., independent or practice including team interaction).

2.3.6.3How the system shall be able to varyHow the system shall be able to vary presentation rate to individual trainee ability.

2.3.6.4How the system shall be able to varyHow the system shall be able to vary the sequence and range of presentation based on trainee ability.

2.3.6.5How the system shall allow the instructor toHow the system shall allow the instructor to provide input during training or effect the individual or group performance pace and path.

2.3.6.6How the portability commands and interface mechanisms supportingHow the portability commands and interface mechanisms supporting interface and controls shall be identified.

2.3.7Test design strategyThis data shall provide a description of test scenarios, applying test items, presentation sequence, appropriate learning types and levels, frequency, student interface, remediation options, and performance tracking.

2.3.8Abnormal operating conditions to be simulatedThis data shall provide a description of abnormal operating condition(s) which could affect accomplishment of performance standards.

2.3.9Course overviewThis data shall identify each module or lesson of an instructional unit, and the recommended presentation sequence for all modules or lessons, and any interrelationships.

2.3.10Course scheduleThis data shall include a chart showing the course's daily and weekly schedule, learning objectives, enabling learning objectives, knowledge, skills, attitudes, instructional events, and media selected.

2.3.11Performance tracking control features for instructional mediaThis data shall identify all course control and instructional media control features, their interrelationships, and their respective rationale. It shall include the following performance tracking and support features:

2.3.11.1Trainee data to be collected, (e.g., name, rank,Trainee data to be collected, (e.g., name, rank, social security number, job position, training requirement, address).

2.3.11.2Tracking of individual trainee progress through a course,Tracking of individual trainee progress through a course, (e.g., problem flags, time on task, use of help functions, comments, repetition, etc.).

2.3.11.3Listing of individual and aggregate test scores andListing of individual and aggregate test scores and times.

2.3.11.4Analysis of test items response branching

2.3.11.5Courseware routing (allows for entry, re-entry and instructorCourseware routing (allows for entry, re-entry and instructor intervention).

2.3.11.6Record of courseware and hardware usage by

2.3.11.6.1Student

2.3.11.6.2Instructor

2.3.11.6.3Support personnel

2.3.11.7Schedule of trainees, equipment, ranges, and other resources

2.3.11.8Inventory of course materials (e.g., expendables, ordnance, fuels)

2.3.11.9A description of all management reports to beA description of all management reports to be generated for supervisors and trainees.

2.3.12Course Structure Format (CSF)A description of the CSF hierarchy to include sub-structure, sequencing, global properties, Sharable Content Objects (SCO), external references, and metadata tagging conventions reflect capability for operating and course using the specific Learning Management Systems (LMS).

2.4Lesson strategyThe lesson strategies shall contain the following:

2.4.1Organization and formatThis data shall describe the organization and format of the lesson and segment strategies. It shall list the headers or section designators that are used, explain the meaning of each designator, and describe the type of information that is found under each. A key shall be used to explain the symbology. This explanation shall be supported with one or more illustrative examples. The lesson strategy shall exhibit traceability to the courseware development process and shall include:

2.4.1.1A reference number, a unit number, and lessonA reference number, a unit number, and lesson number referenced from the syllabus.

2.4.1.2A short title description of the subject toA short title description of the subject to be covered. The title shall be taken from the syllabus lesson title.

2.4.1.3A description of the media for each lesson

2.4.1.4A list of Learning Objectives (LOs) covered byA list of Learning Objectives (LOs) covered by each medium.

2.4.1.5A brief overview of the content of theA brief overview of the content of the lesson shall be provided for lesson authors, Subject Matter Experts (SMEs), and students. The overview shall also include an explanation of why the lesson is required, how it is related to previous lessons, and how the lesson fits into the total program.

2.4.2Learning objectivesThe LOs shall describe the type and level of learning required for each LO. Each LO shall have two numbers assigned: (1) a sequence number to indicate its order of presentation and (2) an identification number to indicate its rank in the LO hierarchy.

2.4.3Unit and lesson mapsThe unit map shall contain a flow diagram showing the sequences and relationships among lessons in the instructional unit. The lesson map shall include a flow diagram showing the hierarchical relationships among lesson objectives.

2.4.4Lesson design strategyThe lesson design strategies shall describe decision-making processes and strategies to be used in designing and implementing the presentation of material and testing student mastery of subject matter. Specific strategies shall include an instructional strategy for each lesson-learning phase, methods of interaction, procedures which assure testing at appropriate learning types and levels, and remediation. Segments to be tested shall be identified and the method of testing defined. (Specific emphasis should be placed on the design strategy for developing and implementing the instructional media into the training program and equipment.) Training, learning, and branching strategies shall also be included, when required. All strategies used shall be appropriately labeled and sequenced under the title description. The lesson design strategy shall identify the conventional techniques, practices, principles, or procedures to be used throughout the design and development of the instructional media module or lesson. The following information shall also be provided:

2.4.4.1A statement of what type behavior the studentA statement of what type behavior the student must exhibit in order to master the LO.

2.4.4.2The facts to be memorized, the critical attributesThe facts to be memorized, the critical attributes of a concept, the steps to follow in applying a rule or procedure, or the cause and effect relationship of a principle. Aids shall be included in the instructional content to help the student recall. The strategies data shall list the most common errors made by the student when learning.

2.4.4.3A description of instance production and shall includeA description of instance production and shall include each type of scenario that is to be included in the examples, practice, and test items. A table shall be provided listing the total number of examples, practice and test items that the lesson author must produce for each type of scenario.

2.4.4.4A description of the theoretical basis upon whichA description of the theoretical basis upon which each instructional strategy is employed.

2.4.4.5A description of SCO specifications and metadata taggingA description of SCO specifications and metadata tagging requirements necessary to support courseware object interoperability across platforms and systems, reusability, and Internet protocol compatibility.

2.4.4.6A description of the level of granularity forA description of the level of granularity for the SCO to be applied within the lesson and the rationale for the level of granularity applied.

2.4.4.7A list of the metadata tags required forA list of the metadata tags required for each SCO in final deliverable format (i.e., compressed or uncompressed) as an element of the course or lesson.

2.4.4.8A list of the metadata tags required forA list of the metadata tags required for each original uncompressed format media object.

2.4.5Test itemsThe test items shall include the type of test and the approach for feedback and remediation based on the lesson design strategy. A list of the test items to be used in measuring the student's knowledge shall be provided and include a statement of the minimum acceptable passing criteria for the lesson or segment. A list of examples and practice exercises to be used in support of the instruction shall also be provided.

2.4.6Lesson format guideThe lesson format guide shall contain explanations of how each section of the lesson and segment specifications will be used during lesson authoring. Special instructions or additional information shall be provided to ensure accurate communication of the content for authors and artists. It shall contain a description of the following:

2.4.6.1Text and graphic layout conventions

2.4.6.2Interpretation of lesson strategies

2.4.6.3Data sources for expansion of lesson strategies

2.4.6.4Learning strategy guidelines

2.4.6.5Use of symbology

2.4.6.6Titling

2.4.6.7Figure numbering

2.4.6.8Referencing conventions

2.4.6.9Page numbering

2.4.7Prototype lessonThe prototype lesson shall consist of courseware, to include supporting design and developmental documentation. (This prototype will demonstrate how the format guide is to be used in conjunction with a lesson strategy to produce the required lessons.)

2.4.8Instructional media resource requirementsThe data shall contain a summary of required resources to include:

2.4.8.1An estimate of the visual and audio resources neededAn estimate of the visual and audio resources needed to support the course as follows:

2.4.8.1.1Existing and new resource footage (e.g., video, audio,Existing and new resource footage (e.g., video, audio, film, slides, photographs, graphics, artwork).

2.4.8.1.2Support requirements (e.g., props, equipment, SMEs, military andSupport requirements (e.g., props, equipment, SMEs, military and civilian personnel).

2.4.8.1.3Talent

2.4.8.1.4Field environment, (e.g., ranges, ships)

2.4.8.1.5Studio requirement

2.4.8.1.6Special equipment

2.4.8.1.7Costumes and uniforms

2.4.8.1.8Lighting

2.4.8.1.9Animation rationale, source, and extent of usage

2.4.8.2A list of the material to be presentedA list of the material to be presented during the course.

2.4.8.3A list of any adjunctive materials required toA list of any adjunctive materials required to support the course.

2.4.8.4A description of the types of personnel andA description of the types of personnel and their respective roles and responsibilities for lesson development.

2.5Courseware logic flow diagramsCourseware logic flow diagrams shall include all defined lesson tasks with references, information frame or sequence, decision points, branching options, remediation, and other screen activities. All flow diagram symbols used shall be clearly defined. Flow diagrams shall include:

2.5.1All blocks of instruction and decision points

2.5.2All program paths or branches

2.5.3Video, graphics, and text frames with reference andVideo, graphics, and text frames with reference and sequence numbers.

2.5.4Audio, still frame, and other audio configurations withAudio, still frame, and other audio configurations with reference and sequence numbers.

2.5.5Performance decision notes

2.5.6Processing and design decision information that supports theProcessing and design decision information that supports the remediation, non-scored test items, motion sequences, computer processing, performance update, scored test items, scoring routine, and database search commands to be used.

2.5.7A legend identifying key symbols that connect elementsA legend identifying key symbols that connect elements of the flow diagram.

3Standard digital dataStandard digital data shall be delivered for the Standard Data Elements (SDEs) marked with an "X" in the "Required" box in Table 1.

References

—

Figures

Figure 1. TABLE 1. Standard digital data requirements

Schema v3.0Community-maintained · Verify against ASSIST

Community-maintained — not an official government database.
Verify against ASSIST·GitHub·About·Disclaimer