"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.",
"name_en": "Constructability",
"description": "通常要求是代码重复率不应该超过0.5%,超过则说明软件中存在较多冗余,不利于软件维护。",
"name": "可重构性",
"score": 5.11,
"dataIndex": "Constructability"
},
{
"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": "Reusability",
"description": "通常要求是代码重复率不应该超过0.5%,超过则说明软件中存在较多冗余,不利于软件维护。",
"name": "可重用性",
"score": 35.24,
"dataIndex": "Reusability"
},
{
"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": "Modifiability",
"description": "通常要求是代码重复率不应该超过0.5%,超过则说明软件中存在较多冗余,不利于软件维护。",
"name": "可修改性",
"score": 7.058,
"dataIndex": "Modifiability"
},
{
"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": "Testability",
"description": "通常要求是代码重复率不应该超过0.5%,超过则说明软件中存在较多冗余,不利于软件维护。",
"name": "可测试性",
"score": 8.19,
"dataIndex": "Testability"
}
]
},
{
"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 direct and indirect dependency among the software units divided by the total number of units. The overall dependency reflects the coupling among templates in the system architecture. As the industrial research indicates, the reduction of the dissemination cost is closely related to the improvement of system efficiency and the reduction of the defect ratio. According to the experience data in the industry, a value greater than 25% will bring heavy maintenance workload for fixing defects in the software.",
"name_en": "Total Dependancy",
"description": "即软件的总体传播成本,它是将软件各单元之间的直接依赖和间接依赖关系的统计值,经单元总数加以平均,得到的软件各单元间彼此依赖的程度。整体依赖度的高低反映了系统架构上模板间整体耦合关系的强弱。业界研究表明,传播成本的降低与系统的效率提高和缺陷率的下降有着密不可分的关系。根据业界经验数据,该值超过25%则该软件在修改缺陷时会带来较大的维护工作量。\n",
"name": "整体依赖度 \n",
"score": 0.038,
"dataIndex": "Total Dependancy"
},
{
"description_en": "Indicates a metric calculated using a specific algorithm based on the direct and indirect dependency among software units. This metric reflects the proportion of modules that can be independently evolved. Based on the research by Professor Cai from the Drexel University in the US, if the value is smaller than 45%, the decoupling design for the software is inadequate. In this case, the development of new features or an upgrade involves multiple software modules, bringing huge development and testing workload.",
"name_en": "Module Evolution Independency",
"description": "根据软件各单元之间的直接依赖和间接依赖关系通过特定算法得出的一个度量值,能够反映系统中有多大比例的模块能够独立演进。根据美国Drexel大学蔡教授的研究,该值低于45%则说明该软件解耦设计不足,在增加新特性或升级时会涉及多个软件模块,带来较大的开发测试工作量。\n",
"name": "模块独立演进度 \n",
"score": 0.7,
"dataIndex": "Module Evolution Independency"
}
]
},
{
"name": "GLOBAL",
"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": "Code Reduplicate Ratio",
"description": "通常要求是代码重复率不应该超过0.5%,超过则说明软件中存在较多冗余,不利于软件维护。",
"name": "代码重复率",
"score": 0.085,
"dataIndex": "Code Reduplicate Ratio"
},
{
"description_en": "Indicates the QDI value calculated based on bad smell in code detected according to the design pattern. If the value exceeds 200, the code is smelly.",
"name_en": "Design Mode Defect Index",
"description": "根据设计模式检查出的代码坏味道计算出的QDI得分,超过200分则代码坏味道比较严重。",
"name": "设计模式缺陷指数 ",
"score": 88.87,
"dataIndex": "Design Mode Defect Index"
},
{
"description_en": "Indicates the probability to influence multi-modules in modification or maintainence of a feature.",
"name_en": "Feature Dispersion",
"description": "Indicates the probability to influence multi-modules in modification or maintainence of a feature.",
"name": "特性离散度",
"score": 0.0,
"dataIndex": "Feature Dispersion"
},
{
"description_en": "Indicates the degree of decoupling between components.",
"name_en": "Component Decoupling",
"description": "Indicates the degree of decoupling between components.",
"name": "组件耦合度",
"score": 1.0,
"dataIndex": "Component Decoupling"
},
{
"description_en": "The ratio of the depend components to the total components in a system.",
"name_en": "Dependent Component Ratio",
"description": "组件依赖组件外代码,违反了公司对组件的定义",
"name": "非独立编译组件",
"score": 1.0,
"dataIndex": "Dependent Component Ratio"
},
{
"description_en": "Logic architecture conforms to a reasonable threshold",
"name_en": "The Depth of Logic View",
"description": "逻辑架构符合合理深度的阈值",
"name": "逻辑架构深度",
"score": 1.0,
"dataIndex": "The Depth of Logic View"
},
{
华为项目Tree canvas画图 数据3
时间: 2024-10-06 12:42:54
华为项目Tree canvas画图 数据3的相关文章
华为项目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画图 数据4
"description_en": "consistency of logic architecture and code directories ","name_en": "Consistency of LA and CD","description": "牵引产品软件规范化设置软件开发的目录,提升软件配置管理效率","name": "逻辑与代码目录一致性
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像素的东西可能显示不出来,但计算机可不管,他会试着画一下. 其实像素终究来说也是一个单位,假如我们把画布放大到足够大,足以看