Develop+a+JDTA+(with+a+focus+on+the+structure+of+data)?

Information Sheet Develop a JDTA (with a focus on the structure of data)

Introduction: When a needs assessment has indicated a training requirement, the ISD/SAT project planning has been completed, and the instructional system concept is approved, it is time to enter the analysis phase of instructional development. During this phase, instructional developers conduct various forms of analyses such as training situation, occupational, job, mission, and task analyses. These analyses continue through the selection of training tasks. The nature and scope of each ISD/SAT project determines which of the various analyses need to be conducted.

References:

Information: The E2E Process is all about defining the work. JDTA's should always be skill-based or at least based on the Application level or higher of Bloom's Taxonomy. In the JDTA, supporting Knowledge is addressed at the Task level by the KSATR's. Since CPM and AIM Learning Object (LO) Module are based upon the development of performance-based instruction, JDTA's are that foundation. As you move further into the E2E process, other features become available to help build effective training at any required instructional level. Some of these include:
 * CPM Projects - has the ability to change action verbs and the platform (platform, system, sub-system, component and non-equipment) field and add multiple different Content Types.
 * LO Module - Each Content Type is made up of elements, LO Module also has the ability to add additional element types and sub-elements to increase the designer / developers ability to address a wide range of instructional requirements.

NOTE: While you can take NAVEDTRA 130 Task-based items and move them over, we hope after you review the items below, that the risk of just coping data over without performing an analysis will be apparent. CPM/LO work very well if the proper analysis to define the work is done first. Short-cuts or taking an approach of just throwing data at the JDTA using an old 130-style approach normally causes the designer / developer to blame the tool for problems later in development. In all of the NAVEDTRA's, the designer / developers must always start with the highest level of skill and work backwards to ensure required material is being taught and assessed properly.

1. In the below graphics (Figure 1 to Figure 7), if the JDTA was performed correctly, the following items would be different (see explainations next to each Figure 1 to 7) ......
 * The JDTA in CPM would be much more organized, (it might be shorter) and broken down using multiple duties, task, KSATR's, sub-task and steps.
 * The describe action (or any recall / comprehension) verb would almost never be used (name a job that someone "describes" something. They operate, evaluate, interrupt, analyze, estimate, perform, etc.... (just to name a few examples)
 * The JDTA would look like this ...... (not complete example, but a good start to sit down with a Sonar SME to complete) Compare with Figure 1.
 * Duty - Sonar
 * Task - Operate Sonar Equipment - KSATR - Knowledge = Different types of Arrays, Projectors, Hydrophones. Describe SONAR.
 * Sub-task - Operate Transmission Sub-system / Equipment
 * Step - Change to Continuous Wave
 * Step - Change Frequency Modulation
 * Step - Change Frequency Pulse Rate
 * Step - Operate in Single Mode
 * Step - Operate in Multi-beam combinations
 * Step - Operate in Omnidirectional Transmission (ODT)
 * Step - Operate in Passive Mode
 * Step - Operate in Active Mode
 * Sub-task - Operate Reception Equipment
 * Task - Interrupt SONAR Presentations - KSATR - Knowledge = Perform Equations
 * Sub-Task - Determine range
 * Sub-Task - Determine bearing
 * Sub-Task - Determine speed
 * Sub-Task - Interrupt Principle Display Elements

NOTE: When building Learning Objectives (from JDTA) later in CPM Projects you can choose different Content Types (mix different ones together), change Action Verbs and use the Platforms option to address specific systems.

__Below is some examples with explanation of bad JDTA's__














include component="comments" page="page:Develop a JDTA (with a focus on the structure of data)?" limit="10"

include component="navigation"