Summary of "Personal summary" software engineering m1/m2

Personal Blog Connection:

Http://www.cnblogs.com/lwq12061168/p/4094252.html

Http://www.cnblogs.com/lwq12061168/p/4028450.html

This homework is the teacher long ago decorate, this evening is the deadline, also just remembered to write. In fact, a few days ago also remember, but busy with other exams and curriculum design, so pushed forward. This reminds me of Gao Xiaopeng Teacher's classic words: "Deadline is the first productive force!" "That's really true. Just have a kind of "hehe" feeling.

I really do not want to write some high-sounding words, said I learned a lot in m1/m2, because I really do not want to make up. In fact, I only went to the course four times, three times in the interim, the medium time, the latter is not. First of all, because there are too few people to go, I am the kind of people who follow the crowd, and then there is the teacher lectures with English ppt, a piece did not keep up with, the latter is difficult to keep up with; most importantly, almost the majority of people have reached a consensus: this course as long as the completion of the teacher's homework is completed, The captain will arrange it. So for me, m1/m2 just has a simple and vague beginning to end, where details such as " requirements/design/implementation/testing/release/maintenance phase" is not too deep experience, I just do my job to complete their assigned to the task.

Demand, design, everyone to a simple meeting, discuss a general, and then disband, in fact, we did not discuss a very good topic, give me the feeling is a little hasty, or simply say that we can write a similar to the good, can pass on the line. Speaking here, I think the team task really lacks a spirit, let everyone desperate, feel the spirit of woe, so write may not be accurate, but that is the meaning. The lack of this spirit of the result is, for their own task is only fast and not refinement, I finished my task is good, the rest to others! As for the direction of the mission, it was the captain's business.

Implementation, testing can learn a lot of things, because nothing, everything from the beginning to learn, but also as mentioned above, just self-study and their own task-related parts, and then discuss the task with the captain, complete it is good. So that the final release, maintenance phase, because the captain did not assign a task, you have to have no much relationship with themselves (of course, the second half of the course set up a heavy task, so can regardless of the best is no matter).

Overall, the entire M1M2 Captain's task is the largest, he has to allocate, but also to integrate, and even to engage in part of the code work. Here, really grateful to the captain. But then again, a team of really learned things, that is the core of the course, probably only the captain of a person! Others cannot refute anything, after all, the more they pay, the more they reap. In addition to the captain, this set of software engineering process down, I think few people who have much to gain. Perhaps my eyes are too short-sighted, but in my eyes, our two classes will not have more than 1/3 learned a lot of things.

This is my summary of the m1m2, there is not much nutrients, but it is what I want to say, I hope the teacher understanding. (complement: learned compared to did not learn, suddenly feel no value)

Summary of "Personal summary" software engineering m1/m2