CN107203370A - Quantify the method and apparatus of developer's code quality - Google Patents
Quantify the method and apparatus of developer's code quality Download PDFInfo
- Publication number
- CN107203370A CN107203370A CN201610150797.2A CN201610150797A CN107203370A CN 107203370 A CN107203370 A CN 107203370A CN 201610150797 A CN201610150797 A CN 201610150797A CN 107203370 A CN107203370 A CN 107203370A
- Authority
- CN
- China
- Prior art keywords
- quantified
- sub
- quantization time
- period
- dimension
- 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
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/77—Software metrics
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The application provides a kind of method and apparatus for quantifying developer's code quality.Methods described includes：Receive and quantify request, it is described to quantify to ask to include：Quantified goal, quantified dimension, quantization time interval and quantization time section；For the quantified goal, the sample data of the matching quantified dimension in the quantization time section is obtained；According to the quantization time interval and the sample data, quantitative information of the quantified goal in the quantified dimension is generated.The application is directed to quantified goal, the sample data for quantifying matching quantified dimension in the period can be obtained, and according to quantization time interval and the sample data, generate quantitative information of the quantified goal in the quantified dimension, so as to which from the code quality of a variety of different ratio developers of dimension ring, reliable basis are provided for the quality management of developer.
Description
Technical field
The application is related to field of computer technology, more particularly to a kind of side for quantifying developer's code quality
Method and device.
Background technology
With the fast development of Internet technology and smart machine, increasing function can pass through software
Realize, therefore, the quality that developer writes code will directly affect the progress of software development, or even shadow
Ring the usage experience of user.How with being continuously increased for developer's quantity, developer is weighed comprehensively
Code quality turn into urgent problem to be solved.
The content of the invention
In view of this, the application provides a kind of method and apparatus for quantifying developer's code quality.
Specifically, the application is achieved by the following technical solution：
A kind of method for quantifying developer's code quality, methods described includes：
Receive and quantify request, it is described to quantify to ask to include：Quantified goal, quantified dimension, quantization time
Interval and quantization time section；
For the quantified goal, the sample number of the matching quantified dimension in the quantization time section is obtained
According to；
According to the quantization time interval and the sample data, the quantified goal is generated in the amount
Change the quantitative information of dimension.
Optionally, methods described also includes：
According to the template of the quantified dimension, show that the quantified goal is believed in the quantization of the quantified dimension
Breath.
Optionally, it is described to be directed to the quantified goal, obtain in the quantization time section and match described quantify
The sample data of dimension, including：
When the quantified dimension is code coverage, the quantified goal is obtained in quantization time section
Interior test case covering lines of code and submission lines of code；
It is described according to the quantization time interval and the sample data, generate the quantified goal in institute
The quantitative information of quantified dimension is stated, including：
According to the quantization time interval, quantization time section is divided into multiple sub- periods；
For each sub- period, calculate test case in the sub- period and cover the total line number of code with carrying
The business of the total line number of code is handed over, code coverage of the quantified goal within the sub- period is obtained；
The quantitative information includes：Code coverage in the quantization time section in each sub- period.
Optionally, it is described to be directed to the quantified goal, obtain in the quantization time section and match described quantify
The sample data of dimension, including：
When the quantified dimension is that aacode defect is counted, the quantified goal is obtained in the quantization time
Defects count in section；
It is described according to the quantization time interval and the sample data, generate the quantified goal in institute
The quantitative information of quantified dimension is stated, including：
According to the quantization time interval, quantization time section is divided into multiple sub- periods；
For each sub- period, the sub- period is calculated according to the defects count in the sub- period
The day defect average of the interior quantified goal；
The quantitative information includes：Day defect average in the quantization time section in each sub- period.
Optionally, it is described to be directed to the quantified goal, obtain in the quantization time section and match described quantify
The sample data of dimension, including：
When the quantified dimension is SIT defect accountings, the quantified goal is obtained in the quantization time
SIT defects counts and DEV defects counts in section；
It is described according to the quantization time interval and the sample data, generate the quantified goal in institute
The quantitative information of quantified dimension is stated, including：
According to the quantization time interval, quantization time section is divided into multiple sub- periods；
For each sub- period, according to SIT defects counts and DEV numbers of defects in the sub- period
Amount calculates SIT defect accountings；
The quantitative information includes：SIT defect accountings in the quantization time section in each sub- period.
A kind of device for quantifying developer's code quality, described device includes：
Request reception unit, receives and quantifies request, described to quantify to ask to include：Quantified goal, quantization
Dimension, quantization time interval and quantization time section；
Data capture unit, for the quantified goal, obtains the matching amount in the quantization time section
Change the sample data of dimension；
Code quantifying unit, according to the quantization time interval and the sample data, generates the amount
Change quantitative information of the target in the quantified dimension.
Optionally, described device also includes：
Quantify display unit, according to the template of the quantified dimension, show the quantified goal in the amount
Change the quantitative information of dimension.
Optionally, the data capture unit, when the quantified dimension is code coverage, obtains institute
State test case covering lines of code and submission lines of code of the quantified goal in quantization time section；
The code quantifying unit, according to the quantization time interval, quantization time section is divided into
Multiple sub- periods, and for each sub- period, calculate test case covering generation in the sub- period
Business of the total line number of code with submitting the total line number of code, obtains generation of the quantified goal within the sub- period
Code coverage rate；
The quantitative information includes：Code coverage in the quantization time section in each sub- period.
Optionally, the data capture unit, when the quantified dimension is that aacode defect is counted, is obtained
Defects count of the quantified goal in quantization time section；
The code quantifying unit, according to the quantization time interval, quantization time section is divided into
Multiple sub- periods, and for each sub- period, calculated according to the defects count in the sub- period
The day defect average of the quantified goal in the sub- period；
The quantitative information includes：Day defect average in the quantization time section in each sub- period.
Optionally, the data capture unit, when the quantified dimension is SIT defect accountings, is obtained
SIT defects count and DEV defects count of the quantified goal in quantization time section；
The code quantifying unit, according to the quantization time interval, quantization time section is divided into
Multiple sub- periods, and for each sub- period, according to SIT defects counts in the sub- period and
DEV defects counts calculate SIT defect accountings；
The quantitative information includes：SIT defect accountings in the quantization time section in each sub- period.
The application is directed to quantified goal it can be seen from above description, can obtain interior of quantization period
Sample data with quantified dimension, and according to quantization time interval and the sample data, generation is described
Quantified goal the quantified dimension quantitative information, so as to ratio from a variety of different dimension rings
The code quality of developer, reliable basis are provided for the quality management of developer.
Brief description of the drawings
Fig. 1 is a kind of method of quantization developer code quality shown in the exemplary embodiment of the application one
Flow chart.
Fig. 2 is a kind of device of quantization developer code quality shown in the exemplary embodiment of the application one
A structural representation.
Fig. 3 is a kind of device of quantization developer code quality shown in the exemplary embodiment of the application one
Structural representation.
Embodiment
Here exemplary embodiment will be illustrated in detail, its example is illustrated in the accompanying drawings.Following
When description is related to accompanying drawing, unless otherwise indicated, the same numbers in different accompanying drawings represent same or analogous
Key element.Embodiment described in following exemplary embodiment does not represent the institute consistent with the application
There is embodiment.On the contrary, they are only one be described in detail in such as appended claims, the application
The example of the consistent apparatus and method of a little aspects.
It is the purpose only merely for description specific embodiment in term used in this application, and is not intended to be limiting
The application." one kind ", " institute of singulative used in the application and appended claims
State " and "the" be also intended to including most forms, unless context clearly shows that other implications.Should also
Work as understanding, term "and/or" used herein refers to and associated lists item comprising one or more
Purpose any or all may combine.
It will be appreciated that though may describe various using term first, second, third, etc. in the application
Information, but these information should not necessarily be limited by these terms.These terms only be used for by same type of information that
This is distinguished.For example, in the case where not departing from the application scope, the first information can also be referred to as
Two information, similarly, the second information can also be referred to as the first information.Depending on linguistic context, as in this institute
Use word " if " can be construed to " and ... when " or " when ... when " or " response
In it is determined that ".
Fig. 1 is a kind of method of quantization developer code quality shown in the exemplary embodiment of the application one
Flow chart.
Fig. 1 is refer to, the method for the quantization developer code quality can be wrapped using in the terminal
Following steps are included：
Step 101, receive and quantify request, it is described to quantify to ask to include：Quantified goal, quantified dimension,
Quantization time interval and quantization time section.
In the present embodiment, it is described quantify request can by check developer's code quality people initiate,
Such as：It is described to quantify to ask to be initiated by the leader of developing department.
In the present embodiment, the quantified goal can be the developer being quantized, the quantified goal
It can also be the developing department being quantized.The quantified dimension can include：Code coverage, code lack
Fall into statistics, SIT (System Integrate Test, system combination test) defect accounting, PMD information
Deng.The quantization time interval and quantization time section are generally configured by the personnel of inquiry code quality,
Such as：Certain developing department leader can voluntarily set described when department's employee code quality is inquired about
Quantization time interval and quantization time section.
As an example it is assumed that the code that department head will be checked in units of week in nearly three months of employee Zhang
Coverage rate, then the leader can input the ID of employee Zhang by quantifying the related pages of code quality,
Such as：Job number or title, and the quantization time is set to 7 days, by quantization time section
It is set to nearly three months, the quantified dimension is set to submit quantization request after code coverage.
Step 102, for the quantified goal, the matching quantization dimension in the quantization time section is obtained
The sample data of degree.
In the present embodiment, the sample data of the matching quantified dimension includes the generation quantization
Various data required for the quantitative information of dimension.Such as：When the quantified dimension is code coverage,
The sample data has generally included test case covering lines of code and has submitted lines of code etc..
Still by taking the citing of abovementioned steps 101 as an example, the quantization request that above-mentioned department head submits is being received
Afterwards, in this step, can obtain Zhang in nearly three months test case covering lines of code and
Submit lines of code.
Step 103, according to the quantization time interval and the sample data, the quantization mesh is generated
It is marked on the quantitative information of the quantified dimension.
Based on abovementioned steps 102, after the sample data for matching the quantified dimension is got, Ke Yixian
Quantization time section is divided into by multiple sub- periods according to the quantization time interval, then for every
The individual sub- period, the quantitative information of the quantified dimension is calculated, to obtain the quantified goal in the amount
Change the quantitative information of each sub- period in the period.
, in this step, can be first in units of 7 days still by taking the citing of abovementioned steps 101 as an example, will
It is divided into 12 periods within nearly three months, code of the employee Zhang in each period is then calculated respectively and is covered
Lid rate, to obtain employee Zhang in nearly trimestral code coverage situation, so as to weigh employee
Certain nearly trimestral code quality.
The application is directed to quantified goal it can be seen from above description, can obtain interior of quantization period
Sample data with quantified dimension, and according to quantization time interval and the sample data, generation is described
Quantified goal the quantified dimension quantitative information, so as to ratio from a variety of different dimension rings
The code quality of developer, reliable basis are provided for the quality management of developer.
Optionally, in the application another example, generating quantification target certain quantified dimension quantization
After information, it can also show that the quantified goal quantifies described according to the template of the quantified dimension
The quantitative information of dimension, intuitively to show the code quality of quantified goal.In the present embodiment, can be pre-
The template of each quantified dimension is first set and preserves, the template can include block diagram, line chart etc., this
Application is not particularly limited to this.
The implementation process of the application is described with reference to specific quantified dimension.
In one example of the application, when quantified dimension is code coverage, request is quantified receiving
Afterwards, test case covering lines of code and submission code of the quantified goal in quantization time section can be obtained
Line number, such as：The interface that can be provided from related test platform obtains quantified goal in quantization time section
Test case covering lines of code and submit lines of code.
In the present embodiment, get test case covering lines of code and submit lines of code it
Afterwards, for each sub- period after division, test case covering code in the sub- period is calculated total
Line number and the business for submitting the total line number of code, to obtain code coverage of the quantified goal within the sub- period
Rate.
Still by taking the citing of abovementioned steps 101 as an example, it is assumed that employee Zhang, which has altogether, in nearly three months submitted
15 codes, then can get the lines of code submitted each time, and after this submission, to it
Test obtained test case covering lines of code, you can to get 15 groups of data, every group of data
Including submitting lines of code and corresponding test case covering lines of code.
After above-mentioned 15 groups of data are got, for each sub- period in units of 7 days, calculating should
Business of the test case covering total line number of code with submitting the total line number of code in the sub- period.It is assumed that above-mentioned 15
There are two groups of data within some sub- period in group data, one group is the submission row of lines of code 300, correspondence
Test case covering lines of code be 270 rows, another group for submit the row of lines of code 600, it is corresponding
Test case covering lines of code is 540 rows, then test case covers the total line number of code in the sub- period
Equal to 270+540, i.e. 810 rows, the total line number of code is submitted to be equal to 300+600, i.e. 900 rows, the son
It is 90% that code coverage, which is equal to 810/900, i.e. code coverage, in period.It is also possible to calculate
Code coverage of the employee Zhang within other sub- periods, to obtain the generation of employee Zhang in nearly three months
Code coverage rate.Pass through the code coverage of employee Zhang in nearly three months, it can be deduced that employee's Zhang's code
The average of coverage rate, when the code coverage of employee Zhang in certain sub- period is seriously less than the average,
Can be to the timely early warning of employee Zhang, to lift the quality mind of its code coverage.
In the application another example, when quantified dimension is that aacode defect is counted, quantization is being received
After request, defects count of the quantified goal in quantization time section can be obtained, such as：Can be from defect
The interface that management platform is provided obtains defects count of the quantified goal in quantization time section.
In the present embodiment, after the defects count is got, for each sub- time after division
Section, calculates the day defect average of quantified goal in the sub- period, to obtain quantified goal in the son
Defect statistics in period.
For example, it will again be assumed that quantization time section is nearly three months, quantization time quantified at intervals of 7 days
Target is employee Zhang, then can obtain the defects count of the employee Zhang in nearly three months, such as：Member
The daily defects count of work Zhang, weekly defects count etc..To get the number of defects weekly of employee Zhang
Exemplified by amount, for each sub- period in units of 7 days, the day defect calculated in the sub- period is equal
Value.It is assumed that the sub- period corresponding all defects counts got are 7, then day defect average is equal to
7/7 day, this day defect average was equal to 1/ day.It is also possible to calculate employee Zhang in other sub- periods
Interior day defect average, to obtain the day defect average of employee Zhang weekly in nearly three months.When certain period of the day from 11 p.m. to 1 a.m
Between in section employee Zhang day defect average it is serious higher when, can be to the timely early warning of employee Zhang, to carry
Rising it reduces the quality mind of aacode defect.
In the application another example, when quantified dimension is SIT defect accountings, quantization is being received
After request, SIT defects count and DEV of the quantified goal in quantization time section can be obtained
(development environment test, development environment test) defects count, such as：Can from lack
The interface for falling into management platform offer obtains SIT defects count and DEV of the quantified goal in quantization time section
Defects count.
In the present embodiment, after the SIT defects counts and DEV defects counts is got, pin
To each sub- period after division, SIT defect accountings in the sub- period are calculated, to be quantified
SIT defect accounting of the target within the sub- period.
For example, it will again be assumed that quantization time section is nearly three months, quantization time quantified at intervals of 7 days
Target is employee Zhang, then can obtain the SIT defects counts and DEV of employee Zhang in nearly three months
Defects count.Wherein, SIT defects counts represent the number of defects that tester's test is obtained after code submission
Amount, before DEV defects counts represent that code is submitted, the defects count that developer voluntarily has found.Obtaining
To after above-mentioned SIT defects counts and DEV defects counts, for each period of the day from 11 p.m. to 1 a.m in units of 7 days
Between section, calculate the SIT defect accountings in the sub- period.It is assumed that the SIT within the sub- period lacks
It is that 3, DEV defects total quantity is 2 to fall into total quantity, then SIT defects accounting is equal to 3/ in the sub- period
(3+2), i.e., 60%.It is also possible to calculate SIT defect of the employee Zhang within other sub- periods
Accounting, to obtain the SIT defect accountings of employee Zhang weekly in nearly three months.
In actual applications, the quantified dimension can also be PMD quantity, omit defect accounting etc.,
This is no longer going to repeat them by the application.
In addition, in the application another example, quantified goal can also be developing department.When the amount
When changing target for developing department, each developer in the developing department can be obtained interior in quantization time section
The sample data of quantified dimension is matched, can be according to described so that the quantified dimension is department's defect as an example
Sample data generates the day defects count per capita of the developing department.
Embodiment with the method for aforementioned quantities developer's code quality is corresponding, present invention also provides
Quantify the embodiment of the device of developer's code quality.
The embodiment that the application quantifies the device of developer's code quality can be applied in terminal.Device
Embodiment can be realized by software, can also be realized by way of hardware or software and hardware combining.With
Exemplified by software is realized, as the device on a logical meaning, being will by the processor of terminal where it
Corresponding computer program instructions read what operation in internal memory was formed in nonvolatile memory.From hardware
For aspect, as shown in Fig. 2 terminal where quantifying the device of developer's code quality for the application
A kind of hardware structure diagram, except the processor shown in Fig. 2, internal memory, network interface and non-volatile
Outside memory, terminal in embodiment where device, can be with generally according to the actual functional capability of the terminal
Including other hardware, this is repeated no more.
Fig. 3 is a kind of device of quantization developer code quality shown in the exemplary embodiment of the application one
Structural representation.
Fig. 3 is refer to, the device 200 of the quantization developer code quality can be applied in earlier figures 2
In shown terminal, include：Request reception unit 201, data capture unit 202, code quantify single
Member 203 and quantization display unit 204.
Wherein, the request reception unit 201, receives and quantifies request, described to quantify to ask to include：
Quantified goal, quantified dimension, quantization time interval and quantization time section；
The data capture unit 202, for the quantified goal, obtains interior of the quantization time section
Sample data with the quantified dimension；
The code quantifying unit 203, it is raw according to the quantization time interval and the sample data
Into the quantified goal the quantified dimension quantitative information.
The quantization display unit 204, according to the template of the quantified dimension, shows the quantified goal
In the quantitative information of the quantified dimension.
Optionally, the data capture unit 202, when the quantified dimension is code coverage, is obtained
Take test case covering lines of code and submission code line of the quantified goal in quantization time section
Number；
The code quantifying unit 203, according to the quantization time interval, quantization time section is drawn
It is divided into multiple sub- periods, and for each sub- period, calculates test case in the sub- period and cover
The total line number of lid code and the business for submitting the total line number of code, obtain the quantified goal within the sub- period
Code coverage；
The quantitative information includes：Code coverage in the quantization time section in each sub- period.
Optionally, the data capture unit 202, when the quantified dimension is that aacode defect is counted,
Obtain defects count of the quantified goal in quantization time section；
The code quantifying unit 203, according to the quantization time interval, quantization time section is drawn
It is divided into multiple sub- periods, and for each sub- period, according to the defects count in the sub- period
Calculate the day defect average of the quantified goal in the sub- period；
The quantitative information includes：Day defect average in the quantization time section in each sub- period.
Optionally, the data capture unit 202, when the quantified dimension is SIT defect accountings,
Obtain SIT defects count and DEV defects count of the quantified goal in quantization time section；
The code quantifying unit 203, according to the quantization time interval, quantization time section is drawn
It is divided into multiple sub- periods, and for each sub- period, according to SIT numbers of defects in the sub- period
Amount and DEV defects counts calculate SIT defect accountings；
The quantitative information includes：SIT defect accountings in the quantization time section in each sub- period.
The function of unit and the implementation process of effect specifically refer to correspondence in the above method in said apparatus
The implementation process of step, will not be repeated here.
For device embodiment, because it corresponds essentially to embodiment of the method, so related part is joined
See the part explanation of embodiment of the method.Device embodiment described above be only it is schematical,
The wherein described unit illustrated as separating component can be or may not be it is physically separate, make
It can be for the part that unit is shown or may not be physical location, you can with positioned at a place,
Or can also be distributed on multiple NEs.Can select according to the actual needs part therein or
Person's whole modules realize the purpose of application scheme.Those of ordinary skill in the art are not paying creativeness
In the case of work, you can to understand and implement.
The preferred embodiment of the application is the foregoing is only, it is all at this not to limit the application
Within the spirit and principle of application, any modification, equivalent substitution and improvements done etc. should be included in
Within the scope of the application protection.
Claims (10)
1. a kind of method for quantifying developer's code quality, it is characterised in that methods described includes：
Receive and quantify request, it is described to quantify to ask to include：Quantified goal, quantified dimension, quantization time
Interval and quantization time section；
For the quantified goal, the sample number of the matching quantified dimension in the quantization time section is obtained
According to；
According to the quantization time interval and the sample data, the quantified goal is generated in the amount
Change the quantitative information of dimension.
2. according to the method described in claim 1, it is characterised in that methods described also includes：
According to the template of the quantified dimension, show that the quantified goal is believed in the quantization of the quantified dimension
Breath.
3. according to the method described in claim 1, it is characterised in that described to be directed to the quantified goal,
The sample data of the matching quantified dimension in the quantization time section is obtained, including：
When the quantified dimension is code coverage, the quantified goal is obtained in quantization time section
Interior test case covering lines of code and submission lines of code；
It is described according to the quantization time interval and the sample data, generate the quantified goal in institute
The quantitative information of quantified dimension is stated, including：
According to the quantization time interval, quantization time section is divided into multiple sub- periods；
For each sub- period, calculate test case in the sub- period and cover the total line number of code with carrying
The business of the total line number of code is handed over, code coverage of the quantified goal within the sub- period is obtained；
The quantitative information includes：Code coverage in the quantization time section in each sub- period.
4. according to the method described in claim 1, it is characterised in that described to be directed to the quantified goal,
The sample data of the matching quantified dimension in the quantization time section is obtained, including：
When the quantified dimension is that aacode defect is counted, the quantified goal is obtained in the quantization time
Defects count in section；
It is described according to the quantization time interval and the sample data, generate the quantified goal in institute
The quantitative information of quantified dimension is stated, including：
According to the quantization time interval, quantization time section is divided into multiple sub- periods；
For each sub- period, the sub- period is calculated according to the defects count in the sub- period
The day defect average of the interior quantified goal；
The quantitative information includes：Day defect average in the quantization time section in each sub- period.
5. according to the method described in claim 1, it is characterised in that described to be directed to the quantified goal,
The sample data of the matching quantified dimension in the quantization time section is obtained, including：
When the quantified dimension is SIT defect accountings, the quantified goal is obtained in the quantization time
SIT defects counts and DEV defects counts in section；
It is described according to the quantization time interval and the sample data, generate the quantified goal in institute
The quantitative information of quantified dimension is stated, including：
According to the quantization time interval, quantization time section is divided into multiple sub- periods；
For each sub- period, according to SIT defects counts and DEV numbers of defects in the sub- period
Amount calculates SIT defect accountings；
The quantitative information includes：SIT defect accountings in the quantization time section in each sub- period.
6. a kind of device for quantifying developer's code quality, it is characterised in that described device includes：
Request reception unit, receives and quantifies request, described to quantify to ask to include：Quantified goal, quantization
Dimension, quantization time interval and quantization time section；
Data capture unit, for the quantified goal, obtains the matching amount in the quantization time section
Change the sample data of dimension；
Code quantifying unit, according to the quantization time interval and the sample data, generates the amount
Change quantitative information of the target in the quantified dimension.
7. device according to claim 6, it is characterised in that described device also includes：
Quantify display unit, according to the template of the quantified dimension, show the quantified goal in the amount
Change the quantitative information of dimension.
8. device according to claim 6, it is characterised in that
The data capture unit, when the quantified dimension is code coverage, obtains the quantization mesh
It is marked on test case covering lines of code and submission lines of code in the quantization time section；
The code quantifying unit, according to the quantization time interval, quantization time section is divided into
Multiple sub- periods, and for each sub- period, calculate test case covering generation in the sub- period
Business of the total line number of code with submitting the total line number of code, obtains generation of the quantified goal within the sub- period
Code coverage rate；
The quantitative information includes：Code coverage in the quantization time section in each sub- period.
9. device according to claim 6, it is characterised in that
The data capture unit, when the quantified dimension is that aacode defect is counted, obtains described quantify
Defects count of the target in quantization time section；
The code quantifying unit, according to the quantization time interval, quantization time section is divided into
Multiple sub- periods, and for each sub- period, calculated according to the defects count in the sub- period
The day defect average of the quantified goal in the sub- period；
The quantitative information includes：Day defect average in the quantization time section in each sub- period.
10. device according to claim 6, it is characterised in that
The data capture unit, when the quantified dimension is SIT defect accountings, obtains described quantify
SIT defects count and DEV defects count of the target in quantization time section；
The code quantifying unit, according to the quantization time interval, quantization time section is divided into
Multiple sub- periods, and for each sub- period, according to SIT defects counts in the sub- period and
DEV defects counts calculate SIT defect accountings；
The quantitative information includes：SIT defect accountings in the quantization time section in each sub- period.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610150797.2A CN107203370A (en) | 2016-03-16 | 2016-03-16 | Quantify the method and apparatus of developer's code quality |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610150797.2A CN107203370A (en) | 2016-03-16 | 2016-03-16 | Quantify the method and apparatus of developer's code quality |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN107203370A true CN107203370A (en) | 2017-09-26 |
Family
ID=59903785
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610150797.2A Pending CN107203370A (en) | 2016-03-16 | 2016-03-16 | Quantify the method and apparatus of developer's code quality |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107203370A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107908550A (en) * | 2017-10-27 | 2018-04-13 | 链家网（北京）科技有限公司 | A kind of software defect statistical processing methods and device |
| CN109254791A (en) * | 2018-09-03 | 2019-01-22 | 平安普惠企业管理有限公司 | Develop management method, computer readable storage medium and the terminal device of data |
| CN110413733A (en) * | 2019-07-23 | 2019-11-05 | 上海易点时空网络有限公司 | Code statistical method and device |
| CN114816977A (en) * | 2021-01-29 | 2022-07-29 | 北京字跳网络技术有限公司 | Component stability detection method, device, equipment and storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101582072A (en) * | 2008-05-16 | 2009-11-18 | 鸿富锦精密工业（深圳）有限公司 | System and method for counting codes |
| CN101552009B (en) * | 2009-05-07 | 2012-05-30 | 无锡中星微电子有限公司 | Quantitative method and apparatus in MP3 coding |
-
2016
- 2016-03-16 CN CN201610150797.2A patent/CN107203370A/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101582072A (en) * | 2008-05-16 | 2009-11-18 | 鸿富锦精密工业（深圳）有限公司 | System and method for counting codes |
| CN101552009B (en) * | 2009-05-07 | 2012-05-30 | 无锡中星微电子有限公司 | Quantitative method and apparatus in MP3 coding |
Non-Patent Citations (2)
| Title |
|---|
| TAEKWON007: "软件项目开发度量分析", 《HTTPS://WENKU.BAIDU.COM/VIEW/6018C263700ABB68A982FBBF.HTML》 * |
| 江边望海: "如何解决开发人员的工作无法量化的问题", 《HTTPS://MY.OSCHINA.NET/JIANGBIANWANGHAI/BLOG/480023》 * |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107908550A (en) * | 2017-10-27 | 2018-04-13 | 链家网（北京）科技有限公司 | A kind of software defect statistical processing methods and device |
| CN107908550B (en) * | 2017-10-27 | 2020-11-13 | 贝壳找房(北京)科技有限公司 | Software defect statistical processing method and device |
| CN109254791A (en) * | 2018-09-03 | 2019-01-22 | 平安普惠企业管理有限公司 | Develop management method, computer readable storage medium and the terminal device of data |
| CN110413733A (en) * | 2019-07-23 | 2019-11-05 | 上海易点时空网络有限公司 | Code statistical method and device |
| CN114816977A (en) * | 2021-01-29 | 2022-07-29 | 北京字跳网络技术有限公司 | Component stability detection method, device, equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Kynčlová et al. | Correlation between compositional parts based on symmetric balances | |
| Bertozzi et al. | The challenges of modeling and forecasting the spread of COVID-19 | |
| Sansom et al. | Parsimony, not Bayesian analysis, recovers more stratigraphically congruent phylogenetic trees | |
| Posthuma et al. | Improved component-based methods for mixture risk assessment are key to characterize complex chemical pollution in surface waters | |
| CN107203370A (en) | Quantify the method and apparatus of developer's code quality | |
| Liu et al. | An agent-based model for quantitatively analyzing and predicting the complex behavior of emergency departments | |
| US20030070157A1 (en) | Method and system for estimating software maintenance | |
| Anciaux et al. | Evolutionary rescue over a fitness landscape | |
| CN109684322B (en) | Data processing system and method for automatic maritime affair auditing | |
| CN113034171B (en) | Business data processing method and device, computer and readable storage medium | |
| CN108762907A (en) | Task processing method based on multiple client and system | |
| CN107909234A (en) | Time limit based reminding method, processing method and its device of Work stream data, equipment | |
| Pacioni et al. | vortexR: an R package for post Vortex simulation analysis | |
| CN107038108A (en) | The method of testing and device of software | |
| Cochrane et al. | Modeling with uncertain science: estimating mitigation credits from abating lead poisoning in Golden Eagles | |
| Oughton et al. | Addressing uncertainties in the ERICA integrated approach | |
| Akerman | Market concentration and the relative demand for college‐educated labour | |
| Liao | Applied stochastic processes | |
| Kaligotla et al. | Modeling an information-based community health intervention on the south side of chicago | |
| Lewis et al. | In silico surveillance: evaluating outbreak detection with simulation models | |
| CN110245778A (en) | Amortization of data detection method and device | |
| Fairbrother et al. | Risk management decisions for pesticides and threatened and endangered species: The role of uncertainty analysis | |
| Chou et al. | Estimating software project effort for manufacturing firms | |
| Cao et al. | Tuning crowdsourced human computation | |
| Schwabe | BayesTwin: An R package for Bayesian inference of item-level twin data |
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: 20170926 |