Do you do a requirements analysis on projects before the actual development gets started?
I once had a position developing medical equipment for numerous clients. companies would come in and ask for a device to be made, and the company I worked for had to figure out how to make the device.
One time a product came in and it was complicated, lot's of features, and future upgradability. As usual, I started the project with a requirements analysis following the MilSpec standard for designing, which I adopted as a personal guideline for engineering. Management pulled me aside and literally said I am not to use any development procedure; that I should get right down to designing each device with no plan. So, I did, and it took an incredible amount of time to finish. Later, the company's design practice was audited and they had to follow ISO standards afterward. Management again pulled me aside and said I have to follow a design practice standard.
Anyway, I find that the most important step in product development is requirement's analysis. I followed MilSpec, others follow ISO. What I want to know is, is there software out there that will help get this particular step under control without the user having to memorize too many standards and practices? Or tools that will help engineers figure out what may have to be done if requirement X, Y, and Z need to be met?
Cabe
