Let you know about software development in advance (37): A Preliminary Study of the Development Process

Part 1 software R & D work summary

R & D process

(This article is my thoughts on my work after I arrive at the company for a month. Please read it .)

I have been internship at the company for more than a month. Recently I completed my first formal task. In retrospect, the process was full of setbacks and surprises. Although it is not as smooth as a normal movie, it is also difficult to forget. In this article, I briefly describe the entire process and occasionally express my personal feelings.

The entire process includes six steps shown in step 1.

Figure 1 software development process

 

(1) accept requirements

Generally, for new employees, the project team will not assign too complex tasks, because we are easy to make mistakes when we are not very familiar with them. After all, technology also needs to be accumulated.

What I did this time is to add a few simple new requirements based on the original code. The first thing to do is to accept the new requirement documents sent by the Project Manager. This new requirement is generally obtained from the customer and then transferred to the developer.

For the requirement document, I think it is necessary to clearly describe the problem, otherwise it will be difficult for us to start. Even if it is done, it may not meet the requirements. When there is a new demand, the Project Manager will also take the relevant developers to evaluate the demand, which means to see if the demand can be done, and don't wait until we have spent a lot of effort to find that we can't do it.

The so-called "customer first" means that if the customer has a need, we should try our best to develop products to meet their needs.

 

(2) read the requirement document, detailed documentation, and source code.

After obtaining the requirement document, the next step is to carefully read this document and clarify the cause and effect of the problem.

Some requirements are described very complicated (rather abstract). We can't simply look at the descriptions. At this time, we will look at the detailed design ("details") documentation and source code. The detailed design document was originally written by the developer. Through this document, we can figure out the general process of the program and find the data structures and functions designed to meet the requirements. Of course, the source code is the specific implementation of the requirement, and each requirement will have the corresponding code. As long as we read these programs patiently, we will find their correspondence with the document.

This step is very important for understanding the needs and procedures. We must read it carefully and never take it lightly. Based on my personal experience, if you do not have a good understanding of the requirements, then the probability of errors will be very high.

 

(3) modify or add the corresponding code

After understanding the new requirements and the code, we have to start programming.

Before programming, we should first find out where to modify or add code. In the programming process, we must concentrate on it and check it several more times to prevent mistakes. Errors include not only program syntax errors, but also logical errors.

In a general project, there are a lot of code, and there are thousands or more lines. It may take some time to find a place to change. This requires a person to calm down and be impetuous.

In addition, many new requirements are similar to some previous requirements. We do not need to design data structures and functions from the beginning. We only need to modify some parameters in the previous program blocks. This saves us time and provides a reference for troubleshooting in the future.

The coding stage is the specific implementation of requirements. It can be said that it is the most important part of the work. We must be up to speed and never take it lightly.

 

(4) Test Procedure

Previously, I thought that development engineers only need to write the program and do not need to test it. The Project Manager reminded me that this idea is wrong. As long as the program has been modified, we must test it. Make sure that the code we handed in is completely correct without any bugs.

Before testing code with software, we must read the program several times with our own eyes to find some obvious errors. This is both a work attitude and a good way to correct errors.

Depending on the project, the tool for testing the program is also different. Sometimes, we need to interact with other modules, so we need other developers to cooperate with us for testing.

Before testing, we should at least design test cases in mind to estimate some expected output values. In addition, we need to perform special and important tests on the boundary value. I think this is also the test technique.

 

(5) Write Test Documents and upgrade documents.

After the test is completed, do not submit the code immediately. Remember to write Test Documents and upgrade documents.

How to test the program, then the test document should show this process. We can briefly describe our testing steps and results to prove that we have tested our code in a responsible manner.

As there is a new requirement, it means that the related products have been upgraded. At this time, we need to write the upgrade document. In this document, we need to rewrite the upgrade section, that is, what are new requirements.

As long as we carefully complete coding and understand the program well, writing these documents is fast.

 

(6) Submit Code and related documents

After ensuring that your program is correct, the last step is to submit the modified Code and related documents.

Generally, each project team has a special place to store these items. We only need to submit our results as instructed. Next we will wait for a new version and dedicated testers to test it.

Remind us that after the task is completed, we not only need to submit code, but also many other things. This should be done according to the project requirements. Do not forget to submit something. To ensure that the submission is successful, you can check the request again.

 

The above is the whole step of my work. I think most of the development work is the same, most of which is similar. I have the following feelings when completing the task:

1)Be calm, patient, read the documents and programs carefully, and start programming after understanding them thoroughly. do not modify the program as soon as it comes up..

2)Strictly follow the programming specifications to facilitate the reading and modification of the program. do not define some strange variables. Let people know the approximate meaning of the variables after seeing them..

3)Do not be too confident in everything. After you have done this, let's look back and see what is forgotten and what is wrong with your understanding..

 

As a developer, we must develop good habits and have a good attitude, so that even more difficult problems can be solved.

(My microblogging: http://weibo.com/zhouzxi? Topnav = 1 & WVR = 5, No.: 245924426, welcome !)