A summary of the course of software engineering

A summary of the course "Software Engineering"

after a semester of study, let me to the Software engineering Project This course has a more profound understanding. From the beginning of this course ignorant ignorance, through the slow learning, weekly practice. Let me gradually have the answer to my previous questions.

1 How to become a software engineer

Become a software engineer to be proficient in application programming software, proficient in programming language, but also have a good sense of teamwork, but also need to be curious and enterprising, so as to become a qualified software engineer.

2 How to learn software engineering well

Software Engineering is a comprehensive discipline, and software engineering is emphasized on the understanding of soft ware, as well as some effective arrangements to develop, track progress, ensure the quality of engineering methods, simply look at these books, if not a certain practical basis is very understanding of the real problems, to more hands-on practice. More into the software programming team, so as to improve themselves, so that they can better learn software engineering.

3 Process of software development

1 Requirements Analysis 2 Overview Design 3 detailed design 4 code 5 test 6 software Delivery 7 acceptance

4 How to evaluate software quality

1 Correctness 2 High efficiency 3 Reliability 4 Ease of Use 5 scalability

5 How much software to develop is a qualified software engineer

Software development needs to continue to practice, continuous learning, only in this way can better improve themselves, so that they become qualified software engineers.

Through this semester of software engineering class learning, let me learn and learn a lot of learning. Software engineering is a project that needs to be practiced constantly, to be constantly hands-on, to participate in every process of software development, from requirement analysis to final software delivery, every step of the way. A software engineering does not mean that simple coding can solve the problem, we do not put more energy on the coding, coding is just a small module, only a small part of it. This fact to a large extent overturned my previous thinking, in my previous understanding, it seems that the whole software is coding, in addition to this, fortunately there is a teacher's guidance, or it will really appear the teacher said, hit the head and head after the mind to use software engineering to complete the work.

Before we really started working, we spent a lot of time doing some front-end work, such as demand analysis and feasibility analysis, the work in other people's opinion may be relatively insignificant, or even more, in fact, in the past, I would think so. However, I am now deeply understand the truth of AX, the completion of these work is too necessary, too important, to want your software useful has market, can be accepted and recognized by others, in the course of the process will not appear collapse of the problem, these work is indispensable. There are some of the next design modules.

Software engineering is a collective project that requires all of us to join together. To ensure the coordination, uniformity and continuity of the system,it is necessary to develop rigorous and detailed development specifications prior to development. It takes a certain amount of time and effort to develop a development specification.,but"sharpening a knife without mistaking the wood",it is equivalent to taking into account the problems developers will encounter in the development process in the future. With the development specifications,in the course of subsequent development,designers don't have to think about how to name one field at a time,programmers don't have to think about how the structure and layout of a program should be,testers also have a standard for judging the wrong procedure. The development norm plays a pre-agreed role in the project development work .,all developers are required to follow together. It constrains the developer's behavior and design, programming style,enables the design and programming staff of different subsystems and modules to reach a tacit understanding,in order to form the harmonious pace and unified style of the whole system.,It is also convenient for future system maintenance and expansion work. So in the process of software development, we should have a good sense of teamwork and cooperation. This will be a good way to work together to complete the project. Through this semester of software engineering, I learned a lot about computer science in terms of technology, so I know more about the whole computing industry. Also made my own programming level has been greatly improved, let me understand the team spirit in the team and how important. Finally thank Feng teacher this semester to lead us to learn software engineering This course, but also thank the pig's feet for our help.

A summary of the course of software engineering