matthewthornton.info

I’m playing with a business idea and I am consequently working on the requirements for the application.  I started out using a program called Virtual Paradigm.  It’s nice.  But not great and certainly not worth the cost of an actual license.  My hypothesis is that I am going to be able to do a much better job by using a wiki to document the requirements.  True, it won’t provide some of the bells and whistles, like being able to create traceability automatically, etc. but it certainly allows for people to quickly read, review, and refine requirements.  During my last semester of classes, I took a course on requirements engineering where we reviewed a number of software requirements development systems.  Sitting in the calm, thoughtful world of academia, they look like a good idea but, in reality, I don’t think it gains people anything.  For example, with the company I work for, they use a glorified document editor to create and track requirements.  I’m pretty well convinced that a wiki is going to be better.  Any thoughts?