Pain points in quality and progress in software development

Pain points in quality and progress in software development

 

In software development,Quality is very important(Everyone knows this estimate.)But in many cases, the quality does not seem to be guaranteed (based on the Progress pressure ). Then, it's messy....I think most people have experienced this situation.

 

"High quality and high reputation software started in a good analysis and design stage, and was not completed by testing and patching later"

 

Let me describe the areas that will affect quality in the following phases:

LAnalysis and Design Phase

LSchedule

LDevelopment Phase

 

I. Analysis and Design Phase

How can we complete this step? To obtain the real needs of users and consider the potential changes, I think these two points can basically ensure the high quality of the analysis and design stages. HerePMIt must take a lot of effort. Because the "requirements that may lead to changes" here requires good business domain knowledgePMWe have to do our homework in this industry. Haha, aboutPMI am not very clear about the work part...

 

Ii. Planning

The chaos mentioned above is often due to time issues. So I think we also need to make a lot of effort here.---The listed plans need to be detailed, there is no need for steps, and the time is almost enough. Of course, what should I do if the upper-level requirement must be completed at a certain time? The project owner needs to raise an objection to the superior to protect the team.

 

 

Iii. Development Stage

When iterative development is adopted, some functions are often developed first, followedQATest the completed functions. If there is a problem with the quality of development, such as many low-level errors, or unstableProgramToQATest,QAAfter reading it, I don't even want to see it ).QAIf the test fails, the developer must modify it again. Therefore, the time will be greatly wasted Based on the quality level! There are many reasons for poor development quality. For example, subjective unit tests are not performed, and objective unit tests are not performed due to tight schedule.QA

1.Subjective unit tests are not performed.

A)This is either because developers do not know what unit testing is (it is estimated that not many people are responsible for this)

B)Or do not transition to trust your programBug

I.You only need to remind me of this.

C)Performance of inactive work

I.Please note this! Dangerous

2.Objective unit tests are not performed due to tight schedule

A)One is that there is a problem with the original plan.

I.In my opinion, we can only use those who plan the plan to consider the details, and the requirements should be prior to the plan.90%Clear (don't know90%Is it too high?...)

B)One is that the technologies used need to tackle the problem

I.The technical R & D department has to hurry up, and the internal losses of the R & D department have to be solved.

C)One is that there is a problem with the old requirements, which leads to a large amount of non-development time in the development phase and consumes the time that should have been developed.

I.There is a problem with requirement acquisition, or the analysis is not detailed enough, it may be because the analysis is not detailed enough, and there are still many things to take for granted, there is no analysis to the point where it can be handed over to developers (this is a challenge !)

D)There is alsoA + B + CHaha (most of them)

I.Amen. solve the above problems one by one...

 

 

 

The above is my personal opinion. Please give me more advice.