I. Introduction
With the continuous improvement of social informatization, the information industry has expanded rapidly, and information companies grow rapidly, and the information market brought is fierce. In order to survive, they have become the primary responsibility of all industries. Depending on the quality, cost and progress of customer satisfaction, quality is one of the key support, which requires us to enhance quality management needs. We all know that PMBOK is divided into 9 knowledge fields, namely range management, time management, cost management, quality management, human resource management, communication management, procurement management, risk management and integrated management. Quality Management As one of the 9 major fields, it is important to see its importance. Quality management includes: quality planning, quality assurance and quality control three process domains. The quality plan is the first process domain of quality management. It is mainly combined with the quality policy, product description, and quality standards and rules to formulate the implementation of the implementation, and its contents have a comprehensive reaction to the user's requirements. Providing guidelines for the effective work of Quality Panel, for project team members and project related personnel to understand how to implement quality assurance and control provides a solid foundation for ensuring that project quality is guaranteed. Quality assurance is a planned and systematic activity throughout the project full lifecycle, and often for evaluation, inspection and improvement of the implementation of the entire project quality plan, providing trust to managers, customers or others. Ensure that the project quality is consistent with the plan. Quality control is to detect, verify the results of phased, and provide a reference basis for quality assurance, which is a PDCA cycle process.
Two quality management responsibility allocation
Our company is produced in accordance with the production method of standardized software on the development project, and is carried out on the production process. In addition to the role of project development, each project is also specially equipped with configuration management team, test team, and quality assurance team to ensure quality management. The following describes: 1. Configuration Management Group Responsibilities Management The group is to ensure that the project is developed, the internal documentation and external documents are completed at the same time. The timely generation and standardization of internal documents is to ensure that the project development team is important for better interface and communication. From another aspect, it is also the premise that the work is not blocked by a critical path. As mentioned above, the configuration management team is also the basis for ensuring the quality assurance team to function. The main responsibilities of the configuration management team include improving the code to send and version control, documentation (including foreign files) and phased outcomes; controlling code, document, etc. Control; for all archived documents Version control; providing document specification and conveys into the development group. 2. Test Group Responsibilities Test Team as the main means of quality control, responsible for software test design and implementation. Like software development, testing before execution, it also needs to perform test plan and test strategy, usually testing can be divided into the following types, such as: correctness test, functional test, performance test, security test, and system Test, etc. These tests need to be described in the test plan and test strategy to guide the test team members to write and test execution. The programmer is a certain unit test before being handed over to the test, ensuring that the program is compiled, and the operation is correct. The tester is tested according to the detailed designed document, ensuring the implementation of the implementation of the implementation of the software, and only proves that the software is correctly reflected in design ideas, but does it really reflect the user's needs. There is still a need for further functional testing. The tester can only ensure that the software products developed by the project team meet the needs of user needs based on the functions mentioned by the Software Demand Specifications. After the correctness test is completed, it is necessary to test the performance of the software. The performance of the software plays an important role in this project. Performance requirements may change the design of the software, in order to avoid the software's post-rework, testing is more Large focus. If necessary, the test team also needs to do safety tests to ensure that the system is safe and reliable. 3. The Quality Assurance Group Responsibilities Quality Assurance Team as a Quality Assurance Implementation Group, the main responsibility is to ensure the main sections of software transparency development. Almost all departments in the process of project development are related to the Quality Assurance Team. The Quality Assurance Team provides the project manager to provide the difference in the project progress and the real development of the project, and propose differences and improvement methods. When the project progress is delayed or the Quality Assurance team, the necessary relevant personnel such as project managers and project leaders will hold a quality conference. Solve the current existing and potential issues. Quality assurance is based on the review of the documentation, so the document version is controlled, especially software configuration management, directly affects the influence and efforts of software quality assurance. The detection range of the Quality Assurance Group includes: whether the system analysts reflect the user's needs; whether the software executive is correctly realized by the analyst's design ideas; whether the tester has a more thorough test; configuration administrator Is there a comparison of the standardization of the document, whether the version control is valid. Three quality management implementation
With a good resource equip, how to implement quality assurance within the project full lifecycle, let us see the implementation process of quality assurance from the following aspects: 1. Quality assurance project progress is the best in the project Intuitive performance. Obviously, the project development plan is necessary before the project begins. If the project development plan is fully reasonable, the progress of the project truly expresses the distance between the project and the final delivery, but it is almost unlikely to develop a full and reasonable project development plan. It can be seen that the project is guaranteed, first ensuring that the project development plan is as reasonable. The reasonable level of the project plan is directly related to the experience of project plan makers engaged in similar sizes and similar business. Through experience, it is often foreseasted potential hindrance, so that the project plan makers need to collect people to improve their plan. When the project plan is established, the project plan review assignment held by the Quality Assurance Group organizes the company's technical experts, users, and project team members, and the members of the project plan will be discussed. The meeting usually uses the brainstorming method, and all expressions, will be given by the designated The recorder forms a quality record and is sent to the relevant personnel. It is revised to the relevant personnel, and the unreasonable places are revised and improved by quality assurance personnel to ensure that the project plan integrity, feasibility, and improved planning Configure the management personnel for version control. However, during the program implementation, the plan is not "fixed". It is often humanitarian, "plan to catch up", but "to keep up with changes." The project plan is bound to milestones, dividing the entire development cycle into a number of phases. According to the completion of the milestone, adjust the task amount of each smaller stage and the task time of each smaller stage, this way is very beneficial to the dynamic adjustment of the entire project plan. Also beneficial to the implementation of project quality assurance. In actual operation, when the Quality Association Focus on the implementation of the plan, the project manager reported that the project manager is responsible for periodically maintenance of the plan, and the programs that have been changed by the warranty team to assist the configuration management team completed version control. The company has developed the centralized customer service system of Hunan Mobile, and the subprojects in the development of the company have been six, which lasted for ten months. At present, the majority project has been developed, and the system is trial, and the project amount tens of millions of yuan. In such a project, from managers to developers to testers have accumulated a relatively rich experience, especially the development plan, and control of project progress. 2. Quality assurance of the project development A, demand analysis demand analysis is what developers need to do and how to do it and how to do. From the experience of system analysis, this process is often a step-by-step process, which is difficult to form a complete understanding of the formation of the system. Only confirming the confirmation of the customer's domain experts, can gradually understand the needs of users. From the process of system development, it is known that the error made when the system analysis will be multiplied in the next stage, the more expensive, the more expensive, the more expensive, the result of correcting the mistakes, Also, it also affects the quality of the system and the quality of the system. Method for resolving system analysis errors Our company usually uses invitation users to participate in demand assessment, and then the opinions of their users are tracked by warranty members to include the demand specifications. At the same time, they are signed with the user to confirm the formation requirements baseline, and the configuration administrator is put into it. Configure the management library. Although users participate in users as soon as possible, there is still no need to change the demand for users in the project. For changes in the development process, we require users to fill in the change application order to send to the project configuration administrator, transfer to the warranty team by configuring the configuentist, responsible for organizing expert group and project team members to discuss the feasibility and implementation of implementation changes Bringing the impact, small changes are directly recorded for change record reasons and risk items, and large changes need to form formal change reports, regardless of that changes require synchronization changes (including demand specifications) Instructions, detailed designs, installation manuals, operating manuals, etc.).
However, for the inclusion of the impact, it will lead to the progress of the progress. At this time, we will submit the change report to the user or invite the user to conduct a coordination meeting, discuss the change of the title or project progress. After the decision is changed, the project manager organizes changes, the test personnel detects the result of change, and the warranty team member supervises the implementation process and helps the configuration administrator to version control after the changed results. After the change is implemented, the specified person can help the user tested together with the user before the line can be on the line. b, the system design excellent architecture should have scalability and configurability, and a good architecture requires a good design method. Natural design selection has become a system design primary work. Which design method is good? ? For design selection, it is not possible, and it is necessary to analyze the structure of the project, the characteristics of the project, and the user's needs. It is also necessary to consider the quality of the members of the project team. If most of them have not been engaged in object-oriented design and projects For urgent times, there is no extra time to train team members to master object-oriented design methods, although we are well known to object-oriented design methods, we are not as good as the process-oriented approach (except for users to designate development and design) to reduce project assumptions. Technical risk. Our company has a project, and the user specifies that it needs to use object-oriented analysis, design and development, and short development cycle. In the case of rogue, the project team can only use the object-oriented software development process, because the project team is very small The development of the object, the lack of experience, leading to the project's post-programs, and the project did not achieve the expected results. In response to this development, we analyzed the reasons, found that the team members exchanged in new technologies in the development process, their respective understandings and ideas, causing inconsistency in understanding, resulting in high work repeatability, lagging project progress. The proposed solution is that the project team members use a centralized office, block learning, and the results of learning will immediately be released to the project-related personnel, and then the configuration administrator will organize the documentation issued by the administrator, and the registration is placed in the configuration library for everyone to share. This makes it easy to learn from each other and reduce duplicate work. In this development, our company has learned a lot of lessons from the management personnel and designers to developers. At the same time, after the development of the project, the team members also accumulated rich object-oriented development experience. In addition to design selection, there is a problem that is easy to neglect, which is public class development. Public class development can reduce repetitive work in our work and reduce development costs. This requires our re-design phase through careful research on user needs, as much as possible to identify public categories, and conduct designated specialists responsible for notifying other designers to reduce duplicate work. For the design documentation provided by the project group, the quality assurance team organizes technical experts, project team designers, developers and testers for their design documents, and detect design documents on the feasibility of their next phase of work, timely discovery design. An error, reducing project development risks, and ensuring that design documents can provide practical guidance for developers and testers. Extraction of can be used as public library design and development, providing project groups or entire company reuse. Finally, the version control of the configuration administrator for design documents. C, implementation is also the production process of the code. Not only includes the generation of code, but also includes the generation of test cases. In response to the previous phase, the programmer begins to encode and debugging the program, and the tester is based on the design of the test case, and the designed use case needs to be approved by the project manager by the project manager to enter the configuration library. At the same time, the programmer debugged the program to submit the test personnel for proper detection. D, document management document maintenance is mainly to configure the management team's work. Documents From the purpose of the purpose, it is mainly divided into internal documents and external documents.
