CN107678738A - A kind of method of software quality management - Google Patents

A kind of method of software quality management Download PDF

Info

Publication number
CN107678738A
CN107678738A CN201710963444.9A CN201710963444A CN107678738A CN 107678738 A CN107678738 A CN 107678738A CN 201710963444 A CN201710963444 A CN 201710963444A CN 107678738 A CN107678738 A CN 107678738A
Authority
CN
China
Prior art keywords
engineer
test
design
requirement
advanced
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
Application number
CN201710963444.9A
Other languages
Chinese (zh)
Inventor
隋云飞
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangzhou Huiruisitong Information Technology Co Ltd
Original Assignee
Guangzhou Huiruisitong Information Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Guangzhou Huiruisitong Information Technology Co Ltd filed Critical Guangzhou Huiruisitong Information Technology Co Ltd
Priority to CN201710963444.9A priority Critical patent/CN107678738A/en
Publication of CN107678738A publication Critical patent/CN107678738A/en
Pending legal-status Critical Current

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00Arrangements for software engineering
    • G06F8/20Software design
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/36Preventing errors by testing or debugging software
    • G06F11/3668Software testing
    • G06F11/3672Test management
    • G06F11/3684Test management for test design, e.g. generating new test cases

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Stored Programmes (AREA)

Abstract

The invention discloses a kind of method of software quality management, comprise the following steps:Research staff, according to the effect of different stage research staff in R&D process, is divided into business expert group, demand analysis group, software development group, software test group by S1, research staff's packet;S2, research staff's classification, according to the experience of research staff, ability quality, are divided into senior engineer, intermediate engineer, junior engineer by research staff;S3, establish 3 sets of quality management schemes, including prevention scheme, inspection scheme and response scheme;S4, management and control processes of research & development.Using technology provided by the present invention, by reasonably arranging research staff, research and development task, establish 3 sets of quality management schemes, and pass through strict management and control processes of research & development, supervise, confirm step by step step by step, find as early as possible and solve problem as much as possible, improve software quality, R&D costs are reduced, also promote research staff to feel hoisting power.

Description

