Most people have a strong interested in software. After graduation, they have entered the company, and started the programmer's career. At that time, we were obsessed with "Daquan", "Cheats", and only code in his heart. When I saw a row of boring code became an apparatus who was able to call, it became a beautiful table on the screen, turned into a beautiful music, accomplishing a sense of accomplishment. I feel that I am also an excellent programmer.
In the user's computer room, I have a BUG that works in software in the software room, and has become a qualifications that can boast. One day before five years ago, I came to Huawei after a lot of code and less proud of the proud document. Here are more young people, I have a fish to get water, you can give full play to your own imagination.
It is still the code, still rushing down the inspiration of a slightly longitudinally on the paper (we call it a document), still endlessly and bug struggle. When one day, a new colleague took the documentation with my name, carefully asked me, I found that I didn't know it. I am a little frustrating, then look at the code, find some of the inspirations recorded on the documentation. I didn't know how the new colleague felt, but I started from then, as I realized what. Now, there are many things that are time.
At the end of last year, the company sent me to India to engage in project development, learning India's software development management methods. A long-lost impulse rises in the bottom of the heart. India, I have been going twice, although it is a horse, but the impression is still relatively profound. I exchanged in the process of visiting India, and they were confident in words. They give me a test environment that is doing software, give me the unit test documentation they write. When I see a software module's unit test case has more than three hundred pages, I feel that my heart is very heavy.
When I step forward on this land, I saw the familiar people, bright eyes, mild smiles, wearing, winding, electric motorcycles, young people in university campus, hands holding a book. .
I also saw my project manager, a child, thin young man, is said that I have just been working back from the United States, I have worked five or six years. I am very happy to hear my heart, this time I have to learn two hands.
The time of demand analysis is one month, the project manager and us (actually represent the customer) discuss the content in Proposal, and determine that each item is needed. Then he roughly divided the module and started to enter the planned learning phase. Everyone should write the film in the learning phase, explain the other people, unconsciously, all people of the project team have a whole solution to the project.
He also arranged some training, such as the software development model of their company, the definition of each role in the project group, and the timely training in time, as long as there is a need in the project team, he always invites QA or related people, training very profession. After the demand analysis is completed, a four0-page document is submitted. When I saw that I wrote in this English document, my feelings are very complicated, some joy, but more It is bitter, how did I have never doing this need for analysis? During my writing documents, QA has trained us about SRS writing template. Later, I still didn't worry, let them write a piece of experience, we wrote it again. Although this SRS is more written, the style is consistent, the content is detailed. What is more valuable is, until the end, this demand analysis has not been changed, so that we have no chance to take the requirements of their needs.
Demand analysis is the first phase of the project, and the development time of the second phase should be determined based on the results of the demand analysis. When the other party's leader (equivalent to the overall team leader of our business) is discussed with our discussion, they have listed the prediction of the number of lines of the code to each module, there may be risk. According to their company's productivity - 300 rows / month, he has drawn a few weeks of the second phase of the project. We have proposed objection: 1) The company is very urgent; 2) Is 300 lines per month; 3) We also have downloaded source code reference. He explained that 300 rows / monthly month is the experience data that enables projects to meet their quality standards, considering that there is an active code reference, productivity cannot exceed 350 rows / month. When he asked our company's productivity, my head turned three circles, I didn't dare to say, about six or seven hundred lines. He was silent for a while, and then said that our plan is based on the quality of guarantee. I think you go to India to develop software. First, it should be the quality assurance of our Indian company. I know that you don't lack software developers, why don't you choose to download software? In a few words, my pain, now the brethren in the country is still running around the products that download software transplantation! Subsequent development activities are in an orderly manner, and we are old and true. System test plan, use case, summary design, integrated test plan, use case, detailed design, unit test plan, use case, code, unit test, integrated test, system test. A complete V model development process, each of which has a REVIEW. When we didn't understand some of the design methods, the project manager sent us related information. I don't know what he thinks, some basic analysis, design method is ten years, or even twenty years ago. In the software engineering book, India's professional personnel are compulsory. And in addition to the code of some specific protocols, we seem to have nothing to know. I feel some shy, Into the city to go straight, I found out the book he opened to me, lying on the bed at night, study carefully, I seem to have encountered a good teacher who can give me a guided teacher who can give me guidance. India has now formed a strong learning atmosphere. After I came back, more than 700 books were also promoted, and these books teach us how to develop software with engineering methods, which is the information necessary to read by software engineers.
Our project manager's plan control has strong program control, when there is anything affected by the project plan, if the person resigns, the laboratory moves, a module is not allowed (this module is our forecast), he always takes The necessary measures, reduce post-extension, adjust the plan. Just beginning, we have a little opinion to the coffee in the next day, 4 o'clock in the afternoon, and later followed it. It turns out that the communication when drinking coffee is very rich, from the project management to the design method, from the development of technology The customs of the customs, all incompetence, understanding our mutual understanding, is very helpful to the atmosphere of the team. The QA of our project also appeared in front of us when appropriate, and we only have some sense of sensibility to her work. Every time she takes the meeting, she often holds a check list, my item manager prepares the corresponding information, answers some questions, she hooks, or writes the explanation of the project manager. When she is training us, she is also very patient, reflecting a good professionalism, I still miss her help.
