CN114444916A - Research and development process improvement method and system based on full-quality characteristics - Google Patents
Research and development process improvement method and system based on full-quality characteristics Download PDFInfo
- Publication number
- CN114444916A CN114444916A CN202210071581.2A CN202210071581A CN114444916A CN 114444916 A CN114444916 A CN 114444916A CN 202210071581 A CN202210071581 A CN 202210071581A CN 114444916 A CN114444916 A CN 114444916A
- Authority
- CN
- China
- Prior art keywords
- project
- product
- node
- quality
- tracking
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06313—Resource planning in a project environment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0639—Performance analysis of employees; Performance analysis of enterprise or organisation operations
- G06Q10/06393—Score-carding, benchmarking or key performance indicator [KPI] analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0639—Performance analysis of employees; Performance analysis of enterprise or organisation operations
- G06Q10/06395—Quality analysis or management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/20—Administration of product repair or maintenance
Landscapes
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Engineering & Computer Science (AREA)
- Strategic Management (AREA)
- Economics (AREA)
- Entrepreneurship & Innovation (AREA)
- Development Economics (AREA)
- Educational Administration (AREA)
- Operations Research (AREA)
- Marketing (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Game Theory and Decision Science (AREA)
- Life Sciences & Earth Sciences (AREA)
- Biodiversity & Conservation Biology (AREA)
- Stored Programmes (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention discloses a research and development process improvement method and system based on full-quality characteristics, wherein the method comprises the steps of S1, setting a milestone node of a project; s2, designing and tracking the special quality characteristics according to the user requirements; s3, designing and tracking all the characteristics of the universal quality characteristics; s4, designing and tracking competitive characteristics; and S5, designing and tracking the overrunning characteristic. The advantages are that: the software and hardware project research and development management process is controlled by an informatization tool and by combining a full quality characteristic and an IPD thought, and various general quality characteristics, special quality characteristics, competitive characteristics and transcendental characteristics are fully considered, designed, implemented and accepted in the software and hardware project development process. The method realizes smooth interaction and sharing of index characteristics in the research and development management process, and assists project managers to integrate full-quality characteristics, research and development management.
Description
Technical Field
The invention relates to the technical field of informatization research and development management, in particular to a research and development process improvement method and system based on full-quality characteristics.
Background
The definition of quality is the degree to which a set of intrinsic properties meets the requirements, in other words the satisfaction of the user's needs. For various software and hardware product projects, the characteristics can be divided into two parts, namely special characteristics and general characteristics, wherein the special characteristics are individual characteristics reflecting the characteristics of different types of projects, and the general characteristics are common characteristics reflecting different projects. Table 1 shows general and specific characteristics of some representative software and hardware projects, which are mainly used for guiding improvement of various software and hardware development processes and evaluating project development capacity. The improvement of productivity and the improvement of product quality are greatly promoted. The implementation of the development of the full-characteristic software and hardware projects is beneficial to improving the acceptance of enterprises in the market.
Table 1: universal and special quality characteristic table for software and hardware items
The characteristic-based software and hardware project research and development helps research and development personnel to realize high-quality delivery by virtue of rich and comprehensive ideas and fully saturated contents. However, for a general project manager, the above characteristic indexes are too complex and difficult to be considered, and it is difficult to plan and sufficiently control each index of a product in the project practice.
Disclosure of Invention
The invention aims to provide a research and development process improvement method and system based on full-quality characteristics, so as to solve the problems in the prior art.
In order to achieve the purpose, the technical scheme adopted by the invention is as follows:
a development process improvement method based on full-quality characteristics comprises the following steps,
s1, setting a milestone node of the project; the method comprises an item establishing node, a demand node, a design node, a development node, a test node and an acceptance release node;
s2, designing the special quality characteristics according to the user requirements, and continuously tracking each milestone node of the project;
s3, designing and tracking all the characteristics of the universal quality characteristics; the universal quality characteristics comprise safety, security, testability, reliability and maintainability;
s4, designing and tracking competitive characteristics; the competitive property is ease of operation;
s5, designing and tracking the overrunning characteristic; the override characteristic is user satisfaction;
s6, automatically reminding a user to fill in related data and information according to the links set in the design and tracking of the characteristics, and automatically reminding the user to solve the conflict when meeting the filling conflict of different quality characteristics; when the filling value is inconsistent with the plan set by the user, reminding the user to check the filling data; if the filled data do not accord with the design values, starting an approval process and requiring a project principal to revise the corresponding quality characteristic design; when the project is finished, all quality characteristic indexes are required to meet the design value, otherwise, the project cannot be finished.
Preferably, step S3 specifically includes the following steps,
s31, designing and tracking safety; the specific process is that,
a1, describing a safety working range as required, and establishing links between each safety index point and the special quality characteristics and other related characteristics of the items;
a2, creating a safety work milestone node of a project;
a3, carrying out technical description on the security index points of the established link;
a4, storing related links for checking and checking the achievement condition of the security index point by each milestone node of the project;
s32, designing and tracking the security; the specific process is that,
b1, setting a comprehensive guarantee mechanism and a comprehensive guarantee management group in the project;
b2, specifying and linking the integrated assurance plan to the project's specific quality characteristics and other relevant characteristics; b3, giving qualitative and quantitative requirements for guarantee;
b4, storing the related links for checking and checking the guaranteed qualitative and quantitative requirement achievement conditions of each milestone node of the project;
s33, designing and tracking the testability; the specific process is that,
c1, selecting a test index from the special quality characteristics and other quality characteristics of the project;
c2, selecting a detection period and/or a trigger node for the selected test index, and establishing a link with the special quality characteristic and other related characteristics of the project;
c3, storing related links for checking the achievement condition of the test index by triggering each milestone node of the node or project, and updating the testability prediction list according to the checking result;
s34, designing and tracking reliability; the specific process is that,
d1, making a reliability guarantee plan and linking the reliability guarantee plan to the special quality characteristics and other relevant characteristics of the project;
d2, giving qualitative and quantitative requirements on reliability;
d3, storing the related links for checking and checking the achievement conditions of qualitative and quantitative requirements of each milestone node of the project on reliability;
s35, designing and tracking maintainability;
e1, entering a planned maintenance node and giving a repairability maintenance scheme, developing project maintainability management, and linking the project maintainability management to the special quality characteristics and other related characteristics of the project;
e2, saving the related links for each milestone node of the project to remind and/or use the repairability maintenance scheme when the project has repair problems.
Preferably, step a2 specifically includes the following steps,
a21, establishing a set-up node, a running node, a checking node and an improvement node of a project safety work organization;
a22, creating security management nodes of project re-acceptors and suppliers in each stage of selection, operation or arrival, quality and after-sale;
a23, creating security and risk management nodes of each stage of the project;
a24, creating safety report requirements and nodes of each node of a project;
a25, creating safety training nodes of each stage of the project.
Preferably, step a3 specifically includes,
the explicit qualitative requirement is: from the use efficiency and the use adaptability of the product, corresponding technical requirements, design principles and risk acceptance criteria are provided for the design of the product to ensure the safety of the product;
the quantitative requirement is clear: the following quantitative requirements for safety parameters are given,
the rate of accidents; the ratio of the total number of accidents of the product to the total number of life units of the product under specified conditions and within a specified time;
average inter-accident time; the ratio of the total number of life units of the product to the total number of product accidents under specified conditions and for a specified time;
the safety and reliability are high; the probability that the product does not have catastrophic accidents caused by product or equipment failure during the task execution under the specified conditions and within the specified time; the ratio of the time of the product not causing a disaster accident due to the failure of the product or equipment to the total number of the product executing task units in the process of executing the task;
the loss rate; the ratio of the total number of catastrophic events to the total number of units of product life under specified conditions and for a specified time.
Preferably, the qualitative and quantitative requirements for security in step B3 include quantitative and qualitative requirements for maintainability, reliability, standardization, component and part control, testability, survivability, security facilities, security equipment, and human resource elements.
Preferably, the test indexes in step C1 include a fault detection rate, a fault isolation rate, a fault latency time, a fault detection time, a fault isolation time, and a false alarm rate; and further guiding a user to fill in a testability prediction table, wherein the filling content comprises technical information such as function names, component names and models, identification numbers, fault rates, fault modes and fault mode frequency ratios, so as to give out testability prediction.
Preferably, the quantitative requirement for reliability in step D2 includes,
reliability; the probability that a product realizes a specified function under specified conditions and within specified time; the ratio of the difference between the total number of the test samples and the number of the failed products in the specified time to the total number of the test samples;
the failure rate; under the specified conditions and within the specified time, the ratio of the number of the failed products within the specified time to the total number of the test samples;
mean time between failures; the ratio of the total number of product life units to the total number of product failures under specified conditions and for a specified time;
qualitative requirements for reliability include the technical maturity of the product and whether the product can be modularized.
Preferably, step S4 specifically includes the following steps,
s41, setting indexes for the operability; the indexes specifically include the following indexes,
product description integrity index: the user can understand the proportion of the related functions after reading the product use instruction;
and (3) demonstration acquisition indexes: the user can obtain the frequency and proportion of product demonstration and guidance;
easy comprehensibility index of product function: the proportion at which the function of the product can be correctly understood by the user;
operating consistency index in use: namely the proportion of the consistent operation of the user in the product using process;
s42, linking the index of easy operability to the special quality characteristic of the project and other related characteristics;
s43, storing the related links for checking and verifying the achievement condition of the easy-operation index by each milestone node of the project;
preferably, step S5 is specifically to design the user satisfaction questionnaire investigation and investigation trigger time, link the user satisfaction investigation and investigation trigger time to the special quality characteristics and other related characteristics of the project, store the related links, and implement the user satisfaction questionnaire investigation by each milestone node of the project, and check and verify the achievement of the user satisfaction.
It is also an object of the present invention to provide a full quality characterization based development process improvement system for implementing any of the above methods, said system comprising,
a milestone node management module; the milestone nodes are used for setting projects and providing the milestone nodes for the linkage of various characteristics in different stages;
a dedicated quality characteristic management module; for designing and tracking the dedicated quality characteristics;
a universal quality characteristic management module; for designing and tracking generic quality characteristics
A competition characteristic management module; the system is used for designing and tracking competitive characteristics;
an override feature management module; for designing and tracking override characteristics.
An ending management module; the system is used for automatically reminding a user to fill in related data and information according to the links set in the design and tracking of the characteristics, and automatically reminding the user to solve conflicts when meeting filling conflicts with different quality characteristics; when the filling value is inconsistent with the plan set by the user, reminding the user to check the filling data; if the filled data do not accord with the design values, starting an approval process and requiring a project principal to revise the corresponding quality characteristic design; when the project is finished, all quality characteristic indexes are required to meet the design value, otherwise, the project cannot be finished.
The invention has the beneficial effects that: 1. based on the research and development process of full quality characteristics, an IPD research and development management system is fused, so that a project manager can be helped to establish comprehensive understanding and general consideration of a designed development project, and enterprises are helped to establish a research and development management mode of market guidance, collaboration of various quality characteristics and platformization; a large research and development management mechanism of 'comprehensive, whole-person and whole course' is formed, the universal quality characteristic, the competitive characteristic and the transcendental characteristic are used as the basis, the design and the tracking of the project management full quality characteristic are realized, and a hand grip is provided for an enterprise to realize the standardization, the visualization and the process of the research and development process full life cycle management. 2. An informatization tool is adopted, and the full quality characteristic and the IPD thought are combined to control the software and hardware project research and development management process, so that various general quality characteristics, special quality characteristics, competitive characteristics and surpassing characteristics in the software and hardware project development process are fully considered, designed, implemented and checked. The method realizes smooth interaction and sharing of index characteristics in the research and development management process, and assists project managers to integrate the full-quality characteristics, research and development management.
Drawings
FIG. 1 is a schematic diagram of a method in an embodiment of the invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is further described in detail below with reference to the accompanying drawings. It should be understood that the detailed description and specific examples, while indicating the invention, are intended for purposes of illustration only and are not intended to limit the scope of the invention.
Example one
In the embodiment, as shown in fig. 1, there is provided a development process improvement method based on full quality characteristics, including the following steps,
s1, setting a milestone node of the project; the method comprises an item establishing node, a demand node, a design node, a development node, a test node and an acceptance release node;
s2, designing the special quality characteristics according to the user requirements, and continuously tracking each milestone node of the project;
s3, designing and tracking all the characteristics of the universal quality characteristics; the universal quality characteristics comprise safety, security, testability, reliability and maintainability;
s4, designing and tracking competitive characteristics; the competitive property is ease of operation;
s5, designing and tracking the overrunning characteristic; the override characteristic is user satisfaction;
s6, automatically reminding a user to fill in related data and information according to the links set in the design and tracking of the characteristics, and automatically reminding the user to solve the conflict when meeting the filling conflict of different quality characteristics; when the filling value is inconsistent with the plan set by the user, reminding the user to check the filling data; if the filled data do not accord with the design values, starting an approval process and requiring a project principal to revise the corresponding quality characteristic design; when the project is finished, all quality characteristic indexes are required to meet the design value, otherwise, the project cannot be finished.
The method mainly comprises six parts of content, namely the setting of milestone nodes, the design and tracking of special quality characteristics, the design and tracking of general quality characteristics, the design and tracking of competitive characteristics, the design and tracking of transcendental characteristics and project conclusion evaluation management. The following provides a detailed description of these six sections.
Setting of milestone node
The partial content corresponds to step S1, specifically, six major milestone nodes including an item establishment node, a demand node, a design node, a development node, a test node, and an acceptance release node are set. The six milestone nodes are the main nodes of the project, and are used for linking each characteristic in different stages.
Second, design and tracking of specialized quality features
The partial content corresponds to step S2, which specifically includes the design of the special quality characteristics and the tracking of the special quality characteristics; the project team personnel plan and set according to the requirements of the user, and continuously track each stage (namely each milestone node) of project establishment, requirements, design, development, test, acceptance and life cycle management and the like.
The special quality characteristics are different from the general quality characteristics, which mainly refer to the relative hardness indexes of the product such as size, weight, material and the like, and the special quality characteristics are different among different products. The design and tracking of the special quality characteristics are mainly the following steps:
1. investigating the customer's requirements for specialized quality characteristics;
2. converting the special quality characteristic requirement of the user into a specification of the special quality characteristic requirement of the product;
3. carrying out summary design on the special quality characteristics;
4. designing the special quality characteristics in detail;
5. developing special quality characteristics;
6. and (5) verifying special quality characteristics.
Design and tracking of common quality characteristics
This section corresponds to step S3, and step S3 specifically includes design and tracking of safety, security, testability, reliability, and serviceability. The method comprises the following specific steps:
1. designing and tracking security; the specific process is that,
(1) describing a safety working range according to requirements, and establishing links between each safety index point and the special quality characteristic and other related characteristics of the project;
(2) creating a safety work milestone node of the project; the method mainly comprises the following steps:
establishing a set node, a running node, a checking node and an improved node of a project safety work organization;
creating security management nodes of the project re-accepting party and the project supplying party in each stage of selection, operation or arrival, quality and after-sale;
creating security and risk management nodes of each stage of the project;
creating safety report requirements and nodes of each node of the project;
and creating safety training nodes of each stage of the project.
(3) Carrying out technical description on the safety index points of the established links; specifically, the method comprises the following steps of (1) determining qualitative requirements and determining quantitative requirements;
the explicit qualitative requirement is: from the use efficiency and the use adaptability of the product, corresponding technical requirements, design principles and risk acceptance criteria are provided for the design of the product to ensure the safety of the product;
the quantitative requirement is clear: the following quantitative requirements for safety parameters are given,
the rate of accidents; the ratio of the total number of accidents of the product to the total number of life units of the product under specified conditions and within a specified time; is calculated by the formula
average inter-accident time; the ratio of the total number of life units of the product to the total number of product accidents under specified conditions and for a specified time; the calculation formula is as follows,
the safety and reliability are high; the probability that the product does not have catastrophic accidents caused by product or equipment failure during the task execution under the specified conditions and within the specified time; the ratio of the time of the product not causing a disaster accident due to the failure of the product or equipment to the total number of the product executing task units in the process of executing the task; the calculation formula is as follows,
the loss rate; the ratio of the total number of catastrophic events to the total number of units of product life under specified conditions and for a specified time; the calculation formula is as follows,
(4) And storing the related links for checking and checking the achievement condition of the safety index point by each milestone node of the project.
Allowing the user to customize the security parameters and check periods/nodes. The user can customize the related security parameters and the checking period according to the actual requirements.
2. Designing and tracking the security, assisting a user in considering the relationship between the security index and the product design, determining the optimal index matching of the product, and tracking the corresponding design index; the specific process is that,
(1) setting a comprehensive guarantee mechanism and a comprehensive guarantee management group in the project;
(2) specifying and linking a comprehensive assurance plan to the special quality characteristics of the project and other relevant characteristics;
(3) giving out qualitative and quantitative requirements of guarantee; the guaranteed qualitative and quantitative requirements include those for maintainability, reliability, standardization, component and part control, testability, survivability, guaranteed facilities, guaranteed equipment, and human resource elements;
qualitative requirements for serviceability include: safe product maintenance and repairability of parts. The quantitative requirements for serviceability include: average repair time, average system recovery time, maintenance man-hour, fault detection rate, fault isolation rate and false alarm rate.
Qualitative requirements for reliability include: technical maturity, whether modular. The quantitative requirements for reliability include: reliability, failure rate, mean time between failures;
the qualitative requirements for normalization include: and evaluating whether the evaluation is timely, moderate, equivalent and advanced. The standardized quantitative requirements include: normalized number coefficient, normalized number of pieces coefficient.
Qualitative requirements for component control requirements include: component modularization level, component availability level and component localization level. The quantitative requirements for component control include: component-related specifications (different for each component).
Qualitative requirements for testability include: testability design bias, test point design principle, which technical files to comply with, which technical files to output. Quantitative requirements for testability include: fault detection rate, fault isolation rate, fault latency, fault detection time, and fault isolation time.
Qualitative requirements for survivability: readiness integrity, availability, readiness rate. Quantitative requirements for viability include: survival time in wartime, locomotor activity rate and locomotor activity intensity.
Qualitative requirements for safeguarding facilities: facility integrity. The quantitative requirements of the support facility include: time of war survival time.
Ensuring the qualitative requirement of the equipment: equipment integrity. The quantitative requirements of the support equipment include: time of war survival time.
Qualitative requirements of human resources: structural integrity of human resources and sufficiency of human resource backup. Quantitative requirements for human resources include: quantity, manpower resources training qualification rate.
(4) And storing the related links for checking and checking the qualitative requirement and quantitative requirement achievement condition of each milestone node of the project on the guarantee.
And automatically checking the relation of maintainability, reliability and testability requirements in the guarantee for the linked special quality characteristics and other quality characteristics, and automatically reminding and solving the same indexes of nodes at the same stage and the same time of product design and development when encountering conflicts.
3. Designing and tracking the testability; the specific process is that,
(1) selecting a test index from the special quality characteristics and other quality characteristics of the project; the test indexes comprise fault detection rate, fault isolation rate, fault latency time, fault detection time, fault isolation time and false alarm rate; further guiding a user to fill in a testability prediction table, wherein the filling content comprises technical information such as function names, component names and models, identification numbers, fault rates, fault modes and fault mode frequency ratios, so as to give out testability prediction;
(2) selecting a detection period and/or a trigger node for the selected test index, and establishing a link with the special quality characteristic and other related characteristics of the project;
(3) storing related links for checking the achievement condition of the test indexes by triggering each milestone node of the nodes or projects, and updating a testability prediction list according to the checking result;
4. designing and tracking reliability; the specific process is that,
(1) establishing a reliability guarantee plan and linking the reliability guarantee plan to the special quality characteristics and other related characteristics of the project;
(2) giving qualitative and quantitative requirements for reliability; the quantitative requirements for reliability include that,
reliability; the probability that a product realizes a specified function under specified conditions and within specified time; the ratio of the difference between the total number of the test samples and the number of the failed products in the specified time to the total number of the test samples; the calculation formula is as follows,
the failure rate; under the specified conditions and within the specified time, the ratio of the number of the failed products within the specified time to the total number of the test samples; the calculation formula is as follows,
mean time between failures; the ratio of the total number of product life units to the total number of product failures under specified conditions and for a specified time;
qualitative requirements for reliability include the technical maturity of the product and whether the product can be modularized.
(3) Storing the related links for checking and checking the achievement conditions of qualitative requirements and quantitative requirements of each milestone node of the project on reliability;
5. designing and tracking maintainability;
(1) entering a planned maintenance node and giving a repairability maintenance scheme, developing project maintainability management, and linking the project maintainability management to the special quality characteristics and other related characteristics of the project;
(2) and storing the related links for each milestone node of the project to remind and/or use a repairable maintenance scheme when the project has repair problems.
When each milestone node of the project checks and checks the related quality characteristic indexes, whether the qualitative requirement is in accordance with the preset qualitative requirement or not is checked, and whether the quantitative requirement is in accordance with the set value or the error between the quantitative requirement and the set value is in an acceptable range is checked.
Fourth, design and tracking of competition characteristics
This section corresponds to step S4, and step S4 specifically includes the following,
1. setting an index for the operability; the indexes specifically include the following indexes,
product description integrity index: the user can understand the proportion of the related functions after reading the product use instruction;
and (3) demonstration acquisition indexes: the user can obtain the frequency and proportion of product demonstration and guidance;
easy comprehensibility index of product function: the proportion at which the function of the product can be correctly understood by the user;
operating consistency index in use: namely the proportion of the consistent operation of the user in the product using process;
2. linking the indicator of ease of operation to the specific quality characteristic of the project and other related characteristics;
3. storing related links to check and verify the achievement condition of the easy-operability index by each milestone node of the standby project;
fifthly, design and tracking of transcendental characteristics
The process corresponds to the content of step S5, and step S5 is specifically to design the user satisfaction questionnaire and the investigation trigger time, link the user satisfaction questionnaire and the investigation trigger time to the special quality characteristics and other related characteristics of the project, save the related links, and implement the user satisfaction questionnaire investigation by each milestone node of the project, and check and verify the achievement of the user satisfaction.
Sixthly, project result evaluation management
Automatically reminding a user to fill in relevant data and information according to the link set in the characteristic design and tracking, and automatically reminding the user to solve the conflict when meeting the filling conflict of different quality characteristics; when the filling value is inconsistent with the plan set by the user, reminding the user to check the filling data; if the filled data do not accord with the design values, starting an approval process and requiring a project principal to revise the corresponding quality characteristic design; when the project is finished, all quality characteristic indexes are required to meet the design value, otherwise, the project cannot be finished. Thereby ensuring that the proprietary, generic quality features, competitive features and override features of all projects developed are designed, tracked and meet the relevant requirements.
The full quality characterization statistics of the present invention are shown in table 2:
TABLE 2 Total Mass Property statistics
Example two
In this embodiment, there is provided a full quality feature based development process improvement system for implementing the method, the system comprising,
a milestone node management module; the milestone nodes are used for setting projects and providing the milestone nodes for the linkage of various characteristics in different stages;
a dedicated quality characteristic management module; for designing and tracking the dedicated quality characteristics;
a universal quality characteristic management module; for designing and tracking generic quality characteristics
A competition characteristic management module; the system is used for designing and tracking competitive characteristics;
an override feature management module; for designing and tracking override characteristics.
An ending management module; the system is used for automatically reminding a user to fill in related data and information according to the links set in the design and tracking of the characteristics, and automatically reminding the user to solve conflicts when meeting filling conflicts with different quality characteristics; when the filling value is inconsistent with the plan set by the user, reminding the user to check the filling data; if the filled data do not accord with the design values, starting an approval process and requiring a project principal to revise the corresponding quality characteristic design; when the project is finished, all quality characteristic indexes are required to meet the design value, otherwise, the project cannot be finished.
By adopting the technical scheme disclosed by the invention, the following beneficial effects are obtained:
the invention provides a research and development process improvement method and a system based on full-quality characteristics, the method is based on the research and development process of the full-quality characteristics, an IPD research and development management system is fused, a project manager can be helped to establish comprehensive understanding and general consideration of a designed development project, and enterprises are helped to establish a research and development management mode of market guidance, collaboration of each quality characteristic and platformization; a large research and development management mechanism of 'comprehensive, whole-person and whole course' is formed, the universal quality characteristic, the competitive characteristic and the transcendental characteristic are used as the basis, the design and the tracking of the project management full quality characteristic are realized, and a hand grip is provided for an enterprise to realize the standardization, the visualization and the process of the research and development process full life cycle management. The method adopts an informatization tool and combines the full quality characteristic and the IPD thought to manage and control the software and hardware project research and development management flow, thereby ensuring that various general quality characteristics, special quality characteristics, competitive characteristics and transcendental characteristics are fully considered, designed, implemented and accepted in the software and hardware project development process. The method realizes smooth interaction and sharing of index characteristics in the research and development management process, and assists project managers to integrate full-quality characteristics, research and development management.
The foregoing is only a preferred embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and improvements can be made without departing from the principle of the present invention, and such modifications and improvements should also be considered within the scope of the present invention.
Claims (10)
1. A research and development process improvement method based on full-quality characteristics is characterized by comprising the following steps: comprises the following steps of (a) carrying out,
s1, setting a milestone node of the project; the method comprises an item establishing node, a demand node, a design node, a development node, a test node and an acceptance release node;
s2, designing the special quality characteristics according to the user requirements, and continuously tracking each milestone node of the project;
s3, designing and tracking all the characteristics of the universal quality characteristics; the universal quality characteristics comprise safety, security, testability, reliability and maintainability;
s4, designing and tracking competitive characteristics; the competitive property is ease of operation;
s5, designing and tracking the overrunning characteristic; the override characteristic is user satisfaction;
s6, automatically reminding a user to fill in related data and information according to the links set in the design and tracking of the characteristics, and automatically reminding the user to solve the conflict when meeting the filling conflict of different quality characteristics; when the filling value is inconsistent with the plan set by the user, reminding the user to check the filling data; if the filled data do not accord with the design values, starting an approval process and requiring a project principal to revise the corresponding quality characteristic design; when the project is finished, all quality characteristic indexes are required to meet the design value, otherwise, the project cannot be finished.
2. The full quality feature based development process improvement method according to claim 1, characterized in that: the step S3 specifically includes the following contents,
s31, designing and tracking safety; the specific process is that,
a1, describing a safety working range as required, and establishing links between each safety index point and the special quality characteristics and other related characteristics of the items;
a2, creating a safety work milestone node of a project;
a3, carrying out technical description on the security index points of the established link;
a4, storing related links for checking and checking the achievement condition of the security index point by each milestone node of the project;
s32, designing and tracking the security; the specific process is that,
b1, setting a comprehensive guarantee mechanism and a comprehensive guarantee management group in the project;
b2, specifying and linking the integrated assurance plan to the project's specific quality characteristics and other relevant characteristics;
b3, giving qualitative and quantitative requirements for guarantee;
b4, storing the related links for checking and checking the guaranteed qualitative and quantitative requirement achievement conditions of each milestone node of the project;
s33, designing and tracking the testability; the specific process is that,
c1, selecting a test index from the special quality characteristics and other quality characteristics of the project;
c2, selecting a detection period and/or a trigger node for the selected test index, and establishing a link with the special quality characteristic and other related characteristics of the project;
c3, storing related links for checking the achievement condition of the test index by triggering each milestone node of the node or project, and updating the testability prediction list according to the checking result;
s34, designing and tracking reliability; the specific process is that,
d1, making a reliability guarantee plan and linking the reliability guarantee plan to the special quality characteristics and other relevant characteristics of the project;
d2, giving qualitative and quantitative requirements on reliability;
d3, storing the related links for checking and checking the achievement conditions of qualitative and quantitative requirements of each milestone node of the project on reliability;
s35, designing and tracking maintainability;
e1, entering a planned maintenance node and giving a repairability maintenance scheme, developing project maintainability management, and linking the project maintainability management to the special quality characteristics and other related characteristics of the project;
e2, saving the related links for each milestone node of the project to remind and/or use the repairability maintenance scheme when the project has repair problems.
3. The full quality feature based development process improvement method according to claim 1, characterized in that: step a2 specifically includes the following,
a21, establishing a set-up node, a running node, a checking node and an improvement node of a project safety work organization;
a22, creating security management nodes of project re-acceptors and suppliers in each stage of selection, operation or arrival, quality and after-sale;
a23, creating security and risk management nodes of each stage of the project;
a24, creating safety report requirements and nodes of each node of a project;
a25, creating safety training nodes of each stage of the project.
4. The full quality feature based development process improvement method according to claim 1, characterized in that: the step a3 specifically includes the steps of,
the explicit qualitative requirement is: from the use efficiency and the use adaptability of the product, corresponding technical requirements, design principles and risk acceptance criteria are provided for the design of the product to ensure the safety of the product;
the quantitative requirement is clear: the following quantitative requirements for safety parameters are given,
the rate of accidents; the ratio of the total number of accidents of the product to the total number of life units of the product under specified conditions and within a specified time;
average inter-accident time; the ratio of the total number of life units of the product to the total number of product accidents under specified conditions and for a specified time;
the safety and reliability are high; the probability that the product does not have catastrophic accidents caused by product or equipment failure during the task execution under the specified conditions and within the specified time; the ratio of the time of the product not causing a disaster accident due to the failure of the product or equipment to the total number of the product executing task units in the process of executing the task;
the loss rate; the ratio of the total number of catastrophic events to the total number of units of product life under specified conditions and for a specified time.
5. The full quality feature based development process improvement method according to claim 1, characterized in that: the qualitative and quantitative requirements for the security in step B3 include quantitative and qualitative requirements for maintainability, reliability, standardization, component and part control, testability, survivability, security facilities, security equipment, and human resource elements.
6. The full quality feature based development process improvement method according to claim 1, characterized in that: the test indexes in the step C1 include a fault detection rate, a fault isolation rate, a fault latency time, a fault detection time, a fault isolation time, and a false alarm rate; and further guiding a user to fill in a testability prediction table, wherein the filling content comprises technical information such as function names, component names and models, identification numbers, fault rates, fault modes and fault mode frequency ratios, so as to give out testability prediction.
7. The full quality feature based development process improvement method according to claim 1, characterized in that: the quantitative requirement for reliability in step D2 includes,
reliability; probability that a product achieves a specified function under specified conditions and within a specified time; the ratio of the difference between the total number of the test samples and the number of the failed products in the specified time to the total number of the test samples;
the failure rate; under the specified conditions and within the specified time, the ratio of the number of the failed products within the specified time to the total number of the test samples;
mean time between failures; the ratio of the total number of product life units to the total number of product failures under specified conditions and for a specified time;
qualitative requirements for reliability include the technical maturity of the product and whether the product can be modularized.
8. The full quality feature based development process improvement method according to claim 1, characterized in that: the step S4 specifically includes the following contents,
s41, setting indexes for the operability; the indexes specifically include the following indexes,
product description integrity index: the user can understand the proportion of the related functions after reading the product use instruction;
and (3) demonstration acquisition indexes: the user can obtain the frequency and proportion of product demonstration and guidance;
easy comprehensibility index of product function: the proportion at which the function of the product can be correctly understood by the user;
operating consistency index in use: namely the proportion of the consistent operation of the user in the product using process;
s42, linking the index of easy operability to the special quality characteristic of the project and other related characteristics;
s43, saving the related links for checking and checking the achievement of the easy operation index by each milestone node of the project.
9. The full quality feature based development process improvement method according to claim 1, characterized in that: step S5 is specifically to design the user satisfaction questionnaire investigation and investigation trigger time, link the user satisfaction investigation and investigation trigger time to the special quality characteristics and other relevant characteristics of the project, store the relevant links, and implement the user satisfaction questionnaire investigation by each milestone node of the project, and check and verify the achievement of the user satisfaction.
10. A research and development process improvement system based on full-quality characteristics is characterized in that: a system for implementing the method of any of the preceding claims 1 to 9, the system comprising,
a milestone node management module; the milestone nodes are used for setting projects and providing the milestone nodes for the linkage of various characteristics in different stages;
a dedicated quality characteristic management module; for designing and tracking the dedicated quality characteristics;
a universal quality characteristic management module; for designing and tracking generic quality characteristics
A competition characteristic management module; the system is used for designing and tracking competitive characteristics;
an override feature management module; for designing and tracking override characteristics.
An ending management module; the system is used for automatically reminding a user to fill in related data and information according to the links set in the design and tracking of the characteristics, and automatically reminding the user to solve conflicts when meeting filling conflicts with different quality characteristics; when the filling value is inconsistent with the plan set by the user, reminding the user to check the filling data; if the filled data do not accord with the design values, starting an approval process and requiring a project principal to revise the corresponding quality characteristic design; when the project is finished, all quality characteristic indexes are required to meet the design value, otherwise, the project cannot be finished.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210071581.2A CN114444916A (en) | 2022-01-21 | 2022-01-21 | Research and development process improvement method and system based on full-quality characteristics |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210071581.2A CN114444916A (en) | 2022-01-21 | 2022-01-21 | Research and development process improvement method and system based on full-quality characteristics |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114444916A true CN114444916A (en) | 2022-05-06 |
Family
ID=81368703
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210071581.2A Pending CN114444916A (en) | 2022-01-21 | 2022-01-21 | Research and development process improvement method and system based on full-quality characteristics |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114444916A (en) |
-
2022
- 2022-01-21 CN CN202210071581.2A patent/CN114444916A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| e Abreu et al. | Evaluating the impact of object-oriented design on software quality | |
| Kitchenham | Towards a constructive quality model. Part 1: Software quality modelling, measurement and prediction | |
| Buckley et al. | Software quality assurance | |
| Kontogiannis | Stress and operator decision making in coping with emergencies | |
| CN110347580A (en) | A method of building non-embedded software reliability test process model | |
| CN103077109B (en) | A kind of test plan dispatching method and system | |
| Weaver et al. | A pragmatic approach to reasoning about the assurance of safety arguments | |
| CN110531608B (en) | High-reliability electronic equipment quantitative FMECA analysis method and system based on redundancy design | |
| CN114444916A (en) | Research and development process improvement method and system based on full-quality characteristics | |
| CN116738642B (en) | Collaborative simulation platform of pipe network system | |
| CN201974848U (en) | Management system for comprehensively arranging and executing maintenance plan of production equipment | |
| CN116051070A (en) | Ship maintenance progress management system | |
| Li et al. | Integrating Software into PRA: A Test‐Based Approach | |
| CN114781991A (en) | Process modeling method for multi-level business activity management | |
| Solovyev | Methodology for Reliability Assessment of Industrial Control Systems | |
| Zhang et al. | Integrated Requirements Management of Civil Aircraft | |
| US20050273691A1 (en) | Metadata system for tracking quality processes | |
| Gore et al. | A limited assessment of the ASEP Human reliability analysis procedure using simulator examination results | |
| United States. Government Accountability Office et al. | Global Positioning System: Updated Schedule Assessment Could Help Decision Makers Address Likely Delays Related to New Ground Control System: Report to Congressional Committees | |
| Hamilton | Accounting for evidence: managing evidence for goal based software safety standards | |
| Carozzoni et al. | Initial Definition of a Knowledge-Based Software Quality Assistant | |
| ANDREEVA et al. | STANDARDIZATION OF THE LIFE CYCLE OF AN INFORMATION SYSTEM | |
| KNOWLEDGEBASED | R L-TR-93-28 tI. IIII. It II IIV I1I | |
| CRALLEY et al. | Computer Support for Conducting Supportability Trade-offs in a Team Setting | |
| Futschik et al. | Application of evaluation model |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |