Reflection on the software development process-from Requirement Analysis to final software development

I saw a very interesting image on a blog of a technical expert two years ago. Unfortunately, I forgot to save it, but I still remember the artistic conception. Today I found in another blog: http: // http://blog.csdn.net/blueluhan/archive/2008/08/08/2787277.aspx that the author uses a text image to describe the picture I have been keeping in mind, so I took a picture of Google and found a similar image. Close up this blog and archive my memories.

 

Demand analysis phase: How the writer wrote it

According to the customer's description, our requirement analysts provide such a requirement report;

 

System design phase: How the shop built it

According to the requirement report, our system analyst designed the entire system in this way;

 

Data Structure Design Stage: How the crew set it up

According to the design of the system analyst, the data structure designer can store, read, and manage data in this way;

 

Code writing stage: What the designer suggested

Based on the design documents and problems encountered in actual development, our smart programmers finally developed the beta version;

 

System test phase: how the director used it

In Beta system testing, a series of problems are exposed. The software can be used normally only according to the logic of programmers;

 

User Acceptance phase: What the producer wanted

After the system test is completed and the finished product is delivered to the user, what the user actually wants is...

 

 

The larger the software project, the more people participate, the higher the chance of failure. From the analysis on the cause of the failure in the tower of Babylon, I learned that communication between people is costly, and errors will definitely be added to this process. The more communication links, the larger the error introduced.

 

So how can we reduce the error? The "on-site customer" advocated in Agile Software development seems to be a good solution. However, in some projects, it is difficult for you to find a field customer who can fully understand the customer's needs and have enough time to deal with developers' inquiries. In this case, I think the only solution is to reduce the link.

 

 

 

Bingo: Find the source image (see the electronic version of Zhou aimin's "Avenue to simplicity)