Personal Final Summary

• translation

Software engineers should do their own analysis, specification, design, development, testing and maintenance, so as to become a useful and respected career. Based on their commitment to software robustness, security, and benefits, software engineers should adhere to the following eight principles:

1. The principle of public--the development direction of software engineer should always be consistent with user's intention;

2. Customer and employer Relationship principles-software engineer development should be consistent with customer and employer's wishes;

3. Product quality principles--software engineers should ensure that their products or released models can pass the highest level of calibration;

4. Judge the principle of fairness-software engineers should always maintain the principle of fairness and fairness, especially for their own projects;

5. Management principles-Software engineering managers and leaders should provide the right way for software development and maintenance management;

6. The principle of professionalism-software engineers should be the user's impression of the integrity and reputation of the example;

7. The principle of peer relationship management-software engineers should be fair to their colleagues and give support;

8. Self-learning principles-- software engineers should be involved in lifelong learning for their profession and should encourage the right approach to professional practice.

• Learning Experience

After this semester of software engineering curriculum learning, the project development process has a general understanding, but also personally as the captain to lead a six-person team for project development, generally harvested a lot.

First, talk about your own learning. The words have been as a member of the development team in the development of the project, but every day just know the code of their own codes, write comments, team communication is only the demand allocation, interoperability interface, and more because the project is not strong development, once faced bankruptcy. At this time, we are more likely to shirk responsibility to each other, and ignore their own part of the problem. Read the "Building law enforcement" this book, found that many of the previous project development process and practices are not in line with the norms, such as code specifications, development methods, so after the development of the project, it is best to have a detailed plan for the project in advance, draw a UML diagram, look at the diagram code, and not now just Code code code, Code codes are only part of the project development, not all.

Secondly, the team management, I found that when the captain really need a very good quality. the captain must first be the most understanding of the project, and the team to plan the project process after the fair division of labor, of course, fairness is not the average, according to the ability to allocate, so the captain must understand the actual ability of each player. In addition to these physical activities, the captain also needs a good temper, you should be ready to deal with the unexpected situation of the players altogether, to its extremely sincere persuasion, good situation is that the players figured out, go back to work, all return to normal, so happy, and if the situation is not good, the players do not listen to advice, You also have to do a fair job of assigning his work to other players, which is a dead loop, and the captain's ability to coordinate is especially important. Finally, the project released, the captain as the spokesperson of the project, in the face of popular love and praise at the same time, the captain also to accept all kinds of ridicule and accusations, at this moment, can maintain a calm attitude is a big test for the captain. So the captain was very tired. However, this is also a plum, when the project can be successfully run, the captain will reap far more than the general team of joy and accomplishment-this is what I led to do, although not perfect, but we have been successful! In short, the captain is a double-sided position.

• Teaching Advice

First of all, I would like to say that software engineering is a very useful subject, if the students want to engage in project development, software engineering will help you a big favor.

As for the proposal, I feel this semester although learned a lot, but almost all in the class self-taught, in class just listen to the teacher to talk about PPT, the effect is very bad, so it is equivalent to the whole class time to waste. I suggest that after the first two weeks to teach students to read the textbook, the software engineering has a general understanding, according to the current way to publish assignments, blog, the code, it is best to change the class time to team Exchange time, after all, because of the course arrangement, many teams do not have much time to sit down to communicate, A thorough communication is an essential element of a successful project team.

Personal Final Summary