Self-study Impressions 5-ch12 to CH15

In the process of software design, the user experience is very important. Developers to design the software, if you want to get a good promotion, it is necessary to make users feel the operation is simple, we can from the visual, auditory, tactile and so on to make users feel the UI interface design beauty. The user experience has one element: The user first impression, is more important. In my personal use of the mobile app, I just started using an app, I want to see a clear functional partition, if the first use can have an operating guide, it will make me faster to accept the use of the app. When I feel the use of the app has many convenient, or interesting features, it will be recommended to the surrounding friends.

I have learned from the case of how not to allow users to make simple mistakes: Solving the user's ability to manipulate product functionality can be confusing or even fatal, and when we are designers, consider whether the user is friendly to the use of these features. In the product development and design, will delve into the details of the interface design. "Details determine success or failure" This sentence is a certain alert role. When users are using the product, they may encounter occasional situations, although the frequency of occurrence is relatively low, but if many users are concerned about a similar situation, then designers should pay attention to the design of the details of the changes.

The product design needs to let the user feel the control right, to the same kind of thing and the operation expression language to be consistent everywhere, the design product can apply to all kinds of users, when the user feels the convenience of use, will be long-term use the product development.

After the software design is completed, it should be tested in various ways. Some according to test design methods, and some according to the purpose of testing, and some according to the timing and role of testing. Each test has a certain scope of application. Software is not only to provide users with services, but also to provide users with a certain level of service, so the test needs to test the effectiveness of the software, is aimed at software non-functional requirements. In the performance test, must be in the actual environment, but do not need to simulate the random environment too much. The real environment is to avoid the difficulty of running software on a server with a load or a database with a large number of records, and excessive simulation of a random environment can result in significant cost savings.

Software quality emphasizes software to meet the needs of users and stakeholders, software development process is good, fast, cheap, in the development process, must pay attention to risk control. Measuring the quality of software engineering has a relatively mature theoretical cmmi. CMMI has five levels: initial level, management level, definition level, quantitative management level, optimization level. The lower level is a higher level, but its effectiveness in Internet business is more than traditional software needs to be further observed.

There are independent test roles in the software test. Independent professional testing is equivalent to the certification of the product. The use of software once connected to the network, security is relative. It is necessary to protect the user's information security. The clear division of labor is for the team to be able to complete product development efficiently, but does not represent the division of labor should be restricting. Only appropriate cooperation should be made so that the members of each section have a better understanding of the whole.

After reading the whole "building law", I have the following questions:

(1) is the innovation of the product really a methodical one? Because in some game development companies, some people say that the first time the designer's inspiration is recognized, slowly discover how to innovate. Does this mean that when we meet more similar products, we can find a place where we can innovate?

(2) When our team decides on a software development project, the biggest problem is not knowing what kind of project we should do. One member proposed that the other member would raise a corresponding objection. The result was a long period of time when consensus was not reached. How does this work? Just need a team member to run further?

(3) Measuring the quality of software engineering, there are many indicators, each indicator can be done very well, is it possible?

(4) The development of software engineering is inseparable from the business model, we see in real life a lot of similar products in the market vicious competition, how should we grasp the yardstick?

(5) Many software now use agile development process, but some products can not develop long-term use of users, and agile processes to reduce development time, is not enough time to spend, so that the product does not have a long-term presence in the market power? How to better weigh the cost and benefit of product development?

Self-study Impressions 5-ch12 to CH15