After users install the software, we need to consider the target users, what they want to achieve, as soon as possible to master the basic functions. How to efficiently implement functions that have real value when they are used for the first time. We need to consider from the user's point of view, software services always have to remember the user's choice, long-term use after the software is become difficult to use or useful. If long-term work in front of the computer, is short-term stimulation or long-term impact more prominent. Don't let the user make simple mistakes. If the user experience and product quality conflict, whether should sacrifice the quality to pursue the user experience, the design of the three levels, as well as the corresponding product characteristics: the level of instinct-shape, behavior level-the use of fun and efficiency, reflective level-self-image, personal satisfaction, memories, three layers of each other intertwined, Affect the user experience together. An important goal of user experience design is to reduce the cognitive resistance of users. There are 10 standards for the evaluation of software, see the "Law of construction" P258.
Software testing is divided into symptoms, procedural errors, and root causes. Test design classification methods: Black box and white boxes, according to the purpose of classification into functional and non-functional testing. Test methods include unit testing, code coverage testing, build verification testing, acceptance testing, exploratory testing, regression testing, scenario/integration/System testing, partner testing, performance testing, stress testing, internal/external public testing, usability testing, "Xiao Qiang" sweeps, testing concepts in combat, and documentation in test work. Using Test tools: Manual testing, automated testing, and the use of test performance.
Software quality = Program Quality + Software engineering quality, program quality is mainly embodied in the quality of external functions of software. The quality of software engineering is embodied in the visibility of the development process, the risk control in the development process, the internal module of the software, the quality delivery quality in the intermediate stage of the project, the factors of the project management tools, the control of the software development cost, and the completion of the internal quality index. The quality of software engineering is implemented as an evaluation standard by implementing CMMI. The role of the test should have a separate test role.
From code completion to release, the software team also performs more complex consultation work, including: the developer submits the consultation bug and the modification plan, the meeting decides whether to agree to revise the plan, executes. Tricks: Design changes, Zbb=zero bug BUILD, return to the final test, cut off the function, fixed the threshold of the bug gradually increased, gradually frozen. Hindsight meeting after publication. When should we start the user experience, and how to deal with detail issues? What are the user experience research methods? How to evaluate the quality of the user experience? How does a bug work? How to ensure quality?
User experience method of software engineering project