Summary of the course of software engineering introduction

This semester most of the class is complaining, complaining about too much homework, complaining about the work is too difficult, complaining why did not learn to let us finish the work, complaining that the teacher is too high on our request, but think carefully compared to other subjects, the harvest is quite a lot.

This course after learning the most influence on me is that after getting the topic is no longer blindly on the beginning to write code to write the code began to feel happy to do other things, I will first analyze, then write my own design ideas, and then slowly implement my code, and then make a summary; Nor will the program write half of the time suddenly feel no idea, so think "alas!" What did I just think? "It's easier to write the program, and it's more proficient in the Java language than it was last year, and a little bit more about JSP technology."

Write two pillars, every day is said two pillars why so silly, they let him do what do what, the teacher too much, has been let the parents of the students to do things; at that time, is also quite helpless, can only verbally complain about, think of the date of the procedure to be or to appoint continue to write; The third time every implementation of a small function should be hurriedly and roommates to share, this may be the most happy time for programmers.

Then the team project, just beginning two people, initially thought I was able to complete the program, and then do not go to the partner to discuss, began to write the program; then the second team project realized the importance of the team, we first did a rough market analysis, then write our design ideas, then write the code, to summarize. To do Android when the team changed to four people, just started because the team name and there is no small controversy, with the slowly running in everyone's duties, as the "Maverick Pig", I also gradually understand the importance of the team to do the project. Then do android , just start on our software to do a very great idea, but the beginning of the sprint, really a face of the vacant, completely do not know where to start, what to do first, so the team played a great role, Daily stand-up meetings are constantly summarizing and learning. Find all kinds of information on the Internet, and then make various changes to our program. Although the last thing to do is not too good, but still feel very happy.

Through the reading of the law of construction I also have more understanding of the software project, such as the basic process of doing the project, to do the requirements of the analysis of the user according to some of the non-professional expression to obtain his real needs or hidden demand, the project team of several models, the individual feel or functional team Model best, there are several groups of people Parrot, chicken), and after the project user experience is the user's first impression of the software is very important, and then the software should always remember the user's choice, give users a good long-term experience. The quality of software needs to be ensured by various tests of the software.

Read the Dream break code, it is to look at the book of Daniel tells the story of their experience in the project, as well as some experience, and they are in this industry to explore the process, every time they think they are really strong, looking forward to someday, if I also become a Daniel I will be a team of what kind of role, What would I do if they had that kind of problem?

After finishing this course, I really feel that the potential of human beings is infinite, the teacher left homework to think how possible, this job so difficult I will not, under pressure, or appointed to do, slowly explore, study, the final timely completion of the quality is not very good, but can still be completed, slowly also adapt to this mode, Complaining doesn't want to be that much at first.

The last point: actually quite like the teacher this way of teaching, at least the class will not be distracted, play mobile phone or something; the teacher is also very funny, even if a lesson really understand in the things not much, but every time back to think of a lot of knowledge points. Learning through self-learning is also a lot of things, like doing Android from the beginning of the ignorant to now through a few people to work together can make their own software, and get a lot of people's recognition, although the process is more difficult but learned things really gratifying.

Advice to the teacher:

1, hope that in the future if you do not use the computer in class can not take, because it is too inconvenient;

2, I hope that the teacher every time to stay in the work of the card so tight, because there are other subjects work, can not just do this section of the homework;

3, if it involves let us self-study when we can give a little more reference, rather than let ourselves blindly to the Internet to find.

Summary of the course of software engineering introduction