Thoughts on reading the Law of construction

With the help of many teachers, we have the honor to learn the new work of Xin Zou, the law of construction, in this semester. Start reading this book, the greatest feeling of the experience is software engineering originally can learn, before the course of learning software engineering, always feel this course and boring, always say too much theory, rarely involve practice, or even no practice this link, so learning is very boring, But the Graduate school reading this book, really is a new feeling, first of all, not only in theory, adding a lot of practical things, but also can be on the Internet and other people to exchange learning experience.

The opening Xin Zou teacher said the "Software = program + Engineering", previously written software or program, just write the program, at most will take into account the knowledge of data structure, rarely use software engineering, but with the depth of learning, the accumulation of code, if it is the same as before just care program as long as it is available, Actually can run, then there is no meaning, such a program is also worthless, first of all, software engineering is not only related to computer or software knowledge, on the contrary, it involves a lot of knowledge of other disciplines, such as: Management, mathematics, industrial design and other disciplines, If a qualified software developer only knows how to write a program, then hi is just the primary stage, and more advanced should consider more things from a more advanced level, such as the architecture of the entire software. After reading through the book, I think it has the following characteristics:
First, both theory and practice. This book introduces the related concepts of software engineering, such as: SW project, Unit test, software development process, agile development, software requirement, user experience, software testing, quality assurance, etc. While introducing these basic concepts, the authors also comprehensively explain how they behave in actual research and development work, and how they relate to each development and testing staff. In introducing these concepts, the author uses examples to illustrate the situation, which makes it easier for everyone to understand.
Secondly, the writing is beautiful and illustrated. The author spends a lot of energy trying to get the reader to read the book without feeling dull. First of all, the content of each paragraph is not many, to prevent the reader from a large page of text in a daze and lost the courage to continue reading, second, the book contains a lot of interesting pictures, readers can use these images to deepen the understanding of the relevant concepts, again, the content of the book is clear, The author lists many points of knowledge in a few small order, making it easier for readers to read and understand.
Third, the language humor, witty. The concept of software engineering is relatively dull and monotonous, and the author is well aware of this. Therefore, in many parts of the book, the author is in a very humorous way to tell. For example, the book uses the dialogue between characters such as "Chiu", "Guo Dong", "Xiao Fei" and "Xiao Li" to reveal the essence of a concept. This makes the reader feel very "ground gas", and through their humorous dialogue and accelerate the understanding of the relevant concepts. Personally, this is the greatest feature of the book.
Four, the coverage is wide, the knowledge point is complete. The purpose of this book is to introduce software engineering, but not just software engineering. This book is also a detailed introduction to the growth of software engineers, innovation and professional ethics in the IT industry. The author views the development of people in the whole industry and industry from different angle of view, which is worth pondering.
Software development is a complex system, only the system of every part of the normal operation, the entire system can be all normal. Once a part of the problem, then the system is like a leaky ship, if not repaired in time, will eventually sink into the sea. Of course, in the actual work, we have different division of labor, have to do the development, have to do testing, have to do QA, and so on. Everyone's duties, the purpose is to make a software to live better, live out of the wonderful, it is best to "longevity", so that everyone's pay to get the due return.

The overall framework of software engineering (software Engineering) can be summed up as: objectives, processes and principles.

Software Engineering Objectives: produce products that are accurate, usable, and cost-appropriate. Correctness refers to the degree to which a software product achieves its intended function. Availability refers to the extent to which the software infrastructure, implementation, and documentation are available to the user. Overhead is the degree to which the entire cost of software development and operation meets the user's requirements. The realization of these goals, both theoretically and in practice, has many problems to be solved, and they form the constraints of process, process model and engineering method selection.

Software Engineering Process: the steps required to produce a product that ultimately meets the requirements and meets the engineering objectives. The software engineering process mainly includes the development process, the operation process and the maintenance process. They cover the requirements, design, implementation, validation, and maintenance activities. Requirements activities include problem analysis and demand analysis. The problem analysis obtains the requirement definition, also called the software Requirement specification. Requirements analysis generates a functional specification. Design activities generally include a summary design and detailed design. The outline design establishes the entire software system structure, including the subsystem, the module as well as the related level explanation, each module's interface definition. Detailed design produces module descriptions that are available to programmers, including data structure descriptions and processing descriptions in each module. The implementation activity transforms the design results into executable program code. Confirmation activities throughout the development process, to achieve the completion of the confirmation, to ensure that the most complete and correct products presented in front of the user.

Post-Reading questions:

1. I heard that after the work of soft testing will be more relaxed, then there is more room to rise?

2. At this stage, where can we start to develop our own development thinking and ability to move towards engineers?

3. How should we strengthen our value? The company needs to create value for its talent, but also the opportunity to let us learn slowly?

4. About project design, how do we design a project, from requirements to testing, what do we need to do halfway?

5. Is there a close relationship between the team work model and the development process? Can the two be divorced?

6. How to learn a language, how to learn more efficient, what is the best way?

Thoughts on reading the Law of construction