11 Sep 2011, 07:15
Generic-user-small

Huzaifa (1 post)

I have been reading about different software methodologies. Every method has a design phase to some extent more or less.

I am not clear on what do we mean by designing? Does this mean writing your thought process on how you will code the feature? Or it is a way of saying what you have coded or will code.

The point where I am most confused is the real world, which is different than putting your thoughts in documents and saying it will work. Since coding details can change, I don’t know what’s the point of having a design before coding.

15 Oct 2011, 17:27
Djb_picture_pragsmall

Donald J. Bailey (2 posts)

A design is a description of what you intend to do with enough detail in it to get a useful review. It is created with less effort than is needed to create the actual code. The purpose is to eliminate problems and make choices cheaply. Each design method has an opinion about what information to record.

I have not read the book, but I have been writing programs for 38 years.

  You must be logged in to comment