A kind of method of software quality management
Technical field
The present invention relates to research and development of software technical field, and in particular to a kind of method of software quality management.
Background technology
At present, in general software company is divided into demand analysis, software development, software test to research and development of software personnel, grinds The hair personnel division of labor is clear and definite but is a lack of being connected, and does not also distribute research and development task by the ability of engineer, experience;Do not establish Kind quality management scheme;To processes of research & development also without the effective management and control of progress.
This just often leads to many software companys, and there are the following problems:Product quality is difficult stabilization, and client is using process In there are many problems, quality problems always repeat.Demand analysis personnel always complain that client is difficult to link up, scene description It is unintelligible, just find that demand model deviate from client's when complaining software not meet customer need after client is using software Application scenarios, so as to be changed to having audited the demand passed through temporarily;Developer always complains that demand frequently changes, and does not have Having time is once resolved problem, but having time recurrent Resolving probiems many times;Tester always embraces Blame program code quality too poor, can be drawn the defects of new again after repairing defect.New product or redaction are difficult to release on time, product Market can not be adapted to after release.Research staff's overtime work, still solves the problems, such as endless, causes customer satisfaction Degree reduces, and R&D costs increase.
The content of the invention
The invention aims to solve drawbacks described above of the prior art, there is provided a kind of side of software quality management Method, by reasonably arranging research staff, research and development task, 3 sets of quality management schemes are established, and stream is researched and developed by strict management and control Journey, supervise, confirm step by step step by step, find as early as possible and solve problem as much as possible, improve software quality, reduce R&D costs, Also research staff is promoted to feel hoisting power.
The purpose of the present invention can be reached by adopting the following technical scheme that:
A kind of method of software quality management, described method comprise the following steps:
S1, research staff's packet, according to the effect of different stage research staff in R&D process, are divided into research staff Business expert group, demand analysis group, software development group, software test group;
S2, research staff's classification, according to the experience of research staff, ability quality, by research staff be divided into senior engineer, Intermediate engineer, junior engineer;
S3,3 sets of quality management schemes are established, including it is pre- caused by problem for effectively being prevented in software development process Anti- scheme, the inspection for finding and solving problem as early as possible in software development process and the solution cost of problem is preferably minimized Scheme, for responding and solving as early as possible problem after software issue in favor of safeguarding the response scheme of the reputation of software product;
S4, management and control processes of research & development, it is specific as follows:
S41, advanced requirement engineer establish Requirements Analysis Model by requirement investigation, through the evaluation of business expert group by then Deliver intermediate requirement engineering Shi Jinhang business scenarios design;Evaluation is not by continuing then to establish Requirements Analysis Model;
Analysis model carries out business scenario design according to demand by S42, intermediate requirement engineering teacher, is examined through advanced requirement engineer Look into and write requirement documents by then delivering primary requirement engineering teacher;Check and do not designed by then continuing business scenario;
S43, primary requirement engineering teacher write requirement documents according to business scenario design, are checked by intermediate requirement engineering teacher By then delivering advanced Developmental Engineer;Check not by then continuing to write requirement documents;
Document carries out framework and Outline Design according to demand by S44, advanced Developmental Engineer, passes through through the evaluation of business expert group Then deliver intermediate Developmental Engineer and carry out detailed design;Evaluation is not by continuing framework and Outline Design then;
S45, intermediate Developmental Engineer carry out detailed design according to Outline Design, are checked through advanced Developmental Engineer by then Primary Developmental Engineer is delivered to be encoded;Check not by then continuing detailed design;
S46, primary Developmental Engineer are encoded according to detailed design, through intermediate Development Engineering inspection by then submitting generation Code;Check not by then continuing to encode;
Document formulates test plan, testing scheme according to demand by S47, advanced test engineer, is evaluated through business expert group By then delivering intermediate Test Engineer;Evaluation is not by continuing then to formulate test plan, testing scheme;
S48, intermediate Test Engineer are according to test plan, testing scheme, requirement documents design test case, through advanced survey Engineer inspection is tried by then delivering primary Test Engineer;Check not by then continuing design test case.Perform primary work Cheng Shi has performed the test case passed through, is identified through, and mark use-case passes through;Use-case by then reporting defect, does not mark Use-case does not pass through;
S49, primary Test Engineer's implementation of test cases, pinpoint the problems, report defect and mark use-case not pass through;Not Pinpoint the problems, deliver intermediate Test Engineer and check and mark use-case to pass through.
Further, described business expert group is by advanced requirement engineer, advanced Developmental Engineer, advanced test engineering Shi Zucheng, it is responsible for evaluation Requirements Analysis Model, architecture design, Outline Design, test plan, testing scheme;
Described demand analysis group is born by advanced requirement engineer, intermediate requirement engineering teacher, primary requirement engineering Shi Zucheng Investigation, analysis, modeling, design, the document work of duty demand;
Described software development group is made up of advanced Developmental Engineer, intermediate Developmental Engineer, primary Developmental Engineer, is born Architecture design, Outline Design, detailed design, coding, the reparation defect for blaming software work;
Described software test group is made up of advanced test engineer, intermediate Test Engineer, primary Test Engineer, is born Duty formulates test plan, testing scheme, design test case, implementation of test cases, submission defect work.
Further, described senior engineer is by advanced requirement engineer, advanced Developmental Engineer, advanced test engineering Shi Zucheng, wherein, described advanced requirement engineer duty is communicated with client, and is established Requirements Analysis Model, is checked intermediate demand work The business scenario of Cheng Shi designs, appoints business expert group director;
Wherein, described advanced Developmental Engineer is responsible for architecture design, Outline Design, checks that intermediate Developmental Engineer's is detailed Thin design, while be business panel member;
Wherein, described advanced test engineer system determines test plan, testing scheme, checks intermediate Test Engineer The test case of design simultaneously carries out exploratory testing, while is business panel member.
Further, described intermediate engineer is by intermediate requirement engineering teacher, intermediate Developmental Engineer, intermediate testing engineering Shi Zucheng, described intermediate requirement engineering teacher are responsible for business scenario design, check the requirement documents that junior engineer writes;
Described intermediate Developmental Engineer is responsible for detailed design, checks the coding of primary Developmental Engineer;
Described intermediate Test Engineer is responsible for design and maintenance test use-case, checks that primary Test Engineer performs and passes through Test case.
Further, described junior engineer is by primary requirement engineering teacher, primary Developmental Engineer, primary testing engineering Shi Zucheng, described primary requirement engineering teacher are responsible for writing requirement documents and carry out document management;
Described primary Developmental Engineer is responsible for coding, repairs defect;
Described primary Test Engineer is responsible for implementation of test cases.
Further, the measure that described prevention scheme includes is as follows:
Experts' evaluation, business expert group determine final demand, framework and Outline Design, test plan and testing scheme, Demand change must be evaluated by business expert group pass through and pair therefore caused by project or product seller's seven sale be responsible for;
Expert training, business expert group be responsible for research staff is giveed training, improve constantly research staff technical merit, Managerial skills;
Code is multiplexed, is multiplexed the existing code of maturation as far as possible;
Specification flow, standardized level is improved constantly, experiences and lessons solidification on stream, and continue to optimize stream Journey.
Further, the measure that described inspection scheme includes is as follows:
Technical Review, business expert group evaluate to technical scheme, thinking, find out the problem of possible before the coding;
Code review, check whether code is consistent with design;
Comprehensively test, carry out unit testing, integration testing, system testing, performance test, regression test, ease for use test, Safety test, and all operations have corresponding test case;
Process inspection, check execution of the research staff to process or specification.
Further, the measure that described response scheme includes is as follows:
Convenient, quickly pre-sales after-sale service is provided, from the access of new client, safeguarded to old and new customers, is established complete Customer service chain;
Optimize the related each link of customer service chain, technical support, sale, marketing, popularization, planning, occurrences in human life are multidisciplinary close Cut distribution closes, and reduces each link customer churn and company cost.
The present invention is had the following advantages relative to prior art and effect:
Using technology provided by the present invention, by reasonably arranging research staff, research and development task, 3 sets of quality pipes are established Reason scheme, and by strict management and control processes of research & development, supervise, confirm step by step step by step, find as early as possible and solve as much as possible ask Topic, software quality is improved, reduce R&D costs, also promote research staff to feel hoisting power.
Brief description of the drawings
Fig. 1 is research staff's packet classification figure in the method for software quality management disclosed by the invention;
Fig. 2 is the processes of research & development figure in the method for software quality management disclosed by the invention.
Embodiment
To make the purpose, technical scheme and advantage of the embodiment of the present invention clearer, below in conjunction with the embodiment of the present invention In accompanying drawing, the technical scheme in the embodiment of the present invention is clearly and completely described, it is clear that described embodiment is Part of the embodiment of the present invention, rather than whole embodiments.Based on the embodiment in the present invention, those of ordinary skill in the art The every other embodiment obtained under the premise of creative work is not made, belongs to the scope of protection of the invention.
Embodiment
The present embodiment specifically discloses a kind of method of software quality management, and research staff is grouped, be classified, builds by methods described 3 sets quality management schemes are found, management and control processes of research & development, substitute the research and development pattern and flow of present generally existing, in a wheel is researched and developed It is as much as possible to solve the problems, such as, software quality is improved, reduces R&D costs.
The method of the software quality management is specific as follows,
Step S1, research staff is grouped:According to the effect of different stage research staff in R&D process, research staff is drawn It is divided into business expert group, demand analysis group, software development group, software test group.Referring in particular to shown in Fig. 1.
Business expert group is made up of advanced requirement engineer, advanced Developmental Engineer, advanced test engineer, is responsible for evaluation Requirements Analysis Model, architecture design, Outline Design, test plan, testing scheme.
Demand analysis group is responsible for demand by advanced requirement engineer, intermediate requirement engineering teacher, primary requirement engineering Shi Zucheng Investigation, analysis, modeling, design, the work such as document.
Software development group is made up of advanced Developmental Engineer, intermediate Developmental Engineer, primary Developmental Engineer, is responsible for software Architecture design, Outline Design, detailed design, coding, repair the work such as defect.
Software test group is made up of advanced test engineer, intermediate Test Engineer, primary Test Engineer, is responsible to define The work such as test plan, testing scheme, design test case, implementation of test cases, submission defect.
Step S2, research staff is classified:According to quality such as the experience of research staff, abilities, research staff is divided into advanced Engineer, intermediate engineer, junior engineer.
Wherein, senior engineer is made up of advanced requirement engineer, advanced Developmental Engineer, advanced test engineer, high Level requirement engineering teacher's duty is communicated with client, and establishes Requirements Analysis Model, is checked the business scenario of intermediate requirement engineering teacher design, is appointed Business expert group director;
Advanced Developmental Engineer is responsible for architecture design, Outline Design, checks the detailed design of intermediate Developmental Engineer, simultaneously It is business panel member;
Advanced test engineer system determines test plan, testing scheme, checks the test of intermediate Test Engineer's design Use-case simultaneously carries out exploratory testing, while is business panel member.
Wherein, intermediate engineer is made up of intermediate requirement engineering teacher, intermediate Developmental Engineer, intermediate Test Engineer, in Level requirement engineering teacher is responsible for business scenario design, checks the requirement documents that junior engineer writes;
Intermediate Developmental Engineer is responsible for detailed design, checks the coding of primary Developmental Engineer;
Intermediate Test Engineer is responsible for design and maintenance test use-case, checks that primary Test Engineer performs the test passed through Use-case.
Wherein, junior engineer is made up of primary requirement engineering teacher, primary Developmental Engineer, primary Test Engineer, just Level requirement engineering teacher is responsible for writing requirement documents and carries out document management;
Primary Developmental Engineer is responsible for coding, repairs defect.
Primary Test Engineer is responsible for implementation of test cases.
Step S3,3 sets of quality management schemes are established:
S31, effective prevention scheme.Effectively prevent problem from producing in software development process.Major measure has:
S311, experts' evaluation, business expert group determine final demand, framework and Outline Design, test plan and test Scheme, demand change must be evaluated by business expert group pass through and pair therefore caused by project or product seller's seven sale be responsible for;
S312, expert training, business expert group are responsible for giveing research staff training, improve constantly the technology of research staff Horizontal, managerial skills.
S313, multiplexing code, the existing code of maturation is multiplexed as far as possible.
S314, specification flow, standardized level is improved constantly, experiences and lessons solidification on stream, and it is constantly excellent Change flow.
S32, reliably check scheme.Pinpointed the problems as early as possible in software development process, solve problem as early as possible, problem Solve cost to be preferably minimized.Major measure has:
S321, Technical Review, business expert group evaluate to technical scheme, thinking, find out before the coding possible Problem.
S322, code review, check whether code is consistent with design.
S323, comprehensively test, test is the important means that leakage detection is filled a vacancy.Carry out unit testing, integration testing, system survey Examination, performance test, regression test, ease for use test, safety test etc., and all operations have corresponding test case.
S324, process inspection, there is some generally acknowledged processes in software development process or specification can be avoided producing some and asked Topic, will check execution of the research staff to process or specification.
S33, quick response scheme.After software issue, client may find that problem, therefore must return as early as possible Should, solve, in favor of safeguarding the reputation of software product.Major measure has:
S331, convenient, quickly pre-sales after-sale service is provided, from the access of new client, safeguard, established to old and new customers Whole customer service chain.
The related each link, technical support, sale, marketing, popularization, planning, occurrences in human life etc. of S332, optimization customer service chain is more Department's close fit, reduce each link customer churn and company cost.
Step S4, management and control processes of research & development, it is as shown in Figure 2, specific as follows:
S41, advanced requirement engineer establish Requirements Analysis Model by requirement investigation, through the evaluation of business expert group by then Deliver intermediate requirement engineering Shi Jinhang business scenarios design;Evaluation is not by continuing then to establish Requirements Analysis Model.
Analysis model carries out business scenario design according to demand by S42, intermediate requirement engineering teacher, is examined through advanced requirement engineer Look into and write requirement documents by then delivering primary requirement engineering teacher;Check and do not designed by then continuing business scenario.
S43, primary requirement engineering teacher write requirement documents according to business scenario design, are checked by intermediate requirement engineering teacher By then delivering advanced Developmental Engineer;Check not by then continuing to write requirement documents.
Document carries out framework and Outline Design according to demand by S44, advanced Developmental Engineer, passes through through the evaluation of business expert group Then deliver intermediate Developmental Engineer and carry out detailed design;Evaluation is not by continuing framework and Outline Design then.
S45, intermediate Developmental Engineer carry out detailed design according to Outline Design, are checked through advanced Developmental Engineer by then Primary Developmental Engineer is delivered to be encoded;Check not by then continuing detailed design.
S46, primary Developmental Engineer are encoded according to detailed design, through intermediate Development Engineering inspection by then submitting generation Code;Check not by then continuing to encode.
Document formulates test plan, testing scheme according to demand by S47, advanced test engineer, is evaluated through business expert group By then delivering intermediate Test Engineer;Evaluation is not by continuing then to formulate test plan, testing scheme.
S48, intermediate Test Engineer are according to test plan, testing scheme, requirement documents design test case, through advanced survey Engineer inspection is tried by then delivering primary Test Engineer;Check not by then continuing design test case.Perform primary work Cheng Shi has performed the test case passed through, is identified through, and mark use-case passes through;Use-case by then reporting defect, does not mark Use-case does not pass through.
S49, primary Test Engineer's implementation of test cases, pinpoint the problems, report defect and mark use-case not pass through;Not Pinpoint the problems, deliver intermediate Test Engineer and check and mark use-case to pass through.
In summary, the method for a kind of software quality management disclosed by the invention, by the way that research staff is grouped, is classified, 3 sets of quality management schemes are established, management and control processes of research & development, the research and development pattern and flow of present generally existing is substituted, finds as early as possible simultaneously Solve problem as much as possible, improve software quality, reduce R&D costs.
Above-described embodiment is the preferable embodiment of the present invention, but embodiments of the present invention are not by above-described embodiment Limitation, other any Spirit Essences without departing from the present invention with made under principle change, modification, replacement, combine, simplification, Equivalent substitute mode is should be, is included within protection scope of the present invention.

