Yes, I do know of the Engineering process, but what I meant by "No Right Way" was that the way for Team X won't always work for Team Y, sorry I didn't clarify. Also, using the established Engineering process won't always work.
Quote:
|
then there is nothing to decide or vote on - the DATA DRIVES your design - the DATA tells you what will give you the most bang for the buck, what the most important function is, the second most, the 3rd most...
|
I do understand this concept, but it doesn't always work right. The most 'bang for your buck' relies on being able to do the 'big bang' effieciantly and effectivly. Have a huge stack and being able to reach KotH was the 1-2 Punch to a win. But was nearly impossible.
The step after compiling the data is to see what is feasible. Because you really can't get the Home Run bot (Master of all aspects), you do have to vote on which is easier to do effectively.