Personal summary of introduction to software engineering

Personal summary of introduction to software engineering

In the blink of an eye again to the end of a semester, here is a simple introduction to software engineering This course to summarize it. To tell you the truth, I really don't know what this class is going to say at first, but I will tell you something about software engineering. However, with the class, again and again the task, I finally understand what this course wants us to do.

This door is like what the teacher is talking about "doing high school" as the main idea, the main emphasis let us in the process of developing software to learn knowledge and skills. In the first few weeks, I think this method is very good, indeed can learn a lot of knowledge. However, this is only a simple start, when the two pillars of the arithmetic is more complex than once, when we form a team, need to sprint in a short time, to complete their own projects, the kind of backward planning progress and one after another bug constantly destroying our original optimistic heart. So, you will hear the teacher's homework how so difficult, time so short to finish it? And so forth. But we will find that after each stage, we still have a lot of gains.

Talk about my own situation, I know myself, not the kind of teacher to understand, class under the so-called "great God" of extensive knowledge. So every course, I try to spend more time in class, at least not behind the majority of people. Then, I will try my best to complete some of the tasks that the teacher confessed, for example, some knowledge of JSP, connection database, in winter vacation, I already will, so this semester this knowledge Master good. However, I found that my analytical ability, but also some data structure of knowledge needs to be strengthened, because this teacher in class in the course of programming problems, I feel it.

Also has learned the software to write some specifications. For example, the teacher asks us each time the programming question, before the programming beginning all must write the design idea, and the more detailed the better, this avoids when we program the time to think where to write, sometimes even forgets oneself to make up. Also require us to write code must pay attention to the specification, such as the necessary indentation, curly braces, and so on, which enhance the readability of our code, and there is every time the programming is completed, we have to do a programming summary, so that we know their own harvest, as well as some of the shortcomings in programming, to avoid making the same mistake.

Then there was the team development project, and at the beginning there was a lot of different opinions, and even a group of names sparked a dispute. But our team is on the right track, we have a stand-up meeting, we program together, everyone plays their part, and although our software still has a lot of shortcomings, I deeply appreciate the importance of a team. In short, you have to be clear: you are a member of the team, you can not decide everything, to listen to everyone's opinion. Because we are a team, a proud wing, a loss.

Let's talk about some of the books we read from our teacher, the book of construction is mainly about how to implement some software. such as: How to carry out requirements analysis, how to model the analysis, design the module, how to compose the Software engineering team, how to test the use case, and so on. And it advocated the method of doing high school, I feel very useful, let me learn a lot of knowledge. Then there is the book "Dream Break Code", which actually teaches us some knowledge of software development through a specific process of project development. I remember clearly that there was a survey that showed that 2/3 of the software was delayed or failed to achieve the desired effect of the project. In the face of such a fact, I can say that it is a surprise, indeed the book said very clearly, the software in the implementation process, do not know when the bug suddenly, perhaps just a small naming specification problem, you can pull down the progress of your project. So we must study hard now, reduce their programming errors, so that their programs more standardized.

Well, learning this course really can learn a lot of knowledge, and class teachers do not let the phone, lectures are also very humorous humor, class There are many exercise our ability to program problems. All of these are very helpful to us. But I still want to give some advice to the teacher: is to hand over the homework time or to loose some, especially now the exam week, and other subjects to review, so the summary can be considered late to pay Ah, there is more to us some examples do reference it, after all, most of us do not know much about programming, you give us some examples, It can save us some time to search for information without any purpose.

In short, the next semester will be more specialized courses, so summer vacation time to learn some useful knowledge it.

Personal summary of introduction to software engineering