I am in the main sympathetic with this article as in comparing the fields of software architecture and instructional design it seems to reveal the deficiencies of each. Posted as an ITForum discussion paper, it has drawn responses mostly along the lines of assertions that 'instructional design is not just another branch of engineering'. Well of course not, but it's exactly that sort of distance from what software architecture really is that leads the author to suggest something like a merger. I'm not saying that a designer should know what an array pointer is, but they should know what an array is, how it differs from an object, and how you could use an object pointer. No? Or maybe we'll keep instructional design at the level of designing page turners.
Today: 0 Total: 1113 [Direct link] [Share]
