DI-MISC-81457A

Lesson Strategy Report

The Lesson Strategy Report describes the instructional strategies, subject matter content, instructional materials formats, and other guidance for authoring and producing lesson training materials, and is used to guide lesson design.

Approval DateSeptember 27, 2007

AMSC NumberF9009

Preparing Activity—

Project Number—

OPR11

DTIC ApplicableNo

GIDEP ApplicableNo

Limitation—

Applicable Forms—

Approval Limitation—

Form Version—

DID Formatdd_form_1664

963C CompliantNo

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

Supersedes

DI-MISC-81457

DI-MISC-81458DI-MISC-81456DI-MISC-81459DI-ILSS-80569

Description & Purpose

—

Application & Interrelationship

—

Use & Relationship

The Lesson Strategy Report describes the instructional strategies, subject matter content, instructional materials formats, and other guidance for authoring and producing the training materials for each lesson. It is used to guide the design of lessons and to prepare the Instructor Planning Document and the Student Guide.

a. This Data Item Description (DID) is applicable to all contracts requiring courseware development. It is used in conjunction with DI-MISC-81458, Instructor Planning Document; DI-MISC-81456, Student Guide; DI-MISC-81459, Syllabus; and DI-ILSS-80569, Objectives and Media Analysis Report.

b. This DID contains the format, content, and intended use information for the data deliverable resulting from the work task described in the contract.

c. DI-MISC-81457A supersedes DI-MISC-81457.

Preparation Instructions

1Reference documents.The applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions, shall be as cited in the contract.

2Format.The Lesson Strategy Report shall be in the contractor's format.

3Content.The Lesson Strategy Report shall include the following sections:

3.1Introduction section.This section shall provide a brief description of the purpose and expected application of the Lesson Strategy Report.

3.2Description of the lesson strategies.This section describes the lesson strategies for all instruction included in the course syllabus. Lesson strategies should ensure traceability to the training requirements. Air Force Manual (AFMAN) 36-2234 should be used for guidance. Each lesson strategy shall include:

3.2.1Cover sheet.This page shall include the title, classification, signatures of the author and approving authority, and date.

3.2.2Lesson strategy organization and format.This section shall describe the organization and format of the lesson and segment strategies. It shall list the headers or section designators that are used, explain what each one means, 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:

3.2.2.1Lesson reference number.The lesson strategy shall consist of a reference number, a unit, and lesson number referenced item from the syllabus.

3.2.2.2Lesson title.The lesson strategy shall have a short title description of the subject to be covered that is taken from the syllabus lesson title.

3.2.2.3Lesson media.The medium or media shall be identified for each lesson. For lessons with multiple media, objectives for each medium shall be indicated.

3.2.2.4Lesson overview.A brief overview of the content of the lesson shall be provided for lesson authors, subject matter experts (SMEs), and students. Included should be an explanation of why the lesson is required, how it is related to previous lessons, and how it fits into the total program.

3.2.3Learning objectives.This section shall describe the type of learning required for each lesson objective and learning event. A strategy for each lesson, learning event, activity, and testing procedure shall be provided. Each objective should 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 objectives hierarchy.

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

3.2.5Lesson design strategy.This section 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 methods of interaction, testing, and remediation. Segments to be tested shall be identified and the method of testing defined. Specific emphasis shall be placed on the design strategy for developing and implementing the interactive courseware (ICW) into the training program and equipment. Training, learning and branching strategies shall also be included, when required. A section parts used shall be appropriately labeled and sequenced under the section part title, e.g., percentage of drill and practice, demonstration, and simulation. The lesson design strategy shall identify the conventional techniques, practices, principles, or procedures to be used throughout the design and development of the ICW module and lesson. The following information shall also be provided:

3.2.5.1Type of behavior.A statement of what the student must do in order to show mastery of the objective, e.g., remember, use aided, or use unaided.

3.2.5.2Generalities.This section shall include the 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 remember and use the generality. This section shall list the most commonly made student errors when learning the generality or test items.

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

3.2.6Test items.This section 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 of the generality 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 of the generality shall also be provided.

3.2.7Lesson format guide.This section shall contain explanations of how each section of the lesson and segment specifications shall 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 on the following items:

3.2.7.1Text and graphic layout conventions.

3.2.7.2Interpretation of lesson strategy sections.

3.2.7.3Data sources for expansion of lesson strategy sections.

3.2.7.4Learning strategy guidelines.

3.2.7.5Use of symbology.

3.2.7.6Titling information

3.2.7.7Figure numbering.

3.2.7.8Referencing conventions.

3.2.7.9Page numbering.

3.2.8Prototype lesson.This section shall consist of a prototype lesson to demonstrate how the format guide is to be used in conjunction with a lesson strategy to produce authored lessons. A complete lesson strategy and resulting prototype lesson shall conform to the lesson format guide.

3.2.9Resource requirements.The section shall contain a summary of resource requirements. Included in this discussion shall be a description of the types of personnel and their respective roles and responsibilities for lesson strategy development.

References

—

Schema v3.0Community-maintained · Verify against ASSIST

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