Claims (8)

  1. A kind of 1. method of software quality management, it is characterised in that described method comprises the following steps:
    Research staff, according to the effect of different stage research staff in R&D process, is divided into business by S1, research staff's packet Expert group, demand analysis group, software development group, software test group;
    S2, research staff's classification, according to the experience of research staff, ability quality, are divided into senior engineer, middle rank by research staff Engineer, junior engineer;
    S3,3 sets of quality management schemes are established, including for effectively preventing prevention side caused by problem in software development process Case, the reviewing party for finding and solving problem as early as possible in software development process and the solution cost of problem is preferably minimized Case, for responding and solving as early as possible problem after software issue in favor of safeguarding the response scheme of the reputation of software product;
    S4, management and control processes of research & development, it is specific as follows:
    S41, advanced requirement engineer establish Requirements Analysis Model by requirement investigation, through the evaluation of business expert group by then delivering Intermediate requirement engineering Shi Jinhang business scenarios design;Evaluation is not by continuing then to establish Requirements Analysis Model;
    Analysis model carries out business scenario design according to demand by S42, intermediate requirement engineering teacher, and through advanced requirement, engineer inspection is led to Cross, deliver primary requirement engineering teacher and write requirement documents;Check and do not designed by then continuing business scenario;
    S43, primary requirement engineering teacher write requirement documents according to business scenario design, check and pass through by intermediate requirement engineering teacher Then deliver advanced Developmental Engineer;Check not by then continuing to write requirement documents;
    Document carries out framework and Outline Design according to demand by S44, advanced Developmental Engineer, through the evaluation of business expert group by then handing over Pay intermediate Developmental Engineer and carry out detailed design;Evaluation is not by continuing framework and Outline Design then;
    S45, intermediate Developmental Engineer carry out detailed design according to Outline Design, are checked through advanced Developmental Engineer by then delivering Primary Developmental Engineer is encoded;Check not by then continuing detailed design;
    S46, primary Developmental Engineer are encoded according to detailed design, through intermediate Development Engineering inspection by then submitting code; Check not by then continuing to encode;
    Document formulates test plan, testing scheme according to demand by S47, advanced test engineer, passes through through the evaluation of business expert group Then deliver intermediate Test Engineer;Evaluation is not by continuing then to formulate test plan, testing scheme;
    S48, intermediate Test Engineer are according to test plan, testing scheme, requirement documents design test case, through advanced test work Cheng Shi is checked by then delivering primary Test Engineer;Check not by then continuing design test case.Perform junior engineer The test case passed through has been performed, has been identified through, mark use-case passes through;Use-case by then reporting defect, does not mark use-case Do not pass through;
    S49, primary Test Engineer's implementation of test cases, pinpoint the problems, report defect and mark use-case not pass through;Do not find Problem then delivers intermediate Test Engineer and checks and mark use-case to pass through.
  2. A kind of 2. method of software quality management according to claim 1, it is characterised in that described business expert group by Advanced requirement engineer, advanced Developmental Engineer, advanced test engineer composition, it is responsible for evaluation Requirements Analysis Model, framework is set Meter, Outline Design, test plan, testing scheme;
    Described demand analysis group is responsible for needing by advanced requirement engineer, intermediate requirement engineering teacher, primary requirement engineering Shi Zucheng Investigation, analysis, modeling, design, the document work asked;
    Described software development group is made up of advanced Developmental Engineer, intermediate Developmental Engineer, primary Developmental Engineer, is responsible for soft The architecture design of part, Outline Design, detailed design, coding, reparation defect work;
    Described software test group is made up of advanced test engineer, intermediate Test Engineer, primary Test Engineer, responsibility system Determine test plan, testing scheme, design test case, implementation of test cases, submission defect work.
  3. A kind of 3. method of software quality management according to claim 1, it is characterised in that described senior engineer by Advanced requirement engineer, advanced Developmental Engineer, advanced test engineer composition, wherein, described advanced requirement engineer duty Communicate with client, establish Requirements Analysis Model, check the business scenario of intermediate requirement engineering teacher design, appoint business expert group to be responsible for People;
    Wherein, described advanced Developmental Engineer is responsible for architecture design, Outline Design, checks setting in detail for intermediate Developmental Engineer Meter, while be business panel member;
    Wherein, described advanced test engineer system determines test plan, testing scheme, checks intermediate Test Engineer's design Test case and carry out exploratory testing, while be business panel member.
  4. A kind of 4. method of software quality management according to claim 1, it is characterised in that described intermediate engineer by Intermediate requirement engineering teacher, intermediate Developmental Engineer, intermediate Test Engineer composition, described intermediate requirement engineering teacher are responsible for business Scenario Design, check the requirement documents that junior engineer writes;
    Described intermediate Developmental Engineer is responsible for detailed design, checks the coding of primary Developmental Engineer;
    Described intermediate Test Engineer is responsible for design and maintenance test use-case, checks that primary Test Engineer performs the survey passed through Example on probation.
  5. A kind of 5. method of software quality management according to claim 1, it is characterised in that described junior engineer by Primary requirement engineering teacher, primary Developmental Engineer, primary Test Engineer composition, described primary requirement engineering teacher are responsible for writing Requirement documents simultaneously carry out document management;
    Described primary Developmental Engineer is responsible for coding, repairs defect;
    Described primary Test Engineer is responsible for implementation of test cases.
  6. 6. the method for a kind of software quality management according to claim 1, it is characterised in that described prevention scheme includes Measure it is as follows:
    Experts' evaluation, business expert group determine final demand, framework and Outline Design, test plan and testing scheme, demand Change must be evaluated by business expert group pass through and pair therefore caused by project or product seller's seven sale be responsible for;
    Expert training, business expert group are responsible for giveing research staff training, improve constantly technical merit, the management of research staff It is horizontal;
    Code is multiplexed, is multiplexed the existing code of maturation as far as possible;
    Specification flow, standardized level is improved constantly, experiences and lessons solidification on stream, and continue to optimize flow.
  7. 7. the method for a kind of software quality management according to claim 1, it is characterised in that described inspection scheme includes Measure it is as follows:
    Technical Review, business expert group evaluate to technical scheme, thinking, find out the problem of possible before the coding;
    Code review, check whether code is consistent with design;
    Test comprehensively, carry out unit testing, integration testing, system testing, performance test, regression test, ease for use test, safety Test, and all operations have corresponding test case;
    Process inspection, check execution of the research staff to process or specification.
  8. 8. the method for a kind of software quality management according to claim 1, it is characterised in that described response scheme includes Measure it is as follows:
    Convenient, quickly pre-sales after-sale service is provided, from the access of new client, is safeguarded to old and new customers, establishes complete client Service chaining;
    Optimize the related each link of customer service chain, technical support, sale, marketing, popularization, planning, occurrences in human life are multidisciplinary matches somebody with somebody closely Close, reduce each link customer churn and company cost.
