Final Summary of software engineering

This is the last job of software engineering, here write my experience and summary since this semester.

From early March to May Low, learning software engineering for nearly three months. From the beginning of the personal project to the later pair programming to the team project, during the period experienced too many difficulties and setbacks, of course, also has a successful harvest. Sometimes after the lights out to continue to stay up to one or two points still in the revision process, when the submission of success in the heart is still very excited. Although the software engineering has already completed the course and finished the final exam, but I can learn a lot in high school, in addition to personal technical knowledge, but also aware of the importance of teamwork, here is still a lot of places are worth affirming.

At first I was preconceived, that software engineering may be similar to other specialized courses, learning textbook knowledge, in the hands of some programs to practice, not actually. It seems to me that software engineering is not a class, but rather a thought. is a process to guide us how to analyze the problem and how to deal with it. It should be said that the category has gone far beyond the course itself and has become a comprehensive collection of ideas that can solve problems.

Requirements Analysis-Overview Design-Detailed design-write code-project test-Project Completion-project maintenance, this is the general procedure and process of software development, I think this is a very meaningful teaching content, it makes our work modular, so more rigorous, but also to improve overall efficiency. When we graduate, we enter the enterprise, which is a very important skill that we should actually use, not only in the scope of software engineering. Even if later engaged in other industries, but this is the thinking and methods of doing things are also useful in life, are from the needs of the design, step by step, organized, and ultimately complete the work. I think this is the meaning of this course, and this is where I feel the most.

Team project work, our team to do an app, his function is to help people at the party to provide you with some entertaining games, as well as the occasional photo function, dice games and so on. Of course, we have personally experienced some, it is very fun, there are many areas of knowledge need to improve and improve. When I use my own team to work together to complete the work is, in addition to meet the pride, but also let me feel the magic of technology. Sometimes a seemingly simple thing, it is hidden behind a myriad of sweat and pay, in layman's eyes even will be dismissive, he just they did not touch it, they do not know how deep the water there. Many people are using mobile phones, social, games, learning, they will not understand how each of the features here, each line of code is how to write. Feel that this is a masterpiece of senior talent, too far away from their own. But if they use an app that we made out of, they will look at us with what kind of vision, that sense of accomplishment is unimaginable.

The next thing to ask is agile development. Simply put, agile development is a large project into a number of interconnected, but can be run independently of small projects, and completed, in the process of software is always available. His values are communication, simplicity, feedback, courage and humility. These are, of course, an essential requirement for a good software engineer. Alistair Cockburn once pointed out that many methods define the role of developers in software development projects, while defining the tasks that each role performs, although none of these methods define the best candidates for those roles. But a successful modeler must have the following personalities: team competition, speaking out, down-to-earth, curiosity, seeking truth from facts, summing up experience and adhering to discipline. A person who wants to succeed in a role should adapt well to him, although it does not require people to master all the skills, but people have to be familiar with these techniques slowly. The above mentioned Agile development, the following is the UML. Many people think that in the era of agile development, there is no need for UML to learn. I don't know, I think the essence of UML modeling is very agile, it is one of the core technologies of Agile development technology and agile modeling.

Compared with most basic courses, the teaching method of software engineering is not so dull. Blog to introduce teaching, so that our learning more convenient, is our communication platform wider. Although this course is over, it teaches us how to do things and ideas, and we need to continue to learn and improve ourselves. Finally, I sincerely thank Xu Teachers for their hard work and explanation, but also thank you for teaching assistants in learning to live in the encouragement and help.

Final Summary of software engineering