The method of construction read Note 04

This week is the fourth school week, time is fast, unknowingly read the notes also wrote to the fourth, these days I also realized the meaning of writing reading notes, writing notes is actually read the knowledge to summarize, to help understand. At the same time, in the process of reading the construction of the law, but also cultivate good habits. This week I read the 12th, 13, 14 chapters of the content, the same harvest quite abundant.

In Chapter 12 user experience, understand the elements of user experience, first of all the user's first impression, followed by the user's point of view, software services always have to remember the user's choice, attention to short-term stimulation and long-term impact, do not allow users to make simple mistakes, understand the user experience and quality of conflict between the solution, And the emotional design of the user experience, the design needs to correspond to the characteristics of the product: the design of the instinctive level-shape, the design of the behavior level-the use of fun and efficiency, reflective level of design-self-image, personal satisfaction, memories, three levels of factors intertwined, together affect the user experience. Learn about the steps and goals of user experience design, conceptual design, behavioral (interactive) design, interface design, interface designs, respectively. The author's principles are understood in the evaluation criteria: as soon as possible to provide tactile feedback, the system interface conforms to the user's practical practice, the user has control, consistency and standardization, suitable for all types of users, to help users identify, diagnose and repair errors, necessary tips and help documentation. In this chapter, a deep sense of a good user interface and experience can make users feel happy in the process of using software, while the mechanical brain remnants of the user experience design will allow users to waste time and increase the cost of learning, so learning good user experience knowledge for the future software design is crucial.

In chapter 13 software testing, we learned a few basic nouns: bugs, software flaws, test cases, test cases, tests suite, testing case sets, and bugs can be divided into symptom symptom: From the user's point of view, the software what is the problem, Program error Fault: From the point of view of the code, what error in the code led to the software problem, root cause root cause: the root cause of the error, the root causes of the code error. According to the test design method classification can be divided into black box and white box, black boxes, in the design test process, the software system as a black box, unable to understand or use the system's internal structure and knowledge. While the white box refers to the design test, the designer can see the internal structure of the software system, and use the internal structure and knowledge of the software to select test data and specific test methods. Classification according to the test purposes can be divided into functional testing, non-functional testing, but also according to the Test timing and role classification. Learn about test methods, including unit tests, code coverage tests, build verification tests, acceptance tests, exploratory testing, regression testing, scenario/integration/System testing, partner testing, performance testing, stress testing, internal/external public testing, usability testing, The core steps in the test are gradually recognized from these tests. The testing process is more clearly defined in the actual practice. In the introduction of testing tools learned and mastered the use of testing tools, as well as the use of the software used, and learned the effectiveness of testing methods.

In the 14th chapter of Quality assurance, learning the definition of software quality, software = program + Software engineering, and the quality of the program quality = Software Engineering quality. The quality of the program is reflected in the quality of the software external function. The quality of software engineering is embodied in the following aspects: the visibility of the development process, the risk control of the software development process, the internal modules of the software, the quality of delivery in the intermediate stages of the project, the factors of the project management tools, the cost of software development and the completion of the internal quality indicators. Learned how to use CMMI to measure the quality of software engineering and the level of CMMI. Learn about the four aspects of prevention, review, internal failure, and external failure are part of the software quality cost.

There are three chapters to the end of the book's reading, but I believe that this knowledge will be deeply engraved in my mind will not forget, this week's three chapters of knowledge so that I have software testing, user experience these words are no longer unfamiliar, see these mind will emerge in the Book of Knowledge, yes, I know them and no longer on the surface, I believe that these knowledge of my future self-development software engineering has a great help, this book will always play its role!

Building a method of reading notes