An introduction to the practice of software engineering

　　"Introduction to Software Engineering Practice" This book is published by Tsinghua University Press in 2005, the author of Fairmont and. The choice of this book as the job selection, is because a senior hand has the book, but also recommended to me this book is worth a look. But the book is relatively thick, and the content is not simple, so I can only be a little bit.

The book in front of some of the software engineering concepts, as well as the combination of engineering, for the actual code design and development process is still a great help, feel a lot of things in our big homework-"scheduling system" there are applications, so give me the feeling is and the actual application of mutual echo, can use the knowledge.
The latter part of the book has a special feature, divided into 36 small parts, and the art of war 36 of the Sun Echo. My feeling is that the author himself is also quite interesting, after all, these two things bull head than horse mouth. Let me give you a concrete look at my book.

1. The beginning is the most basic idea of software engineering, it can also be said to be a programmer must master the idea is also very important: divide and conquer. This idea is very simple but very easy to use, it can be said that software development is constantly refining the problem of differentiation process. The following are some of the relative things, such as software reuse, and optimization. These are the methods and techniques that are good for improving the quality of the code in software engineering, which is an essential part of a software.

Take our big homework for example, our program is a lot of things in the modular embodiment of the idea of divide and conquer, for the input of curriculum requirements, we have a dedicated input module, for the processing of data we have a special curriculum generation module, for the display requirements we have a dedicated display module, It can be said that each module is an embodiment of the idea of divide and conquer. For code reuse and optimization It is also natural not to think that many things in the code development process can be reused by different parts, which also improves the readability of the code.

2. The following is the design process of software engineering. Architecture design, module design, data structure and algorithm design, user interface design, and so on. Good software engineering is conducive to the development of late code, but the book gives me the greatest feeling and not the use of software code development, but for the subsequent change requirements, as well as the role of software maintenance. Complete design documentation and detailed module function notes are important for the functionality of the late software.

In our software engineering big job, we start the design idea to have the very big deviation. Starting the software we want to implement is a course of elective course in university, but later it is found that this course of selection is very important to our topic. So we decided to implement a relatively fixed curriculum generation pattern, which is the curriculum scheduling system with relatively fixed curricula. such as high school's troubleshooting system, which is the original intention of our design, for high school class, we want to be able to use code to achieve this process. At this point, we need to take advantage of the beginning of the idea and design process, so the previous design document is very important.

3. Method of design. There are many methods of software design in this book. such as waterfall model fountain model and so on. The book specifically describes the importance of the actual engineering application of these models, which is important for participating in a relatively large team design process after entering the work.

4. Later in the book, the author, as a scholar with more than 20 years of programming experience, is aware of his experiences. In the form of 36, it echoes the 36 counts of the art of war. Divided into four major chapters: method, design, realization of the chapter, management chapter. Each section contains its own methods.

Methods: User-first, management requirements, economic texts, early integration, control changes, continuous validation, rapid prototyping, normative processes, borrowing chickens to lay eggs, open standards.

Design: Skillfully with the template, object-oriented, internal and external, as a solution, block block, avoid the complexity of Jane, can stretch to bend, at the close, contract interface, local conditions, change in the static, layered platform.

Realize: Never repeat, optimize performance, easy to understand, tiger, excellence, automatic process, strict plugging loopholes, the sharp weapon evergreen, Yanguoliusheng.

Management: Often come to production, division of cooperation, there is a chi, goal-driven, and constantly summed up.

The above is my "Introduction to Software engineering Practice," the book's thoughts, in the process of reading I combined with their own large operations to achieve the process, or some sentiment and feelings.

An introduction to the practice of software engineering