Source code is design-[ZT]-Agile Software Development pioneer Thesis

This article is a pioneer in Agile Software development. It has never been found in the full text.

Flier's blog: [http://www.blogcn.com/user8/flier_lu/blog/1147695.html] Found on

Special reprinted

Special Instruction: This point of view does not represent my own point of view, but the value of thinking is very creative reference:

Exploy the new way-in software programming ^_^

 

This is an article written by Jack reecves in 1992.

Introduction:

【

So far, I can still remember where I was when I had an epiphany and finally produced the following article. That was the summer of 1986. I served as a temporary consultant at the China Lake Naval Weapons Center in California. During this period, I had the honor to attend a seminar on Ada. During the discussion, an audience raised a representative question: "Are software developers engineers ?" I don't remember the answer at the time, but I still remember that I didn't really answer this question at the time. So I quit the discussion and began to think about how I would answer this question. Now, I cannot be sure why I remembered a paper I had read in datamation magazine almost 10 years ago, but what prompted me to remember was something that was discussed later. This paper explains why engineers must be good writers (I remember this paper is about this problem-I haven't read it for a long time), but the key point I got from this paper is: the author believes that the final result of the engineering process is a document. In other words, engineers produce documents, not physical objects. Others make physical objects according to these documents. As a result, I raised a question in my confusion: "Apart from all documents normally generated by software projects, are there other things that can be considered as real engineering documents ?" My answer is, "Yes, there is such a document, and there is only one source code ."

 

Taking the source code as an engineering document-design-completely subverts my views on my chosen career. It changes the way I view everything. In addition, the more I think about it, the more I think it clarifies the many problems that software projects often encounter. More specifically, I think most people do not understand this different view, or intentionally reject the fact that it is enough to explain many problems. A few years later, I finally had the opportunity to publish my opinion publicly. A paper on Software Design in C ++ journal prompted me to write a letter to the editor about this topic. After several correspondence exchanges, the editor livleen Singh agreed to publish my thoughts on this topic as a paper. The following is the article.

]

-- Unfinished

Due to the long length, please refer to: http://www.blogcn.com/user8/flier_lu/blog/1147695.html