CN201710963444.9A 2017-10-17 2017-10-17 A kind of method of software quality management Pending CN107678738A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201710963444.9A CN107678738A (en) 2017-10-17 2017-10-17 A kind of method of software quality management

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201710963444.9A CN107678738A (en) 2017-10-17 2017-10-17 A kind of method of software quality management

Publications (1)

Publication Number Publication Date
CN107678738A true CN107678738A (en) 2018-02-09

Family

ID=61140080

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201710963444.9A Pending CN107678738A (en) 2017-10-17 2017-10-17 A kind of method of software quality management

Country Status (1)

Country Link
CN (1) CN107678738A (en)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108280631A (en) * 2018-02-10 2018-07-13 武汉空心科技有限公司 A kind of front end development task management-control method and system
CN109002283A (en) * 2018-06-14 2018-12-14 南京航空航天大学 A kind of code inspection person's recommended method based on file path analysis
CN110083335A (en) * 2019-04-30 2019-08-02 北京大学软件与微电子学院 A kind of system-oriented software development methodology
CN110286938A (en) * 2019-07-03 2019-09-27 北京百度网讯科技有限公司 For exporting the method and apparatus for being directed to the evaluation information of user
CN112463119A (en) * 2020-12-02 2021-03-09 上海亚远景信息科技有限公司 V flow work decomposition structure
CN114330779A (en) * 2021-12-31 2022-04-12 哈尔滨宇龙自动化有限公司 Quality inspection management and tracking method, system, storage medium and computer

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108280631A (en) * 2018-02-10 2018-07-13 武汉空心科技有限公司 A kind of front end development task management-control method and system
CN109002283A (en) * 2018-06-14 2018-12-14 南京航空航天大学 A kind of code inspection person's recommended method based on file path analysis
CN109002283B (en) * 2018-06-14 2021-07-27 南京航空航天大学 Code reviewer recommendation method based on file path analysis
CN110083335A (en) * 2019-04-30 2019-08-02 北京大学软件与微电子学院 A kind of system-oriented software development methodology
CN110286938A (en) * 2019-07-03 2019-09-27 北京百度网讯科技有限公司 For exporting the method and apparatus for being directed to the evaluation information of user
CN112463119A (en) * 2020-12-02 2021-03-09 上海亚远景信息科技有限公司 V flow work decomposition structure
CN112463119B (en) * 2020-12-02 2023-11-17 上海亚远景信息科技有限公司 Software development method based on V-process work decomposition structure
CN114330779A (en) * 2021-12-31 2022-04-12 哈尔滨宇龙自动化有限公司 Quality inspection management and tracking method, system, storage medium and computer

