Pure user requirements direction led to SloanSpace v1, which became so entangled in nasty technology hacks that one could no longer install it from scratch (the data-model didn't install).
Untrue. The user requirements for ACES and dotLRN are very similar. Technical management of SloanSpace V1 was lax, leading to a situation where the datamodel was being patched in SQL*Plus with the changes not being reflected in the SQL files. Or so I understand, it was already uninstallable when I was asked to help out.
This might've been in part because so much of it was being done by inexperienced undergraduate students of technology, without proper guidance or direction.
But it sure doesn't have anything to do with user requirements driving specs. It was a failure of the technical people involved in the project (inclusive of technical management).
But don't forget that technologists made it modular enough that others could develop for it.
That's your job. No one is suggesting that the EAB will do your job for you. No one is suggesting they'll do the TAB's job for them.
Both of these are red herring arguments. Substance, please.
