Sunday, July 24, 2005

Analysis & Design Factor In Software Development

During early acedamic days in university, we all (me and all the persons whom I know) used to start developing the project without the necessary analysis and design. The thing that we have in our mind in those days were that we would waste our time if we don't start the development as early as possible. With the passage of time, we studied various courses of core computer sciences including the course of software engineering. In software engineering course, we studied various models of software development. These models have their own merits and de-merits but the main emphasis of all the models is that do the necessary analysis and desing first before starting development because it is very easy and time effective to fix the minor errors but very difficult and time consuming to almost re-code all the project. Our early concept of wasting time seems incorrect and rightly so. I myself really try mylevel best to adopt the increamental model of software development in my last two term projects and successful to a certain level. Without the necessary analysis and design, start of writing code seems feasible for a student project to some extent but quite infeasible for a professional level project where quality and time is an important factor. Just consider the scenario that a developer is developing ASP pages referring from FS. After few days, to implement a certain functionality not mentioned in FS, he has to develop his own understanding first and then re-think whole things so to avoid errors. The most worst case would be resulted if after unit testing, he has been asked to exclude that additional functionality. This all would result if analysis and desing wasn't conducted completely. At professional level, it should be avoided not only to increase the quality but also the productivity and throughput of the developers.

No comments: