ADDIE

I was first introduced to ADDIE in INST 4300 a couple of years ago. I feel like IDT is a little behind the software design profession in constructing and implementing models for design. ADDIE reminds me a lot of the "Waterfall" method of the 70's with the project cascading from one phase to the next. I was encouraged by some of the slide presentaions in the Course Documents folder that stated that design must be an iterative process.

The diagram above is one I created for INST 4300. I called it "Agile ADDIE" to connect ADDIE with the new agile design models that are becoming popular in IT development. It shows the process incorporating a spiral model with multiple passes through Analysis, Design, Development, Implementation, and Evaluation which are referred to as "Activities". These activities are all part of each step in the process. The bars across the top and bottom are borrowed from the Rational Unified Process (RUP). The green bar indicates that there are two phases -- the Enginerring Phase in which the framework or architecture for the product is identified and tested. RUP is an "architecture first" methodology. Within the Engineering Phase are two stages -- Inception and Elaboration. The result of the Inception stage is the "Idea", shown on the blue bar below the spiral. Out of the Elaboration stage comes the "Architecture" -- that is the hardware and software "platform" for the product.

The Production Phase is not started until the Architecture has been tested and shown to be able to support the product. The product of the Construction stage is a "Pilot" which is tested by users to insure its functionality and compliance with requirements (objectives). Then comes the Implementation stage when the full product with training materials, manuals, and all pieces of the product are delivered.