Introduction, thousands of miles
I remember the middle school, I have learned the "persuasion" inside, there are two sentences inside: "If you don't take the road, you will not have a small stream." The truth is actually very simple, no one can understand, but Just like all common sense, everyone understands its truth, but seriously, people who do things in accordance with usual truth, always talk, (I am also the same ^ _ ^), most people always know what he know, then But do what he did, so people who succeeded were always so small, and those who fail to fail were always so much, and the world always balanced.
But I really want to do practical things, and do a good job, it is generally true. In the case of the school, I watched the software engineering book in the library. Looking at it, I always felt like a boot, and I didn't understand how to engineered the entire software project. From all major websites, IT media has also told me that there seems that China's software does not rely on what software projects, extremely said that everyone is talking, everyone is not used, and all new software The engineering method is also endless, like agile development, extreme programming, pair programming, reconstruction, etc., new terms, new methods constantly emerge, seem to make people feel unfatient, will never catch up with software engineering wing.
Here, I don't say that these new methods are useless, but many new things can only be used to add flowers on the brown, but can not send charcoals in the snow, want to fly, must run first, step by step, take the road in front of the road to make success The romantic of the shoulders carries new methods.
Software project may be too far from the student era. It works so long, it is a fact that there is some real understanding of software projects. I believe that the software engineering process implemented by the company is not only suitable for the industry I have in. How does software engineering control software quality, software flow? I used to talk about the troops in the paper, and now I have finally have some actual experience. Now I think that the software engineering is very similar to the architectural project of our college, but it is difficult for the graduate era. It is difficult to understand: a group of software programmers talk to a group of buildings. Maybe I know that the core of the software engineering is six words: "The intensive step, the thousand miles." Or "three feet of frozen, not the cold."
Of course, how to implement it, far more than explaining it.
It is too much man who knows the truth, because the reason is not difficult, but knowing how to use it is very small. Combined with my work, I will talk about how the company implements software engineering. How is it makes a plate of sand condense, how to make a group of smart people (no programmer admit it to yourself, how to make They completed the project according to the class.
The start of success should have a good plan.
The company's project development uses strict workload estimates and progress control to ensure the quality of the software. Whenever, on the basis of completing the previous step forward, it is impossible.
Software development is first to make a demand. I am not very clear about this process, because I am not possible to participate in this process, I know that the product line manager and special field expert (Subject Matter Expert), they view International Specification documents, and communicate with customers to propose demand norms, this part may be the most difficult.
There is no doubt that specializes in experts are definitely a technical expert in the telecommunications experience, but the product line manager is not so simple, and it is also the experience of the code in front of the front line, and has a good communication ability, then Propensed. A technical manager I just learned for the product line has worked here for three and a half years. I said his technology level, sitting next to me for a year and a half, I admired him, tell me Ask his question about our existing software development framework, he always can speak very well, including a lot of details. Of course, his English is also very good, otherwise it will not be proposed for technical manager after two or three years. That is to say, people who propose demand have a strong technical background, and the quality of the problem and customer needs, the quality of the software needs must be greatly guaranteed. After the software demand is determined, it will arrange the project (refer to Feature "in accordance with each of the technical manager [you can refer to" continuous success "], and each project is generally handed over to the old experience. Employees do project supervisors (Prime), then arrange employees with less experience and new employees participating in new employees, and the specific number is determined according to the possible difficulty of the project.
The next step is the specific project's survey stage, usually a few weeks (this time is arranged), at this stage, in order to lead the underlying human resources by the project supervisor, the main demand is split into several children. Demand, analyze the difficulty of each child demand, and write into a detailed documentation (including all code, patches, and other survey records).
Following the demand standard document Review (REVIEW), the project's leader, technical manager, and the person who makes the demand standard will be discussed for a time. The project supervisor proposes its own child demand item according to its own survey record. Relevant difficulty estimates, everyone is aggregated after discussion, then estimates the time of the process of the entire software development, and each road sign, and submit to specialized in the time of the number, difficulty, and the number of items to this project, and each road sign. Manage web pages.
Then start the design and development of the entire software, first enter the first road sign DS (Design Start design start).
The work completed at this stage is:
1. The demand specification has been reviewed and confirmed.
2. Project arrangements, specific demand items arrange to specific design leaders (Design Prime).
3. The artificial resource report is submitted and assigned its respective work.
4. Generate project IDs in the project manager (special web management software) and each road sign prediction completion date.
5. Open the document submission path for specific items in the document library.
6. In the project manager, the design starter is filled in the actual date of the design.
After completing, follow the next road sign, called the FR (Functional Reviewed Solution).
The work completed at this stage is:
1. The function description document paragraph is completed. The design test paragraph to include the relevant function list based on the demand specification.
2. All documents related to demand specifications are prepared for discussion.
3. Functional Description Discussion Notification is sent and stored in the event manager.
4. Held a function description meeting, issued a meeting record (stored in the event manager).
5. All specific solutions from discussion are recorded in the program database. 6. All "High" priority scenarios are discussed and close in the program database, not changed.
7. According to the results of the discussion meeting, the function description document is updated, and the new version is deposited into the document database and clearly changing the traces.
8. The actual date of the project manager is set by the design leader by the design leader.
Below is the specific design to complete the needs of the needs, each project is different, and all difficulty is estimated to be experienced. Then enter D
C
(Design
C
OMPLED design ends) Road sign:
1. The document is in the open state in order to complete the design subsidence, and mark the corresponding change marks.
2. Detailed design notifications are sent and stored in the event manager.
3. For a detailed design meeting, a meeting record is issued (stored in the event manager).
4. All specific solutions from discussion are recorded in the program database.
5. All "High" priority scenarios are discussed and close in the program database, not changed.
6. According to the results of the discussion meeting, the function description document is updated, and the new version is deposited into the document database and clearly changing the traces.
7. Set D by design leadership in the project manager
C
(Design
C
The actual date of the OMPLETED design ends.
The above stage is more difficult, but according to the class, it doesn't matter, the hardest part has passed, now enter
C
I
C
Ode Inspection Code Check) Road Sign:
1. According to the detailed design, the changed module list and the specific variation marks are generated.
2. The code submission notification is sent and stored in the event manager.
3. Held the code to submit a meeting, issued a meeting record (stored in the event manager).
4. All specific solutions from discussion are recorded in the program database.
5. All "High" priority scenarios are discussed and close in the program database, not changed.
6. Set by design leadership in the project manager
C
I
C
The actual date of the ODE Inspection code submitted.
Designers' black box test and some white box tests, as much as possible all the possibilities. Enter TR (Testcases Reviewed Test Example by) Road Sign. The test is done by the specific test group, each with a specific test group in advance, and the test discussion is discussed with the corresponding test group.
1. Apply for a test case ID in the test case database.
2. The document is in the open state to complete the design test section and mark the corresponding change traces.
3. Test case discussion notification is sent and stored in the event manager.
4. Held a test case meeting and issued a meeting record (stored in the event manager).
5. All specific solutions from discussion are recorded in the program database.
6. All "High" priority scenarios are discussed and close in the program database, not changed.
7. In the project manager, the actual date of the TR (Testcases Reviewed Test case) is set by the design leader.
The test case is written and passed through the test. Enter DT (Designer Testing
C
OMPLETED test is completed) road sign.
1. The test results are submitted to the test case database, all of which are passed, unless the abnormal conditions are explained. 2. For all modules involved, the code update request is proposed and passed.
For the final phase of the design process, enter the LA (Load Available for PV Loading Submit to Test Group).
1. All code updates are submitted and loaded.
2. All specific solution entries are turned off in the scenario database.
3. The module that gets the verification will go to the next version.
At this point, all steps are finished, the product is given to the specific test group check, mainly for white box testing.
This is the specific process of this design group. Of course, for specific items, the steps inside each step may not all, but the DS (Design Start design begins), Fr (Functional Reviewed solution passed), D
C
(Design
C
OMPLETED design ends),
C
I
C
Ode Inspection Code Submitted), TR (TestCases Reviewed Test Certificate), DT (Designer Testing
C
OMPLETED test is complete), LA (Load Available For PV Loading Submit Group) This whole process is not less, for big projects, usually requires seven or eight months, for small a little, probably need One, two months.
The entire test process of the test department is similar to the design department, and there is a complete quality control process, and each road sign must also come.
Software defects will also be found in the process of testing. At this time, the test group will submit it to the specific designer of this project, and the designer will request to open a "change request" and then get the specific module supervisor. After the promise of the person, the code will be changed again. After the "change request" is completed, the project is over, and it is possible to maintain it in the future.
I started working for half a year, and I started to adapt to the environment and learn basic business logic flows. Behind the specific software development, the project is now larger, "Design Description" is now by an old employee I just finished writing, but I will go home tomorrow, "Design Description" discussed time, etc. Waiting for the Spring Festival in the past two weeks, so the process of "changing the request" is not very clear, but I heard that the time is not available. When solving Change Request, it is the learning phase, preparing for the next project, relatively easy, can be used to take a holiday.
The software engineering purpose is the control of the entire software development process. The successful software process is the balance of pressure and task. Most of the cases only work for five days, it is not eight hours a day. The programmer should first be a normal person. Other time should enjoy more yourself, isn't it? After all, do a hot pot, shopping, playing table tennis, there are a lot of different fun. In this basal, the brocade is of course good, but if the daily pressure and tasks can't get good allocation, dispersion and solve, maybe more new methods are also difficult to control the software projects of the sore baffles into the cream, and the appease is exhausted. programmer.
The big achievements are small achievements, and the daily progress is enough to make a year, and the annual harvest has formed a living harvest.
Since the company's document is all English, there are many terms, it is difficult to express, it is difficult to find the corresponding correspondence, and only the ability to do our best to avoid English. Wu Tong writes in 2004.1.11
Recently modified 2004.1.16
