Drawbacks of Ignoring the Future
Many believe formal requirements analysis and system design are the unavoidable evil conducted solely for giving some eye-services to those guys in the suits who only use Word. Also, many think testing should be not much more than some not-so-skilled programmers clicking here and there on the day before shipping. And the worst, sometimes this is the reality.
Though lots of people like talking about following methodologies in software development, only a few of them understands: a methodology is a series of transformations helping to turn a vision into reality using best practices, and software engineering tools play the roles of the drawing board and the measure.
Creating brief requirements specifications and software design diagrams in Excel or Word would only be time-wasting if requirements or design conditions would never change. But hell, they do! And this is the precious point where Office-based analysts and engineers fall into fatal trouble: it would take ages to find what to modify in the documents and it would take some more ages to redraw all the diagrams with Word’s drawing tools.
Create static content, develop free-form requirements and draw your diagrams using drawing tools, and you’ll soon find yourself in dead-end.