ST第2章需求和设计评审.ppt

Click to edit Master text styles,Second level,Third level,Fourth level,Fifth level,Click to edit Master title style,WebEx Confidential,*,Click to edit Master text styles,Second level,Third level,Fourth level,Fifth level,*,Click to edit Master title style,zhu.kerry,LOGO,Kerry Zhu,Click to edit Master text styles,Second level,Third level,Fourth level,Fifth level,Click to edit Master title style,*,zhu.kerry,Click to edit Master text styles,Second level,Third level,Fourth level,Fifth level,Click to edit Master title style,*,zhu.kerry,Click to edit Master text styles,Second level,Third level,Fourth level,Fifth level,Click to edit Master title style,*,zhu.kerry,Click to edit Master text styles,Second level,Third level,Fourth level,Fifth level,Click to edit Master title style,*,zhu.kerry,Click to edit Master text styles,Second level,Third level,Fourth level,Fifth level,Click to edit Master title style,*,zhu.kerry,Click to edit Master text styles,Second level,Third level,Fourth level,Fifth level,Click to edit Master title style,*,zhu.kerry,Click to edit Master text styles,Second level,Third level,Fourth level,Fifth level,Click to edit Master title style,*,zhu.kerry,Click to edit Master text styles,Second level,Third level,Fourth level,Fifth level,Click to edit Master title style,*,zhu.kerry,Click to edit Master text styles,Second level,Third level,Fourth level,Fifth level,Click to edit Master title style,*,zhu.kerry,Click to edit Master text styles,Second level,Third level,Fourth level,Fifth level,Click to edit Master title style,*,zhu.kerry,Click to edit Master text styles,Second level,Third level,Fourth level,Fifth level,Click to edit Master title style,*,Click to edit Master text styles,Second level,Third level,Fourth level,Fifth level,*,Click to edit Master title style,zhu.kerry,Click to edit Master text styles,Second level,Third level,Fourth level,Fifth level,Click to edit Master title style,*,Click to edit Master text styles,Second level,Third level,Fourth level,Fifth level,Click to edit Master title style,*,软件测试,第,2,章 需求和设计评审,Kerry Zhu,Zhu.KerryG,review,Pass-round,Walkthrough,Peer review,Inspection,评审的技术,检查表（,checklist,）是一种常用的的质量保证手段，也是正式技术评审的必要工具，评审过程往往由检查表驱动。一份精心设计的检查表，对于提高评审效率、改进评审质量具有很大帮助。,可靠性。人们借助检查表以确认被检查对象的所有质量特征均得到满足，避免遗漏任何项目。,效率。检查表归纳了所有检查要点，比起冗长的文档，使用检查表具有更高的工作效率。,检查表、场景分析、头脑风暴和工具等,内容,如何理解需求,2.2.3 需求评审的标准,2.2.4 如何对需求进行评审,问题,为什么在测试计划中谈需求评审,？,功能性测试需求主要是根据产品规格说明书来检验被测试的系统是否满足软件各方面的功能的使用要求，包括用户界面的友好性,。,用户界面是和用户进行交互的窗口，其友好程度直接影响用户对于软件产品或软件服务的满意度。良好的用户体验，简单、方便和明了，让用户舒畅、愉悦,KISS Keep it simple,stupid,Dont make me think,Quality of service,）,QoS,要求是指定某些系统特性的技术规范。,SaaS(Software as a Service),是软件服务模式，厂商将应用软件统一部署在自己的服务器上，客户可以根据自己实际需求定购所需的应用软件服务。,On-Demand Service,On-Premise Service,7x24,不间断服务,可伸缩性，系统容量扩充能力，使系统可以支持来自扩大用户群体的额外负载。,安全性要求，确定可能潜在的安全威胁并找到处理策略。,可维护性要求，对部署系统进行维护的难易程度，可维护性与可用性之间关系密切,或关键任务？,系统架构设计的基本要求就是保证系统具有高性能、高可靠性、高安全性、高扩展性和可管理性,。系统架构设计评审就是保证这些特性在设计中得到充分考虑。,等,&A,