EDITORIAL:
| Good mood today smoked a time the rest of the contents of this book finished reading a really great harvest although I just read the theoretical understanding of them but I feel this understanding of software engineering software engineering courses have a long process great progress, at least before I do not know how to do a real software after reading through the complete book for software engineering have a general understanding of the process in the hope that the next semester can be learned to practice it. |
text:
1. Software Design and Implementation
This chapter explains how to analyze and design software. Analysis and design methods there are many, such as graphical modeling: by establishing a Mind Map, entity-relationship diagrams to describe the relationship between the various roles, and then analyze the needs and functions. But there are many ways in the development of the computer, the emergence of a variety of methods, such as formal methods, literature, programming and so on. These methods have advantages and disadvantages, no one is truly perfect. So after we finished the analysis and design of written documents, we realized how these needs it? The book lists a programmer in the development process after the design documents to get through this development process can make the development process more standardized. During the development phase, a variety of situations happen every day. For instance, some programmers behind closed doors, some programmers do not pay attention to daily build, but will also be some special circumstances at the time of repair BUG: temper justice are wrong, that is, whether the requirements for the embedded code is broad or strict, are Incorrect. These should combine the two. Finally, there may appear Bug Hell, that is hell bug, developers only focus on the development features, do not pay attention BUG, BUG become more than to make only a team of people together to repair the situation of the BUG. At the same time source management in the development process there are certain requirements for source code, we can not only keep up to date, should have retained from the beginning to the final code release for newly recruited staff to learn, but also conducive to the restoration of BUG as well as view and modify future. Finally, the code is complete. This process also officially ended.
2. User Experience
Talked about the last chapter, code development is complete. But software development does not end. We want our software to further optimize the user experience feedback, in order to better meet the needs of users and customers. We have to take into account various situations, such as the user's first impression, do not let the user make some simple mistakes, which requires us to better design. User Experience Design There are many ways, such as rapid prototyping research, which uses paper model, to reproduce the current state of the software, users go to the judge. Or A / B test, directly to existing users to test new features and see if customer satisfaction. So how is the real good user experience? Some basic principles of the book, as soon as possible to provide tactile feedback to the user's realistic practice, the user must have the right to control and so on. These are some of the basis for evaluation. At the same time for different devices have different needs to be examined in accordance with the actual situation.
3. Software Testing
Software testing, a listening vocabulary both excited and sad people. All previous software releases is bound to be tested, not by testing certainly fight back. So how is the author of a variety of software available in the market then test to classify it? Through various angles of the classification, such as by designing test methods are classified, there is a white elephant and black box testing; classified by testing purposes, functional tests, non-functional testing; classified by the timing of the test, such as the Smoke Test. This is designed to test the method, then what specific test methods? The authors introduce 12 kinds of testing methods including unit testing, build verification testing, acceptance testing, etc., in particular no longer start. Once you have theory, is the actual combat test, to theory in actual combat, the author put forward his point of view for some problems. And some of the wrong behavior was correct. After that, the real test tool is used here because I have no project, no way to expand the field, let's skip.
4. Quality Assurance
After the software is completed, through tests, there are many things to consider. Quality guarantee is one of them, to do the most important thing is the software robustness of the program. If a software is not robust crash from time to time, such software can not be released. Well, from concept was first starting, including the quality of the software, what does? The authors suggest a formula, software quality = + program quality software engineering quality, separated in terms of the quality of the program is very simple. Can the stable operation of the program, whether the algorithm is fast enough. Quality software engineering will include more aspects, such as the visibility of the software development process, risk control the software development process and so on. How to measure the quality of software engineering it? You can use a system called the CMMI, CMMI software engineering can be subdivided into five levels, through this classification can clearly see the quality of software engineering. Knowing what is the quality of the software, it is necessary to learn how to protect quality. First, test, test this role should be independent out of it? Authors put forward their point of view: It should be. According to the actual situation and propose a few questions to test the role of the face, such as the blind trust in so-called professionals, there is no clear division of labor and so on. These are the roles tests need to be resolved.
5. stable and publishing stage
Eventually, the code is complete. Finally, there is stability and release phases. We can group consultation, consultation software analyzed by some of the BUG, and their classification, subdivided into various categories, which will be the highest priority for repair. Posting Alpha / Beta version. In the Alpha / Beta when phase, the user will be asked a lot of feedback through this feedback, it still needs the arrangement in accordance with the order of priority, give priority to the high priority needs. At the same time we have to ensure that the development process, the old fixes BUG seen to be repaired, after the emergence of a new BUG prevent the formation of a chain reaction, making the software release cycle again extended. It is not, directly cut some of the features. It is also acceptable. After a series of stable operation, the software officially released. After the release is not to say all right, to be carried out so-called hindsight meeting, we will emerge throughout the project development issues, as well as the progress of demand and so were a summary, in order to better help later.
6.IT industry innovation
Innovation, listening very wonderful words. But in the end where innovation comes from? Innovation really be accepted by the public do? These are the authors of thinking about innovation. I'm here on my own to talk about their own views. Innovation, there is no doubt that the accumulation of the emergence of various knowledge innovation requires not only the accumulation of knowledge, but also requires a variety of chance, but they are quantitative cause qualitative, quantitative and only to a certain extent, the so-called breakthrough appear, achieve real qualitative change. But not only that, even if the proposed innovation, especially disruptive innovation will undoubtedly change the structure of the world, such as the popularity of mobile phones appeared the WWW, and so on, these innovations have changed the world. But when these innovations will be presented by obstruction from all sides. People always accustomed to change, not to mention this change has been let themselves lose their stick, something I had always been faith. In college, teacher if you want to modify the content of the curriculum, submit to the leadership, some leaders will be dismissed on the grounds that no such precedent. There is no such precedent would not it? So, innovation is very complex and difficult. Regardless of the difficulty to come out, if they really wanted out, wanted by extension is more hard work. Therefore, we have to be steadfast to accumulate its own quantitative, positive thinking, can really touch the boundaries of innovation.
7 people, performance and ethics
Here, the authors mention people, performance and so on. But a look at the contents of a daze, can only say that understanding the two. For the time being not summed up.
Summary: This book is the author's style of writing is very funny, and the authors propose a concept of time, it must be accompanied by a vivid example to help you understand. This is what I appreciate. This knowledge class books, hard to do this all of a sudden feeling of watching seventy to eighty pages. "Building of the law" did. He made me understand what real software engineering, software development for various processes have a certain understanding, but also a little more to look forward to next semester's course, look forward to the growth of their own.