Similar Documents

Publication Publication Date Title
CN107678738A (en) A kind of method of software quality management
Kumar et al. Winning customer loyalty in an automotive company through Six Sigma: a case study
De Boeck et al. Food safety climate in food processing organizations: Development and validation of a self-assessment tool
Love et al. State of science: Why does rework occur in construction? What are its consequences? And what can be done to mitigate its occurrence?
Rifkin et al. Applying program comprehension techniques to improve software inspections
Bugdol et al. Systemic support and environmental awareness in a normalised environmental management system consistent with ISO 14001
Broday et al. Application of a quality management tool (8D) for solving industrial problems
Toulemonde et al. Triple check for top quality or triple burden? Assessing EU evaluations
Visaggio Assessment of a renewal process experimented in the field
Polikoff et al. An examination of differential item functioning on the Vanderbilt assessment of leadership in education
Fine et al. Managing quality improvement
Ryabova et al. National Public Control System in Higher Education: The Bologna Process.
Konieczka Solving problems in hoshin kanri system approach using quality management tools
Dong et al. The hybrid systems method integrating STAMP and HFACS for the causal analysis of the road traffic accident
Welford Improving corporate environmental performance
Andriana Analysis of Factors Cause to Non-Optimal Management of Follow-up Audit Findings Case Study on Finance Education and Training Agency, Ministry of Finance
Rahmat et al. A revamp of the internal quality auditing process
Elton Staff Development in Relation to Research
Kareem et al. The Factors Effects on Quality Management System in Construction
Sanchaniya et al. The Effect of External and Internal Factors on Management Effectiveness Within Indian Construction Companies
Ochino-Onyango et al. Secondary School Principals’ Use of Quality Assurance and Standards Assessment Feedback in Supervision in Nairobi Kenya: A Critical Analysis
Tanjung et al. Knowledge, Expertise, and Experience on Employee Performance at PDAM Tirta Siak Pekanbaru City
Rifkin et al. Program comprehension techniques improve software inspections: A case study
Mead The Department of Transportation's Recent Efforts to Strengthen Pipeline Safety
SCHALLER Assuring TQM failure

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
RJ01 Rejection of invention patent application after publication
RJ01 Rejection of invention patent application after publication

Application publication date: 20180209