To be perfectly honest, the system has great potential. Some of that potential is wasted, however, in bureaucratic befuddlement. For instance, why does the eDoc need a description? The amount of training needed on Kuali could be enormous if it gets to be too large and byzantine. However, this is mitigated somewhat by its open attitude towards developers. Indeed, there is even a developer training section on the website which links to multiple pages which can teach users the ins-and-outs of Kuali. This system could theoretically save a lot of money on administrative costs, as its nature, free and open source, would mean that it could be tailored to fit the needs of that organization. Perhaps that is what is most exciting about this project: the novel approach. Instead of integrating...

The swamp that software can so easily become will, theoretically at least, be drained.
If this is the future of software then a few potential problems could arise. Specifically, individual companies modifying a software for their needs, the supposed advantage of a technology like Kuali, can be its downfall. A company could change the program so much that it would run counter to its original intent, eventually becoming useless to the company and drawing the ire of stock owners.

Works Cited

[Illustration]. (2010). Driver's Manual.

Test drives of kuali system. (2010). Retrieved from http://kuali.org/test-drives