Why we are bother implementing the SDLC methodologies ? It costs time, energy, money, and of course brain memory ;-)
Any SDLC methodology has its own steps, but all of them make sure that every step has been done accurately. (OMG... very tired doing all of them)
Last time i thought that we don't have to make a "blue print" of all the system we will built. But i do agree that documentation is an important thing. Coz documentation can make us easier to track-back to our system. But making blue-prints ???
Many textbooks said that we can predict the system will be succeeded or not, from its blue-print, before the system has been built.
(psstt... I still sceptic on this statement.. I feel that making plans, analysis, designs is a boring activity)
Maybe it caused by my lack of skill on programming. When designing an information system, you must have very good understanding on any programming language, algorithms, program flows, etc.
Hope someday I will be used to make the blueprint-proposal....before I screwed up the system.. LOL
