Read Note 06

Thoughts on the follow-up chapters of the Law of construction

Read the following chapters of the law of Construction today, a book on software engineering knowledge, but the main content is not to teach readers how to program, but to tell what a real programmer should be, how a team can work collaboratively to write a software and process management programming.

The 33rd chapter tells the user experience, after the user installs the software, the software first launches, the software designer wants to give the user what kind of first impression? Users first come back to visit your website, what kind of first impression do you want to give them? Indeed some software functions are comprehensive, but if you do not pay attention to the user experience, destined to be eliminated by the market. And to do a good user experience, 1. We have to learn from the user's point of view 2. Software services always remember the user's Choice 3. To pay attention to short-term stimulation and long-term impact 4 do not let the user anti-simple error 5 also to balance the quality and user experience 6 to pay attention to emotional design needs to pay attention to the design of , in order to let some will draw a change on the line, but from the user's point of view, design the user interface. Then there is the standard for evaluating the user interface: 1. Provide a tactile feedback system Status 2 as soon as possible. The system interface conforms to the user's practical Practice 3. The user has control over 4. Consistency and standardization 5. Suitable for all types of users 6. Help users identify, diagnose, and fix error 7. Necessary tips and help documentation

In the 14th chapter, the 14th chapter is about the content of software quality. We know that software = program + Engineering. Then there is "the quality of the program" and "The Quality of software engineering" affect the quality. Software quality = 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 related to "fast" and "cheap", which requires a long-term process to improve. CMMI has now become a software evaluation standard used by many large software industry to improve the internal engineering of the organization.

The 15th chapter is about the software stability and release stage. A team has gone through the planning/design/development phases to achieve the goal of code completion, and it seems that the next thing is going to happen. In fact, the original plan of the software release time is coming, but the software is still a variety of problems, how to do? Each role representative (PM/DEV/TEST/UX, etc.) of the software team formed a consultation group to deal with every issue affecting the release of the product. Handle various bugs and so on. After the software is released, learn from the published software.

The 16th chapter focuses on the innovation of IT industry. Before reading, I thought that as long as there is innovation will be helpful to their own software, but after reading this chapter, I know that not all innovation can be applied immediately with your software, because some innovation will actually hinder your software, or even destroy the market you already have, so innovation is not random, to become an expert in this field, In order to innovate, you can guarantee that your innovation is helpful to your company and your products. One of the innovations in the software sector is the maintenance innovation, which means that companies cannot make disruptive innovations or make large-scale changes that must be considered carefully. Just like Win8 's interface changes make many people do not adapt, lost the market. Thus, innovation is not a simple matter.

Read Note 06