A project development process (personal opinion + Software Engineering)

I haven't updated my blog for a long time, and I have always wanted to write something. However, when I got back to my place, my mind became lazy and I don't like it. In addition, this time is busy, my mood is also complicated, so I have never updated my blog.

Today is Sunday. I think about my previous work and thought about it for a while. Let's make a summary of my work during this time, because, on Friday, our demand was slightly changed, so I didn't know how to do it, and the customer's demand was very intelligent. The web page implementation may not be able to achieve it, but the customer thinks it can be implemented, so as a newbie in the software industry, I will give me a project, how will I complete it, those who like laruence can give me comments. Do not spray water. I have written articles like this before, but I just want to give it a rough description, this blog I want to imitate how I will complete after receiving a project. I like laruence to give comments. Because it is a software development process, I will attach the software development process drawings here:

　　　　

The previously written website is:

Http://www.cnblogs.com/hanyinglong/archive/2012/11/12/2766769.html

Http://www.cnblogs.com/hanyinglong/archive/2012/07/13/2589927.html

Next, let me take a detailed look at my process. For example, the boss now gives us a project. There are six members in our project team, developers, and artists. How can I do this, I still need to add my own ideas based on the eight processes in the software life cycle.

(1) first, I will organize our project team to discuss the feasibility analysis of this project, that is, the opinions of everyone on this project and whether it can be realized, that is, the feasibility study of the software life cycle. Of course, if the leader can take over the task, of course we know that we should be able to win the project. After this step is complete, we will confirm that we can develop this project, and then we will implement the second step.

(2) Step 2: I think we should start to contact the customer to understand what the customer really needs. At this time, I think we should go to at least two people with development experience when we contact the customer, because when a customer says what they need, they should be able to fully understand what the customer needs. after their first talk, their general needs will be ready in their minds, at this time, they will need to convert these requirements into text to be displayed in word or text processing software. At this stage, I think the preliminary design of art and database should also be carried out, after converting the requirement into text, we will confirm with the customer whether the information is developed in this way. After another discussion with the user, we will modify the requirement again, in this way, I feel that the interaction with the customer is almost the same. At this time, our artist can design several pages to let the user have a look, provide comments, and then modify them, this completes the second step.

(3) when the second step is completed, the next step is the outline design and detailed design in the software design lifecycle, but I find that many project teams do not pay much attention to this, when Step 2 is completed, the code is directly carried out. I personally think that although this is relatively fast in the early stage, it can reflect the importance of this piece when there is a Bug in the later stage of the project, so I suggest you design the project here. I think you should know the meaning of the Outline Design and the detailed design. If you do not know it, leave a message for me, or Baidu will find it clearly, so that we can complete step 3.

(4) When we complete step 3, I think our database design should also be completed. If not, let it be quickly completed or we can help him complete it, at this time, it is the world of our developers. We need to work with us and sort out none of the modules. We often encounter this phenomenon in projects, and a module has a problem, forced many programmers to stop their work and wait. This is a common phenomenon. How can we solve this problem? I personally think that when we code, our developers should communicate with each other more, and emergency solutions are very important, so that we can reduce this phenomenon. For our programmers, bugs will always exist. Remember that we have seen such a passage "the famous Microsoft, was there a time when no patch was released for three consecutive months? The answer is: Never ". At this time, our developers and the US work together to complete our coding stage. At this time, our project will be tested.

(5) testing: a good project must be able to withstand testing by testers. There are many testing methods, such as black box, white box, on-site, and off-site. I do not know much about testing, therefore, we do not know how testers perform tests. After we test our project, we hand it over to users for use. After using the project, we feel that the test is complete, after we complete the test, we need to write some help documents and other records, so that our early software testing is complete, of course, we may also perform tests later, because it is impossible for us to develop a perfect project at once, so that we can complete Step 5.

(6) In Step 6, we will begin to prepare for Software Delivery. In fact, this stage is very important because it is in contact with users, when our software testing completes our software testing and meets the requirements, our software developers should submit the developed products, user manuals, how to use and other things required by the customer, and then release the customer's product online, this phase is complete.

(7) finally, after the user has accepted the project, a project of our project team will be completed, and only the maintenance work will be completed later. At this time, we will celebrate the celebration of the project organization, this is a project bonus.

Finally, I would like to thank you for your reading. I hope you can give me some suggestions. The website development process is just a simple development process, I didn't want to write this blog. I just mentioned that our project needs changed a little on Friday, so I wrote this blog as a souvenir.

Motto: Believe in yourself, you are the next winner

Kencery