Requirements or Prototyping? Yes! (NOT KNOWN IF TALK GIVEN BECAUSE AUTHOR HAS LEFT AT&T)

Much has been written about the best way to develop software applications. But there is no best way. In general, in specific situations some ways are more appropriate than others. In this paper we maintain that both prototyping and requirements are necessary. The top-down vs. bottom-up feud is absurd. Let's return to old time engineering and use the tried-and-true process of synthesis and analysis to solve software engineering problems. Bottom-up is the synthesis.