Some Questions about project development (answer waitu)

Waitu raised several questions on the blog, and many of them answered questions, including me. I think his questions are quite representative, and most people will encounter them, so I once again post my answers here. This is my personal opinion. I don't know what other friends think about these problems? This is his post: http://www.cnblogs.com/waitu/archive/2005/02/01/100214.html

1 Does software engineering mean endless meetings? How can we better arrange tasks for everyone, ensure the progress, and be able to communicate better when they encounter problems?

2. In the middle of development [I am talking about web development], What is the ratio of the changes displayed on the page to the total workload?

3. How detailed is the comment of the program code?

4. How do you communicate with your members as the development team owner?

5. How is the task completed? To what extent is the task completed?

When I first entered the web development portal, I felt that I had not touched on the portal. All of the above questions have been answered. Please kindly advise me !!

1 Does software engineering mean endless meetings? How can we better arrange tasks for everyone, ensure the progress, and be able to communicate better when they encounter problems?



A:

> Software Engineering does not mean endless meetings, but it still needs to be held. If you are a leader, when assigning any tasks, the functions of the entire system should be analyzed at previous meetings. At this time, you only need to give a description with the relevant personnel of the task to confirm some details. Of course, if you have detailed documents, prototype diagrams, and so on, you do not have to interview the relevant personnel. In general, my experience is more realistic. when you encounter difficulties, you certainly need to find the leader. If you feel that this method is painful, it means that you have done a lot of work that you should not do. You should not do too detailed work. Have sufficient time to help the team analyze and resolve (possibly assigned to other personnel for implementation) issues.

2. In the middle of development [I am talking about web development], What is the ratio of the changes displayed on the page to the total workload?



A:

> In the Web development process, excluding the previous analysis and design time, page development accounts for 80%. During this period, new pages account for 60% of page development time, and modifications account for 40%, of course, this is my experience, just an example.

3 stepsTo what extent should the comments of the ordered code be detailed??



A:

> It is difficult to answer this question. As mentioned above, it is easy to understand the intention of your code by providing help from others. The better the code is, the less comments it can be. I personally think that it is unnecessary to describe the basic functions and general implementation algorithms of this page on a page. Each method is described in a simple way. A complex piece of code describes some algorithms.

Please pay attention to the comments and descriptions of the Code! For the same annotations, some of them can be understood at first glance, and some cannot be understood at the same time. A simple example:

Assume that there is a duty module, You need to obtain a duty log pair to take over the shift. The Code may include:

If (ondutylog = NULL)

Return;

Some may note: Check for null values

However, some people may note that they cannot get the duty log or take over the shift.



Both annotations describe code operations. The first is a more general description. I just talked about the code to do. However, the second method directly states what he wants to do and why he wants to do so. One sentence: with the second annotation, other developers will know at a glance how to use the two lines of code and why the author wants to write it like this!

4. How do you communicate with your members as the development team owner?



A:

> For project communication, group meetings and separate communication (interview)

5. How is the task completed? To what extent is the task completed?



A:

> First, check whether the created module implements the task you assign to it. For web development, for example, check whether all the required pages are available, therefore, whether the function operations can be smoothly performed as expected. If you can, it is basically done. Then let's see if there are any obvious bugs. If there are no bugs, they will be completed. If your team is large, this should be done for testers, and vice versa, it is done by leader. After the leader acceptance is completed (by the way, check the code for this function), it can be considered completed, and then handed over to the tester for testing.

In addition, the landlord can use bug management software to record changes and configuration tasks. In fact, task allocation and coordination at the initial stage of development won't cause too many problems. The problem is mainly identified in the current iteration process: After the feedback or test report received by your project is returned, developers need to handle it. At the same time, there may be new feedback, these feedbacks may involve the last feedback and may be being modified according to the room requirements. The feedback may also be that the user overwrites his or her opinion and changes the demand. And so on. These problems are a huge challenge. So the quagmire of projects is often in the later stages. Bug management software can solve most problems.

These are my personal experiences and opinions.

I have the opportunity to continue the discussion, my email: chenweibing@gmail.com

MSN: wishbirds@hotmail.com