Issue Log template_v5
第五部分 H3C iMC NTA组件介绍
Prot Operator IpVersion TosIPv4 SourceIP SrcNatIP DestIP DestNatIP SrcPort SrcNatPort DestPort DestNatPort StartTime EndTime InTotalPkg InTotalByte OutTotalPkg OutTotalByte Reserved1 Reserved2 Reserved3
IP承载的协议类型
操作字，主要指流结束原因。
IP报文版本 IPv4报文的Tos字段 源IP NAT转换后的源IP 目的IP NAT转换后的目的IP TCP/UDP源端口号 NAT转换后的TCP/UDP源端口号 TCP/UDP目的端口号 NAT转换后的目的TCP/UDP目的端口号 流起始时间，以秒为单位，以1970/1/1 0:0开始计算 流结束时间，以秒为单位，以1970/1/1 0:0开始计算 （源IP方）接收包数 （源IP方）接收字节数 （源IP方）发出包数 （源IP方）发出字节数 对于0x02版本（FirewallV200R001）保留； 对于0x03版本（FirewallV200R005）第一个字节为源VPN ID，第二个字节为目的VPN ID， 第三、四个字节保留 保留 保留
Destination interface
Destination port Protocol Destination AS Direction Reserved ToS
Reserved
Source AS Source maskbits
Tcp_flags
Destination maskbits
9
NTA license
项目编码 对外型号 对外中文描述 备注 配置该组件时必须同时配 置智能管理平台 功能模块-H3C iMC-SW7M1NTAW-网络流量分析组件-纯软件（CD）中 文版
英语知识
技术类---电声高音扬声器tweeter中低音扬声器subwoofer功放amplifier盆架basketT铁T-yoke磁钢magnet上夹板plate泡沫边纸盆membrane （with foam edge）商标label音圈voice coil定位支片damper washer防尘帽dust cap平衡器front flange高频振膜high-frequency membrane导磁片magnetic sheet导磁碗U-cup防雨罩waterproof cover磁路系统magnet system定位圈spider焊片（左、右）terminal（left，right）功率放大集成电路power amplifier IC锦丝线litz wire电感线圈inductance winding电解电容electrolytic capacitor散热片heat sink双面电路板double-side circuit board支架trestle电阻resistor电容capacitor线束wiring harness扬声器喇叭loudspeaker螺丝钉screw箱座，箱底（下面）tank block盖板（上面）cover board防水垫waterproof washer胶垫glue cushion胶条、胶带adhesive tape插座socket密封圈（垫圈条）seal ring胶glue垫圈washer垫片gasket铆钉rivet接线板connection board保护罩protection cover零件component；part纸盆破坏membrane broken网罩grill卡簧clip支架bracket电感electrical inductance防尘罩center cap/ dust cap蜂巢板honey comb sandwich音箱loudspeaker enclosure振膜diaphragm障板baffle传声器风罩microphone windshield/ microphone windscreen 永磁体permanent magnet磁流体magnetic fluid磁通密度magnetic flux density低频下限频率lower limiting frequency低音抑制bass cut低音增强bass boost电流灵敏度sensitivity to current对称磁场symmetrical magnetic field额定频率范围rated frequency range额定输出功率rated output power额定输入功率rated input power共振频率resonance frequency最大瞬时功率maximum instantaneous power额定最大正弦电压rated maximum sinusoidal voltage额定阻抗rated impedance特性灵敏度级characteristic sensitivity level谐波失真特性harmonic distortion characteristic差频失真difference frequency distortion杨氏模量Young’s Modulus指向性频率特性directivity frequency characteristic信噪比SCR（signal to clutter ratio）过热保护overload protection实验室台式万用表multi-meter寿命试验台life tester高低温试验箱Temperature Alternating Box信号发生器signal generatorF0 测定器FO testerLCR数字电桥LCR digital electric meter绝缘电阻测试仪IR（insulation resistance）test温湿度计humiture meter恒温干燥箱Thermostat drying box喷淋试验箱Water spray box防水试验箱Waterproof Box跌落试验工装drop tester静电释放electrical static discharge极性测定器polarity machine阻抗测试仪impedance testCLIO测试系统CLIO test system寿命试验间life test room音频扫频信号发生器sweep signal generator正副极positive/cathode pole托盘salver电源接口power interface声音信号acoustical signal绝对湿度absolute humidity弯曲强度bend strength阻燃性能flame retardant capability体积电阻bulk resistance吸水性water absorbability干燥条件drying conditions影像测量仪video寿命测试Life Test温度循环T /C Temperature Cycle高温测试H/T High Temperature Test低温测试L/T Low Temperature Test额定电阻rated impedance直流电阻direct current resistance电磁兼容性Electro Magnetic Compatibility,电磁干扰Electro Magnetic Interference表面阻抗测试Surface Impedance Resistance卡尺calipers绝缘电阻测试仪insulation resistance tester振动测试台scillation testerKlippel性能performance缓冲器buffer音频流输入输出接口ASIO（audio stream input output）文件夹Folder温度湿度传感器Temperature humidity sensor启动开关Start switch近声场Near field安装Installation行程、路径Routing电缆接头Cable terminal装置设备Device核实、判定Verify灵敏度Sensitivity活塞话筒Piston phone激励者Exciter手册、手动的Manual工作、任务Task阻抗Impedance声压Sound pressure直流电阻Re音圈电感Le等效顺性Cmes谐振频率Fs总品质因数QTS机械品质因数QMS电气品质因数QES频响曲线Frequency response特性灵敏度、平均声压级Average level 极性Polarity失真THD谐波Harmonic纯音Rub﹠buzz激活、触发Activate计算Calculation退出程序Logout手动清理Manual sweep计划、方案、项目Project编辑Edit视图View操作Operation操作者Operator报告Report数据库Database副本Duplicate样板Save as template项目窗格Project pane剪贴板Clipboard特性Properties使恢复Refresh自定义颜色Custom colors测量Measure接受Accept许可证文件License file参数校准Calibration parameter内容Content延时Delay距离Distance拟合公差Fitting error电压V oltage技术类—电子PAAS部件单词上壳体upper housing下壳体bottom housingPCBA模块PCBA module左护板left baffle plate右护板right baffle plate螺钉screw橡胶垫片rubber gasketPAAS主要参数定义number of audio outputs最大输出声音数output type输出类型minimum load impedance最小负载阻抗max power per channel into min load impedance 最小负载阻抗条件下每频道最大功率short protection 短路保护voltage range 电压范围minimum ON voltage 最小启动电压maximum OFF voltage 最大关闭电压tolerance电压容差De-bounce time消抖时间current draw 消耗电流PAAS故障术语程序烧录异常program recording abnormal声音烧录异常sound recording abnormal外壳体划痕shell scratch上下壳体安装不严the installation of upper and bottom housing is not tight安装螺丝滑丝slipped screw功放部件单词Words of Amplifier Component自攻螺钉tapping screw垫片washer上盖coverPCBA模块PCBA module散热片heat sink安装支架bracketIC支架IC carrier内六角螺钉socket head cap screw功放主要生产流程功放主要参数定义operating voltage 运行电压limit voltage 极限电压total power 总功率operating temperature 运行温度storage temperature 存放温度output frequency 输出频率equivalent load 等效负载total input current 总输入电流dark current 暗电流CAN bus operating voltage控制器局域网总线技术运行电压CAN bus operating current控制器局域网总线技术运行电流Conversion efficiency 转换效率电子元器件Appendix-Electronic Component电容类Capacitor：贴片电容（表面焊接电容）chip capacitor（surface welding capacitor）电解电容electrolytic capacitor钽电容Tantalum Capacitor固态电容solid capacitor聚酯电容polyester capacitor陶瓷电容 ceramic capacitor电阻类Resistance：贴片电阻（表面焊接电阻）chip resistance （surface welding resistance）色环电阻color ring resistance热敏电阻thermistor磁珠magnetic head电感类Inductor：贴片电感chip inductor绕线电感winding inductor共模电感common mode inductor变压器transformer晶体管类：整流二极管 commutation diode肖特基二极管Schottky diodes三极管triode瞬变二极管（TVS管）Transient V oltage Suppressors发光二极管（LED） luminescent diode场效应管（MOS管）metal-oxide semiconductor光耦optocoupler红外发射、接收管IC类IC：微处理芯片（MCU）Microcontroller Unit功放芯片amplifier chips运放芯片operational amplifier chip语音芯片voice chip存储芯片memory chip三端稳压器triode voltage regulator晶振类crystal oscillator：无源晶振crystal有源晶振SPCO standard packaged crystal oscillator开关类switch：按键开关key switch继电器relay元器件特征参数Main Parameter of Electronic Component 封装packaging阻值resistance精度accuracy功率power工作温度范围operational temperature range温度系数temperature coefficient封装类型package type共模/差模common mode / differential mode最大电流maximum current;反向耐压reverse breakdown voltage介质种类medium type采购物流类供应链管理SCM (supply chain management)报价请求、询盘RFQ (request for quote)供应商早期介入ESI (early supplier involvement)标准价格standard price指定供应商nominated supplier潜在供应商potential supplier合格供应商qualified supplier新供应商new supplier引进、开发新供应商introduce and develop new suppliers供应商质量工程师SQE (supplier quality engineer)供应商管理库存supplier managed inventory供应商评估supplier evaluation质量、成本、交期、服务QCDS(quality cost delivery service)预估每年需求量EAU(estimated annual usage)购买、购货purchase采购员buyer物料需求计划MRP(material requirements planning)材料申请计划MRP(material requisition plan)库存水准stock level订单欠交补货BO replenish (back order replenish)供货商管理库存平衡VMSA burning (vendor managed stock area burning) 物流供应链中的库存pipeline采购申请purchase requisition采购订单purchase order执行订单execute the order取消订单cancel the order增加订单increase the order减少订单reduce the order最小订购量MOQ (minimum order quantity)最大供应量MSQ (maximum supply quantity)交期LT (lead time)付款条件payment term准时交付on-time delivery延迟交付delay the delivery退货return the goods付款arrange payment交货单delivery order货到付款COD (cash on delivery)仓管员warehouse keeper收货-验货-发货receipt goods/ inspection goods / issue goods入库be put in storage报废品scraped products先进先出first in first out送料feeding生产日期码D/C (date code)批号L/N (lot number)报废品scraped products处理品disposed products成品finished product半成品semi-finished product单位库存UTS(units to stock)厂商送货进度表VDS(vendor delivery schedule) 成品存货FGI (finished goods inventory)存货清单INV (inventory)发票invoice库存周转天数INV turnover days安全存量safety inventory货物接收单GRN (goods receive note)材料缺陷报告DMR (defective material report)材料回收处RMA (return material administration)制造工程类生产部PD ( product department)生产线production line生产计划控制PPC (production plan control)计划生产BTF (build to forecast)订单生产BTO (build to order)在制品working in process试做P/R (pilot run)量产MP (mass production)允收ACC (accept)拒收REE (reject)废料scrap material工装样件检查报告OTS pruefberichte尺寸DIM (dimension)主要缺陷major defect次要缺陷minor defect极严重缺陷critical defect制程不良deficient manufacturing procedure不良标签defective label生产力production capacity教育与训练education and training提案改善proposal improvement组长group leader线长line leader目视管理visual management个（根，块等）PCS (pieces)双（对等）PS (pairs)数量QTY (quantity)生产节拍production tempo制造单manufacture order工装室TR (tooling room)设备室ER (equipment room)工业工程师IE (industrial engineer)工艺工程师PE (process engineer/ production engineer) 设备工程师EE(equipment engineer)工装设计工程师TDE (tooling design engineer)瓶颈工序bottleneck process生产能力production capacity产能需求计划CRP (capacity requirements planning) 原因分析cause analysis工程能力指数engineering capacity index过程能力指数process capability index工程标准engineering standard技术标准technical standard工艺标准process standards设计变更/工程变更EC (engineer change)工程变更通知engineering change notice工程验证测试EVT (engineer verification test)场地平面布置图LC (layout chart)过程流程图PFC (process flow chart)过程潜在失效模式及后果分析PFMEA (process of potential failure modes and effects analysis)过程潜在失效模式及后果分析FMEA (failure modes and effects analysis)PDCA循环PDCA cycle (plan-do-check action cycle)控制计划CP (control plan)作业指导书WI (work instruction)夹具（治具）fixture/ jig热熔胶hot-melt glue/ hot-melt adhesiveUV胶UV glue/UV adhesive涂胶机glue machine压力机press machine铆钉机rivet driver充磁机magnetizing machine打包机packaging machine液压机hydraulic machine空压机air compressor热熔机fuse machine/ heat stake烘道drying tunnel电动起子electric screw driver拉钉枪rivet gun磁规magnet holder音规voice coil holder自动恒温焊台automatic constant temperature soldering station电烙铁soldering iron扫频信号发生器sweep signal generator极性测试仪polarity machine tester剪线钳wire cutters传送带conveyor belt组装线assembly line自动化automation异常处理abnormal handling胶量glue quantity每小时件数PPH (pieces per hour)工程变更申请ECR (engineering change request)工程变更指令ECO (engineering change order)作业说明书WPS (work procedure sheet)工程变更评估ECE (engineering change estimation)工程变更取消ECC (engineering change cancellation)内部工程备忘录IEM (internal engineering memo)工程分析需求EAR (engineering analysis request)质量管理类质量管理QM (quality management)质量工程师QE (quality engineer)质量保证QA (quality assurance)质量控制QC (quality control)连续工序改善CPI（continuous process improvement）进料质量控制IQC (incoming quality control)过程质量控制PQC (process quality control)出货质量控制OQC (output quality control)设计质量控制DQC (design quality control)最终质量控制FQC (final quality control)全面质量控制TQC (total quality control)产品管理体系product management system产品质量管理product quality management产品计量单位unit of measurement of product产品售后服务after service产品质量标准product quality standard产品质量认证标志certification marking of product quality 产品质量认证程序certification procedure of product quality 产品质量认证制度certification system of product quality认证certification安全认证safety certification安全认证标志mark of safety certification强制性认证compulsory certificate实验室认证laboratory certification认证体系certification system认证计划certification scheme认证机构certification authority检验机构inspection body authority申请人applicant合格标记mark of conformity认证体系的参与者participant in certification system认证体系的成员member of certification system批准approval型式批准type approval测试实验室的认可accreditation of testing laboratory认可accreditation认可体系accreditation system认可机构accreditation authority认可的实验室accredited laboratory认可准则accredited criteria实验室评定laboratory assessment实验室评定者laboratory assessor评审audit评审结果results of audit风险管理risk management质量特性quality characteristic质量成本quality cost质量损失quality loss质量计划quality plan质量标准quality standard质量履历quality history质量改进计划，质量改进方案quality improvement program产品质量检验product quality inspection检验inspection不定期检验non periodic inspection抽样检验sampling inspection出厂检验ex factory inspection国际标准化组织ISO(international organization for standardization) 国际标准化体制结构ISA（international standard architecture）第一方检验first party inspection第二方检验second party inspection第三方检验third party inspection第三方认证制度third party certification定期检验periodic inspection例行检验routine inspection生产检验production inspection生产定型检验production approval inspection验收检验acceptance inspection仲裁检验arbitration inspection产品质量product quality控制上限upper control limit控制下限lower control limit规格上限upper size limit规格下限lower size limit产品管理标准product management standard要求requirement质量协议quality arrangement尺寸dimension直径diameter合格测试conformity testing合格acceptable合格品acceptable part合格认证conformity certification合格认证标志mark of conformity certification合格品标志mark of acceptable product合格证书certificate of conformity评定合格assessment of conformity合格评定conformity assessment型式评价type evaluation合格证明verification of conformity合格保证assurance of conformity供货商声明supplier's declaration生产许可证production license百分比抽样检查percent sampling inspection不合格判定数rejection number不合格质量水平rejection quality level抽查型质量监督sampling quality supervision环境监测environmental monitoring抽样sampling多次抽样multiple sampling分层抽样stratified sampling分层随机抽样stratified random samplings二次抽样double sampling产品合格率product percent of pass直通率first pass yield/rolled yield发生率occurrence检验指导书inspection instruction记录record返工rework返修repair再现性repeatability报废scrap参数parameter量测measurement试验报告test report试样test sample测试设备testing equipment测试试验室testing laboratory试验test验证verification首件确认first article assurance能力指数capability index可追溯性traceability量具gage/ gauge检查表check sheets控制图control charts鱼骨图fishbone diagrams柏拉图Pareto charts零缺点ZD（zero defect）测量系统分析MSA（measurement system analysis）产品质量先期策划APQP（advanced product quality planning）统计过程控制SPC（statistical process control）过程能力指数CPK（complex process capability index）过程性能指数PPK (performance indexes of process)品质小组QCC (quality control team)一般规格GS (general specification)质量工程QE (quality engineering)可接受的质量水平AQL (acceptable quality level)百万件中有损件数DPPM (defective pieces per million units)百万分之一PPM (pieces per million)提案改善proposal improvement/ creative suggestion质量改善小组QIT (quality improvement team)质量改善QI (quality improvement)改善报告CAR (correction action report)市场营销类Marketing Management营销管理New Products Development新产品开发Service Industry Marketing服务业营销Advertising广告Business Negotiation商业谈判International Marketing国际市场营销Sales Channels销售渠道Public Relationship公共关系Consumer Behavior消费者行为Systems of Management Information管理信息系统Marketing Research营销调研accesibility 可进入性account management policies 客户管理策略positioning定位additions to existing product lines 现有产品线的增加administered vertical marketing systems 管理式垂直营销系统market segmentation市场细分sales promotion销售促进alteration 退换annual marketing plan 年度营销计划assurance 保证attitudes of consumers 消费者态度availability 可获得性/供货能力awareness （产品）知晓度/知名度behavioural analysis 行为分析benchmarking 基准benefit clusters 利益群体benefits 利益billing 帐单birth rate 出生率brand awareness 品牌意识/认知brand extensions 品牌扩展brand loyalty 品牌忠诚度brand mark 品牌标志brand name 品牌名称brand positioning 品牌定位brand recognition 品牌识别brand strategies 品牌战略brand 品牌branding strategy 品牌化战略branding 品牌化brand's equity 品牌的价值break-even analysis 盈亏平衡分析break-even volume 盈亏平衡产量breath of product assortment 产品线的宽度breath or diversity of product lines 产品线的宽度或多样性business position 经营地位business sector 商业部门business strategies 经营战略business unit strategy 经营单位战略buyers' bargaining power 买方的讨价还价能力buyers 采购者buying behavior 购买行为capital invested in product 产品投入资本catalogue sales 目录销售categorization of perception 感知分类categorization 分门别类centralization 集中化channel objectives 渠道目标channel of distribution 分销渠道channel power 渠道权力channel-control strategies 渠道控制战略channel-design decisions 渠道设计决策channel-management decisions 渠道管理决策channels of communication 传播渠道choice criteria 选择标准code of ethics （职业）道德标准collection of data 数据收集collection 收款commitment 承诺company personnel 公司员工comparative advertisements 比较广告comparison of brands 品牌比较compensation deals 补偿处理compensation plan 酬金方案compensation/rewards 酬金/奖励compensatory 补偿性的competition and industry evolution 竞争和行业演变competition-orientated pricing 竞争导向定价法competitive advantage 竞争优势competitive factors 竞争因素competitive intelligence 竞争情报/信息competitive strategy 竞争战略competitive strength 竞争优势/能力competitor analysis 竞争者分析complaint handling 投诉处理component materials and parts markets 组成材料和零部件市场conditions of demand 需求情况conflict and resolution strategies 冲突和解决战略conformance to specifications 与规格一致conformance 一致性consumer needs 消费者需求consumption 消费contests 竞赛contribution margin analysis 边际贡献（贡献毛利）分析control strategies 控制战略co-ordination and conflict resolution 协调与冲突解决corporate HQ 公司总部corporate scope 公司（经营）范围corporate strategy 公司战略cost analysis 成本分析customer satisfaction 顾客满意度customer segment pricing 顾客细分市场定价customer service 顾客服务customer-oriented pricing 顾客导向定价法customizing 定制data collection 数据收集data confidentiality 数据保密data research 数据研究data sources 数据来源deciders 决策者defect rate 缺陷率delivery time 交付时间delivery 配送demand characteristics 需求特征demand curve 需求曲线environment and packaging disposal 环境与包装处理environment factors 环境因素export 出口exporting 出口商品extended use strategy 扩大使用战略extending volume growth 扩大市场份额external data sources 外部数据来源external environment 外部环境extrapolation of past sales trends 过去销售趋势推测法gross profit 毛利gross rating points (GRPs) 总级别指数group/category product manager 类别产品经理growing markets 成长市场growth rate of market 市场增长率growth stage of product life cycle 产品生命周期的成长阶段heavy buyer 大客户line stretching 产品线延伸lost customer 失去的顾客market entry strategies 市场进入战略marketing strategy 营销战略market-management organizational structure 市场管理组织结构mission 宗旨mutual trust 相互信任opening relationships 建立关系profitability analysis 盈利性分析profitability 盈利性/盈利能力variability 变化性variable costs 可变成本vision 愿景项目管理类：目标、目的 Objective（日常）运营Operations机会Opportunity组织Organization组织图Organization Chart初始历时Original Duration （OD）输出Output参数式估算 Parametric Estimating完成百分率 Percent Complete （PC or PCT）执行质量保证Perform Quality Assurance （QA）执行质量控制Perform Quality Control （QC）绩效测量基线Performance Measurement Baseline绩效报告Performance Reporting绩效报告Performance Reports执行组织Performing Organization阶段Phase计划签约Plan Contracting计划购买和获取Plan Purchases and Acquisitions计划结束时间Planned Finish Date （PF）计划开始时间Planned Start Date （PS）计划值Planned Value （PV）计划过程Planning Processes [Process Group]职（岗）位描述Position Description惯例Practice前置活动Predecessor Activity预防措施Preventive Action概率和影响矩阵Probability and Impact Matrix流程Procedure过程Process产品Product产品生命周期Product Life Cycle产品范围Product Scope产品范围描述Product Scope Description大型项目Program大型项目管理Program Management大型项目管理办公室Program Management Office （PMO）渐进明细Progressive Elaboration项目Project项目日历Project Calendar项目章程Project Charter项目沟通管理Project Communications Management项目成本管理Project Cost Management项目人力资源管理Project Human Resource Management项目启动Project Initiation项目整体管理Project Integration Management项目生命周期Project Life Cycle项目管理计划Project Management Plan项目管理过程Project Management Process项目管理团队Project Management Team项目阶段Project Phase项目风险管理Project Risk Management项目进度Project Schedule项目进度网络图Project Schedule Network Diagram质量Quality定量风险分析Quantitative Risk Analysis规章Regulation可靠性Reliability剩余历时Remaining Duration （RD）征集资料/信息Request for Information方案征集书 Request for Proposal （RFP）报价请求Request for Quotation （RFQ）请求卖方回应Request Seller Responses已申请的变更Requested Change需求Requirement预留Reserve预留分析Reserve Analysis残余风险Residual Risk资源Resource受限于资源的进度Resource-Constrained Schedule资源图Resource Histogram职责分配矩阵Responsibility Assignment Matrix （RAM）成果、结果 Result保证金Retainage返工Rework风险Risk风险接受Risk Acceptance风险规避Risk Avoidance风险分解结构Risk Breakdown Structure （RBS）风险类别Risk Category风险数据库 Risk Database风险识别Risk Identification风险管理计划Risk Management Plan风险管理规划Risk Management Planning风险缓解Risk Mitigation风险监督和控制Risk Monitoring and Control风险响应规划Risk Response Planning风险转移Risk Transference滚动式计划 Rolling Wave Planning根本原因分析Root Cause Analysis进度、进度表Schedule进度活动Schedule Activity进度分析Schedule Analysis进度压缩Schedule Compression进度控制Schedule Control进度制定Schedule Development进度管理计划Schedule Management Plan进度里程碑 Schedule Milestone进度模型Schedule Model进度网络分析Schedule Network Analysis进度绩效指数Schedule Performance Index （SPI）进度偏差Schedule Variance （SV）计划结束时间Scheduled Finish Date （SF）计划开始时间Scheduled Start Date （SS）范围Scope模拟Simulation技能Skill特定原因Special Cause规格说明书 Specification规格限定Specification Limits人员配置管理计划Staffing Management Plan标准Standard开始时间Start Date开始-结束Start-to-Finish （SF）开始-开始Start-to-Start （SS）工作说明书 Statement of Work （SOW）子阶段Subphase子项目Subproject预定完成时间Target Completion Date （TC）预定结束时间Target Finish Date （TF）预定进度Target Schedule预定开始时间Target Start Date （TS）任务Task团队成员Team Members技术性能测量Technical Performance Measurement 技术Technique模板Template威胁Threat趋势分析Trend Analysis触发条件Triggers三约束Triple Constraint确认Validation差异Variance差异分析Variance Analysis验证Verification工作授权Work Authorization工作分解结构Work Breakdown Structure （WBS）工作项Work Item工作绩效信息Work Performance Information风险急救（方案）/风险应急方案Workaround管理项目团队Manage Project Team管理项目干系人Manage Stakeholders主进度表Master Schedule矩阵型组织 Matrix Organization财务类净收益net earning净利润net income应付票据notes payable应收票据notes receivable个人所得税 personal income tax薪金，工资 salary销售收入sales revenue营业税、销售税sales tax现金结算settlement of cash报表，清单，声明statement报表分析statement analysis会计报表statement of account现金流量表 statement of cash flows 统计分析statistical analysis剩余利润surplus profit定金down payment期限duration关税duty关税退税duty drawback免税duty free税率tax rate退税tax refund应交所得税 taxes owed应交税金taxes payable全面成本控制total cost control 总生产成本 total cost of production 总权益total equity总投资total investment总负债total liability总损益total profit and loss贸易顺差，贸易盈余trade surplus固定资产周转率turnover of fixed assets 库存周转率 turnover of inventory增值税value added tax帐目核对verification of accounts记账凭证voucher工资和薪金 wages and salaries应付工资wages payable福利费用支出welfare expenditures撤销，提款 withdrawal预提税withholding tax周转资金，流动资本working capital冲销，注销 write off年终审计year end audit年终库存year end stock年终调整year end adjustment年报yearly report收益，产出，盈利yield收益率yield rate总资产gross assets毛利，毛收益gross earnings收入总额gross income毛利gross margin收益表、损益表income statement损益表账户 income statement accounts应付帐目，应付帐款payable account收款人payee支付能力paying capacity付款，支付 payment支出payment境外付款payment abroad支付金额payment amount支付协议payment arrangement支付票据payment bill以汇票支付 payment by bill现金付款payment by cash以支票支付 payment by cheque现金付款payment by ready cash已到期应付款payment due预付货、先付payment in advance延滞付款payment in arrear税后利润profit after taxation损益帐profit and loss account损益表profit and loss statement利益分配、利润分配profit distribution营业利润profit from operating盈利企业profit making enterprises经营利润profit on operation销售利润profit on sale汇兑损益profit or loss on exchange句子类（英汉互译）：1.I would like to hold a meeting in the afternoon about our development planning for the project A.今天下午我建议我们就A项目的发展计划开会讨论一下。
Project Management Plan Template
Project Management Plan forProject NameCustomer NamePrepared by: Document AuthorDocument Author TitleProject Document IdDate Prepared: [Date_Prepared]Document InformationDistribution ListVersion HistoryTable of ContentsProprietary Notice (5)Instructions on the Use of this Template (5)Purpose: (5)Audience: (5)TeamPlay Users: (5)Customer Version: (5)References: (6)1.Executive Summary (7)2.Introduction (7)2.1.Customer’s Purpose and Goals (7)2.2.Project Goals and Strategy (8)2.3.Constituent Projects (8)2.4.Critical Success Factors (8)2.5.Key Milestones (8)2.6.Assumptions (8)2.7.Constraints and Dependencies (8)2.8.Definitions (8)2.8.1.Terms (8)2.8.2.Abbreviations (8)3.Scope & WBS (8)3.1.Solution Overview (8)3.2.Scope (8)3.3.Project Deliverables (9)3.4.WBS (9)4.Activities and Estimates (9)4.1.Activities and Estimates (9)5.Schedule (9)5.1.Project Schedule (9)estone List (10)6.Resources (10)6.1.Project Organisation Structure (10)6.2.Responsibilities (10)6.3.Material and Supplies Resources (10)6.4.Facilities (11)6.5.Other (11)munication (11)7.1.Stakeholders (11)7.2.Status Meetings (11)7.3.Status Reporting (11)8.Project Risks (12)8.1.Risk Identification, Assessment and Risk Responses (12)8.2.Risk Management Plan (12)9.Project Processes (12)9.1.Project Tracking and Control (13)9.2.Change Control Process (13)9.3.Customer Acceptance Process (13)9.4.Issue Management and Escalation Process (13)9.5.Warranty (13)10.Appendices (13)10.1.Supplemental Plans (13)10.2.Attachments (14)Proprietary NoticeInstructions on the Use of this Template(delete the section when using the template)Purpose:The purpose is to communicate:●Project goals and the means to achieve them●Resources required (time, money, personnel) and of milestones that have been or will beachieved●Assumptions that were made in determining how the project's goals will be met●Project risks as well as the associated risk response plansThe template provides the structure for the central parts of most projects, however more plans maybe needed depending on the specific project requirements. The project manager must exercise sound business judgment to determine whether the template has the adequate sections or not. If not, the project manager decides whether to include more sections in the template or to develop separate plans.The template does not include sections for:●Quality Plan●Acceptance Test Plan●Deployment Plan●Configuration Management Plan●Contract and Procurement Plan●Warranty Plan●Support PlanAudience:The primary audience for the Project Management Plan document is HW management, who approves the plan.An adapted version of this Project Management Plan may also be shared with the customer because, for the solution to be a success, the customer must "buy into" the plan for producing it.Finally, a completed Project Management Plan may be used as a reference document by project teams and project managers involved in related or similar efforts.TeamPlay Users:If you have, or will, produce a Project Data Sheet (PDS), you are not required to complete every section described in this template. TeamPlay users with a PDS must complete the following sections:●Introduction: definitions, terms and abbreviations●Resources -the entire section●Communication - the entire section●Project Processes - entire sectionCustomer Version:Before distributing this Project Management Plan it must be adapted to remove proprietary information. The project manager, together with HW management, must determine what information in the plan is appropriate to give the customer and how best to provide it (e.g., sections 4. Activitiesand Estimates, 6. Resources, and 8. Project Risks are critical to revise and/or remove before distribution).References:Visit the HW Global Method website to see a number of references to aid in project planning, including:●PJM0100G Applying Global Method PM Guide●PJM1100G Integration Management Guide●PJM1300G Issue Management Guide●PJM1400G Change Control Guide●PJM2101G Scope Management Guide●PJM2150G Work Breakdown Structure Guide●PJM3100G Time Management Guide●PJM4100G Cost Management Guide●PJM5100G Quality Management Guide●PJM6100G HR Management Guide●PJM6500G PMO Practices & Procedures Guide●PJM7100G Communications Management Guide●PJM7150G Project Document Management Guide●PJM8100G Risk Management Guide●PJM9100G Procurement Management Guide1.Executive Summary[At a minimum, include:The project nameThe customer nameAll locations involvedA brief project historyA description of the projectA description of the solution to be deliveredAny other information relevant to the project]Table 1.1 Project Summary2.Introduction2.1.Customer’s Purpose and Goals[Briefly describe the customer’s business needs and problems, explain what the purpose of the project is from a customer perspective.]Table 2.1 Triggering Problems/Opportunities:2.2.Project Goals and Strategy[Describe the project goals, and how they will be met – for example, through a turnkey solution, a partnership with the customer, or integration with third-party solutions. Describe how this project is aligned with / impacts the strategy for the account.]2.3.Constituent Projects[List constituent projects of this project/program. Identify project managers both for HW and third party projects. Cover customer managed project when appropriate.]2.4.Critical Success Factors[Describe the items that need to be in place for the project to be successful.]2.5.Key Milestones[Summarise from the milestone table in section 5.2]2.6.Assumptions[List the assumptions on which the HW solution has been built.]2.7.Constraints and Dependencies[Describe the limitations and external dependencies that could impact the success of the project. Describe the interfaces to organisations external to the project that are essential to its success.] 2.8.Definitions[Describe any terms, acronyms and abbreviations required to understand this document.]2.8.1.Terms2.8.2.Abbreviations3.Scope & WBS3.1.Solution Overview[Provide a high-level description of HW's solution.]3.2.Scope[Provide a statement that describes the limits of the project (describe the what, the who, the where, and the quality criteria of the project). Document what the project will not address.]Table 3.1 Logical Boundaries - What's In, What's Out3.3.Project Deliverables[List the major project deliverables, and refer to the document where the detailed descriptions of the deliverables and sub-deliverables can be found.]Table 3.2 Deliverables Overview3.4.WBS[Provide a graphical or tabular overview of th e project’s WBS, or refer to the document where the WBS can be found.]4.Activities and Estimates4.1.Activities and Estimates[Breakdown the project deliverables and sub-deliverables into activities and provide the following information per activity: activity description, effort estimates, resources/skills required, and the name of the responsible person.]Table 4.1 Activities and Estimates5.Schedule5.1.Project Schedule[Include a high-level schedule for the major deliverables listed in the Work Breakdown Structure (WBS). For each primary deliverable, include duration, start date and end date. Or if a Microsoft Project schedule has been created, a high-level (collapsed) version can be pasted into this section; however, do not paste in the detailed Microsoft Project Gantt Chart.]Table 5.1 Schedule Summaryestone List[Detail the major milestones for the project and indicate the status of the milestones at any given time during the project.]Table 5.2 Project Milestones6.Resources6.1.Project Organisation Structure[Insert organisational chart]6.2.Responsibilities[Define the responsibilities for each resource on the organisation chart ---- HW, the customer, and all internal and external participants.]Table 6.2 Project Responsibilities[List the internal HW resources that are indirectly involved in the project (account manager, financial analyst, legal support, etc.)]Table 6.3 HW Internal Management & Supporting Responsibilities6.3.Material and Supplies Resources[Identify the material and supplies that are needed for each phase. Describe the requirements for telephone access, reprographics support, special technical equipment, and any special computer system needed.]6.4.Facilities[Describe the requirements for workspace, office space, or any special facility requirement.]6.5.Othermunication7.1.Stakeholders[Provide list of stakeholders contact information. List all individuals who are directly and indirectly involved with the project.]Table 7.1 StakeholdersTable 7.2 Organisational Impact7.2.Status Meetings[Define the type and frequency of control / status meetings, and identify meeting participants] Table 7.3 Status Meetings7.3.Status Reporting[Describe the required status reporting requirements for the project. Include details for status reporting to the customer, to internal HW individuals and groups, and to the project manager from project team.]Table 7.4 Status Reporting8.Project Risks8.1.Risk Identification, Assessment and Risk Responses[List the risks that have been prioritised, provide a brief description of the impact of the risk if it occurs. List the risk response strategy that has been chosen for each risk (Avoidance, Transference, Mitigation, or Acceptance), and attach the latest copies of the Risk Response Plan. If risks are identified and responses are planned in a risk log, then attach a copy of the risk log here.]Table 8.1 Project Risk Overview8.2.Risk Management Plan[Describe how the risk management of the project will be performed. Describe the planned frequency for reviewing the project risks, and how the project risks will be monitored and tracked. Engagements with HWS Total Contract Value > $500K US cannot use this section and must create a separate risk management plan using PJM8120 Risk Management Plan template.]9.Project ProcessesTable 9.1 Process Summary9.1.Project Tracking and Control[Describe the project tracking and control processes e.g. for cost, scope, schedule. Refer to section 7.2 Status Meeting and 7.3 Status Reporting as appropriate.]9.2.Change Control Process[Define the change control process that will be used by the project. Specify how to initiate a change request, how changes will be evaluated and how change requests will be approved or rejected. Specify use of the Change Request template and the Change Request Log.]9.3.Customer Acceptance Process[Describe the process that will be used to obtain the client’s acceptance for project deliverables.] 9.4.Issue Management and Escalation Process[Clearly define the process to be followed for issues and escalations. Include impact criteria relevant for the project. Specify use of the Issue Report template and the Issue Log.]9.5.Warranty[Describe the approach to provide warranty for the project’s products and or services. Describe any warranty processes. Identify and estimate the resources required to provide warranty services.] 10.Appendices10.1.Supplemental Plans[A project management plan can be supported by supplemental plans. These supplemental plans can provide additional details if required. Insert any supplemental plans here or specify where they are located. Supplemental plans may be formal documents that are very detailed or they may be more informal and less detailed, depending on the project.][Supplemental plans recorded in separate files can be added as embedded objects (as an icon). How to:-In the menu bar under “Insert”, choose “Object”-Choose “Create from File” and browse to find the file you want to attach-Check the field saying: “Display as icon”. (Do NOT check the field saying: “link to file”)-Click OK]Acceptance Test Plan - defines the how the solution acceptance processes will be managed for the project. This includes definition of key testing milestones, resources, tasks and schedule as well as the overall strategy and approach for acceptance testing.Communications Management Plan - defines procedures for storing documents, details on how information will be distributed, descriptions of the types of information that will be distributed, aschedule for the distribution, details on how to access information, and the process for updating the plan itself.Cost Management Plan - describes how cost variances will be identified and managed.Procurement Management Plan - defines how all the Procurement Management processes will be managed for the project. This may include what types of contracts will be used, what standard documents are available and where to find them, what the team is responsible for vs. the purchasing department, and what system will be used for selecting vendors.Quality Management Plan - describes how quality management activities will be structured and performed to implement the project quality system.Risk Response Plan - For each key risk, describes the actions that will be taken for the chosen response technique.Schedule Management Plan - provides information on how to manage changes to the schedule. This will often reference an existing change management procedure or forms with any specifics, if applicable.Scope Management Plan - documents the expected stability of the project and how the project scope will be managed, including the approach for accepting scope changes including their identification and classification.Solution Support Plan - provides the information needed by an operational support manager to identify, plan, and organise the implementation of all operational support for a specific solution delivered during the installation and operation phases of project life cycle.Staffing Management Plan - defines how and when staff will be engaged for the project. This plan typically becomes more formal as the size and complexity of the project increases. A more detailed plan might include a resource histogram to show the rise and fall of resource requirements for the project.10.2.Attachments[List all attachments and reference documents here.]Table 10.1 Other Attachments and References。
GRE考试：issue写作指导(提纲 模板)
GRE考试：issue作文重点题目和提纲gre issue 提纲“It is dangerous to trust only intelligence.”只相信智力是危险的。
【分析题目】拿到一个题目后，我们不要忙于去写，一定要先对题目进行详细的分析。
通过题目我们知道主要论证的是intelligence的作用，因此，智力是这个题目最关键的突破点。
【提纲1】A. 无可否认的，智力因素在各个领域都很重要，无论是自然科学还是社会科学。
(论据1)Undoubtedly, intelligence plays an important role in many realms, including the natural science and the social sciences.B.要想成功光靠智力是远远不够的，还有很多其他的因素如勤奋、勇敢等。
(论据2)Intelligence by itself is not enough for one to succeed; many other factors such as diligence and courage must be taken into consideration.C.应该在此二者之间寻求平衡，即将两者结合起来。
We should strive for a balance between intelligence and emotion, that is, combine them with each other.【提纲2】Position: Intelligence is sufficient in some cases but not in any case.1、In scientific studies regarding the physical world, we should depend only on intelligence for discovering and testing truths.2、However, in the realm of human affairs, we have to use both our intelligence and our hearts for solving problems.3、Sometimes our intuition can give us valuable assistance in making a judgment.GRE考试：issue字数gre issue 字数要求是怎样的?很多考生担心考试时issue 字数上不去。
关于SSHH_config配置文件中GSSAPIAuthentication选项的作用
关于SSHH_config配置文件中GSSAPIAuthentication选项的作用关于 SSHH_config 配置文件中GSSAPIAuthentication选项的作用我的系统是CENTOS 5.3 ，SSH连接起来很慢，本身是内网，很慢让人受不了，基本上要近一分钟才出现提示输入密码。
基本上解决办法就：1，禁用DNS反向解析UseDNS no2，还有系统默认有个忽略以前登录过主机的记录，将这个打开基本上就会解析登录慢的问题IgnoreRhosts yes重启SSH服务service sshd reload3、修改“GSSAPIAuthentication”的值为“no”（没有的添加该配置选项，注释掉的放开即可）；其实用户可以自己运行“ssh -v host”进行debug的，通过debug信息就可以看到连接到什么地方被耽搁了；我的测试就是在"debug1: Unspecified GSS failure. Minor code may provide more information" 这里停顿了一会儿，所以感觉修改“GSSAPIAuthentication”的值应该会有效果，但实践证明，如果不改上面几项，该处更改在我的系统依然不起作用！# 1. 关于 SSH Server 的整体设定，包含使用的 port 啦，以及使用的密码演算方式Port 22 # SSH 预设使用 22 这个 port，您也可以使用多的 port ！# 亦即重复使用 port 这个设定项目即可！Protocol 2,1 # 选择的 SSH 协议版本，可以是 1 也可以是 2 ，# 如果要同时支持两者，就必须要使用 2,1 这个分隔了！#ListenAddress 0.0.0.0 # 监听的主机适配卡！举个例子来说，如果您有两个 IP，# 分别是 192.168.0.100 及 192.168.2.20 ，那么只想要# 开放 192.168.0.100 时，就可以写如同下面的样式：ListenAddress 192.168.0.100 # 只监听来自192.168.0.100 这个 IP 的SSH联机。
Visual Studio 用户指南说明书
Table of ContentsAbout1 Chapter 1: Getting started with Visual Studio2 Remarks2 Versions2 Examples3 Installation or Setup4 Chapter 2: Adding an extension5 Examples5 Adding an extension to visual studio using a `VSIX` file5 Adding an extension to visual studio from Visual Studio Gallery5 Chapter 3: Code Contracts9 Remarks9 Examples9 Standard precondition9 Precondition that throws a specific Exception9 Pre and postconditions9 Chapter 4: Connecting your visual studio project to Github10 Examples10 Publishing your project to a github repository removing sensitive data10 Chapter 5: Visual Studio tools18 Examples18 Code Lens18 Snippets18 Intoduction18 Using the code181. Header192. Snippet202.1 Imports202.2 Declarations212.3 References222.4 Code22 Import Snippet into Visual Studio25 Point of intrest27 Override merge/compare tools27 Entity Framework28 Credits29AboutYou can share this PDF with anyone you feel could benefit from it, downloaded the latest version from: visual-studioIt is an unofficial and free Visual Studio ebook created for educational purposes. All the content is extracted from Stack Overflow Documentation, which is written by many hardworking individuals at Stack Overflow. It is neither affiliated with Stack Overflow nor official Visual Studio.The content is released under Creative Commons BY-SA, and the list of contributors to each chapter are provided in the credits section at the end of this book. Images may be copyright of their respective owners unless otherwise specified. All trademarks and registered trademarks are the property of their respective company owners.Use the content presented in this book at your own risk; it is not guaranteed to be correct nor accurate, please send your feedback and corrections to ********************Chapter 1: Getting started with Visual Studio RemarksVisual Studio is an Integrated Development Environment (IDE) from Microsoft. It enables the developer to work project orientated with various types of projects, including Windows Forms, Console Applications, Office Plug-Ins, and Windows Universal Apps.The IDE supports various programming languages, the most common being Visual C#, Visual Basic, Visual F#, and Visual C++.There are several editions of Visual Studio: Community (free), Express (free), Professional, Enterprise, and Ultimate (However, not all are available for all versions).VersionsExamplesInstallation or SetupVisual Studio can be downloaded and installed for free in Comunity edition from the Microsoft site and can be also found in different versions. Just click on the Download button and run the executable, then follow the instructions.Read Getting started with Visual Studio online: https:///visual-studio/topic/972/getting-started-with-visual-studioChapter 2: Adding an extensionExamplesAdding an extension to visual studio using a `VSIX` fileIf you have a vsix file, you can install it by running the file.Get the vsix file (this is the extension installer)1.2.Run the file.3.In the window that opens, confirm the installation.Adding an extension to visual studio from Visual Studio GalleryIn Visual studio•go to Tools > Extensions and updates...•In the window that opens go to online•Select Visual Studio GalleryYou can search for an extension on the search box at the upper right corner••Select the extension you want to addClick on download.••Once download is complete, click on the Install button on the window that opened.•In order to use the extension, you might be requested to restart visual studioRead Adding an extension online: https:///visual-studio/topic/2257/adding-an-extensionChapter 3: Code ContractsRemarksIn order to fully benefit from Code Contracts you need to install the extension for Visual Studio. There's also a Code Contracts User Manual.ExamplesStandard preconditionusing System.Diagnostics.Contracts;public int DivideNumbers(int numerator, int denominator){Contract.Requires(denominator != 0);return numerator / denominator;}Precondition that throws a specific Exceptionusing System.Diagnostics.Contracts;public int DivideNumbers(int numerator, int denominator){Contract.Requires<ArgumentOutOfRangeException>(denominator != 0);return numerator / denominator;}Pre and postconditionsusing System.Diagnostics.Contracts;public int IncrementByRandomAmount(int input){Contract.Requires<ArgumentNullException>(input != null); // Don't allow null parameter. Contract.Requires<ArgumentOutOfRangeException>(input < int.MaxValue); // We can't do anything if we're given int.MaxValue.Contract.Ensures(Contract.Result<int>() > input); // Return value will be greater than input value.Random rnd = new Random();input += rnd.Next(1, 13); // Creates a number between 1 and 12 and adds it to input.return input;}Read Code Contracts online: https:///visual-studio/topic/6311/code-contractsChapter 4: Connecting your visual studio project to GithubExamplesPublishing your project to a github repository removing sensitive datathe steps in this example will use the following project structure as a demonstrationand we intend to export it to the "GHTuts" Repository [Note that the Repo doesn't exist yet on github] but leave the "SensitiveProject" without publish as it contains some passwords, keys, etc..1.First of all we make sure the source control plug in is set to "Git" in "Tools > Options > Plug-in Selection"If you can't see the "Team Explorer" tab, view it in visual studio like this 2. Go to your local solution folder and create a new file called ".gitignore.txt" [Note] this step is only important if you have some sensitive information in your project,otherwise, let visual studio create it for you1. Now open the ".gitignore.txt" file and paste this in it, this is a template for ignoring common visual studio files (check the links below)2. ## Ignore Visual Studio temporary files, build results, and## files generated by popular Visual Studio add-ons.# User-specific files*.suo*.user*.userosscache*.sln.docstates# User-specific files (MonoDevelop/Xamarin Studio)*.userprefs# Build results[Dd]ebug/[Dd]ebugPublic/[Rr]elease/[Rr]eleases/x64/x86/bld/ [Bb]in/[Oo]bj/[Ll]og/# Visual Studio 2015 cache/options directory.vs/# Uncomment if you have tasks that create the project's static files in wwwroot #wwwroot/# MSTest test Results[Tt]est[Rr]esult*/[Bb]uild[Ll]og.*# NUNIT*.VisualState.xmlTestResult.xml# Build Results of an ATL Project[Dd]ebugPS/[Rr]eleasePS/dlldata.c# DNXproject.lock.jsonproject.fragment.lock.jsonartifacts/*_i.c*_p.c*_i.h*.ilk*.meta*.obj*.pch*.pdb*.pgc*.pgd*.rsp*.sbr*.tlb*.tli*.tlh*.tmp*.tmp_proj*.log*.vspscc*.vssscc.builds*.pidb*.svclog*.scc# Chutzpah Test files_Chutzpah*# Visual C++ cache filesipch/*.aps*.ncb*.opendb*.opensdf*.sdf*.cachefile*.VC.db*.VC.VC.opendb# Visual Studio profiler*.psess*.vsp*.vspx*.sap# TFS 2012 Local Workspace$tf/# Guidance Automation Toolkit*.gpState# ReSharper is a .NET coding add-in_ReSharper*/*.[Rr]e[Ss]harper*er# JustCode is a .NET coding add-in.JustCode# TeamCity is a build add-in_TeamCity*# DotCover is a Code Coverage Tool*.dotCover# NCrunch_NCrunch_*.*crunch*.local.xmlnCrunchTemp_*# MightyMoose*.mm.*/# Web workbench (sass).sass-cache/# Installshield output folder[Ee]xpress/# DocProject is a documentation generator add-in DocProject/buildhelp/DocProject/Help/*.HxTDocProject/Help/*.HxCDocProject/Help/*.hhcDocProject/Help/*.hhkDocProject/Help/*.hhpDocProject/Help/Html2DocProject/Help/html# Click-Once directorypublish/# Publish Web Output*.[Pp]ublish.xml*.azurePubxml# TODO: Comment the next line if you want to checkin your web deploy settings# but database connection strings (with potential passwords) will be unencrypted*.pubxml*.publishproj# Microsoft Azure Web App publish settings. Comment the next line if you want to# checkin your Azure Web App publish settings, but sensitive information contained# in these scripts will be unencryptedPublishScripts/# NuGet Packages*.nupkg# The packages folder can be ignored because of Package Restore**/packages/*# except build/, which is used as an MSBuild target.!**/packages/build/# Uncomment if necessary however generally it will be regenerated when needed#!**/packages/repositories.config# NuGet v3's project.json files produces more ignoreable files*.nuget.props*.nuget.targets# Microsoft Azure Build Outputcsx/*.build.csdef# Microsoft Azure Emulatorecf/rcf/# Windows Store app package directories and filesAppPackages/BundleArtifacts/Package.StoreAssociation.xml_pkginfo.txt# Visual Studio cache files# files ending in .cache can be ignored*.[Cc]ache# but keep track of directories ending in .cache!*.[Cc]ache/# OthersClientBin/~$**~*.dbmdl*.dbproj.schemaview*.pfx*.publishsettingsnode_modules/orleans.codegen.cs# Since there are multiple workflows, uncomment next line to ignore bower_components # (https:///github/gitignore/pull/1529#issuecomment-104372622)#bower_components/# RIA/Silverlight projectsGenerated_Code/# Backup & report files from converting an old project file# to a newer Visual Studio version. Backup files are not needed,# because we have git ;-)_UpgradeReport_Files/Backup*/UpgradeLog*.XMLUpgradeLog*.htm# SQL Server files*.mdf*.ldf# Business Intelligence projects*.rdl.data*yout*.bim_*.settings# Microsoft FakesFakesAssemblies/# GhostDoc plugin setting file*.GhostDoc.xml# Node.js Tools for Visual Studio.ntvs_analysis.dat# Visual Studio 6 build log*.plg# Visual Studio 6 workspace options file*.opt# Visual Studio LightSwitch build output**/*.HTMLClient/GeneratedArtifacts**/*.DesktopClient/GeneratedArtifacts**/*.DesktopClient/ModelManifest.xml**/*.Server/GeneratedArtifacts**/*.Server/ModelManifest.xml_Pvt_Extensions# Paket dependency manager.paket/paket.exepaket-files/# FAKE - F# Make.fake/# JetBrains Rider.idea/*.sln.iml3.Now add your sensitive project folder to the ".gitignore.txt" file at any line that doesn't contain #, so just add it at the very end, and it should look something like this4.Right click on the solution and choose "Add Solution to Source Control..."[Note] it might ask you to save the solution before you continueNow you have a "LOCAL" git Repo on your pc , which VS will read from,but without a github 5.Repo, and you will see a small blue lock icon next to each file in the solution that was addedto git and a red circle at the ignored project[Note]for more information about .gitignore file, check these links•https:///articles/ignoring-files/•https:///github/gitignoreGo to the "Team Explorer" tab and then "Sync"7.Now we create a repo from vs to github like this, press the "Get Started" button8.Now fill in your information in github for the new Repo, then click "Publish"9. Now when we go to github we see our local repo got published to github without oursensitive project [Note]the url of the repo will look something like thishttps:///<user name>/<repo name>10. Read Connecting your visual studio project to Github online: https:///visual-studio/topic/3826/connecting-your-visual-studio-project-to-githubChapter 5: Visual Studio toolsExamplesCode LensCode lens is a simple way to know what happens with the code. Here you could find an image with the number of references of a method or class.If you can't see the code lens please see this question: Missing CodeLens references count in VS 2015 Community editionSnippetsIntoductionSince Visual Studio 2005 can you make Intellisense Code Snippets. This allow you to generate some code just by typing one keyword and press two times the tab key.Using the codeThe XML code you need for make an Intellisense Code Snippet stands below:<?xml version="1.0" encoding="utf-8"?><CodeSnippets xmlns="/VisualStudio/CodeSnippet"><CodeSnippet Format="1.0.0"> <!-- format attribute is required --><Header> <!-- 1 --><Title></Title><Author></Author><Shortcut></Shortcut><Description></Description><Keywords><Keyword>abc<Keyword><Keyword>def<Keyword></keywords></Header><Snippet> <!-- 2 --><Imports> <!-- 2.1 --><Import><Namespace>System</Namespace></Import></Imports><Declarations> <!-- 2.2 --><Literal Editable="true/false"> <!-- 2.2.1 --><ID>example</ID><Type>System.String</Type><ToolTip>A tip you can show</ToolTip><Default>default value</Default><Function></Function> <!-- 2.2.2 --></Literal><Object> <!-- 2.2.1 --><ID>example</ID><Type>System.String</Type><ToolTip>A tip you can show</ToolTip><Default>default value</Default><Function></Function> <!-- 2.2.2 --></Object></Declarations><References> <!-- 2.3 --><Reference><Assembly>System.Data.dll</Assembly></Reference></References><Code Language=""> <!-- 2.4 --><![CDATA[<!-- your code here if you use literals use dollar chars -->]]></Code></Snippet></CodeSnippet></CodeSnippets>In the snippet tag, you have two required tags named Header and Snippet. You can find more information in next headings. The number near the name are correspondents with the numbers in the code above.There can be zero or more CodeSnippet elements added into the CodeSnippets element.1. HeaderIn the Header-tag, you can place some specific information about the snippet and what he does. The important tags you can use inside this tag are:Source table (but edits): 2. SnippetIn the snippet tag, you can use three different tags. This can be:•Imports•Declarations•Code (required)•ReferencesThese are explained below.2.1 ImportsImports contain the needed namespaces you need for the code. Use the import-tag inside this tag and here you can place the needed namespaces each with the Namespace-tag.2.2 DeclarationsDeclarations can be used for declaring some literals or objects into your code in the Code-tag. The children are literals and objects.2.2.1 Literals and objectsLiterals and objects define the literals and objects of the code snippet that you can edit. Functionality are literals and objects are the same, but it has an additional type constraint.The Literal and object-tag can contain next children:•ID: The ID of the literal (required)•Type: The type of that object including namespace and class (required by objects)•ToolTip: Gives a tip•Default: A default value of that object (required)•FunctionsIn the snippets, there are some predefined literals. They are listed below:Functions in the Literal- or Object-tag means that you can use a function for generating code depending on another element. There are three functions that I know:1 only available in Visual Studio 2005.Source table: Attributes for the Literal and Object ElementsThe Literal and Object tags can have some optional attributes.Source table: 2.3 ReferencesGroups reference elements that contains information about assembly references for the code snippet. This can contain next elements:Assembly: Contains the name of the assembly by the code snippet (required)•Url: Contains a website that gives more information about the assembly•2.4 CodeCode is the code you will generate between <![CDATA[ and ]]>. Place the ID of your literal between dollar chars and Visual Studio will ask you for change these default value if the declarations are filled in. Here, you've an example for C# and VB for the shortcut propfull.<!-- ... Other code ... --><Declarations><Literal><Id>variablename</Id><Default>_myproperty</Default></Literal><Literal><Id>propertytype</Id><Default>int</Default></Literal><Literal><Id>propertyname</Id><Default>myproperty</Default></Literal></Declarations><Code Language="CSharp"><![CDATA[private $propertyvalue$ $variablename$;public $propertyvalue$ $propertyname${get { return $variablename$; }set { $Variablename$ = Value; }}]]></Code><!-- ... Other code ... --><Declarations><Literal><Id>variablename</Id><Default>_myproperty</Default></Literal><Literal><Id>propertytype</Id><Default>int</Default></Literal><Literal><Id>propertyname</Id><Default>myproperty</Default></Literal></Declarations><Code Language="VB"><![CDATA[Private $variablename$ As $propertyvalue$Public Property $propertyname$ As $propertyvalue$GetReturn $variablename$End GetSet (ByVal value As $propertyvalue$)$variablename$ = valueEnd SetEnd Property]]></Code><!-- ... Other code ... -->In the required Language attribute, you can define your language where you are making thesnippet. You can find the languages you can use in the next table.Other optional attributes are:The valid values for the kind variable are:Source tables: Import Snippet into Visual Studio1.Save the XML code and give it the extension .snippet.You can add the new made snippet into Visual Studio by pressing Control + K, Control + B or2.go to "Tools" → "Code Snippets Manager...". This open next window:Choose the language into the combo box for which language you've made the snippet. click on "Import..."and choose the file you've made.3. Click on "Finish". If the file name already has been used, Visual Studio go ask to override the existing file. You've three options:Overwrite: Overwrites the file. You can use this option if you will edit an old snippet.•Rename: Goes to rename the file to an unique name.•Skip: Cancels the import. Renames the file to a unique name.•4. You could also add a new location with all the snippets you've made by clicking on the "Add..." button on the first window and select the folder in the "select folder window". The advantage is now when a new valid snippet is added in that folder, you can use this directly in Visual Studio.Note: Test after importing your snippet for errors, so you don't have any problems when you usethe snippet. You can always remove or overwrite the snippet if there is an error.Point of intrestYou can also see the documentation on MSDN for more information.Override merge/compare toolsGot to Tools | Options | Source Control | Visual Studio Team Foundation Serverclick on the Configure User Tools:You can add separate overrides for 'Compare' and 'Merge' operations. Click on Add and select the operation you want to override. You'd need to type the path to the tool you use, and the exact arguments your tool expects. For example to use BeyondCompare, add the following Arguments " %1 %2 /title1=%6 /title2=%7":To Merge with BeyondCompare use the Arguments "%1 %2 %3 %4 /title1=%6 /title2=%7/title3=%8 /title4=%9"In a 2006 blog post MS employee James Manning surveyed the arguments as expected by various tools: WinDiff, DiffDoc, WinMerge, Beyond Compare, KDiff3, Araxis, Compare It!, SourceGear DiffMerge, TortoiseMerge and Visual SlickEdit. The post is a good starting point, but be sure to check the up to date documentation of your tool.It is highly recommended not to use for merge tools that are incapable of 3-way merges (e.g., WinMerge 2.x).Entity FrameworkEntity Framework (EF) is an object-relational mapper that enables .NET developers towork with relational data using domain-specific objects. It eliminates the need for mostof the data-access code that developers usually need to write.Entity Framework allows you to create a model by writing code or using boxes andlines in the EF Designer. Both of these approaches can be used to target an existingdatabase or create a new database.Source and more information: Entity Framework documentationRead Visual Studio tools online: https:///visual-studio/topic/2398/visual-studio-toolsCredits。
WLAN故障排错综合指导
WLAN 故障排错综合指导ISSUE 1.0日期：2009年8月11日作者：张利兵密级：内部公开课程目标学习完本课程，您应该能够：n掌握FIT AP注册过程中问题的排查思路n了解用户无线使用常见类问题n了解无线产品的几个常见问题n掌握无线用户ping 丢包定位思路及优化措施n掌握WDS问题定位思路及方法n了解部分特性设置及功能说明目录n FIT AP注册问题排查综合指导n无线用户使用常见问题及原因判定n无线产品部分常见问题处理指导n用户ping丢包问题排查综合指导n无线WDS桥接问题定位指导n无线部分特性设置及功能说明FIT AP注册问题排查综合指导（一）l造成注册失败的可能原因分析à一、网络建设问题：1、AP没有上电；2、AP连接的网线存在问题；à二、设备配套问题：1、AP设备提供的信息不匹配；2、AP设备和AC设备的版本不匹配；à三、网络配置问题：1、AP上联的交换机如果启动STP时，一定要将AP连接接口设置为边缘端口，否则可能带来AP注册不成功问题；2、AP所在的网络中没有DHCP服务器；3、AP接入的VLAN网络不正确；4、AP和AC三层组网，但是AP和AC之间网络不通；5、AP和AC三层组网，但是没有使用DHCP option43功能或者DNS功能为AP指定AC列表；6、AC上没有为AP配置对应的模版；7、网络配置变化（例如DHCP服务器配置发生变化），AP没有及时更新相应的地址信息或者AC列表；à四、设备异常带来的问题：1、Fit AP设备出现个体异常，设备无法正常启动；2、Fit AP设备出现个体异常，上行接口工作异常；3、Fit AP设备的CAPWAP任务挂起；FIT AP注册问题排查综合指导（二）l二层网络没有注册成功A P快速排查l三层网络没有注册成功A P快速排查l AP处于不停下载版本的状态出现上面不断进行版本下载的原因可能为：1、AC上放置的Fit AP的版本和AC需要配套的版本不匹配；2、AC上没有Fit AP的型号对应的版本；3、Fit AP设备上没有足够的空间存放下载下来的新版本。
微Focus Fortify软件22.2.0版本发布说明说明书
Micro Focus Fortify Software, Version 22.2.0Release NotesDocument Release Date: November 2022, updated: 1/31/2023Software Release Date: November 2022IN THIS RELEASEThis document provides installation and upgrade notes, known issues, and workarounds thatapply to release 22.2.0 of the Fortify product suite.This information is not available elsewhere in the product documentation. For information onnew features in this release, see What's New in Micro Focus Fortify Software 22.2.0, which isavailable on the Micro Focus Product Documentation website:https:///support/documentation.FORTIFY DOCUMENTATION UPDATESAccessing Fortify DocumentationThe Fortify Software documentation set contains installation, user, and deployment guides. Inaddition, you may find technical notes and release notes that describe forthcoming features,known issues, and last-minute updates. You can access the latest HTML or PDF versions ofthese documents from the Micro Focus Product Documentation website:https:///support/documentation.If you have trouble accessing our documentation, please contact Fortify Customer Support.•The Micro Focus Fortify Plugin for Eclipse User Guide now covers only the Fortify Eclipse Complete Plugin. The new document Micro Focus Fortify Remediation Pluginfor Eclipse User Guide describes the Fortify Remediation plugin for Eclipse.•The Micro Focus Fortify Plugins for JetBrains IDEs and Android Studio User Guide has been renamed to Micro Focus Fortify Analysis Plugin for IntelliJ IDEA and AndroidStudio User Guide and covers only the Fortify Analysis plugin. A new document MicroFocus Fortify Remediation Plugin for IntelliJ IDEA and Android Studio User Guidedescribes the Fortify Remediation plugin.•Support for versions of the GNU gcc and GNU g++ compilers has been expanded to 6.x – 10.4 on Windows, Linux, and macOS operating systems. This change is documented inthe Compiler section of the Micro Focus Fortify Software System Requirements.INSTALLATION AND UPGRADE NOTESComplete instructions for installing Fortify Software products are provided in the documentation for each product.Fortify Static Code AnalyzerMigrating from a Patched Release of Fortify Static Code Analyzer: If your Fortify Static Code Analyzer installation has been patched, the last digit in the version number will be greater than zero. For instance, release 21.2.0 has a zero as the last digit which identifies it as a major release that has not been patched. Versions 20.1.6, 20.2.4, 21.1.4, and 21.2.3 are examples of patched releases. When upgrading from a patched Fortify Static Code Analyzer release, your configuration files and properties (fortify-sca.properties) might not carry over to the new installation. If you would like to migrate your configuration and properties settings to the new installation, please contact Fortify Customer Support for assistance.Fortify Audit Workbench, Secure Code Plugins, and Tools•Eclipse Remediation Plugin is not included inthe Fortify_SCA_and_Apps_<version>_<OS>.zip in this release. It isavailable for download from the Eclipse Marketplace.•IntelliJ IDEA and Android Studio Remediation Plugin is not included in the Fortify_SCA_and_Apps_<version>_<OS>.zip in this release. It is available fordownload from the JetBrains Marketplace.USAGE NOTES FOR THIS RELEASEThere is a landing page (https://fortify.github.io/) for our consolidated (Fortify on Demand + Fortify On-Premises) GitHub repository. It contains links to engineering documentation and the code to several projects, including a parser sample, our plugin framework, and our JavaScript Sandbox Project.Fortify Static Code Analyzer•The SCAState utility does not work in the 22.2.0 release. This functionality will be restored in the upcoming 22.2.1 patch. If you require the SCAState functionality in the22.2.0 release, you can request a hotfix through Customer Support.•For security reasons, Fortify Static Code Analyzer sample projects have been removed from the installer. These samples are now available as a separate ZIP package.Fortify Software Security Center•Recent Chrome or Chromium-based browsers default to SameSite=Lax cookie policy.That means cookies are not sent with sub-requests to 3rd-party sites. Therefore, SAMLSingle Logout will not work correctly in cases when it is not initiated from FortifySoftware Security Center. To make SAML Single Logout work in Chrome or Chromium-based browsers, SameSite policy for session cookies must be changed to “None”. Please note that this denotes less secure policy than the default one, so changing it is left for your consideration. To change the policy for container deployments, useHTTP_SERVER_SAME_SITE_COOKIES environment variable. For non-container deployments, add <CookieProcessor sameSiteCookies="none"/> to the context section of your Tomcat configuration. See https:///tomcat-9.0-doc/config/context.html#Nested_Components for details. Fortify Software SecurityCenter must be restarted for the changes to have effect.• A major upgrade of libraries providing functionality for SAML Single Sign On and Single Logout solutions was delivered in this release. Fortify strongly recommends to test SAML SSO behavior after upgrade on non-production environment first. For successful SAML SSO migration, please follow the instructions below right after upgrading to22.2.0.o HTTP Redirect and HTTP POST bindings are supported, however only one at a time for inbound SAML messages. The default binding is set to HTTP POST. Incase your IdP only supports HTTP Redirect (GET) for sending Single Logoutmessages (this is the case of e.g. Microsoft Azure AD) you must switch to HTTPRedirect binding for inbound Single Logout messages. Addsso.saml.logout.binding.consume=REDIRECT property toapp.properties. Fortify Software Security Center must be restarted for thechanges to have effect.o Navigate to<hostname>:<port>/<context>/saml/metadata/<SP_alias> tore-generate Fortify Software Security Center SAML metadata and re-upload themto your IdP server. To make the transition as smooth as possible, an effort wasmade for SAML SSO to work correctly after upgrade even with SAML metadatagenerated pre-22.2.0 release. However, it is necessary to update the metadata filein IdP server at your earliest convenience.o Please also note that▪HTTP Artifact binding is not supported anymore.▪Logout responses and Logout requests sent by IdP are required to besigned, Fortify Software Security Center will refuse to process themotherwise.•If host.url property includes default port (443 for https or 8080 for http), Fortify Software Security Center will strip it as a part of URL normalization. This behavior can be changed by adding property host.url.normalization.forcePort=true to app.properties. When this property is used, host.url will be normalized to always include a port, adding a default one if none is specified.•Velocity template engine libraries affecting bugtracker filing templates were upgraded in this release from version 1.7 to version 2.3. For detailed list of changes in 2.3 since 1.7 see https:///engine/2.3/upgrading.html. Custom bugtracker filingtemplates, or custom changes to built-in bugtracker templates might be affected by the listed changes. If so, custom template content needs to be manually updated. If you wish to maximize backward compatibility instead, add propertytemplates.velocity.enhancedBackwardCompatibility=true toapp.properties. Please note that this is a best effort for maintaining backwardcompatibility and some manual changes might still be necessary.•In previous releases, a PUT request to ap/v1/issueTemplates/{id} returned 200 even in case a non-existing Issue Template ID was used. Such request will fail with 409 from now on.•Azure DevOps bug filing template was updated and now escapes HTML characters for issue deeplinks and bug attributes. In case this template was customized (specifically, the Description field was altered) in previous releases, the template update might not beapplied in full range, and manual changes might be necessary. For more details on how to apply HTML escaping, please refer to “Editing tips” available when editing bug filingtemplate’s fields in Administration page.Fortify ScanCentral SAST•Due to an issue where scans fail because of very long generated build IDs (multi-modal projects), ScanCentral SAST now uses a hash string for the build ID.KNOWN ISSUESThe following are known problems and limitations in Fortify Software 22.2.0. The problems are grouped according to the product area affected.Fortify Software Security Center•Enabling the "Enhanced Security" option for BIRT reports breaks report generation if Fortify Software Security Center is installed on a Windows system.•For successful integration with Fortify WebInspect Enterprise, Fortify Software Security Center must be deployed to /ssc context. In particular, the context must be changed for Fortify Software Security Center Kubernetes deployment, which uses root context bydefault.•The migration script downloaded from the maintenance page will be saved to file with PDF extension when using Firefox. The contents of the file are accurate, and it can beused for migration upon changing the file extension to .sql.•Fortify Software Security Center does not verify optional signature on SAML identity provider metadata even if it is present. Recommended mitigation is using file:// or https:// URL to provide identity provider's SAML metadata to Fortify Software Security Center (avoid using http:// URL).•When editing Issue Templates in UI, it is not possible to replace the template file. As a workaround, /upload/projectTemplateUpload.html API endpoint can beused to replace existing template file.•Fortify Software Security Center API Swagger spec contains two definitions that differ only in case:o Custom Tag used for assigning custom tag values to issues in an application versiono Custom tag used for managing custom tagsPlease pay attention when using tools to auto-generate API clients from Swagger spec.This might cause conflicts due to case insensitive process, and the generated client might need manual modification.Fortify Static Code Analyzer•While scanning JSP projects, you might notice a considerable increase in vulnerability counts in JSP-related categories (e.g. cross-site scripting) compared to versions of Fortify Static Code Analyzer prior to 22.1.0. To remove these spurious findings, specify the -legacy-jsp-dataflow option on the Fortify Static Code Analyzer command lineduring the analysis phase.•In some circumstances when upgrading Fortify Static Code Analyzer to a new version, the custom settings in the fortify-sca.properties configuration file might not get migrated. As a workaround, copy the custom settings from the fortify-sca.properties configuration file from the old installation location to the new one. Fortify Audit Workbench, Secure Code Plugins, and Tools•If you encounter crashes with Audit Workbench on an older version of Linux make sure you have the required version 3.22 (or later) of the GTK3 library.•Selecting File Bug for the first time on Linux produces an error, but it disappears if you click on the button the second time.•Authenticating with Azure DevOps from the Eclipse Complete plugin results in an error message on Linux.•Clearing the date-typed custom tag's value is not working from the Fortify Remediation plugin for IntelliJ.•BIRT reports do not support generating the XLS file format anymore.•If you are not connected to the internet, you will get an Updating Security Content error when you first start Fortify Security Assistant for Eclipse. After importing the rules, you will no longer get this error upon startup.Fortify ScanCentral DAST•Users who do not have permissions to create settings, and who click EDIT from the Settings List, cannot save the edited settings as a new template. As a workaround, these users can use the Settings Configuration wizard by clicking NEW SCAN or NEWSETTINGS.•The Data Retention setting is not displayed in Base Settings. If Data Retention was set in Base Settings that were configured in ScanCentral DAST 22.1.0, then those settings still apply, but are not displayed in the UI. Also, if Data Retention is enabled at theApplication level, then the setting will be applied to the Base Settings. The DataRetention setting is displayed in the scan Settings. If you create new templates or runscans using these settings, then the Data Retention setting will be applied.•Container names for the DAST Sensor and Utility Service must not exceed 50 characters in Docker run commands or Docker compose files.•ScanCentral DAST uploads the scanner service logs to the database, but there is no UI option to download the logs. To get the logs, use the following API endpoint:GET /api/v2/scans/{scanId}/download-dast-service-logsA ZIP file that may contain multiple ZIP files is downloaded. This is because each time ascan is paused, interrupted, or completed, the logs are uploaded to the database. A scanmay be resumed on a different scanner each time the scan is paused or interrupted, and the logs are saved each time.•When importing an HTTP archive (.har) file to use as a workflow macro, the file size is limited to 4 MB. To increase the file size limit to 30MB, run the following SQLcommand:IF NOT EXISTS (SELECT IdFROM ConfigurationSetting WHERE SettingName ='UtilityWorkerServiceSettings.MaxReceiveMessageSize')INSERTINTO ConfigurationSetting (SettingName, SettingValue, IsEncrypted)VALUES('UtilityWorkerServiceSettings.MaxReceiveMessageSize','31457280', 0)GO•Global Restrictions and Application Settings Domain Restrictions are applied only for Standard Scans or API scans that use a start URL.•The Fortify ScanCentral DAST download package that you obtain from the Software and License Download site includes the scancentral-dast-config-linux.tar file for Alpine Linux distribution. The documentation does not describe how to use theApline Linux version, but instead describes the preferred scancentral-dast-config-ubi.tar file for RedHat Linux distribution. To obtain the RedHat Linuxversion, contact Micro Focus Fortify Customer Support.Fortify WebInspect Enterprise•Completed scan request data presented in the WebInspect Enterprise WebConsole - Scan Requests UI may be overwritten when a new scan request is submitted for thesame application version in Fortify Software Security Center. This issue will beresolved in a hotfix to 22.2.0.•When exporting a scan in XML format to import as an artifact to Fortify Software Security Center, fewer findings may be present in the imported file than were in theoriginal scan.NOTICES OF PLANNED CHANGESThis section includes product features that will be removed from a future release of the software. In some cases, the feature will be removed in the very next release. Features that are identified as deprecated represent features that are no longer recommended for use. In most cases, deprecated features will be completely removed from the product in a future release. Fortify recommends that you remove deprecated features from your workflow at your earliest convenience.Note: For a list of technologies that will lose support in the next release, please see the “Technologies to Lose Support in the Next Release” topic in the Micro Focus Fortify Software System Requirements document.Fortify Static Code Analyzer•Support for the GOPATH will be removed in a future release to align with changes in the Go language.Fortify Software Security Center•SOAP API is deprecated and is scheduled for removal, togetherwith fortifyclient and the wsclient library. Please use REST API(/api/v1/*, /download/* and /transfer/*) endpoints instead of SOAP API (/fm-ws/*) endpoints.•SOAP API is deprecated and is scheduled for complete removal as of the Fortify Software Security Center 24.1.0 release. The phased deprecation is scheduled as follows: - In SSC version 23.1.0, SOAP remains the default- In SSC version 23.2.0, SOAP is disabled by default, but is not removed- In SSC version 24.1.0, SOAP is removed entirelyPlease use REST API (/api/v1/*, /download/* and /transfer/*)endpoints instead of SOAP API (/fm-ws/*) endpoints. A new sample command-linebased Fortify Software Security Center client (ssc-client) using REST API isincluded in the Fortify Software Security Center distribution. The ssc-client sample serves as a starting point for using a REST API-based client as a replacement for theSOAP API-based fortifyclient.Note: It is always possible that, because of schedule delays, SOAP will be removedentirely in a release later than SSC 24.1.0.•Starting with 23.1.0 release, it will not be possible to suppress Plugin Framework’s validation of engineType using system environment variableFORTIFY_PLUGINS_PARSER_VULN_ENGINETYPECHECK or JVM system property fortify.plugins.parser.vuln.engineTypeCheck. Any third-party parsers failing the validation will cease to work. EngineType of the submitted vulnerabilitiesmust be coherent with engineType provided in the plugin metadata.•REST API endpointapi/v1/projectVersions/{parentId}/dynamicScanRequests/actio n/cancel was deprecated and is scheduled for removal.Fortify WebInspect•The Web Service Test Designer tool will be removed in a future release. FEATURES NOT SUPPORTED IN THIS RELEASEThe following features are no longer supported.•Fortify Software Security Center REST API token endpoint /api/v1/auth/token has been removed. Please use the /api/v1/tokens endpoint instead.•Fortify Static Code Analyzer no longer supports Visual Studio Web Site projects. You must convert your Web Site projects to Web Application projects to ensure that FortifyStatic Code Analyzer can scan them.•Fortify WebInspect no longer supports Flash parsing•Fortify ScanCentral SAST -The allow_insecure_clients_with_empty_token property, used toconfigure the Controller, was removed from the config.properties fileNote: For a list of technologies that are no longer supported in this release, please see the “Technologies no Longer Supported in this Release” topic in the Micro Focus Fortify Software System Requirements document. This list only includes features that have lost support in this release.SUPPORTIf you have questions or comments about using this product, contact Micro Focus Fortify Customer Support using the following option.To Manage Your Support Cases, Acquire Licenses, and Manage YourAccount: https:///support.LEGAL NOTICES© Copyright 2022-2023 Micro Focus or one of its affiliates.WarrantyThe only warranties for products and services of Micro Focus and its affiliates and licensors (“Micro Focus”) are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Micro Focus shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice.Restricted Rights LegendConfidential computer software. Except as specifically indicated otherwise, a valid license from Micro Focus is required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.。
CCT问题总结
CCT问题总结CCT常见问题总结[SOLUTION]issue反馈时自行检查如下项§ 1、请确认CCT版本和平台是否匹配？2、请确认连CCT的操作是否正确3、更换usb线，确认是否是由于usb线引起的4、如果担心是新旧版本的问题，请更换其他版本的CCT看是否可以连接5、是否可以进入meta mode ？6、如果连CCT时没有进入meta mode ，请确认meta tool 和sp hw_test tool 是否可以连接，如果可进入meta mode 界面则无需确认issue反馈时需要提交的信息及抓log具体方法：1. 首先清空PC机C:\WM_META_DLL.log和BROM_DLL_V5.log2. 然后连接CCT作相关操作，复现问题,并告知操作步骤以及出现问题的时间点。
3. 连线CCT的同时请打开两个cmd line,抓取kernel log 和Android log(也可以用GA T 工具抓取)4. Issue操作过程的视频，以及问题图片。
5. 操作完毕后提供如下log:C:\WM_META_DLL.logC:\BROM_DLL_V5.logKernel logAndroid log简要介绍adb抓取log的步骤,仅供参考：1. kernel logadb shell cat /proc/kmsg> d:\kerlogkernel log在D盘下kerlog2. android log adb shell logcat -v threadtime > D:\adrlogandroid log在D盘下adrlog，且可以抓取time 和thread 信息[Camera Tuning] CCT常见问题总结1、MT6582 L CCT 调试后save nvram有出现导出参数和原始参数一样，参数不生效或者重开机后修改参数不生效请打patch ALPS01896680 (ae awb 部分) ，ALPS01928784 （ISP 部分）【SwVersion :ALPS.L0.MP2.V1】2、MT6592连CCT自动断开请打patch ALPS01448642 【Sw Version: ALPS.KK1.MP1.V2.11】3、MT6752连接camera调试工具CCT勾选quick capture时，提示adb services is out of d ataMt6752 CCT 在“CCT6752v1.1441.02” 之後加入了Quick Capture，Quick Capture 勾起來, 表示使用ADB 傳檔, 速度較快，只要是手机可以正常连adb的就支持quick capture ，【Root cause】提示adb services is out of data的根本原因是多个adb.exe冲突【调试方法】如下方法1、如果adb是可以连接的，请替换掉cct中自带的adb.exe 文件方法2、删除cct中自带的adb.exe文件方法3 、在硬盘中搜索adb.exe文件，然后找到所对应的应用程序，卸载该应用或者直接删除这个adb. exe即可方法4、将adb.ext AdbWinApi.dll AdbWinUsbApi.dll 三只文件拷贝到C:\Windows\SysWOW6 4文件夹即可4、MT6595 CCT 拍照之后就断开链接，即无法拍照【Root cause】flashlight导致CCT连接失败遇到无法拍照时，首先，确认sensor driver 是否是我司验证过的，没有验证过的sensor可能会导致连CCT无法拍照。
建筑工程施工日志模板范文
建筑工程施工日志模板范文英文回答：Construction Daily Log Template Sample.Date: [Date]Project: [Project Name]Location: [Project Location]Weather Conditions:Temperature: [Temperature]Precipitation: [Precipitation]Wind Speed: [Wind Speed]Work Performed:Task 1: [Description of Task 1]Task 2: [Description of Task 2]Task 3: [Description of Task 3]Task 4: [Description of Task 4]Task 5: [Description of Task 5]Materials Used:Material 1: [Description of Material 1] Material 2: [Description of Material 2] Material 3: [Description of Material 3] Material 4: [Description of Material 4] Material 5: [Description of Material 5]Equipment Used:Equipment 1: [Description of Equipment 1] Equipment 2: [Description of Equipment 2] Equipment 3: [Description of Equipment 3] Equipment 4: [Description of Equipment 4] Equipment 5: [Description of Equipment 5] Issues and Challenges Faced:Issue 1: [Description of Issue 1]Issue 2: [Description of Issue 2]Issue 3: [Description of Issue 3]Issue 4: [Description of Issue 4]Issue 5: [Description of Issue 5]Next Steps:Task 1: [Description of Next Task 1]Task 2: [Description of Next Task 2]Task 3: [Description of Next Task 3]Task 4: [Description of Next Task 4]Task 5: [Description of Next Task 5]Safety Measures:Safety Measure 1: [Description of Safety Measure 1] Safety Measure 2: [Description of Safety Measure 2] Safety Measure 3: [Description of Safety Measure 3]Safety Measure 4: [Description of Safety Measure 4]Safety Measure 5: [Description of Safety Measure 5]英文回答，The construction daily log template sample is as follows:Date: [日期]Project: [项目名称]Location: [项目地点]Weather Conditions:Temperature: [温度]Precipitation: [降水]Wind Speed: [风速]Work Performed:Task 1: [任务1的描述]Task 2: [任务2的描述]Task 3: [任务3的描述]Task 4: [任务4的描述]Task 5: [任务5的描述]Materials Used:Material 1: [材料1的描述] Material 2: [材料2的描述] Material 3: [材料3的描述] Material 4: [材料4的描述]Material 5: [材料5的描述] Equipment Used:Equipment 1: [设备1的描述] Equipment 2: [设备2的描述] Equipment 3: [设备3的描述] Equipment 4: [设备4的描述] Equipment 5: [设备5的描述] Issues and Challenges Faced: Issue 1: [问题1的描述]Issue 2: [问题2的描述]Issue 3: [问题3的描述]Issue 4: [问题4的描述]Issue 5: [问题5的描述]Next Steps:Task 1: [下一步任务1的描述]Task 2: [下一步任务2的描述]Task 3: [下一步任务3的描述]Task 4: [下一步任务4的描述]Task 5: [下一步任务5的描述]Safety Measures:Safety Measure 1: [安全措施1的描述] Safety Measure 2: [安全措施2的描述]Safety Measure 3: [安全措施3的描述]Safety Measure 4: [安全措施4的描述]Safety Measure 5: [安全措施5的描述] 中文回答：建筑工程施工日志模板范文如下：日期，[日期]项目，[项目名称]地点，[项目地点]天气条件：温度，[温度]降水，[降水]风速，[风速]完成的工作：任务1，[任务1的描述] 任务2，[任务2的描述] 任务3，[任务3的描述] 任务4，[任务4的描述] 任务5，[任务5的描述] 使用的材料：材料1，[材料1的描述] 材料2，[材料2的描述] 材料3，[材料3的描述] 材料4，[材料4的描述]使用的设备：设备1，[设备1的描述] 设备2，[设备2的描述] 设备3，[设备3的描述] 设备4，[设备4的描述] 设备5，[设备5的描述] 面临的问题和挑战：问题1，[问题1的描述] 问题2，[问题2的描述] 问题3，[问题3的描述]问题5，[问题5的描述]下一步计划：任务1，[下一步任务1的描述] 任务2，[下一步任务2的描述] 任务3，[下一步任务3的描述] 任务4，[下一步任务4的描述] 任务5，[下一步任务5的描述] 安全措施：安全措施1，[安全措施1的描述] 安全措施2，[安全措施2的描述]安全措施3，[安全措施3的描述] 安全措施4，[安全措施4的描述] 安全措施5，[安全措施5的描述]。
ElasticSearchHighLevelRESTAPI【5】使用模板搜索
ElasticSearchHighLevelRESTAPI【5】使⽤模板搜索ElasticSearch Rest⾼级API 提供了多种搜索⽅式，除了前⾯讲到的search查询，ElasticSearch 还提供了通过模板搜索查询。
我个⼈⽐较喜欢这种⽅式。
我们可以通过脚本预选注册模板，在注册模板时定义⼀个模板名称。
在查询时通过模板名称调⽤该模板。
⾸先演⽰下如何注册模板：public void registTemplate(){RestClient restClient = elasticClient.getRestClient();String template = "{\n" +" \"script\":{\n" +" \"lang\":\"mustache\",\n" +" \"source\":{\n" +" \"query\":{\n" +" \"match\":{\n" +" \"{{key}}\":\"{{value}}\"\n" +" }\n" +" },\n" +" \"size\":\"{{size}}\"\n" +" }\n" +" }\n" +"}";Request scriptRequest1 = new Request("POST", "_scripts/title_search");scriptRequest1.setJsonEntity(template);try {restClient.performRequest(scriptRequest1);restClient.close();} catch (IOException e) {e.printStackTrace();}}由于ElasticSearch 6.5版本的⾼级Rest API中暂时还没有提供⽤于注册模板的存储脚本，所以本⽰例中使⽤的低级REST客户端。
pending issue log模板
pending issue log模板
项目问题日志（Issue Log）
问题日志用于记录和监督问题的解决。
它可用来促进沟通，确保对问题的共同理解。
问题日志强调干系人的关注，强调沟通。
输出和更新问题日志的过程有：监控项目工作（更新）、管理项目团队（更新）、管理沟通（更新）,控制沟通（更新）、管理干系人（输出）；把问题日志作为输入的过程有：管理项目团队。
在管理项目团队过程中，总会出现各种问题。
可用问题日志记录由谁负责在目标日期内解决特定问题，并监督解决情况。
在控制沟通过程中，问题日志用于记录和监督问题的解决。
它可用来促进沟通，确保对问题的共同理解。
书面日志记录了由谁负责在目标日期前解决某特定问题，这有助于对该问题的监督。
应该解决那些妨碍团队实现目标的障碍。
问题日志中的信息对控制沟通过程十分重要，因为它记录了已经发生的问题，并为后续沟通提供了平台。
在管理干系人参与过程中，可以编制问题日志。
问题日志应随新问题的出现和老问题的解决而动态更新。
jira backlog issue排序规则
Jira Backlog Issue排序规则Jira是一款广泛使用的项目管理工具，其中一个重要的功能是管理任务的排期和优先级。
在Jira中，任务被组织在一个被称为”Backlog”的列表中，而”Backlog Issue”则是指待办事项列表中的任务。
在实际项目中，对Backlog Issue进行合理的排序是至关重要的，它决定了团队在开发过程中应该关注的任务和优先级。
本文将介绍Jira Backlog Issue排序规则的相关内容，包括任务的优先级、价值、风险、复杂度等因素的考量。
1. 任务优先级任务的优先级是指任务在整个项目中的重要性和紧急程度。
在Jira中，通常使用High、Medium和Low三个级别来表示任务的优先级。
根据任务的优先级，我们可以将任务按照以下规则进行排序：•高优先级任务：这些任务是项目中最重要和最紧急的任务，需要立即处理。
在排序时，将高优先级任务放在待办事项列表的顶部。
•中优先级任务：这些任务相对来说不如高优先级任务紧急，但仍然具有一定的重要性。
在排序时，将中优先级任务放在待办事项列表的中间部分。
•低优先级任务：这些任务相对来说不太紧急，但仍然需要关注和处理。
在排序时，将低优先级任务放在待办事项列表的底部。
2. 任务价值任务的价值是指任务对项目目标的重要贡献程度。
在Jira中，通常使用Business Value字段来表示任务的价值。
根据任务的价值，我们可以将任务按照以下规则进行排序：•高价值任务：这些任务对项目目标的贡献最大，可以带来较高的业务价值。
在排序时，将高价值任务放在待办事项列表的前面。
•中价值任务：这些任务对项目目标的贡献适中，可以带来一定的业务价值。
在排序时，将中价值任务放在待办事项列表的中间部分。
•低价值任务：这些任务对项目目标的贡献较小，对业务价值的影响也相对较小。
在排序时，将低价值任务放在待办事项列表的后面。
3. 任务风险任务的风险是指任务在实施过程中可能面临的不确定性和困难。
手工配置rsyslog配置文件详解
⼿⼯配置rsyslog配置⽂件详解⼿⼯配置如果您⽆法通过脚本⽣成配置⽂件，这份指导将帮助您通过简单的复制、粘贴⼿动完成配置。
假定您已拥有root或sudo权限，是在通⽤的Linux平台使⽤5.8.0或更⾼版本的rsyslog，rsyslog能接收本地系统⽇志，并通过5140端⼝与外界连接。
1 配置系统环境粘贴以下脚本并运⾏，并且保证 /var/spool/rsyslog ⽬录已存在，如果是Ubuntu系统，还需要对⽬录进⾏权限设置。
sudo mkdir -v /var/spool/rsyslogif [ "$(grep Ubuntu /etc/issue)" != "" ]; thensudo chown -R syslog:adm /var/spool/rsyslogfi2 更新rsyslog配置⽂件。
打开rsyslog配置⽂件，它通常在 /etc/ ⽬录下sudo vim /etc/rsyslog.d/rizhiyi.conf将下列内容粘贴在这个配置⽂件中#real tran log$ModLoad imfile #装载imfile模块$InputFilePollInterval 3 #检查⽇志⽂件间隔（秒）$WorkDirectory /var/spool/rsyslog #定义⼯作⽬录。
例如队列⽂件存储存储⽂件夹。
$InputFileName FILEPATH #读取⽇志⽂件$InputFileTag APPNAME #⽇志写⼊⽇志附加标签字符串不要添加特殊符号$InputFileStateFile stat_APPNAME #定义记录偏移量数据⽂件名不要添加特殊符号$InputFileSeverity info #⽇志等级$InputFilePersistStateInterval 20000 #回写偏移量数据到⽂件间隔时间（秒）$RepeatedMsgReduction off #关闭重复消息控制$InputRunFileMonitor #This activates the current monitor. It has no parameters. If you forget this directive, no file monitoring will take place.#https:///docs/fastuse/tag/ 设置标签(rsyslog)$template RizhiyiFormat_APPNAME,"<%pri%>%protocol-version% %timestamp:::date-rfc3339% %HOSTNAME% %app-name% %procid% %msgid% [06f69fae723038bbc5d75d29564051ea@32473 tag=\"TAG\"] %msg%\n #<85> 0 2014-09-14T16:52:59.814155+08:00macbook my_app - - [91595477-c8e4-42b8-b1f9-696465b422ff@32473 tag="file_upload"tag="my_tag"]if $programname == 'APPNAME' then @@:5140;RizhiyiFormat_APPNAMEif $programname == 'APPNAME' then ~---------------------------------------------------------------对应的单台测试机的配置如下---------------------------------------------------------------------------------------并替换FILEPATH: 需要上传的⽇志⽂件的绝对路径，必须包含⽇志⽂件名。
vue-admin-template
vue-admin-template 动态路由的实现⽰例提供登录与获取⽤户信息数据接⼝在api/user.js中import request from '@/utils/request'const Api = {TakeOut: '/student/students/takeOut/',LoginIn: '/student/students/loginIn/',StudentInfo:'/student/students/studentInfo/',}export function login(parameter) {return request({url: Api.LoginIn,method: 'get',params: parameter})}export function getInfo(token) {return request({url: Api.StudentInfo,method: 'get',params: {'token':token}})}export function logout() {return request({url: Api.TakeOut,method: 'get'})}登录接⼝数据{'code': 200, 'data': {'token': 'X-admin'}, 'message': "操作成功"}退出接⼝数据{'code': 200, 'data': 'success', 'message': "操作成功"}详情接⼝数据{"code": 200,"data": {"avatar": "https:///f778738c-e4f8-4870-b634-56703b4acafe.gif","name": "黄晓果","roles": ["editor"]}}改造router/index.jsimport Vue from 'vue'import Router from 'vue-router'e(Router)/* Layout */import Layout from '@/layout'// 基础路由export const constantRoutes = [{path: '/login',component: () => import('@/views/login/index'),hidden: true},{path: '/404',component: () => import('@/views/404'),hidden: true},{path: '/',component: Layout,redirect: '/dashboard',children: [{path: 'dashboard',name: 'Dashboard',component: () => import('@/views/dashboard/index'),meta: { title: '⾸页', icon: 'el-icon-menu' }}]},]/*** 动态路由*/export const asyncRoutes = [{path: '/studentinformation',component: Layout,children: [{path: 'index',component: () => import('@/views/studentinformation/index'),meta: { title: '学⽣信息', icon: 'el-icon-s-check' }}]},{path: '/lecturerinformation',component: Layout,children: [{path: 'index',component: () => import('@/views/lecturerinformation/index'),meta: { title: '讲师信息', icon: 'el-icon-s-custom', roles: ['editor'] }}]},{path: '/coursemanage',component: Layout,meta: { roles: ['admin'] },children: [{path: 'index',component: () => import('@/views/coursemanage/index'),meta: { title: '课程管理', icon: 'el-icon-s-platform'}}]},// 404 页⾯必须放置在最后⼀个页⾯{ path: '*', redirect: '/404', hidden: true }]const createRouter = () => new Router({// mode: 'history', // require service supportscrollBehavior: () => ({ y: 0 }),routes: constantRoutes})const router = createRouter()// Detail see: https:///vuejs/vue-router/issues/1234#issuecomment-357941465 export function resetRouter() {const newRouter = createRouter()router.matcher = newRouter.matcher // reset router}export default router将动态显⽰的路由写在asyncRoutes 中并添加 roles ，例如meta: { roles: [‘admin'] },在store/modulds⽬录下添加permission.jsimport { asyncRoutes, constantRoutes } from '@/router'/*** Use meta.role to determine if the current user has permission* @param roles* @param route*/function hasPermission(roles, route) {if (route.meta && route.meta.roles) {return roles.some(role => route.meta.roles.includes(role))} else {return true}}/*** Filter asynchronous routing tables by recursion* @param routes asyncRoutes* @param roles*/export function filterAsyncRoutes(routes, roles) {const res = []routes.forEach(route => {const tmp = { ...route }if (hasPermission(roles, tmp)) {if (tmp.children) {tmp.children = filterAsyncRoutes(tmp.children, roles)}res.push(tmp)}})return res}const state = {routes: [],addRoutes: []}const mutations = {SET_ROUTES: (state, routes) => {state.addRoutes = routesstate.routes = constantRoutes.concat(routes)}}const actions = {generateRoutes({ commit }, roles) {return new Promise(resolve => {const accessedRoutes = filterAsyncRoutes(asyncRoutes, roles)commit('SET_ROUTES', accessedRoutes)resolve(accessedRoutes)})}}export default {namespaced: true,state,mutations,actions}修改store/modulds/user.jsimport { login, logout, getInfo } from '@/api/user'import { getToken, setToken, removeToken } from '@/utils/auth'import { resetRouter } from '@/router'const getDefaultState = () => {return {token: getToken(),name: '',avatar: '',roles: []}}const state = getDefaultState()const mutations = {RESET_STATE: (state) => {Object.assign(state, getDefaultState())},SET_TOKEN: (state, token) => {state.token = token},SET_NAME: (state, name) => { = name},SET_AVATAR: (state, avatar) => {state.avatar = avatar},SET_ROLES: (state, roles) => {state.roles = roles}}const actions = {// user loginlogin({ commit }, userInfo) {const { username, password } = userInforeturn new Promise((resolve, reject) => {login({ username: username.trim(), password: password }).then(response => { const { data } = responsecommit('SET_TOKEN', data.token)setToken(data.token)resolve()}).catch(error => {reject(error)})})},// get user infogetInfo({ commit, state }) {return new Promise((resolve, reject) => {getInfo(state.token).then(response => {const { data } = responseif (!data) {return reject('验证失败，请重新登录')}const {roles, name, avatar } = datacommit('SET_ROLES', roles)commit('SET_NAME', name)commit('SET_AVATAR', avatar)resolve(data)}).catch(error => {reject(error)})})},// user logoutlogout({ commit, state }) {return new Promise((resolve, reject) => {logout(state.token).then(() => {removeToken() // must remove token firstresetRouter()commit('RESET_STATE')commit('SET_ROLES', [])resolve()}).catch(error => {reject(error)})})},// remove tokenresetToken({ commit }) {return new Promise(resolve => {removeToken() // must remove token firstcommit('RESET_STATE')commit('SET_ROLES', [])resolve()})}}export default {namespaced: true,state,mutations,actions}添加roles: [] 保存权限列表，添加内容如下const getDefaultState = () => {return {...roles: []}}const mutations = {...SET_ROLES: (state, roles) => {state.roles = roles}}// get user infogetInfo({ commit, state }) {return new Promise((resolve, reject) => {getInfo(state.token).then(response => {...const {roles, name, avatar } = datacommit('SET_ROLES', roles)...}).catch(error => {reject(error)})})},// user logoutlogout({ commit, state }) {return new Promise((resolve, reject) => {logout(state.token).then(() => {...commit('SET_ROLES', [])...}).catch(error => {reject(error)})})},// remove tokenresetToken({ commit }) {return new Promise(resolve => {...commit('SET_ROLES', [])...})}}在store/getters.js中添加rolesconst getters = {sidebar: state => state.app.sidebar,device: state => state.app.device,token: state => er.token,avatar: state => er.avatar,name: state => ,//添加rolesroles: state => er.roles,//动态路由permission_routes: state => state.permission.routes,}export default getters将permission添加到store/index.js中import Vue from 'vue'import Vuex from 'vuex'import getters from './getters'import app from './modules/app'import settings from './modules/settings'import user from './modules/user'//添加permissionimport permission from './modules/permission'e(Vuex)const store = new Vuex.Store({modules: {app,settings,user,//添加permissionpermission},getters})export default store最后修改根⽬录下的permission.jsimport router, { constantRoutes } from './router'import store from './store'import { Message } from 'element-ui'import NProgress from 'nprogress' // progress barimport 'nprogress/nprogress.css' // progress bar styleimport { getToken } from '@/utils/auth' // get token from cookieimport getPageTitle from '@/utils/get-page-title'NProgress.configure({ showSpinner: false }) // NProgress Configuration const whiteList = ['/login'] // no redirect whitelistrouter.beforeEach(async (to, from, next) => {// start progress barNProgress.start()// set page titledocument.title = getPageTitle(to.meta.title)// determine whether the user has logged inconst hasToken = getToken()if (hasToken) {if (to.path === '/login') {// if is logged in, redirect to the home pagenext({ path: '/' })NProgress.done()} else {const hasRoles = store.getters.roles && store.getters.roles.length > 0 if (hasRoles) {next()} else {try {// get user info// note: roles must be a object array! such as: ['admin'] or ,['developer','editor']const { roles } = await store.dispatch('user/getInfo')console.log(roles)// generate accessible routes map based on rolesconst accessRoutes = await store.dispatch('permission/generateRoutes', roles)// dynamically add accessible routesrouter.options.routes = constantRoutes.concat(accessRoutes)router.addRoutes(accessRoutes)// hack method to ensure that addRoutes is complete// set the replace: true, so the navigation will not leave a history recordnext({ ...to, replace: true })} catch (error) {// remove token and go to login page to re-loginawait store.dispatch('user/resetToken')Message.error(error || 'Has Error')next(`/login?redirect=${to.path}`)NProgress.done()}}}} else {/* has no token*/if (whiteList.indexOf(to.path) !== -1) {// in the free login whitelist, go directlynext()} else {// other pages that do not have permission to access are redirected to the login page.next(`/login?redirect=${to.path}`)NProgress.done()}}})router.afterEach(() => {// finish progress barNProgress.done()})将数据绑定到nav导航栏上在layout/components/sidebar/index.vue中...mapGetters([// 动态路由增加permission_routes'permission_routes','sidebar']),<!-- 动态路由 --><sidebar-item v-for="route in permission_routes" :key="route.path" :item="route" :base-path="route.path" />全部代码如下：<template><div :class="{ 'has-logo': showLogo }"><logo v-if="showLogo" :collapse="isCollapse" /><el-scrollbar wrap-class="scrollbar-wrapper"><el-menu:default-active="activeMenu":collapse="isCollapse":background-color="variables.menuBg":text-color="variables.menuText":unique-opened="false":active-text-color="variables.menuActiveText":collapse-transition="false"mode="vertical"><!-- <sidebar-itemv-for="route in routes":key="route.path":item="route":base-path="route.path"/> --><sidebar-itemv-for="route in permission_routes":key="route.path":item="route":base-path="route.path"/></el-menu></el-scrollbar></div></template><script>import { mapGetters } from 'vuex'import Logo from './Logo'import SidebarItem from './SidebarItem'import variables from '@/styles/variables.scss'export default {components: { SidebarItem, Logo },computed: {...mapGetters([// 动态路由增加permission_routes'permission_routes','sidebar',]),routes() {return this.$router.options.routes},activeMenu() {const route = this.$routeconst { meta, path } = route// if set path, the sidebar will highlight the path you setif (meta.activeMenu) {return meta.activeMenu}return path},showLogo() {return this.$store.state.settings.sidebarLogo},variables() {return variables},isCollapse() {return !this.sidebar.opened},},}</script>到此这篇关于vue-admin-template 动态路由的实现的⽂章就介绍到这了,更多相关vue-admin-template 动态路由的实现内容请搜索以前的⽂章或继续浏览下⾯的相关⽂章希望⼤家以后多多⽀持！。
ElementUI源码简析——源码结构篇
ElementUI源码简析——源码结构篇转⾃：⽬录结构解析⾸先，我们先来看看 ElementUI 的⽬录结构，总体来说，ElementUI 的⽬录结构与vue-cli2相差不⼤：.github：存放贡献指南以及 issue、PR 模板，这些是⼀个成熟的开源项⽬必须具备的。
build：毫⽆疑问，看⽂件夹名称就知道是存放打包⼯具的配置⽂件。
examples：存放 ElementUI 组件⽰例。
packages：存放组件源码，也是之后源码分析的主要⽬标。
src：存放⼊⼝⽂件以及各种辅助⽂件。
src/directives：放置⾃定义指令。
src/locale：放置语⾔的配置⽂件。
src/mixins：放置组件⽤的混合⽂件。
src/transitions：放置动画配置⽂件。
src/utils：放置⽤到⼯具函数⽂件。
src/index.js：组件注册的⼊⼝⽂件。
test：存放单元测试⽂件，合格的单元测试也是⼀个成熟的开源项⽬必备的。
types：存放声明⽂件，⽅便引⼊ typescript 写的项⽬中，需要在package.json中指定 typing 字段的值为声明的⼊⼝⽂件才能⽣效。
说完了⽂件夹⽬录，抛开那些常见的.babelrc、.eslintc等⽂件，我们来看看根⽬录下的⼏个看起来⽐较奇怪的⽂件：.travis.yml：持续集成（CI）的配置⽂件，它的作⽤就是在代码提交时，根据该⽂件执⾏对应脚本，成熟的开源项⽬必备之⼀。
CHANGELOG：更新⽇志，⼟豪的 ElementUI 准备了 4 个不同语⾔版本的更新⽇志。
components.json：配置⽂件，标注了组件的⽂件路径，⽅便 webpack 打包时获取组件的⽂件路径。
element_logo.svg：ElementUI 的图标，使⽤了 svg 格式，合理使⽤ svg ⽂件，可以⼤⼤减少图⽚⼤⼩。
FAQ.md：ElementUI 开发者对常见问题的解答。