Building Method Reading Notes 05

Building Method Reading Notes 05

Today, I have read chapter 14, 12th, 13, and 14 of the Building Law. Chapter 5 mainly introduces the user experience. In fact, in my opinion, user experience is the deciding factor to determine whether a software is successful. Because the software serves the user, only the user feels that it is easy to use, only when software has a market can it have value. The book details how to improve users' preference for software, that is, to improve user experience. First, we need to take the first impression of the user. To do this, we need to consider two points: Who is our user? Different users naturally have different requirements on the interface, therefore, we must first consider our user groups. In addition, we also need to consider the bold "subtraction" of the software, that is, try to make the user spend less time on the part that has no value to the user for the first time, most of the time is spent on practical functions. To achieve this, we must consider the problem from the user's perspective, that is, the ability to understand the situation, psychology, and motivation of others. Avoid being horizontally visible to show that our software has several advanced options. During software design, we need to make the software always remember the user's choice. because there are only a few options for users, we need to make the software remember to use it more quickly.

To make the software more useful. Like small remote control on an airplane, we must make our software so that users do not make simple mistakes. This is also a key factor that determines the user experience.

Chapter 2 describes software testing. Software testing is an essential part of the software design process. In the book, software testing is based on the test design method. The functional classification of testing is soft. We are more familiar with software testing. Various software testing methods are also described in detail: unit testing, code coverage testing, construction verification testing, acceptance testing, scenario testing report, exploratory testing, and regression testing, scenario/integration/system testing, partner testing, performance testing, stress testing, internal/external public testing, usability testing, etc, the book introduces the content of each test, which gives me a better understanding of software testing. For software testing, we should not only conduct tests, but also record the test content, write the tests as documents and reports, and conduct frequent software testing experience exchanges to share their testing methods and errors. The book says that software has different testing methods in different development lifecycles. In the vision and planning stages, testing is only in the planning stage. We will discuss the test plan and test design specification, collect users' non-functional requirements for software, such as performance, availability, and internationalization. In addition, you can also preliminarily arrange some testing jobs of the "small and strong" type; development stage; developers need to write unit tests, testers need to write BVT; stability stage: at the end of a development stage, the test team can perform acceptance tests on the software one by one based on the previously established acceptance criteria. Release Phase: The test team should automate as many test cases as possible, prepare for the testing of the next version.

After reading these two chapters, I have a deep understanding of user experience and software testing.

Building Method Reading Notes 05