"description_en": "consistency of logic architecture and code directories ",
"name_en": "Consistency of LA and CD",
"description": "牵引产品软件规范化设置软件开发的目录,提升软件配置管理效率",
"name": "逻辑与代码目录一致性",
"score": 0.0,
"dataIndex": "Consistency of LA and CD"
},
{
"description_en": "Components Size Ratio ",
"name_en": "Components Size Ratio",
"description": "Components Size Ratio",
"name": "独立编译组件占比",
"score": 0.0,
"dataIndex": "Components Size Ratio"
}
]
},
{
"name": "ARCHFACTOR",
"children": [
{
"description_en": "The code duplication rate should not exceed 5%. A higher duplication rate means that the software is redundant and software maintenance is difficult.",
"name_en": "Repeatability",
"description": "通常要求是代码重复率不应该超过0.5%,超过则说明软件中存在较多冗余,不利于软件维护。",
"name": "重复性",
"metricDetail": [
{
"defectType": "Reduplicate Code",
"defectNum": 89.0
}
],
"score": 95.45,
"dataIndex": "Repeatability"
},
{
"description_en": "The code duplication rate should not exceed 5%. A higher duplication rate means that the software is redundant and software maintenance is difficult.",
"name_en": "Module Equilibrium",
"description": "通常要求是代码重复率不应该超过0.5%,超过则说明软件中存在较多冗余,不利于软件维护。",
"name": "模块均衡性",
"metricDetail": [
{
"defectType": "Insufficient Module",
"defectNum": 2.0
},
{
"defectType": "Over-Large Module",
"defectNum": 2.0
}
],
"score": 56.17,
"dataIndex": "Module Equilibrium"
},
{
"description_en": "The code duplication rate should not exceed 5%. A higher duplication rate means that the software is redundant and software maintenance is difficult.",
"name_en": "Module Independency",
"description": "通常要求是代码重复率不应该超过0.5%,超过则说明软件中存在较多冗余,不利于软件维护。",
"name": "模块独立性",
"metricDetail": [
{
"defectType": "Total Dependancy",
"defectNum": "3.8%"
},
{
"defectType": "Module Evolution Independency",
"defectNum": "70.0%"
}
],
"score": 79.92,
"dataIndex": "Module Independency"
},
{
"description_en": "The code duplication rate should not exceed 5%. A higher duplication rate means that the software is redundant and software maintenance is difficult.",
"name_en": "File Scale",
"description": "通常要求是代码重复率不应该超过0.5%,超过则说明软件中存在较多冗余,不利于软件维护。",
"name": "文件规模",
"metricDetail": [
{
"defectType": "LargeFile",
"defectNum": 7.0
}
],
"score": 28.25,
"dataIndex": "File Scale"
},
{
"description_en": "The code duplication rate should not exceed 5%. A higher duplication rate means that the software is redundant and software maintenance is difficult.",
"name_en": "File Complexity",
"description": "通常要求是代码重复率不应该超过0.5%,超过则说明软件中存在较多冗余,不利于软件维护。",
"name": "文件复杂性",
"metricDetail": [
{
"defectType": "SAP Breakers",
"defectNum": 1.0
},
{
"defectType": "God Class",
"defectNum": 1.0
}
],
"score": 92.21,
"dataIndex": "File Complexity"
},
{
"description_en": "The code duplication rate should not exceed 5%. A higher duplication rate means that the software is redundant and software maintenance is difficult.",
"name_en": "Interface Rationality",
"description": "通常要求是代码重复率不应该超过0.5%,超过则说明软件中存在较多冗余,不利于软件维护。",
"name": "接口合理性",
"metricDetail": [
{
"defectType": "Feature Envy",
"defectNum": 2.0
}
],
"score": 98.43,
"dataIndex": "Interface Rationality"
},
{
"description_en": "The code duplication rate should not exceed 5%. A higher duplication rate means that the software is redundant and software maintenance is difficult.",
"name_en": "Function Complexity",
"description": "通常要求是代码重复率不应该超过0.5%,超过则说明软件中存在较多冗余,不利于软件维护。",
"name": "函数复杂性",
"metricDetail": [
{
"defectType": "Over-Complexity Function",
"defectNum": 6.0
}
],
"score": 98.55,
"dataIndex": "Function Complexity"
},
{
"description_en": "The code duplication rate should not exceed 5%. A higher duplication rate means that the software is redundant and software maintenance is difficult.",
"name_en": "Function Scale",
"description": "通常要求是代码重复率不应该超过0.5%,超过则说明软件中存在较多冗余,不利于软件维护。",
"name": "函数规模",
"metricDetail": [],
"score": 100.0,
"dataIndex": "Function Scale"
}
]
},
{
"name": "CALC",
"children": [
{
"description_en": "Indicates the number of files counted by farmland.",
"name_en": "Sum of Files",
"description": "按责任田统计文件的个数",
"name": "文件总数",
"score": 208.0,
"dataIndex": "Sum of Files"
},
{
"description_en": "Indicates the number of software code lines, including empty and comment lines.",
"name_en": "Line of Code",
"description": "软件代码行数,包括空行和注释行。",
"name": "代码行",
"score": 20342.0,
"dataIndex": "Line of Code"
},
{
"description_en": "Indicates the number of minimum directories counted by farmland.",
"name_en": "Sum of Dir",
"description": "按责任田统计最小文件夹的个数",
"name": "文件夹总数",
"score": 0.0,
"dataIndex": "Sum of Dir"
}
]
}
]
},
"page": null
}
*/
华为项目Tree canvas画图 数据4
时间: 2024-09-29 10:26:57
华为项目Tree canvas画图 数据4的相关文章
华为项目Tree canvas画图 数据2
"name": "Structure","children": [{"description_en": "Indicates the overall dissemination cost of the software. It is the average dependency degree among software units based on the statistical values of the dir
华为项目Tree canvas画图 数据
var radarLeftRight = { "Reusability": [ "System Coupling", "Service Complexity", "Service Coupling", "System Consistency", "Component Coupling","Component Complexity","Module Indep
华为项目Tree canvas画图 数据3
"name": "ARCHATTRIBUTE","children": [{"description_en": "The code duplication rate should not exceed 5%. A higher duplication rate means that the software is redundant and software maintenance is difficult.&quo
canvas 画图工具 -- CanvasDraw
最近有些项目中用到了canvas画图: 为了方便封装了一下: 他的强大之处是 处理了各种偏针的问题: 1,css 强制宽高的变形 造成的偏针 2,给canvas加边 造成的偏针 3,上层父级缩放 造成的偏针 ( 前两种函数自行校正,第3种要传参) 更多去 github 吧,记得点赞谢谢 CanvasDraw:https://github.com/songyijian/CanvasDraw var c2=new CanvasDraw('#canvas2',{ 'attr':{'width':400
Canvas画图之中级篇
前段时间介绍了canvas画图的初级篇,今天接着介绍中级篇了... 一.绘制形状 绘制图形不仅仅是利用线条来实现绘图, 还可以有快捷的绘制图形的办法 1.绘制矩形 2.绘制圆弧 1 绘制矩形 绘制矩形的方法 CanvasRenderingContext2D.strokeRect CanvasRenderingContext2D.fillRect CanvasRenderingContext2D.rect 注意: rect 方法就是矩形路径, 还需要使用 fill 或 stroke 才可以看到效果
Canvas画图在360浏览器中跑偏的问题
问题描述,canvas画图的js代码中编写的是画正方形的代码,结果在360浏览器上变成了长方形,不知道怎么回事,请问各位大神是否遇到过此类问题? 1 <!DOCTYPE html> 2 <html> 3 <head> 4 <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/> 5 <title></title> 6
性能测试项目总结-虚拟数据的准备
摘 要:本文主要是面向性能测试的工程师,从实际项目中总结经验.教训,并且提出一些改善的建议,希望大家能在以后的性能测试的项目中吸取和借鉴,本文尤其在性能测试的前期数据准备方面给出了解决方案. 关键词:测试用例:性能测试:测试流程 项目介绍 该项目为两年前的一个项目,目前该系统的性能在一定的条件下速度极慢,当用户量达到一定程度时,整个程序会无法响应,所以需要对该项目进行性能测试,找到系统的瓶颈,为以后的系统升级做充分的准备. 项目延期的原因 XXX项目已经结束,在整个项目的测试过程中遇到了不少困难
项目架构开发:数据访问层之Query
接上文 项目架构开发:数据访问层之Repository 上一章我们讲了IRepository接口,这张我们来讲IQuery 根据字面意思就可以知道,这次主要讲数据查询,上一章我们只针对单表做了查询的操作,多表联查并没有实现 其实对于任何一个项目来说,多表联查都是比较麻烦的地方,因为项目的“读”操作,特别是多表的“读”,至少占据所有“读”的一半以上 然而至今,据我所知还没有哪一款ORM工具可以灵活处理多表联查:想要不写sql语句,又想性能高,还想用强类型的ling查询方法:这对于多表查询来说比较难
html5 Canvas画图3:1px线条模糊问题
点击查看原文地址: html5 Canvas画图3:1px线条模糊问题 本文属于<html5 Canvas画图系列教程> 接上一篇canvas画线条教程 上次我们讲到,canvas有时候会出现1像素的线条模糊不清且好像更宽的情况,如下图: 这样的线条显然不是我们想要的. 这篇文章的目的就是弄清楚里面的原理,以及解决它. 大家都知道屏幕上最小的显示尺寸就是1像素,虽然小于1像素的东西可能显示不出来,但计算机可不管,他会试着画一下. 其实像素终究来说也是一个单位,假如我们把画布放大到足够大,足以看