The law of Construction read Note--5

The typical user should analyze from different angles, that is, the project has different requirements and specific requirements. Defining the initial typical user does not mean that you can start to develop software, we still need to communicate with them, "Create a scene" is to understand the user's needs in the process. After that there is a scene to start the task, in order to let others know the role of your software, specification is a good way. The specification is of great help to our project development. Its writing is also written from the user's point of view. Specifications can also be divided into software functional specifications and software technical description said. The software manual is used to explain the external function of the software and the user's interaction, the software specification is also called the document, mainly used to illustrate the internal design of the software specifications. This is not a moment can be written well, is through practice can write good specifications. This is the first step in letting users know their software first.

Software ( quality ) = Program ( quality ) + Software Engineering ( quality ) software companies often use CMMI ratings to measure the quality of software engineering in each organization, and quality Assurance (QA) differs from software testing (testing). When the role of the test to separate out, will expose the problem, which is my recent problems ———— since there is someone responsible, then I will not be responsible. CMMI (Capacity Maturity Model inegrated, Competency Model integration) models not only reduce project costs, but also improve project quality and schedule completion rates. The cost of quality consists of the following parts: prevention, evaluation, internal failure, external failure, process analysis and improvement. Software testing is also a big problem, we want to ① although there is a person responsible for software testing, but to ensure that quality is still the responsibility of all members, do not trust the "professional", or to have a person to check the quality of independent, do not fully focus on their performance and optimization, which will lead to local optimal and global not necessarily the situation, What we should do, should put the overall position in the first place, do not rigidly adhere to the restricting division of labor, no clear responsibility for the division of labor. Only in this way, we make the software to be quality assurance, to meet the needs of users.

Experience: In these chapters we understand that in the real testing of our software is the release phase of software, only software maintenance with timely software to more long-term application. At this stage, there are a variety of software, and perhaps innovation is becoming more and more difficult, but as it industry innovation is still necessary. Software quality can be described as the fundamental software project, if the quality of a software is not guaranteed, we also how to achieve the user's needs, we work is meaningless to say. We want to be in the engineering process, in every part, no size, as far as possible to the highest level to complete, and do not just focus on their performance, but to the entire team, the overall quality of the first place

The law of Construction read Note--5