{"id": "docx::DzM9wooALifPufkRmjhcBHAnnpg::0", "page_id": "docx::DzM9wooALifPufkRmjhcBHAnnpg", "title": "2.5➡️3.0 软件体系结构 / Software Architecture", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture", "section": "软件体系结构题型", "url": "https://a1npn29y3xu.feishu.cn/wiki/DzM9wooALifPufkRmjhcBHAnnpg", "source_type": "docx", "n_chars": 550, "text": "选择题：30 分（10 题 × 3 分）**【比以前相对简单】- 请大家高度重视**\n\n简答题：20 分（4 题 × 5 分）\n\n**【注意课后discussion的简单题，部分从这里来，然后部分讨论问题融入难题】**\n\n综合题：50 分（10 分 + 10 分 + 15 分 + 15 分）\n\n**给出架构模型，要能够给出架构风格，设计过程，场景，问题，评估方法，解决方案，弱点【ADD过程，ATAM，Tradeoff，堂测】**\n\n①架构分析，做决策【架构设计方案和战术】\n\n②架构评估，评估决策【满足权衡点，风险点，敏感点】\n\n分 A,B 卷 B卷给出效用树，ASRs，架构设计方案和相关图，给质量属性，分析具体的质量属性场景图**（类似作业）**】\n\n选择题3\\*10=30\n\n简答题5\\*4=20\n\n综合题【50分，10，10，15，15】:给出架构模型，要能够给出**架构风格**，设计过程，场景，问题，评估方法，解决方案，弱点【ADD过程，ATAM，Tradeoff，堂测】\n\n①架构分析，做决策【架构设计方案和战术】\n\n②架构评估，评估决策【满足权衡点，风险点，敏感点】\n\n分A,B卷【B卷给出效用树，ASRs，架构设计方案和相关图，给质量属性，分析具体的质量属性场景图（类似作业）】"}
{"id": "docx::DzM9wooALifPufkRmjhcBHAnnpg::1", "page_id": "docx::DzM9wooALifPufkRmjhcBHAnnpg", "title": "2.5➡️3.0 软件体系结构 / Software Architecture", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture", "section": "来自老师的温馨提示", "url": "https://a1npn29y3xu.feishu.cn/wiki/DzM9wooALifPufkRmjhcBHAnnpg", "source_type": "docx", "n_chars": 69, "text": "1. 所有的场景都应该写得出来\n2. 每一个质量属性及其对应的策略都应该烂熟于心\n3. 压轴案例分析题一定要尽量多写！！！**字多分！**"}
{"id": "docx::DzM9wooALifPufkRmjhcBHAnnpg::2", "page_id": "docx::DzM9wooALifPufkRmjhcBHAnnpg", "title": "2.5➡️3.0 软件体系结构 / Software Architecture", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture", "section": "复习课原文", "url": "https://a1npn29y3xu.feishu.cn/wiki/DzM9wooALifPufkRmjhcBHAnnpg", "source_type": "docx", "n_chars": 700, "text": "\n\n\n\n我们整个课程分为三部分，其中重点是第二部分，题目是最多的。第一部分是软件架构导论，软件架构定义和三种类型的结构，三种结构的关系和差异，然后就是我们为什么需要软件架构，第二部分是质量属性，按照顺序讲可用性，交互性可修改性性能这些东西，后面还有一些策略，重要的一个就是定义，还有通用和特定质量属性场景，通用质量属性不考虑自身的应用，具体就考虑，需要写具体质量属性场景，还有质量属性对应的一些策略，大家学完这些课对理解架构有些帮助，类似性能网络延迟之类的一些方法，那我们需要保证高质量，比方说可用性，想到了什么方法技术（都是举例内容自己复习）性能的策略是哪些呢，一个是资源和需求的方法一个是管理层方法（举例）还有一个是可修改性还有其策略（举例）（举例内容自己去复习）下一个就是软件架构模式和分析，一些经典模式要记住（举例）质量属性建模与分析，主要是性能，理论分析性能，端到端延迟什么之类的，第三部分是架构在软件生命周期里的作用，记得几个概念ASR还有utility tree 架构最终的需求最后都会由树来构建，理解节点的含义，叶子节点主要是代表主要质量属性场景，后面就是一些宏观方法决策ADD之类的，然后架构要在测试和实现中发挥的作用还有评估，有自己评估，外部评估和专业公司评估，列上去的所有知识点都要好好复习，不考的都没放在上面题型的话主要就是选择题分析题，题目根据具体案例具"}
{"id": "docx::DzM9wooALifPufkRmjhcBHAnnpg::3", "page_id": "docx::DzM9wooALifPufkRmjhcBHAnnpg", "title": "2.5➡️3.0 软件体系结构 / Software Architecture", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture", "section": "复习课原文", "url": "https://a1npn29y3xu.feishu.cn/wiki/DzM9wooALifPufkRmjhcBHAnnpg", "source_type": "docx", "n_chars": 700, "text": "方法决策ADD之类的，然后架构要在测试和实现中发挥的作用还有评估，有自己评估，外部评估和专业公司评估，列上去的所有知识点都要好好复习，不考的都没放在上面题型的话主要就是选择题分析题，题目根据具体案例具体分析，一定要把卷子写满，希望大家好好复习\n\n第一部分：软件架构导论\n\n1. 软件架构定义\n\n • 软件架构的定义及其核心内涵。\n\n • 三种类型的结构：\n\n • 执行结构。\n\n • 信息结构。\n\n • 模块结构。\n\n • 三种结构的关系与差异。\n\n1. 为什么需要软件架构\n\n • 软件架构的重要性。\n\n • 软件架构在系统开发中的作用。\n\n第二部分：质量属性\n\n1. 质量属性概述\n\n • 重点：质量属性是考试的重点，题目数量最多。\n\n • 按顺序讲解的质量属性：\n\n • 可用性。\n\n • 交互性。\n\n • 可修改性。\n\n • 性能。\n\n • 质量属性定义：\n\n • 每个质量属性的标准定义要掌握。\n\n1. 质量属性场景\n\n • 通用质量属性场景：\n\n • 不考虑具体应用场景。\n\n • 特定质量属性场景：\n\n • 针对具体应用环境设计的场景。\n\n • 要求：\n\n • 需要掌握如何编写具体的质量属性场景。\n\n1. 质量属性策略\n\n • 每个质量属性对应的策略：\n\n • 可用性策略（举例学习，如备份、冗余等）。\n\n • 性能策略：\n\n • 资源与需求方法。\n\n • 管理层方法（需举例）。\n\n • 可修改性策略（举例学习）。"}
{"id": "docx::DzM9wooALifPufkRmjhcBHAnnpg::4", "page_id": "docx::DzM9wooALifPufkRmjhcBHAnnpg", "title": "2.5➡️3.0 软件体系结构 / Software Architecture", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture", "section": "复习课原文", "url": "https://a1npn29y3xu.feishu.cn/wiki/DzM9wooALifPufkRmjhcBHAnnpg", "source_type": "docx", "n_chars": 690, "text": "策略：\n\n • 可用性策略（举例学习，如备份、冗余等）。\n\n • 性能策略：\n\n • 资源与需求方法。\n\n • 管理层方法（需举例）。\n\n • 可修改性策略（举例学习）。\n\n • 复习重点：结合实例理解这些策略如何提升相应质量属性。\n\n第三部分：软件架构模式与分析\n\n1. 软件架构模式\n\n • 经典模式：\n\n • 重点记住一些常见的架构模式（如微服务、分层架构、事件驱动架构等）。\n\n1. 质量属性建模与分析\n\n • 以性能分析为主：\n\n • 理论分析性能。\n\n • 端到端延迟等性能指标的计算与分析方法。\n\n第四部分：架构在软件生命周期中的作用\n\n1. 核心概念\n\n • ASR（Architecturally Significant Requirements，架构关键需求）。\n\n • Utility Tree（效用树）：\n\n • 结构：根节点代表系统需求，叶子节点代表主要的质量属性场景。\n\n • 作用：帮助定义架构需求。\n\n1. 宏观方法与决策\n\n • ADD（Attribute-Driven Design）：\n\n • 重点复习架构设计的决策方法。\n\n1. 架构评估\n\n • 软件架构评估的作用与方法：\n\n • 自评。\n\n • 外部评估。\n\n • 专业公司评估。\n\n题型说明\n\n 1. 选择题：\n\n • 基于基础概念的选择。\n\n 2. 分析题：\n\n • 根据具体案例具体分析质量属性或架构模式。"}
{"id": "docx::DzM9wooALifPufkRmjhcBHAnnpg::5", "page_id": "docx::DzM9wooALifPufkRmjhcBHAnnpg", "title": "2.5➡️3.0 软件体系结构 / Software Architecture", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture", "section": "复习课原文", "url": "https://a1npn29y3xu.feishu.cn/wiki/DzM9wooALifPufkRmjhcBHAnnpg", "source_type": "docx", "n_chars": 264, "text": "专业公司评估。\n\n题型说明\n\n 1. 选择题：\n\n • 基于基础概念的选择。\n\n 2. 分析题：\n\n • 根据具体案例具体分析质量属性或架构模式。\n\n • 重点：答题时结合实例，确保内容详细完整。\n\n复习建议\n\n • 理解概念：关注定义、核心思想和例子。\n\n • 策略掌握：结合实际案例记忆具体策略。\n\n • 建模与分析：熟练分析质量属性场景，尤其是性能的理论分析。\n\n • 时间分配：注意重点部分（第二部分质量属性）。"}
{"id": "docx::DzM9wooALifPufkRmjhcBHAnnpg::6", "page_id": "docx::DzM9wooALifPufkRmjhcBHAnnpg", "title": "2.5➡️3.0 软件体系结构 / Software Architecture", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture", "section": "软件体系结构考纲", "url": "https://a1npn29y3xu.feishu.cn/wiki/DzM9wooALifPufkRmjhcBHAnnpg", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::DzM9wooALifPufkRmjhcBHAnnpg::7", "page_id": "docx::DzM9wooALifPufkRmjhcBHAnnpg", "title": "2.5➡️3.0 软件体系结构 / Software Architecture", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture", "section": "软件体系结构考纲/Part I 软件体系结构的介绍", "url": "https://a1npn29y3xu.feishu.cn/wiki/DzM9wooALifPufkRmjhcBHAnnpg", "source_type": "docx", "n_chars": 54, "text": "什么是软件体系结构？定义是什么？有哪三种结构？\n\n有哪些体系结构的模式以及策略？\n\n为什么需要软件体系结构？"}
{"id": "docx::DzM9wooALifPufkRmjhcBHAnnpg::8", "page_id": "docx::DzM9wooALifPufkRmjhcBHAnnpg", "title": "2.5➡️3.0 软件体系结构 / Software Architecture", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture", "section": "软件体系结构考纲/Part II 质量属性（最核心的内容！）", "url": "https://a1npn29y3xu.feishu.cn/wiki/DzM9wooALifPufkRmjhcBHAnnpg", "source_type": "docx", "n_chars": 217, "text": "Availability\n\nInteroperability\n\nModifiability\n\nPerformance\n\nSecurity\n\nTestability\n\nUsability\n\nOther Quality Attributes\n\n对于每一个质量属性，我们需要学习什么？\n\n定义、通用场景、具体场景、**（tactics）策略**\n\n模式和策略的架构\n\n质量属性建模和分析：availability 和 performance"}
{"id": "docx::DzM9wooALifPufkRmjhcBHAnnpg::9", "page_id": "docx::DzM9wooALifPufkRmjhcBHAnnpg", "title": "2.5➡️3.0 软件体系结构 / Software Architecture", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture", "section": "软件体系结构考纲/Part III 体系结构的生命周期", "url": "https://a1npn29y3xu.feishu.cn/wiki/DzM9wooALifPufkRmjhcBHAnnpg", "source_type": "docx", "n_chars": 81, "text": "架构以及需求：获取 ASR 的方式，Utility Tree\n\n设计一个架构：Design Strategies, ADD\n\n架构，架构实现，架构测试\n\n架构评估"}
{"id": "docx::DzM9wooALifPufkRmjhcBHAnnpg::10", "page_id": "docx::DzM9wooALifPufkRmjhcBHAnnpg", "title": "2.5➡️3.0 软件体系结构 / Software Architecture", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture", "section": "在讲义中会作为例子的项目/Java-Web/美团外卖", "url": "https://a1npn29y3xu.feishu.cn/wiki/DzM9wooALifPufkRmjhcBHAnnpg", "source_type": "docx", "n_chars": 203, "text": "[黑马程序员Java项目实战《苍穹外卖》，最适合新手的SpringBoot+SSM的企业级Java项目实战_哔哩哔哩_bilibili](https://www.bilibili.com/video/BV1TP411v7v6/?spm_id_from=333.337.search-card.all.click)\n\n源代码：https://gitee.com/tiantian17/sky_take_out"}
{"id": "docx::DzM9wooALifPufkRmjhcBHAnnpg::11", "page_id": "docx::DzM9wooALifPufkRmjhcBHAnnpg", "title": "2.5➡️3.0 软件体系结构 / Software Architecture", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture", "section": "在讲义中会作为例子的项目/Java-Web/今日头条", "url": "https://a1npn29y3xu.feishu.cn/wiki/DzM9wooALifPufkRmjhcBHAnnpg", "source_type": "docx", "n_chars": 256, "text": "[黑马程序员Java项目实战微服务项目《黑马头条》开发全套视频教程，基于SpringBoot+SpringCloud+Nacos等企业级微服务架构项目解决方案_哔哩哔哩_bilibili](https://www.bilibili.com/video/BV1Qs4y1v7x4/?spm_id_from=333.337.search-card.all.click)\n\n源代码：https://gitee.com/chicken-with-soft-vegetables/heima-leadnews-master"}
{"id": "docx::DzM9wooALifPufkRmjhcBHAnnpg::12", "page_id": "docx::DzM9wooALifPufkRmjhcBHAnnpg", "title": "2.5➡️3.0 软件体系结构 / Software Architecture", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture", "section": "在讲义中会作为例子的项目/Python-AI/图像识别", "url": "https://a1npn29y3xu.feishu.cn/wiki/DzM9wooALifPufkRmjhcBHAnnpg", "source_type": "docx", "n_chars": 172, "text": "[使用pytorch配合flask搭建简易web服务_哔哩哔哩_bilibili](https://www.bilibili.com/video/BV1Qv41117SR/?spm_id_from=333.337.search-card.all.click&vd_source=da1f2d78d73dfaae6ddfbcfe8e4801d8)"}
{"id": "docx::DzM9wooALifPufkRmjhcBHAnnpg::13", "page_id": "docx::DzM9wooALifPufkRmjhcBHAnnpg", "title": "2.5➡️3.0 软件体系结构 / Software Architecture", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture", "section": "在讲义中会作为例子的项目/Python-AI/大语言模型", "url": "https://a1npn29y3xu.feishu.cn/wiki/DzM9wooALifPufkRmjhcBHAnnpg", "source_type": "docx", "n_chars": 222, "text": "[(超爽中英!) 2024公认最好的【吴恩达LangChain+RAG】教程！更适合中国宝宝体质，全程干货无废话，学完成为AGI大佬！（附课件+代码）\\_哔哩哔哩_bilibili](https://www.bilibili.com/video/BV1TJ4zemETf/?spm_id_from=333.337.search-card.all.click&vd_source=da1f2d78d73dfaae6ddfbcfe8e4801d8)"}
{"id": "docx::DzM9wooALifPufkRmjhcBHAnnpg::14", "page_id": "docx::DzM9wooALifPufkRmjhcBHAnnpg", "title": "2.5➡️3.0 软件体系结构 / Software Architecture", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture", "section": "优秀网课教程", "url": "https://a1npn29y3xu.feishu.cn/wiki/DzM9wooALifPufkRmjhcBHAnnpg", "source_type": "docx", "n_chars": 82, "text": "[软件体系结构 - 老曹同学的马甲线](https://space.bilibili.com/347527982/lists/408707?type=series)"}
{"id": "docx::DzM9wooALifPufkRmjhcBHAnnpg::15", "page_id": "docx::DzM9wooALifPufkRmjhcBHAnnpg", "title": "2.5➡️3.0 软件体系结构 / Software Architecture", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture", "section": "正文部分", "url": "https://a1npn29y3xu.feishu.cn/wiki/DzM9wooALifPufkRmjhcBHAnnpg", "source_type": "docx", "n_chars": 700, "text": ""}
{"id": "docx::DzM9wooALifPufkRmjhcBHAnnpg::17", "page_id": "docx::DzM9wooALifPufkRmjhcBHAnnpg", "title": "2.5➡️3.0 软件体系结构 / Software Architecture", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture", "section": "参考文献及网页地址", "url": "https://a1npn29y3xu.feishu.cn/wiki/DzM9wooALifPufkRmjhcBHAnnpg", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::IYURw9fvEifzc4kc6qfcuAyxnce::18", "page_id": "docx::IYURw9fvEifzc4kc6qfcuAyxnce", "title": "2.5➡️4.0 软件测试 / Software Testing", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing", "section": "2.5➡️4.0 软件测试 / Software Testing", "url": "https://a1npn29y3xu.feishu.cn/wiki/IYURw9fvEifzc4kc6qfcuAyxnce", "source_type": "docx", "n_chars": 700, "text": "\n\n"}
{"id": "docx::QO8OwCvenixITTkLiS6cQWFjnWb::20", "page_id": "docx::QO8OwCvenixITTkLiS6cQWFjnWb", "title": "2024 完结撒花 试卷快速回忆版", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/2024 完结撒花 试卷快速回忆版", "section": "2024 完结撒花 试卷快速回忆版", "url": "https://a1npn29y3xu.feishu.cn/wiki/QO8OwCvenixITTkLiS6cQWFjnWb", "source_type": "docx", "n_chars": 448, "text": "\n\n单选题 2 分 ✖️ 6 题\n\nSCT 是哪三个\n\nAOA 用来估计完成时间的方法\n\n什么不属于 resource management\n\n多选题 4 分 ✖️ 2 题\n\n塔克曼过程\n\n成本管理\n\n判断题 3 + 3 + 4\n\n成本管理的目的在于减少成本\n\n六西格玛采用了减少方差的做法\n\n软件测试只需要在验收前测试\n\n名词解释 5 分 ✖️ 4 题\n\n系统方法\n干系人\n挣值管理\nPMI 人才三角\n瀑布模型\n\n论述题 10 分 ✖️ 2 题\n什么是范围？什么是范围管理？IT 项目经理认为范围管理具有挑战性的原因。\n\n请你列举出项目日程管理的process 和output. 并且分析项目日程管理中的 main conflict\n\n计算题还是那两样（AOA + EV）15 分 ✖️ 2 题"}
{"id": "docx::NdNLw0tUOihRp7kwkThcYoDanLe::21", "page_id": "docx::NdNLw0tUOihRp7kwkThcYoDanLe", "title": "2024 完结撒花：试卷快速回忆版", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/2024 完结撒花：试卷快速回忆版", "section": "2024 完结撒花：试卷快速回忆版", "url": "https://a1npn29y3xu.feishu.cn/wiki/NdNLw0tUOihRp7kwkThcYoDanLe", "source_type": "docx", "n_chars": 404, "text": "选择题考得很简单，除了第三题，丢了就丢了吧\n\n简答题（5题 4分）\n\n1. 通用模块虽然有助于降低耦合，但是也有可能导致降低内聚，请你针对这个论点进行讨论\n2. 软件架构在降低风险的作用\n3. 7 categories of architecutre design，回答出 4 个即可（提示 ABCCDMM）\n4. 请简要论述编程语言的选择和架构设计的关系\n5. Exhausted security tactics？\n\n综合题（10 + 15 + 10 + 15）（问的全是tactics）\n\n1. P2P 与其他模式的实际应用（Gnutella）\n2. 英文版第三版教材 P409 的图片，论述并填补完整，言之有理即可给分\n3. Pipe-and-Filter\n4. Map-Reduce（先分析 Availability，再分析 Performance，最后针对这两个点的 trade-off 做论述）"}
{"id": "docx::AMWXwkRcCioTn9kdm9WcYYtVnbh::22", "page_id": "docx::AMWXwkRcCioTn9kdm9WcYYtVnbh", "title": "2025 [Medium]", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/2025 [Medium]", "section": "大题", "url": "https://a1npn29y3xu.feishu.cn/wiki/AMWXwkRcCioTn9kdm9WcYYtVnbh", "source_type": "docx", "n_chars": 118, "text": "第一个是写sql语句，卷子上还给了hint\n\n第二题是画er图，就三个实体三个关系\n\n第三题是正则覆盖3nf那些\n\n第四题是算transfer和seek（b+树index和index join）\n\n第五题是冲突串行和死锁（PPT 原题）"}
{"id": "docx::ZQ0xwIi34iCX7YkVdsHcbQARnMd::23", "page_id": "docx::ZQ0xwIi34iCX7YkVdsHcbQARnMd", "title": "2025 项目管理考生回忆版", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/2025 项目管理考生回忆版", "section": "2025 项目管理考生回忆版", "url": "https://a1npn29y3xu.feishu.cn/wiki/ZQ0xwIi34iCX7YkVdsHcbQARnMd", "source_type": "docx", "n_chars": 657, "text": "选择题(20分)\n\n单选(2分/题)\n\n所有的单选题都是第九版课本课后原题，而且和24年单选题全部一模一样\n\n1.不属于PM优点(?)的是\n\nA.减少开发次数 B.鼓舞士气(morale) C.降低资本成本(cost of capital) D.提高利率(profit margin)\n\n2.leading agile development method? -scrum(敏捷和scrum锁死，选就完了)\n\n3.下面哪一个不是三球模型？(缩写BOT)\n\n4.组成敏捷需求的是：backlog\n\n5.哪种表示计划和实际：跟踪甘特图(剩下的选项：甘特图，网络图，里程碑图)\n\n6.哪种储备金是用于无法预测的\n\n\n\n多选(4分/题)\n\n7.哪些是创建一个塔克曼团队的过程\n\n形成(forming)，震荡(storming)，规则化(norming)，执行(performing)，收尾(adjourning)，除掉ing，词尾基本都是押韵的）\n\n(考了前四个，剩下一个选项最后不押韵所以排除)\n\n8.下面哪些是项目时间(英文：schedule，也就是time)管理的步骤\n\nA.plan schedule management\n\nB.define activities\n\nC.sequence activities\n\nD.estimate activity costs(错误)\n\n判断题(10分=3+3+4)"}
{"id": "docx::ZQ0xwIi34iCX7YkVdsHcbQARnMd::24", "page_id": "docx::ZQ0xwIi34iCX7YkVdsHcbQARnMd", "title": "2025 项目管理考生回忆版", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/2025 项目管理考生回忆版", "section": "2025 项目管理考生回忆版", "url": "https://a1npn29y3xu.feishu.cn/wiki/ZQ0xwIi34iCX7YkVdsHcbQARnMd", "source_type": "docx", "n_chars": 697, "text": "agement\n\nB.define activities\n\nC.sequence activities\n\nD.estimate activity costs(错误)\n\n判断题(10分=3+3+4)\n\n1.成本管理的目标是节省成本(F，应该是保证在approved budget内完成项目，省不省无所谓只要别超预算)\n\n2.测试只在IT产品开发末期的时候做\n\n3.外部因素是人根据自己的兴趣去做(F，是内部因素)\n\n名词解释(20分，4分/题)\n\n1.project charter(正式批准项目的存在，为目标和管理提供方向)\n2.cost of quality\n3.critical path method\n4.reserves\n5.CMMI\n\n简答题(20分，10分/题)\n\n1. 4-frame organization的概念和每一个的定义\n2. 马斯洛需求层次的定义和每一层的内容\n\n计算题(30分)\n\n1.时间管理(15分)\n\n(1)画pdm(12分，这一题巨恶心，任务依赖描述同一种描述用不同的英文顺序来说，比如说先用陈述句说一遍然后下一题他又用双重否定句说一遍)\n\n(2)找出图中的所有路径(2分)\n\n(3)找出关键路径(1分)\n\n节点的格式\n\n\n\nA是初始 工期5天\n\nB必须在A结束后开始 工期8天\n\nC在A结束前2天可以开始\n\nD在C开始5天后可以开始 工期\n\nE在B结束后3天可以开始 工期15天\n\n原文好像是这么说的（太绕了）：F不能在D、E完成后不早于2天完成"}
{"id": "docx::ZQ0xwIi34iCX7YkVdsHcbQARnMd::25", "page_id": "docx::ZQ0xwIi34iCX7YkVdsHcbQARnMd", "title": "2025 项目管理考生回忆版", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/2025 项目管理考生回忆版", "section": "2025 项目管理考生回忆版", "url": "https://a1npn29y3xu.feishu.cn/wiki/ZQ0xwIi34iCX7YkVdsHcbQARnMd", "source_type": "docx", "n_chars": 354, "text": "须在A结束后开始 工期8天\n\nC在A结束前2天可以开始\n\nD在C开始5天后可以开始 工期\n\nE在B结束后3天可以开始 工期15天\n\n原文好像是这么说的（太绕了）：F不能在D、E完成后不早于2天完成\n\nF在D、E都完成的2天后才可以完成 工期6天\n\n我是这样画的，不知道对不对\n\nC、D不记得了\n\n\n\n2.成本管理(15分)\n\n挣值计算\n\nBAC：1 800 000\n\n按照计划应该完成60%，实际完成55%\n\n实际花费850 000\n\n(1)求EV,CV,SV,CPI,SPI(10分)\n\n(2)CPI保持不变，求EAC(5分)\n\n\"保留到小数点后两位\"教材ch7课后题有对应的英文表达，可以留个意"}
{"id": "docx::QeOvwU3cVi2cW9kLRiscKFW4nL0::26", "page_id": "docx::QeOvwU3cVi2cW9kLRiscKFW4nL0", "title": "2026 [Hard]", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/2026 [Hard]", "section": "2026 [Hard]", "url": "https://a1npn29y3xu.feishu.cn/wiki/QeOvwU3cVi2cW9kLRiscKFW4nL0", "source_type": "docx", "n_chars": 96, "text": "2026 [Hard]\n\n\n\nGood Bye 2025, Hello 2026."}
{"id": "docx::QeOvwU3cVi2cW9kLRiscKFW4nL0::27", "page_id": "docx::QeOvwU3cVi2cW9kLRiscKFW4nL0", "title": "2026 [Hard]", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/2026 [Hard]", "section": "III Relation + SQL 7 题 共 29 分", "url": "https://a1npn29y3xu.feishu.cn/wiki/QeOvwU3cVi2cW9kLRiscKFW4nL0", "source_type": "docx", "n_chars": 441, "text": "SQL书写：一个交易平台数据库模式\nuser ( pid, name, role )\ninteraction ( iid, type )（type有transfer, endorse）\nrecords ( pid1, iid, pid2, timestamp )\n\n1. 所有角色为Miner的用户\n2. 用 ( pid1, iid, pid2 )格式展示type=transfer的interaction\n3. 用 ( UserName, InteractionCount ) 格式展示发起了>20次Interaction的用户\n4. 用关系代数表达式重写3\n5. 用 ( pid, name ) 展示 Transfer 和 Endorse 两种interaction都发起过的用户\n6. 用 ( NameA, NameC ) 展示所有构成关系：从用户A transfer 给用户B，再从用户B transfer 给 C\n7. 发起interaction数量比平均值高的用户pid"}
{"id": "docx::QeOvwU3cVi2cW9kLRiscKFW4nL0::28", "page_id": "docx::QeOvwU3cVi2cW9kLRiscKFW4nL0", "title": "2026 [Hard]", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/2026 [Hard]", "section": "VI 事务管理 4 题 共 10 分", "url": "https://a1npn29y3xu.feishu.cn/wiki/QeOvwU3cVi2cW9kLRiscKFW4nL0", "source_type": "docx", "n_chars": 74, "text": "1. 1.1 画优先图\n\n 1.2判断是否冲突可串行化\n\n1. 2.1 题目给出事务表，要求画wait图\n\n 2.2判断是否死锁"}
{"id": "docx::SlDAwodyPi7IZ0kIolMcp6qHnMh::29", "page_id": "docx::SlDAwodyPi7IZ0kIolMcp6qHnMh", "title": "3.5➡️3.0 数据库系统 / DataBase System", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System", "section": "课本官方网站", "url": "https://a1npn29y3xu.feishu.cn/wiki/SlDAwodyPi7IZ0kIolMcp6qHnMh", "source_type": "docx", "n_chars": 186, "text": "https://www.db-book.com/\n\n\n\nhttps://www.db-book.com/Previous-editions/db6/\n\n"}
{"id": "docx::SlDAwodyPi7IZ0kIolMcp6qHnMh::30", "page_id": "docx::SlDAwodyPi7IZ0kIolMcp6qHnMh", "title": "3.5➡️3.0 数据库系统 / DataBase System", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System", "section": "数据库系统题型", "url": "https://a1npn29y3xu.feishu.cn/wiki/SlDAwodyPi7IZ0kIolMcp6qHnMh", "source_type": "docx", "n_chars": 230, "text": "选择题 + 判断题：20 分（往年**都是填空题**，今年可能会混着出）\n\n选择题 5 题，每题 2 分\n\n判断题 5 题，每题 2 分\n\n综合题：80 分\n\n**讲义（一）（二）**\n\nSQL & 关系代数 25 \\~ 30 分不等\n\n**讲义（三）**\n\nER 模型 15 分左右\n\n数据库设计 & 关系规范化 25 \\~ 30 分不等\n\n**讲义（四）**\n\n查询处理和优化 15 \\~ 20 分不等\n\n**讲义（五）**\n\n事务 5 \\~ 10 分不等"}
{"id": "docx::SlDAwodyPi7IZ0kIolMcp6qHnMh::31", "page_id": "docx::SlDAwodyPi7IZ0kIolMcp6qHnMh", "title": "3.5➡️3.0 数据库系统 / DataBase System", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System", "section": "数据库系统考纲/关系代数", "url": "https://a1npn29y3xu.feishu.cn/wiki/SlDAwodyPi7IZ0kIolMcp6qHnMh", "source_type": "docx", "n_chars": 45, "text": "第一章 **抽象的三个层次（很喜欢考选填题）** 带出后面的每一个章节\n\n第二章 关系代数"}
{"id": "docx::SlDAwodyPi7IZ0kIolMcp6qHnMh::32", "page_id": "docx::SlDAwodyPi7IZ0kIolMcp6qHnMh", "title": "3.5➡️3.0 数据库系统 / DataBase System", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System", "section": "数据库系统考纲/SQL 专题", "url": "https://a1npn29y3xu.feishu.cn/wiki/SlDAwodyPi7IZ0kIolMcp6qHnMh", "source_type": "docx", "n_chars": 211, "text": "给你一题，我有一个 database，有一个 schema，给你 query，让你写出对应的关系代数表达式和 SQL 表达式\n\n其实只会考到最简单的层次，不会用 SQL 写一个过程实现某个功能，也不会揪着 EXIST UNIQUE 等字眼深究\n\n一开始简单涉及到一张表 —— 更多的谓词、更多的表（ 实验\n\n外连接等过难的关键字如果查询结果符合题目要求那么也会给分\n\n你要懂什么是触发器，但不会让你写触发器的 SQL 语句"}
{"id": "docx::SlDAwodyPi7IZ0kIolMcp6qHnMh::33", "page_id": "docx::SlDAwodyPi7IZ0kIolMcp6qHnMh", "title": "3.5➡️3.0 数据库系统 / DataBase System", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System", "section": "数据库系统考纲/数据库设计", "url": "https://a1npn29y3xu.feishu.cn/wiki/SlDAwodyPi7IZ0kIolMcp6qHnMh", "source_type": "docx", "n_chars": 148, "text": "给一段文字描述给你，让你做出 ER 图，最基本的 ER 设计（泛化、概括、聚集不经常出大题）\n\n在 ER 设计以后，如果设计的实体特别多，则可以转化为 schema 的形式（ table 的形式 ）\n\n第八章：难点，就像课后作业的习题一样，R，R 上 有属性，有 F，推一些结论，也不会特别的麻烦"}
{"id": "docx::SlDAwodyPi7IZ0kIolMcp6qHnMh::34", "page_id": "docx::SlDAwodyPi7IZ0kIolMcp6qHnMh", "title": "3.5➡️3.0 数据库系统 / DataBase System", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System", "section": "数据库系统考纲/检索专题", "url": "https://a1npn29y3xu.feishu.cn/wiki/SlDAwodyPi7IZ0kIolMcp6qHnMh", "source_type": "docx", "n_chars": 246, "text": "范式有时候跟着第八章的大题理论推导走的，陈老师承诺只考到第三范式\n\n索引、查询处理、查询优化：不会考得特别的细、特别的难，不会像数据结构考试一样让你手搓 B 树数据插入的全流程\n\n但是今年会考 B+ 树的 property 和实际应用的问题（我有一个表，有多少个元组、占了多少个块、有无索引，如果用 B+ 树需要几个 IO？如果用 Hash 需要几个 IO？）\n\n查询优化，完成一个查询有很多实现形式，各种代价是不一样的，代价是怎么估算的，plan 和 plan 之间的区别，倾向于选哪一个？"}
{"id": "docx::SlDAwodyPi7IZ0kIolMcp6qHnMh::35", "page_id": "docx::SlDAwodyPi7IZ0kIolMcp6qHnMh", "title": "3.5➡️3.0 数据库系统 / DataBase System", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System", "section": "数据库系统考纲/事务恢复", "url": "https://a1npn29y3xu.feishu.cn/wiki/SlDAwodyPi7IZ0kIolMcp6qHnMh", "source_type": "docx", "n_chars": 51, "text": "事务、并发、恢复三合一：事务的基本概念，并发的基本概念，恢复的基本概念，上锁和日志恢复的机制，ACID"}
{"id": "docx::SlDAwodyPi7IZ0kIolMcp6qHnMh::36", "page_id": "docx::SlDAwodyPi7IZ0kIolMcp6qHnMh", "title": "3.5➡️3.0 数据库系统 / DataBase System", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System", "section": "优秀教程/期末", "url": "https://a1npn29y3xu.feishu.cn/wiki/SlDAwodyPi7IZ0kIolMcp6qHnMh", "source_type": "docx", "n_chars": 329, "text": "[【数据库系统概论】三小时复习期末速成不挂科_哔哩哔哩_bilibili](https://www.bilibili.com/video/BV1Bq4y1Y7GC/?spm_id_from=333.337.search-card.all.click&vd_source=da1f2d78d73dfaae6ddfbcfe8e4801d8)\n\n[数据库系统概论，搞定考试_哔哩哔哩_bilibili](https://www.bilibili.com/video/BV1G54y1d7ZK/?spm_id_from=333.337.search-card.all.click&vd_source=da1f2d78d73dfaae6ddfbcfe8e4801d8)"}
{"id": "docx::SlDAwodyPi7IZ0kIolMcp6qHnMh::37", "page_id": "docx::SlDAwodyPi7IZ0kIolMcp6qHnMh", "title": "3.5➡️3.0 数据库系统 / DataBase System", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System", "section": "优秀教程/工具：MySQL PostgreSQL", "url": "https://a1npn29y3xu.feishu.cn/wiki/SlDAwodyPi7IZ0kIolMcp6qHnMh", "source_type": "docx", "n_chars": 419, "text": "https://www.mysql.com/cn/\n\nhttps://www.postgresql.org/\n\n[MySQL实战45讲](https://learn.lianglianglee.com/%E6%9E%81%E5%AE%A2%E6%97%B6%E9%97%B4/MySQL%E5%AE%9E%E6%88%9845%E8%AE%B2.md)\n\n[图解MySQL介绍](https://xiaolincoding.com/mysql/)\n\n[黑马程序员 MySQL数据库入门到精通，从mysql安装到mysql高级、mysql优化全囊括_哔哩哔哩_bilibili](https://www.bilibili.com/video/BV1Kr4y1i7ru/?spm_id_from=333.337.search-card.all.click&vd_source=da1f2d78d73dfaae6ddfbcfe8e4801d8)"}
{"id": "docx::SlDAwodyPi7IZ0kIolMcp6qHnMh::38", "page_id": "docx::SlDAwodyPi7IZ0kIolMcp6qHnMh", "title": "3.5➡️3.0 数据库系统 / DataBase System", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System", "section": "优秀教程/工具：Redis", "url": "https://a1npn29y3xu.feishu.cn/wiki/SlDAwodyPi7IZ0kIolMcp6qHnMh", "source_type": "docx", "n_chars": 309, "text": "[Redis - The Real-time Data Platform](https://redis.io/)\n\n[图解Redis介绍](https://xiaolincoding.com/redis/)\n\n[黑马程序员Redis入门到实战教程，深度透析redis底层原理+redis分布式锁+企业解决方案+黑马点评实战项目_哔哩哔哩_bilibili](https://www.bilibili.com/video/BV1cr4y1671t/?spm_id_from=333.337.search-card.all.click&vd_source=da1f2d78d73dfaae6ddfbcfe8e4801d8)"}
{"id": "docx::SlDAwodyPi7IZ0kIolMcp6qHnMh::39", "page_id": "docx::SlDAwodyPi7IZ0kIolMcp6qHnMh", "title": "3.5➡️3.0 数据库系统 / DataBase System", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System", "section": "正文部分", "url": "https://a1npn29y3xu.feishu.cn/wiki/SlDAwodyPi7IZ0kIolMcp6qHnMh", "source_type": "docx", "n_chars": 699, "text": ""}
{"id": "docx::O3w7wV80sisL0vkaaFEcQNVnnQh::41", "page_id": "docx::O3w7wV80sisL0vkaaFEcQNVnnQh", "title": "3.5➡️3.0 软件项目管理 / IT Project Management", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management", "section": "软件项目管理题型/**选填题（30 分）**", "url": "https://a1npn29y3xu.feishu.cn/wiki/O3w7wV80sisL0vkaaFEcQNVnnQh", "source_type": "docx", "n_chars": 50, "text": "选择题：**单选题，多选题**\n判断题：判断正确或者错误\n这两块一共占了 30 分，往年是没有小题的"}
{"id": "docx::O3w7wV80sisL0vkaaFEcQNVnnQh::42", "page_id": "docx::O3w7wV80sisL0vkaaFEcQNVnnQh", "title": "3.5➡️3.0 软件项目管理 / IT Project Management", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management", "section": "软件项目管理题型/概念默写（20 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/O3w7wV80sisL0vkaaFEcQNVnnQh", "source_type": "docx", "n_chars": 49, "text": "请注意课后的批注以及 PPT 上加粗的内容\n\n有一些章节和图片的核心概念，特别重点的内容大家要关注"}
{"id": "docx::O3w7wV80sisL0vkaaFEcQNVnnQh::43", "page_id": "docx::O3w7wV80sisL0vkaaFEcQNVnnQh", "title": "3.5➡️3.0 软件项目管理 / IT Project Management", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management", "section": "软件项目管理题型/简答题（20 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/O3w7wV80sisL0vkaaFEcQNVnnQh", "source_type": "docx", "n_chars": 148, "text": "请阅读材料，分析材料的某一个计划是干什么用的，某一个管理方法可以用来解决什么问题，在处理**人力和成本**问题中的挑战是什么啊，用什么技术来处理啊\n\n##\n计算题（30 分）\n\n计算题考点相对固定\n**时间管理，成本管理占了计算题绝大部份的内容**\n课堂上反复跟大家强调了，一定要熟练处理净值处理"}
{"id": "docx::O3w7wV80sisL0vkaaFEcQNVnnQh::44", "page_id": "docx::O3w7wV80sisL0vkaaFEcQNVnnQh", "title": "3.5➡️3.0 软件项目管理 / IT Project Management", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management", "section": "软件项目管理考纲：PPT 采用第七版", "url": "https://a1npn29y3xu.feishu.cn/wiki/O3w7wV80sisL0vkaaFEcQNVnnQh", "source_type": "docx", "n_chars": 227, "text": "重点要放在前面的七章\n**尤其是范围管理、时间管理、成本管理**\n这三大要素里面的主干知识点，占比很高\n前面的一些综合管理考小题可能性大\n**概念题和其他的分析题只要言之有理，基本都会酌情给分**\n\n第一章 \\~ 第四章：小题出得多\n\n第五章 \\~ 第七章：大题出得多\n\n剩下的章节：零散地分布在各个部分\n\n吴老师建议的复习顺序：**先复习五六七，再从后往前复习！**\n\n不要把时间第一章第二章太久，没必要！\n\n好的，以下是整理好的复习提纲，按顺序排列："}
{"id": "docx::O3w7wV80sisL0vkaaFEcQNVnnQh::45", "page_id": "docx::O3w7wV80sisL0vkaaFEcQNVnnQh", "title": "3.5➡️3.0 软件项目管理 / IT Project Management", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management", "section": "软件项目管理考纲：PPT 采用第七版/考试重点一：WBS", "url": "https://a1npn29y3xu.feishu.cn/wiki/O3w7wV80sisL0vkaaFEcQNVnnQh", "source_type": "docx", "n_chars": 254, "text": "- PPT 21\n- PPT 24\n- PPT 32\n\n\n\n\n\n\n\n"}
{"id": "docx::O3w7wV80sisL0vkaaFEcQNVnnQh::46", "page_id": "docx::O3w7wV80sisL0vkaaFEcQNVnnQh", "title": "3.5➡️3.0 软件项目管理 / IT Project Management", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management", "section": "软件项目管理考纲：PPT 采用第七版/考试重点一：WBS/考试重点二：时间管理", "url": "https://a1npn29y3xu.feishu.cn/wiki/O3w7wV80sisL0vkaaFEcQNVnnQh", "source_type": "docx", "n_chars": 657, "text": "- PPT 32\n- 有哪两类网络图（双代号网络图或者箭线图）\n- 什么叫前导图 PDM 法，有什么作用\n- 关键路径法\n- PPT 43\n- PPT 46\n- PPT 56\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::O3w7wV80sisL0vkaaFEcQNVnnQh::47", "page_id": "docx::O3w7wV80sisL0vkaaFEcQNVnnQh", "title": "3.5➡️3.0 软件项目管理 / IT Project Management", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management", "section": "软件项目管理考纲：PPT 采用第七版/考试重点一：WBS/考试重点三：成本管理", "url": "https://a1npn29y3xu.feishu.cn/wiki/O3w7wV80sisL0vkaaFEcQNVnnQh", "source_type": "docx", "n_chars": 393, "text": "- Figure 7.1\n- Figure 7.2\n- 净值管理：中文版教材（第七版） 209～213\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::O3w7wV80sisL0vkaaFEcQNVnnQh::48", "page_id": "docx::O3w7wV80sisL0vkaaFEcQNVnnQh", "title": "3.5➡️3.0 软件项目管理 / IT Project Management", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management", "section": "软件项目管理考纲：PPT 采用第七版/考试重点一：WBS/考试重点四：质量管理", "url": "https://a1npn29y3xu.feishu.cn/wiki/O3w7wV80sisL0vkaaFEcQNVnnQh", "source_type": "docx", "n_chars": 72, "text": "- 什么是质量管理？（224）\n\n"}
{"id": "docx::O3w7wV80sisL0vkaaFEcQNVnnQh::49", "page_id": "docx::O3w7wV80sisL0vkaaFEcQNVnnQh", "title": "3.5➡️3.0 软件项目管理 / IT Project Management", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management", "section": "软件项目管理考纲：PPT 采用第七版/考试重点一：WBS/考试重点五：人力资源管理", "url": "https://a1npn29y3xu.feishu.cn/wiki/O3w7wV80sisL0vkaaFEcQNVnnQh", "source_type": "docx", "n_chars": 277, "text": "- 什么是人力资源管理？（259）\n\n\n\n- 需求层次理论（261）\n\n\n\n- 什么是风险管理？（321）\n\n\n\n"}
{"id": "docx::O3w7wV80sisL0vkaaFEcQNVnnQh::50", "page_id": "docx::O3w7wV80sisL0vkaaFEcQNVnnQh", "title": "3.5➡️3.0 软件项目管理 / IT Project Management", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management", "section": "软件项目管理考纲：PPT 采用第七版/考试重点一：WBS/项目综合管理", "url": "https://a1npn29y3xu.feishu.cn/wiki/O3w7wV80sisL0vkaaFEcQNVnnQh", "source_type": "docx", "n_chars": 691, "text": "- 净现值分析必考\n\n\n\n\n\n\n\n- 项目管理过程组：案例研究（60～65）\n\n\n\n- 什么是项目管理的系统观点？\n\n\n\n- 怎么用系统方法去做分析和管理？\n\n\n\n- 项目的生命周期？（瀑布模型、敏捷模型、螺旋模型）\n\n\n\n- 什么是干系人管理？\n\n\n\n\n\n- Scrum 框架\n\n"}
{"id": "docx::O3w7wV80sisL0vkaaFEcQNVnnQh::51", "page_id": "docx::O3w7wV80sisL0vkaaFEcQNVnnQh", "title": "3.5➡️3.0 软件项目管理 / IT Project Management", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management", "section": "软件项目管理考纲：PPT 采用第七版/考试重点一：WBS/项目综合管理", "url": "https://a1npn29y3xu.feishu.cn/wiki/O3w7wV80sisL0vkaaFEcQNVnnQh", "source_type": "docx", "n_chars": 403, "text": "/WZ04bJcuXotZwzxqmEMcVG1qnCc)\n\n- Scrum 框架\n\n\n\n\n\n- 什么是项目管理、项目、集成管理？\n\n\n\n\n\n\n\n"}
{"id": "docx::O3w7wV80sisL0vkaaFEcQNVnnQh::52", "page_id": "docx::O3w7wV80sisL0vkaaFEcQNVnnQh", "title": "3.5➡️3.0 软件项目管理 / IT Project Management", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management", "section": "优秀网课教程", "url": "https://a1npn29y3xu.feishu.cn/wiki/O3w7wV80sisL0vkaaFEcQNVnnQh", "source_type": "docx", "n_chars": 117, "text": "[7e Resources](https://intropm2.com/7e-resources/)\n\n[Certification](https://pmtexts.com/free-resources/pmp-and-capm/)"}
{"id": "docx::O3w7wV80sisL0vkaaFEcQNVnnQh::53", "page_id": "docx::O3w7wV80sisL0vkaaFEcQNVnnQh", "title": "3.5➡️3.0 软件项目管理 / IT Project Management", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management", "section": "正文部分", "url": "https://a1npn29y3xu.feishu.cn/wiki/O3w7wV80sisL0vkaaFEcQNVnnQh", "source_type": "docx", "n_chars": 700, "text": "\n\n#\n复习课问答回顾（草稿）\n\n考试重点一：WBS\n\nPPT 21 24 32\n\n考试重点二：时间管理\n\nPPT 32\n\n有哪两类网络图（双代号网络图或者箭线图）\n\n什么叫前导图 PDM 法，有什么作用\n\n关键路径法\n\n43 46 56\n考试重点三：成本管理\n\nFigure 7.1\n\nFigure 7.2\n净值管理：中文版教材 209～213！\n\n考试重点四：质量管理\n\n什么是质量管理？（224）\n\n考试重点五 ：人力资源管理\n\n什么是人力资源管理？（259）\n\n需求层次理论（261）\n\n什么是风险管理？（321）\n\n项目综合管理（净现值分析必考）\n\n项目管理过程组：案例研究（60～65）\n\n什么是项目管理的系统观点？\n\n怎么用系统方法去做分析和管理？\n\n项目的生命周期？（瀑布模型 敏捷模型 螺旋模型）\n\n什么是干系人管理？\n\nScrum 框架\n\n什么是项目管理、项目、集成管理？"}
{"id": "docx::KLE5wJyTPi8DjUkbtY1cfJDjnrf::55", "page_id": "docx::KLE5wJyTPi8DjUkbtY1cfJDjnrf", "title": "Chapter 04 Understanding Quality Attributes / 第四章：理解质量属性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 04 Understanding Quality Attributes / 第四章：理解质量属性", "section": "这一章相当于是 05 \\~ 11 的总起章节，我们的学习思路是：", "url": "https://a1npn29y3xu.feishu.cn/wiki/KLE5wJyTPi8DjUkbtY1cfJDjnrf", "source_type": "docx", "n_chars": 296, "text": "需求是什么？引入了什么质量属性？\n\n这个质量属性是什么？具有什么特点？\n\n这个质量属性可以应用于哪些场景？\n\nS —— 刺激：① 触发**系统响应的事件** ② 响应的**条件**\n\nS —— 源头：引发刺激的 **实体 或者 组件**\n\nE —— 环境：**条件** 或者 **上下文**\n\nA —— 工件：**系统** / 部分**系统** / 系统集合 / 系统切片\n\nR —— 响应：**对刺激的回复**\n\nR —— 响应度量：① 评估**效率的准则** / ② **可量化的指标**\n\n这个质量属性的策略是什么样的？能不能用一个策略树整理起来？\n\n策略树里面的每一个节点是什么意思？"}
{"id": "docx::KLE5wJyTPi8DjUkbtY1cfJDjnrf::56", "page_id": "docx::KLE5wJyTPi8DjUkbtY1cfJDjnrf", "title": "Chapter 04 Understanding Quality Attributes / 第四章：理解质量属性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 04 Understanding Quality Attributes / 第四章：理解质量属性", "section": "Architecture and Requirements / 架构与需求", "url": "https://a1npn29y3xu.feishu.cn/wiki/KLE5wJyTPi8DjUkbtY1cfJDjnrf", "source_type": "docx", "n_chars": 441, "text": "**Functional requirements**: What the system must do, how it must behave or react to run-time stimuli / 功能需求：系统必须执行的任务，它必须如何在运行时对刺激做出反应或表现\n\n**Quality attribute requirements**: qualify functional requirements. / 质量属性需求：对功能需求进行定性\n\n① How fast must the function be performed? / 功能执行的速度要求是多少？\n\n② How resilient it must be to erroneous input? / 对错误输入的容错能力要求是多少？\n\n**Constraints**: A design decision with zero degrees of freedom. / 限制条件：设计决策，完全没有自由度。"}
{"id": "docx::KLE5wJyTPi8DjUkbtY1cfJDjnrf::57", "page_id": "docx::KLE5wJyTPi8DjUkbtY1cfJDjnrf", "title": "Chapter 04 Understanding Quality Attributes / 第四章：理解质量属性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 04 Understanding Quality Attributes / 第四章：理解质量属性", "section": "Architecture and Requirements / 架构与需求/Functionality / 功能", "url": "https://a1npn29y3xu.feishu.cn/wiki/KLE5wJyTPi8DjUkbtY1cfJDjnrf", "source_type": "docx", "n_chars": 318, "text": "Functionality is the ability of the system to do the work for which it was intended. / 功能性是系统执行其预定工作能力的体现。\n\nFunctionality has a strange relationship to architecture: / 功能性与架构之间有一种奇怪的关系：\n\n- Functionality does not determine architecture. / 功能性不决定架构。\n- Functionality and quality attributes are orthogonal. / 功能性和质量属性是正交的。"}
{"id": "docx::KLE5wJyTPi8DjUkbtY1cfJDjnrf::58", "page_id": "docx::KLE5wJyTPi8DjUkbtY1cfJDjnrf", "title": "Chapter 04 Understanding Quality Attributes / 第四章：理解质量属性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 04 Understanding Quality Attributes / 第四章：理解质量属性", "section": "Quality Attribute Considerations / 质量属性的考虑", "url": "https://a1npn29y3xu.feishu.cn/wiki/KLE5wJyTPi8DjUkbtY1cfJDjnrf", "source_type": "docx", "n_chars": 684, "text": "If a functional requirement is \"**when the user presses the green button the Options dialog appears**”: / 如果一个功能需求是“当用户按下绿色按钮时，选项对话框出现”：\n\n- A **performance** qualification might describe how **quickly** the dialog will appear; / 性能资格可能描述对话框出现的速度；\n- An **availability** qualification might describe how **often this function will fail**, and how **quickly it will be repaired**; / 可用性资格可能描述该功能失败的频率，以及修复的速度；\n- A **usability** qualification might describe how **easy** it is to learn this function. / 可用性资格可能描述学习该功能的难易程度。\n\nThese are the ones that describe some properties of the **system at runtime** — Availability, performance, usability, security. / 描述系统在运行时属性的：可用性、性能、可用性、安全性。(APUS)"}
{"id": "docx::KLE5wJyTPi8DjUkbtY1cfJDjnrf::59", "page_id": "docx::KLE5wJyTPi8DjUkbtY1cfJDjnrf", "title": "Chapter 04 Understanding Quality Attributes / 第四章：理解质量属性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 04 Understanding Quality Attributes / 第四章：理解质量属性", "section": "Quality Attribute Considerations / 质量属性的考虑", "url": "https://a1npn29y3xu.feishu.cn/wiki/KLE5wJyTPi8DjUkbtY1cfJDjnrf", "source_type": "docx", "n_chars": 534, "text": "at runtime** — Availability, performance, usability, security. / 描述系统在运行时属性的：可用性、性能、可用性、安全性。(APUS)\n\nThese are the ones that describe some properties of the **development of the system** — Modifiability, Testability. / 描述系统开发过程中属性的：可修改性、可测试性。(MT)\n\nThere are problems with previous discussions of quality attributes. / 之前关于质量属性的讨论存在一些问题：\n\n1. **Untestable definitions**. The definitions provided for an attribute are not testable. It is meaningless to say that a system will be \"modifiable.\" / **不可测试的定义**：给出的属性定义是不可测试的。说系统是“可修改的”是没有意义的。"}
{"id": "docx::KLE5wJyTPi8DjUkbtY1cfJDjnrf::60", "page_id": "docx::KLE5wJyTPi8DjUkbtY1cfJDjnrf", "title": "Chapter 04 Understanding Quality Attributes / 第四章：理解质量属性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 04 Understanding Quality Attributes / 第四章：理解质量属性", "section": "Quality Attribute Considerations / 质量属性的考虑", "url": "https://a1npn29y3xu.feishu.cn/wiki/KLE5wJyTPi8DjUkbtY1cfJDjnrf", "source_type": "docx", "n_chars": 524, "text": "eaningless to say that a system will be \"modifiable.\" / **不可测试的定义**：给出的属性定义是不可测试的。说系统是“可修改的”是没有意义的。\n2. **Overlapping concerns**. Is a system failure due to a denial of service attack an aspect of availability, performance, security, or usability? / **重叠的关注点**：由于拒绝服务攻击而导致的系统故障是属于可用性、性能、安全性还是可用性方面的问题？\n\nA solution to the problems (untestable definitions and overlapping concerns) is to use ***quality attribute scenarios*** as a means of characterizing quality attributes. / 解决这些问题（不可测试的定义和重叠的关注点）的一种方法是使用***质量属性场景***来表征质量属性。"}
{"id": "docx::KLE5wJyTPi8DjUkbtY1cfJDjnrf::61", "page_id": "docx::KLE5wJyTPi8DjUkbtY1cfJDjnrf", "title": "Chapter 04 Understanding Quality Attributes / 第四章：理解质量属性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 04 Understanding Quality Attributes / 第四章：理解质量属性", "section": "Quality Attribute Considerations / 质量属性的考虑/Quality Attribute Scenarios / 质量属性场景（必考必会）", "url": "https://a1npn29y3xu.feishu.cn/wiki/KLE5wJyTPi8DjUkbtY1cfJDjnrf", "source_type": "docx", "n_chars": 615, "text": "We use a common form to specify all quality attribute requirements as scenarios. / 我们使用一种通用的形式将所有质量属性要求指定为场景。\n\nHere are the parts of quality attribute scenarios: / 质量属性场景的组成部分：\n\n① **Stimulus** / 刺激\n\n- The event that triggers the system to react. / 触发系统反应的事件。\n- Condition that requires a response when it arrives at a system. / 到达系统时需要响应的条件。\n\n② **Stimulus Source** / 刺激源\n\n- The entity (a human, a computer system, or any other actuator) or component that generates the stimulus. / 生成刺激的实体（人类、计算机系统或任何其他执行器）或组件。\n\n③ **Response** / 响应\n\n- The system's reaction to the stimulus. / 系统对刺激的反应。\n\n④ **Response Measure** / 响应度量"}
{"id": "docx::KLE5wJyTPi8DjUkbtY1cfJDjnrf::62", "page_id": "docx::KLE5wJyTPi8DjUkbtY1cfJDjnrf", "title": "Chapter 04 Understanding Quality Attributes / 第四章：理解质量属性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 04 Understanding Quality Attributes / 第四章：理解质量属性", "section": "Quality Attribute Considerations / 质量属性的考虑/Quality Attribute Scenarios / 质量属性场景（必考必会）", "url": "https://a1npn29y3xu.feishu.cn/wiki/KLE5wJyTPi8DjUkbtY1cfJDjnrf", "source_type": "docx", "n_chars": 642, "text": "sponse** / 响应\n\n- The system's reaction to the stimulus. / 系统对刺激的反应。\n\n④ **Response Measure** / 响应度量\n\n- The criteria used to evaluate the effectiveness or performance of the response. / 用于评估响应效果或性能的标准。\n- It should be measurable in some fashion so that the requirement can be tested. / 它应该以某种方式可测量，以便可以测试需求。\n\n⑤ **Environment** / 环境\n\n- The conditions or context under which the system operates when the stimulus occurs. / 刺激发生时，系统运行的条件或环境。\n- The stimulus occurs under certain conditions. The system may be in an overload condition or in normal operation, or some other relevant state. / 刺激在特定条件下发生。系统可能处于过载状态或正常运行状态，或者其他相关状态。\n\n⑥ **Artifact** / 组件"}
{"id": "docx::KLE5wJyTPi8DjUkbtY1cfJDjnrf::63", "page_id": "docx::KLE5wJyTPi8DjUkbtY1cfJDjnrf", "title": "Chapter 04 Understanding Quality Attributes / 第四章：理解质量属性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 04 Understanding Quality Attributes / 第四章：理解质量属性", "section": "Quality Attribute Considerations / 质量属性的考虑/Quality Attribute Scenarios / 质量属性场景（必考必会）", "url": "https://a1npn29y3xu.feishu.cn/wiki/KLE5wJyTPi8DjUkbtY1cfJDjnrf", "source_type": "docx", "n_chars": 457, "text": "ation, or some other relevant state. / 刺激在特定条件下发生。系统可能处于过载状态或正常运行状态，或者其他相关状态。\n\n⑥ **Artifact** / 组件\n\n- The system or part of the system that is affected by the stimulus. / 受刺激影响的系统或系统部分。\n- This may be a collection of systems, the whole system, or some piece or pieces of it. Some artifact are stimulated. / 这可能是系统的集合，整个系统，或其中的某个或某些部分。一些人工制品被激发。\n\n\n\n"}
{"id": "docx::KLE5wJyTPi8DjUkbtY1cfJDjnrf::64", "page_id": "docx::KLE5wJyTPi8DjUkbtY1cfJDjnrf", "title": "Chapter 04 Understanding Quality Attributes / 第四章：理解质量属性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 04 Understanding Quality Attributes / 第四章：理解质量属性", "section": "Quality Attribute Considerations / 质量属性的考虑/Achieving Quality Attributes Through Tactics / 通过策略实现质量属性", "url": "https://a1npn29y3xu.feishu.cn/wiki/KLE5wJyTPi8DjUkbtY1cfJDjnrf", "source_type": "docx", "n_chars": 457, "text": "There are a collection of primitive design techniques that an architect can use to achieve a quality attribute response. We call these architectural design *primitives tactics*. / 有一系列基本的设计技术，架构师可以用它们来实现质量属性的响应。我们称这些为架构设计*原语策略*。\n\nTactics, like design patterns, are techniques that architects have been using for years. / 策略像设计模式一样，是架构师多年来一直在使用的技术。\n\n**We do not invent tactics, we simply capture what architects do in practice. / 我们不是发明策略，而是捕捉架构师在实践中使用的方法。**"}
{"id": "docx::KLE5wJyTPi8DjUkbtY1cfJDjnrf::65", "page_id": "docx::KLE5wJyTPi8DjUkbtY1cfJDjnrf", "title": "Chapter 04 Understanding Quality Attributes / 第四章：理解质量属性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 04 Understanding Quality Attributes / 第四章：理解质量属性", "section": "Quality Attribute Considerations / 质量属性的考虑/Achieving Quality Attributes Through Tactics / 通过策略实现质量属性/Tactics: examples / 策略示例", "url": "https://a1npn29y3xu.feishu.cn/wiki/KLE5wJyTPi8DjUkbtY1cfJDjnrf", "source_type": "docx", "n_chars": 301, "text": "**Resource scheduling** is a tactic for **performance**. / **资源调度**是提高**性能**的策略。\n\n- **Given**: release time, workload of each task / **给定条件**：每个任务的释放时间和工作负载\n- **Objective**: to minimize average completion time of the tasks / **目标**：最小化任务的平均完成时间\n\n"}
{"id": "docx::KLE5wJyTPi8DjUkbtY1cfJDjnrf::66", "page_id": "docx::KLE5wJyTPi8DjUkbtY1cfJDjnrf", "title": "Chapter 04 Understanding Quality Attributes / 第四章：理解质量属性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 04 Understanding Quality Attributes / 第四章：理解质量属性", "section": "Quality Attribute Considerations / 质量属性的考虑/Achieving Quality Attributes Through Tactics / 通过策略实现质量属性/Tatics vs Architectural pattern / 策略和架构模式的对比", "url": "https://a1npn29y3xu.feishu.cn/wiki/KLE5wJyTPi8DjUkbtY1cfJDjnrf", "source_type": "docx", "n_chars": 353, "text": "\"A tactic is a design decision for a single quality attribute. / 策略是针对单一质量属性的设计决策。\n\nA tactic does not consider tradeoffs among quality attributes. / 策略不考虑质量属性之间的权衡。\n\nArchitectural patterns can be seen as 'packages' of tactics, in which tradeoffs are considered.\" / 架构模式可以被看作是“策略包”，其中考虑了质量属性之间的权衡。\n\n"}
{"id": "docx::SnJNwMHnRiQQvxk2zCEcD6ISnsb::67", "page_id": "docx::SnJNwMHnRiQQvxk2zCEcD6ISnsb", "title": "Chapter 04 集成管理 Integration", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 04 集成管理 Integration", "section": "Chapter 04 集成管理 Integration", "url": "https://a1npn29y3xu.feishu.cn/wiki/SnJNwMHnRiQQvxk2zCEcD6ISnsb", "source_type": "docx", "n_chars": 682, "text": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::SnJNwMHnRiQQvxk2zCEcD6ISnsb::68", "page_id": "docx::SnJNwMHnRiQQvxk2zCEcD6ISnsb", "title": "Chapter 04 集成管理 Integration", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 04 集成管理 Integration", "section": "Chapter 04 集成管理 Integration", "url": "https://a1npn29y3xu.feishu.cn/wiki/SnJNwMHnRiQQvxk2zCEcD6ISnsb", "source_type": "docx", "n_chars": 668, "text": "ishu.cn/file/DFlRbu6sRo4qfYxRHu6cmV9Tnpd)\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::SnJNwMHnRiQQvxk2zCEcD6ISnsb::69", "page_id": "docx::SnJNwMHnRiQQvxk2zCEcD6ISnsb", "title": "Chapter 04 集成管理 Integration", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 04 集成管理 Integration", "section": "Chapter 04 集成管理 Integration", "url": "https://a1npn29y3xu.feishu.cn/wiki/SnJNwMHnRiQQvxk2zCEcD6ISnsb", "source_type": "docx", "n_chars": 668, "text": "ishu.cn/file/FQ6bbtH2dolLPaxgrb6cJO3BnNb)\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::SnJNwMHnRiQQvxk2zCEcD6ISnsb::70", "page_id": "docx::SnJNwMHnRiQQvxk2zCEcD6ISnsb", "title": "Chapter 04 集成管理 Integration", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 04 集成管理 Integration", "section": "Chapter 04 集成管理 Integration", "url": "https://a1npn29y3xu.feishu.cn/wiki/SnJNwMHnRiQQvxk2zCEcD6ISnsb", "source_type": "docx", "n_chars": 668, "text": "ishu.cn/file/Hb6KbyTz7odohPxkU23cJMUMnpc)\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::SnJNwMHnRiQQvxk2zCEcD6ISnsb::71", "page_id": "docx::SnJNwMHnRiQQvxk2zCEcD6ISnsb", "title": "Chapter 04 集成管理 Integration", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 04 集成管理 Integration", "section": "Chapter 04 集成管理 Integration", "url": "https://a1npn29y3xu.feishu.cn/wiki/SnJNwMHnRiQQvxk2zCEcD6ISnsb", "source_type": "docx", "n_chars": 668, "text": "ishu.cn/file/C4sDbY5KhowZ4gxwpBVct3rkngb)\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f::72", "page_id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f", "title": "Chapter 05 Availability / 第五章：可用性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 05 Availability / 第五章：可用性", "section": "What is Availability? / 什么是可用性？", "url": "https://a1npn29y3xu.feishu.cn/wiki/UQWlwRLJDiMG8jkZsV4cqpKwn6f", "source_type": "docx", "n_chars": 681, "text": "**Availability** refers to the property of software that it is there and ready to carry out its task when you need it to be. / 可用性是指软件具备在需要时准备好执行任务的特性。\n\n**Availability** refers to the ability of a system to **mask or repair faults** such that the **cumulative service outage period** does not exceed a required value over a specified time interval. / 可用性是指系统能够**屏蔽或修复故障**，从而使得在指定时间间隔内，累计服务中断时间不超过要求的值（累计无法服务时长尽可能短）\n\n**Availability** is about minimizing service outage time by **mitigating faults**. / 可用性旨在通过**减轻故障**来最小化服务中断时间。\n\n**Availability vs. reliability or dependability** / **可用性与可靠性或依赖性的区别**\n\n- Availability encompasses what is normally called reliability. / 可用性包括通常所称的可靠性。"}
{"id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f::73", "page_id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f", "title": "Chapter 05 Availability / 第五章：可用性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 05 Availability / 第五章：可用性", "section": "What is Availability? / 什么是可用性？", "url": "https://a1npn29y3xu.feishu.cn/wiki/UQWlwRLJDiMG8jkZsV4cqpKwn6f", "source_type": "docx", "n_chars": 340, "text": "*可用性与可靠性或依赖性的区别**\n\n- Availability encompasses what is normally called reliability. / 可用性包括通常所称的可靠性。\n- Availability encompasses other considerations such as service outage due to periodic maintenance. / 可用性还包括其他因素，如由于定期维护导致的服务中断。\n\nAvailability is closely related to security, e.g., denial-of-service, performance. / 可用性与安全性密切相关，例如拒绝服务攻击、性能等。"}
{"id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f::74", "page_id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f", "title": "Chapter 05 Availability / 第五章：可用性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 05 Availability / 第五章：可用性", "section": "Availability General Scenario / 可用性的通用场景", "url": "https://a1npn29y3xu.feishu.cn/wiki/UQWlwRLJDiMG8jkZsV4cqpKwn6f", "source_type": "docx", "n_chars": 700, "text": "Portion of Scenario / 场景中的组成部分Possible Values / 可能的取值Source / 源头Internal/external: people, hardware, software, physical infrastructure, physical environment内部/外部：人员、硬件、软件、物理基础设施、物理环境Stimulus / 激励Fault: omission, crash, incorrect timing, incorrect response故障：遗漏、崩溃、时序错误、响应错误Artifact / 组件System's processors, communication channels, persistent storage, processes系统的处理器、通信通道、持久存储、进程Environment / 环境Normal operation, startup, shutdown, repair mode, degraded operation, overloaded operation正常运行、启动、关闭、修复模式、降级运行、过载运行Response / 反馈Prevent the fault from becoming a failure防止故障变成失败Detect the fault检测故障Log the fault记录故障Notify appropriate entities (people or systems)通知相关实体（人员或系统）Recover from the fault从故障中恢复Dis"}
{"id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f::75", "page_id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f", "title": "Chapter 05 Availability / 第五章：可用性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 05 Availability / 第五章：可用性", "section": "Availability General Scenario / 可用性的通用场景", "url": "https://a1npn29y3xu.feishu.cn/wiki/UQWlwRLJDiMG8jkZsV4cqpKwn6f", "source_type": "docx", "n_chars": 700, "text": "fault记录故障Notify appropriate entities (people or systems)通知相关实体（人员或系统）Recover from the fault从故障中恢复Disable source of events causing the fault禁用引发故障的事件源Be temporarily unavailable while repair is being effected在修复过程中暂时不可用Fix or mask the fault/failure or contain the damage it causes修复或屏蔽故障/失效，或遏制其造成的损害Operate in a degraded mode while repair is being effected在修复过程中以降级模式运行Response Measure / 反馈度量Time or time interval when the system must be available系统必须可用的时间或时间间隔Availability percentage (e.g., 99.999%)可用性百分比（例如，99.999%）Time to detect the fault检测故障的时间Monitor time to repair the fault监控修复故障的时间Time or time interval in which system can be in degraded mode系统可处于降级模式的时间或时间间隔Proportion (e.g., 99%) or rate (e"}
{"id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f::76", "page_id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f", "title": "Chapter 05 Availability / 第五章：可用性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 05 Availability / 第五章：可用性", "section": "Availability General Scenario / 可用性的通用场景", "url": "https://a1npn29y3xu.feishu.cn/wiki/UQWlwRLJDiMG8jkZsV4cqpKwn6f", "source_type": "docx", "n_chars": 255, "text": "e interval in which system can be in degraded mode系统可处于降级模式的时间或时间间隔Proportion (e.g., 99%) or rate (e.g., up to 100 per second) of a certain class of faults that the system prevents, or handles without failing系统预防或处理特定类别故障的比例（例如，99%）或速率（例如，每秒最多100个），而不发生失效"}
{"id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f::77", "page_id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f", "title": "Chapter 05 Availability / 第五章：可用性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 05 Availability / 第五章：可用性", "section": "Availability General Scenario / 可用性的通用场景/Sample / 示例", "url": "https://a1npn29y3xu.feishu.cn/wiki/UQWlwRLJDiMG8jkZsV4cqpKwn6f", "source_type": "docx", "n_chars": 584, "text": "The heartbeat monitor detects that the server is nonresponsive during normal operations. The system informs the operator and continues to operate with no downtime. / 心跳监控器检测到服务器在正常运行期间无响应。系统通知操作员，并继续在没有停机的情况下运行。\n\n- **Stimulus**: non-responsiveness / **刺激**：无响应\n- **Response**: inform the operator / **响应**：通知操作员\n- **Response measure**: no downtime, or 100% availability percentage / **响应度量**：无停机时间，或100%的可用性百分比\n- **Environment**: normal operation / **环境**：正常运行\n- **Artifact**: heartbeat monitor / **工件**：心跳监控器\n- **Stimulus source**: server / **刺激源**：服务器\n\nFault vs. Failure / 故障 vs. 失效"}
{"id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f::78", "page_id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f", "title": "Chapter 05 Availability / 第五章：可用性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 05 Availability / 第五章：可用性", "section": "Availability General Scenario / 可用性的通用场景/Sample / 示例", "url": "https://a1npn29y3xu.feishu.cn/wiki/UQWlwRLJDiMG8jkZsV4cqpKwn6f", "source_type": "docx", "n_chars": 390, "text": "monitor / **工件**：心跳监控器\n- **Stimulus source**: server / **刺激源**：服务器\n\nFault vs. Failure / 故障 vs. 失效\n\nA failure occurs when the system no longer delivers a service consistent with its specification – this failure is observable by the system's actors. / 失效发生在系统不再提供与其规格一致的服务时——这种失效是系统的参与者可以观察到的。\n\nA fault (or combination of faults) has the potential to cause a failure. / 故障（或多个故障的组合）具有导致失效的潜力。"}
{"id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f::79", "page_id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f", "title": "Chapter 05 Availability / 第五章：可用性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 05 Availability / 第五章：可用性", "section": "Availability Tactics / 可用性策略/Goal / 目标", "url": "https://a1npn29y3xu.feishu.cn/wiki/UQWlwRLJDiMG8jkZsV4cqpKwn6f", "source_type": "docx", "n_chars": 313, "text": "**Availability tactics** enable a system to endure faults so that services remain compliant with their specifications. / **可用性策略**使系统能够承受故障，从而确保服务持续符合其规格要求。\n\nThe tactics keep faults from becoming failures or at least bound the effects of the fault and make repair possible. / 这些策略防止故障转变为系统故障，或者至少限制故障的影响，并使修复成为可能。"}
{"id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f::80", "page_id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f", "title": "Chapter 05 Availability / 第五章：可用性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 05 Availability / 第五章：可用性", "section": "Availability Tactics / 可用性策略/Tactics Tree / 策略树/**Detect Faults / 监测故障**", "url": "https://a1npn29y3xu.feishu.cn/wiki/UQWlwRLJDiMG8jkZsV4cqpKwn6f", "source_type": "docx", "n_chars": 541, "text": "- **Ping / Echo**:\n Ping is used to determine the reachability of a network and measure the round-trip delay through the associated network path.\n网络延迟检测：Ping用于确定网络的可达性，并测量通过相关网络路径的往返延迟。\n- **Monitor**:\n A component used to monitor the state of health of other parts of the system.\n监控：监控组件用于监测系统其他部分的健康状态。\n- **Heartbeat**:\n A periodic message exchange between a system monitor and a process being monitored.\n\n心跳：系统监控器与被监控进程之间的周期性消息交换。\n\n- The process periodically resets the watchdog timer in its monitor.\n进程定期重置监控器中的看门狗定时器。（实现了周期性的信息交换，但是占用网络）"}
{"id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f::81", "page_id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f", "title": "Chapter 05 Availability / 第五章：可用性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 05 Availability / 第五章：可用性", "section": "Availability Tactics / 可用性策略/Tactics Tree / 策略树/**Detect Faults / 监测故障**", "url": "https://a1npn29y3xu.feishu.cn/wiki/UQWlwRLJDiMG8jkZsV4cqpKwn6f", "source_type": "docx", "n_chars": 674, "text": "ocess periodically resets the watchdog timer in its monitor.\n进程定期重置监控器中的看门狗定时器。（实现了周期性的信息交换，但是占用网络）\n- **Overhead**: Piggybacking the heartbeat messages onto other control messages reduces the overhead. However, heartbeat can consume significant network bandwidth, causing overhead.\n 开销：将心跳消息附加到其他控制消息上可以减少开销，但心跳消息可能占用大量网络带宽，导致开销增加。\n\n**Differences between Ping and Heartbeat / Ping 和 心跳的区别**\n\n- **Ping** is typically used to test the basic reachability of a network or system, while **Heartbeat** is used to monitor the health of a process or system over time.\n- **Ping**: 简单检测网络或系统的基本可达性。\n- **Heartbeat**: 用于长时间监控进程或系统的健康状态。\n- Who initiates the health check ? / 哪个机制初始化健康检查？"}
{"id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f::82", "page_id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f", "title": "Chapter 05 Availability / 第五章：可用性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 05 Availability / 第五章：可用性", "section": "Availability Tactics / 可用性策略/Tactics Tree / 策略树/**Detect Faults / 监测故障**", "url": "https://a1npn29y3xu.feishu.cn/wiki/UQWlwRLJDiMG8jkZsV4cqpKwn6f", "source_type": "docx", "n_chars": 673, "text": "测网络或系统的基本可达性。\n- **Heartbeat**: 用于长时间监控进程或系统的健康状态。\n- Who initiates the health check ? / 哪个机制初始化健康检查？\n In a **Ping** test, the initiator is typically the client or system performing the check. In a **Heartbeat**, the health check is initiated periodically by the system or process being monitored.\n- **Ping**: 通常由客户端或执行检测的系统发起。\n- **Heartbeat**: 由被监控的系统或进程定期发起健康检查。\n- **Timestamp**: A timestamp is used to detect incorrect sequences of events, particularly in distributed message-passing systems.\n 时间戳：时间戳用于检测事件的错误顺序，尤其是在分布式消息传递系统中。\n- **Condition Monitoring**: The process of checking the conditions of a device or process, or validating assumptions made during system design."}
{"id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f::83", "page_id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f", "title": "Chapter 05 Availability / 第五章：可用性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 05 Availability / 第五章：可用性", "section": "Availability Tactics / 可用性策略/Tactics Tree / 策略树/**Detect Faults / 监测故障**", "url": "https://a1npn29y3xu.feishu.cn/wiki/UQWlwRLJDiMG8jkZsV4cqpKwn6f", "source_type": "docx", "n_chars": 383, "text": "hecking the conditions of a device or process, or validating assumptions made during system design.\n 状态监控：检查设备或进程的条件，或验证在系统设计过程中做出的假设。\n- **Checksum**: A checksum is used in data storage and transmission to ensure the integrity of the data.\n 校验码：校验码用于数据存储和传输中，以确保数据的完整性。\n\n\n\n"}
{"id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f::84", "page_id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f", "title": "Chapter 05 Availability / 第五章：可用性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 05 Availability / 第五章：可用性", "section": "Availability Tactics / 可用性策略/Tactics Tree / 策略树/**Recover from Faults (Preparation & Repair) / 从故障中恢复过来（准备 & 恢复）**", "url": "https://a1npn29y3xu.feishu.cn/wiki/UQWlwRLJDiMG8jkZsV4cqpKwn6f", "source_type": "docx", "n_chars": 687, "text": "**Active Redundancy (Hot Spare) / 主动冗余（热备份）**\n\n- In an active redundancy setup, all nodes in a protection group process identical inputs in parallel, allowing redundant spares to maintain synchronous states with the active nodes.\n在主动冗余配置中，保护组中的所有节点并行处理相同的输入，允许冗余备件与活动节点保持同步状态。\n\n**Spare (Cold Spare) / 备件（冷备份）**\n\n- Redundant spares in a cold spare setup remain out of service until a failover occurs. When a failover happens, a power-on-reset procedure is initiated on the redundant spare before it is placed into service.\n在冷备份配置中，冗余备件在故障转移发生之前处于闲置状态，发生故障转移时会对冗余备件进行上电重置操作，然后将其投入使用。\n\n\n\n**Passive Redundancy (Warm Spare) / 被动冗余（暖备份）**"}
{"id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f::85", "page_id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f", "title": "Chapter 05 Availability / 第五章：可用性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 05 Availability / 第五章：可用性", "section": "Availability Tactics / 可用性策略/Tactics Tree / 策略树/**Recover from Faults (Preparation & Repair) / 从故障中恢复过来（准备 & 恢复）**", "url": "https://a1npn29y3xu.feishu.cn/wiki/UQWlwRLJDiMG8jkZsV4cqpKwn6f", "source_type": "docx", "n_chars": 697, "text": "tps://feishu.cn/file/JCoHbAthbousT9x4yrAcNjYenAf)\n\n**Passive Redundancy (Warm Spare) / 被动冗余（暖备份）**\n\n- In passive redundancy, only the active members of the protection group process input traffic. One of their duties is to provide the redundant spare(s) with periodic state updates.\n在被动冗余配置中，只有保护组中的活动成员处理输入流量，它们的职责之一是定期向冗余备件提供状态更新。\n\n\n\n**Rollback / 回滚**\n\n- Rollback refers to reverting to a previous known good state, referred to as the “rollback line.” This tactic is often combined with redundancy tactics to ensure recovery.\n回滚是指恢复到先前已知的良好状态，通常与冗余策略结合使用，以确保系统恢复。\n- After a rollback, a standby version of the failed component becomes active."}
{"id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f::86", "page_id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f", "title": "Chapter 05 Availability / 第五章：可用性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 05 Availability / 第五章：可用性", "section": "Availability Tactics / 可用性策略/Tactics Tree / 策略树/**Recover from Faults (Preparation & Repair) / 从故障中恢复过来（准备 & 恢复）**", "url": "https://a1npn29y3xu.feishu.cn/wiki/UQWlwRLJDiMG8jkZsV4cqpKwn6f", "source_type": "docx", "n_chars": 603, "text": "，通常与冗余策略结合使用，以确保系统恢复。\n- After a rollback, a standby version of the failed component becomes active.\n在回滚后，故障组件的备用版本将成为活动组件。\n- Checkpoint: A checkpoint is a saved version of a previous state, and it can be stored in a fixed location. It needs to be updated regularly to ensure recovery.\n- 检查点：检查点是先前状态的备份，通常存储在固定位置，并需要定期更新以确保恢复。\n\n**Retry / 重试（重启能解决 90% 的问题）**\n\n- When a failure is transient, retrying the operation may lead to success. For example, network re-transmission may resolve a temporary issue.\n当故障是暂时性的时，重试操作可能导致成功。例如，网络重传可能解决暂时性问题。\n\n**Ignore Faulty Behavior (Ostrich Algorithm) / 忽略错误行为（鸵鸟算法）**"}
{"id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f::87", "page_id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f", "title": "Chapter 05 Availability / 第五章：可用性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 05 Availability / 第五章：可用性", "section": "Availability Tactics / 可用性策略/Tactics Tree / 策略树/**Recover from Faults (Preparation & Repair) / 从故障中恢复过来（准备 & 恢复）**", "url": "https://a1npn29y3xu.feishu.cn/wiki/UQWlwRLJDiMG8jkZsV4cqpKwn6f", "source_type": "docx", "n_chars": 581, "text": "是暂时性的时，重试操作可能导致成功。例如，网络重传可能解决暂时性问题。\n\n**Ignore Faulty Behavior (Ostrich Algorithm) / 忽略错误行为（鸵鸟算法）**\n\n- This approach involves ignoring messages sent from a source when it is determined that those messages are spurious or erroneous.For example, ignore the messages from a denial of service attacker.\n这种方法是在确认某些消息是虚假或错误时，忽略这些消息的来源。例如，忽略来自拒绝服务攻击者的消息。\n\n**Degradation / 降级**\n\n- Degradation involves maintaining the most critical system functions in the presence of component failures while dropping less critical functions.\n降级在组件故障的情况下，保持最关键的系统功能，同时丢弃较不重要的功能。\n\n**Reconfiguration / 重新配置**"}
{"id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f::88", "page_id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f", "title": "Chapter 05 Availability / 第五章：可用性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 05 Availability / 第五章：可用性", "section": "Availability Tactics / 可用性策略/Tactics Tree / 策略树/**Recover from Faults (Preparation & Repair) / 从故障中恢复过来（准备 & 恢复）**", "url": "https://a1npn29y3xu.feishu.cn/wiki/UQWlwRLJDiMG8jkZsV4cqpKwn6f", "source_type": "docx", "n_chars": 287, "text": "dropping less critical functions.\n降级在组件故障的情况下，保持最关键的系统功能，同时丢弃较不重要的功能。\n\n**Reconfiguration / 重新配置**\n\n- Reconfiguration refers to reassigning responsibilities to the remaining functioning resources, while maintaining as much functionality as possible.\n重新配置指的是将责任重新分配给剩余的正常工作资源，同时尽可能保持更多的功能。"}
{"id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f::89", "page_id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f", "title": "Chapter 05 Availability / 第五章：可用性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 05 Availability / 第五章：可用性", "section": "Availability Tactics / 可用性策略/Tactics Tree / 策略树/**Prevent Faults / 防止故障**", "url": "https://a1npn29y3xu.feishu.cn/wiki/UQWlwRLJDiMG8jkZsV4cqpKwn6f", "source_type": "docx", "n_chars": 682, "text": "**Removal From Service / 从服务中移除**\n\n- This involves temporarily placing a system component into an out-of-service state to mitigate potential system failures.\n 通过将系统组件暂时置于非服务状态，以减轻潜在的系统故障。\n\n**Transactions / 事务**\n\n- Transactions bundle state updates to ensure that asynchronous messages exchanged between distributed components are:\n- **Atomic**: Changes happen entirely or not at all.\n- **Consistent**: The system remains in a valid state before and after the transaction.\n- **Isolated**: Transactions do not interfere with one another.\n- **Durable**: Once completed, the changes are permanent.\n事务将状态更新捆绑在一起，确保分布式组件之间交换的异步消息具备以下特点：\n- **原子性**：操作要么完全执行，要么完全不执行。\n- **一致性**：事务前后系统处于有效状态。"}
{"id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f::90", "page_id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f", "title": "Chapter 05 Availability / 第五章：可用性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 05 Availability / 第五章：可用性", "section": "Availability Tactics / 可用性策略/Tactics Tree / 策略树/**Prevent Faults / 防止故障**", "url": "https://a1npn29y3xu.feishu.cn/wiki/UQWlwRLJDiMG8jkZsV4cqpKwn6f", "source_type": "docx", "n_chars": 494, "text": "permanent.\n事务将状态更新捆绑在一起，确保分布式组件之间交换的异步消息具备以下特点：\n- **原子性**：操作要么完全执行，要么完全不执行。\n- **一致性**：事务前后系统处于有效状态。\n- **隔离性**：事务之间不相互干扰。\n- **持久性**：一旦完成，变更是永久性的。\n\n**Predictive Model / 预测性模型**\n\n- Predictive models take corrective actions when conditions are detected that indicate likely future faults. This proactive approach helps prevent faults before they occur.\n预测性模型在检测到可能导致未来故障的条件时，采取纠正措施。这种主动的策略有助于在故障发生之前进行预防。\n\n\n\n**Increase Competence Set / 增强能力集**"}
{"id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f::91", "page_id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f", "title": "Chapter 05 Availability / 第五章：可用性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 05 Availability / 第五章：可用性", "section": "Availability Tactics / 可用性策略/Tactics Tree / 策略树/**Prevent Faults / 防止故障**", "url": "https://a1npn29y3xu.feishu.cn/wiki/UQWlwRLJDiMG8jkZsV4cqpKwn6f", "source_type": "docx", "n_chars": 379, "text": "行预防。\n\n\n\n**Increase Competence Set / 增强能力集**\n\n- Designing a component to handle more fault cases as part of its normal operation. This increases the system's robustness and helps prevent faults by ensuring that components can handle a wider range of scenarios.\n将组件设计为能够处理更多故障情况，并作为正常操作的一部分。这样可以增强系统的健壮性，通过确保组件能够处理更广泛的情况来防止故障。"}
{"id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f::92", "page_id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f", "title": "Chapter 05 Availability / 第五章：可用性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 05 Availability / 第五章：可用性", "section": "**Summary of Availability tactics / 可用性策略总结**", "url": "https://a1npn29y3xu.feishu.cn/wiki/UQWlwRLJDiMG8jkZsV4cqpKwn6f", "source_type": "docx", "n_chars": 686, "text": "可用性策略通常分为三类：**故障检测**、**故障恢复** 和 **故障预防**。\n\n**Fault Detection Tactics / 故障检测策略**\n\n- **Detection tactics** focus on detecting signs of life or health indicators from various system components. These signs can help identify potential failures early and prevent service disruption.\n 故障检测策略侧重于从系统的各个组件中检测生命迹象或健康指标。这些迹象可以帮助及早识别潜在故障，并防止服务中断。\n\n**Fault Recovery Tactics / 故障恢复策略**\n\n- **Recovery tactics** include actions such as retrying an operation or maintaining redundant data or computations. These actions ensure that if a failure occurs, the system can quickly recover and continue functioning.\n 故障恢复策略包括重试操作或维持冗余数据或计算等措施。这些策略确保在发生故障时，系统能够迅速恢复并继续运行。\n\n**Fault Prevention Tactics / 故障预防策略**"}
{"id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f::93", "page_id": "docx::UQWlwRLJDiMG8jkZsV4cqpKwn6f", "title": "Chapter 05 Availability / 第五章：可用性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 05 Availability / 第五章：可用性", "section": "**Summary of Availability tactics / 可用性策略总结**", "url": "https://a1npn29y3xu.feishu.cn/wiki/UQWlwRLJDiMG8jkZsV4cqpKwn6f", "source_type": "docx", "n_chars": 497, "text": "ing.\n 故障恢复策略包括重试操作或维持冗余数据或计算等措施。这些策略确保在发生故障时，系统能够迅速恢复并继续运行。\n\n**Fault Prevention Tactics / 故障预防策略**\n\n- **Prevention tactics** focus on removing elements from service or limiting the scope of faults. By taking components offline or restricting their potential impact, the system can reduce the chances of a failure occurring.\n 故障预防策略侧重于将元素从服务中移除或限制故障的范围。通过将组件下线或限制其潜在影响，系统可以减少故障发生的可能性。\n\n\n\n"}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::94", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "序：必考简答题（前 6 题考过）/**1、项目范围管理涉及的6个主要过程**", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 625, "text": "制定范围管理计划\n\n收集需求\n\n定义范围\n\n创建工作分解结构\n\n验证范围\n\n控制范围\n\n**Planning scope:** determining how the project’s scope and requirements will be managed\n\n**Collecting requirements:** defining and documenting the features and functions of the products produced during the project as well as the processes used for creating them\n\n**Defining scope:** reviewing the project charter, requirements documents, and organizational process assets to create a scope statement\n\n**Creating the WBS:** subdividing the major project deliverables into smaller, more manageable components\n\n**Validating scope**: formalizing acceptance of the project deliverables"}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::95", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "序：必考简答题（前 6 题考过）/**1、项目范围管理涉及的6个主要过程**", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 194, "text": "re manageable components\n\n**Validating scope**: formalizing acceptance of the project deliverables\n\n**Controlling scope:** controlling changes to project scope throughout the life of the project"}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::96", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "序：必考简答题（前 6 题考过）/**2、范围管理计划包括哪些信息？**", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 311, "text": "如何准备一个详细的范围说明书\n\n如何创建一个WBS\n\n如何维护和批准WBS\n\n如何获得正式验收已完成的项目可交付成果\n\n如何控制项目范围变更的请求\n\nHow to prepare a detailed project scope statement\n\nHow to create a WBS\n\nHow to maintain and approve the WBS\n\nHow to obtain formal acceptance of the completed project deliverables\n\nHow to control requests for changes to the project scope"}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::97", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "序：必考简答题（前 6 题考过）/**3、收集需求的常用方法**", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 248, "text": "与项目干系人一对一访谈\n\n使用焦点小组会议、引导式研讨会、群体创新和决策技术\n\n问卷调查法\n\n观察法\n\n原型法和文档分析法\n\n基准测试\n\nInterviewing\n\nFocus groups and facilitated workshops\n\nUsing group creativity and decision-making techniques\n\nQuestionnaires and surveys\n\nObservation\n\nPrototyping\n\n**Benchmarking**"}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::98", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "序：必考简答题（前 6 题考过）/**4、制定工作分解结构（WBS）的方法**", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 514, "text": "使用指南\n\n类比法\n\n自上而下法\n\n自下而上法\n\n思维导图法\n\nUsing guidelines: Some organizations, like the DOD, provide guidelines for preparing WBSs\n\nThe **analogy approach**: Review WBSs of similar projects and tailor to your project\n\nThe **top-down approach**: Start with the largest items of the project and break them down\n\nThe **bottom-up approach**: Start with the specific tasks and roll them up\n\nMind-mapping approach: **Mind mapping** is a technique that uses branches radiating out from a core idea to structure thoughts and ideas"}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::99", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "序：必考简答题（前 6 题考过）/**5、范围控制的目标**", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 285, "text": "影响那些导致范围变更的因素\n\n确保变更是按照综合变更控制中开发的过程来处理的\n\n当变更出现的时候对其进行管理\n\nGoals of scope control are to\n\n- **influence the factors** that cause scope changes\n- **assure changes are processed according to procedures developed as part of integrated change control**, and **manage changes** when they occur"}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::100", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "序：必考简答题（前 6 题考过）/**6、公司应遵循哪些最佳实践来避免出现主要的范围问题？**", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 551, "text": "范围要符合实际\n\n使用户参与项目范围管理\n\n如果可能，使用现有的硬件和软件\n\n遵守良好的项目管理过程\n\n1. **Keep the scope realistic.** Don’t make projects so large that they can’t be completed. Break large projects down into a series of smaller ones\n2. **Involve users in project scope management.** Assign key users to the project team and give them ownership of requirements definition and scope verification\n3. **Use off-the-shelf hardware and software whenever possible.** Many IT people enjoy using the latest and greatest technology, but business needs, not technology trends, must take priority"}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::101", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "序：必考简答题（前 6 题考过）/**6、公司应遵循哪些最佳实践来避免出现主要的范围问题？**", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 279, "text": "g the latest and greatest technology, but business needs, not technology trends, must take priority\n4. **Follow good project management processes.** As described in this chapter and others, there are well-defined processes for managing project scope and other aspects of projects"}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::102", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "序：必考简答题（前 6 题考过）/7、范围蔓延产生的原因？是否可以避免？如何预防范围蔓延的产生？", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 236, "text": "1）确保自己明白项目的范围；\n\n2）了解你自己认为重要的东西和项目主管认为重要的东西；\n\n3）定义你的项目发布目标并让项目主管同意它们；\n\n4）把经过同意的项目发布目标细化成具体的工作要求；\n\n5）将项目分解成大的和小的里程碑并编写一个大概的项目时间表以获得项目主管的同意；\n\n6）一旦时间表已经创立，那么你就需要使用一个 PERT图表或者任务分配表来分配资源和确定项目的关键路径；\n\n7）意识到会出现项目范围蔓延。尽早填写项目范围改变要求表格并在开发的过程中说服项目主管"}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::103", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "Learning Objectives / 学习目标", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 681, "text": "- Understand the importance of good project scope management\n- Describe the process of planning scope management\n- Discuss methods for collecting and documenting requirements to meet stakeholder needs and expectations\n- Explain the scope definition process and describe the contents of a project scope statement\n- Discuss the process for creating a work breakdown structure using the analogy, top-down, bottom-up, and mind-mapping approaches\n- Explain the importance of validating scope and how it relates to defining and controlling scope\n- Understand the importance of controlling scope and approaches for preventing scope-related problems on information technology (IT) projects"}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::104", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "Learning Objectives / 学习目标", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 275, "text": "scope and approaches for preventing scope-related problems on information technology (IT) projects\n- Describe how software can assist in project scope management\n\n\n\n"}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::105", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "5.1 What is Project Scope Management? / 什么是项目范围管理？/5.1.1 必考概念", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 669, "text": "**Scope** refers to *all* the work involved in creating the products of the project and the processes used to create them.\n\n**范围**（Scope）是指开发项目产品所涉及的所有 工作 和用来开展工作的所有过程。\n\nA **deliverable** is a product produced as part of a project, such as hardware or software, planning documents, or meeting minutes.\n\n**可交付成果**（deliverable）指作为项目的一部分而生产的产品，可交付成果可以是产品相关的，比如一套硬件或软件、计划文件或会议记录。\n\n**Project scope management** includes the processes involved in defining and controlling what is or is not included in a project.\n\n**项目范围管理 (project scope management)** 是指对项目包括什么与不包括什么的界定和控制的过程。它确保项目团队和于系人在项目开发什么产品以及开发产品使用什么过程这两方面达成共识。\n\n"}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::106", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "5.1 What is Project Scope Management? / 什么是项目范围管理？/5.1.2 过程管理：六个主要过程", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 677, "text": "**Planning scope:** determining how the project’s scope and requirements will be managed\n\n**Collecting requirements:** defining and documenting the features and functions of the products produced during the project as well as the processes used for creating them\n\n**Defining scope:** reviewing the project charter, requirements documents, and organizational process assets to create a scope statement\n\n**Creating the WBS:** subdividing the major project deliverables into smaller, more manageable components\n\n**Validating scope**: formalizing acceptance of the project deliverables\n\n**Controlling scope:** controlling changes to project scope throughout the life of the project"}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::107", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "5.1 What is Project Scope Management? / 什么是项目范围管理？/5.1.2 过程管理：六个主要过程", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 212, "text": "es\n\n**Controlling scope:** controlling changes to project scope throughout the life of the project\n\n\n\n"}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::108", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "5.1 What is Project Scope Management? / 什么是项目范围管理？/5.1.3 项目过程管理概要", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 169, "text": "\n\n\n\n"}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::109", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "5.2 **Planning Scope Management /** 范围管理计划", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 529, "text": "The project team uses expert judgment and meetings to develop two important outputs: the scope management plan and the requirements management plan.\n\nThe scope management plan is a subsidiary part of the project management plan.\n\n\n\n- How to prepare a detailed project scope statement\n- How to create a WBS\n- How to maintain and approve the WBS\n- How to obtain formal acceptance of the completed project deliverables\n- How to control requests for changes to the project scope"}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::110", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "5.2 **Planning Scope Management /** 范围管理计划", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 528, "text": "e of the completed project deliverables\n- How to control requests for changes to the project scope\n\nThe PMBOK® Guide, Fifth Edition, describes requirements as “conditions or capabilities that must be met by the project or present in the product, service, or result to satisfy an agreement or other formally imposed specification”\n\n\n\nThe **requirements management plan** documents how project requirements will be analyzed, documented, and managed.\n\n需求管理计划记录了如何分析、记录和管理项目需求。"}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::111", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "5.3 Collecting Requirements / 收集需求/5.3.1 概述", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 399, "text": "For some IT projects, it is helpful to divide requirements development into categories called elicitation, analysis, specification, and validation.\n\n对于某些 IT 项目，将需求开发划分为称为启发、分析、规范和验证的类别会很有帮助。\n\nIt is important to use an iterative approach to defining requirements since they are often unclear early in a project.\n\n使用迭代方法来定义需求很重要，因为它们在项目早期通常不清楚。\n\n"}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::112", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "5.3 Collecting Requirements / 收集需求/5.3.2 收集需求的方法", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 522, "text": "\n\nInterviewing\n\nFocus groups and facilitated workshops\n\nUsing group creativity and decision-making techniques\n\nQuestionnaires and surveys\n\nObservation\n\nPrototyping\n\n**Benchmarking**, or generating ideas by comparing specific project practices or product characteristics to those of other projects or products inside or outside the performing organization, can also be used to collect requirements.\n\n基准测试（bench marking）是通过与执行组织的内部或外部的其他项目或产品进行比较，从而获得具体项目实践或者产品特征的需求思想。"}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::113", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "5.3 Collecting Requirements / 收集需求/5.3.3 阅读分析题", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 468, "text": "Genesys Telecommunications Laboratories uses Accept software, a product planning and innovation management application and winner of the Excellence in Product Management Award from 2006–2008\n\nAccept helps them instill a consistent, repeatable, and predictable process for new product definition and development\n\nThey can define what information comprises a requirement and enforce discipline around that process\n\n"}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::114", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "5.3 Collecting Requirements / 收集需求/5.3.4 需求分析管理", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 301, "text": "A **requirements traceability matrix (RTM)** is a table that lists requirements, various attributes of each requirement, and the status of the requirements to ensure that all requirements are addressed.\n\n需求跟踪矩阵是列出各种需求、需求属性和需求状态的一种表格，以确保所有需求被跟踪。\n\n"}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::115", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "5.4 Defining Scope / 定义范围/5.4.1 概述", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 611, "text": "**Project scope statements** should include at least a product scope description, product user acceptance criteria, and detailed information on all project deliverables. It is also helpful to document other scope-related information, such as the project boundaries, constraints, and assumptions. The project scope statement should also reference supporting documents, such as product specifications.\n\n项目范围声明应至少包括产品范围描述、产品用户验收标准以及有关所有项目可交付结果的详细信息。记录其他与范围相关的信息（例如，项目边界、约束和假设）也很有帮助。项目范围声明还应引用支持文件，例如商品规格。\n\nAs time progresses, the scope of a project should become more clear and specific.\n\n随着时间的推移，项目的范围应该变得更加清晰和具体。"}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::116", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "5.4 Defining Scope / 定义范围/5.4.2 项目章程与项目范围材料", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::117", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "5.5 Creating Work Breakdown Structure (WBS) / 创建工作分解结构", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 684, "text": "A **WBS** is a deliverable-oriented grouping of the work involved in a project that defines the total scope of the project.\n\n**工作分解结构**（WBS）是对项目所涉及的工作面向交付成果的分组，它定义了项目的**全部范围**。\n\nWBS is a foundation document that provides the basis for planning and managing project schedules, costs, resources, and changes\n\nWBS 是项目管理中的基础文档，因为它提供了计划和管理项目进度、成本、资源和变更的基础。\n\n**Decomposition** is subdividing project deliverables into smaller pieces.\n\n**分解**（Decomposition）是把项目可交付成果划分为更小的部分。\n\nA **work package** is a task at the lowest level of the WBS.\n\n一个**工作包**（work package）即为 WBS 最底层的一项任务。\n\nThe **scope baseline** includes the approved project scope statement and its associated WBS and WBS dictionary."}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::118", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "5.5 Creating Work Breakdown Structure (WBS) / 创建工作分解结构", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 556, "text": "aseline** includes the approved project scope statement and its associated WBS and WBS dictionary.\n\n**范围目标计划**（scope baseline）包括已批准的项目范围声明及其关联的 WBS 和 WBS 字典。\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::119", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "5.5 Creating Work Breakdown Structure (WBS) / 创建工作分解结构/5.5.1 制定 WBS（工作分解结构）的方法", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 667, "text": "- **Using guidelines**: Some organizations, like the DOD, provide guidelines for preparing WBSs\n- The **analogy approach**: Review WBSs of similar projects and tailor to your project\n- The **top-down approach**: Start with the largest items of the project and break them down\n- The **bottom-up approach**: Start with the specific tasks and roll them up\n- **Mind-mapping approach**: **Mind mapping** is a technique that uses branches radiating out from a core idea to structure thoughts and ideas\n\n\n\n\n\n"}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::120", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "5.5 Creating Work Breakdown Structure (WBS) / 创建工作分解结构/5.5.2 WBS 字典", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 580, "text": "Many WBS tasks are vague and must be explained more so people know what to do and can estimate how long it will take and what it will cost to do the work.\n\n许多 WBS 的任务都很模糊，都必须要经过解释才会让人们知道要做什么并且估计要完成工作将会花费多久的时间。\n\nA **WBS dictionary** is a document that describes detailed information about each WBS item.\n\nWBS 字典是一个描述 WBS 每项条目详细信息的文件。\n\n\n\nThe **scope baseline** includes the approved project scope statement and its associated WBS and WBS dictionary.\n\n批准的项目范围说明书和与之相关的WBS和WBS字典构成了**范围基线(scope baseline)**。实现项目范围目标的绩效就是基于这样的范围基线。"}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::121", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "5.5 Creating Work Breakdown Structure (WBS) / 创建工作分解结构/5.5.3 创建 WBS 和 WBS 字典的建议", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 647, "text": "- A unit of work should appear at only one place in the WBS.\n- The work content of a WBS item is the sum of the WBS items below it\n- A WBS item is the responsibility of only one individual, even though many people may be working on it\n- The WBS must be consistent with the way in which work is actually going to be performed; it should serve the project team first, and other purposes only if practical\n- Project team members should be involved in developing the WBS to ensure consistency and buy-in\n- Each WBS item must be documented in a WBS dictionary to ensure accurate understanding of the scope of work included and not included in that item"}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::122", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "5.5 Creating Work Breakdown Structure (WBS) / 创建工作分解结构/5.5.3 创建 WBS 和 WBS 字典的建议", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 327, "text": "ionary to ensure accurate understanding of the scope of work included and not included in that item\n- The WBS must be a flexible tool to accommodate inevitable changes while properly maintaining control of the work content in the project according to the scope statement\n\n"}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::123", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "5.6 **Validating Scope / 确认范围**/5.6.1 什么是范围验证", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 493, "text": "It is very difficult to create a good scope statement and WBS for a project.\n\nIt is even more difficult to verify project scope and minimize scope changes.\n\n\n\n**Scope validation** involves formal acceptance of the completed project deliverables.\n\n范围验证（Scope Validation）包括了正式接受已经完成的可交付项目成果。\n\nAcceptance is often achieved by customer inspection and then sign-off on key deliverables.\n\n"}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::124", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "5.6 **Validating Scope / 确认范围**/5.6.2 材料分析", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 644, "text": "A project scope that is too broad and grandiose can cause severe problems\n\nScope creep and an overemphasis on technology for technology’s sake resulted in the bankruptcy of a large pharmaceutical firm, Texas-based FoxMeyer Drug\n\nIn 2001, McDonald’s fast-food chain initiated a project to create an intranet that would connect its headquarters with all of its restaurants to provide detailed operational information in real time. After spending \\$170 million on consultants and initial implementation planning, McDonald’s realized that the project was too much to handle and terminated it\n\n"}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::125", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "5.7 Controlling Scope / 控制范围/5.7.1 控制范围的目标", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 476, "text": "Scope control involves controlling changes to the project scope / 范围控制涉及控制对项目范围的更改\n\nGoals of scope control are to / 范围控制的目标是\n\n- influence the factors that cause scope changes / 影响导致范围变化的因素\n- assure changes are processed according to procedures developed as part of integrated change control, and manage changes when they occur / 确保根据作为集成变更控制一部分开发的程序处理变更，以及在更改发生时对其进行管理\n\n**Variance（偏差）** is the difference between planned and actual performance. / Variance（偏差） 是计划绩效和实际绩效之间的差值。"}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::126", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "5.7 Controlling Scope / 控制范围/5.7.2 防止范围问题的最佳实践", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 663, "text": "1. Keep the scope realistic. Don’t make projects so large that they can’t be completed. Break large projects down into a series of smaller ones\n2. Involve users in project scope management. Assign key users to the project team and give them ownership of requirements definition and scope verification\n3. Use off-the-shelf hardware and software whenever possible. Many IT people enjoy using the latest and greatest technology, but business needs, not technology trends, must take priority\n4. Follow good project management processes. As described in this chapter and others, there are well-defined processes for managing project scope and other aspects of projects"}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::127", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "5.7 Controlling Scope / 控制范围/5.7.2 防止范围问题的最佳实践", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 154, "text": "others, there are well-defined processes for managing project scope and other aspects of projects\n\n"}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::128", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "5.7 Controlling Scope / 控制范围/5.7.3 改善用户输入的建议", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 515, "text": "Develop a good project selection process and insist that sponsors are from the user organization\n\nHave users on the project team in important roles\n\nHave regular meetings with defined agendas, and have users sign off on key deliverables presented at meetings\n\nDeliver something to users and sponsors on a regular basis\n\nDon’t promise to deliver when you know you can’t\n\nCo-locate users with developers\n\n\n\n"}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::129", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "5.7 Controlling Scope / 控制范围/5.7.4 减少不完善并且频繁改动的需求的建议", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 688, "text": "Develop and follow a requirements management process\n\nUse techniques such as prototyping, use case modeling, and JAD to get more user involvement\n\nPut requirements in writing and keep them current\n\nCreate a requirements management database for documenting and controlling requirements\n\nProvide adequate testing and conduct testing throughout the project life cycle\n\nReview changes from a systems perspective\n\n\n\nEmphasize completion dates to help focus on what’s most important\n\nAllocate resources specifically for handling change requests/enhancements like NWA did with ResNet\n\n"}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::130", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "Chapter Summary", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 373, "text": "Project scope management includes the processes required to ensure that the project addresses all the work required, and only the work required, to complete the project successfully\n\nMain processes include\n\n- Define scope management\n- Collect requirements\n- Define scope\n- Create WBS\n- Validate scope\n- Control scope\n\n"}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::131", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "选择题重点题解析", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::132", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "选择题重点题解析/2 解析：", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 124, "text": "\n\n课本原文，答案选 a\n\n"}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::133", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "选择题重点题解析/5 解析：两个版本的层级不同，课本答案为 B", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 169, "text": "\n\n\n\n"}
{"id": "docx::BH7owKCplifpqtk11DAcVyY9nwg::134", "page_id": "docx::BH7owKCplifpqtk11DAcVyY9nwg", "title": "Chapter 05 范围管理 Scope", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 05 范围管理 Scope", "section": "选择题重点题解析/8 解析：", "url": "https://a1npn29y3xu.feishu.cn/wiki/BH7owKCplifpqtk11DAcVyY9nwg", "source_type": "docx", "n_chars": 81, "text": "\n\nVerification 确认，验证，答案选 b"}
{"id": "docx::F3xPwQE88i4Ia1kvUbIcBHfYn8f::135", "page_id": "docx::F3xPwQE88i4Ia1kvUbIcBHfYn8f", "title": "Chapter 06 Interoperability / 第六章：互操作性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 06 Interoperability / 第六章：互操作性", "section": "What is Interoperability? / 什么是互操作性？", "url": "https://a1npn29y3xu.feishu.cn/wiki/F3xPwQE88i4Ia1kvUbIcBHfYn8f", "source_type": "docx", "n_chars": 663, "text": "**Interoperability** is about the degree to which two or more systems can usefully exchange meaningful information via interfaces in a particular context.\n\n互操作性是指两个或多个系统在特定上下文中通过接口有效地交换有意义的信息的程度。\n\nAny discussion of **a system's interoperability** needs to identify with whom, and under what circumstances.\n\n任何关于系统互操作性的讨论都需要明确与谁、以及在什么情况下进行。\n\n**Types of Interoperability / 互操作性的类型**\n\n1. Syntactic interoperability / 语法互操作性\n\n- Definition: The ability to exchange data.\n定义：数据交换的能力。\n\n1. Semantic interoperability / 语义互操作性\n\n- Definition: The ability to interpret the data being exchanged.\n定义：解释交换数据的能力。\n\n**Two Perspectives for Achieving Interoperability / 实现互操作性的两种视角**"}
{"id": "docx::F3xPwQE88i4Ia1kvUbIcBHfYn8f::136", "page_id": "docx::F3xPwQE88i4Ia1kvUbIcBHfYn8f", "title": "Chapter 06 Interoperability / 第六章：互操作性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 06 Interoperability / 第六章：互操作性", "section": "What is Interoperability? / 什么是互操作性？", "url": "https://a1npn29y3xu.feishu.cn/wiki/F3xPwQE88i4Ia1kvUbIcBHfYn8f", "source_type": "docx", "n_chars": 689, "text": "being exchanged.\n定义：解释交换数据的能力。\n\n**Two Perspectives for Achieving Interoperability / 实现互操作性的两种视角**\n\n1. With knowledge about the interfaces of external systems, design that knowledge into the system.\n拥有外部系统接口的知识，将该知识设计到系统中。\n2. Without knowledge about other systems, design the system to interoperate in a more general fashion.\n没有其他系统的知识，设计系统以更通用的方式进行互操作。\n\n**Examples of Systems and Interoperability （Motivation) / 系统及互操作性的例子 （驱动力）**\n\n- The system provides a service to be used by a collection of unknown systems, e.g., Google Maps.\n该系统提供服务供一组未知系统使用，例如Google Maps。\n- The system is constructed from existing systems, for example:\n系统是由现有系统构建的，例如：\n- Producing a representation of what was sensed"}
{"id": "docx::F3xPwQE88i4Ia1kvUbIcBHfYn8f::137", "page_id": "docx::F3xPwQE88i4Ia1kvUbIcBHfYn8f", "title": "Chapter 06 Interoperability / 第六章：互操作性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 06 Interoperability / 第六章：互操作性", "section": "What is Interoperability? / 什么是互操作性？", "url": "https://a1npn29y3xu.feishu.cn/wiki/F3xPwQE88i4Ia1kvUbIcBHfYn8f", "source_type": "docx", "n_chars": 608, "text": "from existing systems, for example:\n系统是由现有系统构建的，例如：\n- Producing a representation of what was sensed\n生成所感知内容的表示\n- Interpreting the data\n解释数据\n- Processing raw data\n处理原始数据\n- Sensing the environment\n感知环境\n\n**Discovery / 服务发现**\n\nThe consumer of a service must discover the location, identity, and interface of the service.\n\n服务的消费者必须发现服务的位置、身份和接口。\n\n**Handling the Response / 处理响应**\n\nThree possibilities:\n\n三种可能性：\n\n1. The service reports back to the requester\n服务向请求者报告\n2. The service sends its response to another system\n服务将其响应发送到另一个系统\n3. The service broadcasts its response to any interested parties\n服务将其响应广播给所有感兴趣的方"}
{"id": "docx::F3xPwQE88i4Ia1kvUbIcBHfYn8f::138", "page_id": "docx::F3xPwQE88i4Ia1kvUbIcBHfYn8f", "title": "Chapter 06 Interoperability / 第六章：互操作性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 06 Interoperability / 第六章：互操作性", "section": "General Scenario", "url": "https://a1npn29y3xu.feishu.cn/wiki/F3xPwQE88i4Ia1kvUbIcBHfYn8f", "source_type": "docx", "n_chars": 698, "text": "Portion of Scenario / 场景中的组成部分Possible Values / 可能的取值Source / 源头A System一个系统Stimulus / 激励A request to exchange information among system(s)系统间交换信息的请求Artifact / 组件The systems to exchange information among system(s)系统间交换信息的系统Environment / 环境System(s) wishing to interoperate are discovered at run time or known prior to run time希望互操作的系统在运行时被发现或在运行之前已知Response / 反馈One or more of the following:以下之一或多个：The request is (appropriately) rejected and appropriate entities (people or systems) are notified.请求被（适当地）拒绝，相关实体（人员或系统）被通知。The request is (appropriately) accepted and information is exchanged successfully.请求被（适当地）接受，信息成功交换。The request is logged by one or more of the involved systems.请求被一个或多个相关系统记录。"}
{"id": "docx::F3xPwQE88i4Ia1kvUbIcBHfYn8f::139", "page_id": "docx::F3xPwQE88i4Ia1kvUbIcBHfYn8f", "title": "Chapter 06 Interoperability / 第六章：互操作性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 06 Interoperability / 第六章：互操作性", "section": "General Scenario", "url": "https://a1npn29y3xu.feishu.cn/wiki/F3xPwQE88i4Ia1kvUbIcBHfYn8f", "source_type": "docx", "n_chars": 281, "text": "fully.请求被（适当地）接受，信息成功交换。The request is logged by one or more of the involved systems.请求被一个或多个相关系统记录。Response Measure / 反馈度量One or more of the following:以下之一或多个：Percentage of information exchanges correctly processed正确信息交换的百分比Percentage of information exchanges rejected被拒绝的信息交换的百分比"}
{"id": "docx::F3xPwQE88i4Ia1kvUbIcBHfYn8f::140", "page_id": "docx::F3xPwQE88i4Ia1kvUbIcBHfYn8f", "title": "Chapter 06 Interoperability / 第六章：互操作性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 06 Interoperability / 第六章：互操作性", "section": "General Scenario/**Sample / 示例**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F3xPwQE88i4Ia1kvUbIcBHfYn8f", "source_type": "docx", "n_chars": 644, "text": "- **Our vehicle information system** sends our current location to the **traffic monitoring system**.\n我们的车辆信息系统将当前位置发送到交通监控系统。\n- The traffic monitoring system combines our location with other information, overlays this information on a Google Map, and **broadcasts** it.\n交通监控系统将我们的位置信息与其他信息结合，并将这些信息叠加在 Google 地图上，然后广播出去。\n- Our location information is correctly included with a probability of 99.9%.\n我们的位置信息正确包含的概率为 99.9%。\n- Analysis / 分析\n- Source: Our vehicle information system / 我们的车辆信息系统\n- Stimulus: A request to exchange information among system(s) / 系统间交换信息的请求\n- Artifact: The systems to exchange information among system(s) / 系统间交换信息的系统"}
{"id": "docx::F3xPwQE88i4Ia1kvUbIcBHfYn8f::141", "page_id": "docx::F3xPwQE88i4Ia1kvUbIcBHfYn8f", "title": "Chapter 06 Interoperability / 第六章：互操作性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 06 Interoperability / 第六章：互操作性", "section": "General Scenario/**Sample / 示例**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F3xPwQE88i4Ia1kvUbIcBHfYn8f", "source_type": "docx", "n_chars": 674, "text": "system(s) / 系统间交换信息的请求\n- Artifact: The systems to exchange information among system(s) / 系统间交换信息的系统\n- Environment: System(s) wishing to interoperate are discovered at run time or known prior to run time / 希望互操作的系统在运行时被发现或在运行之前已知\n- Response: One or more of the following / 以下之一或多个：\n\n1. The request is (appropriately) accepted and information is exchanged successfully / 请求被（适当地）接受，信息成功交换。\n\n- 车辆信息系统将位置信息发送给交通监控系统，并成功完成交换，交通监控系统成功接收并整合这些信息。\n\n1. The request is logged by one or more of the involved systems / 请求被一个或多个相关系统记录。\n\n- 请求的信息交换被系统记录和追踪。\n- Response Measure: One or more of the following / 以下之一或多个：\n\n1. Percentage of information exchanges correctly processed / 正确信息交换的百分比"}
{"id": "docx::F3xPwQE88i4Ia1kvUbIcBHfYn8f::142", "page_id": "docx::F3xPwQE88i4Ia1kvUbIcBHfYn8f", "title": "Chapter 06 Interoperability / 第六章：互操作性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 06 Interoperability / 第六章：互操作性", "section": "General Scenario/**Sample / 示例**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F3xPwQE88i4Ia1kvUbIcBHfYn8f", "source_type": "docx", "n_chars": 584, "text": "the following / 以下之一或多个：\n\n1. Percentage of information exchanges correctly processed / 正确信息交换的百分比\n\n- 在此场景中，99.9% of our location information is correctly included / 我们的位置信息正确包含的概率为 99.9%，即信息交换的正确处理率为 99.9%。\n\n1. Percentage of information exchanges rejected / 被拒绝的信息交换的百分比\n\n- 根据场景，未提及被拒绝的交换，因此可以假设该百分比为 0。\n\n**SOAP vs REST**\n\nTwo technology options to allow the web-based application to interoperate. / 两种技术选项允许基于Web的应用程序进行互操作。\n\nSOAP is used in SOA systems along with a set of protocols: / SOAP在SOA系统中使用，并伴随着一组协议：\n\n- Service description & discovery / 服务描述与发现\n- Service composition / 服务组合"}
{"id": "docx::F3xPwQE88i4Ia1kvUbIcBHfYn8f::143", "page_id": "docx::F3xPwQE88i4Ia1kvUbIcBHfYn8f", "title": "Chapter 06 Interoperability / 第六章：互操作性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 06 Interoperability / 第六章：互操作性", "section": "General Scenario/**Sample / 示例**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F3xPwQE88i4Ia1kvUbIcBHfYn8f", "source_type": "docx", "n_chars": 260, "text": "SOAP在SOA系统中使用，并伴随着一组协议：\n\n- Service description & discovery / 服务描述与发现\n- Service composition / 服务组合\n\nSOAP is more complex and used for exchange messages with structured data, while REST is simple and used for small messages. / SOAP更复杂，用于交换结构化数据的消息，而REST简单，用于小消息。"}
{"id": "docx::F3xPwQE88i4Ia1kvUbIcBHfYn8f::144", "page_id": "docx::F3xPwQE88i4Ia1kvUbIcBHfYn8f", "title": "Chapter 06 Interoperability / 第六章：互操作性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 06 Interoperability / 第六章：互操作性", "section": "Tactics/Goal", "url": "https://a1npn29y3xu.feishu.cn/wiki/F3xPwQE88i4Ia1kvUbIcBHfYn8f", "source_type": "docx", "n_chars": 569, "text": "For two or more systems to usefully exchange information they must / 两个或多个系统要有效地交换信息，它们必须\n\n- Know about each other. That is the purpose behind the **locate** tactics, / 了解彼此。这是**定位**策略背后的目的，\n- Exchange information in a semantically meaningful fashion. That is the purpose behind the **manage interfaces** tactics. / 以语义上有意义的方式交换信息。这是**管理接口**策略背后的目的。Two aspects of the exchange are / 交换的两个方面是\n\n - Provide services in the correct sequence. / 提供正确的服务顺序。\n - Modify information produced by one actor to a form acceptable to the second actor. / 将一个参与者产生的消息修改为第二个参与者可以接受的形式。"}
{"id": "docx::F3xPwQE88i4Ia1kvUbIcBHfYn8f::145", "page_id": "docx::F3xPwQE88i4Ia1kvUbIcBHfYn8f", "title": "Chapter 06 Interoperability / 第六章：互操作性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 06 Interoperability / 第六章：互操作性", "section": "Tactics/省流：多个人共享位置/Locate", "url": "https://a1npn29y3xu.feishu.cn/wiki/F3xPwQE88i4Ia1kvUbIcBHfYn8f", "source_type": "docx", "n_chars": 179, "text": "Service Discovery / 服务发现\n\n- Locate a service through searching\n通过搜索定位服务\n\nThere are many service discovery mechanisms:\n\n有许多服务发现机制：\n\n- UDDI for Web services\n Web服务的 UDDI（统一描述、发现和集成）"}
{"id": "docx::F3xPwQE88i4Ia1kvUbIcBHfYn8f::146", "page_id": "docx::F3xPwQE88i4Ia1kvUbIcBHfYn8f", "title": "Chapter 06 Interoperability / 第六章：互操作性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 06 Interoperability / 第六章：互操作性", "section": "Tactics/省流：多个人共享位置/Locate/**Service Discovery - Necessary Conditions / 服务发现：必要的条件**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F3xPwQE88i4Ia1kvUbIcBHfYn8f", "source_type": "docx", "n_chars": 674, "text": "The searcher wants to find the searched entity and the searched entity **wants to be found.**\n\n搜索者希望找到被搜索的实体，而被搜索的实体希望被找到。\n\nThe searched entity must have **identifiers.**\n\n被搜索的实体必须具有标识符。\n\nThe searcher must acquire **sufficient identifiers** to identify the searched entity.\n\n搜索者必须获取足够的标识符来识别被搜索的实体。\n\n**Searching Method - Searcher's initiative / 搜索方法 - 搜索者的倡议**\n\n**Flood/Broadcast Request / 洪泛/广播请求**\n\n- Ask every entity and wait for an answer / 向每个实体发出请求并等待回答\n- Efficient and less resource consuming for the searcher / 对搜索者来说高效且资源消耗较少\n- Low resource consuming for the searched / 对被搜索者来说资源消耗较少\n- But disturbing and resource consuming for the environment / 但对环境来说，可能会引起干扰并消耗资源"}
{"id": "docx::F3xPwQE88i4Ia1kvUbIcBHfYn8f::147", "page_id": "docx::F3xPwQE88i4Ia1kvUbIcBHfYn8f", "title": "Chapter 06 Interoperability / 第六章：互操作性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 06 Interoperability / 第六章：互操作性", "section": "Tactics/省流：多个人共享位置/Locate/**Service Discovery - Necessary Conditions / 服务发现：必要的条件**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F3xPwQE88i4Ia1kvUbIcBHfYn8f", "source_type": "docx", "n_chars": 620, "text": "/ 对被搜索者来说资源消耗较少\n- But disturbing and resource consuming for the environment / 但对环境来说，可能会引起干扰并消耗资源\n\n**Successive Request / 连续请求**\n\n- Ask one entity at a time and perform matching / 一次请求一个实体并进行匹配\n- If no match, continue with next until finding a match / 如果没有匹配，继续向下一个实体请求，直到找到匹配\n- Less efficient and high resource consuming for the searcher / 对搜索者来说效率较低且资源消耗较高\n- But less disturbing and less resource consuming for the environment / 但对环境来说，干扰较小且资源消耗较少\n\n\n\n**Searching Method - Searched's initiative / 搜索方法 - 被搜索者的倡议**\n\n**Continuous/Periodical Advertisement / 连续/定期广告**"}
{"id": "docx::F3xPwQE88i4Ia1kvUbIcBHfYn8f::148", "page_id": "docx::F3xPwQE88i4Ia1kvUbIcBHfYn8f", "title": "Chapter 06 Interoperability / 第六章：互操作性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 06 Interoperability / 第六章：互操作性", "section": "Tactics/省流：多个人共享位置/Locate/**Service Discovery - Necessary Conditions / 服务发现：必要的条件**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F3xPwQE88i4Ia1kvUbIcBHfYn8f", "source_type": "docx", "n_chars": 656, "text": "thod - Searched's initiative / 搜索方法 - 被搜索者的倡议**\n\n**Continuous/Periodical Advertisement / 连续/定期广告**\n\n- Continuously or periodically publish advertisement such that every searcher can notice and respond / 持续或定期发布广告，使每个搜索者都能注意到并作出响应\n- Efficient but high resource consuming for the searched / 对被搜索者来说高效，但资源消耗较高\n- Low resource demanding for the searcher / 对搜索者来说资源需求较低\n- Disturbing and resource consuming for the environment / 对环境来说干扰较大且资源消耗较多\n\n**Advertisement Upon Arrival of New Entity / 新实体到达时的广告**\n\n- E.g., present himself when a new person enters the lobby / **例如，当新人员进入大厅时，他会主动展示自己**\n- Require detection mechanism upon new entity arrival / 需要在新实体到达时启用检测机制"}
{"id": "docx::F3xPwQE88i4Ia1kvUbIcBHfYn8f::149", "page_id": "docx::F3xPwQE88i4Ia1kvUbIcBHfYn8f", "title": "Chapter 06 Interoperability / 第六章：互操作性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 06 Interoperability / 第六章：互操作性", "section": "Tactics/省流：多个人共享位置/Locate/**Service Discovery - Necessary Conditions / 服务发现：必要的条件**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F3xPwQE88i4Ia1kvUbIcBHfYn8f", "source_type": "docx", "n_chars": 597, "text": "/ **例如，当新人员进入大厅时，他会主动展示自己**\n- Require detection mechanism upon new entity arrival / 需要在新实体到达时启用检测机制\n- Less resource consuming for the searched / 对被搜索者来说资源消耗较少\n- Low resource demanding for the searcher / 对搜索者来说资源需求较低\n- Less disturbing and resource consuming for the environment / 对环境来说干扰较小，资源消耗较少\n\n**Searching Method - Registration / 搜索方法：注册**\n\n**Introduction of the “Middlemen”, Registry / “中介”介绍，注册表**\n\n- The searched entity registers to a registry / 被搜索的实体向注册表注册\n- The searcher can address the registry to get information and find the searched entity / 搜索者可以查询注册表以获取信息并找到被搜索的实体\n\n**Example / 示例**"}
{"id": "docx::F3xPwQE88i4Ia1kvUbIcBHfYn8f::150", "page_id": "docx::F3xPwQE88i4Ia1kvUbIcBHfYn8f", "title": "Chapter 06 Interoperability / 第六章：互操作性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 06 Interoperability / 第六章：互操作性", "section": "Tactics/省流：多个人共享位置/Locate/**Service Discovery - Necessary Conditions / 服务发现：必要的条件**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F3xPwQE88i4Ia1kvUbIcBHfYn8f", "source_type": "docx", "n_chars": 673, "text": "istry to get information and find the searched entity / 搜索者可以查询注册表以获取信息并找到被搜索的实体\n\n**Example / 示例**\n\n- Service providers register their web services at UDDI registry which can be searched and found by Service Requestors / 服务提供者将其Web服务注册到UDDI注册表，服务请求者可以在该注册表中搜索并找到这些服务。\n\n\n\nLess resource consumption on both searchers, searched and less disturbing to the environment, but the registry must be available, reliable, and correct.\n\n对搜索者和被搜索者的资源消耗较少，对环境干扰较小，但注册表必须是可用的、可靠的和正确的。\n\n\n\nWeb Service Architectrue / 网络服务架构\n\nRegistry / 注册表\n\n1. Publish Service Description / 发布服务描述"}
{"id": "docx::F3xPwQE88i4Ia1kvUbIcBHfYn8f::151", "page_id": "docx::F3xPwQE88i4Ia1kvUbIcBHfYn8f", "title": "Chapter 06 Interoperability / 第六章：互操作性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 06 Interoperability / 第六章：互操作性", "section": "Tactics/省流：多个人共享位置/Locate/**Service Discovery - Necessary Conditions / 服务发现：必要的条件**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F3xPwQE88i4Ia1kvUbIcBHfYn8f", "source_type": "docx", "n_chars": 588, "text": "sCnIb)\n\nWeb Service Architectrue / 网络服务架构\n\nRegistry / 注册表\n\n1. Publish Service Description / 发布服务描述\n\n- Web Service Provider / 网络服务提供者\n\n1. Discovery of Suitable Services and How to Communicate with Them / 发现合适的服务及如何与其通信\n\n- Web Service Client / 网络服务客户端\n\n1. Service Invocation / 服务调用\n\n\n\n\n\nUDDI注册表是一个网络，类似于域名系统（DNS）。所有的UDDI注册表之间会交换信息，提供所有注册表中包含的信息。访问一个注册表就可以获取所有注册表中的内容。\n\n这意味着，UDDI注册表的目的是让两个或多个系统能够有用地交换信息，它们必须知道彼此，并且以语义上有意义的方式交换信息。交换的两个方面包括：按正确的顺序提供服务，以及将一个参与者产生的消息修改为第二个参与者可以接受的形式。"}
{"id": "docx::F3xPwQE88i4Ia1kvUbIcBHfYn8f::152", "page_id": "docx::F3xPwQE88i4Ia1kvUbIcBHfYn8f", "title": "Chapter 06 Interoperability / 第六章：互操作性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 06 Interoperability / 第六章：互操作性", "section": "Tactics/省流：多个人共享位置/Manage Interfaces", "url": "https://a1npn29y3xu.feishu.cn/wiki/F3xPwQE88i4Ia1kvUbIcBHfYn8f", "source_type": "docx", "n_chars": 480, "text": "\n\n**Orchestrate / 协调**\n\n- Uses a control mechanism to coordinate, manage, and sequence the invocation of services. / 使用控制机制来协调、管理和按顺序调用服务。\n- Orchestration is used when systems must interact in a complex fashion to accomplish a complex task. / 协调用于当系统必须以复杂的方式相互作用以完成复杂任务时。\n\n**Tailor Interface / 定制接口**\n\n- Add or remove capabilities to an interface such as translation, buffering, or data-smoothing. / 向接口添加或删除功能，如翻译、缓冲或数据平滑处理。"}
{"id": "docx::F3xPwQE88i4Ia1kvUbIcBHfYn8f::153", "page_id": "docx::F3xPwQE88i4Ia1kvUbIcBHfYn8f", "title": "Chapter 06 Interoperability / 第六章：互操作性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 06 Interoperability / 第六章：互操作性", "section": "Summary", "url": "https://a1npn29y3xu.feishu.cn/wiki/F3xPwQE88i4Ia1kvUbIcBHfYn8f", "source_type": "docx", "n_chars": 353, "text": "\n\nInteroperability refers to the ability of systems to usefully exchange information. / 互操作性指的是系统能够有用地交换信息的能力。\n\nAchieving interoperability involves the relevant systems locating each other and then managing the interfaces so that they can exchange information. / 实现互操作性涉及相关系统定位彼此，然后管理接口，以便它们可以交换信息。"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::154", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "序、必考简答题/**1、项目时间管理中的七个主要过程？**", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 604, "text": "计划进度管理\n\n定义活动\n\n排序活动\n\n估算活动资源\n\n估算活动工期\n\n制订进度计划\n\n控制进度\n\n**Planning schedule management:** determining the policies, procedures, and documentation that will be used for planning, executing, and controlling the project schedule\n\n**Defining activities:** identifying the specific activities that the project team members and stakeholders must perform to produce the project deliverables\n\n**Sequencing activities:** identifying and documenting the relationships between project activities\n\n**Estimating activity resources:** estimating how many **resources** a project team should use to perform project activities"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::155", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "序、必考简答题/**1、项目时间管理中的七个主要过程？**", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 462, "text": "urces:** estimating how many **resources** a project team should use to perform project activities\n\n**Estimating activity durations:** estimating the number of work periods that are needed to complete individual activities\n\n**Developing the schedule:** analyzing activity sequences, activity resource estimates, and activity duration estimates to create the project schedule\n\n**Controlling the schedule:** controlling and managing changes to the project schedule"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::156", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "序、必考简答题/**2、一个进度管理计划应该包括哪些信息？**", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 312, "text": "项目进度模型的开发\n\n在开发项目进度模型中使用的方法和工具\n\n精度水平和计量单位\n\n控制阈值\n\n性能测量的规则\n\n报告格式\n\n过程描述\n\nA schedule management plan includes:\n\n- Project schedule model development\n- The scheduling methodology\n- Level of accuracy and units of measure\n- Control thresholds\n- Rules of performance measurement\n- Reporting formats\n- Process descriptions"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::157", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "序、必考简答题/**3、依赖的三种类型**", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 414, "text": "强制依赖\n\n自由依赖\n\n外部依赖\n\n**Mandatory dependencies:** inherent in the nature of the work being performed on a project, sometimes referred to as hard logic\n\n**Discretionary dependencies:** defined by the project team., sometimes referred to as soft logic and should be used with care since they may limit later scheduling options\n\n**External dependencies:** involve relationships between project and non-project activities"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::158", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "序、必考简答题/**4、辅助进度制订过程的工具和技术有哪些？**", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 211, "text": "甘特图\n\n关键路径分析\n\n关键链进度法\n\nPERT分析\n\nImportant tools and techniques include Gantt charts, critical path analysis, and critical chain scheduling, and PERT analysis\n\n"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::159", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "序、必考简答题/**5、SMART准则是怎样定义里程碑的？**", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 81, "text": "Specific 明确的\n\nMeasurable 可度量的\n\nAssignable 可分配的\n\nRealistic 现实的\n\nTime-framed 有时间限制的"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::160", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "序、必考简答题/**6、使用关键路径来缩短项目进度有哪三个主要技术？**", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 98, "text": "**为活动分配更多的资源或者改变它们的范围**\n\n**赶工**\n\n**快速跟进**\n\n"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::161", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "Learning Objectives / 学习目标", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 479, "text": "Understand the importance of project schedules and good project time management\n\nDiscuss the process of planning schedule management\n\nDefine activities as the basis for developing project schedules\n\nDescribe how project managers use network diagrams and dependencies to assist in activity sequencing\n\nUnderstand the relationship between estimating resources and project schedules\n\nExplain how various tools and techniques help project managers perform activity duration estimates"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::162", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "Learning Objectives / 学习目标", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 637, "text": "Explain how various tools and techniques help project managers perform activity duration estimates\n\nUse a Gantt chart for planning and tracking schedule information, find the critical path for a project, and describe how critical chain scheduling and the Program Evaluation and Review Technique (PERT) affect schedule development\n\nDiscuss how reality checks and discipline are involved in controlling and managing changes to the project schedule\n\nDescribe how project management software can assist in project time management and review words of caution before using this software\n\n"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::163", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "6.1 Importance of Project Schedules / 项目计划的重要性/6.1.1 时间管理综述", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 646, "text": "Managers often cite delivering projects on time as one of their biggest challenges.\n\nTime has the least amount of flexibility; it passes no matter what happens on a project.\n\nSchedule issues are the main reason for conflicts on projects, especially during the second half of projects.\n\n管理者经常将按时交付项目作为他们面临的最大挑战之一。\n\n时间的灵活性最小;无论项目发生什么，它都会通过。\n\n进度问题是项目冲突的主要原因，尤其是在项目的后半部分。\n\n**Individual Work Styles and Cultural Differences Cause Schedule Conflicts**\n\nOne dimension of the Meyers-Briggs Type Indicator focuses on peoples’ attitudes toward structure and deadline\n\nSome people prefer to follow schedules and meet deadlines while others do not (J vs. P)"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::164", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "6.1 Importance of Project Schedules / 项目计划的重要性/6.1.1 时间管理综述", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 332, "text": "deadline\n\nSome people prefer to follow schedules and meet deadlines while others do not (J vs. P)\n\nDifferent cultures and even entire countries have different attitudes about schedules\n\n\n\nMBTI 相信大家比我熟悉，笔者是 ENTJ 哦，这里放张图吧\n\n"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::165", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "6.1 Importance of Project Schedules / 项目计划的重要性/6.1.2 时间管理过程", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 678, "text": "**Planning schedule management:** determining the policies, procedures, and documentation that will be used for planning, executing, and controlling the project schedule\n\n**Defining activities:** identifying the specific activities that the project team members and stakeholders must perform to produce the project deliverables\n\n**Sequencing activities:** identifying and documenting the relationships between project activities\n\n**Estimating activity resources:** estimating how many **resources** a project team should use to perform project activities\n\n**Estimating activity durations:** estimating the number of work periods that are needed to complete individual activities"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::166", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "6.1 Importance of Project Schedules / 项目计划的重要性/6.1.2 时间管理过程", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 680, "text": "rations:** estimating the number of work periods that are needed to complete individual activities\n\n**Developing the schedule:** analyzing activity sequences, activity resource estimates, and activity duration estimates to create the project schedule\n\n**Controlling the schedule:** controlling and managing changes to the project schedule\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::167", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "6.2 **Planning Schedule Management / 计划进度管理**", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 462, "text": "The project team uses expert judgment, analytical techniques, and meetings to develop the schedule management plan.\n\n项目团队使用专家判断、分析技术和会议来制定进度管理计划。\n\nA schedule management plan includes: / 一个计划管理计划包括了：\n\n- Project schedule model development\n- The scheduling methodology\n- Level of accuracy and units of measure\n- Control thresholds\n- Rules of performance measurement\n- Reporting formats\n- Process descriptions\n\n"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::168", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "6.3 Defining Activities / 定义活动/6.3.1 什么是活动", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 655, "text": "An **activity** or **task** is an element of work normally found on the work breakdown structure (WBS) that has an expected duration, a cost, and resource requirements\n\nActivity definition involves developing a more detailed WBS and supporting explanations to understand all the work to be done so you can develop realistic cost and duration estimates\n\n活动或任务是工作分解结构 （WBS） 中通常包含的工作元素，具有预期的持续时间、成本和资源要求。\n\n作业定义涉及制定更详细的 WBS 和支持解释，以了解要完成的所有工作，以便您可以制定切合实际的成本和工期估算。\n\nAn **activity list** is a tabulation of activities to be included on a project schedule that includes\n\n- the activity name\n- an activity identifier or number\n- a brief description of the activity"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::169", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "6.3 Defining Activities / 定义活动/6.3.1 什么是活动", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 369, "text": "udes\n\n- the activity name\n- an activity identifier or number\n- a brief description of the activity\n\n**Activity attributes** provide more information such as predecessors, successors, logical relationships, leads and lags, resource requirements, constraints, imposed dates, and assumptions related to the activity\n\n"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::170", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "6.3 Defining Activities / 定义活动/6.3.2 里程碑", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 373, "text": "A **milestone** is a significant event that normally has no duration\n\nIt often takes several activities and a lot of work to complete a milestone\n\nThey’re useful tools for setting schedule goals and monitoring progress\n\nExamples include obtaining customer sign-off on key documents or completion of specific products\n\n"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::171", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "6.4 Sequencing Activities / 排序活动/6.4.1 依赖/6.4.1.1 依赖或关系", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 293, "text": "Involves reviewing activities and determining dependencies / 包括了回顾活动和决定依赖\n\nA **dependency** or **relationship** is the sequencing of project activities or tasks. / 依赖或关系与项目活动或任务的排序相关。\n\nYou ***must determine dependencies*** in order to use **critical path analysis / 必须使用关键路径分析法去决定依赖关系（期末计算题）**"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::172", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "6.4 Sequencing Activities / 排序活动/6.4.1 依赖/6.4.1.2 依赖的三种类型", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 453, "text": "**Mandatory dependencies:** inherent in the nature of the work being performed on a project, sometimes referred to as hard logic\n\n**Discretionary dependencies:** defined by the project team., sometimes referred to as soft logic and should be used with care since they may limit later scheduling options\n\n**External dependencies:** involve relationships between project and non-project activities\n\n"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::173", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "6.4 Sequencing Activities / 排序活动/6.4.2 网络图", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 372, "text": "Network diagrams are the preferred technique for showing activity sequencing\n\nA **network diagram** is a schematic display of the logical relationships among, or sequencing of, project activities\n\nTwo main formats are arrow and precedence diagramming methods\n\n\n\n"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::174", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "6.4 Sequencing Activities / 排序活动/6.4.2 网络图/6.4.2.1 ADM 和 AOA 是等价的", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 283, "text": "Also called activity-on-arrow (AOA) network diagrams / ADM 和 AOA 在此我们暂时认为是等价的\n\nActivities are represented by arrows / 活动通过箭头表示出来\n\nNodes or circles are the starting and ending points of activities / 节点或者圆圈表示活动的起始点和终结点\n\nCan only show finish-to-start dependencies / 这种方法只能展示 结束-开始 的依赖关系"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::175", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "6.4 Sequencing Activities / 排序活动/6.4.2 网络图/6.4.2.2 构造 AOA 图 的流程", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 571, "text": "1. Find all of the activities that start at node 1. Draw their finish nodes and draw arrows between node 1 and those finish nodes. Put the activity letter or name and duration estimate on the associated arrow\n2. Continuing drawing the network diagram, working from left to right. Look for bursts and merges. **Bursts** occur when a single node is followed by two or more activities. A **merge** occurs when two or more nodes precede a single node\n3. Continue drawing the project network diagram until all activities are included in the diagram that have dependencies"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::176", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "6.4 Sequencing Activities / 排序活动/6.4.2 网络图/6.4.2.2 构造 AOA 图 的流程", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 285, "text": "the project network diagram until all activities are included in the diagram that have dependencies\n4. As a **rule of thumb（惯例）**, all arrowheads should face toward the right, and no arrows should cross on an AOA network diagram\n\n"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::177", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "6.4 Sequencing Activities / 排序活动/6.4.2 网络图/6.4.2.3 PDM", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 407, "text": "Activities are represented by boxes / 活动使用箱子进行表示\n\nArrows show relationships between activities / 箭头用于展示活动之间的关系\n\nBetter at showing different types of dependencies / 在展示不同类型的依赖中表现优秀\n\n\n\n\n\n\n\n"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::178", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "6.5 Estimating Activity Resources / 估计活动资源", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 697, "text": "Before estimating activity durations, you must have a good idea of the quantity and type of resources that will be assigned to each activity; **resources** are people, equipment, and materials\n\nConsider important issues in estimating resources\n\n- How difficult will it be to do specific activities on this project?\n- What is the organization’s history in doing similar activities?\n- Are the required resources available?\n\nA **resource breakdown structure** is a hierarchical structure that identifies the project’s resources by category and type.\n\n在估算活动持续时间之前，您必须对分配给每项活动的资源数量和类型有一个很好的了解；资源包括人员、设备和材料\n\n在估算资源时要考虑的重要问题\n\n- 执行此项目的特定活动有多难？\n- 组织在执行类似活动方面的历史是什么？\n- 所需的资源是否可用？\n\n资源分解结构是一种按类别和类型识别项目资源的层次结构。"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::179", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "6.6 Activity Duration Estimating / 估计活动工期/6.6.1 工期和人工量", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 387, "text": "**Duration** includes the actual amount of time worked on an activity *plus* elapsed time / 工期包括活动上花费的实际时间和占用时间。\n\n**Effort** is the number of workdays or work hours required to complete a task / 人工量是完成任务所需要的工作天数或者工作小时数\n\nEffort does not normally equal duration / 人工量通常不等于工期\n\nPeople doing the work should help create estimates, and an expert should review them / 工作的人们应当帮忙创造估计，并且一个专家应当回顾他们"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::180", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "6.6 Activity Duration Estimating / 估计活动工期/6.6.2 三点估计（合并 PERT）/6.6.2.1 什么是三点估计", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 488, "text": "Instead of providing activity estimates as a discrete number, such as four weeks, it’s often helpful to create a **three-point estimate / 三点估计**通常比将活动估计成一个离散的数字更有用\n\n- an estimate that includes an optimistic, most likely, and pessimistic estimate, such as three weeks for the optimistic, four weeks for the most likely, and five weeks for the pessimistic estimate / 三点估计是乐观估计、悲观估计以及常规估计的加权平均\n\nThree-point estimates are needed for PERT and Monte Carlo simulations / PERT 和 蒙特卡洛模拟是三点估计的重要应用"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::181", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "6.6 Activity Duration Estimating / 估计活动工期/6.6.2 三点估计（合并 PERT）/6.6.2.2 三点估计的实际应用：PERT", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 691, "text": "\n\n**PERT** is a network analysis technique used to estimate project duration when there is a high degree of uncertainty about the individual activity duration estimates\n\nPERT uses **probabilistic time estimates**\n\n- duration estimates based on using optimistic, most likely, and pessimistic estimates of activity durations, or a three-point estimate\n\nPERT 是一种网络分析技术，用于在对单个活动持续时间估计存在高度不确定性时估计项目持续时间\n\nPERT 使用概率时间估计\n\n- 基于使用乐观、最可能和悲观的活动持续时间估计或三点估计的持续时间估计\n\n\n\n用一张 **Excel 表解释清楚计算公式**\n\n| | 乐观时间 | 最有可能时间 | 悲观时间 | PERT 估计的时间 |\n|-|-|-|-|-|\n| 时长（单位统一） | A | B | C | ( A + 4 \\* B + C ) / 6 |"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::182", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "6.6 Activity Duration Estimating / 估计活动工期/6.6.2 三点估计（合并 PERT）/6.6.2.3 三点估计的实际应用：蒙特卡洛模拟（第 11 章）", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 651, "text": "Simulation uses a representation or model of a system to analyze the expected behavior or performance of the system\n\n**Monte Carlo analysis** simulates a model’s outcome many times to provide a statistical distribution of the calculated results\n\nTo use a Monte Carlo simulation, you must have three estimates (most likely, pessimistic, and optimistic) plus an estimate of the likelihood of the estimate being between the most likely and optimistic values\n\n1. Assess the range for the variables being considered\n2. Determine the probability distribution of each variable\n3. For each variable, select a random value based on the probability distribution"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::183", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "6.6 Activity Duration Estimating / 估计活动工期/6.6.2 三点估计（合并 PERT）/6.6.2.3 三点估计的实际应用：蒙特卡洛模拟（第 11 章）", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 314, "text": "of each variable\n3. For each variable, select a random value based on the probability distribution\n4. Run a deterministic analysis or one pass through the model\n5. Repeat steps 3 and 4 many times to obtain the probability distribution of the model’s results\n\n"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::184", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "6.7 **Developing the Schedule** / 制定进度", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 487, "text": "Uses results of the other time management processes to determine the start and end date of the project\n\nThe ultimate goal is to create a realistic project schedule that provides a basis for monitoring project progress for the time dimension of the project\n\nImportant tools and techniques include Gantt charts, critical path analysis, and critical chain scheduling, and PERT analysis\n\n使用其他时间管理流程的结果来确定项目的开始和结束日期\n\n最终目标是创建一个切合实际的项目计划，为监控项目时间维度的项目进度提供基础\n\n重要的工具和技术包括甘特图、关键路径分析和关键链调度以及 PERT 分析"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::185", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "6.7 **Developing the Schedule** / 制定进度/6.7.1 甘特图", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 684, "text": "\n\n\n\n\n\n**Gantt charts** provide a standard format for displaying project schedule information by listing project activities and their corresponding start and finish dates in a calendar format / 甘特图通过列出项目活动以及他们日历格式展示的对应开始时间和结束时间来提供标准格式\n\nSymbols include: / 标志包括\n\n- A black diamond: a milestones / 黑色菱形：里程碑\n- Thick black bars: summary tasks / 厚黑条：总结任务\n- Lighter horizontal bars: durations of tasks / 更亮的水平条：任务的持续时间\n- Arrows: dependencies between tasks / 箭头：任务之间的依赖关系\n\n"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::186", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "6.7 **Developing the Schedule** / 制定进度/6.7.1 甘特图", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 155, "text": "dependencies between tasks / 箭头：任务之间的依赖关系\n\n\n\n"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::187", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "6.7 **Developing the Schedule** / 制定进度/6.7.1 甘特图/6.7.1.1 为甘特图添加里程碑", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 557, "text": "Many people like to focus on meeting milestones, especially for large projects / 许多人喜欢专注于实现里程碑，尤其是对于大型项目而言\n\nMilestones emphasize important events or accomplishments on projects / 里程碑强调了项目的重要事件或成就\n\nNormally create milestone by entering tasks with a zero duration, or you can mark any task as a milestone / 通常通过输入持续时间为零的任务来创建里程碑，或者您可以将任何任务标记为里程碑\n\nMilestones should be / 里程碑应当满足以下特征\n\n- **S**pecific / 具体的\n- **M**easurable / 可度量的\n- **A**ssignable / 可分配的\n- **R**ealistic / 切合实际的\n- **T**ime-framed / 有时间限制的\n\n"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::188", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "6.7 **Developing the Schedule** / 制定进度/6.7.1 甘特图/6.7.1.2 跟踪甘特图比较日期", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::189", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "6.7 **Developing the Schedule** / 制定进度/6.7.2 关键路径法（重点！）/6.7.2.1 什么是关键路径法", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 566, "text": "CPM is a network diagramming technique used to predict total project duration\n\nA critical path for a project is the series of activities that determines the earliest time by which the project can be completed\n\nThe critical path is the longest path through the network diagram and has the least amount of slack or float\n\nSlack or float is the amount of time an activity may be delayed without delaying a succeeding activity or the project finish date\n\nCPM 是一种网络图表绘制技术，用于预测项目总工期\n\n项目的关键路径是一系列活动，决定了项目最早完成的时间\n\n关键路径是网络图中最长的路径，具有最少的松弛或浮动\n\n松弛或浮动是活动可以延迟的时间量，而不会延迟后续活动或项目完成日期"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::190", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "6.7 **Developing the Schedule** / 制定进度/6.7.2 关键路径法（重点！）/6.7.2.2 关键路径法的计算（必考！）", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 454, "text": "First develop a good network diagram\n\nAdd the duration estimates for all activities on each path through the network diagram\n\n**The longest path is the critical path（最长的路径就是关键路径）**\n\nIf one or more of the activities on the critical path takes longer than planned, the whole project schedule will slip unless the project manager takes corrective action\n\n首先绘制一个好的网络图\n\n通过网络图添加每条路径上所有活动的持续时间估计\n\n最长的路径是关键路径\n\n如果关键路径上的一项或多项活动花费的时间比计划的要长，除非项目经理采取纠正措施，否则整个项目进度都会延误"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::191", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "6.7 **Developing the Schedule** / 制定进度/6.7.2 关键路径法（重点！）/6.7.2.2 关键路径法的计算（必考！）/例题（期末母题）：请计算该网络图的关键路径", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 159, "text": "\n\nADHJ 1 + 4 + 6 + 3 = 14\n\n**BEHJ 2 + 5 + 6 + 3 = 16 关键路径！**\n\nBFJ 2 + 4 + 3 = 9\n\nCGIJ 3 + 6 + 2 + 3 = 14"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::192", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "6.7 **Developing the Schedule** / 制定进度/6.7.2 关键路径法（重点！）/6.7.2.2 关键路径法的计算（必考！）/注意事项", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 84, "text": "**① 关键路径并不是包含所有关键活动的路径；它只考虑时间**\n\n② 如果两条或多条路径的长度相同，则可以有一条以上的关键路径\n\n③ 关键路径可能会随着项目的进展而改变"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::193", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "6.7 **Developing the Schedule** / 制定进度/6.7.2 关键路径法（重点！）/6.7.2.2 关键路径法的计算（必考！）/美式幽默：在关键路径种草", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::194", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "6.7 **Developing the Schedule** / 制定进度/6.7.2 关键路径法（重点！）/6.7.2.3 浮动时间的计算", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 696, "text": "Free slack or free float is the amount of time an activity can be delayed without delaying the early start of any immediately following activities\n\nTotal slack or total float is the amount of time an activity may be delayed from its early start without delaying the planned project finish date\n\nA forward pass through the network diagram determines the early start and finish dates\n\nA backward pass determines the late start and finish dates\n\n自由时差或自由浮动是指一项活动可以延迟的时间量，而不会延迟任何紧随其后的活动的最早开始时间\n\n总时差或总浮动是指一项活动可以从最早开始时间推迟的时间量，而不会延迟计划的项目完成日期\n\n通过网络图**向前传递可确定最早开始和结束日期**\n\n**向后传递可确定最晚开始和结束日期**\n\n\n\n"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::195", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "6.7 **Developing the Schedule** / 制定进度/6.7.2 关键路径法（重点！）/6.7.2.3 浮动时间的计算", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 388, "text": "ishu.cn/file/X2bFbazsZoY5ElxTs2icgJtcnDd)\n\n\n\n**总时差（总浮动时间）= LS - ES = LF - EF**\n\n**（一项工作不影响总工期的前提下所具有的动机时间）**\n\n**自由浮动=min（ 随后活动的ES - 当前活动的EF ）**\n\n**（一项工作不影响后续工作的情况下拥有的动机时间）**\n\n **Free Float 是 min {后继所有节点的ES - 当前活动的 EF }，Total Float 是不是 LS - ES**\n\n**关键活动（关键路径上的活动）的总时差，自由时差都是0**\n\n"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::196", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "6.7 **Developing the Schedule** / 制定进度/6.7.2 关键路径法（重点！）/6.7.2.4 使用关键路径法缩短项目时间", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 131, "text": "\n\n快速并行执行的官方翻译是：快速跟进\n\n"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::197", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "6.7 **Developing the Schedule** / 制定进度/6.7.3 关键链调度", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 653, "text": "**Critical chain scheduling**\n\n- a method of scheduling that considers limited resources when creating a project schedule and includes buffers to protect the project completion date\n\nUses the **Theory of Constraints** **(TOC)**\n\n- a management philosophy developed by Eliyahu M. Goldratt and introduced in his book *The Goal*.\n\n\n\nAttempts to minimize **multitasking**\n\n- when a resource works on more than one task at a time\n\n\n\nA **buffer** is additional time to complete a task\n\n**Murphy’s Law** states that if something can go wrong, it will"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::198", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "6.7 **Developing the Schedule** / 制定进度/6.7.3 关键链调度", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 627, "text": "dditional time to complete a task\n\n**Murphy’s Law** states that if something can go wrong, it will\n\n**Parkinson’s Law** states that work expands to fill the time allowed\n\nIn traditional estimates, people often add a buffer to each task and use it if it’s needed or not\n\nCritical chain scheduling removes buffers from individual tasks and instead creates\n\n- a **project buffer** or additional time added before the project’s due date\n- **feeding buffers** or additional time added before tasks on the critical path\n\n\n\n"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::199", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "6.8 Controlling the Schedule / 进度控制", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 658, "text": "Goals are to know the status of the schedule, influence factors that cause schedule changes, determine that the schedule has changed, and manage changes when they occur\n\nTools and techniques include\n\n- Progress reports\n- A schedule change control system\n- Project management software, including schedule comparison charts like the tracking Gantt chart\n- Variance analysis, such as analyzing float or slack\n- Performance management, such as earned value (chapter 7)\n\n\n\n**Reality Checks on Scheduling / 进度的现实性检查和纪律的必要性**\n\nFirst review the draft schedule or estimated completion date in the project charter"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::200", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "6.8 Controlling the Schedule / 进度控制", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 349, "text": "实性检查和纪律的必要性**\n\nFirst review the draft schedule or estimated completion date in the project charter\n\nPrepare a more detailed schedule with the project team\n\nMake sure the schedule is realistic and followed\n\nAlert top management well in advance if there are schedule problems\n\n首先审查项目章程中的计划草案或预计完成日期\n\n与项目团队一起准备更详细的计划\n\n确保计划切实可行且可遵循\n\n如果出现计划问题，请提前通知高层管理人员"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::201", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "Chapter Summary", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 374, "text": "Project time management is often cited as the main source of conflict on projects, and most IT projects exceed time estimates\n\nMain processes include\n\n- Plan schedule management\n- Define activities\n- Sequence activities\n- Estimate activity resources\n- Estimate activity durations\n- Develop schedule\n- Control schedule\n\n"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::202", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "选择题重点题解析：/2.前导活动、后继活动、逻辑关系、提前和滞后、资源需求、约束、强制日期，以及假设都是\\_\\_\\_的例子。", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 40, "text": "A.活动列表项\n\n B.项目甘特图项\n\n C.里程碑属性\n\n D.活动属性"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::203", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "选择题重点题解析：/2 解析：", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::204", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "选择题重点题解析：/3 解析", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::205", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "选择题重点题解析：/6.在甘特图上什么符号表示一个偏移的里程碑？", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 30, "text": "A.黑色箭头 B.白色箭头 C.黑色菱形 D.白色菱形"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::206", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "选择题重点题解析：/6 解析：", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 226, "text": "\n\n\n\n\n\n"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::207", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "选择题重点题解析：/9.下面哪种说法是错误的？", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 106, "text": "A.在一个大型主题公园的关键路径上种草\n\nB.关键路径是确定活动最早完成时间的活动序列\n\nC.通过网络图确定每个活动的最早开始时间和最早完成时间\n\nD.快速跟进是一种权衡成本和进度以最小的成本获取最大的进度的技术"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::208", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "选择题重点题解析：/9 解析：", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 101, "text": "B：关键路径通过 **计算网络图的最长路径** 确定活动的 **最早完成时间**\n\nD：\n\n"}
{"id": "docx::Lst8w154eikHvTkhnb8cEoAxnad::209", "page_id": "docx::Lst8w154eikHvTkhnb8cEoAxnad", "title": "Chapter 06 时间管理 Time", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 06 时间管理 Time", "section": "计算题重点题解析：", "url": "https://a1npn29y3xu.feishu.cn/wiki/Lst8w154eikHvTkhnb8cEoAxnad", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe::210", "page_id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe", "title": "Chapter 07 Modifiability / 第七章：可修改性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 07 Modifiability / 第七章：可修改性", "section": "What is Modifiability? / 什么是可修改性？", "url": "https://a1npn29y3xu.feishu.cn/wiki/JuqxwtMmuiLyffkG8HCcxxetnGe", "source_type": "docx", "n_chars": 544, "text": "**Modifiablity** is about change and our interest in it is in the cost and risk of making changes. / **可修改性**是关于变化的，我们对它的兴趣在于做出改变的成本和风险。\n\nTo plan for modifiability, an architect has to consider 4 questions: / 为了执行可修改的计划，一个架构师需要考虑以下四个问题：\n\n- What can change？ / 什么可以改变？\n- What is the likelihood of the change? / 改变的可能性是什么？\n- When is the change made and who makes it? / 什么时候改变发生了，谁导致改变发生？\n- What is the cost of the change? / 什么是改变的花销？\n\n\n\n"}
{"id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe::211", "page_id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe", "title": "Chapter 07 Modifiability / 第七章：可修改性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 07 Modifiability / 第七章：可修改性", "section": "What is Modifiability? / 什么是可修改性？/What can change? / 什么可以改变？", "url": "https://a1npn29y3xu.feishu.cn/wiki/JuqxwtMmuiLyffkG8HCcxxetnGe", "source_type": "docx", "n_chars": 392, "text": "① The functions of the system / 系统的功能\n\n② The platforms, i.e., the hardware, operating system, middle-ware / 平台，即硬件、操作系统、中间件\n\n③ The environment in which the system operates / 系统运行的环境\n\n- The systems with which it must interoperate / 必须与之互操作的系统\n- The protocols it use to communicate / 用于通信的协议\n\n④ The capacity / 容量\n\n-Number of users supported / 支持的用户数量\n\n-Number of simultaneous operations / 同时操作数"}
{"id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe::212", "page_id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe", "title": "Chapter 07 Modifiability / 第七章：可修改性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 07 Modifiability / 第七章：可修改性", "section": "What is Modifiability? / 什么是可修改性？/When is the change made and who makes it? / 什么时候改变发生，谁导致了改变发生？", "url": "https://a1npn29y3xu.feishu.cn/wiki/JuqxwtMmuiLyffkG8HCcxxetnGe", "source_type": "docx", "n_chars": 559, "text": "- Changes can be made during / 改变可能在以下情景下发生\n\n - Implementation by modifying the source code / 通过更改源代码实现\n - Build by choice of libraries / 通过选择库构建\n - Execution by parameter setting, plugins, etc. / 参数的设置、插件的执行等\n- Changes can also be made by / 改变也有可能因为以下人员发生\n\n - A developer / 一个开发者\n - An end user / 一个终端用户\n - A System Administrator / 一个系统管理员\n- Involving 2 types of cost / 包括两种类型的损失\n\n - The cost of introducing the mechanisms to make the system more modifiable / 引入机制以使系统更易于修改的成本\n - The cost of making the modification using the mechanisms / 使用机制进行修改的成本"}
{"id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe::213", "page_id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe", "title": "Chapter 07 Modifiability / 第七章：可修改性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 07 Modifiability / 第七章：可修改性", "section": "General Scenario / 通用场景", "url": "https://a1npn29y3xu.feishu.cn/wiki/JuqxwtMmuiLyffkG8HCcxxetnGe", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe::214", "page_id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe", "title": "Chapter 07 Modifiability / 第七章：可修改性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 07 Modifiability / 第七章：可修改性", "section": "General Scenario / 通用场景/Sample **/ 示例**", "url": "https://a1npn29y3xu.feishu.cn/wiki/JuqxwtMmuiLyffkG8HCcxxetnGe", "source_type": "docx", "n_chars": 449, "text": "The developer wishes to change the user interface by modifying the code at design time. The modifications are made with no side effects within three hours.\n\n开发者希望通过在设计时修改代码来更改用户界面。修改在三小时内完成，并且没有副作用。\n\n- Stimulus / 刺激: Wishes to change UI\n\n 希望更改用户界面\n\n- Artifact / 工件: Code\n\n 代码\n\n- Environment / 环境: Design time\n设计时\n- Response / 响应: Change made\n已完成更改\n- Response measure / 响应度量: No side effects in three hours\n三小时内无副作用\n- Source / 来源: Developer\n开发者"}
{"id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe::215", "page_id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe", "title": "Chapter 07 Modifiability / 第七章：可修改性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 07 Modifiability / 第七章：可修改性", "section": "Tactics/Goal", "url": "https://a1npn29y3xu.feishu.cn/wiki/JuqxwtMmuiLyffkG8HCcxxetnGe", "source_type": "docx", "n_chars": 122, "text": "- Controlling the complexity of making changes / 控制进行更改的复杂性\n- Controlling the time and cost to make changes / 控制进行更改的时间和成本"}
{"id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe::216", "page_id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe", "title": "Chapter 07 Modifiability / 第七章：可修改性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 07 Modifiability / 第七章：可修改性", "section": "Tactics/Tatics Tree", "url": "https://a1npn29y3xu.feishu.cn/wiki/JuqxwtMmuiLyffkG8HCcxxetnGe", "source_type": "docx", "n_chars": 74, "text": "分而治之、高内聚、低耦合、延迟绑定\n\n"}
{"id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe::217", "page_id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe", "title": "Chapter 07 Modifiability / 第七章：可修改性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 07 Modifiability / 第七章：可修改性", "section": "Tactics/Tatics Tree/Reduce Size of a Module / 减少模块大小", "url": "https://a1npn29y3xu.feishu.cn/wiki/JuqxwtMmuiLyffkG8HCcxxetnGe", "source_type": "docx", "n_chars": 299, "text": "• **Split Module**: If the module being modified includes a great deal of capability, the modification costs will likely be high.\n\n• 拆分模块：如果被修改的模块包含大量功能，则修改成本可能会很高。\n\n• Refining the module into several smaller modules should reduce the average cost of future changes.\n\n• 将模块细化为几个较小的模块应该可以降低未来更改的平均成本。"}
{"id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe::218", "page_id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe", "title": "Chapter 07 Modifiability / 第七章：可修改性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 07 Modifiability / 第七章：可修改性", "section": "Tactics/Tatics Tree/Increase Cohension / 增加内聚", "url": "https://a1npn29y3xu.feishu.cn/wiki/JuqxwtMmuiLyffkG8HCcxxetnGe", "source_type": "docx", "n_chars": 395, "text": "\n\n① **Increase Semantic Coherence**: If the responsibilities A and B in a module do not serve the same purpose, they should be placed in different modules.\n\n增加语义连贯性：如果模块中的职责 A 和 B 没有达到相同的目的，则应将它们放在不同的模块中。\n\n② This may involve creating a new module or it may involve moving a responsibility to an existing module.\n\n这可能涉及创建新模块，也可能涉及将责任转移到现有模块。"}
{"id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe::219", "page_id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe", "title": "Chapter 07 Modifiability / 第七章：可修改性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 07 Modifiability / 第七章：可修改性", "section": "Tactics/Tatics Tree/Reducing Coupling / 减小耦合", "url": "https://a1npn29y3xu.feishu.cn/wiki/JuqxwtMmuiLyffkG8HCcxxetnGe", "source_type": "docx", "n_chars": 614, "text": "\n\n① What is coupling? / 什么是耦合？\n\n② If two modules’ responsibilities overlap, a single change may affect them both. / 如果两个模块的职责重叠，则单个更改可能会影响这两个模块\n\n③ Coupling is measured by this overlap, i.e., by the probability that a modification to one module will propagate to the other. / 耦合是通过这种重叠来衡量的，即对一个模块的修改传播到另一个模块的概率\n\n④ High coupling is an enemy of modifiability. / 高耦合是可修改性的敌人\n\n• **Encapsulate**: Encapsulation introduces an explicit interface to a module. This interface includes an API and its associated responsibilities. / 封装引入了一个明显的接口给模块，这个接口引入了 API 以及与之相关的职责。"}
{"id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe::220", "page_id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe", "title": "Chapter 07 Modifiability / 第七章：可修改性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 07 Modifiability / 第七章：可修改性", "section": "Tactics/Tatics Tree/Reducing Coupling / 减小耦合", "url": "https://a1npn29y3xu.feishu.cn/wiki/JuqxwtMmuiLyffkG8HCcxxetnGe", "source_type": "docx", "n_chars": 627, "text": "face includes an API and its associated responsibilities. / 封装引入了一个明显的接口给模块，这个接口引入了 API 以及与之相关的职责。\n\n• **Use an Intermediary**: Given a dependency between responsibility A and responsibility B (for example, carrying out A first requires carrying out B), the dependency can be broken by using an intermediary. / 使用中间件：给定责任 A 和责任 B 之间的依赖关系（例如，首先执行 A 需要执行 B），可以使用中介来打破依赖关系。\n\n\n\n- **Restrict Dependencies**: restricts the modules which a given module interacts with or depends on. / 限制依赖：限制给定模块与之交互或依赖的模块。By restricting a module’s visibility and by authorization / 通过限制模块的可见性和授权"}
{"id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe::221", "page_id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe", "title": "Chapter 07 Modifiability / 第七章：可修改性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 07 Modifiability / 第七章：可修改性", "section": "Tactics/Tatics Tree/Reducing Coupling / 减小耦合", "url": "https://a1npn29y3xu.feishu.cn/wiki/JuqxwtMmuiLyffkG8HCcxxetnGe", "source_type": "docx", "n_chars": 562, "text": "/ 限制依赖：限制给定模块与之交互或依赖的模块。By restricting a module’s visibility and by authorization / 通过限制模块的可见性和授权\n\n For example, a layer is allowed to see the modules in its bottom layer. / 举例，允许一个层查看其底层的模块\n\n- **Abstract Common Services**: where two modules provide not-quite-the-same but similar services, it may be cost-effective to implement the services just once in a more general (abstract) form. / 抽象通用服务：当两个模块提供不完全相同但相似的服务时，以更通用的（抽象的）形式仅实现一次服务可能具有成本效益。\n\n\n\n"}
{"id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe::222", "page_id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe", "title": "Chapter 07 Modifiability / 第七章：可修改性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 07 Modifiability / 第七章：可修改性", "section": "Tactics/Publish / Subscribe System / 发布/订阅系统", "url": "https://a1npn29y3xu.feishu.cn/wiki/JuqxwtMmuiLyffkG8HCcxxetnGe", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe::223", "page_id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe", "title": "Chapter 07 Modifiability / 第七章：可修改性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 07 Modifiability / 第七章：可修改性", "section": "Tactics/Publish / Subscribe System / 发布/订阅系统/**Publish-Subscribe Pattern / 发布-订阅模式**", "url": "https://a1npn29y3xu.feishu.cn/wiki/JuqxwtMmuiLyffkG8HCcxxetnGe", "source_type": "docx", "n_chars": 625, "text": "Problem: To transmit messages among the producers and consumers so they are unaware of each other's identity, or even their existence? / 问题：如何在生产者和消费者之间传递消息，使它们互不知晓对方的身份，甚至是存在？\n\n**Advantages of Pub/Sub / 发布-订阅的优点**\n\n- Highly suited for mobile applications, ubiquitous computing and distributed embedded systems. / 非常适合用于移动应用、普适计算和分布式嵌入式系统。\n- Robust - Failure of publishers or subscribers does not bring down the entire system. / 强健性 - 发布者或订阅者的失败不会导致整个系统崩溃。\n- Scalability - Suited to build distributed applications consisting of a large number of entities. / 可扩展性 - 适用于构建由大量实体组成的分布式应用。\n\n**Disadvantages of Pub/Sub / 发布-订阅的缺点**"}
{"id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe::224", "page_id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe", "title": "Chapter 07 Modifiability / 第七章：可修改性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 07 Modifiability / 第七章：可修改性", "section": "Tactics/Publish / Subscribe System / 发布/订阅系统/**Publish-Subscribe Pattern / 发布-订阅模式**", "url": "https://a1npn29y3xu.feishu.cn/wiki/JuqxwtMmuiLyffkG8HCcxxetnGe", "source_type": "docx", "n_chars": 496, "text": "a large number of entities. / 可扩展性 - 适用于构建由大量实体组成的分布式应用。\n\n**Disadvantages of Pub/Sub / 发布-订阅的缺点**\n\n- Reliability - No strong guarantee on broker to deliver content to subscriber. After a publisher publishes the event, it assumes that all corresponding subscribers will receive it. / 可靠性 - 经纪人无法强有力地保证将内容传递给订阅者。在发布者发布事件后，它假设所有相关订阅者都会接收到事件。\n- Potential bottleneck in brokers when subscribers and publishers overload them. (Solve by load balancing techniques) / 当订阅者和发布者过载时，经纪人可能成为潜在的瓶颈。（通过负载均衡技术解决）"}
{"id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe::225", "page_id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe", "title": "Chapter 07 Modifiability / 第七章：可修改性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 07 Modifiability / 第七章：可修改性", "section": "Tactics/Publish / Subscribe System / 发布/订阅系统/**Introduction: Motivations for Pub/Sub mode / 引言：发布-订阅模式的动机**", "url": "https://a1npn29y3xu.feishu.cn/wiki/JuqxwtMmuiLyffkG8HCcxxetnGe", "source_type": "docx", "n_chars": 575, "text": "**Traditional Client/Server communication mode / 传统的客户端/服务器通信模式**\n\n(Employs RPC, message queue etc.) / （使用RPC、消息队列等）\n\n- Synchronous, tightly-coupled request invocations. / 同步的、紧耦合的请求调用。\n- Very restrictive for distributed applications, especially for WAN and mobile environments. / 对于分布式应用，尤其是在广域网和移动环境中，非常有限制。\n- When nodes/links fail, the system is affected. Fault tolerance must be built in to support this. / 当节点/链路发生故障时，系统会受到影响，必须构建容错机制来支持此情况。\n\n**Require a more flexible and de-coupled communication style that offers asynchronous mechanisms. / 需要一种更灵活、更松耦合的通信方式，提供异步机制。**"}
{"id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe::226", "page_id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe", "title": "Chapter 07 Modifiability / 第七章：可修改性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 07 Modifiability / 第七章：可修改性", "section": "Tactics/Publish / Subscribe System / 发布/订阅系统/**What is a Publish/Subscribe System? / 什么是发布/订阅系统？**", "url": "https://a1npn29y3xu.feishu.cn/wiki/JuqxwtMmuiLyffkG8HCcxxetnGe", "source_type": "docx", "n_chars": 407, "text": "- **Pub/Sub System** is a communication paradigm that allows freedom in the (distributed) system by the decoupling of communication entities in terms of time, space, and synchronization. / 发布/订阅系统是一种通信范式，通过在时间、空间和同步方面解耦通信实体，为（分布式）系统提供灵活性。\n- An event service system that is asynchronous, anonymous, and loosely coupled. / 一个异步、匿名和松耦合的事件服务系统。\n- Ability to quickly adapt to a dynamic environment. / 能够快速适应动态环境。"}
{"id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe::227", "page_id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe", "title": "Chapter 07 Modifiability / 第七章：可修改性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 07 Modifiability / 第七章：可修改性", "section": "Tactics/Publish / Subscribe System / 发布/订阅系统/**Key components of Pub/Sub System / 发布/订阅系统的关键组件**", "url": "https://a1npn29y3xu.feishu.cn/wiki/JuqxwtMmuiLyffkG8HCcxxetnGe", "source_type": "docx", "n_chars": 614, "text": "- **Publishers:** Publishers generate event data and publish them. / 发布者：发布者生成事件数据并将其发布。\n- **Subscribers:** Subscribers submit their subscriptions and process the events received. / 订阅者：订阅者提交订阅并处理接收到的事件。\n- **P/S service:** It's the mediator/broker that filters and routes events from publishers to interested subscribers. / 发布/订阅服务：它是中介/经纪人，负责过滤并将事件从发布者路由到感兴趣的订阅者。\n\n\n\n**Provides decoupling in time, space and synchronization.**\n\n提供时间、空间和同步方面的解耦。\n\n\n\n"}
{"id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe::228", "page_id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe", "title": "Chapter 07 Modifiability / 第七章：可修改性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 07 Modifiability / 第七章：可修改性", "section": "Tactics/Publish / Subscribe System / 发布/订阅系统/**Classification of Pub/Sub Architectures / 发布/订阅架构的分类**/**Centralized Broker mode / 集中式经纪人模式**", "url": "https://a1npn29y3xu.feishu.cn/wiki/JuqxwtMmuiLyffkG8HCcxxetnGe", "source_type": "docx", "n_chars": 386, "text": "- Consists of multiple publishers and multiple subscribers and centralized broker/brokers (an overlay network of brokers interacting with each other). / 包含多个发布者和多个订阅者，以及一个或多个集中式经纪人（经纪人之间相互交互的叠加网络）。\n- Subscribers/Publishers will contact 1 broker and do not need to have knowledge about others. / 订阅者/发布者将联系一个经纪人，并不需要了解其他经纪人。\n- E.g. CORBA event services, JMS etc... / 例如，CORBA 事件服务、JMS 等。"}
{"id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe::229", "page_id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe", "title": "Chapter 07 Modifiability / 第七章：可修改性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 07 Modifiability / 第七章：可修改性", "section": "Tactics/Publish / Subscribe System / 发布/订阅系统/**Classification of Pub/Sub Architectures / 发布/订阅架构的分类**/P2P Model", "url": "https://a1npn29y3xu.feishu.cn/wiki/JuqxwtMmuiLyffkG8HCcxxetnGe", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe::230", "page_id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe", "title": "Chapter 07 Modifiability / 第七章：可修改性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 07 Modifiability / 第七章：可修改性", "section": "Tactics/Publish / Subscribe System / 发布/订阅系统/Key Functions Implemented by P/S Middleware Service / 由订阅者-发布者中间件服务实现的核心函数", "url": "https://a1npn29y3xu.feishu.cn/wiki/JuqxwtMmuiLyffkG8HCcxxetnGe", "source_type": "docx", "n_chars": 495, "text": "\n\n**Event filtering (event selection) / 事件过滤（事件选择）**\n\n- The process of selecting the set of subscribers that have shown interest in a given event. / 选择对给定事件表示兴趣的订阅者集的过程。\n- Subscriptions are stored in memory and searched when a publisher publishes a new event. / 订阅信息存储在内存中，在发布者发布新事件时进行检索。\n\n**Event routing (event delivery) / 事件路由（事件传递）**\n\n- The process of routing the published events to all interested subscribers. / 将发布的事件路由到所有感兴趣的订阅者的过程。"}
{"id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe::231", "page_id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe", "title": "Chapter 07 Modifiability / 第七章：可修改性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 07 Modifiability / 第七章：可修改性", "section": "Tactics/Publish / Subscribe System / 发布/订阅系统/Key Functions Implemented by P/S Middleware Service / 由订阅者-发布者中间件服务实现的核心函数/**Event Filtering (Subscription Model) / 事件过滤（订阅模型）**/**Topic based VS Content based / 基于主题 vs 基于内容**/**Topic based / 基于主题**", "url": "https://a1npn29y3xu.feishu.cn/wiki/JuqxwtMmuiLyffkG8HCcxxetnGe", "source_type": "docx", "n_chars": 461, "text": "- Generally also known as topic based, group based, or channel based event filtering. / 通常也被称为基于主题、基于组或基于频道的事件过滤。\n- Each event is published to one of these channels by its publisher. / 每个事件由发布者发布到这些频道之一。\n- Subscribers subscribe to a particular channel and will receive ALL events published to the subscribed channel. / 订阅者订阅特定的频道，并将接收到发布到该频道的所有事件。\n\n\n\n"}
{"id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe::232", "page_id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe", "title": "Chapter 07 Modifiability / 第七章：可修改性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 07 Modifiability / 第七章：可修改性", "section": "Tactics/Publish / Subscribe System / 发布/订阅系统/Key Functions Implemented by P/S Middleware Service / 由订阅者-发布者中间件服务实现的核心函数/**Event Filtering (Subscription Model) / 事件过滤（订阅模型）**/**Topic based VS Content based / 基于主题 vs 基于内容**/**Content-based Subscription / 基于内容的订阅**", "url": "https://a1npn29y3xu.feishu.cn/wiki/JuqxwtMmuiLyffkG8HCcxxetnGe", "source_type": "docx", "n_chars": 340, "text": "\n\n\n\n- Added complexity in matching an event to subscriptions. / 在将事件与订阅匹配时增加了复杂性。\n- However, more precision is provided and event routing is easier. / 然而，提供了更高的精确度，事件路由也更容易。\n\n"}
{"id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe::233", "page_id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe", "title": "Chapter 07 Modifiability / 第七章：可修改性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 07 Modifiability / 第七章：可修改性", "section": "Tactics/Publish / Subscribe System / 发布/订阅系统/Key Functions Implemented by P/S Middleware Service / 由订阅者-发布者中间件服务实现的核心函数/**Event Filtering (Subscription Model) / 事件过滤（订阅模型）**/**Advantages of Pub/Sub / 发布/订阅的优点**", "url": "https://a1npn29y3xu.feishu.cn/wiki/JuqxwtMmuiLyffkG8HCcxxetnGe", "source_type": "docx", "n_chars": 522, "text": "- Highly suited for mobile applications, ubiquitous computing, and distributed embedded systems. / 非常适合用于移动应用、普适计算和分布式嵌入式系统。\n- Robust - Failure of publishers or subscribers does not bring down the entire system. / 强健性 - 发布者或订阅者的失败不会导致整个系统崩溃。\n- Scalability - Suited to build distributed applications consisting of a large number of entities. / 可扩展性 - 适用于构建由大量实体组成的分布式应用。\n- Adaptability - Can be varied to suit different environments (mobile, internet games, embedded systems, etc.). / 适应性 - 可以根据不同的环境（如移动、互联网游戏、嵌入式系统等）进行调整。"}
{"id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe::234", "page_id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe", "title": "Chapter 07 Modifiability / 第七章：可修改性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 07 Modifiability / 第七章：可修改性", "section": "Tactics/Publish / Subscribe System / 发布/订阅系统/Key Functions Implemented by P/S Middleware Service / 由订阅者-发布者中间件服务实现的核心函数/**Event Filtering (Subscription Model) / 事件过滤（订阅模型）**/**Disadvantages of Pub/Sub / 发布/订阅的缺点**", "url": "https://a1npn29y3xu.feishu.cn/wiki/JuqxwtMmuiLyffkG8HCcxxetnGe", "source_type": "docx", "n_chars": 397, "text": "- Reliability - No strong guarantee on broker to deliver content to subscriber. After a publisher publishes the event, it assumes that all corresponding subscribers will receive it. / 可靠性 - 经纪人无法强有力地保证将内容传递给订阅者。在发布者发布事件后，它假设所有相关订阅者都会接收到事件。\n- Potential bottleneck in brokers when subscribers and publishers overload them. (Solve by load balancing techniques) / 当订阅者和发布者过载时，经纪人可能成为潜在的瓶颈。（通过负载均衡技术解决）"}
{"id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe::235", "page_id": "docx::JuqxwtMmuiLyffkG8HCcxxetnGe", "title": "Chapter 07 Modifiability / 第七章：可修改性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 07 Modifiability / 第七章：可修改性", "section": "Summary", "url": "https://a1npn29y3xu.feishu.cn/wiki/JuqxwtMmuiLyffkG8HCcxxetnGe", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::WtvKwmF3HiKMoakC61XcldQinlc::236", "page_id": "docx::WtvKwmF3HiKMoakC61XcldQinlc", "title": "Chapter 07 成本管理 Cost", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 07 成本管理 Cost", "section": "序、必考简答题/**1、项目成本管理的4个过程**", "url": "https://a1npn29y3xu.feishu.cn/wiki/WtvKwmF3HiKMoakC61XcldQinlc", "source_type": "docx", "n_chars": 529, "text": "**计划成本管理**\n\n**成本估算**\n\n**确定预算**\n\n**成本控制**\n\n**Planning cost management** :determining the policies, procedures, and documentation that will be used for planning, executing, and controlling project cost.\n\n**Estimating costs:** developing an approximation or estimate of the costs of the resources needed to complete a project\n\n**Determining the budget:** allocating the overall cost estimate to individual work items to establish a baseline for measuring performance\n\n**Controlling costs:** controlling changes to the project budget"}
{"id": "docx::WtvKwmF3HiKMoakC61XcldQinlc::237", "page_id": "docx::WtvKwmF3HiKMoakC61XcldQinlc", "title": "Chapter 07 成本管理 Cost", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 07 成本管理 Cost", "section": "序、必考简答题/**2、成本管理计划应该包括哪些信息？**", "url": "https://a1npn29y3xu.feishu.cn/wiki/WtvKwmF3HiKMoakC61XcldQinlc", "source_type": "docx", "n_chars": 280, "text": "**精确度**\n\n**测量单位**\n\n**组织程序链接**\n\n**控制临界值**\n\n**绩效测量规划**\n\n**报告模板**\n\n**过程描述**\n\nA cost management plan includes:\n\n- Level of accuracy and units of measure\n- Organizational procedure links\n- Control thresholds\n- Rules of performance measurement\n- Reporting formats\n- Process descriptions"}
{"id": "docx::WtvKwmF3HiKMoakC61XcldQinlc::238", "page_id": "docx::WtvKwmF3HiKMoakC61XcldQinlc", "title": "Chapter 07 成本管理 Cost", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 07 成本管理 Cost", "section": "序、必考简答题/**3、三种基本的成本估算类型**", "url": "https://a1npn29y3xu.feishu.cn/wiki/WtvKwmF3HiKMoakC61XcldQinlc", "source_type": "docx", "n_chars": 106, "text": "**粗粒度估算**\n\n**预算估算**\n\n**确定性估算**\n\n- Rough order of magnitude, ROM\n- Budgetary Estimate\n- Definitive Estimate"}
{"id": "docx::WtvKwmF3HiKMoakC61XcldQinlc::239", "page_id": "docx::WtvKwmF3HiKMoakC61XcldQinlc", "title": "Chapter 07 成本管理 Cost", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 07 成本管理 Cost", "section": "序、必考简答题/**4、成本估算的工具和技术有哪些？**", "url": "https://a1npn29y3xu.feishu.cn/wiki/WtvKwmF3HiKMoakC61XcldQinlc", "source_type": "docx", "n_chars": 105, "text": "**类比估算（自上而下估算）**\n\n**自下而上估算**\n\n**三点估算**\n\n**参数估算**\n\n"}
{"id": "docx::WtvKwmF3HiKMoakC61XcldQinlc::240", "page_id": "docx::WtvKwmF3HiKMoakC61XcldQinlc", "title": "Chapter 07 成本管理 Cost", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 07 成本管理 Cost", "section": "序、必考简答题/**5、挣值公式（EV, CV, SV, CPI, SPI）**", "url": "https://a1npn29y3xu.feishu.cn/wiki/WtvKwmF3HiKMoakC61XcldQinlc", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::WtvKwmF3HiKMoakC61XcldQinlc::241", "page_id": "docx::WtvKwmF3HiKMoakC61XcldQinlc", "title": "Chapter 07 成本管理 Cost", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 07 成本管理 Cost", "section": "Learning Objectives / 学习目标", "url": "https://a1npn29y3xu.feishu.cn/wiki/WtvKwmF3HiKMoakC61XcldQinlc", "source_type": "docx", "n_chars": 618, "text": "Understand the importance of project cost management\n\nExplain basic project cost management principles, concepts, and terms\n\nDescribe the process of planning cost management\n\nDiscuss different types of cost estimates and methods for preparing them\n\nUnderstand the processes of determining a budget and preparing a cost estimate for an information technology (IT) project\n\nUnderstand the benefits of earned value management and project portfolio management to assist in cost control\n\nDescribe how project management software can assist in project cost management\n\n"}
{"id": "docx::WtvKwmF3HiKMoakC61XcldQinlc::242", "page_id": "docx::WtvKwmF3HiKMoakC61XcldQinlc", "title": "Chapter 07 成本管理 Cost", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 07 成本管理 Cost", "section": "7.1 **The Importance of Project Cost Management / 项目成本管理的重要性**/7.1.1 什么是成本", "url": "https://a1npn29y3xu.feishu.cn/wiki/WtvKwmF3HiKMoakC61XcldQinlc", "source_type": "docx", "n_chars": 211, "text": "\n\n**Project cost management** includes the processes required to ensure that the project is completed within an approved budget / 项目成本管理包括确保项目在批准的预算内完成所需的流程"}
{"id": "docx::WtvKwmF3HiKMoakC61XcldQinlc::243", "page_id": "docx::WtvKwmF3HiKMoakC61XcldQinlc", "title": "Chapter 07 成本管理 Cost", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 07 成本管理 Cost", "section": "7.1 **The Importance of Project Cost Management / 项目成本管理的重要性**/7.1.2 项目成本管理的过程", "url": "https://a1npn29y3xu.feishu.cn/wiki/WtvKwmF3HiKMoakC61XcldQinlc", "source_type": "docx", "n_chars": 169, "text": "\n\n\n\n"}
{"id": "docx::WtvKwmF3HiKMoakC61XcldQinlc::244", "page_id": "docx::WtvKwmF3HiKMoakC61XcldQinlc", "title": "Chapter 07 成本管理 Cost", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 07 成本管理 Cost", "section": "7.2 **Basic Principles of Cost Management / 成本管理的基本原理**", "url": "https://a1npn29y3xu.feishu.cn/wiki/WtvKwmF3HiKMoakC61XcldQinlc", "source_type": "docx", "n_chars": 169, "text": "\n\n\n\n"}
{"id": "docx::WtvKwmF3HiKMoakC61XcldQinlc::245", "page_id": "docx::WtvKwmF3HiKMoakC61XcldQinlc", "title": "Chapter 07 成本管理 Cost", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 07 成本管理 Cost", "section": "7.2 **Basic Principles of Cost Management / 成本管理的基本原理**/7.2.1 经济学基础术语", "url": "https://a1npn29y3xu.feishu.cn/wiki/WtvKwmF3HiKMoakC61XcldQinlc", "source_type": "docx", "n_chars": 646, "text": "Most members of an executive board better understand and are more interested in financial terms than IT terms , so IT project managers must speak their language\n\n- **Profits** are revenues minus expenditures\n- **Profit** margin is the ratio of revenues to profits\n- **Life cycle costing** considers the total cost of ownership, or development plus support costs, for a project\n- **Cash flow analysis** determines the estimated annual costs and benefits for a project and the resulting annual cash flow\n\n**大多数执行委员会成员对财务术语的理解和兴趣都比 IT 术语更深入**，因此 IT 项目经理必须使用他们的语言\n\n利润是收入减去支出\n\n利润率是收入与利润的比率\n\n生命周期成本考虑项目的总拥有成本或开发成本加上支持成本\n\n现金流分析确定项目的预计年度成本和收益以及由此产生的年度现金流"}
{"id": "docx::WtvKwmF3HiKMoakC61XcldQinlc::246", "page_id": "docx::WtvKwmF3HiKMoakC61XcldQinlc", "title": "Chapter 07 成本管理 Cost", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 07 成本管理 Cost", "section": "7.2 **Basic Principles of Cost Management / 成本管理的基本原理**/7.2.2 成本和收益的类型", "url": "https://a1npn29y3xu.feishu.cn/wiki/WtvKwmF3HiKMoakC61XcldQinlc", "source_type": "docx", "n_chars": 676, "text": "**Tangible costs or benefits** are those costs or benefits that an organization can easily measure in dollars\n\n**Intangible costs or benefits** are costs or benefits that are difficult to measure in monetary terms\n\n**Direct costs** are costs that can be directly related to producing the products and services of the project\n\n**Indirect costs** are costs that are not directly related to the products or services of the project, but are indirectly related to performing the project\n\n**Sunk cost** is money that has been spent in the past; when deciding what projects to invest in or continue, you should not include sunk costs\n\n有形成本或收益是组织可以轻松用美元衡量的成本或收益\n\n无形成本或收益是难以用货币衡量的成本或收益"}
{"id": "docx::WtvKwmF3HiKMoakC61XcldQinlc::247", "page_id": "docx::WtvKwmF3HiKMoakC61XcldQinlc", "title": "Chapter 07 成本管理 Cost", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 07 成本管理 Cost", "section": "7.2 **Basic Principles of Cost Management / 成本管理的基本原理**/7.2.2 成本和收益的类型", "url": "https://a1npn29y3xu.feishu.cn/wiki/WtvKwmF3HiKMoakC61XcldQinlc", "source_type": "docx", "n_chars": 194, "text": "n or continue, you should not include sunk costs\n\n有形成本或收益是组织可以轻松用美元衡量的成本或收益\n\n无形成本或收益是难以用货币衡量的成本或收益\n\n直接成本是与生产项目产品和服务直接相关的成本\n\n间接成本是与项目产品或服务无直接关系但与项目执行间接相关的成本\n\n沉没成本是过去花费的资金；在决定投资或继续进行哪些项目时，不应包括沉没成本"}
{"id": "docx::WtvKwmF3HiKMoakC61XcldQinlc::248", "page_id": "docx::WtvKwmF3HiKMoakC61XcldQinlc", "title": "Chapter 07 成本管理 Cost", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 07 成本管理 Cost", "section": "7.2 **Basic Principles of Cost Management / 成本管理的基本原理**/7.2.3 更多成本管理的基础理论", "url": "https://a1npn29y3xu.feishu.cn/wiki/WtvKwmF3HiKMoakC61XcldQinlc", "source_type": "docx", "n_chars": 697, "text": "**Learning curve theory** states that when many items are produced repetitively, the unit cost of those items decreases in a regular pattern as more units are produced\n\n**Reserves** are dollars included in a cost estimate to mitigate cost risk by allowing for future situations that are difficult to predict\n\n- **Contingency reserves** allow for future situations that may be partially planned for (sometimes called **known unknowns**) and are included in the project cost baseline\n- **Management reserves** allow for future situations that are unpredictable (sometimes called **unknown unknowns)**\n\n**学习曲线**理论指出，当重复生产许多物品时，随着生产单位数量的增加，这些物品的单位成本会以规律的方式下降\n\n**储备金**是成本估算中包含的资金，用于通过考虑难以预测的未来情况来降低成本风险"}
{"id": "docx::WtvKwmF3HiKMoakC61XcldQinlc::249", "page_id": "docx::WtvKwmF3HiKMoakC61XcldQinlc", "title": "Chapter 07 成本管理 Cost", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 07 成本管理 Cost", "section": "7.2 **Basic Principles of Cost Management / 成本管理的基本原理**/7.2.3 更多成本管理的基础理论", "url": "https://a1npn29y3xu.feishu.cn/wiki/WtvKwmF3HiKMoakC61XcldQinlc", "source_type": "docx", "n_chars": 192, "text": "**学习曲线**理论指出，当重复生产许多物品时，随着生产单位数量的增加，这些物品的单位成本会以规律的方式下降\n\n**储备金**是成本估算中包含的资金，用于通过考虑难以预测的未来情况来降低成本风险\n\n- **应急储备金**用于部分计划的未来情况（有时称为**已知的未知**情况），并包含在项目成本基准中\n- **管理储备金**用于考虑不可预测的未来情况（有时称为**未知的未知**情况）"}
{"id": "docx::WtvKwmF3HiKMoakC61XcldQinlc::250", "page_id": "docx::WtvKwmF3HiKMoakC61XcldQinlc", "title": "Chapter 07 成本管理 Cost", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 07 成本管理 Cost", "section": "7.3 Planning Cost Management / 计划成本管理", "url": "https://a1npn29y3xu.feishu.cn/wiki/WtvKwmF3HiKMoakC61XcldQinlc", "source_type": "docx", "n_chars": 432, "text": "\n\nThe project team uses expert judgment, analytical techniques, and meetings to develop the cost management plan\n\nA cost management plan includes:\n\n- Level of accuracy and units of measure\n- Organizational procedure links\n- Control thresholds\n- Rules of performance measurement\n- Reporting formats\n- Process descriptions\n\n"}
{"id": "docx::WtvKwmF3HiKMoakC61XcldQinlc::251", "page_id": "docx::WtvKwmF3HiKMoakC61XcldQinlc", "title": "Chapter 07 成本管理 Cost", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 07 成本管理 Cost", "section": "7.4 Estimating Costs / 成本估算", "url": "https://a1npn29y3xu.feishu.cn/wiki/WtvKwmF3HiKMoakC61XcldQinlc", "source_type": "docx", "n_chars": 328, "text": "Project managers must take cost estimates seriously if they want to complete projects within budget constraints.\n\nIt’s important to know the types of cost estimates, how to prepare cost estimates, and typical problems associated with IT cost estimates.\n\n如果项目经理想在预算限制内完成项目，他们必须认真对待成本估算。\n\n了解成本估算的类型、如何编制成本估算以及与 IT 成本估算相关的典型问题非常重要。"}
{"id": "docx::WtvKwmF3HiKMoakC61XcldQinlc::252", "page_id": "docx::WtvKwmF3HiKMoakC61XcldQinlc", "title": "Chapter 07 成本管理 Cost", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 07 成本管理 Cost", "section": "7.4 Estimating Costs / 成本估算/7.4.1 成本估算的类型", "url": "https://a1npn29y3xu.feishu.cn/wiki/WtvKwmF3HiKMoakC61XcldQinlc", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::WtvKwmF3HiKMoakC61XcldQinlc::253", "page_id": "docx::WtvKwmF3HiKMoakC61XcldQinlc", "title": "Chapter 07 成本管理 Cost", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 07 成本管理 Cost", "section": "7.4 Estimating Costs / 成本估算/7.4.2 成本估算的工具和技术", "url": "https://a1npn29y3xu.feishu.cn/wiki/WtvKwmF3HiKMoakC61XcldQinlc", "source_type": "docx", "n_chars": 616, "text": "Basic tools and techniques for cost estimates:\n\n- **Analogous or top-down estimates**: use the actual cost of a previous, similar project as the basis for estimating the cost of the current project\n- **Bottom-up estimates**: involve estimating individual work items or activities and summing them to get a project total\n- **Parametric modeling** uses project characteristics (parameters) in a mathematical model to estimate project costs\n\n成本估算的基本工具和技术：\n\n- 类比或自上而下的估算：使用以前类似项目的实际成本作为估算当前项目成本的基础\n- 自下而上的估算：涉及估算单个工作项目或活动并将其相加以获得项目总额\n- 参数建模使用数学模型中的项目特征（参数）来估算项目成本\n\n"}
{"id": "docx::WtvKwmF3HiKMoakC61XcldQinlc::254", "page_id": "docx::WtvKwmF3HiKMoakC61XcldQinlc", "title": "Chapter 07 成本管理 Cost", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 07 成本管理 Cost", "section": "7.4 Estimating Costs / 成本估算/7.4.3 IT 项目成本估算的典型问题", "url": "https://a1npn29y3xu.feishu.cn/wiki/WtvKwmF3HiKMoakC61XcldQinlc", "source_type": "docx", "n_chars": 242, "text": "\n\nEstimates are done too quickly / 估算太快\n\nPeople lack estimating experience / 人们缺乏估算经验\n\nHuman beings are biased toward underestimation / 人们倾向于低估困难程度\n\nManagement desires accuracy / 管理层渴望准确性"}
{"id": "docx::WtvKwmF3HiKMoakC61XcldQinlc::255", "page_id": "docx::WtvKwmF3HiKMoakC61XcldQinlc", "title": "Chapter 07 成本管理 Cost", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 07 成本管理 Cost", "section": "7.5 Determining the Budget / 成本预算", "url": "https://a1npn29y3xu.feishu.cn/wiki/WtvKwmF3HiKMoakC61XcldQinlc", "source_type": "docx", "n_chars": 474, "text": "\n\nCost budgeting involves allocating the project cost estimate to individual work items over time\n\nThe WBS is a required input to the cost budgeting process since it defines the work items\n\nImportant goal is to produce a cost baseline\n\n- a time-phased budget that project managers use to measure and monitor cost performance\n\n成本预算涉及将项目成本估算随时间分配给各个工作项目\n\nWBS 是成本预算流程的必需输入，因为它定义了工作项目\n\n重要目标是制定成本基准\n\n- 项目经理用来衡量和监控成本绩效的时间阶段预算"}
{"id": "docx::WtvKwmF3HiKMoakC61XcldQinlc::256", "page_id": "docx::WtvKwmF3HiKMoakC61XcldQinlc", "title": "Chapter 07 成本管理 Cost", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 07 成本管理 Cost", "section": "7.6 Controlling Costs / 成本控制", "url": "https://a1npn29y3xu.feishu.cn/wiki/WtvKwmF3HiKMoakC61XcldQinlc", "source_type": "docx", "n_chars": 369, "text": "\n\nProject cost control includes\n\n- Monitoring cost performance\n- Ensuring that only appropriate project changes are included in a revised cost baseline\n- Informing project stakeholders of authorized changes to the project that will affect costs\n\n项目成本控制包括\n\n- 监控成本绩效\n- 确保只有适当的项目变更才包含在修订的成本基准中\n- 通知项目利益相关者将影响成本的授权项目变更"}
{"id": "docx::WtvKwmF3HiKMoakC61XcldQinlc::257", "page_id": "docx::WtvKwmF3HiKMoakC61XcldQinlc", "title": "Chapter 07 成本管理 Cost", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 07 成本管理 Cost", "section": "7.6 Controlling Costs / 成本控制/7.6.1 Earned Value Management (EVM) / 净值管理", "url": "https://a1npn29y3xu.feishu.cn/wiki/WtvKwmF3HiKMoakC61XcldQinlc", "source_type": "docx", "n_chars": 581, "text": "EVM is a project performance measurement technique that integrates scope, time, and cost data\n\nGiven a baseline (original plan plus approved changes), you can determine how well the project is meeting its goals\n\nYou must enter actual information periodically to use EVM\n\nEVM 是一种项目绩效衡量技术，它整合了范围、时间和成本数据\n\n给定一个基准（原始计划加上已批准的变更），您可以确定项目实现目标的程度\n\n您必须定期输入实际信息才能使用 EVM\n\nThe **planned value (PV),** formerly called the budgeted cost of work scheduled (BCWS), also called the budget, is that portion of the approved total cost estimate planned to be spent on an activity during a given period"}
{"id": "docx::WtvKwmF3HiKMoakC61XcldQinlc::258", "page_id": "docx::WtvKwmF3HiKMoakC61XcldQinlc", "title": "Chapter 07 成本管理 Cost", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 07 成本管理 Cost", "section": "7.6 Controlling Costs / 成本控制/7.6.1 Earned Value Management (EVM) / 净值管理", "url": "https://a1npn29y3xu.feishu.cn/wiki/WtvKwmF3HiKMoakC61XcldQinlc", "source_type": "docx", "n_chars": 597, "text": "rtion of the approved total cost estimate planned to be spent on an activity during a given period\n\n**Actual cost (AC),** formerly called actual cost of work performed (ACWP), is the total of direct and indirect costs incurred in accomplishing work on an activity during a given period\n\nThe **earned value (EV),** formerly called the budgeted cost of work performed (BCWP), is an estimate of the value of the physical work actually completed\n\nEV is based on the original planned costs for the project or activity and the rate at which the team is completing work on the project or activity to date"}
{"id": "docx::WtvKwmF3HiKMoakC61XcldQinlc::259", "page_id": "docx::WtvKwmF3HiKMoakC61XcldQinlc", "title": "Chapter 07 成本管理 Cost", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 07 成本管理 Cost", "section": "7.6 Controlling Costs / 成本控制/7.6.1 Earned Value Management (EVM) / 净值管理", "url": "https://a1npn29y3xu.feishu.cn/wiki/WtvKwmF3HiKMoakC61XcldQinlc", "source_type": "docx", "n_chars": 656, "text": "t or activity and the rate at which the team is completing work on the project or activity to date\n\n**Rate of performance (RP)** is the ratio of actual work completed to the percentage of work planned to have been completed at any given time during the life of the project or activity / **绩效率（RP）是项目或活动生命周期内任何给定时间内实际完成的工作量与计划完成的工作量的百分比之比**\n\n\n\n把 EV 放在前面！！！相减表示偏差，相除表示指数！！！\n\nEV 挣值\n\nPV 计划值\n\nAC 实际成本\n\nCV = EV - AC\n\nSV = EV - PV\n\nCPI = EV / AC\n\nSPI = EV / PV\n\nEAC = BAC / CPI\n\nEFT = OFT / SPI\n\n\n\n"}
{"id": "docx::WtvKwmF3HiKMoakC61XcldQinlc::260", "page_id": "docx::WtvKwmF3HiKMoakC61XcldQinlc", "title": "Chapter 07 成本管理 Cost", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 07 成本管理 Cost", "section": "7.6 Controlling Costs / 成本控制/7.6.1 Earned Value Management (EVM) / 净值管理", "url": "https://a1npn29y3xu.feishu.cn/wiki/WtvKwmF3HiKMoakC61XcldQinlc", "source_type": "docx", "n_chars": 212, "text": "ishu.cn/file/GH0qbMbmeonscxxrNC1cLpaonie)\n\n\n\n\n\n"}
{"id": "docx::WtvKwmF3HiKMoakC61XcldQinlc::261", "page_id": "docx::WtvKwmF3HiKMoakC61XcldQinlc", "title": "Chapter 07 成本管理 Cost", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 07 成本管理 Cost", "section": "Chapter Summary", "url": "https://a1npn29y3xu.feishu.cn/wiki/WtvKwmF3HiKMoakC61XcldQinlc", "source_type": "docx", "n_chars": 329, "text": "Project cost management is a traditionally weak area of IT projects, and project managers must work to improve their ability to deliver projects within approved budgets\n\nMain processes include\n\n- Plan cost management\n- Estimate costs\n- Determine the budget\n- Control costs\n\n"}
{"id": "docx::WtvKwmF3HiKMoakC61XcldQinlc::262", "page_id": "docx::WtvKwmF3HiKMoakC61XcldQinlc", "title": "Chapter 07 成本管理 Cost", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 07 成本管理 Cost", "section": "选择题重点题解析：/2.什么是项目成本管理的主要目标？", "url": "https://a1npn29y3xu.feishu.cn/wiki/WtvKwmF3HiKMoakC61XcldQinlc", "source_type": "docx", "n_chars": 73, "text": "A.用尽量低的成本完成一个项目\n\n B.用一个批准的预算完成一个项目\n\n C.提供真实、准确的项目成本信息\n\n D.确保一个组织的钱使用得当"}
{"id": "docx::WtvKwmF3HiKMoakC61XcldQinlc::263", "page_id": "docx::WtvKwmF3HiKMoakC61XcldQinlc", "title": "Chapter 07 成本管理 Cost", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 07 成本管理 Cost", "section": "选择题重点题解析：/2 解析：", "url": "https://a1npn29y3xu.feishu.cn/wiki/WtvKwmF3HiKMoakC61XcldQinlc", "source_type": "docx", "n_chars": 154, "text": "**Project cost management** includes the processes required to ensure that the project is completed within an approved budget / 项目成本管理包括确保项目在批准的预算内完成所需的流程"}
{"id": "docx::WtvKwmF3HiKMoakC61XcldQinlc::264", "page_id": "docx::WtvKwmF3HiKMoakC61XcldQinlc", "title": "Chapter 07 成本管理 Cost", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 07 成本管理 Cost", "section": "选择题重点题解析：/2 解析：/3.根据《PMBOK®指南》，下列哪个不是项目成本管理工程中估算成本的输出？", "url": "https://a1npn29y3xu.feishu.cn/wiki/WtvKwmF3HiKMoakC61XcldQinlc", "source_type": "docx", "n_chars": 41, "text": "A.活动成本估算\n\n B.成本基线\n\n C.基础估算\n\n D.项目文档的更新"}
{"id": "docx::WtvKwmF3HiKMoakC61XcldQinlc::265", "page_id": "docx::WtvKwmF3HiKMoakC61XcldQinlc", "title": "Chapter 07 成本管理 Cost", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 07 成本管理 Cost", "section": "选择题重点题解析：/3 解析：", "url": "https://a1npn29y3xu.feishu.cn/wiki/WtvKwmF3HiKMoakC61XcldQinlc", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::WtvKwmF3HiKMoakC61XcldQinlc::266", "page_id": "docx::WtvKwmF3HiKMoakC61XcldQinlc", "title": "Chapter 07 成本管理 Cost", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 07 成本管理 Cost", "section": "选择题重点题解析：/7.随着时间的推移，\\_\\_\\_ 涉及分配个人物质资源或工作项目的成本估计。", "url": "https://a1npn29y3xu.feishu.cn/wiki/WtvKwmF3HiKMoakC61XcldQinlc", "source_type": "docx", "n_chars": 36, "text": "A.储备分析\n\nB.生命周期成本计算\n\nC.项目成本预算\n\nD.挣值分析"}
{"id": "docx::WtvKwmF3HiKMoakC61XcldQinlc::267", "page_id": "docx::WtvKwmF3HiKMoakC61XcldQinlc", "title": "Chapter 07 成本管理 Cost", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 07 成本管理 Cost", "section": "选择题重点题解析：/7 解析：", "url": "https://a1npn29y3xu.feishu.cn/wiki/WtvKwmF3HiKMoakC61XcldQinlc", "source_type": "docx", "n_chars": 185, "text": "Cost budgeting involves allocating the project cost estimate to ***individual work items*** over time\n\n成本预算涉及将项目成本估算随时间分配给各个工作项目\n\n"}
{"id": "docx::WtvKwmF3HiKMoakC61XcldQinlc::268", "page_id": "docx::WtvKwmF3HiKMoakC61XcldQinlc", "title": "Chapter 07 成本管理 Cost", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！/Chapter 07 成本管理 Cost", "section": "计算题重点题解析：", "url": "https://a1npn29y3xu.feishu.cn/wiki/WtvKwmF3HiKMoakC61XcldQinlc", "source_type": "docx", "n_chars": 397, "text": "\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf::269", "page_id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf", "title": "Chapter 08 Performance / 第八章：性能", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 08 Performance / 第八章：性能", "section": "What is Performance? / 什么是性能？", "url": "https://a1npn29y3xu.feishu.cn/wiki/CPliwjA0Li4FPmkjouEcctD7nRf", "source_type": "docx", "n_chars": 283, "text": "Performance **is about time**. / 性能与时间密切相关\n\nPerformance is about time and the software system's ability to meet timing requirements. / 性能其实就是软件系统满足与时间相关需求的能力\n\n\n\n当事件发生的时候 —— 中断、信息和请求从用户从其它系统发出来，或者时钟事件标注了时间的通道 —— 那么（开发者的）系统必须准时响应。"}
{"id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf::270", "page_id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf", "title": "Chapter 08 Performance / 第八章：性能", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 08 Performance / 第八章：性能", "section": "General Scenario / 通用场景", "url": "https://a1npn29y3xu.feishu.cn/wiki/CPliwjA0Li4FPmkjouEcctD7nRf", "source_type": "docx", "n_chars": 539, "text": "\n\n\n\nUsers initiate transactions under normal operations. **The system** processes the transactions with an average latency of two seconds.\n\n用户在正常操作下发起交易。系统以平均两秒的延迟处理交易。\n\n- Stimulus / 刺激: Transaction arrivals\n交易到达\n- Source / 来源: Users\n用户\n- Artifact / 工件: The system\n系统\n- Response / 响应: Process the transactions\n处理交易\n- Response measure / 响应度量: Average latency of two seconds\n平均延迟为两秒\n- Environment / 环境: Under normal operation\n正常操作下"}
{"id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf::271", "page_id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf", "title": "Chapter 08 Performance / 第八章：性能", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 08 Performance / 第八章：性能", "section": "Performance Modeling / 性能建模", "url": "https://a1npn29y3xu.feishu.cn/wiki/CPliwjA0Li4FPmkjouEcctD7nRf", "source_type": "docx", "n_chars": 675, "text": "**Two basic contributors to the response time / 响应时间的两个基本组成部分**:\n\n1. **Processing Time / 处理时间**\n\n- Processing time is the time that the system is working to respond.\n 处理时间是系统为响应请求而执行操作的时间。\n\n1. **Blocked Time / 阻塞时间**\n\n- Blocked time is the time that the system is unable to respond.\n 阻塞时间是系统无法响应的时间。\n\n**Blocked Time is caused by / 阻塞时间的原因**：\n\n- **Contention for Resources / 资源竞争**\n- **Availability of Resources / 资源可用性**\n- **Dependency on Other Computations / 依赖其他计算**\n\n**Resources / 资源**:\n\n- **Hardware resources / 硬件资源**: e.g., CPU, data stores, network bandwidth, and memory.\n 硬件资源：例如 CPU、数据存储、网络带宽和内存。\n- **Software resources / 软件资源**: e.g., buffers, or critical sections."}
{"id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf::272", "page_id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf", "title": "Chapter 08 Performance / 第八章：性能", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 08 Performance / 第八章：性能", "section": "Performance Modeling / 性能建模", "url": "https://a1npn29y3xu.feishu.cn/wiki/CPliwjA0Li4FPmkjouEcctD7nRf", "source_type": "docx", "n_chars": 136, "text": "y.\n 硬件资源：例如 CPU、数据存储、网络带宽和内存。\n- **Software resources / 软件资源**: e.g., buffers, or critical sections.\n 软件资源：例如缓冲区或关键区段（critical sections）。"}
{"id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf::273", "page_id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf", "title": "Chapter 08 Performance / 第八章：性能", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 08 Performance / 第八章：性能", "section": "Tactics / 策略/Goal / 目标", "url": "https://a1npn29y3xu.feishu.cn/wiki/CPliwjA0Li4FPmkjouEcctD7nRf", "source_type": "docx", "n_chars": 224, "text": "To generate a response to an event arriving at the system within some time-based constraint. / 为了在基于时间的约束内生成对事件的响应，\n\nThe event can be single or a stream, and is the trigger to perform computation. / 事件可以是单个的或流式的，并且是执行计算的触发器。"}
{"id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf::274", "page_id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf", "title": "Chapter 08 Performance / 第八章：性能", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 08 Performance / 第八章：性能", "section": "Tactics / 策略/Categories / 类别/Control resource demand / 控制资源需求", "url": "https://a1npn29y3xu.feishu.cn/wiki/CPliwjA0Li4FPmkjouEcctD7nRf", "source_type": "docx", "n_chars": 95, "text": "- To produce smaller demand on the resources / 产生对资源的较小需求\n- Operate on the demand side / 在需求侧操作"}
{"id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf::275", "page_id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf", "title": "Chapter 08 Performance / 第八章：性能", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 08 Performance / 第八章：性能", "section": "Tactics / 策略/Categories / 类别/Manage resources / 管理资源", "url": "https://a1npn29y3xu.feishu.cn/wiki/CPliwjA0Li4FPmkjouEcctD7nRf", "source_type": "docx", "n_chars": 138, "text": "- To make the resources at hand work more effectively in handling the demands / 使手头的资源在处理需求时更有效地工作\n- Operate on the response side / 在响应侧操作"}
{"id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf::276", "page_id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf", "title": "Chapter 08 Performance / 第八章：性能", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 08 Performance / 第八章：性能", "section": "Tactics / 策略/Categories / 类别/**Resources / 资源**", "url": "https://a1npn29y3xu.feishu.cn/wiki/CPliwjA0Li4FPmkjouEcctD7nRf", "source_type": "docx", "n_chars": 221, "text": "- **Hardware resources / 硬件资源**: e.g., CPU, data stores, network bandwidth, and memory.\n 硬件资源：例如 CPU、数据存储、网络带宽和内存。\n- **Software resources / 软件资源**: e.g., buffers, or critical sections.\n 软件资源：例如缓冲区或关键区段（critical sections）。"}
{"id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf::277", "page_id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf", "title": "Chapter 08 Performance / 第八章：性能", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 08 Performance / 第八章：性能", "section": "Tactics / 策略/Tatics Tree / 策略树/省流：让网页加载更快", "url": "https://a1npn29y3xu.feishu.cn/wiki/CPliwjA0Li4FPmkjouEcctD7nRf", "source_type": "docx", "n_chars": 43, "text": "| 控制用户对资源的请求 | 充分利用资源，让有限的服务资源效率最大化 |\n|-|-|"}
{"id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf::278", "page_id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf", "title": "Chapter 08 Performance / 第八章：性能", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 08 Performance / 第八章：性能", "section": "Tactics / 策略/Tatics Tree / 策略树/Control Resource Demand / 控制资源需求/**Manage Sampling Rate / 管理采样率**", "url": "https://a1npn29y3xu.feishu.cn/wiki/CPliwjA0Li4FPmkjouEcctD7nRf", "source_type": "docx", "n_chars": 189, "text": "- **Objective**: To reduce the sampling frequency at which a stream of data is captured, helping to minimize unnecessary data processing and system load.\n**目标**：降低数据流采样的频率，以减少不必要的数据处理和系统负载。"}
{"id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf::279", "page_id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf", "title": "Chapter 08 Performance / 第八章：性能", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 08 Performance / 第八章：性能", "section": "Tactics / 策略/Tatics Tree / 策略树/Control Resource Demand / 控制资源需求/**Prioritize Events / 优先级事件（《信号与系统》对此知识点有详细讲解）**", "url": "https://a1npn29y3xu.feishu.cn/wiki/CPliwjA0Li4FPmkjouEcctD7nRf", "source_type": "docx", "n_chars": 214, "text": "- **Objective**: To impose a priority scheme that ranks events according to their importance. Low-priority events are ignored when system resources are insufficient.\n**目标**：制定优先级方案，根据事件的重要性对其进行排序。当系统资源不足时，忽略低优先级事件。"}
{"id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf::280", "page_id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf", "title": "Chapter 08 Performance / 第八章：性能", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 08 Performance / 第八章：性能", "section": "Tactics / 策略/Tatics Tree / 策略树/Control Resource Demand / 控制资源需求/**Reduce Overhead / 减少开销**", "url": "https://a1npn29y3xu.feishu.cn/wiki/CPliwjA0Li4FPmkjouEcctD7nRf", "source_type": "docx", "n_chars": 436, "text": "- **Objective**: The use of intermediaries (such as proxies or message brokers) increases the resources consumed in processing an event stream. Removing these intermediaries can improve latency.\n**目标**：中介的使用（如代理或消息中间件）会增加处理事件流所消耗的资源，去除中介可以改善延迟。\n- **Trade-off**: There is a trade-off between **modifiability** (flexibility of the system) and **performance** (efficiency of event processing).\n**权衡**：在**可修改性**（系统灵活性）和**性能**（事件处理效率）之间存在权衡。"}
{"id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf::281", "page_id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf", "title": "Chapter 08 Performance / 第八章：性能", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 08 Performance / 第八章：性能", "section": "Tactics / 策略/Tatics Tree / 策略树/Control Resource Demand / 控制资源需求/**Bound Execution Times / 限制执行时间**", "url": "https://a1npn29y3xu.feishu.cn/wiki/CPliwjA0Li4FPmkjouEcctD7nRf", "source_type": "docx", "n_chars": 479, "text": "- **Objective**: Place a limit on how much execution time is used to respond to an event, preventing long-running tasks from blocking the system.\n**目标**：限制响应事件所用的执行时间，防止长期运行的任务阻塞系统。\n- In algorithm design, limiting the number of iterations is one method for bounding execution time.\n 在算法设计中，限制迭代次数是限制执行时间的一种方法。\n- **Trade-off**: There is a trade-off between **performance** (system efficiency) and **accuracy** (completeness of results).\n**权衡**：在**性能**（系统效率）和**准确性**（结果的完整性）之间存在权衡。"}
{"id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf::282", "page_id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf", "title": "Chapter 08 Performance / 第八章：性能", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 08 Performance / 第八章：性能", "section": "Tactics / 策略/Tatics Tree / 策略树/Control Resource Demand / 控制资源需求/**Increase Resource Efficiency / 提高资源效率**", "url": "https://a1npn29y3xu.feishu.cn/wiki/CPliwjA0Li4FPmkjouEcctD7nRf", "source_type": "docx", "n_chars": 452, "text": "- **Objective**: Improving the algorithms used in critical areas will decrease latency and increase the overall resource efficiency of the system.\n**目标**：改进关键领域中使用的算法将减少延迟，并提高系统的整体资源效率。\n- **To reduce the complexity of the algorithm / 降低算法复杂度**: Simplifying algorithms can help to reduce the time and resources required for processing, improving system performance.\n 简化算法有助于减少处理所需的时间和资源，从而提高系统性能。\n\n"}
{"id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf::283", "page_id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf", "title": "Chapter 08 Performance / 第八章：性能", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 08 Performance / 第八章：性能", "section": "Tactics / 策略/Tatics Tree / 策略树/就业方向为后端的同学请注意，这一些内容除了“增加资源”，都是面试的重难点！/**Increase Resources / 增加资源**", "url": "https://a1npn29y3xu.feishu.cn/wiki/CPliwjA0Li4FPmkjouEcctD7nRf", "source_type": "docx", "n_chars": 217, "text": "- **Objective**: To reduce latency by upgrading system resources.\n**目标**：通过升级系统资源来减少延迟。\n- **Faster Processors / 更快的处理器**\n- **Additional Processors / 增加处理器**\n- **Additional Memory / 增加内存**\n- **Faster Networks / 更快的网络**"}
{"id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf::284", "page_id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf", "title": "Chapter 08 Performance / 第八章：性能", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 08 Performance / 第八章：性能", "section": "Tactics / 策略/Tatics Tree / 策略树/就业方向为后端的同学请注意，这一些内容除了“增加资源”，都是面试的重难点！/**Increase Concurrency / 增加并发性**", "url": "https://a1npn29y3xu.feishu.cn/wiki/CPliwjA0Li4FPmkjouEcctD7nRf", "source_type": "docx", "n_chars": 614, "text": "- **Objective**: To reduce blocked time by processing tasks in parallel, improving overall system performance.\n**目标**：通过并行处理任务来减少阻塞时间，从而提高系统整体性能。\n- **Parallel Processing of Requests / 请求的并行处理**: If requests can be processed in parallel, the system can handle multiple tasks simultaneously, reducing waiting time and improving throughput.\n 如果请求可以并行处理，系统就能同时处理多个任务，减少等待时间并提高吞吐量。\n- **Concurrency through Threads / 通过线程引入并发**: Concurrency can be introduced by processing different streams of events on different threads, allowing independent processing of multiple event streams.\n 通过在不同线程上处理不同的事件流，可以引入并发，允许多个事件流的独立处理。"}
{"id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf::285", "page_id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf", "title": "Chapter 08 Performance / 第八章：性能", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 08 Performance / 第八章：性能", "section": "Tactics / 策略/Tatics Tree / 策略树/就业方向为后端的同学请注意，这一些内容除了“增加资源”，都是面试的重难点！/Maintain Multiple Copies of Computations / 保持计算的多个副本", "url": "https://a1npn29y3xu.feishu.cn/wiki/CPliwjA0Li4FPmkjouEcctD7nRf", "source_type": "docx", "n_chars": 249, "text": "- The purpose of replicas is to reduce resource contention on a single server. / 副本的目的是减少单个服务器上的资源争用。\n- Load balancer assigns new work to one of the duplicate servers. / 负载均衡器将新工作分配给其中一个副本服务器。\n\n"}
{"id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf::286", "page_id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf", "title": "Chapter 08 Performance / 第八章：性能", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 08 Performance / 第八章：性能", "section": "Tactics / 策略/Tatics Tree / 策略树/就业方向为后端的同学请注意，这一些内容除了“增加资源”，都是面试的重难点！/**Maintain Multiple Copies of Data / 保持数据的多份副本**", "url": "https://a1npn29y3xu.feishu.cn/wiki/CPliwjA0Li4FPmkjouEcctD7nRf", "source_type": "docx", "n_chars": 693, "text": "**Data Caching / 数据缓存**\n\n- **Definition**: Data caching involves storing copies of data on storage devices with varying access speeds (e.g., memory vs. disk, or local vs. remote access via networks).\n**定义**：数据缓存是将数据的副本存储在具有不同访问速度的存储设备上（例如，内存访问与磁盘访问，或通过网络的本地访问与远程访问）。\n- **Memory Access vs. Disk Access / 内存访问与磁盘访问**: Memory access is much faster than disk access, so frequently used data can be cached in memory to reduce access time.\n 内存访问比磁盘访问快得多，因此频繁使用的数据可以缓存到内存中，以减少访问时间。\n- **Local Access vs. Remote Access / 本地访问与远程访问**: Accessing data locally (from the same machine) is faster than accessing data remotely over a network, so caching frequently used data locally can reduce network delays."}
{"id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf::287", "page_id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf", "title": "Chapter 08 Performance / 第八章：性能", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 08 Performance / 第八章：性能", "section": "Tactics / 策略/Tatics Tree / 策略树/就业方向为后端的同学请注意，这一些内容除了“增加资源”，都是面试的重难点！/**Maintain Multiple Copies of Data / 保持数据的多份副本**", "url": "https://a1npn29y3xu.feishu.cn/wiki/CPliwjA0Li4FPmkjouEcctD7nRf", "source_type": "docx", "n_chars": 677, "text": "ng data remotely over a network, so caching frequently used data locally can reduce network delays.\n 本地访问（来自同一台机器）比远程通过网络访问数据更快，因此将频繁使用的数据缓存到本地可以减少网络延迟。\n\n**Data Replication / 数据复制**\n\n- **Definition**: Data replication involves maintaining separate copies of data in different locations to reduce contention from multiple simultaneous accesses. This improves both availability and performance.\n**定义**：数据复制是保持数据在不同位置的副本，以减少多次并发访问时的竞争，从而提高可用性和性能。\n- **Reducing Contention / 减少竞争**: By replicating data, different users or processes can access separate copies of the data simultaneously, improving system performance and reducing delays.\n 通过复制数据，不同的用户或进程可以同时访问数据的独立副本，从而提高系统性能并减少延迟。"}
{"id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf::288", "page_id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf", "title": "Chapter 08 Performance / 第八章：性能", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 08 Performance / 第八章：性能", "section": "Tactics / 策略/Tatics Tree / 策略树/就业方向为后端的同学请注意，这一些内容除了“增加资源”，都是面试的重难点！/**Maintain Multiple Copies of Data / 保持数据的多份副本**", "url": "https://a1npn29y3xu.feishu.cn/wiki/CPliwjA0Li4FPmkjouEcctD7nRf", "source_type": "docx", "n_chars": 155, "text": "ly, improving system performance and reducing delays.\n 通过复制数据，不同的用户或进程可以同时访问数据的独立副本，从而提高系统性能并减少延迟。\n\n"}
{"id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf::289", "page_id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf", "title": "Chapter 08 Performance / 第八章：性能", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 08 Performance / 第八章：性能", "section": "Scheduling / 调度问题", "url": "https://a1npn29y3xu.feishu.cn/wiki/CPliwjA0Li4FPmkjouEcctD7nRf", "source_type": "docx", "n_chars": 676, "text": "当资源发生竞争时，必须进行资源调度以确保公平且高效的资源分配。\n\n我们需要解决处理器调度、缓冲区调度和网络调度的问题\n\n\n\n**Resource Model / 资源模型**\n\n- The resources include a set of machines/processors which are connected by networks. / 资源包括一组由网络连接的机器 / 处理器\n- Machine / Processor Model / 机器 / 处理器模型\n\n - Processing capability / speed, energy comsumption / 加工能力/速度、能耗\n- Network model / 网络模型\n\n - Network topology / 网络拓扑\n - Bandwidths / 带宽\n - Messages and energy comsumption / 信息和能量消耗\n - e.g. Sensor networks, Data Center networks, Mobile Cloud / 例子：传感器网络，数据中心网络，移动云\n\n**Objectives / 目标**\n\nMinimize completion time / 最小化完成时间\n\nMeeting deadline / 满足截止时间\n\nMaximize throughput / 最大化吞吐量"}
{"id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf::290", "page_id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf", "title": "Chapter 08 Performance / 第八章：性能", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 08 Performance / 第八章：性能", "section": "Scheduling / 调度问题", "url": "https://a1npn29y3xu.feishu.cn/wiki/CPliwjA0Li4FPmkjouEcctD7nRf", "source_type": "docx", "n_chars": 471, "text": "目标**\n\nMinimize completion time / 最小化完成时间\n\nMeeting deadline / 满足截止时间\n\nMaximize throughput / 最大化吞吐量\n\nMinimize data transmission/messages / 最小化数据传输/消息\n\nMinimize energy consumption / 最小化能源消耗\n\n...\n\n**Classification of Scheduling / 调度分类**\n\nReal time scheduling v.s. non-real time scheduling / 实时调度与非实时调度\n\nStatic scheduling v.s. dynamic scheduling / 静态调度与动态调度\n\nOffline scheduling v.s. online scheduling / 离线调度与在线调度\n\nDeterminist scheduling v.s. Stochastic scheduling / 确定性调度与随机调度"}
{"id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf::291", "page_id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf", "title": "Chapter 08 Performance / 第八章：性能", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 08 Performance / 第八章：性能", "section": "Scheduling / 调度问题/**Task Scheduling Problems / 任务调度问题**", "url": "https://a1npn29y3xu.feishu.cn/wiki/CPliwjA0Li4FPmkjouEcctD7nRf", "source_type": "docx", "n_chars": 670, "text": "1. Bag-of-Tasks scheduling on single processor / 单处理器上的批量任务调度\n\n\n\n**Given**: release time, workload of each task, or deadline\n\n已知：每个任务的释放时间、工作量或截止时间\n\nTo determine **when** each task is executed\n\n目的是确定每个任务何时执行\n\n**Objectives**: average completion time of the tasks, or meeting deadlines\n\n目标：任务的平均完成时间，或满足截止时间\n\n1. Bag-of-Tasks scheduling on multiple processors / 多处理器上的批量任务调度\n\n\n\n**Given**: release time, workload of each task\n\n已知：每个任务的释放时间、工作量\n\nTo determine **where and when** each task is executed\n\n目的是确定每个任务的执行位置和时间\n\n**Objectives**: make-span\n\n目标：完成时间（Make-span）"}
{"id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf::292", "page_id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf", "title": "Chapter 08 Performance / 第八章：性能", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 08 Performance / 第八章：性能", "section": "Scheduling / 调度问题/**Task Scheduling Problems / 任务调度问题**", "url": "https://a1npn29y3xu.feishu.cn/wiki/CPliwjA0Li4FPmkjouEcctD7nRf", "source_type": "docx", "n_chars": 676, "text": "and when** each task is executed\n\n目的是确定每个任务的执行位置和时间\n\n**Objectives**: make-span\n\n目标：完成时间（Make-span）\n\n1. DAGs scheduling on heterogeneous processors / 异构处理器上的有向无环图调度\n\n\n\nGiven: processing time of every task on every processor communication time on the edges\n\nTo determine where and when each task is executed\n\nObjective: make-span ...\n\n已知：每个处理器上每个任务的处理时间边缘上的通信时间\n\n确定每个任务的执行地点和时间\n\n目标：完成跨度...\n\n1. Job shop scheduling / 作业车间调度\n\n\n\nGiven: processing time of every job on every processor\n\n已知：每个任务在每个处理器上的处理时间\n\nConstraint: every job is executed by every processor exactly once"}
{"id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf::293", "page_id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf", "title": "Chapter 08 Performance / 第八章：性能", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 08 Performance / 第八章：性能", "section": "Scheduling / 调度问题/**Task Scheduling Problems / 任务调度问题**", "url": "https://a1npn29y3xu.feishu.cn/wiki/CPliwjA0Li4FPmkjouEcctD7nRf", "source_type": "docx", "n_chars": 643, "text": "processor\n\n已知：每个任务在每个处理器上的处理时间\n\nConstraint: every job is executed by every processor exactly once\n\n约束条件：每个任务必须在每个处理器上执行一次\n\nObjective: make-span\n\n1. Periodic tasks scheduling / 周期性任务调度\n\n\n\n任务定期发布，以流水线方式执行\n\n**Similar Terminologies / 相似术语**\n\n- Task assignment / 任务分配\n- Task placement / 任务放置\n- Task allocation / 任务分配\n- Resource allocation / 资源分配\n- Resource scheduling / 资源调度\n\nThe problems above are considered as special cases/instances of the scheduling problem. / 上述问题被认为是调度问题的特殊情况/实例。\n\n**Categories of Scheduling Algorithms / 调度算法的类别**\n\nAlgorithms to solve optimization problems / 解决优化问题的算法"}
{"id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf::294", "page_id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf", "title": "Chapter 08 Performance / 第八章：性能", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 08 Performance / 第八章：性能", "section": "Scheduling / 调度问题/**Task Scheduling Problems / 任务调度问题**", "url": "https://a1npn29y3xu.feishu.cn/wiki/CPliwjA0Li4FPmkjouEcctD7nRf", "source_type": "docx", "n_chars": 672, "text": "gories of Scheduling Algorithms / 调度算法的类别**\n\nAlgorithms to solve optimization problems / 解决优化问题的算法\n\n1. Mathematical programming, i.e., integer programming, linear programming / 数学规划，即整数规划、线性规划\n2. Evolutionary algorithms, i.e., GA, PSO, Ant colony / 进化算法，即遗传算法（GA）、粒子群优化（PSO）、蚁群算法\n3. Simple and competitive heuristics, i.e., list scheduling / 简单且竞争性的启发式算法，即列表调度\n4. Machine learning based algorithm, i.e., deep reinforcement learning / 基于机器学习的算法，即深度强化学习\n\n**Scheduling Method: System Considerations**\n\n调度方法：系统考虑\n\nMachine centric approach / 机器中心方法\n\n- Scheduling is triggered when a machine becomes idle. For each idle machine, select the task according to some policies, e.g.,"}
{"id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf::295", "page_id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf", "title": "Chapter 08 Performance / 第八章：性能", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 08 Performance / 第八章：性能", "section": "Scheduling / 调度问题/**Task Scheduling Problems / 任务调度问题**", "url": "https://a1npn29y3xu.feishu.cn/wiki/CPliwjA0Li4FPmkjouEcctD7nRf", "source_type": "docx", "n_chars": 537, "text": "en a machine becomes idle. For each idle machine, select the task according to some policies, e.g.,\n- First-Come-First-Serve (FCFS) / 先到先服务（FCFS）\n- Shortest Job First (SJF) / 最短作业优先（SJF）\n- Earliest Deadline First (EDF) / 最早截止时间优先（EDF）\n- Job with the longest waiting time first, ... / 最长等待时间作业优先，...\n\nTask centric approach / 任务中心方法\n\n- Scheduling is triggered when a new task arrives. For each scheduled task, select the machine according to some policies, e.g., earliest finished time, ... / 当新任务到达时触发调度。对于每个调度的任务，根据某些策略选择机器，例如，最早完成时间，..."}
{"id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf::296", "page_id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf", "title": "Chapter 08 Performance / 第八章：性能", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 08 Performance / 第八章：性能", "section": "Scheduling / 调度问题/**List Scheduling Method /** 列表调度方法", "url": "https://a1npn29y3xu.feishu.cn/wiki/CPliwjA0Li4FPmkjouEcctD7nRf", "source_type": "docx", "n_chars": 661, "text": "**Step 1: Task selection / 步骤 1：任务选择**\n\n- Upward rank / 向上排名\n- Upward rank of node i is the length of the longest path from node i to the exit. / 节点 i 的向上排名是从节点 i 到出口的最长路径的长度。\n\n\n\n**Step 2: Processor Selection / 步骤 2：处理器选择**\n\n- Earliest Finish Time / 最早完成时间\n- For each task, select the machine which can finish that task in the earliest time. / 对于每个任务，选择能够在最早时间完成该任务的机器。\n\n\n\n\n\n上面红色的究竟是什么意思呢？让我们对 Computation Costs 表格进行拓展\n\n| Task | P1 | P2 | P3 | Average Cost（平均成本） | Path Cost（路径成本） |\n|-|-|-|-|-|-|"}
{"id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf::297", "page_id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf", "title": "Chapter 08 Performance / 第八章：性能", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 08 Performance / 第八章：性能", "section": "Scheduling / 调度问题/**List Scheduling Method /** 列表调度方法", "url": "https://a1npn29y3xu.feishu.cn/wiki/CPliwjA0Li4FPmkjouEcctD7nRf", "source_type": "docx", "n_chars": 666, "text": "putation Costs 表格进行拓展\n\n| Task | P1 | P2 | P3 | Average Cost（平均成本） | Path Cost（路径成本） |\n|-|-|-|-|-|-|\n| 1 | 14 | 16 | 9 | 13.0 | 18, 12, 9, 11, 14 |\n| 2 | 13 | 19 | 18 | 16.7 | 19, 16 |\n| 3 | 11 | 13 | 19 | 14.3 | 23 |\n| 4 | 13 | 8 | 17 | 12.7 | 27, 23 |\n| 5 | 12 | 13 | 10 | 11.7 | 13 |\n| 6 | 13 | 16 | 9 | 12.7 | 15 |\n| 7 | 7 | 15 | 11 | 11.0 | 17 |\n| **8** | **5** | **11** | **14** | **10.0** | 11 |\n| 9 | 18 | 12 | 20 | 16.7 | 13 |\n| **10** | **21** | **7** | **15** | **14.7** | —— |\n\n第一步的目的是估算每一个节点的重要成都\n\n大家看了这一张表之后，就可以代入数字进行计算了，我们从 10 号节点开始算，每一个节点的损失计算公式\n\n**节点的最大成本 = max 上一级节点的（成本 + 路径成本） + 本节点的平均成本**\n\n"}
{"id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf::298", "page_id": "docx::CPliwjA0Li4FPmkjouEcctD7nRf", "title": "Chapter 08 Performance / 第八章：性能", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 08 Performance / 第八章：性能", "section": "**Summary of Performance / 性能总结**", "url": "https://a1npn29y3xu.feishu.cn/wiki/CPliwjA0Li4FPmkjouEcctD7nRf", "source_type": "docx", "n_chars": 444, "text": "Performance is about the management of system resources in the face of particular types of demand to achieve acceptable timing behavior. / 性能是指在特定类型的需求面前，如何管理系统资源以实现可接受的时序行为。\n\nPerformance can be measured in terms of throughput and latency for both interactive and embedded real-time systems. / 性能可以通过吞吐量和延迟来衡量，适用于交互式和嵌入式实时系统。\n\nPerformance can be improved by reducing demand or by managing resources more appropriately. / 性能可以通过减少需求或更适当的管理资源来提升。"}
{"id": "docx::VqGUwEHlHiyPu0ktTsTcoK2dn0f::299", "page_id": "docx::VqGUwEHlHiyPu0ktTsTcoK2dn0f", "title": "Chapter 09 Security / 第九章：安全性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 09 Security / 第九章：安全性", "section": "What is Security? / 什么是安全性？", "url": "https://a1npn29y3xu.feishu.cn/wiki/VqGUwEHlHiyPu0ktTsTcoK2dn0f", "source_type": "docx", "n_chars": 693, "text": "\n\n**Security** is a measure of the system's ability to protect data and information from unauthorized access while still providing access to people and systems that are authorized. / 安全性是衡量系统在保护数据和信息免受未授权访问的同时，仍能提供对授权人员和系统的访问能力。\n\nAn action taken against a computer system with the intention of doing harm is called an attack. / 旨在对计算机系统造成危害的行为称为攻击。\n\nAttack can be in different forms:\n\n- Unauthorized attempt to access/modify data or service / 未经授权尝试访问/修改数据或服务\n- Intended to deny services to legitimate users / 旨在拒绝合法用户的服务\n\n \n\n**Security has three main characteristics, called CIA:**"}
{"id": "docx::VqGUwEHlHiyPu0ktTsTcoK2dn0f::300", "page_id": "docx::VqGUwEHlHiyPu0ktTsTcoK2dn0f", "title": "Chapter 09 Security / 第九章：安全性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 09 Security / 第九章：安全性", "section": "What is Security? / 什么是安全性？", "url": "https://a1npn29y3xu.feishu.cn/wiki/VqGUwEHlHiyPu0ktTsTcoK2dn0f", "source_type": "docx", "n_chars": 682, "text": "shu.cn/file/B7X6b8uZ8oFy80xLI2QcOotCnEd)\n\n**Security has three main characteristics, called CIA:**\n\n安全性具有三个主要特性，称为CIA：\n\n1. **Confidentiality** is the property that data or services are protected from unauthorized access.\n保密性是数据或服务受到未授权访问保护的属性。\n\n- For example, a hacker cannot access your income tax returns on a government computer. / 例如，黑客无法访问政府计算机上的个人所得税报表。\n\n1. **Integrity** is the property that data or services are not subject to unauthorized manipulation.\n完整性是数据或服务不受未授权篡改的属性。\n\n- For example, your grade has not been changed since your instructor assigned it. / 例如，自从教师给你打分后，你的成绩没有被更改。\n\n1. **Availability** is the property that the system will be available for legitimate use."}
{"id": "docx::VqGUwEHlHiyPu0ktTsTcoK2dn0f::301", "page_id": "docx::VqGUwEHlHiyPu0ktTsTcoK2dn0f", "title": "Chapter 09 Security / 第九章：安全性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 09 Security / 第九章：安全性", "section": "What is Security? / 什么是安全性？", "url": "https://a1npn29y3xu.feishu.cn/wiki/VqGUwEHlHiyPu0ktTsTcoK2dn0f", "source_type": "docx", "n_chars": 604, "text": "成绩没有被更改。\n\n1. **Availability** is the property that the system will be available for legitimate use.\n可用性是系统能为合法使用提供可用性的属性。\n\n- For example, a denial-of-service attack prevents you from ordering a book from an online bookstore. / 例如，拒绝服务攻击使你无法从在线书店订购书籍。\n\n**Other characteristics that support CIA / 支持CIA的其他特性**\n\n- **Authentication** verifies the identities of the parties to a transaction and checks if they are truly who they claim to be.(**WHO** you are?)\n认证验证交易各方的身份，并检查他们是否真的是他们所声称的人。（你是谁？）\n- **Authorization** grants a user the privileges to perform a task.(**WHAT** you can do?)\n授权授予用户执行任务的权限。（你能做什么？）"}
{"id": "docx::VqGUwEHlHiyPu0ktTsTcoK2dn0f::302", "page_id": "docx::VqGUwEHlHiyPu0ktTsTcoK2dn0f", "title": "Chapter 09 Security / 第九章：安全性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 09 Security / 第九章：安全性", "section": "General Scenario", "url": "https://a1npn29y3xu.feishu.cn/wiki/VqGUwEHlHiyPu0ktTsTcoK2dn0f", "source_type": "docx", "n_chars": 536, "text": "Portion of Scenario / 场景中的组成部分Possible Values / 可能的取值Source / 源头Human or another system which may have been previously identified (either correctly or incorrectly) or may be currently unknown. A human attacker may be from outside the organization or from inside the organization.人类或其他系统可能之前已被识别（正确或错误），或目前未知。人类攻击者可能来自组织外部，也可能来自组织内部。Stimulus / 激励Unauthorized attempt is made to display data, change or delete data, access system services, change the system's behavior, or reduce availability.未授权的尝试是指试图显示数据、修改或删除数据、访问系统服务、改变系统行为或降低系统可用性。"}
{"id": "docx::VqGUwEHlHiyPu0ktTsTcoK2dn0f::303", "page_id": "docx::VqGUwEHlHiyPu0ktTsTcoK2dn0f", "title": "Chapter 09 Security / 第九章：安全性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 09 Security / 第九章：安全性", "section": "General Scenario", "url": "https://a1npn29y3xu.feishu.cn/wiki/VqGUwEHlHiyPu0ktTsTcoK2dn0f", "source_type": "docx", "n_chars": 524, "text": ", change the system's behavior, or reduce availability.未授权的尝试是指试图显示数据、修改或删除数据、访问系统服务、改变系统行为或降低系统可用性。Artifact / 组件System services: 数据在系统中的服务Data within the system: 系统内部的数据A component or resources of the system: 系统的组件或资源Data produced or consumed by the system: 系统产生或消耗的数据Environment / 环境The system is either online or offline, connected to or disconnected from a network, behind a firewall or open to a network, fully operational, partially operational, or not operational.系统可以是在线或离线、连接或断开网络、位于防火墙后面或开放于网络、完全正常运行、部分正常运行或完全不运行。"}
{"id": "docx::VqGUwEHlHiyPu0ktTsTcoK2dn0f::304", "page_id": "docx::VqGUwEHlHiyPu0ktTsTcoK2dn0f", "title": "Chapter 09 Security / 第九章：安全性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 09 Security / 第九章：安全性", "section": "General Scenario", "url": "https://a1npn29y3xu.feishu.cn/wiki/VqGUwEHlHiyPu0ktTsTcoK2dn0f", "source_type": "docx", "n_chars": 430, "text": "nal, partially operational, or not operational.系统可以是在线或离线、连接或断开网络、位于防火墙后面或开放于网络、完全正常运行、部分正常运行或完全不运行。Response / 反馈Transactions are carried out in a fashion such that data or services are protected from unauthorized access; data or services are not being manipulated without authorization; the data, resources, and system services will be available for legitimate use.事务以如下方式进行：数据或服务受到未授权访问的保护；数据或服务不会在未经授权的情况下被篡改；数据、资源和系统服务将可供合法使用。"}
{"id": "docx::VqGUwEHlHiyPu0ktTsTcoK2dn0f::305", "page_id": "docx::VqGUwEHlHiyPu0ktTsTcoK2dn0f", "title": "Chapter 09 Security / 第九章：安全性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 09 Security / 第九章：安全性", "section": "General Scenario", "url": "https://a1npn29y3xu.feishu.cn/wiki/VqGUwEHlHiyPu0ktTsTcoK2dn0f", "source_type": "docx", "n_chars": 700, "text": "ill be available for legitimate use.事务以如下方式进行：数据或服务受到未授权访问的保护；数据或服务不会在未经授权的情况下被篡改；数据、资源和系统服务将可供合法使用。The system tracks activities within it by:系统通过以下方式跟踪其内部活动：Recording access or modification / 记录访问或修改Recording attempts to access data, resources, or services / 记录访问数据、资源或服务的尝试Notifying appropriate entities when an apparent attack is occurring / 在明显的攻击发生时通知相关实体Response Measure / 反馈度量One or more of the following / 以下之一或多个How much of a system is compromised when a particular component or data value is compromised?当特定组件或数据值受到危害时，系统有多少部分被攻破？How much time has passed before an attack was detected?在攻击被发现之前，经过了多少时间？How many attacks were resisted?抵御了多少次攻击？How long does it take to recover from a successf"}
{"id": "docx::VqGUwEHlHiyPu0ktTsTcoK2dn0f::306", "page_id": "docx::VqGUwEHlHiyPu0ktTsTcoK2dn0f", "title": "Chapter 09 Security / 第九章：安全性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 09 Security / 第九章：安全性", "section": "General Scenario", "url": "https://a1npn29y3xu.feishu.cn/wiki/VqGUwEHlHiyPu0ktTsTcoK2dn0f", "source_type": "docx", "n_chars": 194, "text": "现之前，经过了多少时间？How many attacks were resisted?抵御了多少次攻击？How long does it take to recover from a successful attack?从一次成功的攻击中恢复需要多长时间？How much data is vulnerable to a particular attack?有多少数据对特定攻击是脆弱的？"}
{"id": "docx::VqGUwEHlHiyPu0ktTsTcoK2dn0f::307", "page_id": "docx::VqGUwEHlHiyPu0ktTsTcoK2dn0f", "title": "Chapter 09 Security / 第九章：安全性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 09 Security / 第九章：安全性", "section": "General Scenario/Sample / 示例", "url": "https://a1npn29y3xu.feishu.cn/wiki/VqGUwEHlHiyPu0ktTsTcoK2dn0f", "source_type": "docx", "n_chars": 659, "text": "\n\nA disgruntled employee from a remote location attempts to modify the pay rate table during normal operations. The system maintains an audit trail and the correct data is restored within a day.\n\n一名不满的员工从远程位置试图在正常操作期间修改工资表。系统保持审计记录，并在一天内恢复正确的数据。\n\n- Stimulus: unauthorized attempts to modify the pay rate table\n刺激：未授权的尝试修改工资表\n- Stimulus source: a disgruntled employee\n刺激源：一名不满的员工\n- Artifact: the system with pay rate table\n工件：包含工资表的系统\n- Environment: during normal operation\n环境：正常操作期间\n- Response: maintains an audit trail\n响应：保持审计记录\n- Response measure: correct data is restored within a day\n响应度量：在一天内恢复正确的数据"}
{"id": "docx::VqGUwEHlHiyPu0ktTsTcoK2dn0f::308", "page_id": "docx::VqGUwEHlHiyPu0ktTsTcoK2dn0f", "title": "Chapter 09 Security / 第九章：安全性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 09 Security / 第九章：安全性", "section": "Tactics/Tatics Tree", "url": "https://a1npn29y3xu.feishu.cn/wiki/VqGUwEHlHiyPu0ktTsTcoK2dn0f", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::VqGUwEHlHiyPu0ktTsTcoK2dn0f::309", "page_id": "docx::VqGUwEHlHiyPu0ktTsTcoK2dn0f", "title": "Chapter 09 Security / 第九章：安全性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 09 Security / 第九章：安全性", "section": "Tactics/Tatics Tree/省流：1453 君士坦丁（以下内容一点都不严谨，CS 学家和史学家同时震怒", "url": "https://a1npn29y3xu.feishu.cn/wiki/VqGUwEHlHiyPu0ktTsTcoK2dn0f", "source_type": "docx", "n_chars": 392, "text": "| 输入：攻击 | 奥斯曼攻击君士坦丁堡 |\n|-|-|\n| 检测攻击 | 发现奥斯曼人 |\n| ① 检测入侵 | 发现奥斯曼的帐营 |\n| ② 检测服务拒绝 | 护城河 |\n| ③ 验证消息完整性、检测消息延迟 | 军情是否有误 |\n| 抵御攻击 | 囤粮、囤士兵、拉雇佣兵 |\n| 对攻击作出反应 | 进行君士坦丁堡保卫战 |\n| 从攻击中恢复过来 | 保持作战记录，修复君士坦丁城 |\n| 输出：系统检测、抵抗、反应或恢复 | ~~君士坦丁永不陷落~~ [“去告诉全世界，最后的罗马人依然像两千年前一样勇敢”](https://www.bilibili.com/video/BV1PH4y157V6/?spm_id_from=333.337.search-card.all.click&vd_source=da1f2d78d73dfaae6ddfbcfe8e4801d8) |"}
{"id": "docx::VqGUwEHlHiyPu0ktTsTcoK2dn0f::310", "page_id": "docx::VqGUwEHlHiyPu0ktTsTcoK2dn0f", "title": "Chapter 09 Security / 第九章：安全性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 09 Security / 第九章：安全性", "section": "Tactics/Tatics Tree/Detect Attacks", "url": "https://a1npn29y3xu.feishu.cn/wiki/VqGUwEHlHiyPu0ktTsTcoK2dn0f", "source_type": "docx", "n_chars": 640, "text": "\n\n1. **Detect Intrusion / 检测入侵**\n\n- Definition: Compare network traffic or service request patterns within a system to a set of signatures or known patterns of malicious behavior stored in a database.\n定义：将系统内的网络流量或服务请求模式与存储在数据库中的已知恶意行为签名或模式进行比较。\n\n1. **Detect Service Denial / 检测服务拒绝**\n\n- Definition: Comparison of the pattern or signature of network traffic coming into a system to historic profiles of known Denial of Service (DoS) attacks.\n定义：将进入系统的网络流量模式或签名与已知的服务拒绝（DoS）攻击的历史资料进行比较。\n\n\n\n1. **Verify Message Integrity / 验证消息完整性**"}
{"id": "docx::VqGUwEHlHiyPu0ktTsTcoK2dn0f::311", "page_id": "docx::VqGUwEHlHiyPu0ktTsTcoK2dn0f", "title": "Chapter 09 Security / 第九章：安全性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 09 Security / 第九章：安全性", "section": "Tactics/Tatics Tree/Detect Attacks", "url": "https://a1npn29y3xu.feishu.cn/wiki/VqGUwEHlHiyPu0ktTsTcoK2dn0f", "source_type": "docx", "n_chars": 637, "text": "\n\n1. **Verify Message Integrity / 验证消息完整性**\n\n- Definition: Use techniques such as checksums or hash values to verify the integrity of messages, resource files, deployment files, and configuration files.\n定义：使用校验和或哈希值等技术来验证消息、资源文件、部署文件和配置文件的完整性。\n\n\n\n1. **Detect Message Delay / 检测消息延迟**\n\n- Definition: Check the time it takes to deliver a message; it is possible to detect suspicious timing behavior, such as a man-in-the-middle attack.\n定义：检查消息传递所需的时间，可以检测到可疑的时序行为，例如中间人攻击。\n\n"}
{"id": "docx::VqGUwEHlHiyPu0ktTsTcoK2dn0f::312", "page_id": "docx::VqGUwEHlHiyPu0ktTsTcoK2dn0f", "title": "Chapter 09 Security / 第九章：安全性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 09 Security / 第九章：安全性", "section": "Tactics/Tatics Tree/Resist Attacks", "url": "https://a1npn29y3xu.feishu.cn/wiki/VqGUwEHlHiyPu0ktTsTcoK2dn0f", "source_type": "docx", "n_chars": 680, "text": "\n\n\n\n\n\n\n\n1. **Identify Actors / 识别行为者**\n\n- Definition: Identify the source of any external input to the system.\n定义：识别系统的任何外部输入来源。\n\n1. **Authenticate Actors / 验证行为者**\n\n- Definition: Ensure that a user or remote computer is actually who or what it purports to be.\n定义：确保用户或远程计算机确实是其所声明的身份。\n\n1. **Authorize Actors / 授权行为者**\n\n- Definition: Ensuring that an authenticated actor has the rights to access and modify either data or services.\n定义：确保已验证的行为者具有访问和修改数据或服务的权限。"}
{"id": "docx::VqGUwEHlHiyPu0ktTsTcoK2dn0f::313", "page_id": "docx::VqGUwEHlHiyPu0ktTsTcoK2dn0f", "title": "Chapter 09 Security / 第九章：安全性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 09 Security / 第九章：安全性", "section": "Tactics/Tatics Tree/Resist Attacks", "url": "https://a1npn29y3xu.feishu.cn/wiki/VqGUwEHlHiyPu0ktTsTcoK2dn0f", "source_type": "docx", "n_chars": 681, "text": "ed actor has the rights to access and modify either data or services.\n定义：确保已验证的行为者具有访问和修改数据或服务的权限。\n\n1. **Limit Access / 限制访问**\n\n- Definition: Limiting access to resources such as memory, network connections, or access points.\n定义：限制对资源（如内存、网络连接或访问点）的访问。\n\n1. **Limit Exposure / 限制暴露**\n\n- Definition: Minimize the attack surface of a system by having the fewest possible number of access points.\n定义：通过减少访问点的数量来最小化系统的攻击面。\n- Example / 示例:\n- Firewall is a single point of access to the intranet.\n防火墙是访问内网的唯一入口。\n- Closing a port.\n关闭端口。\n\n1. **Passive Defense / 被动防御**\n\n- Definition: Techniques that reduce the chances of an attack succeeding without actively interfering with the attacker."}
{"id": "docx::VqGUwEHlHiyPu0ktTsTcoK2dn0f::314", "page_id": "docx::VqGUwEHlHiyPu0ktTsTcoK2dn0f", "title": "Chapter 09 Security / 第九章：安全性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 09 Security / 第九章：安全性", "section": "Tactics/Tatics Tree/Resist Attacks", "url": "https://a1npn29y3xu.feishu.cn/wiki/VqGUwEHlHiyPu0ktTsTcoK2dn0f", "source_type": "docx", "n_chars": 553, "text": "ues that reduce the chances of an attack succeeding without actively interfering with the attacker.\n定义：通过减少攻击成功的机会来避免攻击，而不是主动干扰攻击者。\n\n1. **Encrypt Data / 加密数据**\n\n- Definition: Apply some form of encryption to data and communication.\n定义：对数据和通信应用某种形式的加密。\n\n1. **Separate Entities / 分离实体**\n\n- Definition: Can be done through physical separation on different servers, or the use of virtual machines.\n定义：可以通过在不同服务器上的物理分离，或使用虚拟机来实现。\n\n1. **Change Default Settings / 更改默认设置**\n\n- Definition: Force the user to change settings assigned by default.\n定义：强制用户更改默认分配的设置。"}
{"id": "docx::VqGUwEHlHiyPu0ktTsTcoK2dn0f::315", "page_id": "docx::VqGUwEHlHiyPu0ktTsTcoK2dn0f", "title": "Chapter 09 Security / 第九章：安全性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 09 Security / 第九章：安全性", "section": "Tactics/Tatics Tree/React to Attacks", "url": "https://a1npn29y3xu.feishu.cn/wiki/VqGUwEHlHiyPu0ktTsTcoK2dn0f", "source_type": "docx", "n_chars": 518, "text": "1. **Revoke Access / 撤销访问权限**\n\n- Definition: Limit access to sensitive resources, even for normally legitimate users and uses, if an attack is suspected.\n定义：如果怀疑发生攻击，即使是正常的合法用户和用途，也要限制对敏感资源的访问。\n\n1. **Lock Computer / 锁定计算机**\n\n- Definition: Limit access to a resource if there are repeated failed attempts to access it.\n定义：如果多次尝试访问资源失败，则限制访问该资源。\n\n1. **Inform Actors / 通知行为者**\n\n- Definition: Notify operators, other personnel, or cooperating systems when an attack is suspected or detected.\n定义：当怀疑或检测到攻击时，通知操作员、其他人员或合作系统。"}
{"id": "docx::VqGUwEHlHiyPu0ktTsTcoK2dn0f::316", "page_id": "docx::VqGUwEHlHiyPu0ktTsTcoK2dn0f", "title": "Chapter 09 Security / 第九章：安全性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 09 Security / 第九章：安全性", "section": "Summary", "url": "https://a1npn29y3xu.feishu.cn/wiki/VqGUwEHlHiyPu0ktTsTcoK2dn0f", "source_type": "docx", "n_chars": 503, "text": "- Attacks against a system can be characterized as attacks against the confidentiality, integrity, or availability of a system.\n\n对系统的攻击可以被描述为对系统的机密性、完整性或可用性的攻击。\n\n- Identifying, authenticating, and authorizing actors are tactics intended to determine which users or systems are entitled to what kind of access to a system.\n\n识别、验证和授权行为者是旨在确定哪些用户或系统有权访问系统的哪些资源的策略。\n\n- Tactics exist to detect an attack, limit the spread of any attack, and to react and recover from an attack.\n\n存在用于检测攻击、限制攻击蔓延、以及应对和恢复攻击的策略。"}
{"id": "docx::MSJUwdBySidmXzk8yboc3zCMnVh::317", "page_id": "docx::MSJUwdBySidmXzk8yboc3zCMnVh", "title": "Chapter 10 Testability / 第十章：可测试性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 10 Testability / 第十章：可测试性", "section": "What is Software Testability?", "url": "https://a1npn29y3xu.feishu.cn/wiki/MSJUwdBySidmXzk8yboc3zCMnVh", "source_type": "docx", "n_chars": 606, "text": "\n\n• **Software testability** refers to the ease with which software can be made to demonstrate its faults through (typically execution-based) testing.\n\n软件的可测试性指的是软件能够通过（通常是执行基础的）测试来展示其缺陷的容易程度。\n\n• **Testability** refers to the probability that it will fail on its next test execution.\n\n可测试性指的是在下一次测试执行中失败的概率。\n\n• If a fault is present in a system, then we want it to fail during testing as quickly as possible.\n\n如果系统中存在故障，那么我们希望它在测试期间尽快失败。\n\n\n\n"}
{"id": "docx::MSJUwdBySidmXzk8yboc3zCMnVh::318", "page_id": "docx::MSJUwdBySidmXzk8yboc3zCMnVh", "title": "Chapter 10 Testability / 第十章：可测试性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 10 Testability / 第十章：可测试性", "section": "What is Software Testability?", "url": "https://a1npn29y3xu.feishu.cn/wiki/MSJUwdBySidmXzk8yboc3zCMnVh", "source_type": "docx", "n_chars": 363, "text": "ishu.cn/file/KDckbkVAEo4Z2kxm54UchuH6nS9)\n\n\n\nFor a system to be testable, it must be possible to *control* each component’s inputs (and possibly manipulate its internal state) and then to *observe* its outputs (and possibly its internal state).\n\n对于一个系统来说，要使其可测试，必须能够控制每个组件的输入（并且可能操纵其内部状态），然后观察它的输出（以及可能的内部状态）"}
{"id": "docx::MSJUwdBySidmXzk8yboc3zCMnVh::319", "page_id": "docx::MSJUwdBySidmXzk8yboc3zCMnVh", "title": "Chapter 10 Testability / 第十章：可测试性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 10 Testability / 第十章：可测试性", "section": "General Scenario / 通用场景", "url": "https://a1npn29y3xu.feishu.cn/wiki/MSJUwdBySidmXzk8yboc3zCMnVh", "source_type": "docx", "n_chars": 584, "text": "\n\n\n\nPortion of Scenario / 场景中的组成部分Possible Values / 可能的取值Source / 源头Unit testers / 单元测试人员Integration testers / 集成测试人员System testers / 系统测试人员Acceptance testers / 验收测试人员End users / 最终用户Either running tests manually or using automated testing tools / 无论是手动运行测试还是使用自动化测试工具。Stimulus / 激励A set of tests are executed due to the completion ofa codingincrement; the complete implementation ofthe system; or the delivery of the system to thecustomer由于完成编码增量；系统完全实现；或将系统交付给客户，所以执行一组测试。"}
{"id": "docx::MSJUwdBySidmXzk8yboc3zCMnVh::320", "page_id": "docx::MSJUwdBySidmXzk8yboc3zCMnVh", "title": "Chapter 10 Testability / 第十章：可测试性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 10 Testability / 第十章：可测试性", "section": "General Scenario / 通用场景", "url": "https://a1npn29y3xu.feishu.cn/wiki/MSJUwdBySidmXzk8yboc3zCMnVh", "source_type": "docx", "n_chars": 488, "text": "tation ofthe system; or the delivery of the system to thecustomer由于完成编码增量；系统完全实现；或将系统交付给客户，所以执行一组测试。Artifact / 组件The portion of the system being tested系统被测试的部分Environment / 环境design time, development time, compile time, integration time, deployment time, run time设计时间，开发时间，编译时间，集成时间，发布时间，运行时间Response / 反馈One of the following: execute tests and capture results; capture activity that resulted in the fault; control and monitor the state of the system以下选项之一：执行测试并捕获结果；捕获导致故障的活动；控制和监控系统的状态。"}
{"id": "docx::MSJUwdBySidmXzk8yboc3zCMnVh::321", "page_id": "docx::MSJUwdBySidmXzk8yboc3zCMnVh", "title": "Chapter 10 Testability / 第十章：可测试性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 10 Testability / 第十章：可测试性", "section": "General Scenario / 通用场景", "url": "https://a1npn29y3xu.feishu.cn/wiki/MSJUwdBySidmXzk8yboc3zCMnVh", "source_type": "docx", "n_chars": 475, "text": "lted in the fault; control and monitor the state of the system以下选项之一：执行测试并捕获结果；捕获导致故障的活动；控制和监控系统的状态。Response Measure / 反馈度量One or more of the following: effort to find a fault; effort to achieve a given percentage of state space coverage;probability of fault being revealed by the next test; time to perform tests; effort to detect faults; length of time to prepare for the test environment以下一项或多项：寻找故障所需的努力；实现特定状态空间覆盖率百分比所需的努力；下一次测试揭示故障的概率；执行测试所需的时间；检测故障所需的努力；准备测试环境所需的时间长度。"}
{"id": "docx::MSJUwdBySidmXzk8yboc3zCMnVh::322", "page_id": "docx::MSJUwdBySidmXzk8yboc3zCMnVh", "title": "Chapter 10 Testability / 第十章：可测试性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 10 Testability / 第十章：可测试性", "section": "General Scenario / 通用场景/Sample / 示例", "url": "https://a1npn29y3xu.feishu.cn/wiki/MSJUwdBySidmXzk8yboc3zCMnVh", "source_type": "docx", "n_chars": 541, "text": "The unit tester completes a code unit during development and performs a test sequence whose results are captured and that gives 85% path coverage within 3 hours of testing.\n\n单元测试员在开发过程中完成一个代码单元，并执行一个测试序列，捕获其结果，并在 3 小时的测试内达到 85% 的路径覆盖率。\n\n- Source / 来源:\n\n - Unit tester\n 单元测试员\n- Stimulus / 刺激:\n\n - Code unit completed\n 代码单元完成\n- Artifact / 工件:\n\n - Code unit\n 代码单元\n- Environment / 环境:\n\n - Development\n 开发环境\n- Response / 响应:\n\n - Capture results\n 捕获结果\n- Response measure / 响应度量:\n\n - 85% path coverage in three hours\n 在三小时内达到 85% 的路径覆盖率"}
{"id": "docx::MSJUwdBySidmXzk8yboc3zCMnVh::323", "page_id": "docx::MSJUwdBySidmXzk8yboc3zCMnVh", "title": "Chapter 10 Testability / 第十章：可测试性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 10 Testability / 第十章：可测试性", "section": "Tactics/Goal", "url": "https://a1npn29y3xu.feishu.cn/wiki/MSJUwdBySidmXzk8yboc3zCMnVh", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::MSJUwdBySidmXzk8yboc3zCMnVh::324", "page_id": "docx::MSJUwdBySidmXzk8yboc3zCMnVh", "title": "Chapter 10 Testability / 第十章：可测试性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 10 Testability / 第十章：可测试性", "section": "Tactics/Tatics Tree", "url": "https://a1npn29y3xu.feishu.cn/wiki/MSJUwdBySidmXzk8yboc3zCMnVh", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::MSJUwdBySidmXzk8yboc3zCMnVh::325", "page_id": "docx::MSJUwdBySidmXzk8yboc3zCMnVh", "title": "Chapter 10 Testability / 第十章：可测试性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 10 Testability / 第十章：可测试性", "section": "Tactics/Tatics Tree/Control and Observe System State / 控制并且观察系统状态", "url": "https://a1npn29y3xu.feishu.cn/wiki/MSJUwdBySidmXzk8yboc3zCMnVh", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::MSJUwdBySidmXzk8yboc3zCMnVh::326", "page_id": "docx::MSJUwdBySidmXzk8yboc3zCMnVh", "title": "Chapter 10 Testability / 第十章：可测试性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 10 Testability / 第十章：可测试性", "section": "Tactics/Tatics Tree/Control and Observe System State / 控制并且观察系统状态/Specialized Interfaces / 专用接口", "url": "https://a1npn29y3xu.feishu.cn/wiki/MSJUwdBySidmXzk8yboc3zCMnVh", "source_type": "docx", "n_chars": 282, "text": "- To control or capture variable values for a component through normal execution. / 通过正常执行来控制或捕获组件的变量值。\n- A *set* and *get* method of variables / 变量的设置和获取方法\n- A *report* method that returns state of the object / 返回对象状态的报告方法\n- A *reset* method to set the internal state / 设置内部状态的重置方法"}
{"id": "docx::MSJUwdBySidmXzk8yboc3zCMnVh::327", "page_id": "docx::MSJUwdBySidmXzk8yboc3zCMnVh", "title": "Chapter 10 Testability / 第十章：可测试性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 10 Testability / 第十章：可测试性", "section": "Tactics/Tatics Tree/Control and Observe System State / 控制并且观察系统状态/Record/Playback / 录制/回放", "url": "https://a1npn29y3xu.feishu.cn/wiki/MSJUwdBySidmXzk8yboc3zCMnVh", "source_type": "docx", "n_chars": 114, "text": "Capturing information crossing an interface and using it as input for further testing.\n\n- 捕获穿过接口的信息，并将其用作进一步测试的输入。"}
{"id": "docx::MSJUwdBySidmXzk8yboc3zCMnVh::328", "page_id": "docx::MSJUwdBySidmXzk8yboc3zCMnVh", "title": "Chapter 10 Testability / 第十章：可测试性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 10 Testability / 第十章：可测试性", "section": "Tactics/Tatics Tree/Control and Observe System State / 控制并且观察系统状态/Localize State Storage / 本地化状态存储", "url": "https://a1npn29y3xu.feishu.cn/wiki/MSJUwdBySidmXzk8yboc3zCMnVh", "source_type": "docx", "n_chars": 158, "text": "To start a system in an arbitrary state for a test, it is most convenient if that state is stored in a single place.\n\n- 为了在测试中从一个任意状态启动系统，如果该状态存储在一个地方，将会非常方便。"}
{"id": "docx::MSJUwdBySidmXzk8yboc3zCMnVh::329", "page_id": "docx::MSJUwdBySidmXzk8yboc3zCMnVh", "title": "Chapter 10 Testability / 第十章：可测试性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 10 Testability / 第十章：可测试性", "section": "Tactics/Tatics Tree/Control and Observe System State / 控制并且观察系统状态/Sandbox / 沙箱", "url": "https://a1npn29y3xu.feishu.cn/wiki/MSJUwdBySidmXzk8yboc3zCMnVh", "source_type": "docx", "n_chars": 87, "text": "Isolate the system from the real world to enable experimentation.\n\n- 将系统与现实世界隔离，以便进行实验。"}
{"id": "docx::MSJUwdBySidmXzk8yboc3zCMnVh::330", "page_id": "docx::MSJUwdBySidmXzk8yboc3zCMnVh", "title": "Chapter 10 Testability / 第十章：可测试性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 10 Testability / 第十章：可测试性", "section": "Tactics/Tatics Tree/Control and Observe System State / 控制并且观察系统状态/Executable Assertions / 可执行断言", "url": "https://a1npn29y3xu.feishu.cn/wiki/MSJUwdBySidmXzk8yboc3zCMnVh", "source_type": "docx", "n_chars": 154, "text": "Assertions are hand coded and placed at desired locations to indicate when and where a program is in a faulty state.\n\n- 断言是手工编码并放置在期望的位置，用以指示程序何时何地处于错误状态。"}
{"id": "docx::MSJUwdBySidmXzk8yboc3zCMnVh::331", "page_id": "docx::MSJUwdBySidmXzk8yboc3zCMnVh", "title": "Chapter 10 Testability / 第十章：可测试性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 10 Testability / 第十章：可测试性", "section": "Tactics/Tatics Tree/Limit Complexity / 限制复杂度", "url": "https://a1npn29y3xu.feishu.cn/wiki/MSJUwdBySidmXzk8yboc3zCMnVh", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::MSJUwdBySidmXzk8yboc3zCMnVh::332", "page_id": "docx::MSJUwdBySidmXzk8yboc3zCMnVh", "title": "Chapter 10 Testability / 第十章：可测试性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 10 Testability / 第十章：可测试性", "section": "Summary", "url": "https://a1npn29y3xu.feishu.cn/wiki/MSJUwdBySidmXzk8yboc3zCMnVh", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::UanCwfubMiNM1pkUADKcHBIjncg::333", "page_id": "docx::UanCwfubMiNM1pkUADKcHBIjncg", "title": "Chapter 11 Usability / 第十一章：易用性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 11 Usability / 第十一章：易用性", "section": "What is Usability? / 什么是易用性？", "url": "https://a1npn29y3xu.feishu.cn/wiki/UanCwfubMiNM1pkUADKcHBIjncg", "source_type": "docx", "n_chars": 692, "text": "\n\n• **Usability** is concerned with how easy it is for the user to accomplish a desired task and the user support the system provides / 可用性关注的是用户完成期望任务的难易程度以及系统提供的用户体验支持。\n\n• **Usability** is one of the cheapest and easiest ways to improve a system’s quality / 可用性是提高系统质量最经济、最简单的方法之一。\n\n\n\nUsability comprises the following areas: / 可用性包括以下几个方面：\n\n- Using a system efficiently. / 高效使用系统。\n- Learning system features. / 学习系统特性。\n- Minimizing the impact of errors. / 最小化错误的影响。\n- Adapting the system to user needs. / 使系统适应用户需求。\n- Increasing confidence and satisfaction. / 提高信心和满意度。"}
{"id": "docx::UanCwfubMiNM1pkUADKcHBIjncg::334", "page_id": "docx::UanCwfubMiNM1pkUADKcHBIjncg", "title": "Chapter 11 Usability / 第十一章：易用性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 11 Usability / 第十一章：易用性", "section": "General Scenario / 通用场景", "url": "https://a1npn29y3xu.feishu.cn/wiki/UanCwfubMiNM1pkUADKcHBIjncg", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::UanCwfubMiNM1pkUADKcHBIjncg::335", "page_id": "docx::UanCwfubMiNM1pkUADKcHBIjncg", "title": "Chapter 11 Usability / 第十一章：易用性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 11 Usability / 第十一章：易用性", "section": "General Scenario / 通用场景/Sample / 示例", "url": "https://a1npn29y3xu.feishu.cn/wiki/UanCwfubMiNM1pkUADKcHBIjncg", "source_type": "docx", "n_chars": 406, "text": "The user downloads a new application and is using it productively after two minutes of experimentation.\n\n用户下载一个新应用程序，并在两分钟的试验后开始高效使用它。\n\n- Source / 来源: User\n用户\n- Stimulus / 刺激: Download a new application\n下载新应用程序\n- Artifact / 工件: System\n系统\n- Environment / 环境: Runtime\n运行时\n- Response / 响应: User uses application productively\n用户高效使用应用程序\n- Response measure / 响应度量: Within two minutes of experimentation\n在两分钟的试验内"}
{"id": "docx::UanCwfubMiNM1pkUADKcHBIjncg::336", "page_id": "docx::UanCwfubMiNM1pkUADKcHBIjncg", "title": "Chapter 11 Usability / 第十一章：易用性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 11 Usability / 第十一章：易用性", "section": "Tactics/Tatics Tree", "url": "https://a1npn29y3xu.feishu.cn/wiki/UanCwfubMiNM1pkUADKcHBIjncg", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::UanCwfubMiNM1pkUADKcHBIjncg::337", "page_id": "docx::UanCwfubMiNM1pkUADKcHBIjncg", "title": "Chapter 11 Usability / 第十一章：易用性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 11 Usability / 第十一章：易用性", "section": "Tactics/Tatics Tree/Support User Initiative / 支持用户计划", "url": "https://a1npn29y3xu.feishu.cn/wiki/UanCwfubMiNM1pkUADKcHBIjncg", "source_type": "docx", "n_chars": 601, "text": "\n\n- Cancel: the system must listen for the cancel request; the command being canceled must be terminated; resources used must be freed; and collaborating components must be informed. / 取消：系统必须监听取消请求；被取消的命令必须终止；使用的资源必须释放；并且必须通知协作组件。\n- Pause/Resume: temporarily free resources so that they may be re-allocated to other tasks. Used for long-running operations. / 暂停/恢复：暂时释放资源，以便它们可以重新分配给其他任务。用于长时间运行的操作。\n- Restore: maintain a sufficient amount of information about system state so that an earlier state may be restored. / 恢复：维护足够的系统状态信息，以便可以恢复到早期状态。"}
{"id": "docx::UanCwfubMiNM1pkUADKcHBIjncg::338", "page_id": "docx::UanCwfubMiNM1pkUADKcHBIjncg", "title": "Chapter 11 Usability / 第十一章：易用性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 11 Usability / 第十一章：易用性", "section": "Tactics/Tatics Tree/Support User Initiative / 支持用户计划", "url": "https://a1npn29y3xu.feishu.cn/wiki/UanCwfubMiNM1pkUADKcHBIjncg", "source_type": "docx", "n_chars": 316, "text": "ormation about system state so that an earlier state may be restored. / 恢复：维护足够的系统状态信息，以便可以恢复到早期状态。\n- Aggregate: ability to aggregate lower-level objects into a group, so that a user operation may be applied to the group, freeing the user from repetitive operations. / 聚合：能够将低级别的对象聚合成一个组，这样用户操作可以应用于该组，从而免除用户重复操作的麻烦。"}
{"id": "docx::UanCwfubMiNM1pkUADKcHBIjncg::339", "page_id": "docx::UanCwfubMiNM1pkUADKcHBIjncg", "title": "Chapter 11 Usability / 第十一章：易用性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 11 Usability / 第十一章：易用性", "section": "Tactics/Tatics Tree/Support System Initiative / 支持系统计划", "url": "https://a1npn29y3xu.feishu.cn/wiki/UanCwfubMiNM1pkUADKcHBIjncg", "source_type": "docx", "n_chars": 457, "text": "\n\n• Maintain Task Model: determines context so the system can have some idea of what the user is attempting and provide assistance. / 维护任务模型：确定上下文，以便系统能够了解用户尝试进行的操作并提供帮助。\n\n• Maintain System Model: system maintains an explicit model of itself. This is used to determine expected system behavior so that appropriate feedback can be given to the user. / 维护系统模型：系统维护一个关于自身的明确模型。这用于确定预期的系统行为，以便能够向用户提供适当的反馈。"}
{"id": "docx::UanCwfubMiNM1pkUADKcHBIjncg::340", "page_id": "docx::UanCwfubMiNM1pkUADKcHBIjncg", "title": "Chapter 11 Usability / 第十一章：易用性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 11 Usability / 第十一章：易用性", "section": "Summary", "url": "https://a1npn29y3xu.feishu.cn/wiki/UanCwfubMiNM1pkUADKcHBIjncg", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::AsKyw443niuYJ1ksicFcQg01nXc::341", "page_id": "docx::AsKyw443niuYJ1ksicFcQg01nXc", "title": "Chapter 12 Other Attributes / 第十二章：其他质量属性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 12 Other Attributes / 第十二章：其他质量属性", "section": "Chapter 12 Other Attributes / 第十二章：其他质量属性", "url": "https://a1npn29y3xu.feishu.cn/wiki/AsKyw443niuYJ1ksicFcQg01nXc", "source_type": "docx", "n_chars": 682, "text": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::AsKyw443niuYJ1ksicFcQg01nXc::342", "page_id": "docx::AsKyw443niuYJ1ksicFcQg01nXc", "title": "Chapter 12 Other Attributes / 第十二章：其他质量属性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 12 Other Attributes / 第十二章：其他质量属性", "section": "Chapter 12 Other Attributes / 第十二章：其他质量属性", "url": "https://a1npn29y3xu.feishu.cn/wiki/AsKyw443niuYJ1ksicFcQg01nXc", "source_type": "docx", "n_chars": 269, "text": "ishu.cn/file/RybQbjLP5oml0LxsVH0chiGNnye)\n\n\n\n\n\n\n\n"}
{"id": "docx::AsKyw443niuYJ1ksicFcQg01nXc::343", "page_id": "docx::AsKyw443niuYJ1ksicFcQg01nXc", "title": "Chapter 12 Other Attributes / 第十二章：其他质量属性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 12 Other Attributes / 第十二章：其他质量属性", "section": "Chapter 12 Other Attributes / 第十二章：其他质量属性/**Functional Suitability / 功能适用性**", "url": "https://a1npn29y3xu.feishu.cn/wiki/AsKyw443niuYJ1ksicFcQg01nXc", "source_type": "docx", "n_chars": 649, "text": "This characteristic represents the degree to which a product or system provides functions that meet stated and implied needs when used under specified conditions. This characteristic is composed of the following sub-characteristics.\n**这一特性表示产品或系统在特定条件下提供的功能满足明确和隐含需求的程度。该特性由以下子特性组成。**\n\n- **Functional completeness / 功能完整性**\n Degree to which the set of functions covers all the specified tasks and intended users' objectives.\n**功能集覆盖所有指定任务和预期用户目标的程度。**\n- **Functional correctness / 功能正确性**\n Degree to which a product or system provides accurate results when used by intended users.\n**产品或系统在预期用户使用时提供准确结果的程度。**\n- **Functional appropriateness / 功能适当性**"}
{"id": "docx::AsKyw443niuYJ1ksicFcQg01nXc::344", "page_id": "docx::AsKyw443niuYJ1ksicFcQg01nXc", "title": "Chapter 12 Other Attributes / 第十二章：其他质量属性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 12 Other Attributes / 第十二章：其他质量属性", "section": "Chapter 12 Other Attributes / 第十二章：其他质量属性/**Functional Suitability / 功能适用性**", "url": "https://a1npn29y3xu.feishu.cn/wiki/AsKyw443niuYJ1ksicFcQg01nXc", "source_type": "docx", "n_chars": 219, "text": "s when used by intended users.\n**产品或系统在预期用户使用时提供准确结果的程度。**\n- **Functional appropriateness / 功能适当性**\n Degree to which the functions facilitate the accomplishment of specified tasks and objectives.\n**功能在完成指定任务和目标中的促进程度。**"}
{"id": "docx::AsKyw443niuYJ1ksicFcQg01nXc::345", "page_id": "docx::AsKyw443niuYJ1ksicFcQg01nXc", "title": "Chapter 12 Other Attributes / 第十二章：其他质量属性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 12 Other Attributes / 第十二章：其他质量属性", "section": "Chapter 12 Other Attributes / 第十二章：其他质量属性/**Performance Efficiency / 性能效率**", "url": "https://a1npn29y3xu.feishu.cn/wiki/AsKyw443niuYJ1ksicFcQg01nXc", "source_type": "docx", "n_chars": 655, "text": "This characteristic represents the degree to which a product performs its functions within specified time and throughput parameters and is efficient in the use of resources (such as CPU, memory, storage, network devices, energy, materials, etc.) under specified conditions. This characteristic is composed of the following sub-characteristics.\n**这一特性表示产品在特定时间和吞吐量参数内执行其功能的效率，并在特定条件下有效利用资源（如 CPU、内存、存储、网络设备、能源、材料等）。该特性由以下子特性组成。**\n\n- **Time behavior / 时间行为**\n Degree to which the response time and throughput rates of a product or system, when performing its functions, meet requirements.\n**产品或系统在执行功能时，其响应时间和吞吐率满足需求的程度。**\n- **Resource utilization / 资源利用率**"}
{"id": "docx::AsKyw443niuYJ1ksicFcQg01nXc::346", "page_id": "docx::AsKyw443niuYJ1ksicFcQg01nXc", "title": "Chapter 12 Other Attributes / 第十二章：其他质量属性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 12 Other Attributes / 第十二章：其他质量属性", "section": "Chapter 12 Other Attributes / 第十二章：其他质量属性/**Performance Efficiency / 性能效率**", "url": "https://a1npn29y3xu.feishu.cn/wiki/AsKyw443niuYJ1ksicFcQg01nXc", "source_type": "docx", "n_chars": 399, "text": "functions, meet requirements.\n**产品或系统在执行功能时，其响应时间和吞吐率满足需求的程度。**\n- **Resource utilization / 资源利用率**\n Degree to which the amounts and types of resources used by a product or system, when performing its functions, meet requirements.\n**产品或系统在执行功能时，所使用的资源量和资源类型满足需求的程度。**\n- **Capacity / 容量**\n Degree to which the maximum limits of a product or system parameter meet requirements.\n**产品或系统参数的最大限制满足需求的程度。**"}
{"id": "docx::AsKyw443niuYJ1ksicFcQg01nXc::347", "page_id": "docx::AsKyw443niuYJ1ksicFcQg01nXc", "title": "Chapter 12 Other Attributes / 第十二章：其他质量属性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 12 Other Attributes / 第十二章：其他质量属性", "section": "Chapter 12 Other Attributes / 第十二章：其他质量属性/**Compatibility / 兼容性**", "url": "https://a1npn29y3xu.feishu.cn/wiki/AsKyw443niuYJ1ksicFcQg01nXc", "source_type": "docx", "n_chars": 649, "text": "Degree to which a product, system, or component can exchange information with other products, systems, or components, and/or perform its required functions while sharing the same common environment and resources. This characteristic is composed of the following sub-characteristics.\n**产品、系统或组件在共享相同的公共环境和资源时，与其他产品、系统或组件交换信息或执行所需功能的程度。该特性由以下子特性组成。**\n\n- **Co-existence / 共存性**\n Degree to which a product can perform its required functions efficiently while sharing a common environment and resources with other products, without detrimental impact on any other product.\n**产品在共享公共环境和资源时，与其他产品共存并有效执行所需功能的程度，不对其他产品产生不利影响。**\n- **Interoperability / 互操作性**"}
{"id": "docx::AsKyw443niuYJ1ksicFcQg01nXc::348", "page_id": "docx::AsKyw443niuYJ1ksicFcQg01nXc", "title": "Chapter 12 Other Attributes / 第十二章：其他质量属性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 12 Other Attributes / 第十二章：其他质量属性", "section": "Chapter 12 Other Attributes / 第十二章：其他质量属性/**Compatibility / 兼容性**", "url": "https://a1npn29y3xu.feishu.cn/wiki/AsKyw443niuYJ1ksicFcQg01nXc", "source_type": "docx", "n_chars": 287, "text": "ny other product.\n**产品在共享公共环境和资源时，与其他产品共存并有效执行所需功能的程度，不对其他产品产生不利影响。**\n- **Interoperability / 互操作性**\n Degree to which a system, product, or component can exchange information with other products and mutually use the information that has been exchanged.\n**系统、产品或组件与其他产品交换信息并互相利用已交换信息的程度。**"}
{"id": "docx::AsKyw443niuYJ1ksicFcQg01nXc::349", "page_id": "docx::AsKyw443niuYJ1ksicFcQg01nXc", "title": "Chapter 12 Other Attributes / 第十二章：其他质量属性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 12 Other Attributes / 第十二章：其他质量属性", "section": "Chapter 12 Other Attributes / 第十二章：其他质量属性/**Interaction Capability / 交互能力**", "url": "https://a1npn29y3xu.feishu.cn/wiki/AsKyw443niuYJ1ksicFcQg01nXc", "source_type": "docx", "n_chars": 695, "text": "Degree to which a product or system can be interacted with by specified users to exchange information via the user interface to complete specific tasks in a variety of contexts of use. This characteristic is composed of the following sub-characteristics.\n**产品或系统在特定的使用情境下，用户通过用户界面与其交互并完成特定任务的能力。该特性由以下子特性组成。**\n\n- **Appropriateness recognizability / 适当性识别度**\n Degree to which users can recognize whether a product or system is appropriate for their needs.\n**用户识别产品或系统是否适合其需求的程度。**\n- **Learnability / 可学习性**\n Degree to which the functions of a product or system can be learned to be used by specified users within a specified amount of time.\n**用户在指定时间内学习并使用产品或系统功能的难易程度。**\n- **Operability / 可操作性**"}
{"id": "docx::AsKyw443niuYJ1ksicFcQg01nXc::350", "page_id": "docx::AsKyw443niuYJ1ksicFcQg01nXc", "title": "Chapter 12 Other Attributes / 第十二章：其他质量属性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 12 Other Attributes / 第十二章：其他质量属性", "section": "Chapter 12 Other Attributes / 第十二章：其他质量属性/**Interaction Capability / 交互能力**", "url": "https://a1npn29y3xu.feishu.cn/wiki/AsKyw443niuYJ1ksicFcQg01nXc", "source_type": "docx", "n_chars": 575, "text": "ed users within a specified amount of time.\n**用户在指定时间内学习并使用产品或系统功能的难易程度。**\n- **Operability / 可操作性**\n Degree to which a product or system has attributes that make it easy to operate and control.\n**产品或系统具有易于操作和控制的属性的程度。**\n- **User error protection / 用户错误保护**\n Degree to which a system prevents users from operating errors.\n**系统防止用户操作错误的程度。**\n- **User engagement / 用户参与度**\n Degree to which a user interface presents functions and information in an inviting and motivating manner, encouraging continued interaction.\n**用户界面以吸引人且激励性的方式呈现功能和信息，鼓励用户持续交互的程度。**\n- **Inclusivity / 包容性**"}
{"id": "docx::AsKyw443niuYJ1ksicFcQg01nXc::351", "page_id": "docx::AsKyw443niuYJ1ksicFcQg01nXc", "title": "Chapter 12 Other Attributes / 第十二章：其他质量属性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 12 Other Attributes / 第十二章：其他质量属性", "section": "Chapter 12 Other Attributes / 第十二章：其他质量属性/**Interaction Capability / 交互能力**", "url": "https://a1npn29y3xu.feishu.cn/wiki/AsKyw443niuYJ1ksicFcQg01nXc", "source_type": "docx", "n_chars": 613, "text": "encouraging continued interaction.\n**用户界面以吸引人且激励性的方式呈现功能和信息，鼓励用户持续交互的程度。**\n- **Inclusivity / 包容性**\n Degree to which a product or system can be used by people of various backgrounds (such as people of various ages, abilities, cultures, ethnicities, languages, genders, economic situations, etc.).\n**产品或系统能被不同背景（如年龄、能力、文化、民族、语言、性别、经济状况等）的人群使用的程度。**\n- **User assistance / 用户帮助**\n Degree to which a product can be used by people with the widest range of characteristics and capabilities to achieve specified goals in a specified context of use.\n**产品帮助不同特征和能力的用户在指定的使用情境中实现指定目标的程度。**\n- **Self-descriptiveness / 自我描述性**"}
{"id": "docx::AsKyw443niuYJ1ksicFcQg01nXc::352", "page_id": "docx::AsKyw443niuYJ1ksicFcQg01nXc", "title": "Chapter 12 Other Attributes / 第十二章：其他质量属性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 12 Other Attributes / 第十二章：其他质量属性", "section": "Chapter 12 Other Attributes / 第十二章：其他质量属性/**Interaction Capability / 交互能力**", "url": "https://a1npn29y3xu.feishu.cn/wiki/AsKyw443niuYJ1ksicFcQg01nXc", "source_type": "docx", "n_chars": 447, "text": "specified context of use.\n**产品帮助不同特征和能力的用户在指定的使用情境中实现指定目标的程度。**\n- **Self-descriptiveness / 自我描述性**\n Degree to which a product presents appropriate information, where needed by the user, to make its capabilities and use immediately obvious to the user without excessive interactions with the product or other resources (such as user documentation, help desks, or other users).\n**产品在需要时呈现适当的信息，使其功能和使用方法无需过多与产品或其他资源（如用户文档、帮助台或其他用户）交互，即可让用户立即理解的程度。**"}
{"id": "docx::AsKyw443niuYJ1ksicFcQg01nXc::353", "page_id": "docx::AsKyw443niuYJ1ksicFcQg01nXc", "title": "Chapter 12 Other Attributes / 第十二章：其他质量属性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 12 Other Attributes / 第十二章：其他质量属性", "section": "Chapter 12 Other Attributes / 第十二章：其他质量属性/**Reliability / 可靠性**", "url": "https://a1npn29y3xu.feishu.cn/wiki/AsKyw443niuYJ1ksicFcQg01nXc", "source_type": "docx", "n_chars": 617, "text": "Degree to which a system, product, or component performs specified functions under specified conditions for a specified period of time. This characteristic is composed of the following sub-characteristics.\n**系统、产品或组件在特定条件下、在指定时间段内执行指定功能的能力。该特性由以下子特性组成。**\n\n- **Faultlessness / 无故障性**\n Degree to which a system, product, or component performs specified functions without fault under normal operation.\n**系统、产品或组件在正常操作下无故障地执行指定功能的程度。**\n- **Availability / 可用性**\n Degree to which a system, product, or component is operational and accessible when required for use.\n**系统、产品或组件在需要时可操作并可以访问的程度。**\n- **Fault tolerance / 故障容忍性**"}
{"id": "docx::AsKyw443niuYJ1ksicFcQg01nXc::354", "page_id": "docx::AsKyw443niuYJ1ksicFcQg01nXc", "title": "Chapter 12 Other Attributes / 第十二章：其他质量属性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 12 Other Attributes / 第十二章：其他质量属性", "section": "Chapter 12 Other Attributes / 第十二章：其他质量属性/**Reliability / 可靠性**", "url": "https://a1npn29y3xu.feishu.cn/wiki/AsKyw443niuYJ1ksicFcQg01nXc", "source_type": "docx", "n_chars": 510, "text": "al and accessible when required for use.\n**系统、产品或组件在需要时可操作并可以访问的程度。**\n- **Fault tolerance / 故障容忍性**\n Degree to which a system, product, or component operates as intended despite the presence of hardware or software faults.\n**系统、产品或组件在硬件或软件故障存在的情况下仍能按预期工作 的程度。**\n- **Recoverability / 恢复性**\n Degree to which, in the event of an interruption or a failure, a product or system can recover the data directly affected and re-establish the desired state of the system.\n**在中断或故障发生时，产品或系统能够恢复直接受影响的数据，并重新建立系统的期望状态的程度。**"}
{"id": "docx::AsKyw443niuYJ1ksicFcQg01nXc::355", "page_id": "docx::AsKyw443niuYJ1ksicFcQg01nXc", "title": "Chapter 12 Other Attributes / 第十二章：其他质量属性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 12 Other Attributes / 第十二章：其他质量属性", "section": "Chapter 12 Other Attributes / 第十二章：其他质量属性/**Security / 安全性**", "url": "https://a1npn29y3xu.feishu.cn/wiki/AsKyw443niuYJ1ksicFcQg01nXc", "source_type": "docx", "n_chars": 597, "text": "Degree to which a product or system defends against attack patterns by malicious actors and protects information and data so that persons or other products or systems have the degree of data access appropriate to their types and levels of authorization. This characteristic is composed of the following sub-characteristics.\n**产品或系统防范恶意行为者攻击模式，保护信息和数据，以确保各方（人或其他产品、系统）对数据的访问权限与其授权类型和级别相适应。该特性由以下子特性组成。**\n\n- **Confidentiality / 保密性**\n The degree to which a product or system ensures that data are accessible only to those authorized to have access.\n**产品或系统确保数据仅对授权访问的人员可用的程度。**\n- **Integrity / 完整性**"}
{"id": "docx::AsKyw443niuYJ1ksicFcQg01nXc::356", "page_id": "docx::AsKyw443niuYJ1ksicFcQg01nXc", "title": "Chapter 12 Other Attributes / 第十二章：其他质量属性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 12 Other Attributes / 第十二章：其他质量属性", "section": "Chapter 12 Other Attributes / 第十二章：其他质量属性/**Security / 安全性**", "url": "https://a1npn29y3xu.feishu.cn/wiki/AsKyw443niuYJ1ksicFcQg01nXc", "source_type": "docx", "n_chars": 688, "text": "essible only to those authorized to have access.\n**产品或系统确保数据仅对授权访问的人员可用的程度。**\n- **Integrity / 完整性**\n Degree to which a system, product, or component ensures that the state of its system and data are protected from unauthorized modification or deletion, either by malicious action or computer error.\n**系统、产品或组件确保其系统和数据的状态不受未经授权的修改或删除（无论是恶意行为还是计算机错误）影响的程度。**\n- **Non-repudiation / 不可否认性**\n Degree to which actions or events can be proven to have taken place so that the events or actions cannot be repudiated later.\n**能够证明某些行为或事件已经发生，以确保这些行为或事件无法被事后否认的程度。**\n- **Accountability / 责任追踪**\n Degree to which the actions of an entity can be traced uniquely to the entity.\n**实体的行为能够被唯一追踪到该实体的程度。**"}
{"id": "docx::AsKyw443niuYJ1ksicFcQg01nXc::357", "page_id": "docx::AsKyw443niuYJ1ksicFcQg01nXc", "title": "Chapter 12 Other Attributes / 第十二章：其他质量属性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 12 Other Attributes / 第十二章：其他质量属性", "section": "Chapter 12 Other Attributes / 第十二章：其他质量属性/**Security / 安全性**", "url": "https://a1npn29y3xu.feishu.cn/wiki/AsKyw443niuYJ1ksicFcQg01nXc", "source_type": "docx", "n_chars": 405, "text": "ee to which the actions of an entity can be traced uniquely to the entity.\n**实体的行为能够被唯一追踪到该实体的程度。**\n- **Authenticity / 真实性**\n Degree to which the identity of a subject or resource can be proved to be the one claimed.\n**能够证明某个主体或资源的身份确实是其所声称的身份的程度。**\n- **Resistance / 抵抗力**\n Degree to which the product or system sustains operations while under attack from a malicious actor.\n**产品或系统在遭遇恶意行为者攻击时仍能持续运作的程度。**"}
{"id": "docx::AsKyw443niuYJ1ksicFcQg01nXc::358", "page_id": "docx::AsKyw443niuYJ1ksicFcQg01nXc", "title": "Chapter 12 Other Attributes / 第十二章：其他质量属性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 12 Other Attributes / 第十二章：其他质量属性", "section": "Chapter 12 Other Attributes / 第十二章：其他质量属性/**Maintainability / 可维护性**", "url": "https://a1npn29y3xu.feishu.cn/wiki/AsKyw443niuYJ1ksicFcQg01nXc", "source_type": "docx", "n_chars": 685, "text": "This characteristic represents the degree of effectiveness and efficiency with which a product or system can be modified to improve it, correct it, or adapt it to changes in environment, and in requirements. This characteristic is composed of the following sub-characteristics.\n**该特性代表产品或系统在提高、修正或适应环境变化及需求变化方面的有效性和效率。该特性由以下子特性组成。**\n\n- **Modularity / 模块化**\n Degree to which a system or computer program is composed of discrete components such that a change to one component has minimal impact on other components.\n**系统或计算机程序由离散组件组成，某个组件的变更对其他组件的影响最小的程度。**\n- **Reusability / 可重用性**\n Degree to which a product can be used as an asset in more than one system, or in building other assets."}
{"id": "docx::AsKyw443niuYJ1ksicFcQg01nXc::359", "page_id": "docx::AsKyw443niuYJ1ksicFcQg01nXc", "title": "Chapter 12 Other Attributes / 第十二章：其他质量属性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 12 Other Attributes / 第十二章：其他质量属性", "section": "Chapter 12 Other Attributes / 第十二章：其他质量属性/**Maintainability / 可维护性**", "url": "https://a1npn29y3xu.feishu.cn/wiki/AsKyw443niuYJ1ksicFcQg01nXc", "source_type": "docx", "n_chars": 689, "text": "ee to which a product can be used as an asset in more than one system, or in building other assets.\n**产品在多个系统中作为资产使用，或用于构建其他资产的程度。**\n- **Analysability / 可分析性**\n Degree of effectiveness and efficiency with which it is possible to assess the impact on a product or system of an intended change to one or more of its parts, or diagnose a product for deficiencies or causes of failures, or to identify parts to be modified.\n**有效且高效地评估某一部分变更对产品或系统的影响，诊断产品缺陷或故障原因，或识别需要修改的部分的程度。**\n- **Modifiability / 可修改性**\n Degree to which a product or system can be effectively and efficiently modified without introducing defects or degrading existing product quality.\n**产品或系统可以有效且高效地修改而不会引入缺陷或降低现有产品质量的程度。**"}
{"id": "docx::AsKyw443niuYJ1ksicFcQg01nXc::360", "page_id": "docx::AsKyw443niuYJ1ksicFcQg01nXc", "title": "Chapter 12 Other Attributes / 第十二章：其他质量属性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 12 Other Attributes / 第十二章：其他质量属性", "section": "Chapter 12 Other Attributes / 第十二章：其他质量属性/**Maintainability / 可维护性**", "url": "https://a1npn29y3xu.feishu.cn/wiki/AsKyw443niuYJ1ksicFcQg01nXc", "source_type": "docx", "n_chars": 368, "text": "introducing defects or degrading existing product quality.\n**产品或系统可以有效且高效地修改而不会引入缺陷或降低现有产品质量的程度。**\n- **Testability / 可测试性**\n Degree of effectiveness and efficiency with which test criteria can be established for a system, product, or component and tests can be performed to determine whether those criteria have been met.\n**为系统、产品或组件建立测试标准并执行测试，验证是否满足这些标准的有效性和效率的程度。**"}
{"id": "docx::AsKyw443niuYJ1ksicFcQg01nXc::361", "page_id": "docx::AsKyw443niuYJ1ksicFcQg01nXc", "title": "Chapter 12 Other Attributes / 第十二章：其他质量属性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 12 Other Attributes / 第十二章：其他质量属性", "section": "Chapter 12 Other Attributes / 第十二章：其他质量属性/**Flexibility / 灵活性**", "url": "https://a1npn29y3xu.feishu.cn/wiki/AsKyw443niuYJ1ksicFcQg01nXc", "source_type": "docx", "n_chars": 675, "text": "Degree to which a product can be adapted to changes in its requirements, contexts of use, or system environment. This characteristic is composed of the following sub-characteristics.\n**产品能够适应其需求、使用情境或系统环境变化的能力。该特性由以下子特性组成。**\n\n- **Adaptability / 适应性**\n Degree to which a product or system can effectively and efficiently be adapted for or transferred to different hardware, software, or other operational or usage environments.\n**产品或系统有效且高效地适应或迁移到不同硬件、软件或其他操作/使用环境的程度。**\n- **Scalability / 可扩展性**\n Degree to which a product can handle growing or shrinking workloads or to adapt its capacity to handle variability.\n**产品处理不断增长或缩小的工作负载，或根据变化调整其容量的能力。**\n- **Installability / 可安装性**"}
{"id": "docx::AsKyw443niuYJ1ksicFcQg01nXc::362", "page_id": "docx::AsKyw443niuYJ1ksicFcQg01nXc", "title": "Chapter 12 Other Attributes / 第十二章：其他质量属性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 12 Other Attributes / 第十二章：其他质量属性", "section": "Chapter 12 Other Attributes / 第十二章：其他质量属性/**Flexibility / 灵活性**", "url": "https://a1npn29y3xu.feishu.cn/wiki/AsKyw443niuYJ1ksicFcQg01nXc", "source_type": "docx", "n_chars": 486, "text": "its capacity to handle variability.\n**产品处理不断增长或缩小的工作负载，或根据变化调整其容量的能力。**\n- **Installability / 可安装性**\n Degree of effectiveness and efficiency with which a product or system can be successfully installed and/or uninstalled in a specified environment.\n**产品或系统在特定环境中成功安装和/或卸载的有效性和效率程度。**\n- **Replaceability / 可替换性**\n Degree to which a product can replace another specified software product for the same purpose in the same environment.\n**产品能够在相同环境下，替代另一个指定软件产品以实现相同目的的程度。**\n\n**Safety / 安全性**"}
{"id": "docx::AsKyw443niuYJ1ksicFcQg01nXc::363", "page_id": "docx::AsKyw443niuYJ1ksicFcQg01nXc", "title": "Chapter 12 Other Attributes / 第十二章：其他质量属性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 12 Other Attributes / 第十二章：其他质量属性", "section": "Chapter 12 Other Attributes / 第十二章：其他质量属性/**Flexibility / 灵活性**", "url": "https://a1npn29y3xu.feishu.cn/wiki/AsKyw443niuYJ1ksicFcQg01nXc", "source_type": "docx", "n_chars": 643, "text": "the same purpose in the same environment.\n**产品能够在相同环境下，替代另一个指定软件产品以实现相同目的的程度。**\n\n**Safety / 安全性**\n\nThis characteristic represents the degree to which a product, under defined conditions, avoids a state in which human life, health, property, or the environment is endangered. This characteristic is composed of the following sub-characteristics.\n\n该特性代表产品在特定条件下，避免进入可能危及人类生命、健康、财产或环境的状态的能力。该特性由以下子特性组成。\n\n- **Operational Constraint / 操作约束**\n Degree to which a product or system constrains its operation to within safe parameters or states when encountering operational hazards.\n当遇到操作风险时，产品或系统将其操作约束在安全参数或状态范围内的程度。\n- **Risk Identification / 风险识别**"}
{"id": "docx::AsKyw443niuYJ1ksicFcQg01nXc::364", "page_id": "docx::AsKyw443niuYJ1ksicFcQg01nXc", "title": "Chapter 12 Other Attributes / 第十二章：其他质量属性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 12 Other Attributes / 第十二章：其他质量属性", "section": "Chapter 12 Other Attributes / 第十二章：其他质量属性/**Flexibility / 灵活性**", "url": "https://a1npn29y3xu.feishu.cn/wiki/AsKyw443niuYJ1ksicFcQg01nXc", "source_type": "docx", "n_chars": 696, "text": "ountering operational hazards.\n当遇到操作风险时，产品或系统将其操作约束在安全参数或状态范围内的程度。\n- **Risk Identification / 风险识别**\n Degree to which a product can identify a course of events or operations that can expose life, property, or the environment to unacceptable risk.\n产品能够识别可能将生命、财产或环境暴露于不可接受风险的事件或操作过程的能力。\n- **Fail-Safe / 故障安全**\n Degree to which a product can automatically place itself in a safe operating mode, or revert to a safe condition in the event of a failure.\n在发生故障时，产品能够自动将自身置于安全操作模式，或恢复到安全状态的能力。\n- **Hazard Warning / 危险警告**\n Degree to which a product or system provides warnings of unacceptable risks to operations or internal controls so that they can react in sufficient time to sustain safe operations."}
{"id": "docx::AsKyw443niuYJ1ksicFcQg01nXc::365", "page_id": "docx::AsKyw443niuYJ1ksicFcQg01nXc", "title": "Chapter 12 Other Attributes / 第十二章：其他质量属性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性/Chapter 12 Other Attributes / 第十二章：其他质量属性", "section": "Chapter 12 Other Attributes / 第十二章：其他质量属性/**Flexibility / 灵活性**", "url": "https://a1npn29y3xu.feishu.cn/wiki/AsKyw443niuYJ1ksicFcQg01nXc", "source_type": "docx", "n_chars": 324, "text": "erations or internal controls so that they can react in sufficient time to sustain safe operations.\n产品或系统能够及时提供关于操作或内部控制不可接受风险的警告，从而使其能够在足够的时间内做出反应，维持安全操作的能力。\n- **Safe Integration / 安全集成**\n Degree to which a product can maintain safety during and after integration with one or more components.\n在与一个或多个组件集成过程中及之后，产品能够维持安全的能力。"}
{"id": "docx::ErnBwcTDciJl0qkKrP5cOAKNnph::366", "page_id": "docx::ErnBwcTDciJl0qkKrP5cOAKNnph", "title": "DB SQL 基础教程", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB SQL 基础教程", "section": "参考教程", "url": "https://a1npn29y3xu.feishu.cn/wiki/ErnBwcTDciJl0qkKrP5cOAKNnph", "source_type": "docx", "n_chars": 105, "text": "https://github.com/cwy007/sql-basic-tutorial-2th\n\n"}
{"id": "docx::ErnBwcTDciJl0qkKrP5cOAKNnph::367", "page_id": "docx::ErnBwcTDciJl0qkKrP5cOAKNnph", "title": "DB SQL 基础教程", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB SQL 基础教程", "section": "常考 SQL 集", "url": "https://a1npn29y3xu.feishu.cn/wiki/ErnBwcTDciJl0qkKrP5cOAKNnph", "source_type": "docx", "n_chars": 638, "text": "```SQL\n-- 创建表格\ncreate table product(\n product_id char(4) not null,\n product_name varchar(100) not null,\n product_type varchar(32) not null,\n sale_price integer,\n purchase_price integer,\n regist_date date,\n primary key (product_id)\n);\n\n-- 插入数据\nINSERT INTO Product VALUES ('O001', 'T恤衫', '衣服', 1000, 500, '2009-09-20');\nINSERT INTO Product VALUES ('0002', '打孔器', '办公用品', 500, 320, '2009-09-11');\nINSERT INTO Product VALUES ('0003', '运动T恤', '衣服', 4000, 2800, NULL);\nINSERT INTO Product VALUES ('0004', '菜刀', '厨房用具', 3000, 2800, '2009-09-20');\nINSERT INTO Product VALUES ('0005', '高压锅', '厨房用具', 6800, 5000, '2009-01-15');"}
{"id": "docx::ErnBwcTDciJl0qkKrP5cOAKNnph::368", "page_id": "docx::ErnBwcTDciJl0qkKrP5cOAKNnph", "title": "DB SQL 基础教程", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB SQL 基础教程", "section": "常考 SQL 集", "url": "https://a1npn29y3xu.feishu.cn/wiki/ErnBwcTDciJl0qkKrP5cOAKNnph", "source_type": "docx", "n_chars": 652, "text": "2800, '2009-09-20');\nINSERT INTO Product VALUES ('0005', '高压锅', '厨房用具', 6800, 5000, '2009-01-15');\nINSERT INTO Product VALUES ('0006', '叉子', '厨房用具', 500, NULL, '2009-09-20');\nINSERT INTO Product VALUES ('0007', '擦菜板', '厨房用具', 880, 790, '2008-04-28');\nINSERT INTO Product VALUES ('0008', '圆珠笔', '办公用品', 100, NULL, '2009-11-11');\n\n-- select\nselect product_id, product_name, purchase_price from product;\n\nselect product.product_id id, product.product_name name, product.purchase_price price from product;\n\nselect distinct product_type type from product;\n\nselect distinct purchase_price price from product;\n\nselect * from product where product_type = '衣服';"}
{"id": "docx::ErnBwcTDciJl0qkKrP5cOAKNnph::369", "page_id": "docx::ErnBwcTDciJl0qkKrP5cOAKNnph", "title": "DB SQL 基础教程", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB SQL 基础教程", "section": "常考 SQL 集", "url": "https://a1npn29y3xu.feishu.cn/wiki/ErnBwcTDciJl0qkKrP5cOAKNnph", "source_type": "docx", "n_chars": 620, "text": "lect distinct purchase_price price from product;\n\nselect * from product where product_type = '衣服';\n\nselect product.purchase_price, purchase_price * 2 expensive from product;\n\nselect * from product where sale_price = 500;\n\nselect product_name, product_type from product where sale_price <> 500;\n\nselect product_name, product_type, sale_price from product where sale_price >= 1000;\n\nselect product_name, product_type, regist_date from product where regist_date = 500;\n\nselect * from product where purchase_price is null;\n\nselect product_type, purchase_price from product where product_type = '厨房用具' and sale_price >= 3000;"}
{"id": "docx::ErnBwcTDciJl0qkKrP5cOAKNnph::370", "page_id": "docx::ErnBwcTDciJl0qkKrP5cOAKNnph", "title": "DB SQL 基础教程", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB SQL 基础教程", "section": "常考 SQL 集", "url": "https://a1npn29y3xu.feishu.cn/wiki/ErnBwcTDciJl0qkKrP5cOAKNnph", "source_type": "docx", "n_chars": 650, "text": "lect product_type, purchase_price from product where product_type = '厨房用具' and sale_price >= 3000;\n\nselect product_name, purchase_price from product where product_type = '厨房用具' or sale_price >= 3000;\n\nselect product_name, product_type, regist_date from product where product_type = '办公用品' and (regist_date = '2009-09-11' or regist_date = '2009-09-20');\n\nselect count(*) from product;\n\nselect count(purchase_price) from product;\n\nselect sum(product.sale_price) from product;\n\nselect sum(sale_price), sum(purchase_price) from product;\n\nselect avg(sale_price), avg(purchase_price) from product;\n\nselect max(sale_price), min(purchase_price) from product;"}
{"id": "docx::ErnBwcTDciJl0qkKrP5cOAKNnph::371", "page_id": "docx::ErnBwcTDciJl0qkKrP5cOAKNnph", "title": "DB SQL 基础教程", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB SQL 基础教程", "section": "常考 SQL 集", "url": "https://a1npn29y3xu.feishu.cn/wiki/ErnBwcTDciJl0qkKrP5cOAKNnph", "source_type": "docx", "n_chars": 609, "text": "ice), avg(purchase_price) from product;\n\nselect max(sale_price), min(purchase_price) from product;\n\nselect max(regist_date), min(regist_date) from product;\n\nselect distinct count(product.product_type) from product; -- 答案是 8，表示多少个物品\nselect count(distinct product_type) from product; -- 答案是 3，表示多少种不同的物品\n\nselect product_type, count(*) from product group by product_type;\n\nselect product_type, count(*) from product group by product_type having count(*) = 2;\n\nselect product_type, avg(sale_price) from product group by product_type having avg(sale_price) >= 2500;\n\nselect * from product order by sale_price desc;"}
{"id": "docx::ErnBwcTDciJl0qkKrP5cOAKNnph::372", "page_id": "docx::ErnBwcTDciJl0qkKrP5cOAKNnph", "title": "DB SQL 基础教程", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB SQL 基础教程", "section": "常考 SQL 集", "url": "https://a1npn29y3xu.feishu.cn/wiki/ErnBwcTDciJl0qkKrP5cOAKNnph", "source_type": "docx", "n_chars": 634, "text": "p by product_type having avg(sale_price) >= 2500;\n\nselect * from product order by sale_price desc;\n\nselect product_type, sum(sale_price), sum(purchase_price) from product group by product_type having sum(sale_price) > 1.5 * sum(purchase_price);\n\nselect * from product order by regist_date desc, sale_price;\n\ninsert into product(product_id, product_name, product_type, sale_price, purchase_price, regist_date)\nvalues\n ('0009', '裙子', '衣服', 1000, 500, '2009-09-21'),\n ('0010', '裤子', '衣服', 1500, 700, '2009-09-22');\n\ndelete from product;\ndelete from product where product_id = '0009';\n\nupdate product set regist_date = '2009-10-10';"}
{"id": "docx::ErnBwcTDciJl0qkKrP5cOAKNnph::373", "page_id": "docx::ErnBwcTDciJl0qkKrP5cOAKNnph", "title": "DB SQL 基础教程", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB SQL 基础教程", "section": "常考 SQL 集", "url": "https://a1npn29y3xu.feishu.cn/wiki/ErnBwcTDciJl0qkKrP5cOAKNnph", "source_type": "docx", "n_chars": 688, "text": "uct;\ndelete from product where product_id = '0009';\n\nupdate product set regist_date = '2009-10-10';\nupdate product set sale_price = sale_price * 1.2 where product_type = '厨房用具';\n\ncreate view product_sum (product_type, cnt_product)\nas\nselect product_type, count(*) from product group by product_type;\n\nselect * from product where sale_price > (select avg(sale_price) from product);\n\nselect * from product as p1 where sale_price > (select avg(sale_price) from product as p2\n where p1.product_type = p2.product_type\n group by p2.product_type);\n\nselect current_date;"}
{"id": "docx::ErnBwcTDciJl0qkKrP5cOAKNnph::374", "page_id": "docx::ErnBwcTDciJl0qkKrP5cOAKNnph", "title": "DB SQL 基础教程", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB SQL 基础教程", "section": "常考 SQL 集", "url": "https://a1npn29y3xu.feishu.cn/wiki/ErnBwcTDciJl0qkKrP5cOAKNnph", "source_type": "docx", "n_chars": 259, "text": "group by p2.product_type);\n\nselect current_date;\nselect current_time;\n\n-- 将某一列的 null 值全部变成某一个值\nselect coalesce(null, 1) as col_1;\n\n-- % 用于匹配任意字符\nselect * from product where product_type like ('%衣%');\nselect * from product where product_type like ('厨___');\n```"}
{"id": "docx::TXuXwGALjivaelkp3plcyiDlnRg::375", "page_id": "docx::TXuXwGALjivaelkp3plcyiDlnRg", "title": "DB 讲义（一） Chapter 01 ~ 02 & 06 关系代数", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（一） Chapter 01 ~ 02 & 06 关系代数", "section": "DB 讲义（一） Chapter 01 ~ 02 & 06 关系代数", "url": "https://a1npn29y3xu.feishu.cn/wiki/TXuXwGALjivaelkp3plcyiDlnRg", "source_type": "docx", "n_chars": 38, "text": "DB 讲义（一） Chapter 01 ~ 02 & 06 关系代数"}
{"id": "docx::TXuXwGALjivaelkp3plcyiDlnRg::376", "page_id": "docx::TXuXwGALjivaelkp3plcyiDlnRg", "title": "DB 讲义（一） Chapter 01 ~ 02 & 06 关系代数", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（一） Chapter 01 ~ 02 & 06 关系代数", "section": "一轮复习手写笔记", "url": "https://a1npn29y3xu.feishu.cn/wiki/TXuXwGALjivaelkp3plcyiDlnRg", "source_type": "docx", "n_chars": 226, "text": "\n\n\n\n\n\n"}
{"id": "docx::TXuXwGALjivaelkp3plcyiDlnRg::377", "page_id": "docx::TXuXwGALjivaelkp3plcyiDlnRg", "title": "DB 讲义（一） Chapter 01 ~ 02 & 06 关系代数", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（一） Chapter 01 ~ 02 & 06 关系代数", "section": "PPT + 速记笔记/第一章 引言", "url": "https://a1npn29y3xu.feishu.cn/wiki/TXuXwGALjivaelkp3plcyiDlnRg", "source_type": "docx", "n_chars": 682, "text": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::TXuXwGALjivaelkp3plcyiDlnRg::378", "page_id": "docx::TXuXwGALjivaelkp3plcyiDlnRg", "title": "DB 讲义（一） Chapter 01 ~ 02 & 06 关系代数", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（一） Chapter 01 ~ 02 & 06 关系代数", "section": "PPT + 速记笔记/第一章 引言", "url": "https://a1npn29y3xu.feishu.cn/wiki/TXuXwGALjivaelkp3plcyiDlnRg", "source_type": "docx", "n_chars": 668, "text": "ishu.cn/file/Fa37bK1rWokZM6x2GqBcwqOAnHc)\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::TXuXwGALjivaelkp3plcyiDlnRg::379", "page_id": "docx::TXuXwGALjivaelkp3plcyiDlnRg", "title": "DB 讲义（一） Chapter 01 ~ 02 & 06 关系代数", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（一） Chapter 01 ~ 02 & 06 关系代数", "section": "PPT + 速记笔记/第一章 引言", "url": "https://a1npn29y3xu.feishu.cn/wiki/TXuXwGALjivaelkp3plcyiDlnRg", "source_type": "docx", "n_chars": 212, "text": "ishu.cn/file/Eb7cb0Hx7oSe4oxV7j9cpn5onlb)\n\n\n\n\n\n"}
{"id": "docx::TXuXwGALjivaelkp3plcyiDlnRg::380", "page_id": "docx::TXuXwGALjivaelkp3plcyiDlnRg", "title": "DB 讲义（一） Chapter 01 ~ 02 & 06 关系代数", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（一） Chapter 01 ~ 02 & 06 关系代数", "section": "PPT + 速记笔记/第二 & 六章 关系模型介绍", "url": "https://a1npn29y3xu.feishu.cn/wiki/TXuXwGALjivaelkp3plcyiDlnRg", "source_type": "docx", "n_chars": 511, "text": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::OKvlwOzxIiASDNkmNHrcr53Bnsg::381", "page_id": "docx::OKvlwOzxIiASDNkmNHrcr53Bnsg", "title": "DB 讲义（三） Chapter 07 ~ 08 数据库设计", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（三） Chapter 07 ~ 08 数据库设计", "section": "一轮复习手写笔记", "url": "https://a1npn29y3xu.feishu.cn/wiki/OKvlwOzxIiASDNkmNHrcr53Bnsg", "source_type": "docx", "n_chars": 682, "text": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::OKvlwOzxIiASDNkmNHrcr53Bnsg::382", "page_id": "docx::OKvlwOzxIiASDNkmNHrcr53Bnsg", "title": "DB 讲义（三） Chapter 07 ~ 08 数据库设计", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（三） Chapter 07 ~ 08 数据库设计", "section": "一轮复习手写笔记", "url": "https://a1npn29y3xu.feishu.cn/wiki/OKvlwOzxIiASDNkmNHrcr53Bnsg", "source_type": "docx", "n_chars": 611, "text": "ishu.cn/file/URCgbtZvzoIrW7xLjDccUXfxnoh)\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::OKvlwOzxIiASDNkmNHrcr53Bnsg::383", "page_id": "docx::OKvlwOzxIiASDNkmNHrcr53Bnsg", "title": "DB 讲义（三） Chapter 07 ~ 08 数据库设计", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（三） Chapter 07 ~ 08 数据库设计", "section": "期末例题", "url": "https://a1npn29y3xu.feishu.cn/wiki/OKvlwOzxIiASDNkmNHrcr53Bnsg", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::OKvlwOzxIiASDNkmNHrcr53Bnsg::384", "page_id": "docx::OKvlwOzxIiASDNkmNHrcr53Bnsg", "title": "DB 讲义（三） Chapter 07 ~ 08 数据库设计", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（三） Chapter 07 ~ 08 数据库设计", "section": "PPT + 速记笔记", "url": "https://a1npn29y3xu.feishu.cn/wiki/OKvlwOzxIiASDNkmNHrcr53Bnsg", "source_type": "docx", "n_chars": 682, "text": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::OKvlwOzxIiASDNkmNHrcr53Bnsg::385", "page_id": "docx::OKvlwOzxIiASDNkmNHrcr53Bnsg", "title": "DB 讲义（三） Chapter 07 ~ 08 数据库设计", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（三） Chapter 07 ~ 08 数据库设计", "section": "PPT + 速记笔记", "url": "https://a1npn29y3xu.feishu.cn/wiki/OKvlwOzxIiASDNkmNHrcr53Bnsg", "source_type": "docx", "n_chars": 497, "text": "ishu.cn/file/Jg1PbuvaXoALCVxvZrBc5mlInbb)\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::WVxPwXZXrie0gRkDpVZcBaGRnic::386", "page_id": "docx::WVxPwXZXrie0gRkDpVZcBaGRnic", "title": "DB 讲义（二） Chapter 03 ~ 05 SQL 专题", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（二） Chapter 03 ~ 05 SQL 专题", "section": "一轮复习手写笔记", "url": "https://a1npn29y3xu.feishu.cn/wiki/WVxPwXZXrie0gRkDpVZcBaGRnic", "source_type": "docx", "n_chars": 682, "text": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::WVxPwXZXrie0gRkDpVZcBaGRnic::387", "page_id": "docx::WVxPwXZXrie0gRkDpVZcBaGRnic", "title": "DB 讲义（二） Chapter 03 ~ 05 SQL 专题", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（二） Chapter 03 ~ 05 SQL 专题", "section": "SQL 黑马程序员版", "url": "https://a1npn29y3xu.feishu.cn/wiki/WVxPwXZXrie0gRkDpVZcBaGRnic", "source_type": "docx", "n_chars": 94, "text": ""}
{"id": "docx::WVxPwXZXrie0gRkDpVZcBaGRnic::388", "page_id": "docx::WVxPwXZXrie0gRkDpVZcBaGRnic", "title": "DB 讲义（二） Chapter 03 ~ 05 SQL 专题", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（二） Chapter 03 ~ 05 SQL 专题", "section": "PPT + 速记笔记/第三章 SQL", "url": "https://a1npn29y3xu.feishu.cn/wiki/WVxPwXZXrie0gRkDpVZcBaGRnic", "source_type": "docx", "n_chars": 682, "text": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::WVxPwXZXrie0gRkDpVZcBaGRnic::389", "page_id": "docx::WVxPwXZXrie0gRkDpVZcBaGRnic", "title": "DB 讲义（二） Chapter 03 ~ 05 SQL 专题", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（二） Chapter 03 ~ 05 SQL 专题", "section": "PPT + 速记笔记/第三章 SQL", "url": "https://a1npn29y3xu.feishu.cn/wiki/WVxPwXZXrie0gRkDpVZcBaGRnic", "source_type": "docx", "n_chars": 668, "text": "ishu.cn/file/GEmvbCp4Eofo0ax2hvoczEmAnUm)\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::WVxPwXZXrie0gRkDpVZcBaGRnic::390", "page_id": "docx::WVxPwXZXrie0gRkDpVZcBaGRnic", "title": "DB 讲义（二） Chapter 03 ~ 05 SQL 专题", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（二） Chapter 03 ~ 05 SQL 专题", "section": "PPT + 速记笔记/第三章 SQL", "url": "https://a1npn29y3xu.feishu.cn/wiki/WVxPwXZXrie0gRkDpVZcBaGRnic", "source_type": "docx", "n_chars": 212, "text": "ishu.cn/file/BbOvb8o3Do4OvvxUSkqcIwEunFc)\n\n\n\n\n\n"}
{"id": "docx::WVxPwXZXrie0gRkDpVZcBaGRnic::391", "page_id": "docx::WVxPwXZXrie0gRkDpVZcBaGRnic", "title": "DB 讲义（二） Chapter 03 ~ 05 SQL 专题", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（二） Chapter 03 ~ 05 SQL 专题", "section": "PPT + 速记笔记/第四章 中级 SQL", "url": "https://a1npn29y3xu.feishu.cn/wiki/WVxPwXZXrie0gRkDpVZcBaGRnic", "source_type": "docx", "n_chars": 226, "text": "\n\n\n\n\n\n"}
{"id": "docx::WVxPwXZXrie0gRkDpVZcBaGRnic::392", "page_id": "docx::WVxPwXZXrie0gRkDpVZcBaGRnic", "title": "DB 讲义（二） Chapter 03 ~ 05 SQL 专题", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（二） Chapter 03 ~ 05 SQL 专题", "section": "PPT + 速记笔记/第五章 高级 SQL", "url": "https://a1npn29y3xu.feishu.cn/wiki/WVxPwXZXrie0gRkDpVZcBaGRnic", "source_type": "docx", "n_chars": 283, "text": "\n\n\n\n\n\n\n\n"}
{"id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb::393", "page_id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb", "title": "DB 讲义（五） Chapter 14 ~ 16 事务恢复", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（五） Chapter 14 ~ 16 事务恢复", "section": "一轮复习手写笔记（14 章）", "url": "https://a1npn29y3xu.feishu.cn/wiki/HTWZwzfAUi6xUskLfboc9EGJnTb", "source_type": "docx", "n_chars": 169, "text": "\n\n\n\n"}
{"id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb::394", "page_id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb", "title": "DB 讲义（五） Chapter 14 ~ 16 事务恢复", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（五） Chapter 14 ~ 16 事务恢复", "section": "一轮复习补充笔记（15 16 章）/第十四章 事务", "url": "https://a1npn29y3xu.feishu.cn/wiki/HTWZwzfAUi6xUskLfboc9EGJnTb", "source_type": "docx", "n_chars": 169, "text": "\n\n\n\n"}
{"id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb::395", "page_id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb", "title": "DB 讲义（五） Chapter 14 ~ 16 事务恢复", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（五） Chapter 14 ~ 16 事务恢复", "section": "一轮复习补充笔记（15 16 章）/第十四章 事务/Concurrency Control", "url": "https://a1npn29y3xu.feishu.cn/wiki/HTWZwzfAUi6xUskLfboc9EGJnTb", "source_type": "docx", "n_chars": 692, "text": "A database must provide a mechanism that will ensure that all possible schedules are either conflict or view serializable, and are recoverable and preferably cascadeless / 数据库必须提供一种机制，以确保所有可能的调度都是 conflict 或 view serializable，以及是可恢复的，最好是无级联的\n\nA policy in which only one transaction can execute at a time generates serial schedules, but provides a poor degree of concurrency / 一次只能执行一个事务的策略会生成串行计划，但并发程度很差\n\nAre serial schedules recoverable/cascadeless? / 串行调度是否可恢复/无级联？\n\nTesting a schedule for serializability *after* it has executed is a little too late! / 在执行计划后测试计划的可序列化性有点太晚了！\n\n**Goal** – to develop concurrency control protocols that will assure serializability. / 目标 – 开发可确保可序列化性的并发控制协议。"}
{"id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb::396", "page_id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb", "title": "DB 讲义（五） Chapter 14 ~ 16 事务恢复", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（五） Chapter 14 ~ 16 事务恢复", "section": "一轮复习补充笔记（15 16 章）/第十四章 事务/Concurrency Control vs. **Serializability Tests**", "url": "https://a1npn29y3xu.feishu.cn/wiki/HTWZwzfAUi6xUskLfboc9EGJnTb", "source_type": "docx", "n_chars": 634, "text": "Concurrency-control protocols allow concurrent schedules, but ensure that the schedules are conflict/view serializable, and are recoverable and cascadeless . / 并发控制协议允许并发计划，但要确保计划是冲突/视图可序列化的，并且是可恢复的和无级联的。\n\nConcurrency control protocols generally do not examine the precedence graph as it is being created / 并发控制协议通常不会在创建优先级图时对其进行检查\n\nInstead, a protocol imposes a discipline that avoids nonseralizable schedules. / 相反，协议施加了避免不可调整的时间表的纪律。\n\nDifferent concurrency control protocols provide different tradeoffs between the amount of concurrency they allow and the amount of overhead that they incur. / 不同的并发控制协议在它们允许的并发量和它们产生的开销量之间提供不同的权衡。"}
{"id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb::397", "page_id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb", "title": "DB 讲义（五） Chapter 14 ~ 16 事务恢复", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（五） Chapter 14 ~ 16 事务恢复", "section": "一轮复习补充笔记（15 16 章）/第十四章 事务/Concurrency Control vs. **Serializability Tests**", "url": "https://a1npn29y3xu.feishu.cn/wiki/HTWZwzfAUi6xUskLfboc9EGJnTb", "source_type": "docx", "n_chars": 221, "text": "ncy they allow and the amount of overhead that they incur. / 不同的并发控制协议在它们允许的并发量和它们产生的开销量之间提供不同的权衡。\n\nTests for serializability help us understand why a concurrency control protocol is correct. / 可序列化性测试有助于我们了解并发控制协议为何是正确的。"}
{"id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb::398", "page_id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb", "title": "DB 讲义（五） Chapter 14 ~ 16 事务恢复", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（五） Chapter 14 ~ 16 事务恢复", "section": "一轮复习补充笔记（15 16 章）/第十四章 事务/对 MySQL 的事务感兴趣，请移步 xiaolincoding.com/mysql", "url": "https://a1npn29y3xu.feishu.cn/wiki/HTWZwzfAUi6xUskLfboc9EGJnTb", "source_type": "docx", "n_chars": 156, "text": "[事务隔离级别是怎么实现的？](https://xiaolincoding.com/mysql/transaction/mvcc.html)\n\n[MySQL 可重复读隔离级别，完全解决幻读了吗？](https://xiaolincoding.com/mysql/transaction/phantom.html)"}
{"id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb::399", "page_id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb", "title": "DB 讲义（五） Chapter 14 ~ 16 事务恢复", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（五） Chapter 14 ~ 16 事务恢复", "section": "一轮复习补充笔记（15 16 章）/第十五章 并发控制/15.1 基于锁的协议", "url": "https://a1npn29y3xu.feishu.cn/wiki/HTWZwzfAUi6xUskLfboc9EGJnTb", "source_type": "docx", "n_chars": 682, "text": "\n\nA transaction may be granted a lock on an item if the requested lock is compatible with locks already held on the item by other transactions / 如果请求的锁与其他事务已经持有的项目上的锁兼容，则可以授予事务对项目的锁\n\nAny number of transactions can hold shared locks on an item, but if any transaction holds an exclusive on the item, no other transaction may hold any lock on the item. / 任何数量的事务都可以对项目持有共享锁，但如果任何事务对该项目持有排他性，则任何其他事务都不能对该项目持有任何锁。\n\nIf a lock cannot be granted, the requesting transaction is made to wait till all incompatible locks held by other transactions have been released. The lock is then granted. / 如果无法授予锁，则使请求事务等待其他事务持有的所有不兼容锁都被释放。然后授予锁。"}
{"id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb::400", "page_id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb", "title": "DB 讲义（五） Chapter 14 ~ 16 事务恢复", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（五） Chapter 14 ~ 16 事务恢复", "section": "一轮复习补充笔记（15 16 章）/第十五章 并发控制/15.1 基于锁的协议/**Pitfalls of Lock-Based Protocols / 基于锁的协议的陷阱**", "url": "https://a1npn29y3xu.feishu.cn/wiki/HTWZwzfAUi6xUskLfboc9EGJnTb", "source_type": "docx", "n_chars": 534, "text": "The potential for deadlock exists in most locking protocols. Deadlocks are a necessary evil. / 大多数锁定协议都存在死锁的可能性。死锁是一种必要的邪恶。\n\n**Starvation** is also possible if concurrency control manager is badly designed. For example: / 如果并发控制管理器设计不当，也可能出现匮乏。例如：\n\nA transaction may be waiting for an X-lock on an item, while a sequence of other transactions request and are granted an S-lock on the same item. / 一个事务可能正在等待对某个项目的 X-lock，而其他事务序列请求并被授予对同一项目的 S-lock。\n\nThe same transaction is repeatedly rolled back due to deadlocks. / 由于死锁，同一事务会反复回滚。"}
{"id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb::401", "page_id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb", "title": "DB 讲义（五） Chapter 14 ~ 16 事务恢复", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（五） Chapter 14 ~ 16 事务恢复", "section": "一轮复习补充笔记（15 16 章）/第十五章 并发控制/15.1 基于锁的协议/**The Two-Phase Locking Protocol / 两阶段锁协议**", "url": "https://a1npn29y3xu.feishu.cn/wiki/HTWZwzfAUi6xUskLfboc9EGJnTb", "source_type": "docx", "n_chars": 686, "text": "This is a protocol which ensures conflict-serializable schedules. / 这是一个确保冲突可序列化调度的协议。\n\nPhase 1: Growing Phase / 阶段 1：成长期\n\nTransaction may obtain locks / 事务可能会获取锁\n\nTransaction may not release locks / 事务可能无法释放锁\n\nPhase 2: Shrinking Phase / 阶段 2：收缩阶段\n\nTransaction may release locks / 事务可能会释放锁\n\nTransaction may not obtain locks / 事务可能无法获取锁\n\nThe protocol assures serializability. It can be proved that the transactions can be serialized in the order of their **lock points** (i.e. the point where a transaction acquired its final lock). / 该协议确保了可序列化性。可以证明 transactions 可以按照它们的锁点的顺序进行序列化 （即 transaction 获得其最终锁的点）。\n\nTwo-phase locking *does not* ensure freedom from deadlocks. / 两阶段锁无法确保免于死锁"}
{"id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb::402", "page_id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb", "title": "DB 讲义（五） Chapter 14 ~ 16 事务恢复", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（五） Chapter 14 ~ 16 事务恢复", "section": "一轮复习补充笔记（15 16 章）/第十五章 并发控制/15.1 基于锁的协议/**Partial Schedule Under Two-Phase Locking / 两相锁定下的部分计划**", "url": "https://a1npn29y3xu.feishu.cn/wiki/HTWZwzfAUi6xUskLfboc9EGJnTb", "source_type": "docx", "n_chars": 686, "text": "Cascading roll-back is possible under two-phase locking. / 在两阶段锁定下，可以进行级联回滚。\n\nTo avoid this, follow a modified protocol called **strict two-phase locking**. Here a transaction must hold all its ***exclusive*** locks till it commits/aborts. / 为避免这种情况，请遵循称为严格两阶段锁定的修改协议。在这里，事务必须持有其所有独占锁，直到提交/中止。\n\n**Rigorous two-phase locking** is even stricter: here ***all*** locks are held till commit/abort. In this protocol transactions can be serialized in the order in which they commit. / 严格的两阶段锁定甚至更严格：这里所有的锁都保持到提交/中止。在此协议中，事务可以按照其提交的顺序进行序列化。\n\n\n\n\n\n带锁转换的两相锁定：\n\n – 第一阶段：\n\n可以获得对物品的锁定 S"}
{"id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb::403", "page_id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb", "title": "DB 讲义（五） Chapter 14 ~ 16 事务恢复", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（五） Chapter 14 ~ 16 事务恢复", "section": "一轮复习补充笔记（15 16 章）/第十五章 并发控制/15.1 基于锁的协议/**Partial Schedule Under Two-Phase Locking / 两相锁定下的部分计划**", "url": "https://a1npn29y3xu.feishu.cn/wiki/HTWZwzfAUi6xUskLfboc9EGJnTb", "source_type": "docx", "n_chars": 293, "text": ")\n\n\n\n带锁转换的两相锁定：\n\n – 第一阶段：\n\n可以获得对物品的锁定 S\n\n可以在物品上获得 Lock-X\n\n可以将 lock-S 转换为 lock-X（升级）\n\n – 第二阶段：\n\n可以释放锁 S\n\n可以释放 Lock-X\n\n可以将 lock-X 转换为 lock-S（降级）\n\n此协议可确保可序列化性。但仍然依赖程序员插入各种锁定指令。\n\n"}
{"id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb::404", "page_id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb", "title": "DB 讲义（五） Chapter 14 ~ 16 事务恢复", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（五） Chapter 14 ~ 16 事务恢复", "section": "一轮复习补充笔记（15 16 章）/第十五章 并发控制/15.1 基于锁的协议/Implementation of Locking / 锁的执行", "url": "https://a1npn29y3xu.feishu.cn/wiki/HTWZwzfAUi6xUskLfboc9EGJnTb", "source_type": "docx", "n_chars": 573, "text": "A **lock manager** can be implemented as a separate process to which transactions send lock and unlock requests. / 锁管理器 可以实现为事务发送锁和解锁请求的单独进程。\n\nThe lock manager replies to a lock request by sending a lock grant message (or a message asking the transaction to roll back, in case of a deadlock). / 锁管理器通过发送锁授予消息（或在死锁的情况下要求事务回滚的消息）来回复锁请求。\n\nThe requesting transaction waits until its request is answered. / 请求事务将等待，直到其请求得到响应。\n\nThe lock manager maintains a data-structure called a **lock table** to record granted locks and pending requests. / 锁管理器维护一个称为锁表的数据结构，用于记录已授予的锁和待处理请求。"}
{"id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb::405", "page_id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb", "title": "DB 讲义（五） Chapter 14 ~ 16 事务恢复", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（五） Chapter 14 ~ 16 事务恢复", "section": "一轮复习补充笔记（15 16 章）/第十五章 并发控制/15.1 基于锁的协议/Implementation of Locking / 锁的执行", "url": "https://a1npn29y3xu.feishu.cn/wiki/HTWZwzfAUi6xUskLfboc9EGJnTb", "source_type": "docx", "n_chars": 376, "text": "**lock table** to record granted locks and pending requests. / 锁管理器维护一个称为锁表的数据结构，用于记录已授予的锁和待处理请求。\n\nThe lock table is usually implemented as an in-memory hash table indexed on the name of the data item being locked. / lock table 通常实现为内存中的哈希表，该哈希表根据被锁定的数据项的名称进行索引。\n\n\n\n"}
{"id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb::406", "page_id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb", "title": "DB 讲义（五） Chapter 14 ~ 16 事务恢复", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（五） Chapter 14 ~ 16 事务恢复", "section": "一轮复习补充笔记（15 16 章）/第十五章 并发控制/15.2 死锁处理", "url": "https://a1npn29y3xu.feishu.cn/wiki/HTWZwzfAUi6xUskLfboc9EGJnTb", "source_type": "docx", "n_chars": 198, "text": "\n\n- 如果存在一组事务，使得该集合中的每个事务都在等待该集合中的另一个事务，则系统处于死锁状态。\n- 使用死锁进行计划\n\n - 有两种主要方法：\n\n - 死锁预防协议，以确保系统永远不会进入死锁状态\n - 允许系统进入死锁状态，然后尝试使用死锁检测和死锁恢复方法进行修复"}
{"id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb::407", "page_id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb", "title": "DB 讲义（五） Chapter 14 ~ 16 事务恢复", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（五） Chapter 14 ~ 16 事务恢复", "section": "一轮复习补充笔记（15 16 章）/第十五章 并发控制/15.2 死锁处理/15.2.1 死锁预防", "url": "https://a1npn29y3xu.feishu.cn/wiki/HTWZwzfAUi6xUskLfboc9EGJnTb", "source_type": "docx", "n_chars": 628, "text": "\n\n死锁预防协议可确保系统永远不会进入死锁状态。一些预防策略\n\n\n\n- 防止死锁的第二种方法是使用抢占 （抢占） 和事务回滚 （事务回滚）。\n\n - wait-die 方案 — 非抢占式\n\n - 较早的事务可能会等待较年轻的事务释放数据项。年轻的交易永远不会等待旧的交易;它们将被回滚。\n - 在获取所需的数据项之前，事务可能会多次终止\n - wound-wait 方案 — 抢占式\n\n - 较旧的事务会伤害 （强制回滚） 较年轻的事务，而不是等待它。较年轻的交易可能会等待较早的交易。\n - 可能比 wait-die 方案的回滚次数少。\n- 在 wait-die 和 wound-wait 方案中，回滚的事务都会使用其原始时间戳重新启动。因此，较旧的事务优先于较新的事务，因此避免了饥饿。\n\n\n\n- 另一种简单的死锁预防方法基于锁超时。\n\n - 事务仅等待锁定指定的时间。在此之后，等待超时，事务将回滚。\n - 因此不可能出现死锁\n - 易于实施;但饥饿是可能的。也很难确定超时间隔的好值。"}
{"id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb::408", "page_id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb", "title": "DB 讲义（五） Chapter 14 ~ 16 事务恢复", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（五） Chapter 14 ~ 16 事务恢复", "section": "一轮复习补充笔记（15 16 章）/第十五章 并发控制/15.2 死锁处理/15.2.2 死锁检测与恢复", "url": "https://a1npn29y3xu.feishu.cn/wiki/HTWZwzfAUi6xUskLfboc9EGJnTb", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb::409", "page_id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb", "title": "DB 讲义（五） Chapter 14 ~ 16 事务恢复", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（五） Chapter 14 ~ 16 事务恢复", "section": "一轮复习补充笔记（15 16 章）/第十五章 并发控制/15.4 基于时间戳的协议", "url": "https://a1npn29y3xu.feishu.cn/wiki/HTWZwzfAUi6xUskLfboc9EGJnTb", "source_type": "docx", "n_chars": 283, "text": "\n\n\n\n\n\n\n\n"}
{"id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb::410", "page_id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb", "title": "DB 讲义（五） Chapter 14 ~ 16 事务恢复", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（五） Chapter 14 ~ 16 事务恢复", "section": "一轮复习补充笔记（15 16 章）/第十五章 并发控制/15.4 基于时间戳的协议/15.4.3 Thomas 写规则", "url": "https://a1npn29y3xu.feishu.cn/wiki/HTWZwzfAUi6xUskLfboc9EGJnTb", "source_type": "docx", "n_chars": 195, "text": "\n\n\n\n- 时间戳排序协议保证了可序列化性，因此，优先级图中将没有循环。\n- 时间戳协议确保不会死锁，因为没有交易等待。\n- 但该计划可能不是无级联的，甚至可能无法恢复。"}
{"id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb::411", "page_id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb", "title": "DB 讲义（五） Chapter 14 ~ 16 事务恢复", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（五） Chapter 14 ~ 16 事务恢复", "section": "一轮复习补充笔记（15 16 章）/第十六章 恢复系统/16.1 故障分类", "url": "https://a1npn29y3xu.feishu.cn/wiki/HTWZwzfAUi6xUskLfboc9EGJnTb", "source_type": "docx", "n_chars": 429, "text": "\n\n\n\n- 考虑从账户 A 向账户 B 转账 50 美元的交易 Ti\n\n - 两次更新：从 A 中减去 50，然后将 50 添加到 B\n- 事务 Ti 需要将 A 和 B 的更新输出到数据库。（出错的情况可能不一样，备份文件 ＞ 数据文件）\n\n - 在进行其中一项修改之后，但在进行两项修改之前，可能会发生失败。\n - 在不确保事务将提交的情况下修改数据库可能会使数据库处于不一致状态\n - 如果在事务提交后立即发生故障，则不修改数据库可能会导致更新丢失\n- 恢复算法分为两部分\n\n1. 在正常事务处理期间采取的操作，以确保存在足够的信息以从故障中恢复\n2. 在无法将数据库内容恢复到可确保原子性、一致性和持久性的状态后采取的操作"}
{"id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb::412", "page_id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb", "title": "DB 讲义（五） Chapter 14 ~ 16 事务恢复", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（五） Chapter 14 ~ 16 事务恢复", "section": "一轮复习补充笔记（15 16 章）/第十六章 恢复系统/16.2 存储器", "url": "https://a1npn29y3xu.feishu.cn/wiki/HTWZwzfAUi6xUskLfboc9EGJnTb", "source_type": "docx", "n_chars": 634, "text": "\n\n- 易失性存储：\n\n - 在系统崩溃后无法幸存\n - 示例：主内存、缓存内存\n- 非易失性存储器：\n\n - 在系统崩溃后继续存在\n - 示例：磁盘、磁带、闪存、非易失性（电池备份）RAM\n- 稳定存储：\n\n - 一种神话般的存储形式，可以在所有故障中幸存下来\n - 通过在不同的非易失性介质上维护多个副本来近似\n\n #### 16.2.1 稳定存储器的实现\n\n\n\n\n\n- 由于输出操作期间的故障，块的副本可能会有所不同。要从故障中恢复：\n\n1. 首先找到不一致的块：\n\n 1. 昂贵的解决方案：比较每个磁盘块的两个副本。\n 2. 更好的解决方案：\n\n - 在非易失性存储（非易失性 RAM 或磁盘的特殊区域）上记录正在进行的磁盘写入。\n - 在恢复过程中使用此信息查找可能不一致的块，并且仅比较这些块的副本。\n - 用于硬件 RAID 系统\n2. 如果检测到不一致块的任一副本有错误（校验和错误），则用另一个副本覆盖它。 如果两者没有错误，但不同，则用第一个数据块覆盖第二个数据块。"}
{"id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb::413", "page_id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb", "title": "DB 讲义（五） Chapter 14 ~ 16 事务恢复", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（五） Chapter 14 ~ 16 事务恢复", "section": "一轮复习补充笔记（15 16 章）/第十六章 恢复系统/16.2 存储器/16.2.2 数据访问", "url": "https://a1npn29y3xu.feishu.cn/wiki/HTWZwzfAUi6xUskLfboc9EGJnTb", "source_type": "docx", "n_chars": 226, "text": "\n\n\n\n\n\n"}
{"id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb::414", "page_id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb", "title": "DB 讲义（五） Chapter 14 ~ 16 事务恢复", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（五） Chapter 14 ~ 16 事务恢复", "section": "一轮复习补充笔记（15 16 章）/第十六章 恢复系统/16.3 恢复与原子性", "url": "https://a1npn29y3xu.feishu.cn/wiki/HTWZwzfAUi6xUskLfboc9EGJnTb", "source_type": "docx", "n_chars": 686, "text": "- To ensure atomicity despite failures, we first output information describing the modifications to stable storage without modifying the database itself. / 为了确保在失败的情况下的原子性，我们首先输出描述对稳定存储的修改的信息，而不修改数据库本身。\n- We study two approaches:\n\n - log-based recovery（基于日志的方式）\n - shadow-paging（影子分页技术）\n- We assume (initially) that transactions run serially, that is, one after the other. / 我们假设（最初）事务是串行运行的，即一个接一个。\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb::415", "page_id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb", "title": "DB 讲义（五） Chapter 14 ~ 16 事务恢复", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（五） Chapter 14 ~ 16 事务恢复", "section": "一轮复习补充笔记（15 16 章）/第十六章 恢复系统/16.3 恢复与原子性", "url": "https://a1npn29y3xu.feishu.cn/wiki/HTWZwzfAUi6xUskLfboc9EGJnTb", "source_type": "docx", "n_chars": 657, "text": "ishu.cn/file/ItD3bYgCuoXAk5xaWl9cGTAHnUh)\n\n\n\n- 撤消日志记录将旧值 V1 写入 X\n- 重做日志记录会将新值 V2 写入 X\n- 撤消和重做事务\n\n - undo（Ti） 将 Ti 更新的所有数据项的值恢复为旧值，从 Ti 的最后一条日志记录向后返回\n\n - 每次将数据项 X 恢复到其旧值 V 时，都会写出一条特殊的日志记录\n - 当事务的撤消完成时，将写出日志记录 。\n - redo（Ti） 将 Ti 更新的所有数据项的值设置为新值，从 Ti 的第一个日志记录开始\n\n - 在这种情况下，不进行日志记录\n\n\n\n- 失败后恢复时：\n\n如果日志包含记录 但不包含记录 或 ，那么就是 undone\n\n如果日志包含记录 并且包含记录 或 ，那么就是 redone\n\n- 请注意，如果事务 Ti 之前已撤消，并且 记录写入日志，然后发生故障，则在从故障中恢复时，将重做 Ti\n\n - 此类重做将重做所有原始操作，包括恢复旧值的步骤\n\n - 称为重复历史\n - 看起来很浪费，但大大简化了回收\n\n"}
{"id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb::416", "page_id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb", "title": "DB 讲义（五） Chapter 14 ~ 16 事务恢复", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（五） Chapter 14 ~ 16 事务恢复", "section": "一轮复习补充笔记（15 16 章）/第十六章 恢复系统/16.3 恢复与原子性", "url": "https://a1npn29y3xu.feishu.cn/wiki/HTWZwzfAUi6xUskLfboc9EGJnTb", "source_type": "docx", "n_chars": 683, "text": "旧值的步骤\n\n - 称为重复历史\n - 看起来很浪费，但大大简化了回收\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n- 从故障中恢复：两个阶段"}
{"id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb::417", "page_id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb", "title": "DB 讲义（五） Chapter 14 ~ 16 事务恢复", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（五） Chapter 14 ~ 16 事务恢复", "section": "一轮复习补充笔记（15 16 章）/第十六章 恢复系统/16.3 恢复与原子性", "url": "https://a1npn29y3xu.feishu.cn/wiki/HTWZwzfAUi6xUskLfboc9EGJnTb", "source_type": "docx", "n_chars": 681, "text": "8cbPPrRoFQqkxX3LxcuSzInHu)\n\n\n\n- 从故障中恢复：两个阶段\n\n - 重做阶段：重放所有事务的更新，无论它们是否已提交、已中止或未完成\n - 撤消阶段：撤消所有未完成的事务\n- 重做阶段：\n\n1. 找到最后一个 记录，并将 undo-list 设置为 L。\n2. 从上面向前扫描 记录\n\n 1. 每当找到记录 时，通过将 V2 写入 Xj 来重做它\n 2. 每当找到日志记录 时，将 Ti 添加到撤销列表\n 3. 每当找到日志记录 或 时，从撤消列表中删除 Ti\n\n- 撤销阶段：\n\n1. 从末尾向后扫描日志\n\n 1. 每当在 Ti 位于撤消列表中的位置找到日志记录 时，请执行与事务回滚相同的操作\n\n 1. 通过将 V1 写入 Xj 来执行撤销。\n 2. 写入日志记录\n 2. 每当在撤销列表中找到 Ti 所在的日志记录时，\n\n 1. 写入日志记录\n 2. 从撤销列表中删除 Ti\n 3. undo-list 为空时停止: 即 已为 undo-list 中的每个事务找到\n\n- 撤消阶段完成后，可以开始正常的事务处理\n\n\n\n"}
{"id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb::418", "page_id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb", "title": "DB 讲义（五） Chapter 14 ~ 16 事务恢复", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（五） Chapter 14 ~ 16 事务恢复", "section": "一轮复习补充笔记（15 16 章）/第十六章 恢复系统/16.9 远程备份系统", "url": "https://a1npn29y3xu.feishu.cn/wiki/HTWZwzfAUi6xUskLfboc9EGJnTb", "source_type": "docx", "n_chars": 528, "text": "\n\n- 故障检测：主站点什么时候发生故障？\n\n - 通信线路故障会使远程备份站点误以为主站点已发生故障，因此在主站点和备份站点之间维持几条具有独立故障模式的通信线路\n- 控制权的移交：备份站点何时开始工作？\n\n - 当主站点发生故障时，备份站点就接管处理并成为新的主站\n - 当原来的主站点恢复后，它可以作为远程备份站点工作，抑或再次接管并作为主站点。\n - 移交控制权最简单的办法是原主站点从原备份站点收到 redo 日志，并将它们应用到本地以赶上更新。\n- 恢复时间\n\n - 如果远程备份站点上的日志增长到很大，恢复就会花很长时间。\n - 远程备份站点可以周期性地处理它收到的自由日志，并执行一个检查点\n - 采用热备份(hot spare) 配置可使备份站点几乎能在一瞬间接管\n- 提交时间\n\n - 为保证已提交事务的更新是持久的，只有在其日志记录到达备份站点之后才能宣称该事务已提交。该延迟会导致等待事务提交的时间变长，因此某些系统允许较低程度的持久性。\n - 持久性的程度可以按如下分类：一方保险，两方保险，两方强保险"}
{"id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb::419", "page_id": "docx::HTWZwzfAUi6xUskLfboc9EGJnTb", "title": "DB 讲义（五） Chapter 14 ~ 16 事务恢复", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（五） Chapter 14 ~ 16 事务恢复", "section": "PPT + 速记笔记", "url": "https://a1npn29y3xu.feishu.cn/wiki/HTWZwzfAUi6xUskLfboc9EGJnTb", "source_type": "docx", "n_chars": 454, "text": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::VSkqwnV6lik7REkuX6BcLTctnId::420", "page_id": "docx::VSkqwnV6lik7REkuX6BcLTctnId", "title": "DB 讲义（四） Chapter 11 ~ 13 检索专题", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（四） Chapter 11 ~ 13 检索专题", "section": "一轮复习手写笔记", "url": "https://a1npn29y3xu.feishu.cn/wiki/VSkqwnV6lik7REkuX6BcLTctnId", "source_type": "docx", "n_chars": 682, "text": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::VSkqwnV6lik7REkuX6BcLTctnId::421", "page_id": "docx::VSkqwnV6lik7REkuX6BcLTctnId", "title": "DB 讲义（四） Chapter 11 ~ 13 检索专题", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（四） Chapter 11 ~ 13 检索专题", "section": "一轮复习手写笔记", "url": "https://a1npn29y3xu.feishu.cn/wiki/VSkqwnV6lik7REkuX6BcLTctnId", "source_type": "docx", "n_chars": 155, "text": "ishu.cn/file/ECXCbyPZToTBZLxOH2ecxF4Fnbg)\n\n\n\n"}
{"id": "docx::VSkqwnV6lik7REkuX6BcLTctnId::422", "page_id": "docx::VSkqwnV6lik7REkuX6BcLTctnId", "title": "DB 讲义（四） Chapter 11 ~ 13 检索专题", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（四） Chapter 11 ~ 13 检索专题", "section": "一轮复习手写笔记/备注：B+ 树的增删改查", "url": "https://a1npn29y3xu.feishu.cn/wiki/VSkqwnV6lik7REkuX6BcLTctnId", "source_type": "docx", "n_chars": 454, "text": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::VSkqwnV6lik7REkuX6BcLTctnId::423", "page_id": "docx::VSkqwnV6lik7REkuX6BcLTctnId", "title": "DB 讲义（四） Chapter 11 ~ 13 检索专题", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（四） Chapter 11 ~ 13 检索专题", "section": "PPT + 速记笔记", "url": "https://a1npn29y3xu.feishu.cn/wiki/VSkqwnV6lik7REkuX6BcLTctnId", "source_type": "docx", "n_chars": 283, "text": "\n\n\n\n\n\n\n\n"}
{"id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh::424", "page_id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh", "title": "DB 黑马程序员 MySQL", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 黑马程序员 MySQL", "section": "手写笔记", "url": "https://a1npn29y3xu.feishu.cn/wiki/KxrDw9K9ciVkxXkAKa1cb1GXnwh", "source_type": "docx", "n_chars": 682, "text": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh::425", "page_id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh", "title": "DB 黑马程序员 MySQL", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 黑马程序员 MySQL", "section": "手写笔记", "url": "https://a1npn29y3xu.feishu.cn/wiki/KxrDw9K9ciVkxXkAKa1cb1GXnwh", "source_type": "docx", "n_chars": 554, "text": "ishu.cn/file/Ad4Wb7zOdowof5xv6JccTUGenge)\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh::426", "page_id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh", "title": "DB 黑马程序员 MySQL", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 黑马程序员 MySQL", "section": "多表查询/例题", "url": "https://a1npn29y3xu.feishu.cn/wiki/KxrDw9K9ciVkxXkAKa1cb1GXnwh", "source_type": "docx", "n_chars": 236, "text": "\n\n使用了以下三张表\n\n\n\n\n\n"}
{"id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh::427", "page_id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh", "title": "DB 黑马程序员 MySQL", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 黑马程序员 MySQL", "section": "多表查询/参考答案", "url": "https://a1npn29y3xu.feishu.cn/wiki/KxrDw9K9ciVkxXkAKa1cb1GXnwh", "source_type": "docx", "n_chars": 695, "text": "```SQL\n-- 1\nselect e.name, e.age, e.job, d.name from emp e, dept d where e.dept_id = d.id;\n\n-- 2\nselect * from emp e inner join dept d on e.dept_id = d.id where e.age > 30;\n\n-- 3 一题多解\nselect * from dept where id in (select dept_id from emp);\nselect distinct d.* from emp e, dept d where e.dept_id = d.id;\n\n-- 4 必须要有部门\nselect emp.name, dept.name from emp, dept where emp.age > 40 and emp.dept_id = dept.id;\n\n-- 4 可以不分配部门（请注意两个 sql 的区别）\n-- 正确的写法\nselect e.*, d.name from emp e left join dept d on e.dept_id = d.id where e.age > 40;\n-- 错误的写法\nselect e.*, d.name from emp e left join dept d on e.dept_id = d.id and e.age > 40;\n-- 为什么错了？\n/*\n在 SQL 中，`LEFT JOIN` 用于从左表（`emp`）返回所有的记录，即使右表（`dept`）中没有匹配的记录。"}
{"id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh::428", "page_id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh", "title": "DB 黑马程序员 MySQL", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 黑马程序员 MySQL", "section": "多表查询/参考答案", "url": "https://a1npn29y3xu.feishu.cn/wiki/KxrDw9K9ciVkxXkAKa1cb1GXnwh", "source_type": "docx", "n_chars": 641, "text": "d = d.id and e.age > 40;\n-- 为什么错了？\n/*\n在 SQL 中，`LEFT JOIN` 用于从左表（`emp`）返回所有的记录，即使右表（`dept`）中没有匹配的记录。\n`LEFT JOIN` 会将左表的所有记录与右表中匹配的记录合并，如果右表中没有匹配的记录，那么结果集中右表的部分将为 `NULL`。\n\n错误的写法中，`WHERE` 子句的条件 `e.age > 40` 被错误地放在了 `ON` 子句中，与 `e.dept_id = d.id` 通过 `AND` 连接。\n这样做的结果是，只有当 `emp` 表中的记录年龄大于 40 岁且与 `dept` 表中的记录匹配时，才会进行连接。\n这意味着，如果 `emp` 表中的记录年龄不大于 40 岁，即使它们与 `dept` 表中的记录有匹配，这些记录也不会出现在结果集中。\n这违反了 `LEFT JOIN` 的本意，即返回左表的所有记录。\n\n正确的写法是将 `e.age > 40` 放在 `WHERE` 子句中，这样 `LEFT JOIN` 会先执行，\n返回 `emp` 表的所有记录与 `dept` 表中匹配的记录，然后再由 `WHERE` 子句过滤出年龄大于 40 岁的记录。\n*/\n\n-- 5\nselect e.*, s.grade from salgrade s, emp e where (e.salary between s.losal and s.highsal);\n\n-- 6"}
{"id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh::429", "page_id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh", "title": "DB 黑马程序员 MySQL", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 黑马程序员 MySQL", "section": "多表查询/参考答案", "url": "https://a1npn29y3xu.feishu.cn/wiki/KxrDw9K9ciVkxXkAKa1cb1GXnwh", "source_type": "docx", "n_chars": 676, "text": "5\nselect e.*, s.grade from salgrade s, emp e where (e.salary between s.losal and s.highsal);\n\n-- 6\nselect e.*, s.grade from emp e, dept d, salgrade s where e.dept_id = d.id and d.name = '研发部' and (e.salary between s.losal and s.highsal);\n\n-- 7\nselect avg(e.salary) from emp e, dept d, salgrade s where e.dept_id = d.id and d.name = '研发部';\n\n-- 8\nselect * from emp e where e.salary > (select salary from emp where emp.name = '灭绝');\n\n-- 9\nselect * from emp e where e.salary > (select avg(salary) from emp);\n\n-- 10 查询低于本部门平均工资的员工信息\n\n-- a. 查询指定部门的平均薪资\nselect avg(e.salary) from emp e where e.dept_id = 1;\nselect avg(e.salary) from emp e where e.dept_id = 2;\n\n-- b. 查询低于本部门平均工资的员工信息"}
{"id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh::430", "page_id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh", "title": "DB 黑马程序员 MySQL", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 黑马程序员 MySQL", "section": "多表查询/参考答案", "url": "https://a1npn29y3xu.feishu.cn/wiki/KxrDw9K9ciVkxXkAKa1cb1GXnwh", "source_type": "docx", "n_chars": 301, "text": "e where e.dept_id = 1;\nselect avg(e.salary) from emp e where e.dept_id = 2;\n\n-- b. 查询低于本部门平均工资的员工信息\nselect * from emp a where a.salary < ( select avg(e.salary) from emp e where e.dept_id = a.dept_id );\n\n-- 11\nselect d.id, d.name, (select count(*) from emp e where dept_id = d.id) '人数' from dept d;\n```"}
{"id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh::431", "page_id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh", "title": "DB 黑马程序员 MySQL", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 黑马程序员 MySQL", "section": "截图缓存/事务", "url": "https://a1npn29y3xu.feishu.cn/wiki/KxrDw9K9ciVkxXkAKa1cb1GXnwh", "source_type": "docx", "n_chars": 682, "text": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh::432", "page_id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh", "title": "DB 黑马程序员 MySQL", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 黑马程序员 MySQL", "section": "截图缓存/事务", "url": "https://a1npn29y3xu.feishu.cn/wiki/KxrDw9K9ciVkxXkAKa1cb1GXnwh", "source_type": "docx", "n_chars": 155, "text": "ishu.cn/file/TTf9bj30OobhprxC5KkcQpgunsf)\n\n\n\n"}
{"id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh::433", "page_id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh", "title": "DB 黑马程序员 MySQL", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 黑马程序员 MySQL", "section": "截图缓存/索引", "url": "https://a1npn29y3xu.feishu.cn/wiki/KxrDw9K9ciVkxXkAKa1cb1GXnwh", "source_type": "docx", "n_chars": 682, "text": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh::434", "page_id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh", "title": "DB 黑马程序员 MySQL", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 黑马程序员 MySQL", "section": "截图缓存/索引", "url": "https://a1npn29y3xu.feishu.cn/wiki/KxrDw9K9ciVkxXkAKa1cb1GXnwh", "source_type": "docx", "n_chars": 668, "text": "ishu.cn/file/Vp5MbohuioCM6zx6gzUco8ORnUg)\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh::435", "page_id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh", "title": "DB 黑马程序员 MySQL", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 黑马程序员 MySQL", "section": "截图缓存/索引", "url": "https://a1npn29y3xu.feishu.cn/wiki/KxrDw9K9ciVkxXkAKa1cb1GXnwh", "source_type": "docx", "n_chars": 668, "text": "ishu.cn/file/H5FPbjCPWo5DorxQ6KGcI955n2e)\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh::436", "page_id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh", "title": "DB 黑马程序员 MySQL", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 黑马程序员 MySQL", "section": "截图缓存/索引", "url": "https://a1npn29y3xu.feishu.cn/wiki/KxrDw9K9ciVkxXkAKa1cb1GXnwh", "source_type": "docx", "n_chars": 668, "text": "ishu.cn/file/Aukcbj1MiosRpIxeYE7cPpSinUc)\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh::437", "page_id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh", "title": "DB 黑马程序员 MySQL", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 黑马程序员 MySQL", "section": "截图缓存/索引", "url": "https://a1npn29y3xu.feishu.cn/wiki/KxrDw9K9ciVkxXkAKa1cb1GXnwh", "source_type": "docx", "n_chars": 668, "text": "ishu.cn/file/LNdFbz5hZooblDxG6NscFvaInwd)\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh::438", "page_id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh", "title": "DB 黑马程序员 MySQL", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 黑马程序员 MySQL", "section": "截图缓存/索引", "url": "https://a1npn29y3xu.feishu.cn/wiki/KxrDw9K9ciVkxXkAKa1cb1GXnwh", "source_type": "docx", "n_chars": 668, "text": "ishu.cn/file/WpGVbxuDlo8d2NxwKOKcG0bgnJb)\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh::439", "page_id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh", "title": "DB 黑马程序员 MySQL", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 黑马程序员 MySQL", "section": "截图缓存/索引", "url": "https://a1npn29y3xu.feishu.cn/wiki/KxrDw9K9ciVkxXkAKa1cb1GXnwh", "source_type": "docx", "n_chars": 497, "text": "ishu.cn/file/CgnnbbDxJoIOIrxjCoYcEiPtnpg)\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh::440", "page_id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh", "title": "DB 黑马程序员 MySQL", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 黑马程序员 MySQL", "section": "课程地址，笔记就是 PPT", "url": "https://a1npn29y3xu.feishu.cn/wiki/KxrDw9K9ciVkxXkAKa1cb1GXnwh", "source_type": "docx", "n_chars": 189, "text": "[黑马程序员 MySQL数据库入门到精通，从mysql安装到mysql高级、mysql优化全囊括_哔哩哔哩_bilibili](https://www.bilibili.com/video/BV1Kr4y1i7ru?spm_id_from=333.788.videopod.episodes&vd_source=da1f2d78d73dfaae6ddfbcfe8e4801d8)"}
{"id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh::441", "page_id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh", "title": "DB 黑马程序员 MySQL", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 黑马程序员 MySQL", "section": "进阶篇/存储引擎 01 — 07 ✅", "url": "https://a1npn29y3xu.feishu.cn/wiki/KxrDw9K9ciVkxXkAKa1cb1GXnwh", "source_type": "docx", "n_chars": 147, "text": "02 0020，0429，0444\n\n03 0353，0504，0723，0803\n\n04 0232，0856\n\n05 0100，0346，0457\n\n06 0340\n\nMySQL 使用 InnoDB\n\nMongoDB 代替了 MyISAM\n\nRedis 代替了 Memory\n\n07 0305"}
{"id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh::442", "page_id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh", "title": "DB 黑马程序员 MySQL", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 黑马程序员 MySQL", "section": "进阶篇/✨ 索引 09 — 31 ✅", "url": "https://a1npn29y3xu.feishu.cn/wiki/KxrDw9K9ciVkxXkAKa1cb1GXnwh", "source_type": "docx", "n_chars": 664, "text": "09 0045，0241，0630，0835\n\n10 0218，0307（默认 B+ 树）\n\n11 0337，1157\n\n12 0143，0428，0633\n\n13 0304，0448\n\n14 面试题：为什么 InnoDB 选择了 B+ Tree 索引结构？\n\n\n\n15 0030（工业界和学术界对主键索引的定义不同）0450 0712（聚集和二级的区别） 0910\n\n16\n\n\n\n根据 id 查询性能是高的\n\n\n\n17 \\~ 27 截图缓存有笔记\n\n28 0327，0506，0715\n\n重点需要理解（**选择性**）的概念及其用法\n\n\n\n\n\n29\n\n\n\n"}
{"id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh::443", "page_id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh", "title": "DB 黑马程序员 MySQL", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 黑马程序员 MySQL", "section": "进阶篇/✨ 索引 09 — 31 ✅", "url": "https://a1npn29y3xu.feishu.cn/wiki/KxrDw9K9ciVkxXkAKa1cb1GXnwh", "source_type": "docx", "n_chars": 235, "text": "ishu.cn/file/YpqVbGoemoEkyXxZWYqcixJ5ncd)\n\n\n\n\n\n\n\n30 0100\n\n31 0400 0930"}
{"id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh::444", "page_id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh", "title": "DB 黑马程序员 MySQL", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 黑马程序员 MySQL", "section": "进阶篇/SQL 优化 32 — 39 ✅", "url": "https://a1npn29y3xu.feishu.cn/wiki/KxrDw9K9ciVkxXkAKa1cb1GXnwh", "source_type": "docx", "n_chars": 395, "text": "Insert 0330 0645 1230\n\nPrimary Key 0240 0340 1114 1325\n\nOrder By 0113 0140 0223 0320 0430 0450 0530 0715 0740 0911 1038 1130 1205 1238 1423 1505 1625\n\nGroup By 0020 0210 0309 0425 0544 0606\n\nLimit 0052 0300 0558 0634\n\nCount 0223 0915 1002\n\n\n\nUpdate 一定要根据索引字段建立，否则行锁变成表锁，并发性能大幅降低 0740\n\n"}
{"id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh::445", "page_id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh", "title": "DB 黑马程序员 MySQL", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 黑马程序员 MySQL", "section": "进阶篇/视图 40 — 44 ✅", "url": "https://a1npn29y3xu.feishu.cn/wiki/KxrDw9K9ciVkxXkAKa1cb1GXnwh", "source_type": "docx", "n_chars": 391, "text": "**40** 0210 0530 0605 0730 0757 0815 1000 1050 1125\n\n**41** 0230 0450 0840 1230 1533 1605\n\n**42** 0204 0344 0545 0610 0709 0824\n\n**43** 0238 0310 0550\n\n**44** 视图例题\n\n\n\n\n\n\n\n"}
{"id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh::446", "page_id": "docx::KxrDw9K9ciVkxXkAKa1cb1GXnwh", "title": "DB 黑马程序员 MySQL", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 黑马程序员 MySQL", "section": "进阶篇/存储过程 45 — 58", "url": "https://a1npn29y3xu.feishu.cn/wiki/KxrDw9K9ciVkxXkAKa1cb1GXnwh", "source_type": "docx", "n_chars": 75, "text": "45 0220 0330 0415\n\n46 0121 0324 0434 0514 0735 0930 1152\n\n47 0126 0234 0425"}
{"id": "docx::YCBHwkhM5iTkfdkd5ykc7yvrnPb::447", "page_id": "docx::YCBHwkhM5iTkfdkd5ykc7yvrnPb", "title": "Github 精选材料", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/Github 精选材料", "section": "Github 精选材料", "url": "https://a1npn29y3xu.feishu.cn/wiki/YCBHwkhM5iTkfdkd5ykc7yvrnPb", "source_type": "docx", "n_chars": 65, "text": "**Github 源地址：https://github.com/KuiH/IT-Project-Management-Note**"}
{"id": "docx::YCBHwkhM5iTkfdkd5ykc7yvrnPb::448", "page_id": "docx::YCBHwkhM5iTkfdkd5ykc7yvrnPb", "title": "Github 精选材料", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/Github 精选材料", "section": "Github 精选材料/思维导图", "url": "https://a1npn29y3xu.feishu.cn/wiki/YCBHwkhM5iTkfdkd5ykc7yvrnPb", "source_type": "docx", "n_chars": 625, "text": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::EZkfw44YJirqfPk8zRPcxQX5n9f::449", "page_id": "docx::EZkfw44YJirqfPk8zRPcxQX5n9f", "title": "PM 专项突破", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破", "section": "PM 专项突破", "url": "https://a1npn29y3xu.feishu.cn/wiki/EZkfw44YJirqfPk8zRPcxQX5n9f", "source_type": "docx", "n_chars": 262, "text": ""}
{"id": "docx::MC6fwoWqNihRJ8kqIB0cCnuUnZc::450", "page_id": "docx::MC6fwoWqNihRJ8kqIB0cCnuUnZc", "title": "PM 讲义（一）Chapter 01 ~ 03", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（一）Chapter 01 ~ 03", "section": "PM 讲义（一）Chapter 01 ~ 03", "url": "https://a1npn29y3xu.feishu.cn/wiki/MC6fwoWqNihRJ8kqIB0cCnuUnZc", "source_type": "docx", "n_chars": 251, "text": "PM 讲义（一）Chapter 01 ~ 03\n\n\n\n\n\n\n\n"}
{"id": "docx::MC6fwoWqNihRJ8kqIB0cCnuUnZc::451", "page_id": "docx::MC6fwoWqNihRJ8kqIB0cCnuUnZc", "title": "PM 讲义（一）Chapter 01 ~ 03", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（一）Chapter 01 ~ 03", "section": "Chapter 01 Introduction to Project Management / 项目管理介绍/第九版 PPT 解析", "url": "https://a1npn29y3xu.feishu.cn/wiki/MC6fwoWqNihRJ8kqIB0cCnuUnZc", "source_type": "docx", "n_chars": 682, "text": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::MC6fwoWqNihRJ8kqIB0cCnuUnZc::452", "page_id": "docx::MC6fwoWqNihRJ8kqIB0cCnuUnZc", "title": "PM 讲义（一）Chapter 01 ~ 03", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（一）Chapter 01 ~ 03", "section": "Chapter 01 Introduction to Project Management / 项目管理介绍/第九版 PPT 解析", "url": "https://a1npn29y3xu.feishu.cn/wiki/MC6fwoWqNihRJ8kqIB0cCnuUnZc", "source_type": "docx", "n_chars": 668, "text": "ishu.cn/file/FKx3bKYtZoEAYfxq4uGcICZQnVf)\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::MC6fwoWqNihRJ8kqIB0cCnuUnZc::453", "page_id": "docx::MC6fwoWqNihRJ8kqIB0cCnuUnZc", "title": "PM 讲义（一）Chapter 01 ~ 03", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（一）Chapter 01 ~ 03", "section": "Chapter 01 Introduction to Project Management / 项目管理介绍/第九版 PPT 解析", "url": "https://a1npn29y3xu.feishu.cn/wiki/MC6fwoWqNihRJ8kqIB0cCnuUnZc", "source_type": "docx", "n_chars": 326, "text": "ishu.cn/file/UpDbb88CUobUVuxIaIlcpROrnsc)\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::MC6fwoWqNihRJ8kqIB0cCnuUnZc::454", "page_id": "docx::MC6fwoWqNihRJ8kqIB0cCnuUnZc", "title": "PM 讲义（一）Chapter 01 ~ 03", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（一）Chapter 01 ~ 03", "section": "Chapter 01 Introduction to Project Management / 项目管理介绍/潜在考点", "url": "https://a1npn29y3xu.feishu.cn/wiki/MC6fwoWqNihRJ8kqIB0cCnuUnZc", "source_type": "docx", "n_chars": 511, "text": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::MC6fwoWqNihRJ8kqIB0cCnuUnZc::455", "page_id": "docx::MC6fwoWqNihRJ8kqIB0cCnuUnZc", "title": "PM 讲义（一）Chapter 01 ~ 03", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（一）Chapter 01 ~ 03", "section": "Chapter 01 Introduction to Project Management / 项目管理介绍/章节总结", "url": "https://a1npn29y3xu.feishu.cn/wiki/MC6fwoWqNihRJ8kqIB0cCnuUnZc", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::MC6fwoWqNihRJ8kqIB0cCnuUnZc::456", "page_id": "docx::MC6fwoWqNihRJ8kqIB0cCnuUnZc", "title": "PM 讲义（一）Chapter 01 ~ 03", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（一）Chapter 01 ~ 03", "section": "Chapter 01 Introduction to Project Management / 项目管理介绍/期末复习参考题", "url": "https://a1npn29y3xu.feishu.cn/wiki/MC6fwoWqNihRJ8kqIB0cCnuUnZc", "source_type": "docx", "n_chars": 226, "text": "\n\n\n\n\n\n"}
{"id": "docx::MC6fwoWqNihRJ8kqIB0cCnuUnZc::457", "page_id": "docx::MC6fwoWqNihRJ8kqIB0cCnuUnZc", "title": "PM 讲义（一）Chapter 01 ~ 03", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（一）Chapter 01 ~ 03", "section": "Chapter 02 **The Project Management and Information Technology Context**/第九版 PPT 解析", "url": "https://a1npn29y3xu.feishu.cn/wiki/MC6fwoWqNihRJ8kqIB0cCnuUnZc", "source_type": "docx", "n_chars": 682, "text": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::MC6fwoWqNihRJ8kqIB0cCnuUnZc::458", "page_id": "docx::MC6fwoWqNihRJ8kqIB0cCnuUnZc", "title": "PM 讲义（一）Chapter 01 ~ 03", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（一）Chapter 01 ~ 03", "section": "Chapter 02 **The Project Management and Information Technology Context**/第九版 PPT 解析", "url": "https://a1npn29y3xu.feishu.cn/wiki/MC6fwoWqNihRJ8kqIB0cCnuUnZc", "source_type": "docx", "n_chars": 440, "text": "ishu.cn/file/KXOmb3ZG5oDQEQxkosEcuWeRned)\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::MC6fwoWqNihRJ8kqIB0cCnuUnZc::459", "page_id": "docx::MC6fwoWqNihRJ8kqIB0cCnuUnZc", "title": "PM 讲义（一）Chapter 01 ~ 03", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（一）Chapter 01 ~ 03", "section": "Chapter 02 **The Project Management and Information Technology Context**/课本回顾", "url": "https://a1npn29y3xu.feishu.cn/wiki/MC6fwoWqNihRJ8kqIB0cCnuUnZc", "source_type": "docx", "n_chars": 682, "text": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::MC6fwoWqNihRJ8kqIB0cCnuUnZc::460", "page_id": "docx::MC6fwoWqNihRJ8kqIB0cCnuUnZc", "title": "PM 讲义（一）Chapter 01 ~ 03", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（一）Chapter 01 ~ 03", "section": "Chapter 02 **The Project Management and Information Technology Context**/课本回顾", "url": "https://a1npn29y3xu.feishu.cn/wiki/MC6fwoWqNihRJ8kqIB0cCnuUnZc", "source_type": "docx", "n_chars": 668, "text": "ishu.cn/file/HNzqbU2zroYULFxgHUdcl1XgnJe)\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::MC6fwoWqNihRJ8kqIB0cCnuUnZc::461", "page_id": "docx::MC6fwoWqNihRJ8kqIB0cCnuUnZc", "title": "PM 讲义（一）Chapter 01 ~ 03", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（一）Chapter 01 ~ 03", "section": "Chapter 02 **The Project Management and Information Technology Context**/章节总结", "url": "https://a1npn29y3xu.feishu.cn/wiki/MC6fwoWqNihRJ8kqIB0cCnuUnZc", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::MC6fwoWqNihRJ8kqIB0cCnuUnZc::462", "page_id": "docx::MC6fwoWqNihRJ8kqIB0cCnuUnZc", "title": "PM 讲义（一）Chapter 01 ~ 03", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（一）Chapter 01 ~ 03", "section": "Chapter 02 **The Project Management and Information Technology Context**/期末复习参考题", "url": "https://a1npn29y3xu.feishu.cn/wiki/MC6fwoWqNihRJ8kqIB0cCnuUnZc", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::MC6fwoWqNihRJ8kqIB0cCnuUnZc::463", "page_id": "docx::MC6fwoWqNihRJ8kqIB0cCnuUnZc", "title": "PM 讲义（一）Chapter 01 ~ 03", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（一）Chapter 01 ~ 03", "section": "Chapter 03 **The Project Management Process Groups: A Case Study**/本章节以案例为主，仅保留课本原文", "url": "https://a1npn29y3xu.feishu.cn/wiki/MC6fwoWqNihRJ8kqIB0cCnuUnZc", "source_type": "docx", "n_chars": 340, "text": "\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::464", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 08 Project Quality Management / 项目质量管理/序、必考问答题/**4、7种基本的质量工具**", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 62, "text": "**因果图**\n\n**控制图**\n\n**检查表**\n\n**散点图**\n\n**直方图**\n\n**帕累托图**\n\n**流程图**"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::465", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 08 Project Quality Management / 项目质量管理/序、必考问答题/**5、DMAIC改进过程代表哪五个阶段**", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 82, "text": "**界定（define）**\n\n**度量（measure）**\n\n**分析（analyze）**\n\n**改进（improve）**\n\n**控制（control）**"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::466", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 08 Project Quality Management / 项目质量管理/8.2 什么是项目质量管理", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 561, "text": "The International Organization for Standardization (ISO) defines **quality** as “the degree to which a set of inherent characteristics fulfils requirements” (ISO9000:2000)\n\nOther experts define quality based on:\n\n- **Conformance to requirements**: The project’s processes and products meet written specifications\n- **Fitness for use**: A product can be used as it was intended\n\n\n\n**Project quality management** ensures that the project will satisfy the needs for which it was undertaken\n\nProcesses include:"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::467", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 08 Project Quality Management / 项目质量管理/8.2 什么是项目质量管理", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 667, "text": "** ensures that the project will satisfy the needs for which it was undertaken\n\nProcesses include:\n\n- **Planning quality manasgement**: Identifying which quality standards are relevant to the project and how to satisfy them; a **metric** is a standard of measurement\n- **Performing quality assurance**: Periodically evaluating overall project performance to ensure the project will satisfy the relevant quality standards\n- **Performing quality control**: Monitoring specific project results to ensure that they comply with the relevant quality standards\n\n\n\n"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::468", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 08 Project Quality Management / 项目质量管理/8.2 什么是项目质量管理", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 155, "text": "ishu.cn/file/XZKdbG29moyJPZxNFYGcUxYnnKc)\n\n\n\n"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::469", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 08 Project Quality Management / 项目质量管理/8.3 计划质量管理", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 697, "text": "Implies the ability to anticipate situations and prepare actions to bring about the desired outcome\n\nImportant to prevent defects by:\n\n- Selecting proper materials\n- Training and indoctrinating people in quality\n- Planning a process that ensures the appropriate outcome\n\n**Functionality** is the degree to which a system performs its intended function\n\n**Features** are the system’s special characteristics that appeal to users\n\n**System** **outputs** are the screens and reports the system generates\n\n**Performance** addresses how well a product or service performs the customer’s intended use\n\n**Reliability** is the ability of a product or service to perform as expected under normal conditions"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::470", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 08 Project Quality Management / 项目质量管理/8.3 计划质量管理", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 177, "text": "eliability** is the ability of a product or service to perform as expected under normal conditions\n\n**Maintainability** addresses the ease of performing maintenance on a product"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::471", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 08 Project Quality Management / 项目质量管理/8.4 实施质量保证", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 578, "text": "**Quality assurance** includes all the activities related to satisfying the relevant quality standards for a project\n\nAnother goal of quality assurance is continuous quality improvement\n\n**Benchmarking** generates ideas for quality improvements by comparing specific project practices or product characteristics to those of other projects or products within or outside the performing organization\n\nA **quality audit** is a structured review of specific quality management activities that help identify lessons learned that could improve performance on current or future projects"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::472", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 08 Project Quality Management / 项目质量管理/8.5 质量控制", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 236, "text": "The main outputs of quality control are:\n\n- Acceptance decisions\n- Rework\n- Process adjustments\n\n**There are Seven Basic Tools of Quality that help in performing quality control**\n\n"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::473", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 08 Project Quality Management / 项目质量管理/8.6 质量控制的工具和技术", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 682, "text": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::474", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 08 Project Quality Management / 项目质量管理/8.6 质量控制的工具和技术", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 155, "text": "ishu.cn/file/QNKwbr4VBo6OdHxXheCc19bLnsd)\n\n\n\n"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::475", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 08 Project Quality Management / 项目质量管理/8.6 质量控制的工具和技术/8.6.1 统计抽样", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 169, "text": "\n\n\n\n"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::476", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 08 Project Quality Management / 项目质量管理/8.6 质量控制的工具和技术/8.6.2 六西格玛", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 397, "text": "\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::477", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 08 Project Quality Management / 项目质量管理/8.6 质量控制的工具和技术/8.6.3 测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 226, "text": "\n\n\n\n\n\n"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::478", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 08 Project Quality Management / 项目质量管理/8.7 现代质量管理", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::479", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 08 Project Quality Management / 项目质量管理/8.8 提高 IT 项目质量", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::480", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 08 Project Quality Management / 项目质量管理/Chapter Summary", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 254, "text": "Project quality management ensures that the project will satisfy the needs for which it was undertaken\n\nMain processes include:\n\n- Plan quality\n- Perform quality assurance\n- Perform quality control\n\n"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::481", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/序、必考问答题/**1、项目人力资源管理的4个过程**", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 48, "text": "**计划人力资源管理**\n\n**组建项目团队**\n\n**建设项目团队**\n\n**管理项目团队**"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::482", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/序、必考问答题/2**、马斯洛需求层次理论从低到高是哪几层？**", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 48, "text": "**生理需求**\n\n**安全需求**\n\n**社交需求**\n\n**尊重需求**\n\n**自我实现**"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::483", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/序、必考问答题/3**、项目经理运用哪7种习惯来提高项目工作的效率？**", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 97, "text": "**积极主动**\n\n**开始执行时心中就已规划如何结束**\n\n**优先的事优先做**\n\n**考虑双赢**\n\n**首先寻求理解别人，然后再寻求被别人理解**\n\n**协同**\n\n**“磨快锯子”**"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::484", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/序、必考问答题/**4、资源平衡的优点是什么**", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 126, "text": "**（1）当资源的使用情况比较稳定时，它们需要的管理就较少**\n\n**（2）资源平衡可使项目经理通过使用分包商或者其他昂贵的资源而使用零库存策略**\n\n**（3）资源平衡可以减少财务部与项目人员方面的一些问题**\n\n**（4）资源平衡还可以提高士气**"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::485", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/序、必考问答题/**5、塔克曼模型描述的团队建设的5个阶段？**", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 48, "text": "**形成阶段**\n\n**震荡阶段**\n\n**规范阶段**\n\n**执行阶段**\n\n**终止阶段**"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::486", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/Learning Objectives / 学习目标", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 694, "text": "Explain the importance of good human resource management on projects, including the current state of the global IT workforce and future implications for it\n\nDefine project human resource management and understand its processes\n\nSummarize key concepts for managing people by understanding the theories of Abraham Maslow, Frederick Herzberg, David McClelland, and Douglas McGregor on motivation, H. J. Thamhain and D. L. Wilemon on influencing workers, and Stephen Covey on how people and teams can become more effective\n\nDiscuss human resource management planning and be able to create a human resource plan, project organizational chart, responsibility assignment matrix, and resource histogram"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::487", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/Learning Objectives / 学习目标", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 615, "text": "ource plan, project organizational chart, responsibility assignment matrix, and resource histogram\n\nUnderstand important issues involved in project staff acquisition and explain the concepts of resource assignments, resource loading, and resource leveling\n\nAssist in team development with training, team-building activities, and reward systems\n\nExplain and apply several tools and techniques to help manage a project team and summarize general advice on managing teams\n\nDescribe how project management software can assist in project human resource management\n\n"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::488", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/9.1 The Importance of Human Resource Management / 人力资源管理的重要性", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 202, "text": "Proactive organizations are addressing workforce needs by\n\n- improving benefits\n- redefining work hours and incentives\n- finding future workers\n\n积极主动的组织正在通过以下方式满足劳动力需求：\n\n- 改善福利\n- 重新定义工作时间和激励措施\n- 寻找未来的员工"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::489", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/9.2 What is Project Human Resource Management / 什么是项目人力资源管理", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 692, "text": "Making the most effective use of the people involved with a project\n\nProcesses include\n\n- **Planning human resource management:** identifying and documenting project roles, responsibilities, and reporting relationships\n- **Acquiring the project team:** getting the needed personnel assigned to and working on the project\n- **Developing the project team:** building individual and group skills to enhance project performance\n- **Managing the project team:** tracking team member performance, motivating team members, providing timely feedback, resolving issues and conflicts, and coordinating changes to help enhance project performance\n\n"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::490", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/9.2 What is Project Human Resource Management / 什么是项目人力资源管理", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 212, "text": "anges to help enhance project performance\n\n\n\n\n\n"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::491", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/9.3 Keys to Managing People / 人员管理的关键理论", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 266, "text": "Psychologists and management theorists have devoted much research and thought to the field of managing people at work\n\nImportant areas related to project management include\n\n- motivation theories\n- influence and power\n- effectiveness\n\n心理学家和管理理论家对工作中人员管理领域进行了大量的研究和思考"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::492", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/9.3 Keys to Managing People / 人员管理的关键理论/9.3.1 激励理论", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 279, "text": "与项目管理相关的重要领域包括\n\n- 激励理论\n- 影响力和权力\n- 有效性\n\n**Intrinsic motivation** causes people to participate in an activity for their own enjoyment\n\n**Extrinsic motivation** causes people to do something for a reward or to avoid a penalty\n\n"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::493", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/9.3 Keys to Managing People / 人员管理的关键理论/9.3.1 激励理论/9.3.1.1 马斯洛的需求层次理论", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 465, "text": "Abraham Maslow argued that humans possess unique qualities that enable them to make independent choices, thus giving them control of their destiny.\n\nMaslow developed a hierarchy of needs which states that people’s behaviors are guided or motivated by a sequence of needs.\n\n亚伯拉罕·马斯洛认为人类拥有独特的品质，使其能够做出独立的选择，从而控制自己的命运。\n\n马斯洛提出了需求层次理论，指出人们的行为受到一系列需求的引导或激励。\n\n\n\n"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::494", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/9.3 Keys to Managing People / 人员管理的关键理论/9.3.1 激励理论/9.3.1.2 赫兹伯格的“激励-保健”理论", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 552, "text": "Frederick Herzberg wrote several famous books and articles about worker motivation. He distinguished between\n\n- motivational factors: achievement, recognition, the work itself, responsibility, advancement, and growth, which produce job satisfaction\n- hygiene factors: cause dissatisfaction if not present, but do not motivate workers to do more. Examples include larger salaries, more supervision, and a more attractive work environment\n\n\n\n"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::495", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/9.3 Keys to Managing People / 人员管理的关键理论/9.3.1 激励理论/9.3.1.3 麦克利兰的“获得-需求”理论", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 644, "text": "Specific needs are acquired or learned over time and shaped by life experiences, including:\n\n- Achievement (nAch): Achievers like challenging projects with achievable goals and lots of feedback\n- Affiliation (nAff): People with high nAff desire harmonious relationships and need to feel accepted by others, so managers should try to create a cooperative work environment for them\n- Power: (nPow): People with a need for power desire either personal power (not good) or institutional power (good for the organization). Provide institutional power seekers with management opportunities\n\n"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::496", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/9.3 Keys to Managing People / 人员管理的关键理论/9.3.1 激励理论/9.3.1.4 麦克格雷戈的 X 理论和 Y 理论", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 685, "text": "Douglas McGregor popularized the human relations approach to management in the 1960s\n\nTheory X: assumes workers dislike and avoid work, so managers must use coercion, threats and various control schemes to get workers to meet objectives\n\nTheory Y: assumes individuals consider work as natural as play or rest and enjoy the satisfaction of esteem and self-actualization needs\n\nTheory Z: introduced in 1981 by William Ouchi and is based on the Japanese approach to motivating workers, emphasizing trust, quality, collective decision making, and cultural values\n\n道格拉斯·麦格雷戈在 20 世纪 60 年代推广了人际关系管理方法\n\n理论 X：假设员工不喜欢并逃避工作，因此管理者必须使用胁迫、威胁和各种控制方案来让员工达到目标\n\n理论 Y：假设个人认为工作就像玩耍或休息一样自然，并享受自尊和自我实现需求的满足"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::497", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/9.3 Keys to Managing People / 人员管理的关键理论/9.3.1 激励理论/9.3.1.4 麦克格雷戈的 X 理论和 Y 理论", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 152, "text": "际关系管理方法\n\n理论 X：假设员工不喜欢并逃避工作，因此管理者必须使用胁迫、威胁和各种控制方案来让员工达到目标\n\n理论 Y：假设个人认为工作就像玩耍或休息一样自然，并享受自尊和自我实现需求的满足\n\n理论 Z：由威廉·大内于 1981 年提出，基于日本激励员工的方法，强调信任、质量、集体决策和文化价值观"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::498", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/9.3 Keys to Managing People / 人员管理的关键理论/9.3.2 赛姆海恩和威利蒙的影响力和权力理论", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 650, "text": "1. Authority: the legitimate hierarchical right to issue orders\n2. Assignment: the project manager's perceived ability to influence a worker's later work assignments\n3. Budget: the project manager's perceived ability to authorize others' use of discretionary funds\n4. Promotion: the ability to improve a worker's position\n5. Money: the ability to increase a worker's pay and benefits\n6. Penalty: the project manager's ability to cause punishment\n7. Work challenge: the ability to assign work that capitalizes on a worker's enjoyment of doing a particular task\n8. Expertise: the project manager's perceived special knowledge that others deem important"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::499", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/9.3 Keys to Managing People / 人员管理的关键理论/9.3.2 赛姆海恩和威利蒙的影响力和权力理论", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 539, "text": "lar task\n8. Expertise: the project manager's perceived special knowledge that others deem important\n9. Friendship: the ability to establish friendly personal relationships between the project manager and others\n\n\n\nProjects are more likely to *succeed* when project managers influence with\n\n- expertise\n- work challenge\n\nProjects are more likely to *fail* when project managers rely too heavily on\n\n- authority\n- money\n- penalty\n\n"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::500", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/9.3 Keys to Managing People / 人员管理的关键理论/9.3.2 赛姆海恩和威利蒙的影响力和权力理论/9.3.2.1 权力（Power）", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 360, "text": "**Power** is the potential ability to influence behavior to get people to do things they would not otherwise do\n\nTypes of power include\n\n- Coercive\n- Legitimate\n- Expert\n- Reward\n- Referent\n\n\n\n\n\n"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::501", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/9.3 Keys to Managing People / 人员管理的关键理论/9.3.2 赛姆海恩和威利蒙的影响力和权力理论/9.3.2.2 柯维的提升效率理论", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 680, "text": "Project managers can apply Covey’s 7 habits to improve effectiveness on projects\n\n- Be proactive\n- Begin with the end in mind\n- Put first things first\n- Think win/win\n- Seek first to understand, then to be understood\n- Synergize\n- Sharpen the saw\n\n\n\n\n\nGood project managers are empathic listeners - they listen with the intent to understand\n\nBefore you can communicate with others, you have to have rapport – a relation of harmony, conformity, accord, or affinity\n\nMirroring is the matching of certain behaviors of the other person, a technique to help establish rapport"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::502", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/9.3 Keys to Managing People / 人员管理的关键理论/9.3.2 赛姆海恩和威利蒙的影响力和权力理论/9.3.2.2 柯维的提升效率理论", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 293, "text": "ng is the matching of certain behaviors of the other person, a technique to help establish rapport\n\nIT professionals need to develop empathic listening and other people's skills to improve relationships with users and other stakeholders\n\n"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::503", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/9.4 Developing the Human Resource Plan / 制定人力资源计划/9.4.1 项目组织结构图", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 526, "text": "Involves identifying and documenting project roles, responsibilities, and reporting relationships\n\nContents include\n\n- project organizational charts\n- staffing management plan\n- responsibility assignment matrixes\n- resource histograms\n\n涉及识别和记录项目角色、职责和报告关系\n\n内容包括\n\n- 项目组织结构图\n- 人员管理计划\n- 责任分配矩阵\n- 资源直方图\n\n\n\n\n\n\n\n"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::504", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/9.4 Developing the Human Resource Plan / 制定人力资源计划/9.4.2 责任分配矩阵", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 365, "text": "A **responsibility assignment matrix (RAM)** is a matrix that maps the work of the project as described in the WBS to the people responsible for performing the work as described in the OBS\n\nCan be created in different ways to meet unique project needs\n\n\n\n"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::505", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/9.4 Developing the Human Resource Plan / 制定人力资源计划/9.4.3 人员配置计划和资源直方图", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 333, "text": "A **staffing management plan** describes when and how people will be added to and taken off the project team\n\n\n\nA **resource histogram** is a column chart that shows the number of resources assigned to a project over time\n\n"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::506", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/9.5 Acquiring the Project Team / 组建项目团队", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 334, "text": "Acquiring qualified people for teams is crucial / 为团队招募合格人员至关重要\n\nThe project manager, who is the smartest person on the team, has done a poor job of recruiting! / 项目经理是团队中最聪明的人，但他的招聘工作做得很差！\n\nIt’s important to assign the appropriate type and number of people to work on projects at the appropriate times / 在适当的时间分配适当类型和数量的人员来从事项目工作非常重要"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::507", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/9.5 Acquiring the Project Team / 组建项目团队/9.5.1 人力资源分配", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::508", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/9.5 Acquiring the Project Team / 组建项目团队/9.5.2 资源负荷", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 478, "text": "**Resource loading** refers to the amount of individual resources an existing schedule requires during specific time periods\n\nHelps project managers develop a general understanding of the demands a project will make on the organization’s resources and individual people’s schedules\n\n**Overallocation** means more resources than are available are assigned to perform work at a given time\n\n**资源负荷**是指现有计划在特定时间段内所需的单个资源量\n\n帮助项目经理对项目对组织资源和个人计划的要求有一个总体了解\n\n**过度分配**意味着在给定时间内分配的资源多于可用资源"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::509", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/9.5 Acquiring the Project Team / 组建项目团队/9.5.3 资源平衡", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 685, "text": "**Resource leveling** is a technique for resolving resource conflicts by delaying tasks\n\nThe main purpose of resource leveling is to create a smoother distribution of resource usage and reduce overallocation\n\n**资源平衡**是一种通过延迟任务来解决资源冲突的技术\n\n资源平衡的主要目的是使资源使用分配更加平稳，减少过度分配\n\n\n\n**Benefits of Resource Leveling / 资源平衡的好处**\n\nWhen resources are used on a more constant basis, they require less management\n\nIt may enable project managers to use a just-in-time inventory type of policy for using subcontractors or other expensive resources\n\nIt results in fewer problems for project personnel and accounting department\n\nIt often improves morale"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::510", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/9.5 Acquiring the Project Team / 组建项目团队/9.5.3 资源平衡", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 188, "text": "esults in fewer problems for project personnel and accounting department\n\nIt often improves morale\n\n当资源被更持续地使用时，它们需要的管理就会减少\n\n它可能使项目经理能够使用即时库存类型的政策来使用分包商或其他昂贵的资源\n\n这会减少项目人员和会计部门的问题\n\n它通常会提高士气"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::511", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/9.6 建设项目团队", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 367, "text": "The main goal of team development is to help people work together more effectively to improve project performance.\n\nIt takes teamwork to successfully complete most projects.\n\n团队建设的主要目标是帮助人们更有效地合作，以提高项目绩效\n\n大多数项目都需要团队合作才能成功完成\n\n**Tuckman Model of Team Development**\n\nForming、Storming、Norming、Performing、Adjourning\n\n"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::512", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/9.6 建设项目团队/9.6.1 培训", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 253, "text": "Training can help people understand themselves, each other, and how to work better in teams\n\nTeam building activities include\n\n- physical challenges\n- psychological preference indicator tools\n\n培训可以帮助人们了解自己、了解彼此，以及如何更好地在团队中工作\n\n团队建设活动包括\n\n- 身体挑战\n- 心理偏好指标工具"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::513", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/9.6 建设项目团队/9.6.2 团队建设活动/9.6.2.1 MBTI", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::514", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/9.6 建设项目团队/9.6.2 团队建设活动/9.6.2.2 社交类型模型", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 336, "text": "People are perceived as behaving primarily in one of four zones, based on their assertiveness and responsiveness:\n\n- Drivers\n- Expressives\n- Analyticals\n- Amiables\n\nPeople on opposite corners (drivers and amiables, analyticals and expressives) may have difficulties getting along\n\n"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::515", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/9.6 建设项目团队/9.6.2 团队建设活动/9.6.2.3 DISC 模型", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 294, "text": "It also uses a four-dimensional model of normal behavior\n\n- Dominance\n- Influence\n- Steadiness\n- Compliance\n\nPeople in opposite quadrants can have problems understanding each other\n\n\n\n"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::516", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/9.6 建设项目团队/9.6.3 奖励和赏识系统", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 297, "text": "Team-based reward and recognition systems can promote teamwork\n\nFocus on rewarding teams for achieving specific goals\n\nAllow time for team members to mentor and help each other to meet project goals and develop human resources\n\n基于团队的奖励和认可系统可以促进团队合作\n\n专注于奖励实现特定目标的团队\n\n留出时间让团队成员互相指导和帮助，以实现项目目标并开发人力资源"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::517", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/9.7 管理项目团队", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 526, "text": "\n\nProject managers must lead their teams in performing various project activities\n\nAfter assessing team performance and related information, the project manager must decide\n\n- if changes should be requested to the project\n- if corrective or preventive actions should be recommended\n- if updates are needed to the project management plan or organizational process assets.\n\n项目经理必须带领其团队开展各种项目活动\n\n在评估团队绩效和相关信息后，项目经理必须决定\n\n- 是否应要求对项目进行变更\n- 是否应建议采取纠正或预防措施\n- 是否需要更新项目管理计划或组织流程资产。"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::518", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/9.7 管理项目团队/9.7.1 管理项目团队的工具和技术", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 136, "text": "Observation and conversation / 观察与对话\n\nProject performance appraisals / 项目绩效评估\n\nInterpersonal skills / 人际交往技巧\n\nConflict management / 冲突管理"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::519", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/9.7 管理项目团队/9.7.1 管理项目团队的工具和技术/9.7.1.2 冲突管理六大模式", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 626, "text": "1.**Confrontation**: Directly face a conflict using a problem-solving approach\n\n2.**Compromise**: Use a give-and-take approach\n\n3.**Smoothing**: De-emphasize areas of difference and emphasize areas of agreement\n\n4.**Forcing**: The win-lose approach\n\n5.**Withdrawal**: Retreat or withdraw from an actual or potential disagreement\n\n6.**Collaborating**: Decision makers incorporate different viewpoints and insights to develop consensus and commitment\n\n1. 对抗：采用解决问题的方法直接面对冲突\n2. 妥协：采用互利互惠的方法\n3. 平滑：淡化分歧，强调一致意见\n4. 强迫：双赢的方法\n5. 撤退：从实际或潜在的分歧中撤退或退出\n6. 合作：决策者吸纳不同的观点和见解，以达成共识和承诺\n\n"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::520", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/9.7 管理项目团队/9.7.1 管理项目团队的工具和技术/9.7.1.2 冲突可以是一件好事", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 532, "text": "Conflict often produces important results, such as new ideas, better alternatives, and motivation to work harder and more collaboratively\n\n**Groupthink**: Conformance to the values or ethical standards of a group. Groupthink can develop if there are no conflicting viewpoints\n\nResearch suggests that task-related conflict often improves team performance, but emotional conflict often depresses team performance\n\n冲突通常会产生重要的结果，例如新想法、更好的替代方案以及更加努力和更协作地工作的动力\n\n群体思维：遵守群体的价值观或道德标准。如果没有冲突的观点，群体思维就会发展\n\n研究表明，与任务相关的冲突通常会提高团队绩效，但情感冲突往往会降低团队绩效"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::521", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/9.7 管理项目团队/9.7.1 管理项目团队的工具和技术/9.7.1.3 团队的五种功能障碍", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 419, "text": "Patrick Lencioni, author of several books on teams, says that “Teamwork remains the one sustainable competitive advantage that has been large untapped”\n\nThe five dysfunctions of teams are\n\n1.Absence of trust\n\n2.Fear of conflict\n\n3.Lack of commitment\n\n4.Avoidance of accountability\n\n5.Inattention to results\n\n撰写过多本关于团队的书的 Patrick Lencioni 表示，“团队合作仍是一项尚未得到充分开发的可持续竞争优势”\n\n团队的五大障碍是\n\n1. 缺乏信任\n2. 害怕冲突\n3. 缺乏承诺\n4. 逃避责任\n5. 不关注结果"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::522", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/9.7 管理项目团队/9.7.2 关于团队管理的一般性建议", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 692, "text": "\n\n1. Be patient and kind with your team\n2. Fix the problem instead of blaming people\n3. Establish regular, effective meetings\n4. Allow time for teams to go through the basic team-building stages\n5. Limit the size of work teams to three to seven members\n6. Plan some social activities to help project team members and other stakeholders get to know each other better\n7. Stress team identity\n8. Nurture team members and encourage them to help each other\n9. Take additional actions to work with virtual team members\n\n1. 对你的团队要有耐心和善意\n2. 解决问题而不是责备他人\n3. 建立定期、有效的会议\n4. 留出时间让团队完成基本的团队建设阶段\n5. 将工作团队的规模限制为三到七名成员\n6. 计划一些社交活动，帮助项目团队成员和其他利益相关者更好地了解彼此"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::523", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/9.7 管理项目团队/9.7.2 关于团队管理的一般性建议", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 147, "text": "不是责备他人\n3. 建立定期、有效的会议\n4. 留出时间让团队完成基本的团队建设阶段\n5. 将工作团队的规模限制为三到七名成员\n6. 计划一些社交活动，帮助项目团队成员和其他利益相关者更好地了解彼此\n7. 强调团队认同\n8. 培养团队成员并鼓励他们互相帮助\n9. 采取额外行动与虚拟团队成员合作"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::524", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 09 Project Human Resource Management / 项目人力资源管理/Chapter Summary", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 317, "text": "Project human resource management includes the processes required to make the most effective use of the people involved with a project\n\nMain processes include\n\n- Plan human resource management\n- Acquire project team\n- Develop project team\n- Manage project team\n\n"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::525", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 10 Project Communications Management / 项目沟通管理/序、必考问答题/**1、项目沟通管理的5个过程**", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 61, "text": "**识别利益相关者；**\n\n**规划沟通；**\n\n**分布信息；**\n\n**管理利益相关者期望；**\n\n**报告绩效；**"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::526", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 10 Project Communications Management / 项目沟通管理/序、必考问答题/**2、项目沟通管理计划应包括哪些内容？**", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 146, "text": "**干系人的沟通需求；**\n\n**需要沟通的信息，包括语言、内容、格式、详细程度；**\n\n**产生和接收信息的个人或小组；**\n\n**传达信息的推荐方式或技术；**\n\n**沟通频率；**\n\n**为解决问题所需的向上提报程序；**\n\n**更新沟通管理计划的再版程序；**\n\n**常用术语表；**"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::527", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 10 Project Communications Management / 项目沟通管理/序、必考问答题/**3、发布信息应该注意哪些方面？**", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 119, "text": "**增加沟通的频次；**\n\n**理解小组和个人的沟通需求；**\n\n**同时使用正式与非正式沟通；**\n\n**用有效、适时的方式发布重要信息；**\n\n**选择适当的交流媒介；**\n\n**为坏消息搭建语境；**\n\n**确定沟通渠道的数量；**"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::528", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 10 Project Communications Management / 项目沟通管理/序、必考问答题/4**、期望管理矩阵包括哪些条目？**", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 42, "text": "**标准；**\n\n**优先权；**\n\n**期望；**\n\n**各项标准的衡量指南；**"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::529", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 10 Project Communications Management / 项目沟通管理/序、必考问答题/**6、改善沟通的一些建议**", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 66, "text": "使用沟通技巧来管理冲突；\n\n开发更好的沟通技巧；\n\n召开有效的会议；\n\n有效使用电子邮件、即时通讯等协作工具；\n\n使用项目沟通模板；"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::530", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 10 Project Communications Management / 项目沟通管理/序、必考问答题/**7、如何有效开会？**", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 96, "text": "确定会议是否必要；\n\n定义会议目的和预期产出；\n\n决定会议参与人；\n\n在会议开启前提供会议议程；\n\n准备手稿和直观教具，提前做好后勤安排；\n\n专业地开会；\n\n为会议制定基本要求；\n\n建立关系；"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::531", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 10 Project Communications Management / 项目沟通管理/序、必考问答题/**8、如何更高效使用电子邮件或其他通讯工具？**", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 92, "text": "选择最适合的媒介；\n\n确保信息发送给了正确的人；\n\n在邮件中使用有意义的主题行，并尽量将内容限制在一个主题下，如果有其他主题，那么就发另外的邮件；\n\n确保授权了合适的人来分享协作文档；"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::532", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 10 Project Communications Management / 项目沟通管理/Learning Objectives / 学习目标", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 562, "text": "Understand the **importance** of good communications on projects and the need to develop soft skills, especially for IT project managers and their teams\n\nReview **key concepts** related to communications\n\nExplain the **elements of planning project communications** and **how to create a communications management plan**\n\nDescribe how to **manage communications**, including communication technologies, media, and performance reporting\n\nDiscuss methods for **controlling communications** to ensure that information needs are met throughout the life of the project"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::533", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 10 Project Communications Management / 项目沟通管理/Learning Objectives / 学习目标", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 380, "text": "lling communications** to ensure that information needs are met throughout the life of the project\n\nList various methods for improving project communications, such as running effective meetings, using various technologies effectively, and using templates\n\nDescribe how software can enhance project communications management\n\n"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::534", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 10 Project Communications Management / 项目沟通管理/10.1 Importance of Good Communications / 项目沟通管理的重要性", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 481, "text": "§ The **greatest threat** to many projects is a failure to communicate\n\n对许多项目来说，最大的威胁是沟通失败。\n\n§ Our culture does not portray IT professionals as being good communicators\n\n我们的文化并没有把IT专业人士描绘成善于沟通的人。\n\n§ Research shows that IT professionals must be able to communicate effectively to **succeed in** their positions\n\n研究表明，IT专业人士必须能够有效地沟通，才能在他们的职位上取得成功。\n\n§ Strong verbal and non-technical skills are a key factor in **career advancement** for IT professionals\n\n强大的语言和非技术技能是IT专业人士职业发展的关键因素"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::535", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 10 Project Communications Management / 项目沟通管理/10.1 Importance of Good Communications / 项目沟通管理的重要性/10.1.2 项目沟通管理的主要过程", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 527, "text": "**Planning communications management**: Determining the information and communications needs of the **stakeholders**\n\n**Managing communications:** Creating, distributing, storing, retrieving, and disposing of project communications based on the communications management plan\n\n**Controlling communications**: Monitoring and controlling project communications to ensure that stakeholder communication needs are met\n\n\n\n"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::536", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 10 Project Communications Management / 项目沟通管理/10.2 Key to Good Communications / 良好沟通的关键要素/[用正确的姿势阅读软件工程圣经 —— 《人月神话》【让阅读再次伟大#1】](https://www.bilibili.com/video/BV1Mr421M7ZX/?spm_id_from=333.999.0.0&vd_source=da1f2d78d73dfaae6ddfbcfe8e4801d8)", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 220, "text": "[看书是为了提升你的综合素养，而不仅仅是代码【直播精华#10】](https://www.bilibili.com/video/BV1xJ4m157KF/?spm_id_from=333.337.search-card.all.click&vd_source=da1f2d78d73dfaae6ddfbcfe8e4801d8)\n\n"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::537", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 10 Project Communications Management / 项目沟通管理/10.2 Key to Good Communications / 良好沟通的关键要素/10.2.1 良好沟通的重要性", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 612, "text": "People are not **interchangeable** parts\n\nAs illustrated in Brooks’ book ***The Mythical Man-Month（人月神话）***, you cannot assume that a task originally scheduled to take two months of one person’s time can be done in one month by two people\n\nNine women cannot produce a baby in one month!\n\n\n\nProject managers say they **spend as much** as 90 percent of their time communicating / 项目经理表示，他们有 90% 的时间用于沟通\n\nNeed to **focus on** group and individual communication **needs** / 需要关注团队和个人的沟通需求\n\nUse **formal and informal** methods for communicating / 使用正式和非正式的方法进行沟通"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::538", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 10 Project Communications Management / 项目沟通管理/10.2 Key to Good Communications / 良好沟通的关键要素/10.2.2 影响沟通需求的要素/10.2.2.1 个人喜好", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 576, "text": "Introverts like more private communications, while extroverts like to discuss things in public / 内向的人喜欢更私密的交流，而外向的人喜欢在公共场合讨论事情\n\nIntuitive people like to understand the big picture, while sensing people need step-by-step details / 直觉型的人喜欢了解大局，而感知型的人需要一步步了解细节\n\nThinkers want to know the logic behind decisions, while feeling people want to know how something affects them personally / 思考型的人想知道决策背后的逻辑，而感知型的人想知道某件事对他们个人的影响\n\nJudging people are driven to meet deadlines while perceiving people need more help in developing and following plans / 判断型的人会被迫按时完成任务，而感知型的人在制定和执行计划时需要更多帮助"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::539", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 10 Project Communications Management / 项目沟通管理/10.2 Key to Good Communications / 良好沟通的关键要素/10.2.2 影响沟通需求的要素/10.2.2.2 鼓励更多面对面交流", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 352, "text": "**Short, frequent meetings** are often very effective in IT projects / 简短、频繁的会议在 IT 项目中通常非常有效\n\n**Stand-up meetings** force people to focus on what they really need to communicate / 站立会议迫使人们专注于他们真正需要沟通的内容\n\nSome companies have policies preventing the use of e-mail between certain hours or even entire days of the week / 一些公司制定了政策，禁止在特定时段甚至一周内的所有日子使用电子邮件"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::540", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 10 Project Communications Management / 项目沟通管理/10.2 Key to Good Communications / 良好沟通的关键要素/10.2.3 Distribute important information in an **effective and timely** manner / 及时有效地分发重要信息", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 334, "text": "§ Don’t bury **crucial information / 不要隐瞒重要的信息**\n\n§ Don’t be afraid to report **bad information / 不要害怕汇报坏信息**\n\n§ **Oral communication** via meetings and informal talks helps bring important information— good and bad — out into the open / 通过会议和非正式会谈进行的口头交流有助于将重要信息——无论好坏——公开\n\n§ Set the stage for communicating **bad news** / 为传达坏消息做好准备"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::541", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 10 Project Communications Management / 项目沟通管理/10.2 Key to Good Communications / 良好沟通的关键要素/10.2.4 Determine the number of **communication channels** / 确定沟通渠道的数量", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::542", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 10 Project Communications Management / 项目沟通管理/10.2 Key to Good Communications / 良好沟通的关键要素/10.2.5 **Other Communication Considerations / 其余沟通考虑**", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 314, "text": "Rarely does the receiver interpret a message exactly as the sender intended\n\n接收方很少完全按照发送方的意思来理解信息\n\nGeographic location and cultural background affect the complexity of project communications / 地理位置和文化背景影响项目沟通的复杂性。\n\n- Different working hours / 不同的工作时间\n- Language barriers / 语言障碍\n- Different cultural norms / 不同的文化规范"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::543", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 10 Project Communications Management / 项目沟通管理/10.3 Planning Communications Management / 计划沟通管理", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 691, "text": "Every project should include some type of **communications management** plan, a document that guides project communications / 每个项目都应该包括某种形式的沟通管理计划，一种指导项目沟通的文件。\n\nThe communications management plan varies with the needs of the project, but some type of written plan should always be prepared / 沟通管理计划随着项目的需要而变化，但总是应该准备某种形式的书面计划。\n\nFor small projects, the communications management plan can be part of the team contract / 对于小项目，沟通管理计划可以作为团队合同的一部分\n\nFor large projects, it should be a separate document / 对于大项目，沟通管理计划应当是被分开的文档\n\n\n\n\n\n"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::544", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 10 Project Communications Management / 项目沟通管理/10.4 **Managing Communications** / 管理沟通", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 457, "text": "Managing communications is a large part of a project manager’s job / 管理沟通是项目经理工作的重要组成部分\n\nGetting project information to the right people at the right time and in a useful format is just as important as developing the information in the first place / 在正确的时间以有用的格式将项目信息传递给正确的人与首先开发信息一样重要\n\nImportant considerations include **the use of technology**, the appropriate methods and **media** to use, and **performance reporting** / 重要的考虑因素包括技术的使用、适当的方法和媒体的使用以及绩效报告"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::545", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 10 Project Communications Management / 项目沟通管理/10.4 **Managing Communications** / 管理沟通/10.4.1 用技术手段加强信息的创建和分配", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 217, "text": "Technology can **facilitate** the process of creating and distributing information, when used properly. It is important to select the appropriate communication method and media\n\n如果使用得当，技术可以促进信息的创造和传播过程。选择合适的传播方法和媒介很重要"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::546", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 10 Project Communications Management / 项目沟通管理/10.4 **Managing Communications** / 管理沟通/10.4.2 选择适当的沟通方法和媒介", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 681, "text": "*1）* ***Interactive communication***: Two or more people interact to exchange information via meetings, phone calls, or video conferencing. Most effective way to ensure common understanding\n\n*2）* ***Push communication***: Information is sent or pushed to recipients without their request via reports, e-mails, faxes, voice mails, and other means. Ensures that the information is distributed, but does not ensure that it was received or understood\n\n*3）* ***Pull communication***: Information is sent to recipients at their request via Web sites, bulletin boards, e-learning, knowledge repositories like blogs, and other means\n\n"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::547", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 10 Project Communications Management / 项目沟通管理/10.4 **Managing Communications** / 管理沟通/10.4.3 报告绩效", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 454, "text": "Performance reporting keeps stakeholders informed about how resources are being used to achieve project objectives\n\n- **Status reports** describe where the project stands at a specific point in time\n- **Progress reports** describe what the project team has accomplished during a certain period of time\n- **Forecasts** predict future project status and progress based on past information and trends\n\n"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::548", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 10 Project Communications Management / 项目沟通管理/10.5 Controlling Communications / 控制沟通", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 643, "text": "The main goal of controlling communications is to **ensure the optimal flow of information** throughout the entire project life cycle\n\nThe project manager and project team should use their various **reporting systems, expert judgment, and meetings** to assess how well communications are working. If problems exist, the project manager and team need to take action, which often requires changes to the earlier processes of planning and managing project communications\n\nIt is often beneficial to have a facilitator from outside the project team assess how well communications are working\n\n"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::549", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 10 Project Communications Management / 项目沟通管理/10.6 **Suggestions for Improving Project Communications / 改进项目沟通的建议**", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 433, "text": "Develop better communication skills\n\nRun effective meetings\n\nUse e-mail and other technologies effectively\n\nUse templates for project communications\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg::550", "page_id": "docx::GRACwqU1HiVz28kZo2Bcp8kxnDg", "title": "PM 讲义（三）Chapter 08 ~ 10", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（三）Chapter 08 ~ 10", "section": "Chapter 10 Project Communications Management / 项目沟通管理/Chapter Summary", "url": "https://a1npn29y3xu.feishu.cn/wiki/GRACwqU1HiVz28kZo2Bcp8kxnDg", "source_type": "docx", "n_chars": 331, "text": "The goal of project communications management is to ensure timely and appropriate generation, collection, dissemination, storage, and disposition of project information\n\nMain process include:\n\n- Plan communications management\n- Manage communications\n- Control communications\n\n"}
{"id": "docx::UJqxwklZfilfE3kPEx2cBFXDnvc::551", "page_id": "docx::UJqxwklZfilfE3kPEx2cBFXDnvc", "title": "PM 讲义（二）Chapter 04 ~ 07 最重要！", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 讲义（二）Chapter 04 ~ 07 最重要！", "section": "PM 讲义（二）Chapter 04 \\~ 07 最重要！", "url": "https://a1npn29y3xu.feishu.cn/wiki/UJqxwklZfilfE3kPEx2cBFXDnvc", "source_type": "docx", "n_chars": 384, "text": ""}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::552", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/The definition, concepts, and types of **Module Structure**, **Allocation Structure**, and **C&C Structure**. For example, 7 categories of design decisions? Its Role in Project Risk Reduction (How to reduce risks)?", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 82, "text": "模块结构、分配结构和C&C结构的定义、概念和类型。\n\n"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::553", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/The definition, concepts, and types of **Module Structure**, **Allocation Structure**, and **C&C Structure**. For example, 7 categories of design decisions? Its Role in Project Risk Reduction (How to reduce risks)?/Module Structure", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 511, "text": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::554", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/The definition, concepts, and types of **Module Structure**, **Allocation Structure**, and **C&C Structure**. For example, 7 categories of design decisions? Its Role in Project Risk Reduction (How to reduce risks)?/Allocation Structure", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 397, "text": "\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::555", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/The definition, concepts, and types of **Module Structure**, **Allocation Structure**, and **C&C Structure**. For example, 7 categories of design decisions? Its Role in Project Risk Reduction (How to reduce risks)?/C&C Structures", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 340, "text": "\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::556", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/The definition, concepts, and types of **Module Structure**, **Allocation Structure**, and **C&C Structure**. For example, 7 categories of design decisions? Its Role in Project Risk Reduction (How to reduce risks)?/① **Seven categories** of design decisions?", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 66, "text": "七种设计决策的类别\n\n"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::557", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/The definition, concepts, and types of **Module Structure**, **Allocation Structure**, and **C&C Structure**. For example, 7 categories of design decisions? Its Role in Project Risk Reduction (How to reduce risks)?/② Its **role in project risk reduction**? (how to reduce risks?)", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 466, "text": "它在项目风险降低中的作用是什么？（如何降低风险？）\n\nSoftware architecture plays a critical role in reducing risks by providing a clear structure that supports system design, development, and evolution. It influences decisions about scalability, maintainability, performance, and security.\n\n1. Decompose Complexity: By breaking down the system into manageable modules or components, you reduce the complexity of individual parts, making the system easier to understand, develop, and maintain."}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::558", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/The definition, concepts, and types of **Module Structure**, **Allocation Structure**, and **C&C Structure**. For example, 7 categories of design decisions? Its Role in Project Risk Reduction (How to reduce risks)?/② Its **role in project risk reduction**? (how to reduce risks?)", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 583, "text": "the complexity of individual parts, making the system easier to understand, develop, and maintain.\n2. Design for Change: Designing components with well-defined interfaces and minimal dependencies between them ensures that future changes can be made without affecting other parts of the system. This reduces the risk of costly and time-consuming rework.\n3. Fault Tolerance and Redundancy: Implementing failover mechanisms and redundant systems in the allocation structure helps ensure that the system remains operational even in the face of hardware failures or unexpected conditions."}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::559", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/The definition, concepts, and types of **Module Structure**, **Allocation Structure**, and **C&C Structure**. For example, 7 categories of design decisions? Its Role in Project Risk Reduction (How to reduce risks)?/② Its **role in project risk reduction**? (how to reduce risks?)", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 617, "text": "that the system remains operational even in the face of hardware failures or unexpected conditions.\n4. Performance and Scalability: Properly designing how components are distributed and how tasks are allocated across hardware resources ensures that the system can scale efficiently, thus avoiding performance bottlenecks that might cause project delays or cost overruns.\n5. Security Considerations: Architecture decisions that consider security upfront can prevent costly security breaches, reduce vulnerability, and ensure compliance with regulations, ultimately lowering the risk of legal or financial consequences."}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::560", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/The definition, concepts, and types of **Module Structure**, **Allocation Structure**, and **C&C Structure**. For example, 7 categories of design decisions? Its Role in Project Risk Reduction (How to reduce risks)?/② Its **role in project risk reduction**? (how to reduce risks?)", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 560, "text": "nsure compliance with regulations, ultimately lowering the risk of legal or financial consequences.\n6. Early Prototyping and Validation: Architecture allows teams to build prototypes or models of high-risk components early in the project, which can validate design assumptions and reduce the risk of costly design changes later in the process.\n7. Documentation and Communication: Clear architectural decisions and documentation help align the development team, reducing misunderstandings and rework that could arise from unclear or incomplete design decisions."}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::561", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/The definition, concepts, and types of **Module Structure**, **Allocation Structure**, and **C&C Structure**. For example, 7 categories of design decisions? Its Role in Project Risk Reduction (How to reduce risks)?/② Its **role in project risk reduction**? (how to reduce risks?)", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 269, "text": "educing misunderstandings and rework that could arise from unclear or incomplete design decisions.\n\nBy incorporating these strategies, the architecture ensures that the system is robust, flexible, and capable of handling change, thereby minimizing risks to the project."}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::562", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/The types, concepts, and tactics of QAs./① **Availability** and related tactics (e.g. **how to detect faults?**)", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 648, "text": "可用性及相关策略（例如，如何检测故障？）。\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::563", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/The types, concepts, and tactics of QAs./① **Availability** and related tactics (e.g. **how to detect faults?**)", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 383, "text": "ishu.cn/file/SjetblpkfosvDsxF1vDcSyklnMe)\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::564", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/The types, concepts, and tactics of QAs./② **Performance** and related tactics", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 692, "text": "性能及相关策略。\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::565", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/The types, concepts, and tactics of QAs./② **Performance** and related tactics", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 440, "text": "ishu.cn/file/AxxibXZqioQfp4xQbrFcoVRWnnc)\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::566", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/Architectural Pattern.", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::567", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/Architectural Pattern./① **P2P**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 353, "text": "definition, basic concepts, related QAs (e.g., availability and performance), weaknesses (how to improve?), strengths, and trade-offs.\n\nP2P的定义、基本概念、相关质量属性（例如，可用性和性能）、弱点（如何改进？）、优势和权衡。\n\n\n\n\n\n"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::568", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/Architectural Pattern./② **MapReduce**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 644, "text": "definition, basic concepts, related QAs (e.g., availability and performance), weaknesses (how to improve?), strengths, and trade-offs.\n\nMapReduce的定义、基本概念、相关质量属性（例如，可用性和性能）、弱点（如何改进？）、优势和权衡。\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::569", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/Architectural Pattern./③ **Pipe-and-Filter**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 299, "text": "definition, basic concepts, related QAs (e.g., availability and performance), weaknesses (how to improve?), strengths, and trade-offs.\n\n管道与过滤器的定义、基本概念、相关质量属性（例如，可用性和性能）、弱点（如何改进？）、优势和权衡。\n\n\n\n"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::570", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/**ATAM** (architectural reasons), **Participants’ Roles**, the usage of **Utility Tree**.", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 25, "text": "ATAM（架构原因）、参与者的角色、效用树的使用。"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::571", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/**ATAM** (architectural reasons), **Participants’ Roles**, the usage of **Utility Tree**./ATAM", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 682, "text": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::572", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/**ATAM** (architectural reasons), **Participants’ Roles**, the usage of **Utility Tree**./ATAM", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 326, "text": "ishu.cn/file/RDlPb9gWsoP17Zx8zNUcdMuPnme)\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::573", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/**ATAM** (architectural reasons), **Participants’ Roles**, the usage of **Utility Tree**./Participant's Roles", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::574", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/**ATAM** (architectural reasons), **Participants’ Roles**, the usage of **Utility Tree**./Utility Tree", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 283, "text": "\n\n\n\n\n\n\n\n"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::575", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/Open discussion./① The abstract common services tactic is intended to **reduce coupling**, **but it also might reduce cohesion**?", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 278, "text": "抽象公共服务策略旨在减少耦合，但它也可能减少内聚性？\n\nThe tactic of using abstract common services to reduce coupling is often a key design consideration in software architecture, especially in systems that need to scale, evolve, or maintain flexibility. Here's how it works and the potential trade-offs:"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::576", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/Open discussion./① The abstract common services tactic is intended to **reduce coupling**, **but it also might reduce cohesion**?/**Reducing Coupling**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 640, "text": "- Coupling refers to the degree to which one component (or module) depends on another. The idea behind using abstract common services is to centralize common functionality (e.g., logging, authentication, data access) in shared services, so that individual components don't need to implement the same logic or directly reference one another.\n- By defining abstract interfaces for these services, different modules or components can rely on the service without being tightly coupled to the specific implementation. This makes the system more modular, as individual components can evolve independently as long as they conform to the interface."}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::577", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/Open discussion./① The abstract common services tactic is intended to **reduce coupling**, **but it also might reduce cohesion**?/**Reducing Cohesion**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 700, "text": "- Cohesion, on the other hand, refers to how closely the responsibilities of a single component or module are related to each other. High cohesion means that the responsibilities of a component are highly related and focused. For example, a service that only handles user authentication has high cohesion.\n- When we abstract common services, there’s a risk that cohesion within components might decrease. For instance, instead of a service being highly focused on a particular domain (e.g., payment processing), it might have to deal with a broader set of concerns, like interacting with multiple abstracted common services (e.g., logging, security, and error handling). This could dilute the service"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::578", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/Open discussion./① The abstract common services tactic is intended to **reduce coupling**, **but it also might reduce cohesion**?/**Reducing Cohesion**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 132, "text": "tracted common services (e.g., logging, security, and error handling). This could dilute the service’s focus, reducing its cohesion."}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::579", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/Open discussion./① The abstract common services tactic is intended to **reduce coupling**, **but it also might reduce cohesion**?/**Balance**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 590, "text": "The key challenge here is balancing reducing coupling with maintaining high cohesion. By abstracting common functionality, you reduce direct dependencies between modules, but you also risk over-generalizing the services, leading to poor cohesion or making services harder to understand and maintain. The design should ensure that:\n\n- Common services are generic enough to serve multiple components, but not so abstract that they lose the focus or purpose of a specific domain.\n- Cohesion is preserved at the component level so that the domain logic of each module remains clear and focused."}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::580", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 33, "text": "讨论编程语言的选择（作为技术选择的一个例子）及其与架构的一般关系。"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::581", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/Open discussion./Solution A", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 231, "text": "Choosing the right programming language or technology stack is one of the most crucial decisions in software architecture, as it can have a significant impact on architecture's design, maintainability, scalability, and performance."}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::582", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/Open discussion./Solution A/**Programming Language and Architecture**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 638, "text": "The programming language or framework you choose for a system is tightly coupled with architecture in several ways:\n\n1. Performance Considerations:\n\n - Some languages (like C++ or Rust) offer fine-grained control over system resources (e.g., memory management, concurrency), which can be crucial for high-performance systems like embedded software or real-time applications.\n - Other languages (like Python or Ruby) prioritize developer productivity over raw performance. These languages often favor ease of development, but may not be suitable for performance-critical components without optimization.\n2. Concurrency and Parallelism:"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::583", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/Open discussion./Solution A/**Programming Language and Architecture**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 585, "text": "suitable for performance-critical components without optimization.\n2. Concurrency and Parallelism:\n\n - Different programming languages have varying levels of support for concurrency and parallelism. For instance, Go and Erlang provide strong concurrency models natively, making them excellent choices for distributed systems and services that require high levels of concurrency.\n - Languages like Java or C# provide concurrency models through threading and async programming, but handling concurrency might require more boilerplate or configuration.\n3. Scalability and Flexibility:"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::584", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/Open discussion./Solution A/**Programming Language and Architecture**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 577, "text": "dling concurrency might require more boilerplate or configuration.\n3. Scalability and Flexibility:\n\n - Languages like JavaScript (with Node.js) or Python have thriving ecosystems for building scalable web applications due to their vast libraries and frameworks (e.g., Express.js, Flask, Django).\n - For microservices architectures, some languages (e.g., Java, Go, Node.js) may offer better support for rapid service deployment, while others (like PHP or Ruby) may face challenges scaling effectively, especially in high-concurrency environments.\n4. Ecosystem and Libraries:"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::585", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/Open discussion./Solution A/**Programming Language and Architecture**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 629, "text": "nges scaling effectively, especially in high-concurrency environments.\n4. Ecosystem and Libraries:\n\n - The ecosystem of a language plays a big role in the architecture. Languages like Java and Python have mature ecosystems with frameworks for almost any problem—whether it’s web development, data science, or machine learning. This can simplify architectural decisions, as many off-the-shelf solutions are available.\n - On the other hand, choosing a language with a smaller ecosystem could require more custom-built solutions, which may increase the complexity of the architecture.\n5. Maintainability and Developer Expertise:"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::586", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/Open discussion./Solution A/**Programming Language and Architecture**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 622, "text": "which may increase the complexity of the architecture.\n5. Maintainability and Developer Expertise:\n\n - A language’s simplicity (or complexity) affects maintainability. Python is known for its simplicity, making it easy to understand and maintain code, but it may not offer the same level of type safety or performance guarantees as Java or C++.\n - Similarly, the team's expertise in a particular language is a crucial factor in architectural decisions. Adopting a language your team is proficient in will reduce the time needed for development and ensure long-term maintainability of architecture.\n6. Interoperability:"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::587", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/Open discussion./Solution A/**Programming Language and Architecture**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 471, "text": "needed for development and ensure long-term maintainability of architecture.\n6. Interoperability:\n\n - In a modern software system, interoperability between components is often required. For example, if you are building a system where some components are written in Java and others in Python, choosing languages that facilitate easy integration (e.g., through REST APIs, message queues, or shared data formats like JSON or Protocol Buffers) will shape your architecture."}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::588", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/Open discussion./Solution A/**Examples of Technology Choices and Architecture**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 593, "text": "- A microservices architecture might be best served by a combination of languages, depending on the specific needs of each service. For instance, the authentication service might be written in Go for fast performance and scalability, while the data analytics service might be built with Python for its rich ecosystem of machine learning libraries.\n- A monolithic application, on the other hand, might prefer a Java or C# stack, where strong typing, scalability, and the mature frameworks (e.g., Spring, ASP.NET) are beneficial for handling the complexity of a large, tightly integrated system."}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::589", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/Open discussion./Solution A/**Conclusion**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 548, "text": "The choice of programming language and the overall technology stack directly influence the architecture of a system by shaping the design patterns, deployment strategies, and scalability approaches. It is important to consider the specific needs of the application, the expertise of the team, and the long-term maintenance implications when selecting the appropriate technologies. Ultimately, the goal is to choose technologies that align with the architectural goals, whether those are modularity, scalability, performance, or ease of development."}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::590", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/Open discussion./Solution B", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 506, "text": "In the context of software architecture, the choice of programming language plays a critical role in shaping the design and structure of a system. Each language comes with its strengths and weaknesses, and its impact on system architecture can vary depending on the goals of the application, the team's expertise, and the technical environment. Below, we will compare **Java** and **Python**, two commonly used programming languages, and discuss how their characteristics influence architectural decisions."}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::591", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/Open discussion./Solution B/**Java: Strengths and Architectural Impact**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 683, "text": "1. **Performance and Efficiency**:\n\n - **Java** is a statically typed language known for its high performance, especially in large-scale, enterprise-level applications. The Java Virtual Machine (JVM) allows Java programs to be platform-independent, providing **cross-platform portability** and consistent performance across different environments.\n - Java’s **strong typing** and **compilation** process catch errors early in the development cycle, which contributes to maintainability, stability, and predictable performance in large systems. This makes it well-suited for **enterprise architecture**, where stability, security, and performance are critical.\n2. **Scalability**:"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::592", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/Open discussion./Solution B/**Java: Strengths and Architectural Impact**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 697, "text": "prise architecture**, where stability, security, and performance are critical.\n2. **Scalability**:\n\n - Java is widely used in **large-scale systems** and has proven to scale well in highly concurrent and distributed environments. It supports multi-threading and parallel processing natively through its robust concurrency libraries (e.g., **Executor Framework**, **Concurrency Utilities**).\n - In architectures such as **microservices**, Java is often preferred due to its strong support for **scalable** and **fault-tolerant** services. Additionally, Java's JVM is optimized for **long-running applications**, making it ideal for systems that require high uptime.\n3. **Enterprise Ecosystem**:"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::593", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/Open discussion./Solution B/**Java: Strengths and Architectural Impact**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 664, "text": "applications**, making it ideal for systems that require high uptime.\n3. **Enterprise Ecosystem**:\n\n - Java has a mature ecosystem with many **frameworks** that support enterprise-level architecture, such as **Spring**, **Hibernate**, and **Java EE** (Jakarta EE). These frameworks provide tools for handling persistence, transactions, security, and web services, making it easy to integrate different components of a large system.\n - Java’s strong ecosystem is particularly beneficial when adopting **Layered Architectures** (e.g., MVC, 3-tier), where the separation of concerns between the user interface, business logic, and data access layers is essential."}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::594", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/Open discussion./Solution B/**Java: Strengths and Architectural Impact**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 629, "text": "ration of concerns between the user interface, business logic, and data access layers is essential.\n4. **Interoperability and Integration**:\n\n - Java integrates well with **other languages** and technologies, especially in large systems where multiple technologies must coexist. For example, Java applications often use **REST APIs**, **SOAP** services, or **message queues** to communicate with other components written in different languages. Its strong support for integration through **web services** makes it well-suited for **service-oriented architectures (SOA)** and **microservices**.\n5. **Long-Term Maintainability**:"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::595", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/Open discussion./Solution B/**Java: Strengths and Architectural Impact**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 507, "text": "**service-oriented architectures (SOA)** and **microservices**.\n5. **Long-Term Maintainability**:\n\n - Java's static typing, clear object-oriented principles, and rigorous development practices (e.g., unit testing, design patterns) contribute to long-term maintainability and developer collaboration in large teams. Its popularity in the **enterprise software industry** has created a large pool of resources, documentation, and developers, which further supports its role in mission-critical applications."}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::596", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/Open discussion./Solution B/**Python: Strengths and Architectural Impact**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 457, "text": "1. **Rapid Development and Flexibility**:\n\n - **Python** is dynamically typed and interpreted, making it ideal for **rapid prototyping** and **quick development**. Python’s syntax is simple and expressive, which makes it a great choice for projects where time-to-market is a priority. This characteristic makes Python particularly suitable for **startups**, **MVPs**, or experimental applications where iterative development and flexibility are important."}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::597", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/Open discussion./Solution B/**Python: Strengths and Architectural Impact**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 429, "text": ", **MVPs**, or experimental applications where iterative development and flexibility are important.\n - However, Python’s dynamic nature can introduce runtime errors that are harder to detect compared to statically typed languages like Java. This can be a challenge for large, complex systems, where **predictability** and **robust error handling** are important architectural considerations.\n2. **Performance and Scalability**:"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::598", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/Open discussion./Solution B/**Python: Strengths and Architectural Impact**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 468, "text": "t error handling** are important architectural considerations.\n2. **Performance and Scalability**:\n\n - Python is generally **slower** than Java, particularly for CPU-bound tasks. Its interpreted nature and dynamic typing can lead to performance bottlenecks, especially in high-performance or high-throughput applications. However, Python can be optimized using external libraries written in **C** or **Cython**, which can mitigate performance concerns in some cases."}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::599", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/Open discussion./Solution B/**Python: Strengths and Architectural Impact**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 522, "text": "al libraries written in **C** or **Cython**, which can mitigate performance concerns in some cases.\n - Python is well-suited for **lightweight services** and **high-level applications**, but for systems that require intensive processing, Python might need to be supplemented with other technologies (e.g., C++ for performance-critical modules). For example, Python is commonly used in **data science** and **machine learning**, where its ease of use outweighs the performance concerns.\n3. **Data-Centric Architectures**:"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::600", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/Open discussion./Solution B/**Python: Strengths and Architectural Impact**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 434, "text": "ng**, where its ease of use outweighs the performance concerns.\n3. **Data-Centric Architectures**:\n\n - Python’s extensive ecosystem of libraries for **data processing** (e.g., **NumPy**, **Pandas**, **TensorFlow**, **PyTorch**) makes it a natural fit for **data-centric architectures**. When building systems that rely heavily on **data manipulation**, **analytics**, or **machine learning**, Python is often the language of choice."}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::601", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/Open discussion./Solution B/**Python: Strengths and Architectural Impact**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 449, "text": "ata manipulation**, **analytics**, or **machine learning**, Python is often the language of choice.\n - Python is also widely used in the **web development** space with frameworks like **Django** and **Flask**, which promote rapid development and agile methodologies. These frameworks support the creation of **RESTful APIs**, **web applications**, and **microservices** quickly and efficiently.\n4. **Microservices and Cloud-Native Architectures**:"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::602", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/Open discussion./Solution B/**Python: Strengths and Architectural Impact**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 484, "text": "nd **microservices** quickly and efficiently.\n4. **Microservices and Cloud-Native Architectures**:\n\n - While **Java** is often the go-to for large-scale enterprise microservices architectures, **Python** has become a strong contender in the realm of **cloud-native architectures**. Python’s minimalistic approach and the wide range of **cloud integration libraries** (e.g., **Boto3** for AWS) make it easy to deploy Python services in cloud environments, such as AWS, GCP, or Azure."}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::603", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/Open discussion./Solution B/**Python: Strengths and Architectural Impact**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 448, "text": "for AWS) make it easy to deploy Python services in cloud environments, such as AWS, GCP, or Azure.\n - Python’s compatibility with **containerization technologies** like **Docker** and **Kubernetes** also makes it well-suited for **microservice architectures**, where small, independently deployable services are key. Python is commonly used to develop smaller, lighter-weight services in a microservices ecosystem.\n5. **Community and Ecosystem**:"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::604", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/Open discussion./Solution B/**Python: Strengths and Architectural Impact**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 668, "text": "lop smaller, lighter-weight services in a microservices ecosystem.\n5. **Community and Ecosystem**:\n\n - Python has a large and active **open-source community**, especially in fields like **data science**, **web development**, and **automation**. This community-driven development has created a rich ecosystem of **libraries** and **tools** that can greatly speed up development in specific domains (e.g., **Flask**, **Django**, **FastAPI** for web services).\n - However, Python’s ecosystem is less mature than Java’s when it comes to **enterprise-level** solutions, especially for areas like **transaction management**, **security**, and **enterprise integration**."}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::605", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/Open discussion./Solution B/**Architectural Trade-Offs: Java vs. Python**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 619, "text": "- **Enterprise-Scale Systems**: Java is better suited for enterprise-level applications requiring high performance, stability, and scalability. Its strong typing and robust frameworks (e.g., **Spring Boot**) support large, complex systems with well-defined layers (e.g., data, business logic, presentation).\n- **Rapid Development and Flexibility**: Python excels in projects that require rapid iteration, ease of development, and flexibility. It is commonly used in systems that prioritize **developer productivity** and **quick turnaround** times, such as **startups**, **MVPs**, and **machine learning applications**."}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::606", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/Open discussion./Solution B/**Architectural Trade-Offs: Java vs. Python**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 697, "text": "**quick turnaround** times, such as **startups**, **MVPs**, and **machine learning applications**.\n- **Performance**: Java tends to outperform Python in CPU-intensive applications due to its statically typed nature and compiled code running on the JVM. For high-performance systems (e.g., large-scale distributed systems, real-time applications), Java is generally a better choice.\n- **Scalability**: Both languages can be used in scalable systems, but Java is typically favored in environments requiring **high concurrency** and **fault tolerance**. Python can also scale, but it might require additional optimization techniques or the use of other technologies to handle heavy loads effectively."}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::607", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/Open discussion./Solution B/**Architectural Trade-Offs: Java vs. Python**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 467, "text": "itional optimization techniques or the use of other technologies to handle heavy loads effectively.\n- **Microservices**: Both Java and Python can work in microservices architectures, but the choice depends on the use case. Java is better for **large-scale microservices** with strict requirements on **transaction management**, **reliability**, and **performance**, while Python is often used for **smaller, quicker-to-develop services** in cloud-native environments."}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::608", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/Open discussion./Solution B/**Conclusion**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 700, "text": "The choice between **Java** and **Python** has a significant impact on the **architecture** of a system. Java is typically chosen for its performance, scalability, and strong ecosystem for building large, enterprise-level systems, while Python is selected for its rapid development capabilities, flexibility, and strong support for data-centric architectures and cloud-native applications. The decision depends largely on the requirements of the project—whether you need high performance, robust frameworks for enterprise-level solutions, or a quick, agile development process with strong support for data science and machine learning. Understanding the trade-offs between these two languages can hel"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::609", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/Open discussion./Solution B/**Conclusion**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 171, "text": "data science and machine learning. Understanding the trade-offs between these two languages can help architects make more informed decisions based on their system’s needs."}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::610", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 I 卷/textbook **P409 English version**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::611", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 II 卷/**Software architecture**'s definition and concept", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 318, "text": "软件架构的定义和概念。\n\n\n\n\n\n\n\nThe definition, concepts, and types of **Module Structure, Allocation Structure, and C&C Structure ( X1 )**\n\n模块结构、分配结构和C&C结构的定义、概念和类型。"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::612", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 II 卷/Relationships between **Pattern** and **Tactics**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 239, "text": "\n\n模式与策略之间的关系。\n\n\n\n\n\n"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::613", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 II 卷/The types, concepts, and tactics of QAs", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 191, "text": "质量属性的类型、概念和策略。例如，\n\n① **Availability** and related tactics (e.g. **how to detect faults?**) **（ X2 1️⃣ ）**\n\n可用性及相关策略（例如，如何检测故障？）\n\n② **Performance** and related tactics **（ X2 2️⃣ )**\n\n性能及相关策略。"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::614", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 II 卷/The types, concepts, and tactics of QAs/③ **Security** and related tactics", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 693, "text": "安全性及相关策略。\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::615", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 II 卷/The types, concepts, and tactics of QAs/③ **Security** and related tactics", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 383, "text": "ishu.cn/file/I1PLbQPTRoSrZIx7BvxcufM9noc)\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::616", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 II 卷/The types, concepts, and tactics of QAs/④ **Interoperability** and related tactics (e.g. how Service Discovery works)", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 652, "text": "互操作性及相关策略（例如，服务发现是如何工作的）。\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::617", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 II 卷/The types, concepts, and tactics of QAs/④ **Interoperability** and related tactics (e.g. how Service Discovery works)", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 611, "text": "ishu.cn/file/JhHhb8a3ToXeUoxjfRBcxCEfngI)\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::618", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 II 卷/The types, concepts, and tactics of QAs/⑤ **Quality** attribute scenarios/真题集锦", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 283, "text": "\n\n\n\n\n\n\n\n"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::619", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 II 卷/The types, concepts, and tactics of QAs/⑤ **Quality** attribute scenarios/Chapter 05 Availability", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::620", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 II 卷/The types, concepts, and tactics of QAs/⑤ **Quality** attribute scenarios/Chapter 06 Interoperability", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::621", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 II 卷/The types, concepts, and tactics of QAs/⑤ **Quality** attribute scenarios/Chapter 07 Modifiability", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::622", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 II 卷/The types, concepts, and tactics of QAs/⑤ **Quality** attribute scenarios/Chapter 08 Performance", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::623", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 II 卷/The types, concepts, and tactics of QAs/⑤ **Quality** attribute scenarios/Chapter 09 Security", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 226, "text": "\n\n\n\n\n\n"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::624", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 II 卷/The types, concepts, and tactics of QAs/⑤ **Quality** attribute scenarios/Chapter 10 Testability", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 169, "text": "\n\n\n\n"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::625", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 II 卷/The types, concepts, and tactics of QAs/⑤ **Quality** attribute scenarios/Chapter 11 Usability", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::626", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 II 卷/The types, concepts, and tactics of QAs/⑤ **Quality** attribute scenarios/Chapter 12 Other Quality attributes", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 673, "text": "[iso25000.com](https://iso25000.com/index.php/en/iso-25000-standards/iso-25010)\n\n[ISO/IEC 25010 Software Quality Standard](https://thetechnologyvault.com/iso-25010-software-quality-standard#:~:text=ISO%2FIEC%2025010%20%28often%20referred%20to%20as%20simply%20ISO,model%20for%20assessing%20the%20quality%20of%20software%20products.)\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::627", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 II 卷/The types, concepts, and tactics of QAs/⑤ **Quality** attribute scenarios/Chapter 12 Other Quality attributes", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 155, "text": "ishu.cn/file/MB2bbTlF4oc2gBxMJlzcTvYHnOc)\n\n\n\n"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::628", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 II 卷/**Architectural Pattern**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 433, "text": "架构模式。例如，\n\n① **P2P's** definition, basic concepts, related QAs (e.g., availability and performance) weaknesses (how to improve?), strengths, and trade-offs**（ X3 1️⃣）**\n\nP2P的定义、基本概念、相关质量属性（例如，可用性和性能）、弱点（如何改进？）、优势和权衡。\n\n② **MapReduce's** definition, basic concepts, related QAs (e.g., availability and performance) weaknesses (how to improve?), strengths, and trade-offs**（X3 2️⃣）**\n\nMapReduce的定义、基本概念、相关质量属性（例如，可用性和性能）、弱点（如何改进？）、优势和权衡。"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::629", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 II 卷/**Architectural Pattern**/③ **Pub/Sub**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 697, "text": "definition, basic concepts, related QAs (e.g., availability and performance), weaknesses (how to improve?), strengths, and trade-offs.\n\n发布/订阅的定义、基本概念、相关质量属性（例如，可用性和性能）、弱点（如何改进？）、优势和权衡。\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::630", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 II 卷/**Architectural Pattern**/③ **Pub/Sub**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 554, "text": "ishu.cn/file/O9t6bNvkno3uKixlPtacR4ZknLf)\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::631", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 II 卷/**Architectural Pattern**/④ **MVC's**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 408, "text": "definition, basic concepts, related QAs (e.g., availability and performance) weaknesses (how to improve?), strengths, and trade-offs\n\nMVC的定义、基本概念、相关质量属性（例如，可用性和性能）、弱点（如何改进？）、优势和权衡。\n\n\n\n\n\n\n\n"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::632", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 II 卷/**Architectural Pattern**/④ **MVC's**/批注：Java Go Python 的 MVC 应用（感兴趣的同学可自行去框架官方文档处学习）", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 146, "text": "Java：https://docs.spring.io/spring-framework/reference/web/webmvc.html\n\nGo：https://revel.github.io/\n\nPython：https://docs.djangoproject.com/en/5.1/"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::633", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 II 卷/Definition, concepts, and steps (procedure) of **ATAM✅, ASRs, ADD, and Utility Tree✅**", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 31, "text": "ATAM、ASRs、ADD和效用树的定义、概念和步骤（程序）。"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::634", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 II 卷/Definition, concepts, and steps (procedure) of **ATAM✅, ASRs, ADD, and Utility Tree✅**/ASRs", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 340, "text": "\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::F0RRwY3LoingoMk36vGcWptjnyg::635", "page_id": "docx::F0RRwY3LoingoMk36vGcWptjnyg", "title": "SA 2024 真题知识点复习（纯英文，AB 卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（纯英文，AB 卷）", "section": "✅新高考/新高考 II 卷/Definition, concepts, and steps (procedure) of **ATAM✅, ASRs, ADD, and Utility Tree✅**/ADD", "url": "https://a1npn29y3xu.feishu.cn/wiki/F0RRwY3LoingoMk36vGcWptjnyg", "source_type": "docx", "n_chars": 625, "text": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::636", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/纯英文 PPT 版本（两卷分离）", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 105, "text": ""}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::637", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/**Software architecture**'s definition and concept/ 软件架构的定义和概念。/What is Software Architecture? / 什么是软件架构？", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 222, "text": "The software architecture of a system is the set of structures needed to reason about the system, which comprise software elements, relations among them, and properties of both. / 系统的软件架构是理解系统所需的结构集合，包括软件元素、元素之间的关系以及它们的属性。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::638", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/**Software architecture**'s definition and concept/ 软件架构的定义和概念。/Architecture is a Set of Software Structures / 架构是软件结构的集合", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 378, "text": "A structure is a set of elements held together by a relation. / 结构是由关系连接在一起的一组元素。\n\nSoftware systems are composed of many structures, and no single structure holds claim to being the architecture. / 软件系统由许多结构组成，没有单一的结构可以称为架构。\n\nThere are three important categories of architectural structures: / 架构有三个重要的结构类别：\n\n1. Module / 模块\n2. Component and Connector / 组件与连接器\n3. Allocation / 分配"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::639", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/**Software architecture**'s definition and concept/ 软件架构的定义和概念。/Which Structures are Architectural? / 哪些结构是架构性的？", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 566, "text": "A structure is architectural if it supports reasoning about the system and the system's properties. / 如果一个结构有助于推理系统及其属性，则该结构是架构性的。\n\nThe reasoning should be about an attribute of the system that is important to some stakeholder. / 该推理应关注系统的一个属性，该属性对某些利益相关者至关重要。\n\nThese include:\n\n这些包括：\n\n- Functionality achieved by the system / 系统实现的功能\n- The availability of the system in the face of faults / 系统在面对故障时的可用性\n- The difficulty of making specific changes to the system / 对系统进行特定修改的难度\n- The responsiveness of the system to user requests / 系统对用户请求的响应能力\n- Many others / 许多其他因素"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::640", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The definition, concepts, and types of **Module Structure**, **Allocation Structure**, and **C&C Structure**. For example, 7 categories of design decisions? Its Role in Project Risk Reduction (How to reduce risks)?", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 437, "text": "模块结构、分配结构和C&C结构的定义、概念和类型。\n\n**① Module structures / 模块结构**\n\n- Decomposition structure / 分解结构\n- Uses structure -> Layer pattern / 使用结构 -> 层模式\n- Class structure / 类结构\n- Data model / 数据模型\n\n**② Component-and-connector structures / C&C结构，组成-连接器结构**\n\n- Service structure / 服务结构\n- Concurrency structure / 并发结构\n\n**③ Allocation structures 分配结构**\n\n- Deployment structure / 部署结构\n- Implementation structure / 实施结构\n- Work assignment structure / 工作分配结构"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::641", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The definition, concepts, and types of **Module Structure**, **Allocation Structure**, and **C&C Structure**. For example, 7 categories of design decisions? Its Role in Project Risk Reduction (How to reduce risks)?/Module Structure/**Module Structures / 模块结构**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 533, "text": "Some structures partition systems into implementation units, which we call modules. / 一些结构将系统划分为实现单元，我们称之为模块。\nModules are assigned specific computational responsibilities, and are the basis of work assignments for programming teams. / 模块被分配了特定的计算责任，并成为编程团队工作分配的基础。\nIn large projects, these elements (modules) are subdivided for assignment to subteams. / 在大型项目中，这些元素（模块）会进一步细分，以便分配给子团队。\n\nModule structures embody decisions as to how the system is to be structured as a set of **code or data units.** / 模块结构体现了关于系统如何作为一组代码或数据单元进行组织的决策。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::642", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The definition, concepts, and types of **Module Structure**, **Allocation Structure**, and **C&C Structure**. For example, 7 categories of design decisions? Its Role in Project Risk Reduction (How to reduce risks)?/Module Structure/**Module Structures / 模块结构**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 400, "text": "system is to be structured as a set of **code or data units.** / 模块结构体现了关于系统如何作为一组代码或数据单元进行组织的决策。\n\nIn any module structure, the elements are modules of some kind (perhaps classes, or layers, or merely divisions of functionality all of which are units of implementation). / 在任何模块结构中，元素都是某种类型的模块（可能是类，层，或者仅仅是功能的划分，这些都属于实现单元）。\n\nModules are assigned areas of functional responsibility. / 模块被分配了特定的功能责任区域。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::643", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The definition, concepts, and types of **Module Structure**, **Allocation Structure**, and **C&C Structure**. For example, 7 categories of design decisions? Its Role in Project Risk Reduction (How to reduce risks)?/Module Structure/Some Useful Module Structures / 一些有用的模块结构/**Decomposition Structure / 分解结构**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 659, "text": "The units are modules that are related to each other by the is-a-submodule-of relation. / 这些单元是通过“是一个子模块”关系相互关联的模块。\nIt shows how modules are decomposed into smaller modules recursively until the modules are small enough to be easily understood. / 它展示了模块如何递归地被分解成更小的模块，直到模块足够小，易于理解。\nModules often have products (such as interface specifications, code, test plans, etc.) associated with them. / 模块通常会有一些产品（如接口规范、代码、测试计划等）与之关联。\nThe decomposition structure determines, to a large degree, the system's modifiability, by assuring that likely changes are localized. / 分解结构在很大程度上决定了系统的可修改性，通过确保可能的变更被局部化来实现这一点。\n\n"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::644", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The definition, concepts, and types of **Module Structure**, **Allocation Structure**, and **C&C Structure**. For example, 7 categories of design decisions? Its Role in Project Risk Reduction (How to reduce risks)?/Module Structure/Some Useful Module Structures / 一些有用的模块结构/Uses Structure / 使用结构", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 426, "text": "The units here are also modules, perhaps classes / 这些单元也是模块，可能是类\nThe units are related by the ***uses*** relation, a specialized form of dependency. / 这些单元通过“使用关系”相互关联，这是一种特定形式的依赖关系。\nA unit of software ***uses*** another if the correctness of the first requires the presence of a correctly functioning version of the second. / 如果第一个单元的正确性依赖于第二个单元的正确运行，那么第一个单元就使用了第二个单元。\n\n"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::645", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The definition, concepts, and types of **Module Structure**, **Allocation Structure**, and **C&C Structure**. For example, 7 categories of design decisions? Its Role in Project Risk Reduction (How to reduce risks)?/Module Structure/Some Useful Module Structures / 一些有用的模块结构/Layer Stucture / 层结构", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 544, "text": "The modules in this structure are called *layers*. / 该结构中的模块称为层。\nA layer is an abstract “virtual machine” that provides a cohesive set of services through a managed interface. / 层是一个抽象的“虚拟机”，通过受控接口提供一组有凝聚力的服务。\nLayers are *allowed* to use other layers in a strictly managed fashion. / 层允许以严格管理的方式使用其他层。\nIn strictly layered systems, a layer is only allowed to use a single other layer. / 在严格的分层系统中，一个层只允许使用一个其他层。\nThis structure imbues a system with portability, the ability to change the underlying computing platform. / 这种结构赋予系统可移植性，即能够更换底层计算平台。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::646", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The definition, concepts, and types of **Module Structure**, **Allocation Structure**, and **C&C Structure**. For example, 7 categories of design decisions? Its Role in Project Risk Reduction (How to reduce risks)?/Module Structure/Some Useful Module Structures / 一些有用的模块结构/Class (or generalization) Structure / 类结构", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 412, "text": "The module units in this structure are called *classes*. / 该结构中的模块单元称为类。\nThe relation is *inherited* from or is an instance of. / 该关系为“继承自”或“是某个实例”。\n**Inheritance** is a mechanism for **code reuse** and to allow independent extensions of the original software. / 继承是一种代码重用机制，允许对原始软件进行独立扩展。\nThe class structure allows one to reason for reuse and the incremental addition of functionality. / 类结构使得可以推理关于重用和功能的增量添加。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::647", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The definition, concepts, and types of **Module Structure**, **Allocation Structure**, and **C&C Structure**. For example, 7 categories of design decisions? Its Role in Project Risk Reduction (How to reduce risks)?/Module Structure/Some Useful Module Structures / 一些有用的模块结构/**Data Model Structure / 数据模型结构**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 405, "text": "The data model describes the static information structure in terms of data entities and their relationships. / 数据模型通过数据实体及其关系描述静态信息结构。\nFor example, in a banking system, entities will typically include Account, Customer, and Loan. / 例如，在银行系统中，实体通常包括账户、客户和贷款。\nAccount has several attributes, such as account number, type (savings or checking), status, and current balance. / 账户有多个属性，如账户号码、类型（储蓄或支票）、状态和当前余额。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::648", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The definition, concepts, and types of **Module Structure**, **Allocation Structure**, and **C&C Structure**. For example, 7 categories of design decisions? Its Role in Project Risk Reduction (How to reduce risks)?/Allocation Structure / 分配结构", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 637, "text": "- Allocation structures describe **the mapping from software structures to the system's environments.** / 分配结构描述了从软件结构到系统环境的映射。\n\nFor example:\n\n- Modules are assigned to **teams** to develop, and assigned to places in **a file structure** for implementation, integration, and testing. / 例如：\n\n - 模块被分配给团队进行开发，并在文件结构中分配位置以实现、集成和测试。\n- Components are deployed onto hardware in order to execute. / 组件被部署到硬件上以便执行。\n- ***Allocation structures*** show the relationship between the software elements and the elements in one or more external environments in which the software is created and executed. / 分配结构显示了软件元素与一个或多个外部环境元素之间的关系，在这些环境中软件被创建和执行。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::649", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The definition, concepts, and types of **Module Structure**, **Allocation Structure**, and **C&C Structure**. For example, 7 categories of design decisions? Its Role in Project Risk Reduction (How to reduce risks)?/Allocation Structure / 分配结构", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 493, "text": "ments in which the software is created and executed. / 分配结构显示了软件元素与一个或多个外部环境元素之间的关系，在这些环境中软件被创建和执行。\n- ***Allocation views*** help us answer questions such as these: / 分配视图帮助我们回答以下问题：\n\n① What processor does each software element execute on? / 每个软件元素在哪个处理器上执行？\n\n② In what directories or files is each element stored during development, testing, and system building? / 在开发、测试和系统构建过程中，每个元素存储在哪些目录或文件中？\n\n③ What is the assignment of each software element to development teams? / 每个软件元素分配给开发团队的任务是什么？"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::650", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The definition, concepts, and types of **Module Structure**, **Allocation Structure**, and **C&C Structure**. For example, 7 categories of design decisions? Its Role in Project Risk Reduction (How to reduce risks)?/Allocation Structure / 分配结构/Some Useful Allocation Structures / 一些有用的分配结构/Deployment Structure / 部署结构", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 699, "text": "The deployment structure shows how software is assigned to hardware processing and communication elements. / 部署结构展示了软件如何分配给硬件处理和通信元素。\n\nThe elements are software elements (usually a process from a C&C view), hardware entities (processors), and communication pathways. / 这些元素包括软件元素（通常是 C&C 视图中的进程）、硬件实体（处理器）和通信通道。\n\nRelations are **allocated-to**, showing on which physical units the software elements reside, and migrates-to if the allocation is dynamic.\n\n关系通过**“分配到”**来表示，展示软件元素所在的物理单元；如果分配是动态的，则通过“迁移到”来表示。\n\nThis structure can be used to reason for performance, data integrity, security, and availability.\n\n该结构可用于推理性能、数据完整性、安全性和可用性。\n\nIt is of particular interest in distributed and parallel systems."}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::651", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The definition, concepts, and types of **Module Structure**, **Allocation Structure**, and **C&C Structure**. For example, 7 categories of design decisions? Its Role in Project Risk Reduction (How to reduce risks)?/Allocation Structure / 分配结构/Some Useful Allocation Structures / 一些有用的分配结构/Deployment Structure / 部署结构", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 178, "text": "lity.\n\n该结构可用于推理性能、数据完整性、安全性和可用性。\n\nIt is of particular interest in distributed and parallel systems.\n\n在分布式和并行系统中，这一结构尤为重要。\n\n"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::652", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The definition, concepts, and types of **Module Structure**, **Allocation Structure**, and **C&C Structure**. For example, 7 categories of design decisions? Its Role in Project Risk Reduction (How to reduce risks)?/Allocation Structure / 分配结构/Some Useful Allocation Structures / 一些有用的分配结构/Implementation structure / 实现结构", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 288, "text": "This structure shows how software elements (usually modules) are mapped to **the file structure(s)** in the system's development, integration, or configuration control environments.\n\n该结构展示了软件元素（通常是模块）如何映射到系统的开发、集成或配置控制环境中的**文件结构。**\n\n"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::653", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The definition, concepts, and types of **Module Structure**, **Allocation Structure**, and **C&C Structure**. For example, 7 categories of design decisions? Its Role in Project Risk Reduction (How to reduce risks)?/Allocation Structure / 分配结构/Some Useful Allocation Structures / 一些有用的分配结构/Work assignment structure / 工作分配结构", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 155, "text": "This structure assigns responsibility for implementing and integrating the modules to the **teams** who will carry it out. / 该结构将模块的实现和集成责任分配给将负责执行的**团队**。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::654", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The definition, concepts, and types of **Module Structure**, **Allocation Structure**, and **C&C Structure**. For example, 7 categories of design decisions? Its Role in Project Risk Reduction (How to reduce risks)?/Component-and-connector Structures", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 552, "text": "**组件与连接器结构**\n\nOther structures focus on the way the elements interact with each other **at runtime** to carry out the system's functions. / 其他结构关注于元素在运行时如何相互交互以实现系统的功能。\n\nWe call **runtime** structures component-and-connector (C&C) structures. / 我们称这种运行时结构为组件与连接器（C&C）结构。\n\nA component is always a runtime entity. / 组件始终是一个运行时实体。\n\nIn SOA, the system is to be built as a set of services. / 在面向服务架构（SOA）中，系统将构建为一组服务。\n\nThese services are made up of (compiled from) the programs in the various implementation units—modules. / 这些服务由各种实现单元（模块）中的程序组成（或由程序编译而成）。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::655", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The definition, concepts, and types of **Module Structure**, **Allocation Structure**, and **C&C Structure**. For example, 7 categories of design decisions? Its Role in Project Risk Reduction (How to reduce risks)?/Component-and-connector Structures", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 662, "text": "from) the programs in the various implementation units—modules. / 这些服务由各种实现单元（模块）中的程序组成（或由程序编译而成）。\n\nComponent-and-connector structures embody decisions as to how the system is to be structured as a set of elements that have runtime behavior (components) and interactions (connectors). / 组件与连接器结构体现了如何将系统结构化为一组具有运行时行为（组件）和交互（连接器）的元素的决策。\n\nElements are runtime components such as services, peers, clients, servers, or many other types of runtime element. / 元素是运行时组件，如服务、对等体、客户端、服务器或其他多种类型的运行时元素。\n\nConnectors are the communication ways among components, such as call-return, process synchronization operators, pipes, or others. / 连接器是组件之间的通信方式，如调用返回、进程同步操作符、管道或其他方式。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::656", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The definition, concepts, and types of **Module Structure**, **Allocation Structure**, and **C&C Structure**. For example, 7 categories of design decisions? Its Role in Project Risk Reduction (How to reduce risks)?/Component-and-connector Structures", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 546, "text": "eturn, process synchronization operators, pipes, or others. / 连接器是组件之间的通信方式，如调用返回、进程同步操作符、管道或其他方式。\n\n**Component-and-connector views help us answer questions such as these: / 组件与连接器视图帮助我们回答以下问题：**\n\n- What are the major executing components and how do they interact at runtime? / 主要的执行组件是什么，它们在运行时如何交互？\n- What are the major shared data stores? / 主要的共享数据存储有哪些？\n- Which parts of the system are replicated? / 系统的哪些部分是复制的？\n- **How does data progress through the system? / 数据是如何在系统中流动的？**\n- What parts of the system can run in parallel? / 系统的哪些部分可以并行运行？"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::657", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The definition, concepts, and types of **Module Structure**, **Allocation Structure**, and **C&C Structure**. For example, 7 categories of design decisions? Its Role in Project Risk Reduction (How to reduce risks)?/Component-and-connector Structures/Some Useful C&C Structures / 一些有用的组件与连接器结构/Service structure / 服务结构", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 316, "text": "The units are services that interoperate with each other by service coordination mechanisms such as SOAP. / 这些单元是通过服务协调机制（如SOAP）相互操作的服务。\n\nThe service structure helps to engineer a system composed of components that may have been developed anonymously and independently of each other. / 服务结构有助于构建由可能匿名开发且相互独立的组件组成的系统。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::658", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The definition, concepts, and types of **Module Structure**, **Allocation Structure**, and **C&C Structure**. For example, 7 categories of design decisions? Its Role in Project Risk Reduction (How to reduce risks)?/Component-and-connector Structures/Some Useful C&C Structures / 一些有用的组件与连接器结构/Concurrency structure / 并发结构", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 371, "text": "This structure helps determine opportunities for parallelism and the locations where resource contention may occur. / 该结构有助于确定并行性的机会以及可能发生资源争用的位置。\n\nThe units are components. / 单元是组件。\n\nThe connectors are their communication mechanisms. / 连接器是它们的通信机制。\n\nThe components are arranged into logical threads. / 组件被安排为逻辑线程。\n\n"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::659", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The definition, concepts, and types of **Module Structure**, **Allocation Structure**, and **C&C Structure**. For example, 7 categories of design decisions? Its Role in Project Risk Reduction (How to reduce risks)?/① **Seven categories** of design decisions?", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 483, "text": "七种设计决策的类别\n\n\n\nArchitecture design is a systematic approach to making design decisions. / 架构设计是一个系统化的方法，用于做出设计决策。\n\nWe categorize the design decisions as follows: / 我们将设计决策分类如下：\n\n1. Allocation of responsibilities / 责任分配\n2. Coordination model / 协调模型\n3. Data model monitor / 数据模型监控\n4. Management of resources / 资源管理\n5. Mapping among architectural elements / 架构元素之间的映射\n6. Binding time decisions / 绑定时间决策\n7. Choice of technology / 技术选择"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::660", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The definition, concepts, and types of **Module Structure**, **Allocation Structure**, and **C&C Structure**. For example, 7 categories of design decisions? Its Role in Project Risk Reduction (How to reduce risks)?/② Its **role in project risk reduction**? (how to reduce risks?)", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 639, "text": "它在项目风险降低中的作用是什么？（如何降低风险？）\n\nSoftware architecture plays a critical role in reducing risks by providing a clear structure that supports system design, development, and evolution. It influences decisions about scalability, maintainability, performance, and security. / 软件架构通过提供清晰的结构，支持系统设计、开发和演进，发挥着减少风险的关键作用。它影响着关于可扩展性、可维护性、性能和安全性的决策。\n\n1. **Decompose Complexity** / **分解复杂性**\n By breaking down the system into manageable modules or components, you reduce the complexity of individual parts, making the system easier to understand, develop, and maintain. / 通过将系统分解为可管理的模块或组件，减少了单个部分的复杂性，使得系统更易于理解、开发和维护。\n2. **Design for Change** / **设计以应对变化**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::661", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The definition, concepts, and types of **Module Structure**, **Allocation Structure**, and **C&C Structure**. For example, 7 categories of design decisions? Its Role in Project Risk Reduction (How to reduce risks)?/② Its **role in project risk reduction**? (how to reduce risks?)", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 690, "text": "d maintain. / 通过将系统分解为可管理的模块或组件，减少了单个部分的复杂性，使得系统更易于理解、开发和维护。\n2. **Design for Change** / **设计以应对变化**\n Designing components with well-defined interfaces and minimal dependencies between them ensures that future changes can be made without affecting other parts of the system. This reduces the risk of costly and time-consuming rework. / 设计具有明确定义接口且相互依赖最小的组件，确保未来的变更可以不影响系统的其他部分，从而降低了成本高昂和耗时的返工风险。\n3. **Fault Tolerance and Redundancy** / **容错与冗余**\n Implementing failover mechanisms and redundant systems in the allocation structure helps ensure that the system remains operational even in the face of hardware failures or unexpected conditions. / 在分配结构中实施故障转移机制和冗余系统，帮助确保系统在硬件故障或意外情况下仍能保持正常运行。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::662", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The definition, concepts, and types of **Module Structure**, **Allocation Structure**, and **C&C Structure**. For example, 7 categories of design decisions? Its Role in Project Risk Reduction (How to reduce risks)?/② Its **role in project risk reduction**? (how to reduce risks?)", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 495, "text": "ace of hardware failures or unexpected conditions. / 在分配结构中实施故障转移机制和冗余系统，帮助确保系统在硬件故障或意外情况下仍能保持正常运行。\n4. **Performance and Scalability** / **性能与可扩展性**\n Properly designing how components are distributed and how tasks are allocated across hardware resources ensures that the system can scale efficiently, thus avoiding performance bottlenecks that might cause project delays or cost overruns. / 通过合理设计组件的分布方式以及任务如何在硬件资源之间分配，确保系统能够高效地扩展，从而避免性能瓶颈，防止项目延迟或成本超支。\n5. **Security Considerations** / **安全考虑**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::663", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The definition, concepts, and types of **Module Structure**, **Allocation Structure**, and **C&C Structure**. For example, 7 categories of design decisions? Its Role in Project Risk Reduction (How to reduce risks)?/② Its **role in project risk reduction**? (how to reduce risks?)", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 695, "text": "计组件的分布方式以及任务如何在硬件资源之间分配，确保系统能够高效地扩展，从而避免性能瓶颈，防止项目延迟或成本超支。\n5. **Security Considerations** / **安全考虑**\n Architecture decisions that consider security upfront can prevent costly security breaches, reduce vulnerability, and ensure compliance with regulations, ultimately lowering the risk of legal or financial consequences. / 提前考虑安全的架构决策可以防止昂贵的安全漏洞，减少系统的脆弱性，并确保符合相关法规，从而降低法律或财务后果的风险。\n6. **Early Prototyping and Validation** / **早期原型与验证**\n Architecture allows teams to build prototypes or models of high-risk components early in the project, which can validate design assumptions and reduce the risk of costly design changes later in the process. / 架构使团队能够在项目初期构建高风险组件的原型或模型，从而验证设计假设，减少后期进行昂贵设计变更的风险。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::664", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The definition, concepts, and types of **Module Structure**, **Allocation Structure**, and **C&C Structure**. For example, 7 categories of design decisions? Its Role in Project Risk Reduction (How to reduce risks)?/② Its **role in project risk reduction**? (how to reduce risks?)", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 603, "text": "f costly design changes later in the process. / 架构使团队能够在项目初期构建高风险组件的原型或模型，从而验证设计假设，减少后期进行昂贵设计变更的风险。\n7. **Documentation and Communication** / **文档与沟通**\n Clear architectural decisions and documentation help align the development team, reducing misunderstandings and rework that could arise from unclear or incomplete design decisions. / 清晰的架构决策和文档有助于对齐开发团队，减少因设计决策不明确或不完整而可能产生的误解和返工。\n\nBy incorporating these strategies, the architecture ensures that the system is robust, flexible, and capable of handling change, thereby minimizing risks to the project. / 通过采用这些策略，架构确保系统具有强健性、灵活性，并能够应对变化，从而最大限度地减少项目的风险。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::665", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Relationships between **Pattern** and **Tactics / 架构模式和架构策略的关系**/Comparision / 对比", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 405, "text": "An architectural tactic is a design decision that affects a quality attribute response. The focus of a tactic is on a single quality attribute response. A tactic does not consider tradeoffs among quality attributes. / 架构策略是一个设计决策，影响质量属性的响应。策略的重点是单一质量属性响应。一个策略并不考虑质量属性之间的权衡。\n\nArchitectural patterns can be seen as \"packages\" of tactics, in which tradeoffs are considered. / 架构模式可以看作是“策略的组合”，其中会考虑质量属性之间的权衡。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::666", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Relationships between **Pattern** and **Tactics / 架构模式和架构策略的关系**/Achieving Quality Attributes Through Tactics / 通过策略实现质量属性", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 443, "text": "There are a collection of primitive design techniques that an architect can use to achieve a quality attribute response. We call these architectural design primitives tactics. / 有一组原始设计技术，架构师可以用来实现质量属性的响应。我们将这些称为架构设计原语策略。\n\nTactics, like design patterns, are techniques that architects have been using for years. / 策略，像设计模式一样，是架构师多年使用的技术。\n\nWe do not invent tactics, we simply capture what architects do in practice. / 我们不是发明策略，而是捕捉架构师在实践中所做的工作。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::667", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Relationships between **Pattern** and **Tactics / 架构模式和架构策略的关系**/Tatic example: Resource Scheduling / 策略样例：资源调度", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 269, "text": "Resource scheduling is a tactic for performance. / 资源调度是提高性能的一种策略。\n\nGiven: release time, workload of each task / 已知：每个任务的发布时刻、工作负载\n\nTo determine: when each task is executed / 目标：确定每个任务的执行时间\n\nObjectives: to minimize average completion time of the tasks / 目标：最小化任务的平均完成时间"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::668", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/① **Availability** and related tactics (e.g. **how to detect faults?**) / 可用性及相关策略（例如，如何检测故障？）。", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::669", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/① **Availability** and related tactics (e.g. **how to detect faults?**) / 可用性及相关策略（例如，如何检测故障？）。/What is Availability?", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 557, "text": "**什么是可用性？**\n\nAvailability refers to a property of software that it is there and ready to carry out its task when you need it to be. / 可用性是软件的一种属性，指的是软件在需要时可以随时运行并完成其任务。\n\nAvailability refers to the ability of a system to mask or repair faults such that the cumulative service outage period does not exceed a required value over a specified time interval. / 可用性是指系统能够屏蔽或修复故障，使得在指定时间间隔内累计的服务中断时间不超过要求的值。\n\nAvailability is about minimizing service outage time by mitigating faults. / 可用性是通过缓解故障来最小化服务中断时间。\n\n"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::670", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/① **Availability** and related tactics (e.g. **how to detect faults?**) / 可用性及相关策略（例如，如何检测故障？）。/**Availability General Scenario**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 687, "text": "可用性一般场景\n\n**Portion of Scenario: Possible Values**\n\n场景部分：可能的值\n\n- Source / 源\n\n - Internal/external: people, hardware, software, physical infrastructure, physical environment\n - 内部/外部：人员、硬件、软件、物理基础设施、物理环境\n- Stimulus / 激励\n\n - Fault: omission, crash, incorrect timing, incorrect response\n - 故障：遗漏、崩溃、时序错误、响应错误\n- Artifact / 工件\n\n - System's processors, communication channels, persistent storage, processes\n - 系统的处理器、通信通道、持久存储、进程\n- Environment / 环境\n\n - Normal operation, startup, shutdown, repair mode, degraded operation, overloaded operation\n - 正常运行、启动、关闭、修复模式、降级运行、过载运行\n- Response / 响应\n\n - Prevent the fault from becoming a failure\n - 防止故障变成失败\n\n - Detect the fault\n\n - 检测故障"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::671", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/① **Availability** and related tactics (e.g. **how to detect faults?**) / 可用性及相关策略（例如，如何检测故障？）。/**Availability General Scenario**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 693, "text": "- Prevent the fault from becoming a failure\n - 防止故障变成失败\n\n - Detect the fault\n\n - 检测故障\n\n - Log the fault\n\n - 记录故障\n - Notify appropriate entities (people or systems)\n\n - 通知相关实体（人员或系统）\n - Recover from the fault\n\n - 从故障中恢复\n - Disable source of events causing the fault\n\n - 禁用引发故障的事件源\n - Be temporarily unavailable while repair is being effected\n\n - 在修复过程中暂时不可用\n - Fix or mask the fault/failure or contain the damage it causes\n\n - 修复或屏蔽故障/失效，或遏制其造成的损害\n - Operate in a degraded mode while repair is being effected\n\n - 在修复过程中以降级模式运行\n- Response Measure / 响应度量\n\n - Time or time interval when the system must be available"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::672", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/① **Availability** and related tactics (e.g. **how to detect faults?**) / 可用性及相关策略（例如，如何检测故障？）。/**Availability General Scenario**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 599, "text": "修复过程中以降级模式运行\n- Response Measure / 响应度量\n\n - Time or time interval when the system must be available\n - 系统必须可用的时间或时间间隔\n\n - Availability percentage (e.g., 99.999%)\n\n - 可用性百分比（例如，99.999%）\n - Time to detect the fault\n\n - 检测故障的时间\n - Monitor time to repair the fault\n\n - 监控修复故障的时间\n - Time or time interval in which system can be in degraded mode\n\n - 系统可处于降级模式的时间或时间间隔\n - Proportion (e.g., 99%) or rate (e.g., up to 100 per second) of a certain class of faults that the system prevents, or handles without failing\n\n - 系统预防或处理特定类别故障的比例（例如，99%）或速率（例如，每秒最多100个），而不发生失效"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::673", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/① **Availability** and related tactics (e.g. **how to detect faults?**) / 可用性及相关策略（例如，如何检测故障？）。/Sample Concrete Availability Scenario", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 568, "text": "**具体可用性场景示例**\n\nThe heartbeat monitor detects that the server is nonresponsive during normal operations. The system informs the operator and continues to operate with no downtime. / 心跳监控器检测到服务器在正常运行期间无响应。系统通知操作员，并继续在没有停机的情况下运行。\n\n- **Stimulus**: non-responsiveness / **刺激**：无响应\n- **Response**: inform the operator / **响应**：通知操作员\n- **Response measure**: no downtime, or 100% availability percentage / **响应度量**：无停机时间，或100%的可用性百分比\n- **Environment**: normal operation / **环境**：正常运行\n- **Artifact**: heartbeat monitor / **工件**：心跳监控器\n- **Stimulus source**: server / **刺激源**：服务器"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::674", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/① **Availability** and related tactics (e.g. **how to detect faults?**) / 可用性及相关策略（例如，如何检测故障？）。/Goal of Availability Tactics", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 389, "text": "可用性策略的目标\n\nFault vs. Failure / 故障 vs. 失效\n\nA failure occurs when the system no longer delivers a service consistent with its specification – this failure is observable by the system's actors. / 失效发生在系统不再提供与其规格一致的服务时——这种失效是系统的参与者可以观察到的。\n\nA fault (or combination of faults) has the potential to cause a failure. / 故障（或多个故障的组合）具有导致失效的潜力。\n\n"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::675", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/① **Availability** and related tactics (e.g. **how to detect faults?**) / 可用性及相关策略（例如，如何检测故障？）。/Availability Tactics/Detect Faults / 检测故障", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 179, "text": "- Ping & Echo\n- Monitor / 监测\n- Heartbeat / 心跳\n- Timestamp / 时间戳\n- Sanity Checking / 完整性检查\n- Condition Monitoring / 状态监控\n- Voting / 投票\n- Exception Detection / 异常检测\n- Self-Test / 自检"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::676", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/① **Availability** and related tactics (e.g. **how to detect faults?**) / 可用性及相关策略（例如，如何检测故障？）。/Availability Tactics/Preparation, Reintroduction and Repair / 准备、重新引入和修复", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 228, "text": "- Active Redundancy / 主动冗余\n- Passive Redundancy / 被动冗余\n- Spare / 备用\n- Exception Handling / 异常处理\n- Rollback / 回滚\n- Software Upgrade / 软件升级\n- Retry / 重试\n- Ignore Faulty Behavior / 忽略故障行为\n- Degradation / 降级\n- Reconfiguration / 重新配置"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::677", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/① **Availability** and related tactics (e.g. **how to detect faults?**) / 可用性及相关策略（例如，如何检测故障？）。/Availability Tactics/Reintroduction / 重新引入", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 106, "text": "- Shadow / 影子\n- State Resynchronization / 状态重新同步\n- Escalating Restart / 升级重启\n- Non-Stop Forwarding / 不间断转发"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::678", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/① **Availability** and related tactics (e.g. **how to detect faults?**) / 可用性及相关策略（例如，如何检测故障？）。/Availability Tactics/Prevent Faults / 防止故障", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 141, "text": "- Removal from Service / 从服务中移除\n- Transactions / 事务\n- Predictive Model / 预测模型\n- Exception Prevention / 异常预防\n- Increase Competence Set / 增加能力集"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::679", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/① **Availability** and related tactics (e.g. **how to detect faults?**) / 可用性及相关策略（例如，如何检测故障？）。/Detect Faults / 监测故障", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 541, "text": "- **Ping / Echo**:\nPing is used to determine the reachability of a network and measure the round-trip delay through the associated network path.\n网络延迟检测：Ping用于确定网络的可达性，并测量通过相关网络路径的往返延迟。\n- **Monitor**:\nA component used to monitor the state of health of other parts of the system.\n监控：监控组件用于监测系统其他部分的健康状态。\n- **Heartbeat**:\nA periodic message exchange between a system monitor and a process being monitored. 心跳：系统监控器与被监控进程之间的周期性消息交换。\n\n - The process periodically resets the watchdog timer in its monitor.\n 进程定期重置监控器中的看门狗定时器。（实现了周期性的信息交换，但是占用网络）"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::680", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/① **Availability** and related tactics (e.g. **how to detect faults?**) / 可用性及相关策略（例如，如何检测故障？）。/Detect Faults / 监测故障", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 683, "text": "ess periodically resets the watchdog timer in its monitor.\n 进程定期重置监控器中的看门狗定时器。（实现了周期性的信息交换，但是占用网络）\n - **Overhead**: Piggybacking the heartbeat messages onto other control messages reduces the overhead. However, heartbeat can consume significant network bandwidth, causing overhead.\n 开销：将心跳消息附加到其他控制消息上可以减少开销，但心跳消息可能占用大量网络带宽，导致开销增加。\n\n**Differences between Ping and Heartbeat / Ping 和 心跳的区别**\n\n- **Ping** is typically used to test the basic reachability of a network or system, while **Heartbeat** is used to monitor the health of a process or system over time.\n\n - **Ping**: 简单检测网络或系统的基本可达性。\n - **Heartbeat**: 用于长时间监控进程或系统的健康状态。\n- Who initiates the health check ? / 哪个机制初始化健康检查？"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::681", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/① **Availability** and related tactics (e.g. **how to detect faults?**) / 可用性及相关策略（例如，如何检测故障？）。/Detect Faults / 监测故障", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 677, "text": "络或系统的基本可达性。\n - **Heartbeat**: 用于长时间监控进程或系统的健康状态。\n- Who initiates the health check ? / 哪个机制初始化健康检查？\nIn a **Ping** test, the initiator is typically the client or system performing the check. In a **Heartbeat**, the health check is initiated periodically by the system or process being monitored.\n\n - **Ping**: 通常由客户端或执行检测的系统发起。\n - **Heartbeat**: 由被监控的系统或进程定期发起健康检查。\n- **Timestamp**: A timestamp is used to detect incorrect sequences of events, particularly in distributed message-passing systems.\n 时间戳：时间戳用于检测事件的错误顺序，尤其是在分布式消息传递系统中。\n- **Condition Monitoring**: The process of checking the conditions of a device or process, or validating assumptions made during system design."}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::682", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/① **Availability** and related tactics (e.g. **how to detect faults?**) / 可用性及相关策略（例如，如何检测故障？）。/Detect Faults / 监测故障", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 326, "text": "hecking the conditions of a device or process, or validating assumptions made during system design.\n 状态监控：检查设备或进程的条件，或验证在系统设计过程中做出的假设。\n- **Checksum**: A checksum is used in data storage and transmission to ensure the integrity of the data.\n 校验码：校验码用于数据存储和传输中，以确保数据的完整性。\n\n"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::683", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/① **Availability** and related tactics (e.g. **how to detect faults?**) / 可用性及相关策略（例如，如何检测故障？）。/Recover from Faults (Preparation & Repair) / 从故障中恢复过来（准备 & 恢复）/**Active Redundancy (Hot Spare) / 主动冗余（热备份）**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 229, "text": "- In an active redundancy setup, all nodes in a protection group process identical inputs in parallel, allowing redundant spares to maintain synchronous states with the active nodes.\n在主动冗余配置中，保护组中的所有节点并行处理相同的输入，允许冗余备件与活动节点保持同步状态。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::684", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/① **Availability** and related tactics (e.g. **how to detect faults?**) / 可用性及相关策略（例如，如何检测故障？）。/Recover from Faults (Preparation & Repair) / 从故障中恢复过来（准备 & 恢复）/Spare (**Cold Spare) / 备件（冷备份）**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 269, "text": "- Redundant spares in a cold spare setup remain out of service until a failover occurs. When a failover happens, a power-on-reset procedure is initiated on the redundant spare before it is placed into service.\n在冷备份配置中，冗余备件在故障转移发生之前处于闲置状态，发生故障转移时会对冗余备件进行上电重置操作，然后将其投入使用。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::685", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/① **Availability** and related tactics (e.g. **how to detect faults?**) / 可用性及相关策略（例如，如何检测故障？）。/Recover from Faults (Preparation & Repair) / 从故障中恢复过来（准备 & 恢复）/**Passive Redundancy (Warm Spare) / 被动冗余（暖备份）**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 231, "text": "- In passive redundancy, only the active members of the protection group process input traffic. One of their duties is to provide the redundant spare(s) with periodic state updates.\n在被动冗余配置中，只有保护组中的活动成员处理输入流量，它们的职责之一是定期向冗余备件提供状态更新。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::686", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/① **Availability** and related tactics (e.g. **how to detect faults?**) / 可用性及相关策略（例如，如何检测故障？）。/Recover from Faults (Preparation & Repair) / 从故障中恢复过来（准备 & 恢复）/**Rollback / 回滚**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 523, "text": "- Rollback refers to reverting to a previous known good state, referred to as the “rollback line.” This tactic is often combined with redundancy tactics to ensure recovery.\n回滚是指恢复到先前已知的良好状态，通常与冗余策略结合使用，以确保系统恢复。\n\n - After a rollback, a standby version of the failed component becomes active.\n 在回滚后，故障组件的备用版本将成为活动组件。\n- Checkpoint: A checkpoint is a saved version of a previous state, and it can be stored in a fixed location. It needs to be updated regularly to ensure recovery.\n\n - 检查点：检查点是先前状态的备份，通常存储在固定位置，并需要定期更新以确保恢复。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::687", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/① **Availability** and related tactics (e.g. **how to detect faults?**) / 可用性及相关策略（例如，如何检测故障？）。/Recover from Faults (Preparation & Repair) / 从故障中恢复过来（准备 & 恢复）/**Retry / 重试**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 181, "text": "- When a failure is transient, retrying the operation may lead to success. For example, network re-transmission may resolve a temporary issue.\n当故障是暂时性的时，重试操作可能导致成功。例如，网络重传可能解决暂时性问题。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::688", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/① **Availability** and related tactics (e.g. **how to detect faults?**) / 可用性及相关策略（例如，如何检测故障？）。/Recover from Faults (Preparation & Repair) / 从故障中恢复过来（准备 & 恢复）/**Ignore Faulty Behavior (Ostrich Algorithm) / 忽略错误行为（鸵鸟算法）**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 246, "text": "- This approach involves ignoring messages sent from a source when it is determined that those messages are spurious or erroneous.For example, ignore the messages from a denial of service attacker.\n这种方法是在确认某些消息是虚假或错误时，忽略这些消息的来源。例如，忽略来自拒绝服务攻击者的消息。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::689", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/① **Availability** and related tactics (e.g. **how to detect faults?**) / 可用性及相关策略（例如，如何检测故障？）。/Recover from Faults (Preparation & Repair) / 从故障中恢复过来（准备 & 恢复）/**Degradation / 降级**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 183, "text": "- Degradation involves maintaining the most critical system functions in the presence of component failures while dropping less critical functions.\n降级在组件故障的情况下，保持最关键的系统功能，同时丢弃较不重要的功能。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::690", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/① **Availability** and related tactics (e.g. **how to detect faults?**) / 可用性及相关策略（例如，如何检测故障？）。/Recover from Faults (Preparation & Repair) / 从故障中恢复过来（准备 & 恢复）/**Reconfiguration / 重新配置**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 188, "text": "- Reconfiguration refers to reassigning responsibilities to the remaining functioning resources, while maintaining as much functionality as possible.\n重新配置指的是将责任重新分配给剩余的正常工作资源，同时尽可能保持更多的功能。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::691", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/① **Availability** and related tactics (e.g. **how to detect faults?**) / 可用性及相关策略（例如，如何检测故障？）。/**Prevent Faults / 防止故障**/**Removal From Service / 从服务中移除**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 152, "text": "- This involves temporarily placing a system component into an out-of-service state to mitigate potential system failures.\n 通过将系统组件暂时置于非服务状态，以减轻潜在的系统故障。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::692", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/① **Availability** and related tactics (e.g. **how to detect faults?**) / 可用性及相关策略（例如，如何检测故障？）。/**Prevent Faults / 防止故障**/**Transactions / 事务**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 534, "text": "- Transactions bundle state updates to ensure that asynchronous messages exchanged between distributed components are:\n\n - **Atomic**: Changes happen entirely or not at all.\n - **Consistent**: The system remains in a valid state before and after the transaction.\n - **Isolated**: Transactions do not interfere with one another.\n - **Durable**: Once completed, the changes are permanent.\n 事务将状态更新捆绑在一起，确保分布式组件之间交换的异步消息具备以下特点：\n - **原子性**：操作要么完全执行，要么完全不执行。\n - **一致性**：事务前后系统处于有效状态。\n - **隔离性**：事务之间不相互干扰。\n - **持久性**：一旦完成，变更是永久性的。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::693", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/① **Availability** and related tactics (e.g. **how to detect faults?**) / 可用性及相关策略（例如，如何检测故障？）。/**Prevent Faults / 防止故障**/**Predictive Model / 预测性模型**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 224, "text": "- Predictive models take corrective actions when conditions are detected that indicate likely future faults. This proactive approach helps prevent faults before they occur.\n预测性模型在检测到可能导致未来故障的条件时，采取纠正措施。这种主动的策略有助于在故障发生之前进行预防。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::694", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/① **Availability** and related tactics (e.g. **how to detect faults?**) / 可用性及相关策略（例如，如何检测故障？）。/**Prevent Faults / 防止故障**/**Increase Competence Set / 增强能力集**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 279, "text": "- Designing a component to handle more fault cases as part of its normal operation. This increases the system's robustness and helps prevent faults by ensuring that components can handle a wider range of scenarios.\n将组件设计为能够处理更多故障情况，并作为正常操作的一部分。这样可以增强系统的健壮性，通过确保组件能够处理更广泛的情况来防止故障。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::695", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/① **Availability** and related tactics (e.g. **how to detect faults?**) / 可用性及相关策略（例如，如何检测故障？）。/Summary of Availability tactics / 可用性策略总结", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 41, "text": "可用性策略通常分为三类：**故障检测**、**故障恢复** 和 **故障预防**。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::696", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/① **Availability** and related tactics (e.g. **how to detect faults?**) / 可用性及相关策略（例如，如何检测故障？）。/Summary of Availability tactics / 可用性策略总结/**Fault Detection Tactics / 故障检测策略**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 253, "text": "- **Detection tactics** focus on detecting signs of life or health indicators from various system components. These signs can help identify potential failures early and prevent service disruption.\n 故障检测策略侧重于从系统的各个组件中检测生命迹象或健康指标。这些迹象可以帮助及早识别潜在故障，并防止服务中断。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::697", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/① **Availability** and related tactics (e.g. **how to detect faults?**) / 可用性及相关策略（例如，如何检测故障？）。/Summary of Availability tactics / 可用性策略总结/**Fault Recovery Tactics / 故障恢复策略**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 274, "text": "- **Recovery tactics** include actions such as retrying an operation or maintaining redundant data or computations. These actions ensure that if a failure occurs, the system can quickly recover and continue functioning.\n 故障恢复策略包括重试操作或维持冗余数据或计算等措施。这些策略确保在发生故障时，系统能够迅速恢复并继续运行。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::698", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/① **Availability** and related tactics (e.g. **how to detect faults?**) / 可用性及相关策略（例如，如何检测故障？）。/Summary of Availability tactics / 可用性策略总结/**Fault Prevention Tactics / 故障预防策略**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 283, "text": "- **Prevention tactics** focus on removing elements from service or limiting the scope of faults. By taking components offline or restricting their potential impact, the system can reduce the chances of a failure occurring.\n 故障预防策略侧重于将元素从服务中移除或限制故障的范围。通过将组件下线或限制其潜在影响，系统可以减少故障发生的可能性。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::699", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/**Performance Modeling / 性能建模**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 618, "text": "**Two basic contributors to the response time / 响应时间的两个基本组成部分**:\n\n1. **Processing Time / 处理时间**\n\n - Processing time is the time that the system is working to respond.\n 处理时间是系统为响应请求而执行操作的时间。\n2. **Blocked Time / 阻塞时间**\n\n - Blocked time is the time that the system is unable to respond.\n 阻塞时间是系统无法响应的时间。\n\n**Blocked Time is caused by / 阻塞时间的原因**：\n\n- **Contention for Resources / 资源竞争**: Multiple tasks competing for the same resources can lead to blocking.\n 资源竞争：多个任务争夺相同资源时，可能导致阻塞。\n- **Availability of Resources / 资源可用性**: The system resources are unavailable, causing tasks to wait.\n 资源可用性：系统中的资源不可用时，可能导致任务等待。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::700", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/**Performance Modeling / 性能建模**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 548, "text": "/ 资源可用性**: The system resources are unavailable, causing tasks to wait.\n 资源可用性：系统中的资源不可用时，可能导致任务等待。\n- **Dependency on Other Computations / 依赖其他计算**: Tasks depend on other tasks or computations, causing delays.\n 依赖其他计算：任务之间的依赖关系可能导致一个任务需要等待其他任务的完成。\n\n**Resources / 资源**:\n\n- **Hardware resources / 硬件资源**: e.g., CPU, data stores, network bandwidth, and memory.\n 硬件资源：例如 CPU、数据存储、网络带宽和内存。\n- **Software resources / 软件资源**: e.g., buffers, or critical sections.\n 软件资源：例如缓冲区或关键区段（critical sections）。\n\n"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::701", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/Performance Tactics / 性能策略（开源节流）/Control Resource Demand / 控制资源需求", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 586, "text": "**Manage Sampling Rate / 管理采样率**\n\n- Adjust the frequency at which data is sampled to ensure efficient monitoring without overwhelming the system.\n调整数据采样的频率，以确保有效监控而不会使系统过载。\n\n**Limit Event Response / 限制事件响应**\n\n- Limit the number of events the system responds to, ensuring that only the most important or time-sensitive events are processed.\n限制系统响应的事件数量，确保仅处理最重要或时间敏感的事件。\n\n**Prioritize Events / 优先级事件**\n\n- Assign priorities to events to ensure that critical events are handled first, reducing the impact of less important events.\n为事件分配优先级，确保先处理关键事件，减少不重要事件的影响。\n\n**Reduce Overhead / 减少开销**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::702", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/Performance Tactics / 性能策略（开源节流）/Control Resource Demand / 控制资源需求", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 682, "text": "ng the impact of less important events.\n为事件分配优先级，确保先处理关键事件，减少不重要事件的影响。\n\n**Reduce Overhead / 减少开销**\n\n- Minimize the resources required to handle events or tasks, thus reducing the system's overhead and improving overall performance.\n最小化处理事件或任务所需的资源，从而减少系统开销并提高整体性能。\n\n**Bound Execution Times / 限制执行时间**\n\n- Set limits on the time allowed for tasks or operations to execute, ensuring that no process takes too long and causes delays.\n对任务或操作的执行时间设定限制，确保没有过程因执行时间过长而导致延迟。\n\n**Increase Resource Efficiency / 提高资源效率**\n\n- Optimize the use of available resources (e.g., CPU, memory, network) to improve system performance while maintaining stability.\n优化可用资源（例如 CPU、内存、网络）的使用，以提高系统性能，同时保持系统稳定性。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::703", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/Performance Tactics / 性能策略（开源节流）/Manage Resources / 管理资源", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 675, "text": "**Increase Resources / 增加资源**\n\n**Introduce Concurrency / 引入并发**\n\n- By allowing multiple tasks to be executed simultaneously, concurrency can increase the system's throughput and responsiveness.\n通过允许多个任务同时执行，并发可以提高系统的吞吐量和响应能力。\n\n**Maintain Multiple Copies of Data / 保持多个数据副本**\n\n- Storing multiple copies of data enhances availability, durability, and reliability, as well as providing faster access in some cases (e.g., distributed databases).\n保持多个数据副本增强了可用性、持久性和可靠性，并在某些情况下（例如分布式数据库）提供更快的数据访问。\n\n**Bound Queue Sizes / 限制队列大小**\n\n- Limiting the size of queues prevents system overload, ensuring that the system can manage resource requests efficiently without unnecessary delays."}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::704", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/Performance Tactics / 性能策略（开源节流）/Manage Resources / 管理资源", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 337, "text": "load, ensuring that the system can manage resource requests efficiently without unnecessary delays.\n限制队列的大小可以防止系统过载，确保系统能够有效管理资源请求，避免不必要的延迟。\n\n**Schedule Resources / 调度资源**\n\n- Efficient resource scheduling ensures that system resources are allocated optimally, balancing workload and reducing idle time.\n高效的资源调度确保系统资源得到最佳分配，平衡工作负载并减少空闲时间。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::705", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/Control Resource Demand / 控制资源需求/**Manage Sampling Rate / 管理采样率**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 189, "text": "- **Objective**: To reduce the sampling frequency at which a stream of data is captured, helping to minimize unnecessary data processing and system load.\n**目标**：降低数据流采样的频率，以减少不必要的数据处理和系统负载。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::706", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/Control Resource Demand / 控制资源需求/**Prioritize Events / 优先级事件**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 214, "text": "- **Objective**: To impose a priority scheme that ranks events according to their importance. Low-priority events are ignored when system resources are insufficient.\n**目标**：制定优先级方案，根据事件的重要性对其进行排序。当系统资源不足时，忽略低优先级事件。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::707", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/Control Resource Demand / 控制资源需求/**Reduce Overhead / 减少开销**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 441, "text": "- **Objective**: The use of intermediaries (such as proxies or message brokers) increases the resources consumed in processing an event stream. Removing these intermediaries can improve latency.\n**目标**：中介的使用（如代理或消息中间件）会增加处理事件流所消耗的资源，去除中介可以改善延迟。\n\n - **Trade-off**: There is a trade-off between **modifiability** (flexibility of the system) and **performance** (efficiency of event processing).\n **权衡**：在**可修改性**（系统灵活性）和**性能**（事件处理效率）之间存在权衡。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::708", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/Control Resource Demand / 控制资源需求/**Bound Execution Times / 限制执行时间**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 488, "text": "- **Objective**: Place a limit on how much execution time is used to respond to an event, preventing long-running tasks from blocking the system.\n**目标**：限制响应事件所用的执行时间，防止长期运行的任务阻塞系统。\n\n - In algorithm design, limiting the number of iterations is one method for bounding execution time.\n 在算法设计中，限制迭代次数是限制执行时间的一种方法。\n - **Trade-off**: There is a trade-off between **performance** (system efficiency) and **accuracy** (completeness of results).\n **权衡**：在**性能**（系统效率）和**准确性**（结果的完整性）之间存在权衡。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::709", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/Control Resource Demand / 控制资源需求/**Increase Resource Efficiency / 提高资源效率**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 400, "text": "- **Objective**: Improving the algorithms used in critical areas will decrease latency and increase the overall resource efficiency of the system.\n**目标**：改进关键领域中使用的算法将减少延迟，并提高系统的整体资源效率。\n\n - **To reduce the complexity of the algorithm / 降低算法复杂度**: Simplifying algorithms can help to reduce the time and resources required for processing, improving system performance.\n 简化算法有助于减少处理所需的时间和资源，从而提高系统性能。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::710", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/Manage Resources / 管理资源/**Increase Resources / 增加资源**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 665, "text": "- **Objective**: To reduce latency by upgrading system resources.\n**目标**：通过升级系统资源来减少延迟。\n\n - **Faster Processors / 更快的处理器**: Using faster processors can speed up the overall processing time, reducing the time it takes to respond to events.\n 使用更快的处理器可以加快整体处理速度，减少响应事件所需的时间。\n - **Additional Processors / 增加处理器**: Adding more processors can allow the system to handle more tasks in parallel, improving performance and reducing bottlenecks.\n 增加更多的处理器可以让系统并行处理更多任务，从而提高性能并减少瓶颈。\n - **Additional Memory / 增加内存**: More memory allows the system to store more data for faster access, reducing delays caused by memory constraints.\n 更多的内存允许系统存储更多数据，快速访问，从而减少由内存限制引起的延迟。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::711", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/Manage Resources / 管理资源/**Increase Resources / 增加资源**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 301, "text": "aster access, reducing delays caused by memory constraints.\n 更多的内存允许系统存储更多数据，快速访问，从而减少由内存限制引起的延迟。\n - **Faster Networks / 更快的网络**: Upgrading the network infrastructure can reduce the time required for data transfer, helping to lower latency in data exchange.\n 升级网络基础设施可以减少数据传输所需的时间，从而帮助降低数据交换中的延迟。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::712", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/Manage Resources / 管理资源/**Increase Concurrency / 增加并发性**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 680, "text": "- **Objective**: To reduce blocked time by processing tasks in parallel, improving overall system performance.\n**目标**：通过并行处理任务来减少阻塞时间，从而提高系统整体性能。\n\n - **Parallel Processing of Requests / 请求的并行处理**: If requests can be processed in parallel, the system can handle multiple tasks simultaneously, reducing waiting time and improving throughput.\n 如果请求可以并行处理，系统就能同时处理多个任务，减少等待时间并提高吞吐量。\n - **Concurrency through Threads / 通过线程引入并发**: Concurrency can be introduced by processing different streams of events on different threads, allowing independent processing of multiple event streams.\n 通过在不同线程上处理不同的事件流，可以引入并发，允许多个事件流的独立处理。\n\n"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::713", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/Maintain Multiple Copies of Data / 保持数据的多份副本/**Data Caching / 数据缓存**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 675, "text": "- **Definition**: Data caching involves storing copies of data on storage devices with varying access speeds (e.g., memory vs. disk, or local vs. remote access via networks).\n**定义**：数据缓存是将数据的副本存储在具有不同访问速度的存储设备上（例如，内存访问与磁盘访问，或通过网络的本地访问与远程访问）。\n\n - **Memory Access vs. Disk Access / 内存访问与磁盘访问**: Memory access is much faster than disk access, so frequently used data can be cached in memory to reduce access time.\n 内存访问比磁盘访问快得多，因此频繁使用的数据可以缓存到内存中，以减少访问时间。\n - **Local Access vs. Remote Access / 本地访问与远程访问**: Accessing data locally (from the same machine) is faster than accessing data remotely over a network, so caching frequently used data locally can reduce network delays."}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::714", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/Maintain Multiple Copies of Data / 保持数据的多份副本/**Data Caching / 数据缓存**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 154, "text": "ng data remotely over a network, so caching frequently used data locally can reduce network delays.\n 本地访问（来自同一台机器）比远程通过网络访问数据更快，因此将频繁使用的数据缓存到本地可以减少网络延迟。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::715", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/Maintain Multiple Copies of Data / 保持数据的多份副本/**Data Replication / 数据复制**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 499, "text": "- **Definition**: Data replication involves maintaining separate copies of data in different locations to reduce contention from multiple simultaneous accesses. This improves both availability and performance.\n**定义**：数据复制是保持数据在不同位置的副本，以减少多次并发访问时的竞争，从而提高可用性和性能。\n\n - **Reducing Contention / 减少竞争**: By replicating data, different users or processes can access separate copies of the data simultaneously, improving system performance and reducing delays.\n 通过复制数据，不同的用户或进程可以同时访问数据的独立副本，从而提高系统性能并减少延迟。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::716", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/Maintain Multiple Copies of Data / 保持数据的多份副本/**How to Choose the Data to be Cached or Replicated / 如何选择需要缓存或复制的数据**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 455, "text": "- **Caching Decisions**: Typically, frequently accessed or critical data is chosen to be cached. This helps to improve performance by reducing access time for commonly used data.\n**缓存决策**：通常，选择频繁访问或关键的数据进行缓存。这样可以通过减少对常用数据的访问时间来提高性能。\n- **Replication Decisions**: Data that is frequently requested by multiple users or processes, or data that needs to be highly available, is a good candidate for replication.\n**复制决策**：经常被多个用户或进程请求的数据，或需要高可用性的数据，通常是复制的理想候选。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::717", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/Maintain Multiple Copies of Data / 保持数据的多份副本/**How to Guarantee the Consistency of Multiple Copies / 如何保证多个副本的一致性**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 560, "text": "- **Consistency Models**: To ensure consistency across multiple copies of data, consistency models like **strong consistency**, **eventual consistency**, or **quorum-based consistency** are used, depending on the requirements of the system.\n**一致性模型**：为了确保多个数据副本之间的一致性，通常使用**强一致性**、**最终一致性**或**基于法定多数的一致性**等一致性模型，这取决于系统的要求。\n\n - **Strong Consistency / 强一致性**: Ensures that all copies of the data are immediately updated and synchronized after a change, providing the highest consistency but may impact performance.\n 强一致性：确保数据更改后，所有副本都立即更新和同步，提供最高的一致性，但可能影响性能。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::718", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/Maintain Multiple Copies of Data / 保持数据的多份副本/**How to Guarantee the Consistency of Multiple Copies / 如何保证多个副本的一致性**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 636, "text": "the highest consistency but may impact performance.\n 强一致性：确保数据更改后，所有副本都立即更新和同步，提供最高的一致性，但可能影响性能。\n - **Eventual Consistency / 最终一致性**: Allows copies of data to be temporarily inconsistent, but guarantees that all copies will eventually converge to the same value. This can improve performance but may result in temporary inconsistencies.\n 最终一致性：允许数据副本暂时不一致，但保证所有副本最终会收敛到相同的值。这可以提高性能，但可能导致临时的不一致。\n - **Quorum-based Consistency / 基于法定多数的一致性**: Involves ensuring that a majority of copies are consistent, allowing for more flexibility in achieving consistency across distributed systems.\n 基于法定多数的一致性：确保多数副本一致，从而在分布式系统中实现一致性时提供更多灵活性。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::719", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/**Scheduling / 调度**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 681, "text": "当资源发生竞争时，必须进行资源调度以确保公平且高效的资源分配。\n\n1. **Processors / 处理器**\n\n - **Description**: Processors need to be scheduled to ensure tasks are executed in a timely manner. Scheduling algorithms manage which tasks are assigned to which processor and when, optimizing CPU usage and preventing bottlenecks.\n **描述**：处理器需要调度，以确保任务及时执行。调度算法管理任务分配给哪个处理器以及何时分配，从而优化 CPU 使用并防止瓶颈。\n2. **Buffers / 缓冲区**\n\n - **Description**: Buffers, often used to temporarily store data between processes, need to be scheduled to ensure efficient data flow. Buffer scheduling prevents overflows and underflows, maintaining smooth data transfer.\n **描述**：缓冲区通常用于在进程之间临时存储数据，需要进行调度以确保高效的数据流动。缓冲区调度可以防止溢出和下溢，保持平稳的数据传输。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::720", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/**Scheduling / 调度**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 687, "text": "ining smooth data transfer.\n **描述**：缓冲区通常用于在进程之间临时存储数据，需要进行调度以确保高效的数据流动。缓冲区调度可以防止溢出和下溢，保持平稳的数据传输。\n3. **Networks / 网络Bag of tasks** (任务包) 是一种任务调度模型，通常用于并行处理系统中，表示多个独立且可以并行执行的任务集合。这些任务之间没有直接依赖关系，可以独立执行。\n\n - **Description**: Network resources must be scheduled to avoid congestion and ensure that data is transmitted efficiently. Network scheduling manages the prioritization of data packets, optimizing network bandwidth usage and reducing latency.\n **描述**：网络资源必须调度，以避免拥塞并确保数据高效传输。网络调度管理数据包的优先级，优化网络带宽使用并减少延迟。\n\n \n\n ##### Task Model / 任务模型\n\n ###### **Bag of Tasks / 任务包**\n\n ###### **Directed Acyclic Graph (DAG) / 有向无环图**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::721", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/**Scheduling / 调度**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 662, "text": "Model / 任务模型\n\n ###### **Bag of Tasks / 任务包**\n\n ###### **Directed Acyclic Graph (DAG) / 有向无环图**\n\n - **Definition**: A Directed Acyclic Graph (DAG) is a graph structure where tasks are represented as nodes and dependencies between tasks as directed edges. It is used to model tasks that have dependencies, where some tasks must be completed before others can begin.\n **定义**：有向无环图（DAG）是一种图结构，其中任务作为节点表示，任务之间的依赖关系作为有向边表示。它用于建模具有依赖关系的任务，其中某些任务必须在其他任务开始之前完成。\n\n ###### **Periodic / Cyclic Tasks / 周期性/循环任务**\n\n - **Definition**: Periodic or cyclic tasks are tasks that are repeated at regular intervals, such as tasks that execute every fixed amount of time."}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::722", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/**Scheduling / 调度**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 631, "text": "asks that are repeated at regular intervals, such as tasks that execute every fixed amount of time.\n **定义**：周期性或循环任务是按固定时间间隔重复执行的任务，例如每隔固定时间执行一次的任务。\n\n ###### **Task Properties / 任务属性**\n\n 1. **Execution Cost / 执行成本**\n\n - The time or resources required to execute the task. It includes CPU time, memory usage, or other system resources.\n 执行任务所需的时间或资源，包括 CPU 时间、内存使用量或其他系统资源。\n 2. **Transmission Cost / 传输成本**\n\n - The cost associated with transferring data or communication between tasks, including network bandwidth or communication latency.\n 与任务之间的数据传输或通信相关的成本，包括网络带宽或通信延迟。\n 3. **Arrival Time / 到达时间**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::723", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/**Scheduling / 调度**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 693, "text": "dth or communication latency.\n 与任务之间的数据传输或通信相关的成本，包括网络带宽或通信延迟。\n 3. **Arrival Time / 到达时间**\n\n - The time at which a task arrives or is ready to start execution. For real-time systems, this may be critical for scheduling.\n 任务到达或准备开始执行的时间。对于实时系统而言，这在调度中可能非常关键。\n 4. **Deadline / 截止时间**\n\n - The latest time by which a task must be completed. It is critical for real-time systems where tasks must meet strict timing constraints.\n 任务必须完成的最晚时间。在实时系统中，任务必须满足严格的时间约束。\n 5. **Preemptive or Non-preemptive / 可抢占或不可抢占**\n\n - **Preemptive**: In preemptive scheduling, tasks can be interrupted and resumed later, allowing higher-priority tasks to take over the processor."}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::724", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/**Scheduling / 调度**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 339, "text": "ks can be interrupted and resumed later, allowing higher-priority tasks to take over the processor.\n **可抢占**：在可抢占调度中，任务可以被中断，并稍后恢复，使得优先级更高的任务能够接管处理器。\n - **Non-preemptive**: In non-preemptive scheduling, once a task starts executing, it runs to completion without being interrupted.\n **不可抢占**：在不可抢占调度中，一旦任务开始执行，它会运行到完成，不会被中断。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::725", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/**Resource Model / 资源模型**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 48, "text": "资源模型描述了系统中可用的硬件和通信基础设施。它包括一组机器/处理器，这些机器通过网络相互连接。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::726", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/**Resource Model / 资源模型**/**Machine/Processor Model / 机器/处理器模型**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 521, "text": "- **Processing Capability/Speed / 处理能力/速度**\n\n - Describes the computation power and processing speed of a machine or processor. This includes factors like clock speed, number of cores, and processing throughput.\n 描述机器或处理器的计算能力和处理速度，包括时钟速度、核心数量和处理吞吐量等因素。\n- **Energy Consumption / 能源消耗**\n\n - Refers to the amount of energy consumed by the machine or processor during operation. This is critical in energy-efficient systems such as mobile devices or green data centers.\n 指机器或处理器在运行过程中消耗的能量。这在能源高效系统（如移动设备或绿色数据中心）中尤为重要。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::727", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/**Resource Model / 资源模型**/**Network Model / 网络模型**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 527, "text": "- **Network Topology / 网络拓扑**\n\n - Describes the physical or logical layout of the network, including how machines/processing units are connected. Common topologies include star, mesh, ring, and tree.\n 描述网络的物理或逻辑布局，包括机器/处理单元如何连接。常见的拓扑结构包括星型、网状、环型和树型。\n- **Bandwidths / 带宽**\n\n - Refers to the maximum rate at which data can be transmitted over the network. Higher bandwidth allows faster data transfer between machines/processing units.\n 指网络上数据传输的最大速率。更高的带宽允许机器/处理单元之间更快的数据传输。\n- **Messages and Energy Consumption / 消息与能源消耗**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::728", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/**Resource Model / 资源模型**/**Network Model / 网络模型**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 354, "text": "g units.\n 指网络上数据传输的最大速率。更高的带宽允许机器/处理单元之间更快的数据传输。\n- **Messages and Energy Consumption / 消息与能源消耗**\n\n - Involves the energy required to send and receive messages between machines or processors over the network. Communication energy consumption can be significant, especially in wireless or sensor networks.\n 涉及通过网络发送和接收消息所需的能量。通信能源消耗可能很大，尤其是在无线或传感器网络中。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::729", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/**Resource Model / 资源模型**/**Example Use Cases / 应用实例**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 558, "text": "- **Sensor Networks / 传感器网络**\n\n - In sensor networks, the focus is often on low energy consumption, low bandwidth, and reliable communication over potentially unreliable channels.\n 在传感器网络中，重点通常是低能耗、低带宽和在可能不可靠的信道上可靠的通信。\n- **Data Center Networks / 数据中心网络**\n\n - Data centers require high bandwidth, low-latency, and high-throughput networks to support large-scale computation and data storage. Energy consumption is also a key consideration in green data center design.\n 数据中心需要高带宽、低延迟和高吞吐量的网络，以支持大规模计算和数据存储。能源消耗也是绿色数据中心设计中的关键考虑因素。\n- **Mobile Cloud / 移动云**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::730", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/**Resource Model / 资源模型**/**Example Use Cases / 应用实例**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 313, "text": "er design.\n 数据中心需要高带宽、低延迟和高吞吐量的网络，以支持大规模计算和数据存储。能源消耗也是绿色数据中心设计中的关键考虑因素。\n- **Mobile Cloud / 移动云**\n\n - In mobile cloud environments, network performance (bandwidth, latency) and energy consumption are crucial factors, as mobile devices often have limited resources.\n 在移动云环境中，网络性能（带宽、延迟）和能源消耗是关键因素，因为移动设备通常资源有限。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::731", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/Objectives / 目标", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 186, "text": "- Minimize completion time / 最小化完成时间\n- Meeting deadline / 遵守截止时间\n- Maximize throughput / 最大化吞吐量\n- Minimize data transmission/messages / 最小化数据传输/消息\n- Minimize energy consumption / 最小化能源消耗"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::732", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/Classification of Scheduling / 调度的分类", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 240, "text": "- Real-time scheduling vs. non-real-time scheduling / 实时调度与非实时调度\n- Static scheduling vs. dynamic scheduling / 静态调度与动态调度\n- Offline scheduling vs. online scheduling / 离线调度与在线调度\n- Deterministic scheduling vs. stochastic scheduling / 确定性调度与随机调度"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::733", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/Task Scheduling Problems / 任务调度问题", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 680, "text": "1. Bag-of-Tasks scheduling on single processor / 单处理器上的任务包调度\n2. Bag-of-Tasks scheduling on multiple processors / 多处理器上的任务包调度\n3. DAGs scheduling on heterogeneous processors / 在异构处理器上的DAG调度\n4. Job shop scheduling / 作业车间调度\n5. Periodic tasks scheduling / 周期性任务调度\n\n\n\n**Given**: release time, workload of each task, or deadline\n\n已知：每个任务的释放时间、工作量或截止时间\n\nTo determine **when** each task is executed\n\n目的是确定每个任务何时执行\n\n**Objectives**: average completion time of the tasks, or meeting deadlines\n\n目标：任务的平均完成时间，或满足截止时间\n\n\n\n**Given**: release time, workload of each task\n\n已知：每个任务的释放时间、工作量"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::734", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/Task Scheduling Problems / 任务调度问题", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 699, "text": "ile/Rs1IbBsAlooAk6xnvuVcvYmAnmb)\n\n**Given**: release time, workload of each task\n\n已知：每个任务的释放时间、工作量\n\nTo determine **where and when** each task is executed\n\n目的是确定每个任务的执行位置和时间\n\n**Objectives**: make-span\n\n目标：完成时间（Make-span）\n\n\n\nGiven: processing time of every task on every processor communication time on the edges\n\nTo determine where and when each task is executed\n\nObjective: make-span ...\n\n已知：每个处理器上每个任务的处理时间边缘上的通信时间\n\n确定每个任务的执行地点和时间\n\n目标：完成跨度...\n\n\n\nGiven: processing time of every job on every processor\n\n已知：每个任务在每个处理器上的处理时间\n\nConstraint: every job is executed by every processor exactly once"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::735", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/Task Scheduling Problems / 任务调度问题", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 239, "text": "y processor\n\n已知：每个任务在每个处理器上的处理时间\n\nConstraint: every job is executed by every processor exactly once\n\n约束条件：每个任务必须在每个处理器上执行一次\n\nObjective: make-span\n\n目标：完成时间（Make-span）\n\n\n\n任务定期发布，以流水线方式执行"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::736", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/Similar Terminologies / 相似术语", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 244, "text": "- Task assignment / 任务分配\n- Task placement / 任务放置\n- Task allocation / 任务分配\n- Resource allocation / 资源分配\n- Resource scheduling / 资源调度\n\nThe problems above are considered as special cases/instances of the scheduling problem. / 上述问题被认为是调度问题的特殊情况/实例。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::737", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/Categories of Scheduling Algorithms / 调度算法的类别", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 406, "text": "Algorithms to solve optimization problems / 解决优化问题的算法\n\n1. Mathematical programming, i.e., integer programming, linear programming / 数学规划，即整数规划、线性规划\n2. Evolutionary algorithms, i.e., GA, PSO, Ant colony / 进化算法，即遗传算法（GA）、粒子群优化（PSO）、蚁群算法\n3. Simple and competitive heuristics, i.e., list scheduling / 简单且竞争性的启发式算法，即列表调度\n4. Machine learning based algorithm, i.e., deep reinforcement learning / 基于机器学习的算法，即深度强化学习"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::738", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/Scheduling Method: System Considerations", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 620, "text": "调度方法：系统考虑\n\nMachine centric approach / 机器中心方法\n\n- Scheduling is triggered when a machine becomes idle. For each idle machine, select the task according to some policies, e.g.,\n\n - First-Come-First-Serve (FCFS) / 先到先服务（FCFS）\n - Shortest Job First (SJF) / 最短作业优先（SJF）\n - Earliest Deadline First (EDF) / 最早截止时间优先（EDF）\n - Job with the longest waiting time first, ... / 最长等待时间作业优先，...\n\nTask centric approach / 任务中心方法\n\n- Scheduling is triggered when a new task arrives. For each scheduled task, select the machine according to some policies, e.g., earliest finished time, ... / 当新任务到达时触发调度。对于每个调度的任务，根据某些策略选择机器，例如，最早完成时间，..."}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::739", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/List Scheduling Method/Step 1: Task selection / 步骤 1：任务选择", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 195, "text": "- Upward rank / 向上排名\n\n - Upward rank of node i is the length of the longest path from node i to the exit. / 节点 i 的向上排名是从节点 i 到出口的最长路径的长度。\n\n"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::740", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/List Scheduling Method/Step 2: Processor Selection / 步骤 2：处理器选择", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 261, "text": "- Earliest Finish Time / 最早完成时间\n\n - For each task, select the machine which can finish that task in the earliest time. / 对于每个任务，选择能够在最早时间完成该任务的机器。\n\n\n\n"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::741", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/② **Performance** and related tactics / 性能及相关策略/Summary of Performance / 性能总结", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 444, "text": "Performance is about the management of system resources in the face of particular types of demand to achieve acceptable timing behavior. / 性能是指在特定类型的需求面前，如何管理系统资源以实现可接受的时序行为。\n\nPerformance can be measured in terms of throughput and latency for both interactive and embedded real-time systems. / 性能可以通过吞吐量和延迟来衡量，适用于交互式和嵌入式实时系统。\n\nPerformance can be improved by reducing demand or by managing resources more appropriately. / 性能可以通过减少需求或更适当的管理资源来提升。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::742", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/③ **Security** and related tactics / 安全性及相关策略。/What is Security? / 什么是安全性？", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 699, "text": "**Security** is a measure of the system's ability to protect data and information from unauthorized access while still providing access to people and systems that are authorized. / 安全性是衡量系统在保护数据和信息免受未授权访问的同时，仍能提供对授权人员和系统的访问能力。\n\nAn action taken against a computer system with the intention of doing harm is called an attack. / 旨在对计算机系统造成危害的行为称为攻击。\n\nAttack can be in different forms:\n\n- Unauthorized attempt to access/modify data or service / 未经授权尝试访问/修改数据或服务\n- Intended to deny services to legitimate users / 旨在拒绝合法用户的服务\n\n**Security has three main characteristics, called CIA:**\n\n安全性具有三个主要特性，称为CIA：\n\n1. **Confidentiality** is the property that data or services are protected from unauthorized access."}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::743", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/③ **Security** and related tactics / 安全性及相关策略。/What is Security? / 什么是安全性？", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 587, "text": ". **Confidentiality** is the property that data or services are protected from unauthorized access.\n保密性是数据或服务受到未授权访问保护的属性。\n\n - For example, a hacker cannot access your income tax returns on a government computer. / 例如，黑客无法访问政府计算机上的个人所得税报表。\n2. **Integrity** is the property that data or services are not subject to unauthorized manipulation.\n完整性是数据或服务不受未授权篡改的属性。\n\n - For example, your grade has not been changed since your instructor assigned it. / 例如，自从教师给你打分后，你的成绩没有被更改。\n3. **Availability** is the property that the system will be available for legitimate use.\n可用性是系统能为合法使用提供可用性的属性。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::744", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/③ **Security** and related tactics / 安全性及相关策略。/What is Security? / 什么是安全性？", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 576, "text": "lity** is the property that the system will be available for legitimate use.\n可用性是系统能为合法使用提供可用性的属性。\n\n - For example, a denial-of-service attack prevents you from ordering a book from an online bookstore. / 例如，拒绝服务攻击使你无法从在线书店订购书籍。\n\n**Other characteristics that support CIA / 支持CIA的其他特性**\n\n- **Authentication** verifies the identities of the parties to a transaction and checks if they are truly who they claim to be.(WHO you are?)\n认证验证交易各方的身份，并检查他们是否真的是他们所声称的人。（你是谁？）\n- **Authorization** grants a user the privileges to perform a task.(WHAT you can do?)\n授权授予用户执行任务的权限。（你能做什么？）"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::745", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/③ **Security** and related tactics / 安全性及相关策略。/Security General Scenario /安全性通用场景", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 650, "text": "**Portion of Scenario: Possible Values**\n\n场景部分：可能的值\n\n- Source / 源\n\n - Human or another system which may have been previously identified (either correctly or incorrectly) or may be currently unknown. A human attacker may be from outside the organization or from inside the organization.\n - 人类或其他系统可能之前已被识别（正确或错误），或目前未知。人类攻击者可能来自组织外部，也可能来自组织内部。\n- Stimulus / 激励\n\n - **Unauthorized** attempt is made to display data, change or delete data, access system services, change the system's behavior, or reduce availability.\n - 未授权的尝试是指试图显示数据、修改或删除数据、访问系统服务、改变系统行为或降低系统可用性。\n- Artifact / 工件\n\n - System services: 数据在系统中的服务\n - Data within the system: 系统内部的数据"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::746", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/③ **Security** and related tactics / 安全性及相关策略。/Security General Scenario /安全性通用场景", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 477, "text": "改变系统行为或降低系统可用性。\n- Artifact / 工件\n\n - System services: 数据在系统中的服务\n - Data within the system: 系统内部的数据\n - A component or resources of the system: 系统的组件或资源\n - Data produced or consumed by the system: 系统产生或消耗的数据\n- Environment / 环境\n\n - The system is either online or offline, connected to or disconnected from a network, behind a firewall or open to a network, fully operational, partially operational, or not operational.\n - 系统可以是在线或离线、连接或断开网络、位于防火墙后面或开放于网络、完全正常运行、部分正常运行或完全不运行。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::747", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/③ **Security** and related tactics / 安全性及相关策略。/Security General Scenario /安全性通用场景", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 618, "text": "artially operational, or not operational.\n - 系统可以是在线或离线、连接或断开网络、位于防火墙后面或开放于网络、完全正常运行、部分正常运行或完全不运行。\n- Response / 响应Transactions are carried out in a fashion such that data or services are protected from unauthorized access; data or services are not being manipulated without authorization; the data, resources, and system services will be available for legitimate use.事务以如下方式进行：数据或服务受到未授权访问的保护；数据或服务不会在未经授权的情况下被篡改；数据、资源和系统服务将可供合法使用。The system tracks activities within it by:系统通过以下方式跟踪其内部活动：\n\n - Recording access or modification / 记录访问或修改\n - Recording attempts to access data, resources, or services / 记录访问数据、资源或服务的尝试"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::748", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/③ **Security** and related tactics / 安全性及相关策略。/Security General Scenario /安全性通用场景", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 667, "text": "ification / 记录访问或修改\n - Recording attempts to access data, resources, or services / 记录访问数据、资源或服务的尝试\n - Notifying appropriate entities when an apparent attack is occurring / 在明显的攻击发生时通知相关实体\n- Response Measure / 响应度量One or more of the following / 以下之一或多个\n\n - How much of a system is compromised when a particular component or data value is compromised?\n 当特定组件或数据值受到危害时，系统有多少部分被攻破？\n - How much time has passed before an attack was detected?\n 在攻击被发现之前，经过了多少时间？\n - How many attacks were resisted?\n 抵御了多少次攻击？\n - How long does it take to recover from a successful attack?\n 从一次成功的攻击中恢复需要多长时间？\n - How much data is vulnerable to a particular attack?\n 有多少数据对特定攻击是脆弱的？"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::749", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/③ **Security** and related tactics / 安全性及相关策略。/Sample Concrete Security Scenario / 样例具体安全场景", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 659, "text": "A disgruntled employee from a remote location attempts to modify the pay rate table during normal operations. The system maintains an audit trail and the correct data is restored within a day.\n\n一名不满的员工从远程位置试图在正常操作期间修改工资表。系统保持审计记录，并在一天内恢复正确的数据。\n\n- Stimulus: unauthorized attempts to modify the pay rate table\n刺激：未授权的尝试修改工资表\n- Stimulus source: a disgruntled employee\n刺激源：一名不满的员工\n- Artifact: the system with pay rate table\n工件：包含工资表的系统\n- Environment: during normal operation\n环境：正常操作期间\n- Response: maintains an audit trail\n响应：保持审计记录\n- Response measure: correct data is restored within a day\n响应度量：在一天内恢复正确的数据\n\n"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::750", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/③ **Security** and related tactics / 安全性及相关策略。/Security Tactics / 安全性策略/Detect Attacks / 检测攻击", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 122, "text": "Detect Intrusion / 检测入侵\n\nDetect Service Denial / 检测服务拒绝\n\nVerify Message Integrity / 验证消息完整性\n\nDetect Message Delay / 检测消息延迟"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::751", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/③ **Security** and related tactics / 安全性及相关策略。/Security Tactics / 安全性策略/Resist Attacks / 抵御攻击", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 203, "text": "Identify Actors / 识别行为者\n\nAuthenticate Actors / 认证行为者\n\nAuthorize Actors / 授权行为者\n\nLimit Access / 限制访问\n\nLimit Exposure / 限制暴露\n\nEncrypt Data / 加密数据\n\nSeparate Entities / 分离实体\n\nChange Default Settings / 更改默认设置"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::752", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/③ **Security** and related tactics / 安全性及相关策略。/Security Tactics / 安全性策略/React to Attacks / 对攻击做出反应", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 68, "text": "Revoke Access / 撤销访问权限\n\nLock Computer / 锁定计算机\n\nInform Actors / 通知行为者"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::753", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/③ **Security** and related tactics / 安全性及相关策略。/Security Tactics / 安全性策略/Recover from Attacks / 从攻击中恢复过来", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 73, "text": "Maintain Audit Trail / 保持审计记录\n\nRestore / 恢复\n\n恢复详情请搜索：Availability Tactics"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::754", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/③ **Security** and related tactics / 安全性及相关策略。/Detect Attacks / 检测攻击", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 698, "text": "1. **Detect Intrusion / 检测入侵**\n\n - Definition: Compare network traffic or service request patterns within a system to a set of signatures or known patterns of malicious behavior stored in a database.\n 定义：将系统内的网络流量或服务请求模式与存储在数据库中的已知恶意行为签名或模式进行比较。\n2. **Detect Service Denial / 检测服务拒绝**\n\n - Definition: Comparison of the pattern or signature of network traffic coming into a system to historic profiles of known Denial of Service (DoS) attacks.\n 定义：将进入系统的网络流量模式或签名与已知的服务拒绝（DoS）攻击的历史资料进行比较。\n3. **Verify Message Integrity / 验证消息完整性**\n\n - Definition: Use techniques such as checksums or hash values to verify the integrity of messages, resource files, deployment files, and configuration files."}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::755", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/③ **Security** and related tactics / 安全性及相关策略。/Detect Attacks / 检测攻击", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 430, "text": "ues to verify the integrity of messages, resource files, deployment files, and configuration files.\n 定义：使用校验和或哈希值等技术来验证消息、资源文件、部署文件和配置文件的完整性。\n4. **Detect Message Delay / 检测消息延迟**\n\n - Definition: Check the time it takes to deliver a message; it is possible to detect suspicious timing behavior, such as a man-in-the-middle attack.\n 定义：检查消息传递所需的时间，可以检测到可疑的时序行为，例如中间人攻击。\n\n"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::756", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/③ **Security** and related tactics / 安全性及相关策略。/Resist Attacks / 抵御攻击", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 636, "text": "1. Identify Actors / 识别行为者\n\n - Definition: Identify the source of any external input to the system.\n 定义：识别系统的任何外部输入来源。\n2. Authenticate Actors / 验证行为者\n\n - Definition: Ensure that a user or remote computer is actually who or what it purports to be.\n 定义：确保用户或远程计算机确实是其所声明的身份。\n3. Authorize Actors / 授权行为者\n\n - Definition: Ensuring that an authenticated actor has the rights to access and modify either data or services.\n 定义：确保已验证的行为者具有访问和修改数据或服务的权限。\n4. Limit Access / 限制访问\n\n - Definition: Limiting access to resources such as memory, network connections, or access points.\n 定义：限制对资源（如内存、网络连接或访问点）的访问。\n5. Limit Exposure / 限制暴露"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::757", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/③ **Security** and related tactics / 安全性及相关策略。/Resist Attacks / 抵御攻击", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 681, "text": "ory, network connections, or access points.\n 定义：限制对资源（如内存、网络连接或访问点）的访问。\n5. Limit Exposure / 限制暴露\n\n - Definition: Minimize the attack surface of a system by having the fewest possible number of access points.\n 定义：通过减少访问点的数量来最小化系统的攻击面。\n - Example / 示例:\n\n - Firewall is a single point of access to the intranet.\n 防火墙是访问内网的唯一入口。\n - Closing a port.\n 关闭端口。\n6. Passive Defense / 被动防御\n\n - Definition: Techniques that reduce the chances of an attack succeeding without actively interfering with the attacker.\n 定义：通过减少攻击成功的机会来避免攻击，而不是主动干扰攻击者。\n7. Encrypt Data / 加密数据\n\n - Definition: Apply some form of encryption to data and communication.\n 定义：对数据和通信应用某种形式的加密。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::758", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/③ **Security** and related tactics / 安全性及相关策略。/Resist Attacks / 抵御攻击", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 676, "text": "- Definition: Apply some form of encryption to data and communication.\n 定义：对数据和通信应用某种形式的加密。\n\n\n\n1. Separate Entities / 分离实体\n\n - Definition: Can be done through physical separation on different servers, or the use of virtual machines.\n 定义：可以通过在不同服务器上的物理分离，或使用虚拟机来实现。\n2. Change Default Settings / 更改默认设置\n\n - Definition: Force the user to change settings assigned by default.\n 定义：强制用户更改默认分配的设置。\n3. Revoke Access / 撤销访问权限\n\n - Definition: Limit access to sensitive resources, even for normally legitimate users and uses, if an attack is suspected.\n 定义：如果怀疑发生攻击，即使是正常的合法用户和用途，也要限制对敏感资源的访问。\n4. Lock Computer / 锁定计算机"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::759", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/③ **Security** and related tactics / 安全性及相关策略。/Resist Attacks / 抵御攻击", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 400, "text": "es, if an attack is suspected.\n 定义：如果怀疑发生攻击，即使是正常的合法用户和用途，也要限制对敏感资源的访问。\n4. Lock Computer / 锁定计算机\n\n - Definition: Limit access to a resource if there are repeated failed attempts to access it.\n 定义：如果多次尝试访问资源失败，则限制访问该资源。\n5. Inform Actors / 通知行为者\n\n - Definition: Notify operators, other personnel, or cooperating systems when an attack is suspected or detected.\n 定义：当怀疑或检测到攻击时，通知操作员、其他人员或合作系统。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::760", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/③ **Security** and related tactics / 安全性及相关策略。/Summary of Security / 安全性总结", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 497, "text": "Attacks against a system can be characterized as attacks against the confidentiality, integrity, or availability of a system.\n\n对系统的攻击可以被描述为对系统的机密性、完整性或可用性的攻击。\n\nIdentifying, authenticating, and authorizing actors are tactics intended to determine which users or systems are entitled to what kind of access to a system.\n\n识别、验证和授权行为者是旨在确定哪些用户或系统有权访问系统的哪些资源的策略。\n\nTactics exist to detect an attack, limit the spread of any attack, and to react and recover from an attack.\n\n存在用于检测攻击、限制攻击蔓延、以及应对和恢复攻击的策略。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::761", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/④ **Interoperability** and related tactics (e.g. how Service Discovery works)", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 25, "text": "互操作性及相关策略（例如，服务发现是如何工作的）。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::762", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/④ **Interoperability** and related tactics (e.g. how Service Discovery works)/What is interoperability? / 什么是互操作性？", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 339, "text": "**Interoperability** is about the degree to which two or more systems can usefully exchange meaningful information via interfaces in a particular context.\n\n互操作性是指两个或多个系统在特定上下文中通过接口有效地交换有意义的信息的程度。\n\nAny discussion of **a system's interoperability** needs to identify with whom, and under what circumstances.\n\n任何关于系统互操作性的讨论都需要明确与谁、以及在什么情况下进行。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::763", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/④ **Interoperability** and related tactics (e.g. how Service Discovery works)/**Types of Interoperability / 互操作性的类型**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 625, "text": "1. Syntactic interoperability / 语法互操作性\n\n - Definition: The ability to exchange data.\n 定义：数据交换的能力。\n2. Semantic interoperability / 语义互操作性\n\n - Definition: The ability to interpret the data being exchanged.\n 定义：解释交换数据的能力。\n\n**Two Perspectives for Achieving Interoperability / 实现互操作性的两种视角**\n\n1. With knowledge about the interfaces of external systems, design that knowledge into the system.\n拥有外部系统接口的知识，将该知识设计到系统中。\n2. Without knowledge about other systems, design the system to interoperate in a more general fashion.\n没有其他系统的知识，设计系统以更通用的方式进行互操作。\n\n**Examples of Systems and Interoperability （Motivation) / 系统及互操作性的例子 （驱动力）**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::764", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/④ **Interoperability** and related tactics (e.g. how Service Discovery works)/**Types of Interoperability / 互操作性的类型**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 679, "text": "知识，设计系统以更通用的方式进行互操作。\n\n**Examples of Systems and Interoperability （Motivation) / 系统及互操作性的例子 （驱动力）**\n\n- The system provides a service to be used by a collection of unknown systems, e.g., Google Maps.\n该系统提供服务供一组未知系统使用，例如Google Maps。\n- The system is constructed from existing systems, for example:\n系统是由现有系统构建的，例如：\n\n - Producing a representation of what was sensed\n 生成所感知内容的表示\n - Interpreting the data\n 解释数据\n - Processing raw data\n 处理原始数据\n - Sensing the environment\n 感知环境\n\n**Discovery / 服务发现**\n\nThe consumer of a service must discover the location, identity, and interface of the service.\n\n服务的消费者必须发现服务的位置、身份和接口。\n\n**Handling the Response / 处理响应**\n\nThree possibilities:\n\n三种可能性："}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::765", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/④ **Interoperability** and related tactics (e.g. how Service Discovery works)/**Types of Interoperability / 互操作性的类型**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 302, "text": "e service.\n\n服务的消费者必须发现服务的位置、身份和接口。\n\n**Handling the Response / 处理响应**\n\nThree possibilities:\n\n三种可能性：\n\n1. The service reports back to the requester\n服务向请求者报告\n2. The service sends its response to another system\n服务将其响应发送到另一个系统\n3. The service broadcasts its response to any interested parties\n服务将其响应广播给所有感兴趣的方"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::766", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/④ **Interoperability** and related tactics (e.g. how Service Discovery works)/Interoperability General Scenario / 互操作性通用场景", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 696, "text": "**Portion of Scenario: Possible Values**\n\n场景部分：可能的值\n\n- Source / 源\n\n - A System\n - 一个系统\n- Stimulus / 激励\n\n - A request to exchange information among system(s)\n - 系统间交换信息的请求\n- Artifact / 工件\n\n - The systems to exchange information among system(s)\n - 系统间交换信息的系统\n- Environment / 环境\n\n - System(s) wishing to interoperate are discovered at run time or known prior to run time\n - 希望互操作的系统在运行时被发现或在运行之前已知\n- Response / 响应One or more of the following:以下之一或多个：\n\n - The request is (appropriately) rejected and appropriate entities (people or systems) are notified.\n 请求被（适当地）拒绝，相关实体（人员或系统）被通知。\n - The request is (appropriately) accepted and information is exchanged successfully.\n 请求被（适当地）接受，信息成功交换。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::767", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/④ **Interoperability** and related tactics (e.g. how Service Discovery works)/Interoperability General Scenario / 互操作性通用场景", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 384, "text": "request is (appropriately) accepted and information is exchanged successfully.\n 请求被（适当地）接受，信息成功交换。\n - The request is logged by one or more of the involved systems.\n 请求被一个或多个相关系统记录。\n- Response Measure / 响应度量One or more of the following:以下之一或多个：\n\n - Percentage of information exchanges correctly processed\n 正确信息交换的百分比\n - Percentage of information exchanges rejected\n 被拒绝的信息交换的百分比"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::768", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/④ **Interoperability** and related tactics (e.g. how Service Discovery works)/Sample Concrete Interoperability Scenario / 具体的互操作性场景示例", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 651, "text": "- **Our vehicle information system** sends our current location to the **traffic monitoring system**.\n我们的车辆信息系统将当前位置发送到交通监控系统。\n- The traffic monitoring system combines our location with other information, overlays this information on a Google Map, and **broadcasts** it.\n交通监控系统将我们的位置信息与其他信息结合，并将这些信息叠加在 Google 地图上，然后广播出去。\n- Our location information is correctly included with a probability of 99.9%.\n我们的位置信息正确包含的概率为 99.9%。\n- Analysis / 分析\n\n - Source: Our vehicle information system / 我们的车辆信息系统\n - Stimulus: A request to exchange information among system(s) / 系统间交换信息的请求\n - Artifact: The systems to exchange information among system(s) / 系统间交换信息的系统"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::769", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/④ **Interoperability** and related tactics (e.g. how Service Discovery works)/Sample Concrete Interoperability Scenario / 具体的互操作性场景示例", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 628, "text": "stem(s) / 系统间交换信息的请求\n - Artifact: The systems to exchange information among system(s) / 系统间交换信息的系统\n - Environment: System(s) wishing to interoperate are discovered at run time or known prior to run time / 希望互操作的系统在运行时被发现或在运行之前已知\n - Response: One or more of the following / 以下之一或多个：\n\n 1. The request is (appropriately) accepted and information is exchanged successfully / 请求被（适当地）接受，信息成功交换。\n\n - 车辆信息系统将位置信息发送给交通监控系统，并成功完成交换，交通监控系统成功接收并整合这些信息。\n 2. The request is logged by one or more of the involved systems / 请求被一个或多个相关系统记录。\n\n - 请求的信息交换被系统记录和追踪。\n - Response Measure: One or more of the following / 以下之一或多个："}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::770", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/④ **Interoperability** and related tactics (e.g. how Service Discovery works)/Sample Concrete Interoperability Scenario / 具体的互操作性场景示例", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 455, "text": "多个相关系统记录。\n\n - 请求的信息交换被系统记录和追踪。\n - Response Measure: One or more of the following / 以下之一或多个：\n\n 1. Percentage of information exchanges correctly processed / 正确信息交换的百分比\n\n - 在此场景中，99.9% of our location information is correctly included / 我们的位置信息正确包含的概率为 99.9%，即信息交换的正确处理率为 99.9%。\n 2. Percentage of information exchanges rejected / 被拒绝的信息交换的百分比\n\n - 根据场景，未提及被拒绝的交换，因此可以假设该百分比为 0。\n\n"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::771", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/④ **Interoperability** and related tactics (e.g. how Service Discovery works)/Interoperability Tactics / 互操作性策略/Manage Interfaces / 管理接口", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 41, "text": "Orchestrate / 编排\n\nTailor Interface / 定制界面"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::772", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/④ **Interoperability** and related tactics (e.g. how Service Discovery works)/Locate / 定位", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 178, "text": "Service Discovery / 服务发现\n\n- Locate a service through searching\n通过搜索定位服务\n\nThere are many service discovery mechanisms:\n\n有许多服务发现机制：\n\n- UDDI for Web services\nWeb服务的 UDDI（统一描述、发现和集成）"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::773", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/④ **Interoperability** and related tactics (e.g. how Service Discovery works)/Service Discovery - Necessary Conditions / 服务发现：必要的条件", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 298, "text": "The searcher wants to find the searched entity and the searched entity **wants to be found.**\n\n搜索者希望找到被搜索的实体，而被搜索的实体希望被找到。\n\nThe searched entity must have **identifiers.**\n\n被搜索的实体必须具有标识符。\n\nThe searcher must acquire **sufficient identifiers** to identify the searched entity.\n\n搜索者必须获取足够的标识符来识别被搜索的实体。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::774", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/④ **Interoperability** and related tactics (e.g. how Service Discovery works)/Searching Method - Searcher's initiative / 搜索方法 - 搜索者的倡议/Flood/Broadcast Request / 洪泛/广播请求", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 273, "text": "- Ask every entity and wait for an answer / 向每个实体发出请求并等待回答\n- Efficient and less resource consuming for the searcher / 对搜索者来说高效且资源消耗较少\n- Low resource consuming for the searched / 对被搜索者来说资源消耗较少\n- But disturbing and resource consuming for the environment / 但对环境来说，可能会引起干扰并消耗资源"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::775", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/④ **Interoperability** and related tactics (e.g. how Service Discovery works)/Searching Method - Searcher's initiative / 搜索方法 - 搜索者的倡议/Successive Request / 连续请求", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 319, "text": "- Ask one entity at a time and perform matching / 一次请求一个实体并进行匹配\n- If no match, continue with next until finding a match / 如果没有匹配，继续向下一个实体请求，直到找到匹配\n- Less efficient and high resource consuming for the searcher / 对搜索者来说效率较低且资源消耗较高\n- But less disturbing and less resource consuming for the environment / 但对环境来说，干扰较小且资源消耗较少"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::776", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/④ **Interoperability** and related tactics (e.g. how Service Discovery works)/Searching Method - Searched's initiative / 搜索方法 - 被搜索者的倡议/Continuous/Periodical Advertisement / 连续/定期广告", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 338, "text": "- Continuously or periodically publish advertisement such that every searcher can notice and respond / 持续或定期发布广告，使每个搜索者都能注意到并作出响应\n- Efficient but high resource consuming for the searched / 对被搜索者来说高效，但资源消耗较高\n- Low resource demanding for the searcher / 对搜索者来说资源需求较低\n- Disturbing and resource consuming for the environment / 对环境来说干扰较大且资源消耗较多"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::777", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/④ **Interoperability** and related tactics (e.g. how Service Discovery works)/Searching Method - Searched's initiative / 搜索方法 - 被搜索者的倡议/Advertisement Upon Arrival of New Entity / 新实体到达时的广告", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 350, "text": "- E.g., present himself when a new person enters the lobby / 例如，当新人员进入大厅时，他会主动展示自己\n- Require detection mechanism upon new entity arrival / 需要在新实体到达时启用检测机制\n- Less resource consuming for the searched / 对被搜索者来说资源消耗较少\n- Low resource demanding for the searcher / 对搜索者来说资源需求较低\n- Less disturbing and resource consuming for the environment / 对环境来说干扰较小，资源消耗较少"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::778", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/④ **Interoperability** and related tactics (e.g. how Service Discovery works)/Searching Method - Registration / 搜索方法：注册/Introduction of the “Middlemen”, Registry / “中介”介绍，注册表", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 175, "text": "- The searched entity registers to a registry / 被搜索的实体向注册表注册\n- The searcher can address the registry to get information and find the searched entity / 搜索者可以查询注册表以获取信息并找到被搜索的实体"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::779", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/④ **Interoperability** and related tactics (e.g. how Service Discovery works)/Searching Method - Registration / 搜索方法：注册/Example / 示例", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 692, "text": "- Service providers register their web services at UDDI registry which can be searched and found by Service Requestors / 服务提供者将其Web服务注册到UDDI注册表，服务请求者可以在该注册表中搜索并找到这些服务。\n\n\n\nLess resource consumption on both searchers, searched and less disturbing to the environment, but the registry must be available, reliable, and correct.\n\n对搜索者和被搜索者的资源消耗较少，对环境干扰较小，但注册表必须是可用的、可靠的和正确的。\n\n\n\nWeb Service Architectrue / 网络服务架构\n\nRegistry / 注册表\n\n1. Publish Service Description / 发布服务描述\n\n- Web Service Provider / 网络服务提供者\n\n1. Discovery of Suitable Services and How to Communicate with Them / 发现合适的服务及如何与其通信"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::780", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/④ **Interoperability** and related tactics (e.g. how Service Discovery works)/Searching Method - Registration / 搜索方法：注册/Example / 示例", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 217, "text": "der / 网络服务提供者\n\n1. Discovery of Suitable Services and How to Communicate with Them / 发现合适的服务及如何与其通信\n\n- Web Service Client / 网络服务客户端\n\n1. Service Invocation / 服务调用\n\n"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::781", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/④ **Interoperability** and related tactics (e.g. how Service Discovery works)/Manage Interfaces / 管理接口/Orchestrate / 协调", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 247, "text": "- Uses a control mechanism to coordinate, manage, and sequence the invocation of services. / 使用控制机制来协调、管理和按顺序调用服务。\n- Orchestration is used when systems must interact in a complex fashion to accomplish a complex task. / 协调用于当系统必须以复杂的方式相互作用以完成复杂任务时。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::782", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/④ **Interoperability** and related tactics (e.g. how Service Discovery works)/Manage Interfaces / 管理接口/Tailor Interface / 定制接口", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 123, "text": "- Add or remove capabilities to an interface such as translation, buffering, or data-smoothing. / 向接口添加或删除功能，如翻译、缓冲或数据平滑处理。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::783", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/⑤ **Quality** attribute scenarios/Chapter 05 Availability / 可用性/General Scenario / 通用场景", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::784", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/⑤ **Quality** attribute scenarios/Chapter 05 Availability / 可用性/Example / 示例", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 505, "text": "The heartbeat monitor detects that the server is nonresponsive during normal operations. The system informs the operator and continues to operate with no downtime.\n\n心跳监控器检测到服务器在正常操作期间无响应。系统通知操作员，并在没有停机的情况下继续运行。\n\n- Stimulus / 刺激: Non-responsiveness\n无响应\n- Response / 响应: Inform the operator\n通知操作员\n- Response measure / 响应度量: No downtime, or 100% availability percentage\n没有停机，或 100% 的可用性百分比\n- Environment / 环境: Normal operation\n正常操作\n- Artifact / 工件: Heartbeat monitor\n心跳监控器\n- Stimulus source / 刺激源: Server\n服务器"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::785", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/⑤ **Quality** attribute scenarios/Chapter 06 Interoperability / 互操作性/General Scenario / 通用场景", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::786", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/⑤ **Quality** attribute scenarios/Chapter 06 Interoperability / 互操作性/Example / 示例", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 411, "text": "Our vehicle information system sends our current location to the traffic monitoring system.\n\n我们的车辆信息系统将当前位置信息发送给交通监控系统。\n\nThe traffic monitoring system combines our location with other information, overlays this information on a Google Map, and broadcasts it.\n\n交通监控系统将我们的位置信息与其他信息结合，并将这些信息叠加在 Google 地图上，然后进行广播。\n\nOur location information is correctly included with a probability of 99.9%.\n\n我们的位置信息正确包含的概率为 99.9%。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::787", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/⑤ **Quality** attribute scenarios/Chapter 07 Modifiability / 可修改性/General Scenario / 通用场景", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::788", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/⑤ **Quality** attribute scenarios/Chapter 07 Modifiability / 可修改性/Example / 示例", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 449, "text": "The developer wishes to change the user interface by modifying the code at design time. The modifications are made with no side effects within three hours.\n\n开发者希望通过在设计时修改代码来更改用户界面。修改在三小时内完成，并且没有副作用。\n\n- Stimulus / 刺激: Wishes to change UI\n\n 希望更改用户界面\n\n- Artifact / 工件: Code\n\n 代码\n\n- Environment / 环境: Design time\n设计时\n- Response / 响应: Change made\n已完成更改\n- Response measure / 响应度量: No side effects in three hours\n三小时内无副作用\n- Source / 来源: Developer\n开发者"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::789", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/⑤ **Quality** attribute scenarios/Chapter 08 Performance / 性能/General Scenario / 通用场景", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::790", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/⑤ **Quality** attribute scenarios/Chapter 08 Performance / 性能/Example / 示例", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 421, "text": "Users initiate transactions under normal operations. The system processes the transactions with an average latency of two seconds.\n\n用户在正常操作下发起交易。系统以平均两秒的延迟处理交易。\n\n- Stimulus / 刺激: Transaction arrivals\n交易到达\n- Source / 来源: Users\n用户\n- Artifact / 工件: The system\n系统\n- Response / 响应: Process the transactions\n处理交易\n- Response measure / 响应度量: Average latency of two seconds\n平均延迟为两秒\n- Environment / 环境: Under normal operation\n正常操作下"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::791", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/⑤ **Quality** attribute scenarios/Chapter 09 Security / 安全性/General Scenario / 通用场景", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 283, "text": "\n\n\n\n\n\n\n\n"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::792", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/⑤ **Quality** attribute scenarios/Chapter 09 Security / 安全性/Example / 示例", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 616, "text": "A disgruntled employee from a remote location attempts to modify the pay rate table during normal operations. The system maintains an audit trail and the correct data is restored within a day.\n\n一名不满的员工从远程位置试图在正常操作期间修改薪资表。系统保持审计追踪，并且在一天内恢复正确的数据。\n\n- Stimulus / 刺激: Unauthorized attempts to modify the pay rate table\n未经授权的尝试修改薪资表\n- Stimulus source / 刺激源: A disgruntled employee\n一名不满的员工\n- Artifact / 工件: The system with pay rate table\n包含薪资表的系统\n- Environment / 环境: During normal operation\n正常操作期间\n- Response / 响应: Maintains an audit trail\n保持审计追踪\n- Response measure / 响应度量: Correct data is restored within a day\n正确的数据在一天内恢复"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::793", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/⑤ **Quality** attribute scenarios/Chapter 10 Testability / 可测试性/General Scenario / 通用场景", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 550, "text": "\n\n\n\n\n\n**Response Measure / 响应度量**\n\nOne or more of the following:\n\n以下之一或多个：\n\n- Effort to find a fault\n寻找故障的努力\n- Effort to achieve a given percentage of state space coverage\n实现给定状态空间覆盖率的努力\n- Probability of fault being revealed by the next test\n通过下一个测试揭示故障的概率\n- Time to perform tests\n执行测试的时间\n- Effort to detect faults\n检测故障的努力\n- Length of time to prepare for the test environment\n准备测试环境的时间"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::794", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/⑤ **Quality** attribute scenarios/Chapter 10 Testability / 可测试性/Example / 示例", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 499, "text": "The unit tester completes a code unit during development and performs a test sequence whose results are captured and that gives 85% path coverage within 3 hours of testing.\n\n单元测试员在开发过程中完成一个代码单元，并执行一个测试序列，捕获其结果，并在 3 小时的测试内达到 85% 的路径覆盖率。\n\n- Source / 来源: Unit tester\n单元测试员\n- Stimulus / 刺激: Code unit completed\n代码单元完成\n- Artifact / 工件: Code unit\n代码单元\n- Environment / 环境: Development\n开发环境\n- Response / 响应: Capture results\n捕获结果\n- Response measure / 响应度量: 85% path coverage in three hours\n在三小时内达到 85% 的路径覆盖率"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::795", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/⑤ **Quality** attribute scenarios/Chapter 11 Usability / 易用性/General Scenario / 通用场景", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::796", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/⑤ **Quality** attribute scenarios/Chapter 11 Usability / 易用性/Example / 示例", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 406, "text": "The user downloads a new application and is using it productively after two minutes of experimentation.\n\n用户下载一个新应用程序，并在两分钟的试验后开始高效使用它。\n\n- Source / 来源: User\n用户\n- Stimulus / 刺激: Download a new application\n下载新应用程序\n- Artifact / 工件: System\n系统\n- Environment / 环境: Runtime\n运行时\n- Response / 响应: User uses application productively\n用户高效使用应用程序\n- Response measure / 响应度量: Within two minutes of experimentation\n在两分钟的试验内"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::797", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/⑤ **Quality** attribute scenarios/Chapter 12 Other Quality attributes / 其他质量属性", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 502, "text": "[iso25000.com](https://iso25000.com/index.php/en/iso-25000-standards/iso-25010)\n\n[ISO/IEC 25010 Software Quality Standard](https://thetechnologyvault.com/iso-25010-software-quality-standard#:~:text=ISO%2FIEC%2025010%20%28often%20referred%20to%20as%20simply%20ISO,model%20for%20assessing%20the%20quality%20of%20software%20products.)\n\n\n\n\n\n"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::798", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/⑤ **Quality** attribute scenarios/Chapter 12 Other Quality attributes / 其他质量属性/**Functional Suitability / 功能适用性**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 649, "text": "This characteristic represents the degree to which a product or system provides functions that meet stated and implied needs when used under specified conditions. This characteristic is composed of the following sub-characteristics.\n**这一特性表示产品或系统在特定条件下提供的功能满足明确和隐含需求的程度。该特性由以下子特性组成。**\n\n- **Functional completeness / 功能完整性**\n Degree to which the set of functions covers all the specified tasks and intended users' objectives.\n**功能集覆盖所有指定任务和预期用户目标的程度。**\n- **Functional correctness / 功能正确性**\n Degree to which a product or system provides accurate results when used by intended users.\n**产品或系统在预期用户使用时提供准确结果的程度。**\n- **Functional appropriateness / 功能适当性**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::799", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/⑤ **Quality** attribute scenarios/Chapter 12 Other Quality attributes / 其他质量属性/**Functional Suitability / 功能适用性**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 219, "text": "s when used by intended users.\n**产品或系统在预期用户使用时提供准确结果的程度。**\n- **Functional appropriateness / 功能适当性**\n Degree to which the functions facilitate the accomplishment of specified tasks and objectives.\n**功能在完成指定任务和目标中的促进程度。**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::800", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/⑤ **Quality** attribute scenarios/Chapter 12 Other Quality attributes / 其他质量属性/**Performance Efficiency / 性能效率**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 655, "text": "This characteristic represents the degree to which a product performs its functions within specified time and throughput parameters and is efficient in the use of resources (such as CPU, memory, storage, network devices, energy, materials, etc.) under specified conditions. This characteristic is composed of the following sub-characteristics.\n**这一特性表示产品在特定时间和吞吐量参数内执行其功能的效率，并在特定条件下有效利用资源（如 CPU、内存、存储、网络设备、能源、材料等）。该特性由以下子特性组成。**\n\n- **Time behavior / 时间行为**\n Degree to which the response time and throughput rates of a product or system, when performing its functions, meet requirements.\n**产品或系统在执行功能时，其响应时间和吞吐率满足需求的程度。**\n- **Resource utilization / 资源利用率**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::801", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/⑤ **Quality** attribute scenarios/Chapter 12 Other Quality attributes / 其他质量属性/**Performance Efficiency / 性能效率**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 399, "text": "functions, meet requirements.\n**产品或系统在执行功能时，其响应时间和吞吐率满足需求的程度。**\n- **Resource utilization / 资源利用率**\n Degree to which the amounts and types of resources used by a product or system, when performing its functions, meet requirements.\n**产品或系统在执行功能时，所使用的资源量和资源类型满足需求的程度。**\n- **Capacity / 容量**\n Degree to which the maximum limits of a product or system parameter meet requirements.\n**产品或系统参数的最大限制满足需求的程度。**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::802", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/⑤ **Quality** attribute scenarios/Chapter 12 Other Quality attributes / 其他质量属性/**Compatibility / 兼容性**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 649, "text": "Degree to which a product, system, or component can exchange information with other products, systems, or components, and/or perform its required functions while sharing the same common environment and resources. This characteristic is composed of the following sub-characteristics.\n**产品、系统或组件在共享相同的公共环境和资源时，与其他产品、系统或组件交换信息或执行所需功能的程度。该特性由以下子特性组成。**\n\n- **Co-existence / 共存性**\n Degree to which a product can perform its required functions efficiently while sharing a common environment and resources with other products, without detrimental impact on any other product.\n**产品在共享公共环境和资源时，与其他产品共存并有效执行所需功能的程度，不对其他产品产生不利影响。**\n- **Interoperability / 互操作性**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::803", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/⑤ **Quality** attribute scenarios/Chapter 12 Other Quality attributes / 其他质量属性/**Compatibility / 兼容性**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 287, "text": "ny other product.\n**产品在共享公共环境和资源时，与其他产品共存并有效执行所需功能的程度，不对其他产品产生不利影响。**\n- **Interoperability / 互操作性**\n Degree to which a system, product, or component can exchange information with other products and mutually use the information that has been exchanged.\n**系统、产品或组件与其他产品交换信息并互相利用已交换信息的程度。**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::804", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/⑤ **Quality** attribute scenarios/Chapter 12 Other Quality attributes / 其他质量属性/**Interaction Capability / 交互能力**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 695, "text": "Degree to which a product or system can be interacted with by specified users to exchange information via the user interface to complete specific tasks in a variety of contexts of use. This characteristic is composed of the following sub-characteristics.\n**产品或系统在特定的使用情境下，用户通过用户界面与其交互并完成特定任务的能力。该特性由以下子特性组成。**\n\n- **Appropriateness recognizability / 适当性识别度**\n Degree to which users can recognize whether a product or system is appropriate for their needs.\n**用户识别产品或系统是否适合其需求的程度。**\n- **Learnability / 可学习性**\n Degree to which the functions of a product or system can be learned to be used by specified users within a specified amount of time.\n**用户在指定时间内学习并使用产品或系统功能的难易程度。**\n- **Operability / 可操作性**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::805", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/⑤ **Quality** attribute scenarios/Chapter 12 Other Quality attributes / 其他质量属性/**Interaction Capability / 交互能力**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 575, "text": "ed users within a specified amount of time.\n**用户在指定时间内学习并使用产品或系统功能的难易程度。**\n- **Operability / 可操作性**\n Degree to which a product or system has attributes that make it easy to operate and control.\n**产品或系统具有易于操作和控制的属性的程度。**\n- **User error protection / 用户错误保护**\n Degree to which a system prevents users from operating errors.\n**系统防止用户操作错误的程度。**\n- **User engagement / 用户参与度**\n Degree to which a user interface presents functions and information in an inviting and motivating manner, encouraging continued interaction.\n**用户界面以吸引人且激励性的方式呈现功能和信息，鼓励用户持续交互的程度。**\n- **Inclusivity / 包容性**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::806", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/⑤ **Quality** attribute scenarios/Chapter 12 Other Quality attributes / 其他质量属性/**Interaction Capability / 交互能力**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 613, "text": "encouraging continued interaction.\n**用户界面以吸引人且激励性的方式呈现功能和信息，鼓励用户持续交互的程度。**\n- **Inclusivity / 包容性**\n Degree to which a product or system can be used by people of various backgrounds (such as people of various ages, abilities, cultures, ethnicities, languages, genders, economic situations, etc.).\n**产品或系统能被不同背景（如年龄、能力、文化、民族、语言、性别、经济状况等）的人群使用的程度。**\n- **User assistance / 用户帮助**\n Degree to which a product can be used by people with the widest range of characteristics and capabilities to achieve specified goals in a specified context of use.\n**产品帮助不同特征和能力的用户在指定的使用情境中实现指定目标的程度。**\n- **Self-descriptiveness / 自我描述性**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::807", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/⑤ **Quality** attribute scenarios/Chapter 12 Other Quality attributes / 其他质量属性/**Interaction Capability / 交互能力**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 447, "text": "specified context of use.\n**产品帮助不同特征和能力的用户在指定的使用情境中实现指定目标的程度。**\n- **Self-descriptiveness / 自我描述性**\n Degree to which a product presents appropriate information, where needed by the user, to make its capabilities and use immediately obvious to the user without excessive interactions with the product or other resources (such as user documentation, help desks, or other users).\n**产品在需要时呈现适当的信息，使其功能和使用方法无需过多与产品或其他资源（如用户文档、帮助台或其他用户）交互，即可让用户立即理解的程度。**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::808", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/⑤ **Quality** attribute scenarios/Chapter 12 Other Quality attributes / 其他质量属性/**Reliability / 可靠性**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 617, "text": "Degree to which a system, product, or component performs specified functions under specified conditions for a specified period of time. This characteristic is composed of the following sub-characteristics.\n**系统、产品或组件在特定条件下、在指定时间段内执行指定功能的能力。该特性由以下子特性组成。**\n\n- **Faultlessness / 无故障性**\n Degree to which a system, product, or component performs specified functions without fault under normal operation.\n**系统、产品或组件在正常操作下无故障地执行指定功能的程度。**\n- **Availability / 可用性**\n Degree to which a system, product, or component is operational and accessible when required for use.\n**系统、产品或组件在需要时可操作并可以访问的程度。**\n- **Fault tolerance / 故障容忍性**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::809", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/⑤ **Quality** attribute scenarios/Chapter 12 Other Quality attributes / 其他质量属性/**Reliability / 可靠性**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 510, "text": "al and accessible when required for use.\n**系统、产品或组件在需要时可操作并可以访问的程度。**\n- **Fault tolerance / 故障容忍性**\n Degree to which a system, product, or component operates as intended despite the presence of hardware or software faults.\n**系统、产品或组件在硬件或软件故障存在的情况下仍能按预期工作 的程度。**\n- **Recoverability / 恢复性**\n Degree to which, in the event of an interruption or a failure, a product or system can recover the data directly affected and re-establish the desired state of the system.\n**在中断或故障发生时，产品或系统能够恢复直接受影响的数据，并重新建立系统的期望状态的程度。**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::810", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/⑤ **Quality** attribute scenarios/Chapter 12 Other Quality attributes / 其他质量属性/**Security / 安全性**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 596, "text": "Degree to which a product or system defends against attack patterns by malicious actors and protects information and data so that persons or other products or systems have the degree of data access appropriate to their types and levels of authorization. This characteristic is composed of the following sub-characteristics.\n**产品或系统防范恶意行为者攻击模式，保护信息和数据，以确保各方（人或其他产品、系统）对数据的访问权限与其授权类型和级别相适应。该特性由以下子特性组成。**\n\n- **Confidentiality / 保密性**\nThe degree to which a product or system ensures that data are accessible only to those authorized to have access.\n**产品或系统确保数据仅对授权访问的人员可用的程度。**\n- **Integrity / 完整性**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::811", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/⑤ **Quality** attribute scenarios/Chapter 12 Other Quality attributes / 其他质量属性/**Security / 安全性**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 688, "text": "essible only to those authorized to have access.\n**产品或系统确保数据仅对授权访问的人员可用的程度。**\n- **Integrity / 完整性**\n Degree to which a system, product, or component ensures that the state of its system and data are protected from unauthorized modification or deletion, either by malicious action or computer error.\n**系统、产品或组件确保其系统和数据的状态不受未经授权的修改或删除（无论是恶意行为还是计算机错误）影响的程度。**\n- **Non-repudiation / 不可否认性**\n Degree to which actions or events can be proven to have taken place so that the events or actions cannot be repudiated later.\n**能够证明某些行为或事件已经发生，以确保这些行为或事件无法被事后否认的程度。**\n- **Accountability / 责任追踪**\n Degree to which the actions of an entity can be traced uniquely to the entity.\n**实体的行为能够被唯一追踪到该实体的程度。**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::812", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/⑤ **Quality** attribute scenarios/Chapter 12 Other Quality attributes / 其他质量属性/**Security / 安全性**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 405, "text": "ee to which the actions of an entity can be traced uniquely to the entity.\n**实体的行为能够被唯一追踪到该实体的程度。**\n- **Authenticity / 真实性**\n Degree to which the identity of a subject or resource can be proved to be the one claimed.\n**能够证明某个主体或资源的身份确实是其所声称的身份的程度。**\n- **Resistance / 抵抗力**\n Degree to which the product or system sustains operations while under attack from a malicious actor.\n**产品或系统在遭遇恶意行为者攻击时仍能持续运作的程度。**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::813", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/⑤ **Quality** attribute scenarios/Chapter 12 Other Quality attributes / 其他质量属性/**Maintainability / 可维护性**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 685, "text": "This characteristic represents the degree of effectiveness and efficiency with which a product or system can be modified to improve it, correct it, or adapt it to changes in environment, and in requirements. This characteristic is composed of the following sub-characteristics.\n**该特性代表产品或系统在提高、修正或适应环境变化及需求变化方面的有效性和效率。该特性由以下子特性组成。**\n\n- **Modularity / 模块化**\n Degree to which a system or computer program is composed of discrete components such that a change to one component has minimal impact on other components.\n**系统或计算机程序由离散组件组成，某个组件的变更对其他组件的影响最小的程度。**\n- **Reusability / 可重用性**\n Degree to which a product can be used as an asset in more than one system, or in building other assets."}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::814", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/⑤ **Quality** attribute scenarios/Chapter 12 Other Quality attributes / 其他质量属性/**Maintainability / 可维护性**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 689, "text": "ee to which a product can be used as an asset in more than one system, or in building other assets.\n**产品在多个系统中作为资产使用，或用于构建其他资产的程度。**\n- **Analysability / 可分析性**\n Degree of effectiveness and efficiency with which it is possible to assess the impact on a product or system of an intended change to one or more of its parts, or diagnose a product for deficiencies or causes of failures, or to identify parts to be modified.\n**有效且高效地评估某一部分变更对产品或系统的影响，诊断产品缺陷或故障原因，或识别需要修改的部分的程度。**\n- **Modifiability / 可修改性**\n Degree to which a product or system can be effectively and efficiently modified without introducing defects or degrading existing product quality.\n**产品或系统可以有效且高效地修改而不会引入缺陷或降低现有产品质量的程度。**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::815", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/⑤ **Quality** attribute scenarios/Chapter 12 Other Quality attributes / 其他质量属性/**Maintainability / 可维护性**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 368, "text": "introducing defects or degrading existing product quality.\n**产品或系统可以有效且高效地修改而不会引入缺陷或降低现有产品质量的程度。**\n- **Testability / 可测试性**\n Degree of effectiveness and efficiency with which test criteria can be established for a system, product, or component and tests can be performed to determine whether those criteria have been met.\n**为系统、产品或组件建立测试标准并执行测试，验证是否满足这些标准的有效性和效率的程度。**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::816", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/⑤ **Quality** attribute scenarios/Chapter 12 Other Quality attributes / 其他质量属性/**Flexibility / 灵活性**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 675, "text": "Degree to which a product can be adapted to changes in its requirements, contexts of use, or system environment. This characteristic is composed of the following sub-characteristics.\n**产品能够适应其需求、使用情境或系统环境变化的能力。该特性由以下子特性组成。**\n\n- **Adaptability / 适应性**\n Degree to which a product or system can effectively and efficiently be adapted for or transferred to different hardware, software, or other operational or usage environments.\n**产品或系统有效且高效地适应或迁移到不同硬件、软件或其他操作/使用环境的程度。**\n- **Scalability / 可扩展性**\n Degree to which a product can handle growing or shrinking workloads or to adapt its capacity to handle variability.\n**产品处理不断增长或缩小的工作负载，或根据变化调整其容量的能力。**\n- **Installability / 可安装性**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::817", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/⑤ **Quality** attribute scenarios/Chapter 12 Other Quality attributes / 其他质量属性/**Flexibility / 灵活性**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 468, "text": "its capacity to handle variability.\n**产品处理不断增长或缩小的工作负载，或根据变化调整其容量的能力。**\n- **Installability / 可安装性**\n Degree of effectiveness and efficiency with which a product or system can be successfully installed and/or uninstalled in a specified environment.\n**产品或系统在特定环境中成功安装和/或卸载的有效性和效率程度。**\n- **Replaceability / 可替换性**\n Degree to which a product can replace another specified software product for the same purpose in the same environment.\n**产品能够在相同环境下，替代另一个指定软件产品以实现相同目的的程度。**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::818", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/⑤ **Quality** attribute scenarios/Chapter 12 Other Quality attributes / 其他质量属性/**Safety / 安全性**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 688, "text": "This characteristic represents the degree to which a product, under defined conditions, avoids a state in which human life, health, property, or the environment is endangered. This characteristic is composed of the following sub-characteristics.\n\n该特性代表产品在特定条件下，避免进入可能危及人类生命、健康、财产或环境的状态的能力。该特性由以下子特性组成。\n\n- **Operational Constraint / 操作约束**\nDegree to which a product or system constrains its operation to within safe parameters or states when encountering operational hazards.\n当遇到操作风险时，产品或系统将其操作约束在安全参数或状态范围内的程度。\n- **Risk Identification / 风险识别**\nDegree to which a product can identify a course of events or operations that can expose life, property, or the environment to unacceptable risk."}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::819", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/⑤ **Quality** attribute scenarios/Chapter 12 Other Quality attributes / 其他质量属性/**Safety / 安全性**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 637, "text": "se of events or operations that can expose life, property, or the environment to unacceptable risk.\n产品能够识别可能将生命、财产或环境暴露于不可接受风险的事件或操作过程的能力。\n- **Fail-Safe / 故障安全**\nDegree to which a product can automatically place itself in a safe operating mode, or revert to a safe condition in the event of a failure.\n在发生故障时，产品能够自动将自身置于安全操作模式，或恢复到安全状态的能力。\n- **Hazard Warning / 危险警告**\nDegree to which a product or system provides warnings of unacceptable risks to operations or internal controls so that they can react in sufficient time to sustain safe operations.\n产品或系统能够及时提供关于操作或内部控制不可接受风险的警告，从而使其能够在足够的时间内做出反应，维持安全操作的能力。\n- **Safe Integration / 安全集成**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::820", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/The types, concepts, and tactics of QAs. / 质量属性的类型、概念和策略。/⑤ **Quality** attribute scenarios/Chapter 12 Other Quality attributes / 其他质量属性/**Safety / 安全性**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 234, "text": "perations.\n产品或系统能够及时提供关于操作或内部控制不可接受风险的警告，从而使其能够在足够的时间内做出反应，维持安全操作的能力。\n- **Safe Integration / 安全集成**\nDegree to which a product can maintain safety during and after integration with one or more components.\n在与一个或多个组件集成过程中及之后，产品能够维持安全的能力。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::821", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Architectural Patterns. / 架构模式", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 691, "text": "An **architectural pattern** presents the element types and their forms of interaction used in solving a particular problem.\n\n一个架构模式展示了解决特定问题时所使用的元素类型及其交互方式。\n\nA common module type pattern is the **Layered pattern.**\n\n一种常见的模块类型模式是分层模式。\n\n- When the usage of software elements is strictly unidirectional, a system of layers emerges\n当软件元素之间的使用关系严格单向时，层次系统便会出现\n- A layer is a coherent set of related functionality.\n一层是一个相关功能的连贯集合。\n- **Module type pattern - 模块类型模式**\n\n - Layered pattern - 分层模式\n- **Component-and-connector type pattern - 组件与连接器类型模式**\n\n - Shared data pattern - 共享数据模式\n - Client and server pattern - 客户端和服务器模式\n - Peer to peer pattern - 对等模式\n- **Allocation type pattern - 分配类型模式**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::822", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Architectural Patterns. / 架构模式", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 195, "text": "server pattern - 客户端和服务器模式\n - Peer to peer pattern - 对等模式\n- **Allocation type pattern - 分配类型模式**\n\n - Multi-tier pattern - 多层模式\n - Competence center pattern - 能力中心模式\n - Platform pattern - 平台模式"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::823", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Architectural Patterns. / 架构模式/① **P2P**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 182, "text": "definition, basic concepts, related QAs (e.g., availability and performance), weaknesses (how to improve?), strengths, and trade-offs.\n\nP2P的定义、基本概念、相关质量属性（例如，可用性和性能）、弱点（如何改进？）、优势和权衡。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::824", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Architectural Patterns. / 架构模式/① **P2P**/Peer-to-Peer model / 对等模式", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 476, "text": "- Each node can be publisher, subscriber or broker. / 每个节点可以是发布者、订阅者或代理。\n- Subscribers subscribe to publishers directly and publishers notify subscribers directly. Therefore, they must maintain knowledge of each other. / 订阅者直接订阅发布者，发布者也直接通知订阅者。因此，它们必须彼此保持知晓。\n- Complex in nature, mechanisms such as DHT and CHORD are employed to locate nodes in the network. / 本质上较为复杂，像 DHT 和 CHORD 这样的机制被用来定位网络中的节点。\n- E.g., Java distributed event service. / 例如，Java 分布式事件服务。\n\n**Problem / 问题**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::825", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Architectural Patterns. / 架构模式/① **P2P**/Peer-to-Peer model / 对等模式", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 696, "text": "ORD 这样的机制被用来定位网络中的节点。\n- E.g., Java distributed event service. / 例如，Java 分布式事件服务。\n\n**Problem / 问题**\n\n- How can a set of “equal” distributed computational entities be connected to each other via a common protocol, such that they can organize and share their services with high availability and scalability? / 如何通过一个通用协议将一组“平等”的分布式计算实体连接在一起，使它们能够以高可用性和可扩展性组织和共享服务？\n\n**Solution / 解决方案**\n\n- In the peer-to-peer (P2P) pattern, components directly interact as peers. All peers are “equal”. Peer-to-peer communication is typically a request/reply interaction **without the asymmetry found** in the client-server pattern. / 在对等模式（P2P）中，组件作为对等体直接进行交互。所有对等体都是“平等”的。对等通信通常是一个请求/回复的交互方式，**没有客户端-服务器模式中的不对称性。**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::826", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Architectural Patterns. / 架构模式/① **P2P**/Peer-to-Peer model / 对等模式", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 388, "text": "erver pattern. / 在对等模式（P2P）中，组件作为对等体直接进行交互。所有对等体都是“平等”的。对等通信通常是一个请求/回复的交互方式，**没有客户端-服务器模式中的不对称性。**\n\n**Weaknesses / 弱点**\n\n- Managing data consistency, data/service availability, backup, and recovery are all more complex. / 数据一致性、数据/服务可用性、备份和恢复的管理都更为复杂。\n- Small peer-to-peer systems may not be able to achieve quality goals such as performance and availability. / 小型对等系统可能无法达到诸如性能和可用性等质量目标。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::827", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Architectural Patterns. / 架构模式/② **MapReduce**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 678, "text": "definition, basic concepts, related QAs (e.g., availability and performance), weaknesses (how to improve?), strengths, and trade-offs.\n\nMapReduce的定义、基本概念、相关质量属性（例如，可用性和性能）、弱点（如何改进？）、优势和权衡。\n\n**Origin from Google, [OSDl'04] A simple programming model. / 起源于Google，[OSDl'04] 一个简单的编程模型。**\n\n- For large-scale data processing. / 用于大规模数据处理。\n- Exploits large set of commodity computers. / 利用大量商用计算机。\n- Executes the process in a distributed manner. / 以分布式方式执行过程。\n- Offers high availability. / 提供高可用性。\n\n\n\n\n\n\n\n**Map: / 映射：**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::828", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Architectural Patterns. / 架构模式/② **MapReduce**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 623, "text": "bb5JWhomLroxNTsWcVmsYndb)\n\n\n\n**Map: / 映射：**\n\n- Accepts input key/value pair. / 接受输入的键/值对。\n- Emits intermediate key/value pair. / 发出中间键/值对。\n\n**Reduce: / 归约：**\n\n- Accepts intermediate key/value pair. / 接受中间键/值对。\n- Emits output key/value pair. / 发出输出的键/值对。\n\n\n\n**Functions in the Model / 模型中的函数**\n\n**Map / 映射**\n\n- Process a key/value pair to generate intermediate key/value pairs. / 处理键/值对以生成中间键/值对。\n\n**Reduce / 归约**\n\n- Merge all intermediate values associated with the same key. / 合并所有与相同键相关的中间值。\n\n**Partition / 分区**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::829", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Architectural Patterns. / 架构模式/② **MapReduce**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 291, "text": "Merge all intermediate values associated with the same key. / 合并所有与相同键相关的中间值。\n\n**Partition / 分区**\n\n- By default: hash(key) mod R — Well balanced. / 默认情况下：hash(key) mod R — 良好平衡。\n\n\n\n"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::830", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Architectural Patterns. / 架构模式/③ **Pipe-and-Filter**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 185, "text": "definition, basic concepts, related QAs (e.g., availability and performance), weaknesses (how to improve?), strengths, and trade-offs.\n\n管道与过滤器的定义、基本概念、相关质量属性（例如，可用性和性能）、弱点（如何改进？）、优势和权衡。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::831", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Architectural Patterns. / 架构模式/③ **Pipe-and-Filter**/**Pipe and Filter Pattern** / 管道与过滤器模式", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 478, "text": "**Context:** Streaming data processing / 背景：流数据处理\n\n**Problem:** How to speed up data processing? / 问题：如何加速数据处理？\n\n**Solution:** Data arrives at a filter's input port, is transformed, and then is passed via its output port through a pipe to the next filter. / 解决方案：数据到达过滤器的输入端口后，进行转换，然后通过其输出端口通过管道传递到下一个过滤器。\n\nA single filter can consume data from, or produce data to, one or more ports. / 单个过滤器可以从一个或多个端口消费数据，或向一个或多个端口输出数据。\n\n"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::832", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Architectural Patterns. / 架构模式/③ **Pipe-and-Filter**/**Pipe and Filter Solution / 管道与过滤器解决方案**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 590, "text": "**Elements / 元素：**\n\n- Filter: A component that transforms data read on its input port to data written on its output port. / 过滤器：一个组件，将从输入端口读取的数据转换为写入输出端口的数据。\n- Pipe: A connector that conveys data from a filter's output port to another filter's input port. / 管道：一个连接器，将数据从过滤器的输出端口传送到另一个过滤器的输入端口。\n\n**Relations / 关系：**\n\n- The attachment relation associates the output of filters with the input of pipes and vice versa. / 附着关系将过滤器的输出与管道的输入关联起来，反之亦然。\n\n**Constraints / 限制：**\n\n- Connected filters must agree on the type of data being passed along the connecting pipe. / 连接的过滤器必须就通过连接管道传递的数据类型达成一致。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::833", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Architectural Patterns. / 架构模式/④ **Pub/Sub**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 683, "text": "definition, basic concepts, related QAs (e.g., availability and performance), weaknesses (how to improve?), strengths, and trade-offs.\n\n发布/订阅的定义、基本概念、相关质量属性（例如，可用性和性能）、弱点（如何改进？）、优势和权衡。\n\n**Publish-Subscribe Pattern / 发布-订阅模式**\n\nProblem: To transmit messages among the producers and consumers so they are unaware of each other's identity, or even their existence? / 问题：如何在生产者和消费者之间传递消息，使它们互不知晓对方的身份，甚至是存在？\n\n**Advantages of Pub/Sub / 发布-订阅的优点**\n\n- Highly suited for mobile applications, ubiquitous computing and distributed embedded systems. / 非常适合用于移动应用、普适计算和分布式嵌入式系统。\n- Robust - Failure of publishers or subscribers does not bring down the entire system. / 强健性 - 发布者或订阅者的失败不会导致整个系统崩溃。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::834", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Architectural Patterns. / 架构模式/④ **Pub/Sub**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 667, "text": "e of publishers or subscribers does not bring down the entire system. / 强健性 - 发布者或订阅者的失败不会导致整个系统崩溃。\n- Scalability - Suited to build distributed applications consisting of a large number of entities. / 可扩展性 - 适用于构建由大量实体组成的分布式应用。\n\n**Disadvantages of Pub/Sub / 发布-订阅的缺点**\n\n- Reliability - No strong guarantee on broker to deliver content to subscriber. After a publisher publishes the event, it assumes that all corresponding subscribers will receive it. / 可靠性 - 经纪人无法强有力地保证将内容传递给订阅者。在发布者发布事件后，它假设所有相关订阅者都会接收到事件。\n- Potential bottleneck in brokers when subscribers and publishers overload them. (Solve by load balancing techniques) / 当订阅者和发布者过载时，经纪人可能成为潜在的瓶颈。（通过负载均衡技术解决）"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::835", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Architectural Patterns. / 架构模式/④ **Pub/Sub**/**Introduction: Motivations for Pub/Sub mode / 引言：发布-订阅模式的动机**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 630, "text": "**Traditional Client/Server communication mode / 传统的客户端/服务器通信模式**\n\n(Employs RPC, message queue etc.) / （使用RPC、消息队列等）\n\n- Synchronous, tightly-coupled request invocations. / 同步的、紧耦合的请求调用。\n- Very restrictive for distributed applications, especially for WAN and mobile environments. / 对于分布式应用，尤其是在广域网和移动环境中，非常有限制。\n- When nodes/links fail, the system is affected. Fault tolerance must be built in to support this. / 当节点/链路发生故障时，系统会受到影响，必须构建容错机制来支持此情况。\n\n**Require a more flexible and de-coupled communication style that offers asynchronous mechanisms. / 需要一种更灵活、更松耦合的通信方式，提供异步机制。**\n\n**What is a Publish/Subscribe System? / 什么是发布/订阅系统？**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::836", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Architectural Patterns. / 架构模式/④ **Pub/Sub**/**Introduction: Motivations for Pub/Sub mode / 引言：发布-订阅模式的动机**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 507, "text": "s mechanisms. / 需要一种更灵活、更松耦合的通信方式，提供异步机制。**\n\n**What is a Publish/Subscribe System? / 什么是发布/订阅系统？**\n\n- **Pub/Sub System** is a communication paradigm that allows freedom in the (distributed) system by the decoupling of communication entities in terms of time, space, and synchronization. / 发布/订阅系统是一种通信范式，通过在时间、空间和同步方面解耦通信实体，为（分布式）系统提供灵活性。\n- An event service system that is asynchronous, anonymous, and loosely coupled. / 一个异步、匿名和松耦合的事件服务系统。\n- Ability to quickly adapt to a dynamic environment. / 能够快速适应动态环境。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::837", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Architectural Patterns. / 架构模式/④ **Pub/Sub**/**Key components of Pub/Sub System / 发布/订阅系统的关键组件**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 557, "text": "- **Publishers:** Publishers generate event data and publish them. / 发布者：发布者生成事件数据并将其发布。\n- **Subscribers:** Subscribers submit their subscriptions and process the events received. / 订阅者：订阅者提交订阅并处理接收到的事件。\n- **P/S service:** It's the mediator/broker that filters and routes events from publishers to interested subscribers. / 发布/订阅服务：它是中介/经纪人，负责过滤并将事件从发布者路由到感兴趣的订阅者。\n\n\n\n**Provides decoupling in time, space and synchronization.**\n\n提供时间、空间和同步方面的解耦。\n\n"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::838", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Architectural Patterns. / 架构模式/④ **Pub/Sub**/**Classification of Pub/Sub Architectures / 发布/订阅架构的分类**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 538, "text": "**Centralized Broker mode / 集中式经纪人模式**\n\n- Consists of multiple publishers and multiple subscribers and centralized broker/brokers (an overlay network of brokers interacting with each other). / 包含多个发布者和多个订阅者，以及一个或多个集中式经纪人（经纪人之间相互交互的叠加网络）。\n- Subscribers/Publishers will contact 1 broker and do not need to have knowledge about others. / 订阅者/发布者将联系一个经纪人，并不需要了解其他经纪人。\n- E.g. CORBA event services, JMS etc... / 例如，CORBA 事件服务、JMS 等。\n\n• **Peer-to-Peer model / P2P 模型**\n\n– Each node can be publisher, subscriber or broker. / 每一个节点都可以是发布者、订阅者或者经纪人"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::839", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Architectural Patterns. / 架构模式/④ **Pub/Sub**/**Classification of Pub/Sub Architectures / 发布/订阅架构的分类**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 672, "text": "Peer model / P2P 模型**\n\n– Each node can be publisher, subscriber or broker. / 每一个节点都可以是发布者、订阅者或者经纪人\n\n– Subscribers subscribe to publishers directly and publishers notify subscribers directly. Therefore, they must maintain knowledge of each other. / 订阅者直接订阅发布者（的消息），并且发布者直接注意订阅者的消息。因此，他们必须对彼此保持联系\n\n– Complex in nature, mechanisms such as DHT and CHORD are employed to locate nodes in the network. / 实际上非常难，所以采用了 DHT 和 CHORD 等策略去定位网络上的节点。\n\n– E.g. Java distributed event service / 例子：Java 的分布式时间服务（Eureka？）\n\n**Event filtering (event selection) / 事件过滤（事件选择）**\n\n- The process of selecting the set of subscribers that have shown interest in a given event. / 选择对给定事件表示兴趣的订阅者集的过程。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::840", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Architectural Patterns. / 架构模式/④ **Pub/Sub**/**Classification of Pub/Sub Architectures / 发布/订阅架构的分类**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 424, "text": "selecting the set of subscribers that have shown interest in a given event. / 选择对给定事件表示兴趣的订阅者集的过程。\n- Subscriptions are stored in memory and searched when a publisher publishes a new event. / 订阅信息存储在内存中，在发布者发布新事件时进行检索。\n\n**Event routing (event delivery) / 事件路由（事件传递）**\n\n- The process of routing the published events to all interested subscribers. / 将发布的事件路由到所有感兴趣的订阅者的过程。\n\n**Event Filtering (Subscription Model) / 事件过滤（订阅模型）**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::841", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Architectural Patterns. / 架构模式/④ **Pub/Sub**/**Topic based VS Content based / 基于主题 vs 基于内容**/**Topic based / 基于主题**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 347, "text": "- Generally also known as topic based, group based, or channel based event filtering. / 通常也被称为基于主题、基于组或基于频道的事件过滤。\n- Each event is published to one of these channels by its publisher. / 每个事件由发布者发布到这些频道之一。\n- Subscribers subscribe to a particular channel and will receive ALL events published to the subscribed channel. / 订阅者订阅特定的频道，并将接收到发布到该频道的所有事件。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::842", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Architectural Patterns. / 架构模式/④ **Pub/Sub**/**Topic based VS Content based / 基于主题 vs 基于内容**/**Content-based Subscription / 基于内容的订阅**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 169, "text": "- Added complexity in matching an event to subscriptions. / 在将事件与订阅匹配时增加了复杂性。\n- However, more precision is provided and event routing is easier. / 然而，提供了更高的精确度，事件路由也更容易。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::843", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Architectural Patterns. / 架构模式/④ **Pub/Sub**/**Advantages of Pub/Sub / 发布/订阅的优点**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 522, "text": "- Highly suited for mobile applications, ubiquitous computing, and distributed embedded systems. / 非常适合用于移动应用、普适计算和分布式嵌入式系统。\n- Robust - Failure of publishers or subscribers does not bring down the entire system. / 强健性 - 发布者或订阅者的失败不会导致整个系统崩溃。\n- Scalability - Suited to build distributed applications consisting of a large number of entities. / 可扩展性 - 适用于构建由大量实体组成的分布式应用。\n- Adaptability - Can be varied to suit different environments (mobile, internet games, embedded systems, etc.). / 适应性 - 可以根据不同的环境（如移动、互联网游戏、嵌入式系统等）进行调整。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::844", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Architectural Patterns. / 架构模式/④ **Pub/Sub**/**Disadvantages of Pub/Sub / 发布/订阅的缺点**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 397, "text": "- Reliability - No strong guarantee on broker to deliver content to subscriber. After a publisher publishes the event, it assumes that all corresponding subscribers will receive it. / 可靠性 - 经纪人无法强有力地保证将内容传递给订阅者。在发布者发布事件后，它假设所有相关订阅者都会接收到事件。\n- Potential bottleneck in brokers when subscribers and publishers overload them. (Solve by load balancing techniques) / 当订阅者和发布者过载时，经纪人可能成为潜在的瓶颈。（通过负载均衡技术解决）"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::845", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Architectural Patterns. / 架构模式/⑤ **MVC's**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 197, "text": "definition, basic concepts, related QAs (e.g., availability and performance) weaknesses (how to improve?), strengths, and trade-offs\n\nMVC的定义、基本概念、相关质量属性（例如，可用性和性能）、弱点（如何改进？）、优势和权衡。\n\n以下是按照要求格式进行的翻译："}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::846", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Architectural Patterns. / 架构模式/⑤ **MVC's**/**Model-View-Controller Pattern / 模型-视图-控制器模式**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 576, "text": "**Context / 背景**\n\nUser interface software is the most frequently modified portion of an interactive application. / 用户界面软件是交互式应用程序中最频繁修改的部分。\n\n**Problem / 问题**\n\nHow can user interface functionality be kept separate from application functionality and yet still be responsive to user input, or to changes in the underlying application's data? And how can multiple views of the user interface be created, maintained, and coordinated when the underlying application data changes? / 如何将用户界面功能与应用程序功能分离，同时仍能响应用户输入或底层应用程序数据的变化？以及当底层应用程序数据发生变化时，如何创建、维护和协调多个用户界面的视图？\n\n**Solution / 解决方案**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::847", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Architectural Patterns. / 架构模式/⑤ **MVC's**/**Model-View-Controller Pattern / 模型-视图-控制器模式**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 634, "text": "将用户界面功能与应用程序功能分离，同时仍能响应用户输入或底层应用程序数据的变化？以及当底层应用程序数据发生变化时，如何创建、维护和协调多个用户界面的视图？\n\n**Solution / 解决方案**\n\nThe model-view-controller (MVC) pattern separates application functionality into three kinds of components: / 模型-视图-控制器（MVC）模式将应用程序功能分为三种组件：\n\n- **A model** which contains the application's data. / 模型，包含应用程序的数据。\n- **A view,** which displays some portion of the underlying data and interacts with the user**.** / 视图，显示底层数据的某一部分并与用户交互。\n- **A controller,** which mediates between the model and the view and manages the notifications of state changes. / 控制器，作为模型和视图之间的中介，并管理状态变化的通知。\n\n"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::848", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Architectural Patterns. / 架构模式/⑤ **MVC's**/MVC Solution / MVC 解决方案", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 234, "text": "**Constraints / 限制：**\n\n- There must be at least one instance for each model, view, and controller. / 每个模型、视图和控制器必须至少有一个实例。\n\n**Weaknesses / 弱点：**\n\n- The complexity may not be worth it for simple user interfaces. / 对于简单的用户界面，这种复杂性可能不值得。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::849", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Architectural Patterns. / 架构模式/⑤ **MVC's**/批注：Java Go Python 的 MVC 应用（感兴趣的同学可自行去框架官方文档处学习）", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 146, "text": "Java：https://docs.spring.io/spring-framework/reference/web/webmvc.html\n\nGo：https://revel.github.io/\n\nPython：https://docs.djangoproject.com/en/5.1/"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::850", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/**ATAM (architectural reasons), participants' roles, and the usage of Utility Tree, along with the definition, concepts, and steps (procedure) of ATAM, ASRs, ADD, and Utility Tree, are all key components in the evaluation process.**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 71, "text": "ATAM（架构原因）、参与者的角色和效用树的使用，以及ATAM、ASR、ADD和效用树的定义、概念和步骤（程序）都是评估过程中的关键组成部分。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::851", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/**ATAM (architectural reasons), participants' roles, and the usage of Utility Tree, along with the definition, concepts, and steps (procedure) of ATAM, ASRs, ADD, and Utility Tree, are all key components in the evaluation process.**/**The Architecture Tradeoff Analysis Method (ATAM) / 架构权衡分析方法（ATAM）**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 429, "text": "- The ATAM has been used for over a decade to evaluate software architectures in domains ranging from automotive to financial to defense. / ATAM 已经被用于超过十年的时间，评估涵盖从汽车到金融到国防等领域的软件架构。\n- The ATAM is designed so that evaluators need not be familiar with the architecture or its business goals, the system need not yet be constructed, and there may be a large number of stakeholders. / ATAM 的设计使得评估人员无需熟悉架构或其业务目标，系统可能尚未构建，且可能涉及大量利益相关者。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::852", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/**ATAM (architectural reasons), participants' roles, and the usage of Utility Tree, along with the definition, concepts, and steps (procedure) of ATAM, ASRs, ADD, and Utility Tree, are all key components in the evaluation process.**/**The Architecture Tradeoff Analysis Method (ATAM) / 架构权衡分析方法（ATAM）**/Primary Outputs of the ATAM / ATAM 的主要输出", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 569, "text": "**A set of risks and nonrisks / 一组风险和非风险**\n\n- A **risk** is defined as an architectural decision that may lead to undesirable consequences in light of quality attribute requirements. / 风险被定义为一种架构决策，可能导致在质量属性要求下的 undesirable 后果。\n- A **nonrisk** is an architectural decision that is deemed safe. / 非风险是被认为是安全的架构决策。\n\n**A set of risk themes / 一组风险主题**\n\n- Examines the full set of risks to look for themes that identify **system weaknesses** in the architecture. / 检查所有风险，寻找能够识别架构中系统弱点的主题。\n- These risk themes will threaten the project's business goals. / 这些风险主题将威胁到项目的业务目标。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::853", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/**ATAM (architectural reasons), participants' roles, and the usage of Utility Tree, along with the definition, concepts, and steps (procedure) of ATAM, ASRs, ADD, and Utility Tree, are all key components in the evaluation process.**/**The Architecture Tradeoff Analysis Method (ATAM) / 架构权衡分析方法（ATAM）**/Other Outputs of the ATAM / ATAM 的其他输出", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 492, "text": "1. A concise **presentation of the architecture** / 架构的简洁展示\n2. Articulation of the business goals / 明确表达业务目标\n3. **Prioritized** quality attribute requirements expressed as quality attribute scenarios / 按优先级排列的质量属性要求，以质量属性场景的形式表达\n4. **Mapping** of architectural decisions to quality requirements / 将架构决策与质量要求进行映射\n5. A set of identified sensitivity and **tradeoff points**: architectural decisions that have a marked effect on one or more quality attributes / 一组已识别的敏感性和权衡点：对一个或多个质量属性有显著影响的架构决策"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::854", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/**ATAM (architectural reasons), participants' roles, and the usage of Utility Tree, along with the definition, concepts, and steps (procedure) of ATAM, ASRs, ADD, and Utility Tree, are all key components in the evaluation process.**/**The Architecture Tradeoff Analysis Method (ATAM) / 架构权衡分析方法（ATAM）**/Phases and Steps of ATAM / ATAM 的步骤与阶段", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 700, "text": "**Step 1: Present the ATAM / 步骤1：介绍ATAM**\n\n- \"The evaluation leader describes the ATAM steps in brief and the outputs of the evaluation.\" / 评估领导简要描述ATAM的步骤以及评估结果。\n\n**Step 2: Present Business Drivers / 步骤2：介绍业务驱动因素**\n\n- \"The project decision maker (ideally the project manager or the system's customer) presents a system overview from a business perspective.\" / 项目决策者（理想情况下是项目经理或系统客户）从业务角度介绍系统概览。\n- \"The presentation should describe: important functions, relevant technical, managerial, economic, or political constraints, business goals and context, major stakeholders, architectural drivers (architecturally significant requirements).\" / 演示应描述：重要功能、相关的技术、管理、经济或政治约束、业务目标和背景、主要利益相关者、架构驱动因素（架构上重要的需求）。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::855", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/**ATAM (architectural reasons), participants' roles, and the usage of Utility Tree, along with the definition, concepts, and steps (procedure) of ATAM, ASRs, ADD, and Utility Tree, are all key components in the evaluation process.**/**The Architecture Tradeoff Analysis Method (ATAM) / 架构权衡分析方法（ATAM）**/Phases and Steps of ATAM / ATAM 的步骤与阶段", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 651, "text": "cturally significant requirements).\" / 演示应描述：重要功能、相关的技术、管理、经济或政治约束、业务目标和背景、主要利益相关者、架构驱动因素（架构上重要的需求）。\n\n**Step 3: Present the Architecture / 步骤3：介绍架构**\n\n- \"The lead architect makes a presentation describing the architecture.\" / 首席架构师进行架构描述的演示。\n- \"Technical constraints such as operating system, hardware, or middleware prescribed for use, and other systems with which the system must interact.\" / 描述操作系统、硬件或指定使用的中间件等技术约束，以及系统必须交互的其他系统。\n- \"Architectural approaches, i.e., patterns & tactics used to meet the requirements.\" / 架构方法，即用于满足需求的模式和策略。\n- \"Should convey the essence of the architecture and NOT go too deeply into the details.\" / 应传达架构的精髓，而不是深入细节。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::856", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/**ATAM (architectural reasons), participants' roles, and the usage of Utility Tree, along with the definition, concepts, and steps (procedure) of ATAM, ASRs, ADD, and Utility Tree, are all key components in the evaluation process.**/**The Architecture Tradeoff Analysis Method (ATAM) / 架构权衡分析方法（ATAM）**/Phases and Steps of ATAM / ATAM 的步骤与阶段", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 700, "text": "onvey the essence of the architecture and NOT go too deeply into the details.\" / 应传达架构的精髓，而不是深入细节。\n\n**Step 4: Identify Architectural Approaches / 步骤4：识别架构方法**\n\n- \"Understand its architectural approaches, especially patterns and tactics.\" / 了解架构方法，特别是模式和策略。\n- \"The evaluation team catalogs the patterns and tactics that have been identified. The list is publicly captured and will serve as the basis for later analysis.\" / 评估团队对已识别的模式和策略进行分类。该列表会公开记录，并作为后续分析的基础。\n\n**Step 5: Generate Utility Tree / 步骤5：生成效用树**\n\n- \"The evaluation team works with the project decision makers to identify, prioritize, and refine the system's most important quality attribute goals.\" / 评估团队与项目决策者合作，识别、优先排序并完善系统最重要的质量属性目标。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::857", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/**ATAM (architectural reasons), participants' roles, and the usage of Utility Tree, along with the definition, concepts, and steps (procedure) of ATAM, ASRs, ADD, and Utility Tree, are all key components in the evaluation process.**/**The Architecture Tradeoff Analysis Method (ATAM) / 架构权衡分析方法（ATAM）**/Phases and Steps of ATAM / ATAM 的步骤与阶段", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 684, "text": "refine the system's most important quality attribute goals.\" / 评估团队与项目决策者合作，识别、优先排序并完善系统最重要的质量属性目标。\n- \"The quality attribute goals are articulated in detail via a quality attribute utility tree.\" / 质量属性目标通过质量属性效用树详细表达。\n- \"The scenarios are assigned a rank of importance (High, Medium, Low).\" / 为场景分配重要性等级（高、中、低）。\n\n**Step 6: Analyze Architectural Approaches / 步骤6：分析架构方法**\n\n- \"The evaluation team examines the highest-ranked scenarios one at a time; the architect is asked to explain how the architecture supports each one.\" / 评估团队逐一检查排名最高的场景；架构师需要解释架构如何支持每个场景。\n- \"Evaluation team members probe for the architectural approaches used to carry out the scenario.\" / 评估团队成员探讨为执行场景所采用的架构方法。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::858", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/**ATAM (architectural reasons), participants' roles, and the usage of Utility Tree, along with the definition, concepts, and steps (procedure) of ATAM, ASRs, ADD, and Utility Tree, are all key components in the evaluation process.**/**The Architecture Tradeoff Analysis Method (ATAM) / 架构权衡分析方法（ATAM）**/Phases and Steps of ATAM / ATAM 的步骤与阶段", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 690, "text": "rs probe for the architectural approaches used to carry out the scenario.\" / 评估团队成员探讨为执行场景所采用的架构方法。\n- \"The evaluation team documents the relevant architectural decisions and identifies and catalogs their risks, nonrisks, and tradeoff points.\" / 评估团队记录相关架构决策，并识别和分类它们的风险、非风险和权衡点。\n**Examples: / 示例：**\n\n - **Risk:** The frequency of heartbeats affects the time in which the system can detect a failed component. / **风险**：心跳频率影响系统检测故障组件的时间。\n - **Tradeoff:** The heartbeat frequency determines the time for detecting a fault. Higher frequency leads to better availability but consumes more processing time and communication bandwidth (potentially reducing performance). / **权衡**：心跳频率决定检测故障的时间。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::859", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/**ATAM (architectural reasons), participants' roles, and the usage of Utility Tree, along with the definition, concepts, and steps (procedure) of ATAM, ASRs, ADD, and Utility Tree, are all key components in the evaluation process.**/**The Architecture Tradeoff Analysis Method (ATAM) / 架构权衡分析方法（ATAM）**/Phases and Steps of ATAM / ATAM 的步骤与阶段", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 549, "text": "cessing time and communication bandwidth (potentially reducing performance). / **权衡**：心跳频率决定检测故障的时间。更高的频率提高可用性，但会消耗更多的处理时间和通信带宽（可能降低性能）。\n\n**Step 7: Brainstorm and Prioritize Scenarios / 步骤7：头脑风暴并优先排序场景**\n\n- \"The purpose of scenario brainstorming is to understand what system success means for stakeholders.\" / 场景头脑风暴的目的是理解对利益相关者来说，系统成功意味着什么。\n- \"Once the scenarios have been collected, they are prioritized by voting.\" / 收集场景后，进行投票排序。\n- \"The list of prioritized scenarios is compared with those from the utility tree exercise.\" / 对比优先排序的场景与效用树活动中的场景。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::860", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/**ATAM (architectural reasons), participants' roles, and the usage of Utility Tree, along with the definition, concepts, and steps (procedure) of ATAM, ASRs, ADD, and Utility Tree, are all key components in the evaluation process.**/**The Architecture Tradeoff Analysis Method (ATAM) / 架构权衡分析方法（ATAM）**/Phases and Steps of ATAM / ATAM 的步骤与阶段", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 654, "text": "ioritized scenarios is compared with those from the utility tree exercise.\" / 对比优先排序的场景与效用树活动中的场景。\n\n - \"If they agree, it indicates good alignment between the architect had in mind and what the stakeholders actually wanted.\" / 如果一致，则表明架构师的设计和利益相关者的实际需求高度一致。\n - \"If additional driving scenarios are discovered, this may itself be a risk, some disagreement between the stakeholders and the architect.\" / 如果发现了额外的驱动场景，这本身可能就是一个风险，表示利益相关者和架构师之间存在某些分歧。\n\n**Step 8: Analyze Architectural Approaches / 步骤8：分析架构方法**\n\n- \"In this step the evaluation team performs the same activities as in step 6.\" / 在此步骤中，评估团队进行与步骤6相同的活动。\n\n**Step 9: Present Results / 步骤9：呈现结果**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::861", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/**ATAM (architectural reasons), participants' roles, and the usage of Utility Tree, along with the definition, concepts, and steps (procedure) of ATAM, ASRs, ADD, and Utility Tree, are all key components in the evaluation process.**/**The Architecture Tradeoff Analysis Method (ATAM) / 架构权衡分析方法（ATAM）**/Phases and Steps of ATAM / ATAM 的步骤与阶段", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 654, "text": "he same activities as in step 6.\" / 在此步骤中，评估团队进行与步骤6相同的活动。\n\n**Step 9: Present Results / 步骤9：呈现结果**\n\n- \"The evaluation team groups risks into risk themes based on some systemic deficiency.\" / 评估团队根据某些系统缺陷将风险分组为风险主题。\n\n - \"For example, a group of risks about the system's inability to function in the face of various hardware and/or software failures might lead to a risk theme about insufficient attention to providing high availability.\" / 例如，一组关于系统在面对各种硬件和/或软件故障时无法正常工作的问题，可能会导致一个关于对高可用性关注不足的风险主题。\n- \"For each risk theme, the evaluation team identifies which of the business drivers listed in step 2 are affected.\" / 对于每个风险主题，评估团队识别哪些在步骤2中列出的业务驱动因素受到影响。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::862", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/**ATAM (architectural reasons), participants' roles, and the usage of Utility Tree, along with the definition, concepts, and steps (procedure) of ATAM, ASRs, ADD, and Utility Tree, are all key components in the evaluation process.**/**The Architecture Tradeoff Analysis Method (ATAM) / 架构权衡分析方法（ATAM）**/Phases and Steps of ATAM / ATAM 的步骤与阶段", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 697, "text": "hich of the business drivers listed in step 2 are affected.\" / 对于每个风险主题，评估团队识别哪些在步骤2中列出的业务驱动因素受到影响。\n- \"The collected information from the evaluation is summarized and presented to stakeholders.\" / 从评估中收集到的信息将总结并呈现给利益相关者。\n- \"The following outputs are presented: / 以下输出将呈现：\\*\\*\n\n - \"The architectural approaches documented.\" / 已记录的架构方法。\n - \"The set of scenarios and their prioritization from the brainstorming.\" / 头脑风暴中收集的场景及其优先级排序。\n - \"The utility tree.\" / 效用树。\n - \"The risks discovered.\" / 发现的风险。\n - \"The nonrisks documented.\" / 记录的非风险。\n - \"The sensitivity points and tradeoff points found.\" / 发现的敏感点和权衡点。\n - \"Risk themes and the business drivers threatened by each one.\" / 风险主题及其威胁的业务驱动因素。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::863", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/**ATAM (architectural reasons), participants' roles, and the usage of Utility Tree, along with the definition, concepts, and steps (procedure) of ATAM, ASRs, ADD, and Utility Tree, are all key components in the evaluation process.**/**The Architecture Tradeoff Analysis Method (ATAM) / 架构权衡分析方法（ATAM）**/Phases and Steps of ATAM / ATAM 的步骤与阶段", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 625, "text": "发现的敏感点和权衡点。\n - \"Risk themes and the business drivers threatened by each one.\" / 风险主题及其威胁的业务驱动因素。\n\n\n\n\n\n以下是按照要求格式进行的翻译：\n\n**Lightweight Architectural Evaluation / 轻量级架构评估**\n\n- **An ATAM is a substantial undertaking. / ATAM 是一个庞大的工作量。**\n\n - \"It requires some 20 to 30 person-days of effort from an evaluation team, plus even more for the architect and stakeholders.\" / 它需要评估团队大约20到30个工作日的努力，还需要架构师和利益相关者投入更多时间。\n - \"Investing this amount of time makes sense on a large and costly project.\" / 在大型且高成本的项目中，投入这么多时间是有意义的。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::864", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/**ATAM (architectural reasons), participants' roles, and the usage of Utility Tree, along with the definition, concepts, and steps (procedure) of ATAM, ASRs, ADD, and Utility Tree, are all key components in the evaluation process.**/**The Architecture Tradeoff Analysis Method (ATAM) / 架构权衡分析方法（ATAM）**/Phases and Steps of ATAM / ATAM 的步骤与阶段", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 581, "text": "esting this amount of time makes sense on a large and costly project.\" / 在大型且高成本的项目中，投入这么多时间是有意义的。\n\n**A Lightweight Architecture Evaluation method for smaller, less risky projects. / 小型、低风险项目的轻量级架构评估方法**\n\n- \"May take place in a single day, or even a half-day meeting.\" / 评估可能在一天甚至半天的会议中完成。\n- \"May be carried out entirely by members internal to the organization.\" / 评估可以完全由组织内部成员进行。\n- \"Of course this may not probe the architecture as deeply.\" / 当然，这样的评估可能不会深入挖掘架构的细节。\n\n\n\n"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::865", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/**ATAM (architectural reasons), participants' roles, and the usage of Utility Tree, along with the definition, concepts, and steps (procedure) of ATAM, ASRs, ADD, and Utility Tree, are all key components in the evaluation process.**/Participant's Roles / 参与者的职责", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 645, "text": "**Participants in the ATAM / ATAM 参与者**\n\n**The evaluation team / 评估团队**\n\n- \"3 to 5 people.\" / 3到5人。\n- \"Competent, unbiased outsiders.\" / 能力强且公正的外部人员。\n\n**Project decision makers / 项目决策者**\n\n- \"The project manager, the architect and the customer who bill for the development.\" / 项目经理、架构师以及为开发付费的客户。\n\n**Architecture stakeholders / 架构利益相关者**\n\n- \"Developers, testers, integrators, maintainers, performance engineers, users, builders of systems.\" / 开发人员、测试人员、集成商、维护人员、性能工程师、用户、系统构建者。\n- \"To articulate the specific quality attribute goals.\" / 阐明具体的质量属性目标。\n- \"12 to 15 stakeholders for a large enterprise-critical architecture.\" / 对于大型企业关键架构，12到15个利益相关者。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::866", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/**ATAM (architectural reasons), participants' roles, and the usage of Utility Tree, along with the definition, concepts, and steps (procedure) of ATAM, ASRs, ADD, and Utility Tree, are all key components in the evaluation process.**/ASRs / 架构重要需求", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 252, "text": "- \"Not all requirements are created equal. An **Architecturally Significant Requirement (ASR)** is a requirement that will have a **profound effect** on the architecture.\" / 并非所有需求都是平等的。架构上重要的需求（ASR）是对架构有深远影响的需求。\n- \"How do we find those?\" / 我们如何找到这些需求？"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::867", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/**ATAM (architectural reasons), participants' roles, and the usage of Utility Tree, along with the definition, concepts, and steps (procedure) of ATAM, ASRs, ADD, and Utility Tree, are all key components in the evaluation process.**/ASRs / 架构重要需求/Approaches to Capture ASRs / 捕捉 ASR 的方法", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 603, "text": "- **From Requirements Document / 从需求文档中**\n\n - \"An obvious location to look for candidate ASRs is in the requirements documents.\" / 寻找候选 ASR 的明显位置是需求文档。\n - \"Unfortunately, this is not usually the case.\" / 不幸的是，这通常不是情况。\n- **Gathering ASRs from Stakeholders / 从利益相关者收集 ASR**\n\n - \"Stakeholders often have no idea what QAs they want in a system.\" / 利益相关者通常不知道他们在系统中需要哪些质量属性（QA）。\n - \"If you insist on quantitative QA requirements, you're likely to get numbers that are arbitrary.\" / 如果坚持量化的质量属性要求，您很可能得到任意的数字。\n - \"At least some of those requirements will be very difficult to satisfy.\" / 至少其中一些要求将非常难以满足。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::868", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/**ATAM (architectural reasons), participants' roles, and the usage of Utility Tree, along with the definition, concepts, and steps (procedure) of ATAM, ASRs, ADD, and Utility Tree, are all key components in the evaluation process.**/ASRs / 架构重要需求/Approaches to Capture ASRs / 捕捉 ASR 的方法", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 652, "text": "数字。\n - \"At least some of those requirements will be very difficult to satisfy.\" / 至少其中一些要求将非常难以满足。\n - \"Architects often have very good ideas about what QAs are reasonable to provide.\" / 架构师通常对哪些质量属性是合理的有很好的理解。\n - **\"Interviewing the stakeholders is the surest way to learn what they know and need.\" / 采访利益相关者是了解他们知道和需要什么的最可靠方式。**\n - \"The results of stakeholder interviews should include: / 利益相关者访谈的结果应包括：\n\n - \"A list of architectural drivers.\" / 架构驱动因素的列表。\n - \"A set of QA scenarios that the stakeholders (as a group) prioritized.\" / 利益相关者（作为一个团体）优先排序的质量属性场景。\n- **By Understanding the Business Goals / 通过理解商业目标**\n- **In Utility Tree / 从效能树中**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::869", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/**ATAM (architectural reasons), participants' roles, and the usage of Utility Tree, along with the definition, concepts, and steps (procedure) of ATAM, ASRs, ADD, and Utility Tree, are all key components in the evaluation process.**/ASRs / 架构重要需求/Summary / 总结", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 389, "text": "- \"Architectures are driven by Architecturally Significant Requirements (ASRs): requirements that will have profound effects on the architecture.\" / 架构受到架构上重要需求（ASR）的驱动：这些需求对架构有深远影响。\n- \"ASRs may be captured: / ASR 可以通过以下方式捕获：\\*\\*\n\n - \"From requirements documents.\" / 从需求文档中。\n - \"By interviewing stakeholders.\" / 通过采访利益相关者。\n - \"By conducting a Quality Attribute Workshop.\" / 通过进行质量属性研讨会。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::870", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/**ATAM (architectural reasons), participants' roles, and the usage of Utility Tree, along with the definition, concepts, and steps (procedure) of ATAM, ASRs, ADD, and Utility Tree, are all key components in the evaluation process.**/Utility Tree / 效能树", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 678, "text": "An ASR must have the following characteristics / ASR 必须具备以下特征\n\n- *A profound impact on architecture.*\n\n - Including this requirement will very likely result in a different architecture than if it were not included.\n 对架构有深远的影响。包含此需求将很可能导致与未包含时不同的架构。\n- *A high business or mission value.*\n\n - If architecture is going to satisfy this requirement, it must be of high value to important stakeholders.\n 具有高商业或使命价值。如果架构要满足此需求，它必须对重要的利益相关者具有高价值。\n- Utility Tree is A way to record ASRs all in one place. / 效能树是一种将 ASR 集中记录在一个地方的方法。\n- Establishes priority of each ASR in terms of: / 以以下方式确定每个 ASR 的优先级：\n\n - Impact on architecture. / 对架构的影响。\n - Business or mission value. / 商业或使命价值。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::871", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/**ATAM (architectural reasons), participants' roles, and the usage of Utility Tree, along with the definition, concepts, and steps (procedure) of ATAM, ASRs, ADD, and Utility Tree, are all key components in the evaluation process.**/Utility Tree / 效能树", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 447, "text": "以下方式确定每个 ASR 的优先级：\n\n - Impact on architecture. / 对架构的影响。\n - Business or mission value. / 商业或使命价值。\n- ASRs are captured as scenarios. / ASR 作为场景进行捕获。\n- **Root of tree is placeholder node called Utility. / 树的根是一个占位节点，称为 'Utility'。**\n- Second level of tree contains broad QA categories. / 第二层包含广泛的质量属性（QA）类别。\n- The third level of tree refines those categories. / 第三层细化这些类别。\n- **Leaf nodes are concrete quality attribute scenarios. / 叶节点是具体的质量属性场景。**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::872", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/**ATAM (architectural reasons), participants' roles, and the usage of Utility Tree, along with the definition, concepts, and steps (procedure) of ATAM, ASRs, ADD, and Utility Tree, are all key components in the evaluation process.**/Utility Tree / 效能树/效能树的四个层级已经固定了内容是什么：Utility — 质量属性 — 属性类别 — ASR（架构重要需求）", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::873", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/**ATAM (architectural reasons), participants' roles, and the usage of Utility Tree, along with the definition, concepts, and steps (procedure) of ATAM, ASRs, ADD, and Utility Tree, are all key components in the evaluation process.**/Utility Tree / 效能树/**Utility Tree: Next Steps / 实用性树：下一步**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 348, "text": "- \"ASRs that rate a (H,H) rating are the ones that deserve the most attention.\"\n/ 获得（高，高）评分的 ASR 是最值得关注的。\n- \"A very large number of these might be a cause for concern: Is the system achievable?\"\n/ 如果这些 ASR 的数量过多，可能会成为一个问题：系统是否可实现？\n- \"Stakeholders can review the utility tree to make sure their concerns are addressed.\"\n/ 利益相关者可以查看实用性树，确保他们的关注点得到解决。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::874", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/**ATAM (architectural reasons), participants' roles, and the usage of Utility Tree, along with the definition, concepts, and steps (procedure) of ATAM, ASRs, ADD, and Utility Tree, are all key components in the evaluation process.**/Utility Tree / 效能树/Tying the Methods Together / 将方法结合起来", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 462, "text": "- \"How should you employ requirements documents, stakeholder interviews, Quality Attribute Workshops, and utility trees together?\"\n/ 如何将需求文档、利益相关者访谈、质量属性研讨会（QAW）和实用性树结合使用？\n- \"If important stakeholders have been overlooked in the requirements-gathering process, use interviews or a QAW.\"\n/ 如果在需求收集过程中忽视了重要的利益相关者，可以使用访谈或质量属性研讨会（QAW）。\n- \"Use a quality attribute utility tree as a repository for the scenarios produced by a QAW.\"\n/ 使用质量属性实用性树作为质量属性研讨会（QAW）生成的场景的存储库。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::875", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/**ATAM (architectural reasons), participants' roles, and the usage of Utility Tree, along with the definition, concepts, and steps (procedure) of ATAM, ASRs, ADD, and Utility Tree, are all key components in the evaluation process.**/ADD/**The Attribute-Driven Design Method / 属性驱动设计方法**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 559, "text": "- \"An iterative method. At each iteration you: / 一种迭代方法。在每次迭代中，您将：\n\n - **\"Choose a part of the system to design.\" / 选择系统的某一部分进行设计。**\n - **\"Marshal all the architecturally significant requirements for that part.\" / 收集该部分的所有架构上重要的需求。**\n - **\"Generate and test a design for that part.\" / 为该部分生成并测试设计。**\n- \"ADD does not result in a complete design.\" / 属性驱动设计（ADD）不会生成完整的设计。\n- \"Set of containers with responsibilities.\" / 一组具有责任的容器。\n- \"Interactions and information flow among containers.\" / 容器之间的交互和信息流。\n- \"Does not produce an API for containers.\" / 不生成容器的 API。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::876", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/**ATAM (architectural reasons), participants' roles, and the usage of Utility Tree, along with the definition, concepts, and steps (procedure) of ATAM, ASRs, ADD, and Utility Tree, are all key components in the evaluation process.**/ADD/ADD Inputs / 属性驱动设计方法的输入", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 341, "text": "Requirements / 需求\n\n- \"Functional, quality, constraints\" / 功能性需求、质量需求、约束条件\n\nA context description / 上下文描述\n\n- \"What are the boundaries of the system being designed?\" / 被设计系统的边界是什么？\n- \"What are the external systems, devices, users, and environment conditions with which the system being designed must interact?\" / 被设计系统必须与哪些外部系统、设备、用户和环境条件进行交互？"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::877", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/**ATAM (architectural reasons), participants' roles, and the usage of Utility Tree, along with the definition, concepts, and steps (procedure) of ATAM, ASRs, ADD, and Utility Tree, are all key components in the evaluation process.**/ADD/ADD Outputs / 属性驱动设计方法的输出", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 466, "text": "Architectural elements and their relationship / 架构元素及其关系\n\n- \"Responsibility of elements\" / 元素的责任\n- \"Interactions\" / 交互\n- \"Information flow among the elements\" / 元素之间的信息流\n\n**Input: Requirements / 输入：需求**\n\n- \"Functional\" / 功能性需求\n- \"Quality\" / 质量需求\n- \"Constraints\" / 约束条件\n\nParser: ADD Process / 处理器：ADD 过程\n\n**Output: \"Containers\" / 容器**\n\n- \"Responsibilities\" / 责任\n- \"Interactions\" / 交互\n- \"Information flow\" / 信息流\n\n"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::878", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/**ATAM (architectural reasons), participants' roles, and the usage of Utility Tree, along with the definition, concepts, and steps (procedure) of ATAM, ASRs, ADD, and Utility Tree, are all key components in the evaluation process.**/ADD/The Steps of ADD 属性驱动设计方法的步骤", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 404, "text": "1. **Choose an element** of the system to design / 选择系统的一个元素进行设计\n2. **Identify the ASRs** for the chosen element. / 确定所选元素的架构上重要需求（ASRs）。\n3. **Generate a design solution** for the chosen element. / 为所选元素生成设计解决方案。\n4. **Inventory remaining requirements** and select the input for the next iteration. / 清点剩余需求并选择下一次迭代的输入。\n5. Repeat steps 1-4 until all the ASRs have been satisfied. / 重复步骤 1-4，直到所有 ASR 都已满足。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::879", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/**ATAM (architectural reasons), participants' roles, and the usage of Utility Tree, along with the definition, concepts, and steps (procedure) of ATAM, ASRs, ADD, and Utility Tree, are all key components in the evaluation process.**/ADD/The Steps of ADD 属性驱动设计方法的步骤/Step 1: Choose an Element of the System to Design / 步骤 1：选择系统的一个元素进行设计", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 655, "text": "- \"For **green field designs**, the element chosen is usually the whole system.\" / 对于全新设计（green field design），通常选择整个系统作为设计元素。\n- \"For **legacy designs**, the element is the portion to be added.\" / 对于遗留系统设计（legacy design），选择的元素是需要添加的部分。\n\n\n\n\n\n**Which Element Comes Next? / 下一个选择哪个元素？**\n\n**Two basic refinement strategies: / 两种基本的细化策略：**\n\n- \"Breadth first\" / 广度优先\n- \"Depth first\" / 深度优先\n\n**Which one to choose? / 选择哪一个？**\n\n- **If using new technology => depth first: explore the implications of using that technology. / 如果使用新技术 => 深度优先：探索使用该技术的影响。**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::880", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/**ATAM (architectural reasons), participants' roles, and the usage of Utility Tree, along with the definition, concepts, and steps (procedure) of ATAM, ASRs, ADD, and Utility Tree, are all key components in the evaluation process.**/ADD/The Steps of ADD 属性驱动设计方法的步骤/Step 1: Choose an Element of the System to Design / 步骤 1：选择系统的一个元素进行设计", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 251, "text": "=> depth first: explore the implications of using that technology. / 如果使用新技术 => 深度优先：探索使用该技术的影响。**\n- **If a team needs work => depth first: generate requirements for that team. / 如果团队需要工作 => 深度优先：为该团队生成需求。**\n- Otherwise => breadth first. / 否则 => 广度优先。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::881", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/**ATAM (architectural reasons), participants' roles, and the usage of Utility Tree, along with the definition, concepts, and steps (procedure) of ATAM, ASRs, ADD, and Utility Tree, are all key components in the evaluation process.**/ADD/The Steps of ADD 属性驱动设计方法的步骤/**Step 2: Identify the ASRs for the Chosen Element / 步骤 2：确定所选元素的架构上重要需求（ASRs）**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 298, "text": "- If the chosen element is the **whole system**, then use a **utility tree** (as described earlier). / 如果所选元素是整个系统，则使用实用性树（如前所述）。\n- If the chosen element is further down the decomposition tree, then generate a utility tree from the requirements for that element. / 如果所选元素位于分解树的更深层次，则从该元素的需求中生成实用性树。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::882", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/**ATAM (architectural reasons), participants' roles, and the usage of Utility Tree, along with the definition, concepts, and steps (procedure) of ATAM, ASRs, ADD, and Utility Tree, are all key components in the evaluation process.**/ADD/The Steps of ADD 属性驱动设计方法的步骤/Step 3: Generate a Design Solution for the Chosen Element / 步骤 3：为所选元素生成设计解决方案", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 155, "text": "- \"Apply generate and test to the chosen element with its ASRs.\" / 对所选元素及其架构上重要需求（ASRs）应用生成与测试的方法。\n\n"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::883", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/**ATAM (architectural reasons), participants' roles, and the usage of Utility Tree, along with the definition, concepts, and steps (procedure) of ATAM, ASRs, ADD, and Utility Tree, are all key components in the evaluation process.**/ADD/The Steps of ADD 属性驱动设计方法的步骤/Step 4: Select the Input for the Next Iteration / 步骤 4：选择下一次迭代的输入", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 650, "text": "- \"For each **functional requirement**: / 对每个功能性需求：\n\n - \"Ensure that the requirement has been **satisfied**.\" / 确保该需求已被满足。\n - \"If not, then add responsibilities to satisfy the requirement.\" / 如果未满足，则添加责任来满足该需求。\n - \"**Add** them to a container with similar requirements.\" / 将其添加到具有相似需求的容器中。\n - \"If no such container, may need to **create a new one** or add to a container with dissimilar responsibilities (coherence).\" / 如果没有这样的容器，则可能需要创建一个新容器，或将其添加到具有不同责任的容器中（保持一致性）。\n - \"If container has too many requirements for a team, **split** it into two portions. Try to achieve loose coupling when splitting.\" / 如果容器包含的需求对一个团队来说过多，则将其拆分为两个部分。拆分时尽量实现松耦合。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::884", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/**ATAM (architectural reasons), participants' roles, and the usage of Utility Tree, along with the definition, concepts, and steps (procedure) of ATAM, ASRs, ADD, and Utility Tree, are all key components in the evaluation process.**/ADD/Summary of ADD / 属性驱动设计方法的总结/**Designing Strategies / 设计策略**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 127, "text": "- \"Decomposition\" / 分解\n- \"Designing to Architecturally Significant Requirements\" / 根据架构上重要的需求进行设计\n- \"Generate and Test\" / 生成与测试"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::885", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/**ATAM (architectural reasons), participants' roles, and the usage of Utility Tree, along with the definition, concepts, and steps (procedure) of ATAM, ASRs, ADD, and Utility Tree, are all key components in the evaluation process.**/ADD/Summary of ADD / 属性驱动设计方法的总结/**Attribute Driven Design / 属性驱动设计**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 228, "text": "- \"**Choose a part** of the system to design.\" / 选择系统的某一部分进行设计。\n- \"**Marshal** all the architecturally significant requirements for that part.\" / 收集该部分的所有架构上重要的需求。\n- \"**Generate and test a design** for that part.\" / 为该部分生成并测试设计。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::886", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./① The abstract common services tactic is intended to **reduce coupling**, **but it also might reduce cohesion**?", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 352, "text": "抽象公共服务策略旨在减少耦合，但它也可能减少内聚性？\n\nThe tactic of using abstract common services to reduce coupling is often a key design consideration in software architecture, especially in systems that need to scale, evolve, or maintain flexibility. Here's how it works and the potential trade-offs:\n\n使用抽象公共服务来减少耦合的策略通常是软件架构中的一个关键设计考虑，尤其是在需要扩展、演进或保持灵活性的系统中。以下是它的工作原理和潜在的权衡："}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::887", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./① The abstract common services tactic is intended to **reduce coupling**, **but it also might reduce cohesion**?/**Reducing Coupling / 减少耦合**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 437, "text": "- Coupling refers to the degree to which one component (or module) depends on another. The idea behind using abstract common services is to centralize common functionality (e.g., logging, authentication, data access) in shared services, so that individual components don't need to implement the same logic or directly reference one another. / 耦合指的是一个组件（或模块）对另一个组件的依赖程度。使用抽象公共服务的想法是将常见功能（如日志记录、身份验证、数据访问）集中在共享服务中，这样各个组件就不需要实现相同的逻辑或直接引用彼此。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::888", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./① The abstract common services tactic is intended to **reduce coupling**, **but it also might reduce cohesion**?/**Reducing Coupling / 减少耦合**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 481, "text": "r. / 耦合指的是一个组件（或模块）对另一个组件的依赖程度。使用抽象公共服务的想法是将常见功能（如日志记录、身份验证、数据访问）集中在共享服务中，这样各个组件就不需要实现相同的逻辑或直接引用彼此。\n- By defining abstract interfaces for these services, different modules or components can rely on the service without being tightly coupled to the specific implementation. This makes the system more modular, as individual components can evolve independently as long as they conform to the interface. / 通过为这些服务定义抽象接口，不同的模块或组件可以依赖于这些服务，而不必紧密耦合到具体的实现。这使得系统更加模块化，因为各个组件可以独立演化，只要它们遵循接口。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::889", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./① The abstract common services tactic is intended to **reduce coupling**, **but it also might reduce cohesion**?/**Reducing Cohesion / 减少内聚性**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 382, "text": "- Cohesion, on the other hand, refers to how closely the responsibilities of a single component or module are related to each other. High cohesion means that the responsibilities of a component are highly related and focused. For example, a service that only handles user authentication has high cohesion. / 另一方面，内聚性指的是一个组件或模块的职责之间的相关程度。高内聚性意味着一个组件的职责高度相关且集中。例如，只有处理用户身份验证的服务具有高内聚性。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::890", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./① The abstract common services tactic is intended to **reduce coupling**, **but it also might reduce cohesion**?/**Reducing Cohesion / 减少内聚性**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 651, "text": "ion has high cohesion. / 另一方面，内聚性指的是一个组件或模块的职责之间的相关程度。高内聚性意味着一个组件的职责高度相关且集中。例如，只有处理用户身份验证的服务具有高内聚性。\n- When we abstract common services, there’s a risk that cohesion within components might decrease. For instance, instead of a service being highly focused on a particular domain (e.g., payment processing), it might have to deal with a broader set of concerns, like interacting with multiple abstracted common services (e.g., logging, security, and error handling). This could dilute the service’s focus, reducing its cohesion. / 当我们抽象公共服务时，存在组件内部的内聚性可能降低的风险。例如，一个服务可能不再专注于某个特定领域（例如支付处理），而是需要处理更广泛的问题，如与多个抽象的公共服务（例如日志、身份验证和错误处理）进行交互。这可能会稀释服务的关注点，减少内聚性。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::891", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./① The abstract common services tactic is intended to **reduce coupling**, **but it also might reduce cohesion**?/**Balance**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 620, "text": "The key challenge here is balancing reducing coupling with maintaining high cohesion. By abstracting common functionality, you reduce direct dependencies between modules, but you also risk over-generalizing the services, leading to poor cohesion or making services harder to understand and maintain. The design should ensure that:\n\n这里的关键挑战是平衡减少耦合与保持高内聚性之间的关系。通过抽象公共功能，您可以减少模块之间的直接依赖，但也可能面临过度泛化服务的风险，从而导致内聚性差或使服务变得难以理解和维护。设计应确保：\n\n- Common services are generic enough to serve multiple components, but not so abstract that they lose the focus or purpose of a specific domain. / 公共服务足够通用，可以服务多个组件，但又不会过于抽象，以至于失去特定领域的关注点或目标。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::892", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./① The abstract common services tactic is intended to **reduce coupling**, **but it also might reduce cohesion**?/**Balance**", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 246, "text": "they lose the focus or purpose of a specific domain. / 公共服务足够通用，可以服务多个组件，但又不会过于抽象，以至于失去特定领域的关注点或目标。\n- Cohesion is preserved at the component level so that the domain logic of each module remains clear and focused. / 在组件级别保持内聚性，以便每个模块的领域逻辑保持清晰且集中。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::893", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.（textbook **P409 English version**）", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 90, "text": "讨论编程语言的选择（作为技术选择的一个例子）及其与架构的一般关系。\n\n"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::894", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.（textbook **P409 English version**）/Solution A（ Various Languages )", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 531, "text": "Choosing the right programming language or technology stack is one of the most crucial decisions in software architecture, as it can have a significant impact on architecture's design, maintainability, scalability, and performance.\n选择合适的编程语言或技术栈是软件架构中最关键的决策之一，因为它会对架构的设计、可维护性、可扩展性和性能产生重大影响。\n\n**Programming Language and Architecture / 编程语言与架构**\n\nThe programming language or framework one chooses for a system is tightly coupled with architecture in several ways: 为系统选择的编程语言或框架在多个方面与架构紧密相关：\n\n1. **Performance Considerations / 性能考虑：**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::895", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.（textbook **P409 English version**）/Solution A（ Various Languages )", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 695, "text": "rchitecture in several ways: 为系统选择的编程语言或框架在多个方面与架构紧密相关：\n\n1. **Performance Considerations / 性能考虑：**\n\n- Some languages (like C++ or Rust) offer fine-grained control over system resources (e.g., memory management, concurrency), which can be crucial for high-performance systems like embedded software or real-time applications.\n某些语言（如C++或Rust）提供对系统资源（例如内存管理、并发）的细粒度控制，这对高性能系统（如嵌入式软件或实时应用程序）至关重要。\n- Other languages (like Python or Ruby) prioritize developer productivity over raw performance. These languages often favor ease of development, but may not be suitable for performance-critical components without optimization.\n其他语言（如Python或Ruby）将开发者生产力置于原始性能之上。这些语言通常更注重开发的便捷性，但对于性能关键的组件，未经优化的情况下可能不适用。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::896", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.（textbook **P409 English version**）/Solution A（ Various Languages )", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 656, "text": "without optimization.\n其他语言（如Python或Ruby）将开发者生产力置于原始性能之上。这些语言通常更注重开发的便捷性，但对于性能关键的组件，未经优化的情况下可能不适用。\n\n1. **Concurrency and Parallelism / 并发与并行：**\n\n- Different programming languages have varying levels of support for concurrency and parallelism. For instance, Go and Erlang provide strong concurrency models natively, making them excellent choices for distributed systems and services that require high levels of concurrency.\n不同的编程语言对并发和并行的支持程度不同。例如，Go和Erlang本身提供强大的并发模型，非常适合需要高并发的分布式系统和服务。\n- Languages like Java or C# provide concurrency models through threading and async programming, but handling concurrency might require more boilerplate or configuration."}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::897", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.（textbook **P409 English version**）/Solution A（ Various Languages )", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 496, "text": "ng and async programming, but handling concurrency might require more boilerplate or configuration.\n像Java或C#这样的语言通过线程和异步编程提供并发模型，但处理并发可能需要更多的样板代码或配置。\n\n1. **Scalability and Flexibility / 可扩展性与灵活性：**\n\n- Languages like JavaScript (with Node.js) or Python have thriving ecosystems for building scalable web applications due to their vast libraries and frameworks (e.g., Express.js, Flask, Django).\n 像JavaScript（配合Node.js）或Python这样的语言，由于其丰富的库和框架（例如Express.js、Flask、Django），在构建可扩展的Web应用程序方面有着蓬勃发展的生态系统。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::898", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.（textbook **P409 English version**）/Solution A（ Various Languages )", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 478, "text": "avaScript（配合Node.js）或Python这样的语言，由于其丰富的库和框架（例如Express.js、Flask、Django），在构建可扩展的Web应用程序方面有着蓬勃发展的生态系统。\n- For microservices architectures, some languages (e.g., Java, Go, Node.js) may offer better support for rapid service deployment, while others (like PHP or Ruby) may face challenges scaling effectively, especially in high-concurrency environments.\n 对于微服务架构，一些语言（如Java、Go、Node.js）可能更适合快速部署服务，而其他语言（如PHP或Ruby）在有效扩展时可能面临挑战，特别是在高并发环境中。\n\n1. **Ecosystem and Libraries:**\n **生态系统与库：**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::899", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.（textbook **P409 English version**）/Solution A（ Various Languages )", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 688, "text": "可能更适合快速部署服务，而其他语言（如PHP或Ruby）在有效扩展时可能面临挑战，特别是在高并发环境中。\n\n1. **Ecosystem and Libraries:**\n **生态系统与库：**\n\n- The ecosystem of a language plays a big role in the architecture. Languages like Java and Python have mature ecosystems with frameworks for almost any problem—whether it’s web development, data science, or machine learning. This can simplify architectural decisions, as many off-the-shelf solutions are available.\n编程语言的生态系统在架构中起着重要作用。像Java和Python这样的语言拥有成熟的生态系统，几乎可以为任何问题提供框架——无论是Web开发、数据科学还是机器学习。这可以简化架构决策，因为许多现成的解决方案是可用的。\n- On the other hand, choosing a language with a smaller ecosystem could require more custom-built solutions, which may increase the complexity of the architecture."}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::900", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.（textbook **P409 English version**）/Solution A（ Various Languages )", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 536, "text": "m could require more custom-built solutions, which may increase the complexity of the architecture.\n另一方面，选择一个生态系统较小的语言可能需要更多自定义构建的解决方案，这可能增加架构的复杂性。\n\n1. **Maintainability and Developer Expertise / 可维护性与开发者专业知识：**\n\n- A language’s simplicity (or complexity) affects maintainability. Python is known for its simplicity, making it easy to understand and maintain code, but it may not offer the same level of type safety or performance guarantees as Java or C++.\n编程语言的简洁性（或复杂性）会影响可维护性。Python以简洁著称，使得理解和维护代码变得容易，但它可能无法提供像Java或C++那样的类型安全性或性能保障。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::901", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.（textbook **P409 English version**）/Solution A（ Various Languages )", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 447, "text": "ees as Java or C++.\n编程语言的简洁性（或复杂性）会影响可维护性。Python以简洁著称，使得理解和维护代码变得容易，但它可能无法提供像Java或C++那样的类型安全性或性能保障。\n- Similarly, the team's expertise in a particular language is a crucial factor in architectural decisions. Adopting a language your team is proficient in will reduce the time needed for development and ensure long-term maintainability of architecture.\n同样，团队在特定语言中的专业知识是架构决策中的一个关键因素。采用团队熟练掌握的语言可以减少开发时间，并确保架构的长期可维护性。\n\n1. **Interoperability / 互操作性**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::902", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.（textbook **P409 English version**）/Solution A（ Various Languages )", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 663, "text": "e.\n同样，团队在特定语言中的专业知识是架构决策中的一个关键因素。采用团队熟练掌握的语言可以减少开发时间，并确保架构的长期可维护性。\n\n1. **Interoperability / 互操作性**\n\n- In a modern software system, interoperability between components is often required. For example, if you are building a system where some components are written in Java and others in Python, choosing languages that facilitate easy integration (e.g., through REST APIs, message queues, or shared data formats like JSON or Protocol Buffers) will shape your architecture.\n在现代软件系统中，组件之间的互操作性通常是必需的。例如，如果你正在构建一个系统，其中某些组件用Java编写，其他组件用Python编写，那么选择支持轻松集成的语言（例如通过REST API、消息队列，或共享数据格式如JSON或协议缓冲区）将影响你的架构。\n\n**Examples of Technology Choices and Architecture / 技术选择与架构的示例**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::903", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.（textbook **P409 English version**）/Solution A（ Various Languages )", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 555, "text": "消息队列，或共享数据格式如JSON或协议缓冲区）将影响你的架构。\n\n**Examples of Technology Choices and Architecture / 技术选择与架构的示例**\n\n- A microservices architecture might be best served by a combination of languages, depending on the specific needs of each service. For instance, the authentication service might be written in Go for fast performance and scalability, while the data analytics service might be built with Python for its rich ecosystem of machine learning libraries.\n 微服务架构可能最好通过语言组合来实现，具体取决于每个服务的需求。例如，身份验证服务可能会用Go编写，以实现快速性能和可扩展性，而数据分析服务可能会用Python构建，因为Python拥有丰富的机器学习库生态系统。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::904", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.（textbook **P409 English version**）/Solution A（ Various Languages )", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 453, "text": "最好通过语言组合来实现，具体取决于每个服务的需求。例如，身份验证服务可能会用Go编写，以实现快速性能和可扩展性，而数据分析服务可能会用Python构建，因为Python拥有丰富的机器学习库生态系统。\n- A monolithic application, on the other hand, might prefer a Java or C# stack, where strong typing, scalability, and the mature frameworks (e.g., Spring, ASP.NET) are beneficial for handling the complexity of a large, tightly integrated system.\n 另一方面，一个单体应用程序可能更倾向于使用Java或C#技术栈，因为强类型、可扩展性以及成熟的框架（如Spring、ASP.NET）有助于处理大型、紧密集成系统的复杂性。\n\n**Conclusion / 结论**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::905", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.（textbook **P409 English version**）/Solution A（ Various Languages )", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 648, "text": "体应用程序可能更倾向于使用Java或C#技术栈，因为强类型、可扩展性以及成熟的框架（如Spring、ASP.NET）有助于处理大型、紧密集成系统的复杂性。\n\n**Conclusion / 结论**\n\nThe choice of programming language and the overall technology stack directly influence the architecture of a system by shaping the design patterns, deployment strategies, and scalability approaches. It is important to consider the specific needs of the application, the expertise of the team, and the long-term maintenance implications when selecting the appropriate technologies. Ultimately, the goal is to choose technologies that align with the architectural goals, whether those are modularity, scalability, performance, or ease of development."}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::906", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.（textbook **P409 English version**）/Solution A（ Various Languages )", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 243, "text": "chitectural goals, whether those are modularity, scalability, performance, or ease of development.\n\n 编程语言的选择和整体技术栈直接影响系统的架构，通过塑造设计模式、部署策略和可扩展性方法来决定架构的方向。在选择合适的技术时，重要的是考虑应用程序的特定需求、团队的专业知识以及长期维护的影响。最终目标是选择与架构目标相一致的技术，无论这些目标是模块化、可扩展性、性能，还是开发的简易性。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::907", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.（textbook **P409 English version**）/Solution B ( Java & Python )", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 685, "text": "- In the context of software architecture, the choice of programming language plays a critical role in shaping the design and structure of a system. Each language comes with its strengths and weaknesses, and its impact on system architecture can vary depending on the goals of the application, the team's expertise, and the technical environment. Below, we will compare Java and Python, two commonly used programming languages, and discuss how their characteristics influence architectural decisions.\n\n在软件架构的背景下，编程语言的选择在塑造系统的设计和结构中起着至关重要的作用。每种语言都有其优点和缺点，它对系统架构的影响会根据应用程序的目标、团队的专业知识和技术环境有所不同。下面，我们将比较两种常用的编程语言——Java和Python，并讨论它们的特性如何影响架构决策。\n\n**Java: Strengths and Architectural Impact**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::908", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.（textbook **P409 English version**）/Solution B ( Java & Python )", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 558, "text": "有所不同。下面，我们将比较两种常用的编程语言——Java和Python，并讨论它们的特性如何影响架构决策。\n\n**Java: Strengths and Architectural Impact**\n**Java：优点与架构影响**\n\n1. **Performance and Efficiency: / 性能与效率：**\n\n- Java is a statically typed language known for its high performance, especially in large-scale, enterprise-level applications. The Java Virtual Machine (JVM) allows Java programs to be platform-independent, providing cross-platform portability and consistent performance across different environments.\n\nJava是一种静态类型语言，以其高性能著称，特别是在大规模企业级应用中。Java虚拟机（JVM）使得Java程序可以跨平台运行，提供跨平台的可移植性，并在不同的环境中保持一致的性能。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::909", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.（textbook **P409 English version**）/Solution B ( Java & Python )", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 516, "text": "ents.\n\nJava是一种静态类型语言，以其高性能著称，特别是在大规模企业级应用中。Java虚拟机（JVM）使得Java程序可以跨平台运行，提供跨平台的可移植性，并在不同的环境中保持一致的性能。\n\n- Java’s strong typing and compilation process catch errors early in the development cycle, which contributes to maintainability, stability, and predictable performance in large systems. This makes it well-suited for enterprise architecture, where stability, security, and performance are critical.\n\nJava的强类型和编译过程可以在开发周期的早期捕捉到错误，这有助于大系统的可维护性、稳定性和可预测性能。因此，它非常适合企业架构，在这种架构中，稳定性、安全性和性能至关重要。\n\n1. **Scalability: / 可扩展性：**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::910", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.（textbook **P409 English version**）/Solution B ( Java & Python )", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 459, "text": "周期的早期捕捉到错误，这有助于大系统的可维护性、稳定性和可预测性能。因此，它非常适合企业架构，在这种架构中，稳定性、安全性和性能至关重要。\n\n1. **Scalability: / 可扩展性：**\n\n- Java is widely used in large-scale systems and has proven to scale well in highly concurrent and distributed environments. It supports multi-threading and parallel processing natively through its robust concurrency libraries (e.g., Executor Framework, Concurrency Utilities).\n\nJava广泛应用于大规模系统，并且在高度并发和分布式环境中表现出良好的扩展性。它通过强大的并发库（例如Executor框架、并发工具）本地支持多线程和并行处理。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::911", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.（textbook **P409 English version**）/Solution B ( Java & Python )", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 474, "text": "ency Utilities).\n\nJava广泛应用于大规模系统，并且在高度并发和分布式环境中表现出良好的扩展性。它通过强大的并发库（例如Executor框架、并发工具）本地支持多线程和并行处理。\n\n- In architectures such as microservices, Java is often preferred due to its strong support for scalable and fault-tolerant services. Additionally, Java's JVM is optimized for long-running applications, making it ideal for systems that require high uptime.\n\n在微服务等架构中，Java通常是首选，因为它对可扩展和容错服务有很好的支持。此外，Java的JVM针对长期运行的应用进行了优化，适合需要高可用性的系统。\n\n1. **Enterprise Ecosystem: / 企业生态系统：**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::912", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.（textbook **P409 English version**）/Solution B ( Java & Python )", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 531, "text": "，因为它对可扩展和容错服务有很好的支持。此外，Java的JVM针对长期运行的应用进行了优化，适合需要高可用性的系统。\n\n1. **Enterprise Ecosystem: / 企业生态系统：**\n\n- Java has a mature ecosystem with many frameworks that support enterprise-level architecture, such as Spring, Hibernate, and Java EE (Jakarta EE). These frameworks provide tools for handling persistence, transactions, security, and web services, making it easy to integrate different components of a large system.\n\nJava拥有成熟的生态系统，提供许多支持企业级架构的框架，如Spring、Hibernate和Java EE（Jakarta EE）。这些框架提供了处理持久化、事务、安全性和Web服务的工具，使得集成大型系统中的不同组件变得容易。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::913", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.（textbook **P409 English version**）/Solution B ( Java & Python )", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 456, "text": "多支持企业级架构的框架，如Spring、Hibernate和Java EE（Jakarta EE）。这些框架提供了处理持久化、事务、安全性和Web服务的工具，使得集成大型系统中的不同组件变得容易。\n\n- Java’s strong ecosystem is particularly beneficial when adopting Layered Architectures (e.g., MVC, 3-tier), where the separation of concerns between the user interface, business logic, and data access layers is essential.\n\n当采用分层架构（例如MVC、三层架构）时，Java的强大生态系统尤其有利，因为在这种架构中，用户界面、业务逻辑和数据访问层之间的关注点分离是至关重要的。\n\n1. **Interoperability and Integration:**\n**互操作性与集成：**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::914", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.（textbook **P409 English version**）/Solution B ( Java & Python )", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 694, "text": "其有利，因为在这种架构中，用户界面、业务逻辑和数据访问层之间的关注点分离是至关重要的。\n\n1. **Interoperability and Integration:**\n**互操作性与集成：**\n\n- Java integrates well with other languages and technologies, especially in large systems where multiple technologies must coexist. For example, Java applications often use REST APIs, SOAP services, or message queues to communicate with other components written in different languages. Its strong support for integration through web services makes it well-suited for service-oriented architectures (SOA) and microservices.\n\nJava与其他语言和技术的集成表现良好，尤其是在需要多种技术共存的大型系统中。例如，Java应用程序通常使用REST API、SOAP服务或消息队列与用不同语言编写的其他组件进行通信。它通过Web服务的强大集成支持使得Java非常适合服务导向架构（SOA）和微服务架构。\n\n1. **Long-Term Maintainability:**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::915", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.（textbook **P409 English version**）/Solution B ( Java & Python )", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 692, "text": "息队列与用不同语言编写的其他组件进行通信。它通过Web服务的强大集成支持使得Java非常适合服务导向架构（SOA）和微服务架构。\n\n1. **Long-Term Maintainability:**\n**长期可维护性：**\n\n- Java's static typing, clear object-oriented principles, and rigorous development practices (e.g., unit testing, design patterns) contribute to long-term maintainability and developer collaboration in large teams. Its popularity in the enterprise software industry has created a large pool of resources, documentation, and developers, which further supports its role in mission-critical applications.\n\nJava的静态类型、明确的面向对象原则和严格的开发实践（例如单元测试、设计模式）有助于大型团队的长期可维护性和开发者之间的协作。它在企业软件行业的流行创造了大量的资源、文档和开发者，从而进一步支持它在关键任务应用中的角色。\n\n**Python: Strengths and Architectural Impact / Python：优点与架构影响**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::916", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.（textbook **P409 English version**）/Solution B ( Java & Python )", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 686, "text": "大量的资源、文档和开发者，从而进一步支持它在关键任务应用中的角色。\n\n**Python: Strengths and Architectural Impact / Python：优点与架构影响**\n\n1. **Rapid Development and Flexibility:快速开发与灵活性:**\n\n- Python is dynamically typed and interpreted, making it ideal for rapid prototyping and quick development. Python’s syntax is simple and expressive, which makes it a great choice for projects where time-to-market is a priority. This characteristic makes Python particularly suitable for startups, MVPs, or experimental applications where iterative development and flexibility are important.\n\nPython是动态类型并且解释型的，使其成为快速原型设计和快速开发的理想选择。Python的语法简单且富有表现力，这使得它非常适合那些将市场响应时间放在首位的项目。这一特点使得Python特别适用于初创公司、最小可行产品（MVP）或实验性应用程序，这些应用程序强调迭代开发和灵活性。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::917", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.（textbook **P409 English version**）/Solution B ( Java & Python )", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 526, "text": "on的语法简单且富有表现力，这使得它非常适合那些将市场响应时间放在首位的项目。这一特点使得Python特别适用于初创公司、最小可行产品（MVP）或实验性应用程序，这些应用程序强调迭代开发和灵活性。\n\n- However, Python’s dynamic nature can introduce runtime errors that are harder to detect compared to statically typed languages like Java. This can be a challenge for large, complex systems, where predictability and robust error handling are important architectural considerations.\n\n然而，Python的动态特性可能会引入运行时错误，这些错误比静态类型语言（如Java）更难以检测。在大型复杂系统中，这可能会成为一个挑战，因为可预测性和稳健的错误处理是重要的架构考虑因素。\n\n1. **Performance and Scalability: / 性能与可扩展性：**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::918", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.（textbook **P409 English version**）/Solution B ( Java & Python )", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 573, "text": "难以检测。在大型复杂系统中，这可能会成为一个挑战，因为可预测性和稳健的错误处理是重要的架构考虑因素。\n\n1. **Performance and Scalability: / 性能与可扩展性：**\n\n- Python is generally slower than Java, particularly for CPU-bound tasks. Its interpreted nature and dynamic typing can lead to performance bottlenecks, especially in high-performance or high-throughput applications. However, Python can be optimized using external libraries written in C or Cython, which can mitigate performance concerns in some cases.\n\nPython通常比Java慢，尤其是在CPU密集型任务中。它的解释型特性和动态类型可能会导致性能瓶颈，尤其是在高性能或高吞吐量的应用中。然而，Python可以通过使用用C或Cython编写的外部库进行优化，从而在某些情况下缓解性能问题。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::919", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.（textbook **P409 English version**）/Solution B ( Java & Python )", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 636, "text": "PU密集型任务中。它的解释型特性和动态类型可能会导致性能瓶颈，尤其是在高性能或高吞吐量的应用中。然而，Python可以通过使用用C或Cython编写的外部库进行优化，从而在某些情况下缓解性能问题。\n\n- Python is well-suited for lightweight services and high-level applications, but for systems that require intensive processing, Python might need to be supplemented with other technologies (e.g., C++ for performance-critical modules). For example, Python is commonly used in data science and machine learning, where its ease of use outweighs the performance concerns.\n\nPython非常适合轻量级服务和高层应用，但对于需要大量处理的系统，Python可能需要与其他技术（例如C++用于性能关键模块）结合使用。例如，Python常用于数据科学和机器学习领域，在这些领域中，Python的易用性往往超越了性能问题。\n\n1. **Data-Centric Architectures: / 数据驱动架构：**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::920", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.（textbook **P409 English version**）/Solution B ( Java & Python )", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 504, "text": "。例如，Python常用于数据科学和机器学习领域，在这些领域中，Python的易用性往往超越了性能问题。\n\n1. **Data-Centric Architectures: / 数据驱动架构：**\n\n- Python’s extensive ecosystem of libraries for data processing (e.g., NumPy, Pandas, TensorFlow, PyTorch) makes it a natural fit for data-centric architectures. When building systems that rely heavily on data manipulation, analytics, or machine learning, Python is often the language of choice.\n\nPython拥有广泛的数据处理库生态系统（如NumPy、Pandas、TensorFlow、PyTorch），使其成为数据驱动架构的自然选择。在构建依赖数据操作、分析或机器学习的系统时，Python通常是首选语言。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::921", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.（textbook **P409 English version**）/Solution B ( Java & Python )", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 532, "text": "泛的数据处理库生态系统（如NumPy、Pandas、TensorFlow、PyTorch），使其成为数据驱动架构的自然选择。在构建依赖数据操作、分析或机器学习的系统时，Python通常是首选语言。\n\n- Python is also widely used in the web development space with frameworks like Django and Flask, which promote rapid development and agile methodologies. These frameworks support the creation of RESTful APIs, web applications, and microservices quickly and efficiently.\n\nPython在Web开发领域也被广泛使用，框架如Django和Flask促进了快速开发和敏捷方法论。这些框架支持快速高效地创建RESTful API、Web应用程序和微服务。\n\n---\n\n1. **Microservices and Cloud-Native Architectures:**\n**微服务与云原生架构：**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::922", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.（textbook **P409 English version**）/Solution B ( Java & Python )", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 584, "text": "RESTful API、Web应用程序和微服务。\n\n---\n\n1. **Microservices and Cloud-Native Architectures:**\n**微服务与云原生架构：**\n\n- While Java is often the go-to for large-scale enterprise microservices architectures, Python has become a strong contender in the realm of cloud-native architectures. Python’s minimalistic approach and the wide range of cloud integration libraries (e.g., Boto3 for AWS) make it easy to deploy Python services in cloud environments, such as AWS, GCP, or Azure.\n\n虽然Java通常是大规模企业微服务架构的首选，Python已经成为云原生架构领域的强有力竞争者。Python的极简主义方法以及丰富的云集成库（如Boto3用于AWS）使得在AWS、GCP或Azure等云环境中部署Python服务变得更加容易。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::923", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.（textbook **P409 English version**）/Solution B ( Java & Python )", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 545, "text": "Python已经成为云原生架构领域的强有力竞争者。Python的极简主义方法以及丰富的云集成库（如Boto3用于AWS）使得在AWS、GCP或Azure等云环境中部署Python服务变得更加容易。\n\n- Python’s compatibility with containerization technologies like Docker and Kubernetes also makes it well-suited for microservice architectures, where small, independently deployable services are key. Python is commonly used to develop smaller, lighter-weight services in a microservices ecosystem.\n\nPython与Docker和Kubernetes等容器化技术的兼容性使其非常适合微服务架构，在这种架构中，小型、独立可部署的服务至关重要。Python常用于在微服务生态系统中开发更小、更轻量的服务。\n\n1. **Community and Ecosystem:**\n**社区与生态系统：**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::924", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.（textbook **P409 English version**）/Solution B ( Java & Python )", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 534, "text": "这种架构中，小型、独立可部署的服务至关重要。Python常用于在微服务生态系统中开发更小、更轻量的服务。\n\n1. **Community and Ecosystem:**\n**社区与生态系统：**\n\n- Python has a large and active open-source community, especially in fields like data science, web development, and automation. This community-driven development has created a rich ecosystem of libraries and tools that can greatly speed up development in specific domains (e.g., Flask, Django, FastAPI for web services).\n\nPython拥有一个庞大且活跃的开源社区，尤其在数据科学、Web开发和自动化等领域。社区驱动的开发创造了丰富的库和工具生态系统，这些工具可以大大加速特定领域（例如Web服务的Flask、Django、FastAPI）的开发。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::925", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.（textbook **P409 English version**）/Solution B ( Java & Python )", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 407, "text": "跃的开源社区，尤其在数据科学、Web开发和自动化等领域。社区驱动的开发创造了丰富的库和工具生态系统，这些工具可以大大加速特定领域（例如Web服务的Flask、Django、FastAPI）的开发。\n\n- However, Python’s ecosystem is less mature than Java’s when it comes to enterprise-level solutions, especially for areas like transaction management, security, and enterprise integration.\n\n然而，Python的生态系统在企业级解决方案方面不如Java成熟，尤其是在事务管理、安全性和企业集成等领域。\n\nArchitectural Trade-Offs: Java vs. Python / 架构权衡：Java与Python"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::926", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.（textbook **P409 English version**）/Solution B ( Java & Python )", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 492, "text": "解决方案方面不如Java成熟，尤其是在事务管理、安全性和企业集成等领域。\n\nArchitectural Trade-Offs: Java vs. Python / 架构权衡：Java与Python\n\n- Enterprise-Scale Systems: Java is better suited for enterprise-level applications requiring high performance, stability, and scalability. Its strong typing and robust frameworks (e.g., Spring Boot) support large, complex systems with well-defined layers (e.g., data, business logic, presentation).\n\n企业级系统：Java更适合需要高性能、稳定性和可扩展性的企业级应用。其强类型和稳健的框架（例如Spring Boot）支持具有明确层次（如数据层、业务逻辑层、表示层）的大型复杂系统。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::927", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.（textbook **P409 English version**）/Solution B ( Java & Python )", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 482, "text": "ion).\n\n企业级系统：Java更适合需要高性能、稳定性和可扩展性的企业级应用。其强类型和稳健的框架（例如Spring Boot）支持具有明确层次（如数据层、业务逻辑层、表示层）的大型复杂系统。\n\n- Rapid Development and Flexibility: Python excels in projects that require rapid iteration, ease of development, and flexibility. It is commonly used in systems that prioritize developer productivity and quick turnaround times, such as startups, MVPs, and machine learning applications.\n\n快速开发与灵活性：Python在需要快速迭代、简易开发和灵活性的项目中表现出色。它常用于那些优先考虑开发者生产力和快速交付时间的系统，例如初创公司、最小可行产品（MVP）和机器学习应用。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::928", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.（textbook **P409 English version**）/Solution B ( Java & Python )", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 478, "text": "ns.\n\n快速开发与灵活性：Python在需要快速迭代、简易开发和灵活性的项目中表现出色。它常用于那些优先考虑开发者生产力和快速交付时间的系统，例如初创公司、最小可行产品（MVP）和机器学习应用。\n\n- Performance: Java tends to outperform Python in CPU-intensive applications due to its statically typed nature and compiled code running on the JVM. For high-performance systems (e.g., large-scale distributed systems, real-time applications), Java is generally a better choice.\n\n性能：由于Java是静态类型语言，并且编译后的代码在JVM上运行，因此Java在CPU密集型应用中往往优于Python。在高性能系统（例如大规模分布式系统、实时应用）中，Java通常是更好的选择。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::929", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.（textbook **P409 English version**）/Solution B ( Java & Python )", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 493, "text": "性能：由于Java是静态类型语言，并且编译后的代码在JVM上运行，因此Java在CPU密集型应用中往往优于Python。在高性能系统（例如大规模分布式系统、实时应用）中，Java通常是更好的选择。\n\n- Scalability: Both languages can be used in scalable systems, but Java is typically favored in environments requiring high concurrency and fault tolerance. Python can also scale, but it might require additional optimization techniques or the use of other technologies to handle heavy loads effectively.\n\n可扩展性：两种语言都可以用于可扩展的系统，但Java通常在需要高并发和容错性的环境中更受青睐。Python也可以扩展，但它可能需要额外的优化技术或使用其他技术来有效处理重负载。"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::930", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.（textbook **P409 English version**）/Solution B ( Java & Python )", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 577, "text": "ctively.\n\n可扩展性：两种语言都可以用于可扩展的系统，但Java通常在需要高并发和容错性的环境中更受青睐。Python也可以扩展，但它可能需要额外的优化技术或使用其他技术来有效处理重负载。\n\n- Microservices: Both Java and Python can work in microservices architectures, but the choice depends on the use case. Java is better for large-scale microservices with strict requirements on transaction management, reliability, and performance, while Python is often used for smaller, quicker-to-develop services in cloud-native environments.\n\n微服务：Java和Python都可以在微服务架构中工作，但选择取决于使用场景。Java更适用于具有严格事务管理、可靠性和性能要求的大规模微服务，而Python通常用于云原生环境中开发小型、更易于开发的服务。\n\n---\n\n**Conclusion**\n **结论**"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::931", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.（textbook **P409 English version**）/Solution B ( Java & Python )", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 700, "text": "使用场景。Java更适用于具有严格事务管理、可靠性和性能要求的大规模微服务，而Python通常用于云原生环境中开发小型、更易于开发的服务。\n\n---\n\n**Conclusion**\n **结论**\n\n- The choice between Java and Python has a significant impact on the architecture of a system. Java is typically chosen for its performance, scalability, and strong ecosystem for building large, enterprise-level systems, while Python is selected for its rapid development capabilities, flexibility, and strong support for data-centric architectures and cloud-native applications. The decision depends largely on the requirements of the project—whether you need high performance, robust frameworks for enterprise-level solutions, or a quick, agile development process with strong support for data scie"}
{"id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe::932", "page_id": "docx::SavQwwJsIiYSXAkhV0QcJUUknKe", "title": "SA 2024 真题知识点复习（超爽中英，合并卷）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2024 真题知识点复习（超爽中英，合并卷）", "section": "SA 2024 真题知识点复习（超爽中英，合并卷）/中英文 背诵 版本（两卷合并）/Open discussion./② Discuss the choice of **programming language** (an example of choice of technology) and its **relation to architecture** in general.（textbook **P409 English version**）/Solution B ( Java & Python )", "url": "https://a1npn29y3xu.feishu.cn/wiki/SavQwwJsIiYSXAkhV0QcJUUknKe", "source_type": "docx", "n_chars": 476, "text": "enterprise-level solutions, or a quick, agile development process with strong support for data science and machine learning. Understanding the trade-offs between these two languages can help architects make more informed decisions based on their system’s needs.\n\nJava和Python的选择对系统架构有着显著影响。Java通常因其性能、可扩展性和构建大型企业级系统的强大生态系统而被选用，而Python则因其快速开发能力、灵活性以及对数据驱动架构和云原生应用的强力支持而被选择。决策通常取决于项目的需求——是需要高性能、适用于企业级解决方案的稳健框架，还是需要快速、敏捷的开发过程，以及对数据科学和机器学习的强力支持。了解这两种语言之间的权衡可以帮助架构师根据系统的需求做出更明智的决策。"}
{"id": "docx::Y7JcwfY5Ji771dka9hIcbfYhnAf::933", "page_id": "docx::Y7JcwfY5Ji771dka9hIcbfYhnAf", "title": "SA 2025 真题 回忆版", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2025 真题 回忆版", "section": "SA 2025 真题 回忆版/选择题(30分=3×10)", "url": "https://a1npn29y3xu.feishu.cn/wiki/Y7JcwfY5Ji771dka9hIcbfYhnAf", "source_type": "docx", "n_chars": 276, "text": "1-2 SA概念 视图与结构\n\n-软件架构的作用\n\n-开发时(development time)对软件映射到开发团队(?)适合用什么结构描述\n\n选项：分配结构\n\n一道问哪些选项与 coordination 相关（7大决策分类）\n\n4道QA/Tactics相关的的考点\n\n-安全性的特点(CIA)\n\n答案：Confidentiality\n\n-ADD在一次迭代之后的输出是什么\n\n选项：带part的那一项，一次迭代只进行了局部的设计\n\n-一道问你哪个行为可以增强架构与代码之间的一致性\n\n选项关键词：enforce constraint，framework"}
{"id": "docx::Y7JcwfY5Ji771dka9hIcbfYhnAf::934", "page_id": "docx::Y7JcwfY5Ji771dka9hIcbfYhnAf", "title": "SA 2025 真题 回忆版", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2025 真题 回忆版", "section": "SA 2025 真题 回忆版/简答(20分)", "url": "https://a1npn29y3xu.feishu.cn/wiki/Y7JcwfY5Ji771dka9hIcbfYhnAf", "source_type": "docx", "n_chars": 277, "text": "基本都是概念理解：\n\n1.自行举例，列出两个一般需求，满足可修改性需要把这个需求进行简化的目标(例如修改用户界面)\n\n2.效用树的层级，以及优先级元组(H,M,L)的作用\n\n3.1 architecture Pattern和Tactics的区别\n\n3.2architecture Pattern和Tactics如何一同设计系统(Tactics Augmentation)\n\n4.除了查找显式的(Explicit)需求文档，再写出两种找到ASR的途径，为什么架构师要区分ASR和一般需求\n\n5.权衡敏捷与架构在什么场景下要用哪个，什么情况下适合两个都用"}
{"id": "docx::Y7JcwfY5Ji771dka9hIcbfYhnAf::935", "page_id": "docx::Y7JcwfY5Ji771dka9hIcbfYhnAf", "title": "SA 2025 真题 回忆版", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2025 真题 回忆版", "section": "SA 2025 真题 回忆版/综合题(50分)", "url": "https://a1npn29y3xu.feishu.cn/wiki/Y7JcwfY5Ji771dka9hIcbfYhnAf", "source_type": "docx", "n_chars": 656, "text": "**1.mHealth系统，一个移动健康系统(20分)**\n\n\n\n(1) 列出一个延迟（用性能来描述）相关的具体场景（如果病人（Mobile）出现非正常情况，到告知医生之间的延迟是一个需要考虑的问题）\n\n(2) 从(1)的答案中找出可能影响延迟的因素\n\n(3) 列出3种可以降低延迟的战术，同时解释原因\n\n(4) 列出一个保密性（安全） 相关的具体场景\n\n(5) 根据(4)列出2种合适的战术，同时解释原因\n\n**2.pub-sub模式的架构图(e-commerce系统，包含了三个微服务cart，shipping，email ，10分)**\n\n(1) 这个模式使用了什么战术\n\n(2) 解决了什么QA\n\n(3) 可能遇到什么QA问题（may struggle with ...，并附上原因）\n\n**3.一个House Hub，智能家居场景(20分)**\n\n题干列出了一系列非功能需求（a-j，共12条）\n\n(1) 将需求归到对应的QA类型(共5类，只有试卷上有表格)\n\n(2) QA/Tactics：拿出题干中的一条需求，问需要什么QA（可用性），然后问在这个context下可以使用什么战术，同时解释原因\n\n需求：意外断电(outage)后要持续工作24小时以上\n\n(3)视图与结构\n\n(i) Module和C&C结构的聚焦点和不同点\n\n(ii) 拿出题干中某条需求，问用什么View描述并说明理由"}
{"id": "docx::Y7JcwfY5Ji771dka9hIcbfYhnAf::936", "page_id": "docx::Y7JcwfY5Ji771dka9hIcbfYhnAf", "title": "SA 2025 真题 回忆版", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2025 真题 回忆版", "section": "SA 2025 真题 回忆版/综合题(50分)", "url": "https://a1npn29y3xu.feishu.cn/wiki/Y7JcwfY5Ji771dka9hIcbfYhnAf", "source_type": "docx", "n_chars": 586, "text": "因\n\n需求：意外断电(outage)后要持续工作24小时以上\n\n(3)视图与结构\n\n(i) Module和C&C结构的聚焦点和不同点\n\n(ii) 拿出题干中某条需求，问用什么View描述并说明理由\n\n需求：并行处理100户需求(关键词：concurrent，100 households)\n\n(iii) 拿题干中另一条需求，问实现这个需求后改变了哪一种Structure\n\n需求：开发团队在5个person-time之内加入对品牌(brand)的某项支持(support)\n\n以下为试卷高级抄手提供的原文\n\n第一题题干没抄完，希望有人补充一下\n(1) Suppose latency is the primary quality goal of the system, please define one concrete Quality Attribute scenario that explicitly describes the latency requirement. [4']\n(2) Based on the latency Quality Attribute scenario defined in (1), identify all the key factors that could impact the system's latency. [4']"}
{"id": "docx::Y7JcwfY5Ji771dka9hIcbfYhnAf::937", "page_id": "docx::Y7JcwfY5Ji771dka9hIcbfYhnAf", "title": "SA 2025 真题 回忆版", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2025 真题 回忆版", "section": "SA 2025 真题 回忆版/综合题(50分)", "url": "https://a1npn29y3xu.feishu.cn/wiki/Y7JcwfY5Ji771dka9hIcbfYhnAf", "source_type": "docx", "n_chars": 567, "text": "scenario defined in (1), identify all the key factors that could impact the system's latency. [4']\n(3) For the latency Quality Attribute scenario, propose three specific tactics to reduce system latency. Briefly explain how each tactic addresses the latency challenge. [6']\n(4) Suppose patient data confidentiality is another non-negotiable quality requirement. Please define one concrete Quality Attribute scenario that specifies the patient data confidentiality requirement. [3']\n(5) For the scenario in (4), suggest two effective tactics to ensure confidentiality."}
{"id": "docx::Y7JcwfY5Ji771dka9hIcbfYhnAf::938", "page_id": "docx::Y7JcwfY5Ji771dka9hIcbfYhnAf", "title": "SA 2025 真题 回忆版", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2025 真题 回忆版", "section": "SA 2025 真题 回忆版/综合题(50分)", "url": "https://a1npn29y3xu.feishu.cn/wiki/Y7JcwfY5Ji771dka9hIcbfYhnAf", "source_type": "docx", "n_chars": 682, "text": "rement. [3']\n(5) For the scenario in (4), suggest two effective tactics to ensure confidentiality.\n\n2. [10'] Fig.2 shows an e-commerce system based on the micro-service architecture. The system has three services including \"cart\", \"shipping\" and \"email\".\n(1) [3'] Which tactic is used in the diagram?\n(2) [3'] Which quality attribute does the tactic target?\n(3) [4'] Which other quality attribute may this architecture struggle with? Explain why.\n\n3. [20'] Read the following non-standard requirements document for a \"Smart Home Control Hub\" system.\n\n(这里给出了很多需求，需要判别对应哪一质量属性)\n\n(1) Please categorize the non-functional requirements from the list above. Fill in the table below. [5']"}
{"id": "docx::Y7JcwfY5Ji771dka9hIcbfYhnAf::939", "page_id": "docx::Y7JcwfY5Ji771dka9hIcbfYhnAf", "title": "SA 2025 真题 回忆版", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2025 真题 回忆版", "section": "SA 2025 真题 回忆版/综合题(50分)", "url": "https://a1npn29y3xu.feishu.cn/wiki/Y7JcwfY5Ji771dka9hIcbfYhnAf", "source_type": "docx", "n_chars": 640, "text": "lease categorize the non-functional requirements from the list above. Fill in the table below. [5']\n(2) Which Quality Attribute is primarily addressed by requirement h (24 hours operation during internet outage)? [1'] Name and briefly explain 2 architectural tactics that could be used to achieve this attribute in the given context. [4']\n(3) [10'] View and Structure Analysis\ni) Describe the primary focus and differences between the C&C view and the Module View for the system. [4']\nii) Which architecture view would be most important for analyzing requirement j (concurrent requirements from 100 households)? Explain your reasoning. [3']"}
{"id": "docx::Y7JcwfY5Ji771dka9hIcbfYhnAf::940", "page_id": "docx::Y7JcwfY5Ji771dka9hIcbfYhnAf", "title": "SA 2025 真题 回忆版", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 2025 真题 回忆版", "section": "SA 2025 真题 回忆版/综合题(50分)", "url": "https://a1npn29y3xu.feishu.cn/wiki/Y7JcwfY5Ji771dka9hIcbfYhnAf", "source_type": "docx", "n_chars": 239, "text": "analyzing requirement j (concurrent requirements from 100 households)? Explain your reasoning. [3']\niii) Requirement g (adding a new device in 5 days) primarily influences which type of architecture structures? Explain your reasoning. [3']"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::941", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "SA 讲义（一） Chapter 01, 02 Introduction", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 93, "text": "SA 讲义（一） Chapter 01, 02 Introduction\n\n"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::942", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/What is Software Architecture / 什么是软件体系结构？（必考）", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 249, "text": "*The software architecture of a system is the set of structures（有三种必考的重要结构） needed to* ***reason（推导）*** *for the system, which comprise software elements, relations among them, and properties of both.* / 系统的软件架构是为系统进行推理所需的一组结构，包含软件元素、它们之间的关系以及两者的属性。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::943", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Architecture is a Set of Software Structures / 架构是一组软件结构", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 379, "text": "A structure is a set of elements held together by a relation. / 结构是一组通过关系连接在一起的元素。\n\n Software systems are composed of many structures, and no single structure holds claim to being the architecture. / 软件系统由许多结构组成，且没有单一结构可以声称自己是架构。\n\nThere are 3 important categories of architectural structures: / 有三种重要的结构类型\n\n① Module / 模块\n\n② Component and Connector / 组件和连接器\n\n③ Allocation / 分配"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::944", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Architecture is a Set of Software Structures / 架构是一组软件结构/Module Structures / 模块结构", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 461, "text": "Modules: **Implementation units** that could partition systems / 可以把系统拆分的**实现单元**\n\nModules are assigned specific computational responsibilities, and are the basis of work assignments for programming teams. / 模块被分配特定的计算责任，是编程团队工作分配的基础。\n\nIn large projects, these elements (modules) are subdivided for assignment to sub-teams. / 在大型项目中，这些元素（模块）被细分并分配给子团队。\n\n**批注：前后端分离也算是模块结构的一种表现形式，而前端和后端又会根据功能的不同拆分出细致的模块**\n\n"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::945", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Architecture is a Set of Software Structures / 架构是一组软件结构/Component-and-connector Structures / 组件-连接器结构", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 527, "text": "Named as **runtime structures** / 也名为运行结构\nFocus on the way the elements interact with each other at runtime to carry out the system's functions. / 关注元素在运行时如何相互作用，以执行系统的功能。\n\nA component is always a runtime entity. / 一个组件一直都是运行实体\n\n- In SOA, the system is to be built as a set of services. / 在面向服务架构（SOA）中，系统将作为一组服务构建。\n- These services are made up of (compiled from) the programs in the various implementation units modules. / 这些服务由不同实现单元（模块）中的程序组成（编译而来）。\n- Suppose the system is to be built as a set of services. / 假设系统将作为一组服务构建。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::946", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Architecture is a Set of Software Structures / 架构是一组软件结构/Component-and-connector Structures / 组件-连接器结构", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 327, "text": "由不同实现单元（模块）中的程序组成（编译而来）。\n- Suppose the system is to be built as a set of services. / 假设系统将作为一组服务构建。\n- The services, the infrastructure they interact with, and the synchronization and interaction relations among them form another kind of structure often used to describe a system. / 服务、它们交互的基础设施，以及它们之间的同步和交互关系，构成了另一种常用于描述系统的结构。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::947", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Architecture is a Set of Software Structures / 架构是一组软件结构/Component-and-connector Structures / 组件-连接器结构/批注：Android 架构的底层原理", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::948", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Architecture is a Set of Software Structures / 架构是一组软件结构/Component-and-connector Structures / 组件-连接器结构/批注：在 Linux TCP/IP 体系结构中的应用：", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 656, "text": "\n\n1. **组件（Component）**：在 Linux 内核的 TCP/IP 体系结构中，组件可以是网络协议栈中的各个模块，如网络驱动程序、IP层、TCP层、UDP层、应用程序接口（如 sockets）等。每个组件都有自己的功能，它们各自负责特定的任务（例如数据传输、地址分配、协议处理等）。\n2. **连接器（Connector）**：连接器在这里就是这些组件如何相互交互。比如说，TCP 层和 IP 层之间是通过特定的协议接口来进行交互的。TCP 协议通过 IP 协议传输数据包，这样就形成了一个组件-连接器的互动关系。每个层次的协议都依赖于上层和下层的通信接口（连接器）来完成各自的任务。\n3. **服务和交互**：TCP/IP 协议栈在运行时提供的服务和这些服务之间的交互是非常典型的组件-连接器结构。在实际应用中，数据的传输不仅依赖于各个组件的功能实现，还依赖于它们之间的协调与同步。例如，在 TCP 传输过程中，数据的可靠传输需要 TCP 层和应用层之间的协作，而这种协作则依赖于底层的操作系统和硬件资源。\n\nLinux 内核的 TCP/IP 体系结构图正是通过展示网络栈中各个协议层（如 TCP、IP、网络驱动程序等）作为“组件”，它们之间通过数据流、协议接口等“连接器”互相连接，从而共同完成系统的网络功能。你可以将每个协议栈看作是一个组件，而它们之间的通信和数据交换则是连接器。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::949", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Architecture is a Set of Software Structures / 架构是一组软件结构/Component-and-connector Structures / 组件-连接器结构/批注：在 Linux TCP/IP 体系结构中的应用：", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 157, "text": "（如 TCP、IP、网络驱动程序等）作为“组件”，它们之间通过数据流、协议接口等“连接器”互相连接，从而共同完成系统的网络功能。你可以将每个协议栈看作是一个组件，而它们之间的通信和数据交换则是连接器。通过这个结构图，我们可以知道，系统的功能并非单一的，而是由多个组件协同工作，通过各自的连接器实现复杂的交互和同步。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::950", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Architecture is a Set of Software Structures / 架构是一组软件结构/Allocation Structures / 分配结构", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 502, "text": "Allocation structures **describe the mapping** from software structures to the system's environments. / 分配结构描述了从软件结构到系统环境的**映射关系**\n\n- Organizational / 组织性的\n- Developmental / 发展的\n- Installation / 安装\n- Execution / 执行\n\nFor example, / 举个例子\n\n- Modules are assigned to **teams** to develop, and assigned to places in **a file structure** for implemantation, integration, and testing. / 模块被分配给了团队去开发，并且分配了一个文件结构进行实现、集成和测试\n- Components are deployed onto **hardware** in order to execute. / 为了执行，组件都被部署到了**硬件**上"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::951", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Which Structures are Architectural? / 哪些结构是架构化的", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 580, "text": "**A structure is architectural if it supports reasoning about the system and the system's properties. / 如果一个结构支持对系统及其属性的推理，那么它就是架构性的。**\n\nThe reasoning should be about an attribute of the system that is important to some stakeholder. / 该推理应当围绕系统中对某些利益相关者重要的属性进行。\n These include / 这些属性包括\n\n- functionality achieved by the system, / 系统实现的功能，\n- the availability of the system in the face of faults, / 系统在故障面前的可用性，\n- the difficulty of making specific changes to the system, / 对系统进行特定更改的难易程度，\n- the responsiveness of the system to user requests, / 系统对用户请求的响应性，\n- many others. / 以及许多其他属性。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::952", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Architecture is an Abstraction / 架构是一种抽象", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 463, "text": "An architecture specifically omits certain information about elements that is not useful for reasoning about the system. / 架构特意省略了关于元素的某些信息，这些信息对于对系统进行推理没有帮助。\n\nThe architectural abstraction lets us look at the system in terms of its elements, how they are arranged, how they interact, how they are composed, and so forth. / 架构抽象使我们能够从元素的角度观察系统，了解它们是如何排列、如何交互、如何组合等。\n\nThis abstraction is essential to taming the complexity of an architecture. / 这种抽象对于驾驭架构的复杂性至关重要。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::953", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Architecture includes behavior / 架构包括了行为", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 304, "text": "The behavior of each element is part of architecture insofar as that behavior can be used to reason for the system. / 每个元素的行为是架构的一部分，只要该行为可以用来对系统进行推理。\nThis behavior embodies how elements interact with each other, which is clearly part of the definition of architecture. / 这种行为体现了元素之间如何相互作用，而这显然是架构定义的一部分。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::954", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Architecture includes behavior / 架构包括了行为/批注：在同步异步的应用", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 668, "text": "1. **同步与异步的交互行为：**\n\n - **同步**：在同步的交互中，一个组件或服务在等待另一个组件完成操作之前不会继续执行。这种交互方式意味着组件之间的操作是顺序的，通常会影响系统的响应时间和吞吐量。\n - **异步**：异步交互则允许一个组件在等待其他组件完成操作时继续执行其他任务，减少了等待时间，提高了系统的并发性和响应性。\n2. 这两种行为体现了组件如何在系统中相互作用，以及这些交互如何影响系统的整体性能、可扩展性等属性。\n3. **推理与架构属性：** 同步和异步行为可以作为“推理”系统架构中某些重要属性的依据。例如，如果系统的可用性和响应时间是关键属性，那么选择同步或异步的交互方式将直接影响这些属性的实现。在架构设计中，理解这些行为有助于评估系统在面对高并发请求时的表现，或者系统在发生故障时的可恢复性。\n4. **对关键利益相关者的重要性：** 在设计架构时，不同的利益相关者（如开发人员、运维人员、用户等）关心的可能是不同的系统属性。同步和异步的选择能够影响系统的可维护性（比如修改异步通信方式比同步方式更复杂）或系统的响应时间（异步可能更适合处理高并发的用户请求）。这种行为是架构设计中的核心，帮助各利益相关者推理和评估系统。\n\n同步和异步行为是架构设计中的基本元素，它们展现了组件如何相互作用，并且通过这些交互，我们能够推理出系统的各种重要属性（如响应性、可用性、可扩展性等）。这种推理过程是架构设计中至关重要的一部分，因为它能够帮助我们预测系统在不同场景下的表现，从而做出更加合理的设计决策。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::955", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Strcutures and Views / 结构和视图", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 547, "text": "Architects design structures. They document views of those structures. / 架构师设计结构，并记录这些结构的视图。\n\nA view is a representation of a coherent set of architectural elements, as written by and read by system stakeholders. / 视图是一个连贯的架构元素集合的表现形式，由系统利益相关者编写和阅读。\nA structure is the set of elements itself, as they exist in software or hardware. / 结构是元素本身的集合，存在于软件或硬件中。\n\nIn short, a view is a representation of a structure. / 简而言之，视图是结构的表现形式。\n\n- For example, a module structure is the set of the system's modules and their organization. / 例如，模块结构是系统模块及其组织方式的集合。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::956", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Strcutures and Views / 结构和视图", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 297, "text": "odule structure is the set of the system's modules and their organization. / 例如，模块结构是系统模块及其组织方式的集合。\n- A module view is the representation of that structure, documented according to a template in a chosen notation, and used by some system stakeholders. / 模块视图是该结构的表现形式，按照选定的符号模板进行文档化，并由一些系统利益相关者使用。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::957", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Strcutures and Views / 结构和视图/Module Structures / 模块结构", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 223, "text": "Module structures **embody（体现了）** decisions as to how the system is to be structured as a set of code or data units. / 模块结构了体现了如何让系统被组成一组代码或者数据单元的决策。\n\nModules are assigned areas of functional responsibility. / 模块被分配了功能责任区域。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::958", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Strcutures and Views / 结构和视图/Module Structures / 模块结构/Some useful module structures / 一些有用的模块结构/**Decomposition Structure / 分解结构**", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 659, "text": "The units are modules that are related to each other by the is-a-submodule-of relation. / 这些单元是通过“是一个子模块”关系相互关联的模块。\nIt shows how modules are decomposed into smaller modules recursively until the modules are small enough to be easily understood. / 它展示了模块如何递归地被分解成更小的模块，直到模块足够小，易于理解。\nModules often have products (such as interface specifications, code, test plans, etc.) associated with them. / 模块通常会有一些产品（如接口规范、代码、测试计划等）与之关联。\nThe decomposition structure determines, to a large degree, the system's modifiability, by assuring that likely changes are localized. / 分解结构在很大程度上决定了系统的可修改性，通过确保可能的变更被局部化来实现这一点。\n\n"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::959", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Strcutures and Views / 结构和视图/Module Structures / 模块结构/Some useful module structures / 一些有用的模块结构/**Decomposition Structure / 分解结构**/Uses Structure / 使用结构", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 426, "text": "The units here are also modules, perhaps classes / 这些单元也是模块，可能是类\nThe units are related by the ***uses*** relation, a specialized form of dependency. / 这些单元通过“使用关系”相互关联，这是一种特定形式的依赖关系。\nA unit of software ***uses*** another if the correctness of the first requires the presence of a correctly functioning version of the second. / 如果第一个单元的正确性依赖于第二个单元的正确运行，那么第一个单元就使用了第二个单元。\n\n"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::960", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Strcutures and Views / 结构和视图/Module Structures / 模块结构/Some useful module structures / 一些有用的模块结构/**Decomposition Structure / 分解结构**/Layer Structure / 层结构", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 544, "text": "The modules in this structure are called *layers*. / 该结构中的模块称为层。\nA layer is an abstract “virtual machine” that provides a cohesive set of services through a managed interface. / 层是一个抽象的“虚拟机”，通过受控接口提供一组有凝聚力的服务。\nLayers are *allowed* to use other layers in a strictly managed fashion. / 层允许以严格管理的方式使用其他层。\nIn strictly layered systems, a layer is only allowed to use a single other layer. / 在严格的分层系统中，一个层只允许使用一个其他层。\nThis structure imbues a system with portability, the ability to change the underlying computing platform. / 这种结构赋予系统可移植性，即能够更换底层计算平台。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::961", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Strcutures and Views / 结构和视图/Module Structures / 模块结构/Some useful module structures / 一些有用的模块结构/**Decomposition Structure / 分解结构**/Class (or generalization) Structure / 类结构", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 412, "text": "The module units in this structure are called *classes*. / 该结构中的模块单元称为类。\nThe relation is *inherited* from or is an instance of. / 该关系为“继承自”或“是某个实例”。\n**Inheritance** is a mechanism for **code reuse** and to allow independent extensions of the original software. / 继承是一种代码重用机制，允许对原始软件进行独立扩展。\nThe class structure allows one to reason for reuse and the incremental addition of functionality. / 类结构使得可以推理关于重用和功能的增量添加。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::962", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Strcutures and Views / 结构和视图/Module Structures / 模块结构/Some useful module structures / 一些有用的模块结构/**Decomposition Structure / 分解结构**/**Data Model Structure / 数据模型结构**", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 405, "text": "The data model describes the static information structure in terms of data entities and their relationships. / 数据模型通过数据实体及其关系描述静态信息结构。\nFor example, in a banking system, entities will typically include Account, Customer, and Loan. / 例如，在银行系统中，实体通常包括账户、客户和贷款。\nAccount has several attributes, such as account number, type (savings or checking), status, and current balance. / 账户有多个属性，如账户号码、类型（储蓄或支票）、状态和当前余额。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::963", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Strcutures and Views / 结构和视图/Component-and-connector Structures / 组件-连接器结构", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 639, "text": "C & C structures embody decisions as to how the system is to be structured as a set of elements that have runtime behavior(components) and interactions(connectors). / C＆C 结构体现了如何将系统构建为具有运行时行为（组件）和交互（连接器）的一组元素的决策。\n\n Elements are runtime components such as services, peers, clients, servers, or many other types of runtime element. / 元素是运行时组件，如服务、对等体、客户端、服务器或其他许多类型的运行时元素。\n Connectors are the communication ways among components, such as call-return, process synchronization operators, pipes, or others. / 连接器是组件之间的通信方式，如调用-返回、进程同步操作符、管道等。\n\nComponent-and-connector views help us answer questions such as these: / 组件和连接器视图可帮助我们回答以下问题："}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::964", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Strcutures and Views / 结构和视图/Component-and-connector Structures / 组件-连接器结构", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 654, "text": "管道等。\n\nComponent-and-connector views help us answer questions such as these: / 组件和连接器视图可帮助我们回答以下问题：\n\n- What are the major executing components and how do they interact at runtime? / 主要的执行组件有哪些，它们在运行时如何交互？\n- What are the major shared data stores? / 主要的共享数据存储有哪些？\n- Which parts of the system are replicated? / 系统的哪些部分被复制？\n- How does data progress through the system? / 数据如何在系统中传输？\n- What parts of the system can run in parallel? / 系统的哪些部分可以并行运行？\n- Can the system's structure change as it executes and,if so,how? / 系统的结构是否可以在执行过程中发生变化？如果可以，如何变化？\n\n使用谷歌的 MapReduce 作为例子来解释组件-连接器结构，可以帮助我们更好地理解组件间如何交互以及它们如何协同完成任务。MapReduce 是一种分布式计算模型，常用于处理大量数据，特别是在大数据分析和处理的场景中。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::965", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Strcutures and Views / 结构和视图/Component-and-connector Structures / 组件-连接器结构", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 160, "text": "duce 作为例子来解释组件-连接器结构，可以帮助我们更好地理解组件间如何交互以及它们如何协同完成任务。MapReduce 是一种分布式计算模型，常用于处理大量数据，特别是在大数据分析和处理的场景中。在分析组件-连接器结构时，MapReduce 的各个部分可以被看作是组件，而它们之间的协作和通信则是通过连接器来实现的。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::966", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Strcutures and Views / 结构和视图/Component-and-connector Structures / 组件-连接器结构/批注：在 MapReduce 的应用", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 367, "text": "MapReduce 主要包含两个阶段：\n\n1. **Map 阶段**：对输入数据进行处理，将其转换为键值对（key-value pairs）。\n2. **Reduce 阶段**：对由 Map 阶段输出的键值对进行合并与汇总。\n\n通过 MapReduce 框架的例子，我们可以看到其典型的组件-连接器结构：\n\n- **组件**：Map 阶段、Shuffle 阶段、Reduce 阶段、任务调度组件等；\n- **连接器**：组件之间的数据传递和协调，如 Map 和 Shuffle 之间的连接、Shuffle 和 Reduce 之间的连接等。\n\n这些组件通过连接器进行高效的协作，共同完成大规模数据处理任务。通过这种架构设计，MapReduce 不仅支持系统功能的实现，还能满足容错、扩展性等重要属性，从而使其成为大数据处理中的重要工具。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::967", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Strcutures and Views / 结构和视图/Component-and-connector Structures / 组件-连接器结构/批注：在 CS, P2P 和 BS 的应用/1. **CS 架构（Client-Server 架构）**", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 166, "text": "- **组件**：在 CS 架构中，客户端（Client）和服务器端（Server）分别作为两个主要的组件。客户端负责发起请求，而服务器端负责响应请求并提供服务。\n- **连接器**：客户端和服务器之间的通信通常通过 **请求/响应协议**（如 HTTP、FTP）来实现。这个协议充当连接器的角色，负责在客户端和服务器之间传递信息。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::968", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Strcutures and Views / 结构和视图/Component-and-connector Structures / 组件-连接器结构/批注：在 CS, P2P 和 BS 的应用/2. **BS 架构（Browser-Server 架构）**", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 166, "text": "- **组件**：在 BS 架构中，主要的组件是 **浏览器（Browser）** 和 **服务器（Server）**。浏览器作为客户端，通过网络与服务器进行交互。\n- **连接器**：浏览器与服务器之间的交互通过 **HTTP 协议**（或其他类似的协议）来完成。HTTP 协议不仅传输请求和响应的数据，也负责数据的格式化和渲染。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::969", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Strcutures and Views / 结构和视图/Component-and-connector Structures / 组件-连接器结构/批注：在 CS, P2P 和 BS 的应用/3. **P2P 架构（Peer-to-Peer 架构）**", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 140, "text": "- **组件**：在 P2P 架构中，所有参与的节点都可以同时作为客户端和服务器。每个节点（Peer）既能发起请求，也能响应请求。\n- **连接器**：节点之间的通信通过 **P2P 协议**（如 BitTorrent、Skype 等）来实现。这种协议确保节点间的数据交换和共享。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::970", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Strcutures and Views / 结构和视图/Component-and-connector Structures / 组件-连接器结构/Some useful C & C Structures/Service structure / 服务结构", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 316, "text": "The units are services that interoperate with each other by service coordination mechanisms such as SOAP. / 这些单元是通过服务协调机制（如SOAP）相互操作的服务。\n\nThe service structure helps to engineer a system composed of components that may have been developed anonymously and independently of each other. / 服务结构有助于构建由可能匿名开发且相互独立的组件组成的系统。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::971", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Strcutures and Views / 结构和视图/Component-and-connector Structures / 组件-连接器结构/Some useful C & C Structures/Service structure / 服务结构/Concurrency structure / 并发结构", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 371, "text": "This structure helps determine opportunities for parallelism and the locations where resource contention may occur. / 该结构有助于确定并行性的机会以及可能发生资源争用的位置。\n\nThe units are components. / 单元是组件。\n\nThe connectors are their communication mechanisms. / 连接器是它们的通信机制。\n\nThe components are arranged into logical threads. / 组件被安排为逻辑线程。\n\n"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::972", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Strcutures and Views / 结构和视图/Allocation Structures / 分配结构", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 634, "text": "**Allocation structures** show the relationship between the software elements and elements in one or more external environments **in which the software is created and executed**. / **分配结构**显示软件元素与一个或多个外部环境中元素之间的关系，这些环境是软件创建和执行的场所。\n**Allocation views** help us answer questions such as these: / **分配视图**帮助我们回答以下问题：\nWhat **processor** does each software element execute on? / 每个软件元素在什么**处理器**上执行？\nIn what directories or **files** is each element stored during development, testing, and system building? / 每个元素在开发、测试和系统构建过程中存储在哪些目录或**文件**中？\nWhat is the assignment of each software element to development **teams**? / 每个软件元素分配给哪些开发**团队**？"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::973", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Strcutures and Views / 结构和视图/Allocation Structures / 分配结构/Some Useful Allocation Structures / 一些有用的分配结构/Deployment Structure / 部署结构", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 699, "text": "The deployment structure shows how software is assigned to hardware processing and communication elements. / 部署结构展示了软件如何分配给硬件处理和通信元素。\n\nThe elements are software elements (usually a process from a C&C view), hardware entities (processors), and communication pathways. / 这些元素包括软件元素（通常是 C&C 视图中的进程）、硬件实体（处理器）和通信通道。\n\nRelations are **allocated-to**, showing on which physical units the software elements reside, and migrates-to if the allocation is dynamic.\n\n关系通过**“分配到”**来表示，展示软件元素所在的物理单元；如果分配是动态的，则通过“迁移到”来表示。\n\nThis structure can be used to reason for performance, data integrity, security, and availability.\n\n该结构可用于推理性能、数据完整性、安全性和可用性。\n\nIt is of particular interest in distributed and parallel systems."}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::974", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Strcutures and Views / 结构和视图/Allocation Structures / 分配结构/Some Useful Allocation Structures / 一些有用的分配结构/Deployment Structure / 部署结构", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 178, "text": "lity.\n\n该结构可用于推理性能、数据完整性、安全性和可用性。\n\nIt is of particular interest in distributed and parallel systems.\n\n在分布式和并行系统中，这一结构尤为重要。\n\n"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::975", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Strcutures and Views / 结构和视图/Allocation Structures / 分配结构/Some Useful Allocation Structures / 一些有用的分配结构/Deployment Structure / 部署结构/Implementation structure / 实现结构", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 288, "text": "This structure shows how software elements (usually modules) are mapped to **the file structure(s)** in the system's development, integration, or configuration control environments.\n\n该结构展示了软件元素（通常是模块）如何映射到系统的开发、集成或配置控制环境中的**文件结构。**\n\n"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::976", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Strcutures and Views / 结构和视图/Allocation Structures / 分配结构/Some Useful Allocation Structures / 一些有用的分配结构/Deployment Structure / 部署结构/Work assignment structure / 工作分配结构", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 155, "text": "This structure assigns responsibility for implementing and integrating the modules to the **teams** who will carry it out. / 该结构将模块的实现和集成责任分配给将负责执行的**团队**。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::977", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Strcutures and Views / 结构和视图/Structures provide insight / 结构提供灵感", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 686, "text": "Each structure provides a perspective for reasoning about some of the relevant quality attributes. / 每个结构提供了一种视角，用于推理系统的一些相关质量属性。\nFor example: / 例如：\nThe module structure, which embodies what modules use what other modules, is strongly tied to the ease with which a system can be extended. / 模块结构体现了哪些模块使用了其他模块，它与系统扩展的难易程度密切相关。\nThe concurrency structure, which embodies parallelism within the system, is strongly tied to the ease with which a system can be made free of deadlock and performance bottlenecks. / 并发结构体现了系统内部的并行性，它与系统避免死锁和性能瓶颈的难易程度密切相关。\nThe deployment structure is strongly tied to the achievement of performance, availability, and security goals. / 部署结构与实现性能、可用性和安全性目标密切相关。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::978", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Strcutures and Views / 结构和视图/Relating Structures to Each other / 结构之间相互关联", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 483, "text": "Elements of one structure will be related to elements of other structures, and we need to reason about these relations. / 一个结构的元素将与其他结构的元素相关，我们需要推理这些关系。\n\n- A module in a decomposition structure may be manifested as one, part of one, or several components in one of the component-and-connector structures. / 分解结构中的模块可能表现为组件和连接器结构中的一个组件、一个组件的一部分或多个组件。\n\nIn general, mappings between strucures are many to many. / 通常，结构之间的映射是多对多的。\n\n"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::979", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Architectural Patterns / 架构模式", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 680, "text": "An **architectural pattern** presents the element types and their forms of interaction used in solving a particular problem. / 架构模式呈现了解决特定问题时所使用的元素类型及其交互形式。\nA common **module type pattern** is the Layered pattern. / 一种常见的模块类型模式是分层模式。\n\n- When the usage of software elements is strictly unidirectional, a system of layers emerges. / 当软件元素之间的使用关系严格单向时，分层系统就会出现。\n- A layer is a coherent set of related functionality. / 一层是一个相关功能的连贯集合。\n\nCommon **component-and-connector type patterns**: / 常见的组件和连接器类型模式：\n\n- Shared-data (or repository) pattern. / 共享数据（或仓库）模式。\n① This pattern comprises components and connectors that create, store, and access persistent data. / 该模式包含创建、存储和访问持久数据的组件和连接器。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::980", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Architectural Patterns / 架构模式", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 640, "text": "mponents and connectors that create, store, and access persistent data. / 该模式包含创建、存储和访问持久数据的组件和连接器。\n② The repository usually takes the form of a (commercial) database. / 仓库常采用（商业）数据库的形式。\n③ The connectors are protocols for managing the data, such as SQL. / 连接器用于管理数据的协议（SQL）\nCommon **component-and-connector type patterns**: / 常见的组件和连接器类型模式：\n\n \n- Client-server pattern. / 客户端-服务器模式。\n\n - The components are the clients and the servers. / 组件是客户端和服务器。\n - The connectors are protocols and messages they share among each other to carry out the system's work. / 连接器是它们之间共享的协议和消息，用于完成系统的工作。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::981", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Architectural Patterns / 架构模式", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 642, "text": "messages they share among each other to carry out the system's work. / 连接器是它们之间共享的协议和消息，用于完成系统的工作。\n- Peer-to-peer pattern / 点对点模式Common **allocation patterns**: / 常见的分配模式：\n\n - E.g. Bittorrent, eMule / 例如，Bittorrent，eMule\n- Multi-tier pattern / 多层模式\n\n - This pattern specializes in the generic deployment (software-to-hardware allocation) structure. / 该模式专门化了通用的部署（软件到硬件分配）结构。\n - Describes how to distribute and allocate the components of a system in distinct subsets of hardware and software, connected by some communication medium. / 描述如何将系统的组件分配到不同的硬件和软件子集，并通过某种通信媒介将它们连接起来。\n- Competence center pattern and platform pattern / 能力中心模式与平台模式"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::982", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Architectural Patterns / 架构模式", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 627, "text": "统的组件分配到不同的硬件和软件子集，并通过某种通信媒介将它们连接起来。\n- Competence center pattern and platform pattern / 能力中心模式与平台模式\n\n - These patterns specialize in a software system's work assignment structure. / 这些模式专门化了软件系统的工作分配结构。\n - In competence center, work is allocated to sites depending on the technical or domain expertise located at a site. / 在能力中心，工作根据各站点的技术或领域专长进行分配。\n - In platform, one site is tasked with developing **reusable core assets** of a software product line, and other sites develop applications that use the core assets. / 在平台模式中，一个站点负责开发软件产品线的可重用核心资产，其他站点开发使用这些核心资产的应用程序。\n\n"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::983", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Rules of Thumb makes \"Good\" Architecture / 经验法则创造了好的架构/**Process “Rules of Thumb”** / 过程“经验法则”", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 604, "text": "Architecture should be the product of a single architect or a small group of architects with an identified technical leader. / 架构应由一名架构师或一个由明确技术领导者领导的小组架构师团队完成。\nThe architect (or architecture team) should base the architecture on a prioritized list of well-specified quality attribute requirements. / 架构师（或架构团队）应基于优先排序的明确质量属性需求列表来构建架构。\nThe architecture should be documented using views. / 架构应通过视图文档化。\nArchitecture should be evaluated for its ability to deliver the system's important quality attributes. / 应评估架构在提供系统重要质量属性方面的能力。\nArchitecture should lend itself to incremental implementation. / 架构应便于增量实现。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::984", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Rules of Thumb makes \"Good\" Architecture / 经验法则创造了好的架构/**Structural “Rules of Thumb”** / 结构“经验法则”", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 699, "text": "The architecture should feature well-defined modules. / 架构应具有明确定义的模块。\nThe architecture should never depend on a particular version of a commercial product or tool. / 架构不应依赖于特定版本的商业产品或工具。\nModules that produce data should be separate from modules that consume data. / 产生数据的模块应与消耗数据的模块分离。\n\n- This tends to increase modifiability. / 这有助于提高可修改性。\n\nDon't expect a one-to-one correspondence between modules and components. / 不要期望模块与组件之间存在一一对应关系。\nEvery process should be written so that its assignment to a specific processor can be easily changed, perhaps even at runtime. / 每个进程应编写成可以轻松地分配到特定处理器，甚至在运行时改变。\nThe architecture should feature a small number of ways for components to interact. / 架构应具有少量的组件交互方式。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::985", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Rules of Thumb makes \"Good\" Architecture / 经验法则创造了好的架构/**Structural “Rules of Thumb”** / 结构“经验法则”", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 189, "text": "he architecture should feature a small number of ways for components to interact. / 架构应具有少量的组件交互方式。\n\n- The system should do the same things in the same way throughout. / 系统应始终以相同的方式执行相同的操作。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::986", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Summary / 总结", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::987", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Summary / 总结/What is software architecture ? / 什么是软件架构？", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 486, "text": "**The software architecture** of a system is the set of structures needed to reason about the system, which comprise software elements, relations among them, and properties of both. / 系统的软件架构是为系统进行推理所需的一组结构，包含软件元素、它们之间的关系以及两者的属性。\n\n**A structure** is a set of elements and their relations among them. / 结构是一组元素及其之间的关系。\n**A view** is a representation of a coherent set of architectural elements. A view is a representation of one or more structures. / 视图是一个连贯的架构元素集合的表现形式。视图是一个或多个结构的表现形式。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::988", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Summary / 总结/**Some Useful Structures** / 一些有用的结构/Module Structures / 模块结构", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 125, "text": "- Decomposition structure / 分解结构\n- User structure -> layer pattern / 用户结构 -> 分层模式\n- Class structure / 类结构\n- Data model / 数据模型"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::989", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Summary / 总结/**Some Useful Structures** / 一些有用的结构/Component-and-connector structures / 组件与连接器结构", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 57, "text": "- Service structure / 服务结构\n- Concurrency structure / 并发结构"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::990", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Summary / 总结/**Some Useful Structures** / 一些有用的结构/Allocation structures / 分配结构", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 100, "text": "- Deployment structure / 部署结构\n- Implementation structure / 实现结构\n- Work assignment structure / 工作分配结构"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::991", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 01 What is Software Architecture? / 第一章 什么是软件架构？/Summary / 总结/**Architectural Patterns** / 架构模式", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 352, "text": "- Module type pattern / 模块类型模式\n\n - Layered pattern / 分层模式\n- Component-and-connector type pattern / 组件与连接器类型模式\n\n - Shared data pattern / 共享数据模式\n - Client and server pattern / 客户端-服务器模式\n - Peer to peer pattern / 点对点模式\n- Allocation type pattern / 分配类型模式\n\n - Multi-tier pattern / 多层模式\n - Competence center pattern / 能力中心模式\n - Platform pattern / 平台模式"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::992", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 02 Why is Software Architecture Important? / 第二章 为什么软件架构重要？", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 656, "text": "##\n**Inhibiting or Enabling a System's Quality Attributes** / 抑制或促进系统的质量属性\n\nWhether a system will be able to exhibit its desired (or required) quality attributes is substantially determined by its architecture. / 系统是否能够展现其期望（或要求的）质量属性在很大程度上取决于其架构。\n\n- Performance / 性能\n- Modifiability / 可修改性\n- Security / 安全性\n- Scalability / 可扩展性\n- Reusability / 可重用性\n\nAbout 80 percent of a typical software system's total cost occurs after initial deployment: accommodate new features, adapt to new environments, fix bugs, and so forth. / 典型软件系统的总成本中约80％发生在初始部署之后：包括适应新功能、适应新环境、修复缺陷等。\n\nEvery architecture partitions possible changes into three categories: / 每个架构将可能的变化分为三类："}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::993", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 02 Why is Software Architecture Important? / 第二章 为什么软件架构重要？", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 600, "text": "环境、修复缺陷等。\n\nEvery architecture partitions possible changes into three categories: / 每个架构将可能的变化分为三类：\n\n- A *local change* can be accomplished by modifying a single element. / *本地变更* 可以通过修改单个元素来实现。\n- A *nonlocal change* requires multiple element modifications but leaves the underlying architectural approach intact. / *非本地变更* 需要修改多个元素，但不会改变底层的架构方法。\n- *Architectural change* affects the fundamental ways in which the elements interact with each other and will require changes all over the system. / *架构变更* 影响元素之间相互作用的基本方式，必须对整个系统进行变更。\n\n**Obviously, local changes are the most desirable. / 显然，本地变更是最理想的。**"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::994", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 02 Why is Software Architecture Important? / 第二章 为什么软件架构重要？", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 227, "text": "影响元素之间相互作用的基本方式，必须对整个系统进行变更。\n\n**Obviously, local changes are the most desirable. / 显然，本地变更是最理想的。**\n\nA good architecture is one in which the most common changes are local, and hence easy to make. / 一个好的架构是那些最常见的变更是局部的，因此容易实现的架构。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::995", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 02 Why is Software Architecture Important? / 第二章 为什么软件架构重要？/**Predicting System Qualities** / 预测系统的质量", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 540, "text": "When we examine an architecture, we can confidently predict that the architecture will exhibit the associated qualities. / 当我们审查架构时，可以自信地预测该架构将表现出相关的质量属性。\nThe earlier you can find a problem with your design, the cheaper, easier, and less disruptive it will be to fix. / 你越早发现设计中的问题，修复起来就会越便宜、越容易，且对系统的影响越小。\n\n##\n**Enhancing Communication Among Stakeholders** / 增强利益相关者之间的沟通\n\n- The architecture — or at least parts of it — is sufficiently abstract that most non-technical stakeholders can understand. / 架构——或至少是其部分——具有足够的抽象性，足以让大多数非技术利益相关者理解。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::996", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 02 Why is Software Architecture Important? / 第二章 为什么软件架构重要？/**Predicting System Qualities** / 预测系统的质量", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 483, "text": "ract that most non-technical stakeholders can understand. / 架构——或至少是其部分——具有足够的抽象性，足以让大多数非技术利益相关者理解。\n- Most of the system's stakeholders can use it as a basis for creating mutual understanding, negotiating, forming consensus, and communicating with each other. / 系统的大多数利益相关者可以将其作为建立共同理解、协商、形成共识并相互沟通的基础。\n- Each stakeholder of a software system is concerned with different characteristics of the system. / 软件系统的每个利益相关者关注系统的不同特性。\n\n - Users, clients, managers, architects / 用户、客户、经理、架构师"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::997", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 02 Why is Software Architecture Important? / 第二章 为什么软件架构重要？/**Earliest Design Decisions** / 最早的设计决策", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 685, "text": "Software architecture is a manifestation of the earliest design decisions about a system. / 软件架构是系统最早设计决策的体现。\nThese early decisions affect the system's remaining development, its deployment, and its maintenance life. / 这些早期决策影响系统的后续开发、部署和维护生命周期。\n What are these early design decisions? / 这些早期设计决策是什么？\n\n- Will the system run on one processor or be distributed across multiple processors? / 系统将在一个处理器上运行，还是分布在多个处理器上？\n- Will the software be layered? If so, how many layers will there be? / 软件是否采用分层结构？如果是，有多少层？\n- What will each one do? / 每一层将执行什么功能？\n- Will components communicate synchronously or asynchronously? / 组件将同步还是异步通信？\n- What communication protocol will we choose? / 我们将选择什么通信协议？"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::998", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 02 Why is Software Architecture Important? / 第二章 为什么软件架构重要？/**Earliest Design Decisions** / 最早的设计决策", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 295, "text": "usly or asynchronously? / 组件将同步还是异步通信？\n- What communication protocol will we choose? / 我们将选择什么通信协议？\n- Will the system depend on specific features of the operating system or hardware? / 系统是否依赖于操作系统或硬件的特定功能？\n- Will the information that flows through the system be encrypted or not? / 流经系统的信息是否会加密？"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::999", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 02 Why is Software Architecture Important? / 第二章 为什么软件架构重要？/**Defining Constraints on an Implementation** / 定义对实现的约束", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 421, "text": "An implementation exhibits an architecture if it conforms to the design decisions prescribed by the architecture. / 如果实现遵循架构所规定的设计决策，则该实现体现了架构。\n\n- The implementation must be implemented as the set of prescribed elements. / 实现必须作为规定元素的集合来实施。\n- These elements must interact with each other in the prescribed fashion. / 这些元素必须以规定的方式相互作用。\n\nEach of these prescriptions is a constraint on the implementer. / 这些规定中的每一项都是对实现者的约束。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::1000", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 02 Why is Software Architecture Important? / 第二章 为什么软件架构重要？/**Influencing the Organizational Structure** / 影响组织结构", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 188, "text": "Architecture prescribes the structure of the system being developed. / 架构规定了正在开发的系统的结构。\nThe architecture is typically used as the basis for the work-breakdown structure. / 架构通常作为工作分解结构的基础。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::1001", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 02 Why is Software Architecture Important? / 第二章 为什么软件架构重要？/**Enabling Evolutionary Prototyping** / 启用演化原型开发", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 698, "text": "Once an architecture has been defined, it can be prototyped as a skeletal system. / 一旦架构被定义，它就可以作为骨架系统进行原型开发。\nA skeletal system is one in which at least some of the infrastructure is built before much of the system's functionality has been created. / 骨架系统是在系统的许多功能尚未创建之前，至少构建了部分基础设施的系统。\nThe fidelity of the system increases as prototype parts are replaced with complete versions of these parts. / 随着原型部分被完整版本替换，系统的保真度提高。\nThis approach aids the development process because the system is executable early in the product's life cycle. / 这种方法有助于开发过程，因为系统在产品生命周期早期就可以执行。\nThis approach allows potential performance problems to be identified early in the product's life cycle. / 这种方法允许在产品生命周期的早期识别潜在的性能问题。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::1002", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 02 Why is Software Architecture Important? / 第二章 为什么软件架构重要？/**Enabling Evolutionary Prototyping** / 启用演化原型开发", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 657, "text": "rformance problems to be identified early in the product's life cycle. / 这种方法允许在产品生命周期的早期识别潜在的性能问题。\nThese benefits reduce the potential risk in the project. / 这些好处降低了项目的潜在风险。\n\n##\n**Improving Cost and Schedule Estimates** / 改进成本和进度估算\n\nArchitecture is used to help the project manager create cost and schedule estimates early in the project life cycle. / 架构用于帮助项目经理在项目生命周期早期制定成本和进度估算。\nTop-down estimates are useful for setting goals and apportioning budgets. / 自上而下的估算有助于设定目标和分配预算。\nBottom-up understanding of the system's pieces are typically more accurate than those that are based purely on top-down system knowledge. / 对系统各部分的自下而上的理解通常比纯粹依赖自上而下系统知识的估算更为准确。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::1003", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 02 Why is Software Architecture Important? / 第二章 为什么软件架构重要？/**Enabling Evolutionary Prototyping** / 启用演化原型开发", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 368, "text": "n those that are based purely on top-down system knowledge. / 对系统各部分的自下而上的理解通常比纯粹依赖自上而下系统知识的估算更为准确。\nThe best cost and schedule estimates will typically emerge from a consensus between the top-down estimates (created by the architect and project manager) and the bottom-up estimates (created by the developers). / 最佳的成本和进度估算通常来自自上而下估算（由架构师和项目经理制定）与自下而上估算（由开发人员制定）之间的共识。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::1004", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 02 Why is Software Architecture Important? / 第二章 为什么软件架构重要？/**Transferable, Reusable Model** / 可转移、可重用的模型", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 424, "text": "Reuse of architectures provides tremendous benefits for systems with similar requirements. / 架构的重用为具有相似需求的系统提供了巨大的好处。\n\n- Not only can code be reused, but also can the requirements that led to the architecture in the first place. / 不仅代码可以重用，最初导致架构设计的需求也可以重用。\n- When architectural decisions can be reused across multiple systems, all of the early-decision consequences are also transferred. / 当架构决策可以在多个系统中重用时，所有早期决策的后果也会随之转移。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::1005", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 02 Why is Software Architecture Important? / 第二章 为什么软件架构重要？/**Using Independently Developed Components** / 使用独立开发的组件", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 503, "text": "Architecture-based development often focuses on components that are likely to have been developed separately, even independently. / 基于架构的开发通常关注那些可能已被单独开发，甚至独立开发的组件。\nCommercial off-the-shelf components, open source software, publicly available apps, and networked services are examples of interchangeable software components. / 商用现成组件、开源软件、公开可用的应用程序和网络服务是可替换软件组件的例子。\n The payoff can be: / 收益可能是：\n\n- Decreased time to market / 缩短上市时间\n- Increased reliability / 提高可靠性\n- Lower cost / 降低成本\n- Flexibility / 灵活性"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::1006", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 02 Why is Software Architecture Important? / 第二章 为什么软件架构重要？/**Restricting Design Vocabulary** / 限制设计词汇", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 537, "text": "As useful architectural patterns are collected, we see the benefit in restricting ourselves to a relatively small number of choices of elements and their interactions. / 随着有用的架构模式的收集，我们发现限制选择较少的元素及其相互作用具有很大的好处。\n\n- We minimize the design complexity of the system we are building. / 我们最小化正在构建的系统的设计复杂度。\n- Enhanced reuse / 增强重用性\n- More regular and simpler designs that are more easily understood and communicated / 更规则、更简单的设计，更易于理解和沟通\n- More capable analysis / 更强的分析能力\n- Shorter selection time / 更短的选择时间\n- Greater interoperability / 更强的互操作性"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::1007", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 02 Why is Software Architecture Important? / 第二章 为什么软件架构重要？/**Basis for Training** / 培训基础", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 422, "text": "Architecture can serve as the first introduction to the system for new project members. / 架构可以作为新项目成员对系统的首次介绍。\n\n- Module views show someone the structure of a project: / 模块视图向人员展示项目的结构：\n\n - Who does what, which teams are assigned to which parts of the system, and so forth. / 谁做什么，哪些团队被分配到系统的哪些部分，等等。\n- Component-and-connector explains how the system is expected to work and accomplish its job. / 组件与连接器解释了系统如何预期工作并完成其任务。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::1008", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 02 Why is Software Architecture Important? / 第二章 为什么软件架构重要？/Summary / 总结", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 690, "text": "软件架构重要总共有十三点原因\n\n**英文原文：**\n\n1. Architecture will inhibit or enable a system's driving quality attributes. / 架构将抑制或促进系统的关键质量属性。\n2. The decisions made in architecture allow you to reason about and manage change as the system evolves. / 架构中的决策使您能够在系统发展过程中推理并管理变化。\n3. The analysis of architecture enables early prediction of a system's qualities. / 对架构的分析使得能够提前预测系统的质量。\n4. A documented architecture enhances communication among stakeholders. / 文档化的架构增强了利益相关者之间的沟通。\n5. Architecture is a carrier of the earliest and hence most fundamental, hardest-to-change design decisions. / 架构承载了最早且最根本、最难更改的设计决策。\n6. An architecture defines a set of constraints on subsequent implementation. / 架构定义了一组对后续实现的约束。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::1009", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 02 Why is Software Architecture Important? / 第二章 为什么软件架构重要？/Summary / 总结", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 568, "text": "策。\n6. An architecture defines a set of constraints on subsequent implementation. / 架构定义了一组对后续实现的约束。\n7. The architecture dictates the structure of an organization, or vice versa. / 架构决定了组织的结构，反之亦然。\n8. An architecture can provide the basis for evolutionary prototyping. / 架构可以为演化原型提供基础。\n9. Architecture is the key artifact that allows the architect and project manager to reason about cost and schedule. / 架构是架构师和项目经理推理成本和进度的关键产物。\n10. Architecture can be created as a transferable, reusable model that forms the heart of a product line. / 架构可以作为一个可转移、可重用的模型创建，并成为产品线的核心。"}
{"id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc::1010", "page_id": "docx::CEG7wQCc2iC9XSkesXTclXZynAc", "title": "SA 讲义（一） Chapter 01, 02 Introduction", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（一） Chapter 01, 02 Introduction", "section": "Chapter 02 Why is Software Architecture Important? / 第二章 为什么软件架构重要？/Summary / 总结", "url": "https://a1npn29y3xu.feishu.cn/wiki/CEG7wQCc2iC9XSkesXTclXZynAc", "source_type": "docx", "n_chars": 511, "text": "nsferable, reusable model that forms the heart of a product line. / 架构可以作为一个可转移、可重用的模型创建，并成为产品线的核心。\n11. Architecture-based development focuses attention on the assembly of components, rather than simply on their creation. / 基于架构的开发将重点放在组件的组装上，而不仅仅是它们的创建。\n12. By restricting design alternatives, architecture channels the creativity of developers, reducing design and system complexity. / 通过限制设计选项，架构引导开发者的创造力，减少设计和系统复杂性。\n13. Architecture can be the foundation for training a new team member. / 架构可以作为培训新团队成员的基础。"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1011", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "Chapter 13 Patterns and Tactics / 第十三章：模式和策略", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 165, "text": "Also checkout 思维导图版: \n\n"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1012", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "Chapter 13 Patterns and Tactics / 第十三章：模式和策略/What is a Pattern? / 什么是模式？", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 341, "text": "- An architectural pattern is a package of design decisions that is found repeatedly in practice. / 一种架构模式是一种在实践中被反复发现的设计决策包\n- Has known properties that permit reuse and describe a class of architecture. / 具有允许重用的已知属性，并描述一类体系结构\n\n\n\n"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1013", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "Chapter 13 Patterns and Tactics / 第十三章：模式和策略/Architectural Patterns / 架构模式", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1014", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "Chapter 13 Patterns and Tactics / 第十三章：模式和策略/Layer Pattern / 分层模式", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 645, "text": "\n\n- Context: Modules of the system may be independently developed and maintained. / 上下文：系统的模块可以独立开发和维护。\n- Problem: To minimize the interaction among the different development organizations, and support portability, modifiability, and reuse. / 问题： 最小化不同开发组织之间的交互，并支持可移植性、可修改性和重用性。\n- The layered pattern divides the software into units called layers. / 分层的模式把软件分成了层级单元\n- Each layer is a grouping of modules that offers a cohesive set of services. / 每一层都是一组模块，提供一组内聚的服务\n- Each layer is exposed through a public **interface**. / 每一层都通过一个公用的接口暴露出来\n- The usage must be unidirectional. / 使用必须是非定向的"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1015", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "Chapter 13 Patterns and Tactics / 第十三章：模式和策略/Layer Pattern / 分层模式", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 155, "text": "hrough a public **interface**. / 每一层都通过一个公用的接口暴露出来\n- The usage must be unidirectional. / 使用必须是非定向的\n\n"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1016", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "Chapter 13 Patterns and Tactics / 第十三章：模式和策略/Layer Pattern / 分层模式/Solution / 解决方案", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 504, "text": "• The layered pattern defines layers and a unidirectional allowed-to-use relation among the layers. / 分层模式定义层以及层之间的单向允许使用关系\n\n• Constraints: / 约束\n\n– Every piece of software is allocated to exactly one layer. / 每一个软件都只分配给一个层\n\n– There are at least two layers. / 至少存在两层\n\n– The allowed-to-use relations should not be circular. / 允许使用的关系不应该是循环的\n\n• Weaknesses: / 弱点\n\n– The addition of layers adds up cost and complexity to a system. / 添加层会增加系统的成本和复杂性\n\n– Layers contribute a performance penalty. / 图层会导致性能下降"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1017", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "Chapter 13 Patterns and Tactics / 第十三章：模式和策略/Layer Pattern / 分层模式/3 Layered Applications : JavaWeb / 三层架构： 以 JavaWeb 为例子", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 226, "text": "\n\n\n\n\n\n"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1018", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "Chapter 13 Patterns and Tactics / 第十三章：模式和策略/Component-and-Connector Structure / 组件连接器结构", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 365, "text": "- Component-and-Connector patterns / 组件-连接器模式\n\n - Broker pattern / 经纪人模式\n - Model-View-Controller pattern / 模型-视图-控制器模式\n - Pipe-and-Filter pattern / 管道-过滤器模式\n - Client-Server pattern / 客户端-服务器模式\n - Peer-to-Peer pattern / 对等网络模式\n - Service-Oriented Architecture (SOA) pattern / 面向服务的架构模式\n - Publish-Subscribe pattern / 发布-订阅模式\n - Shared-Data pattern / 共享数据模式"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1019", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "Chapter 13 Patterns and Tactics / 第十三章：模式和策略/Component-and-Connector Structure / 组件连接器结构/Broker Pattern / 经纪人模式", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 688, "text": "- Context: Many systems are constructed from a collection of services distributed across multiple servers / 背景：许多系统由分布在多个服务器上的一系列服务构成。\n- Problem: How do we structure distributed software so that service users do not need to know the nature and location of service providers? / 问题：我们如何构建分布式软件，使得服务用户不需要知道服务提供者的性质和位置？\n- Solution: The broker pattern separates clients from providers servers by inserting an intermediary, called a broker. / 解决方案：经纪人模式通过插入一个名为经纪人的中介来将客户端与提供服务器分开。\n- **Overview:** The broker pattern defines a runtime component, called a broker, that mediates the communication between a number of clients and servers. / **概览：**经纪人模式定义了一个运行时组件，称为经纪人（broker），它在多个客户端和服务器之间调解通信。"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1020", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "Chapter 13 Patterns and Tactics / 第十三章：模式和策略/Component-and-Connector Structure / 组件连接器结构/Broker Pattern / 经纪人模式", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 615, "text": "between a number of clients and servers. / **概览：**经纪人模式定义了一个运行时组件，称为经纪人（broker），它在多个客户端和服务器之间调解通信。\n- **Elements: / 元素：**\n\n - *Client*, a requester of services / *客户端*：服务的请求者。\n - *Server*, a provider of services / *服务器*：服务的提供者。\n - *Broker*, an intermediary that locates an appropriate server to fulfill a client’s request, forwards the request to the server, and returns the results to the client / *经纪人*：中介，定位合适的服务器以满足客户端的请求，将请求转发给服务器，并将结果返回给客户端。\n- **Constraints**: The client can only attach to a broker. The server can only attach to a broker. / **约束**：客户端只能连接到经纪人。服务器也只能连接到经纪人。\n- **Weaknesses**: / **弱点**："}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1021", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "Chapter 13 Patterns and Tactics / 第十三章：模式和策略/Component-and-Connector Structure / 组件连接器结构/Broker Pattern / 经纪人模式", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 416, "text": "rver can only attach to a broker. / **约束**：客户端只能连接到经纪人。服务器也只能连接到经纪人。\n- **Weaknesses**: / **弱点**：\n\n - Brokers add latency between clients and servers, and it may be a communication bottleneck. / 经纪人在客户端和服务器之间增加了延迟，并且可能是通信瓶颈。\n - The broker can be a single point of failure. / 经纪人可能是单点故障。\n - A broker may be a target for security attacks. / 经纪人可能是安全攻击的目标。\n\n"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1022", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "Chapter 13 Patterns and Tactics / 第十三章：模式和策略/Component-and-Connector Structure / 组件连接器结构/Model-View-Controller Pattern / MVC 模式", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 559, "text": "- Context: User interface software is the most frequently modified portion of an interactive application. / 背景：用户界面软件是交互式应用程序中最常被修改的部分。\n- Problem: How can user interface functionality be kept separate from application functionality and yet still be responsive to user input, or to changes in the underlying application’s data? / 问题：如何将用户界面功能与应用程序功能分开，同时仍然能够响应用户输入，或底层应用程序数据的变化？\n- And how can **multiple views of the user interface** be created, maintained, and coordinated when the underlying application data changes? / 以及如何在底层应用程序数据变化时创建、维护和协调**用户界面的多个视图**？"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1023", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "Chapter 13 Patterns and Tactics / 第十三章：模式和策略/Component-and-Connector Structure / 组件连接器结构/Model-View-Controller Pattern / MVC 模式", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 657, "text": "coordinated when the underlying application data changes? / 以及如何在底层应用程序数据变化时创建、维护和协调**用户界面的多个视图**？\n- **Solution**: The model-view-controller (MVC) pattern separates application functionality into three kinds of components: / **解决方案**：模型-视图-控制器（MVC）模式将应用程序功能分为三种组件：\n\n - A **model**, which contains the application’s data / 一个模型，包含应用程序的数据\n - A **view**, which displays some portion of the underlying data and interacts with the user / 一个视图，显示部分底层数据并与用户交互\n - A **controller**, which mediates between the model and the view and manages the notifications of state changes / 一个控制器，它在模型和视图之间调解，并管理状态变化的通知\n\n"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1024", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "Chapter 13 Patterns and Tactics / 第十三章：模式和策略/Component-and-Connector Structure / 组件连接器结构/Example: SpringMVC / 以 Java 后端框架为例/Controller / 控制器", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 539, "text": "```Java\npackage com.example;\n\nimport org.springframework.stereotype.Controller;\nimport org.springframework.ui.Model;\nimport org.springframework.web.bind.annotation.GetMapping;\nimport org.springframework.web.bind.annotation.RequestParam;\n\n@Controller\npublic class HelloController {\n\n @GetMapping(\"/hello\")\n public String sayHello(@RequestParam(name = \"name\", required = false, defaultValue = \"World\") String name,\n Model model) {\n model.addAttribute(\"message\", \"Hello \" + name + \"!\");\n return \"hello\";\n }\n}\n```"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1025", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "Chapter 13 Patterns and Tactics / 第十三章：模式和策略/Component-and-Connector Structure / 组件连接器结构/Example: SpringMVC / 以 Java 后端框架为例/View / 视图", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 44, "text": "```Java\n\n Hello Page\n\n ${message}\n\n```"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1026", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "Chapter 13 Patterns and Tactics / 第十三章：模式和策略/Component-and-Connector Structure / 组件连接器结构/Example: SpringMVC / 以 Java 后端框架为例/Model / 模型", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 333, "text": "这个示例中，模型（Model）并不是一个具体的类文件，而是通过控制器方法参数 `Model` 和在 JSP 视图中使用 EL 表达式 `${message}` 来体现的。这种方式使得控制器和视图之间可以方便地传递数据。\n\n• **Constraints**:\n\nThere must be at least one instance for each model, view, and controller. / MVC 必须各自得至少有一个实例\n\n• **Weaknesses**:\n\nThe complexity may not be worth it for simple user interfaces. / 对于简单的用户接口，这种复杂度也许并不值得使用"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1027", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "Chapter 13 Patterns and Tactics / 第十三章：模式和策略/Component-and-Connector Structure / 组件连接器结构/Pipe and Filter Pattern / 管道与过滤模式", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 580, "text": "\n\n- **Context:** Streaming data processing / **背景：**流数据的处理\n- **Problem:** How to speed up data processing? / **问题：**如何加快数据处理速度？\n- **Solution:** Data arrives at a filter’s input port, is transformed, and then is passed via its output port through a pipe to the next filter. / **解决方案：**数据到达过滤器的输入端口，被转换后，然后通过其输出端口通过管道传递给下一个过滤器。\n\n - A single filter can consume data from, or produce data to, one or more ports. / 单个过滤器可以从一个或多个端口消费数据，或向一个或多个端口产生数据。\n\n\n\n- **Elements: / 元素：**"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1028", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "Chapter 13 Patterns and Tactics / 第十三章：模式和策略/Component-and-Connector Structure / 组件连接器结构/Pipe and Filter Pattern / 管道与过滤模式", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 591, "text": "费数据，或向一个或多个端口产生数据。\n\n\n\n- **Elements: / 元素：**\n\n - *Filter,* which is a component that transforms data read on its input port to data written on its output port. / 过滤器，这是一个组件，它将其输入端口读取的数据转换为写在其输出端口的数据。\n - *Pipe,* which is a connector that conveys data from a filter’s output port to another filter’s input port. / 管道，这是一个连接器，它将数据从一个过滤器的输出端口传递到另一个过滤器的输入端口。\n- **Relations: / 关系：**\n\n - The *attachment* relation associates the output of filters with the input of pipes and vice versa. / 连接关系将过滤器的输出与管道的输入以及反之亦然相关联。\n- **Constraints: / 约束：**"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1029", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "Chapter 13 Patterns and Tactics / 第十三章：模式和策略/Component-and-Connector Structure / 组件连接器结构/Pipe and Filter Pattern / 管道与过滤模式", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 221, "text": "ers with the input of pipes and vice versa. / 连接关系将过滤器的输出与管道的输入以及反之亦然相关联。\n- **Constraints: / 约束：**\n\n - Connected filters must agree on the type of data being passed along the connecting pipe. / 连接的过滤器必须就沿连接管道传递的数据类型达成一致。"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1030", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "过滤器1：将输入的字符串转换为大写", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 90, "text": "def to_upper(input_generator):\n for data in input_generator:\n yield data.upper()"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1031", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "过滤器2：过滤掉空字符串", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 107, "text": "def filter_empty(input_generator):\n for data in input_generator:\n if data:\n yield data"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1032", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "数据源", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 77, "text": "def data_source():\n yield from [\"hello\", \"world\", \"\", \"streaming\", \"data\"]"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1033", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "管道和过滤器的连接", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 225, "text": "def pipe_and_filter(data_source):\n # 将数据源连接到第一个过滤器\n upper_generator = to_upper(data_source())\n # 将第一个过滤器的输出连接到第二个过滤器\n filtered_generator = filter_empty(upper_generator)\n # 返回最终的生成器\n return filtered_generator"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1034", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "使用管道和过滤器处理数据", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 96, "text": "if __name__ == \"__main__\":\n for data in pipe_and_filter(data_source):\n print(data)\n```"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1035", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "使用管道和过滤器处理数据/Client-Server Pattern / 客户端-服务器 模式", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 680, "text": "\n\n- **Context:** There are *shared resources and services* that large numbers of distributed clients wish to access, and for which we wish to *control access or quality of service*. / 背景：存在许多分布式客户端希望访问的共享资源和服务，我们希望控制这些资源和服务的访问或服务质量。\n- **Problem:** To improve availability by *centralizing the control* of these resources and services. / 问题：通过集中控制这些资源和服务来提高可用性。\n- **Solution:** Clients interact by requesting services of servers. / 解决方案：客户端通过请求服务器的服务进行交互。\n- There may be one central server or multiple distributed ones. / 可能有一个中央服务器或多个分布式服务器。\n- **Weaknesses: / 弱点：**\n\n - Server can be a performance bottleneck. / 服务器可能成为性能瓶颈。"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1036", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "使用管道和过滤器处理数据/Client-Server Pattern / 客户端-服务器 模式", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 356, "text": "中央服务器或多个分布式服务器。\n- **Weaknesses: / 弱点：**\n\n - Server can be a performance bottleneck. / 服务器可能成为性能瓶颈。\n - Server can be a single point of failure. / 服务器可能是单点故障。\n - Decisions about where to locate functionality **(in the client or in the server)** are often complex and costly to change after a system has been built. / 在客户端或服务器中定位功能的决定通常是复杂的，并且在系统建成后更改成本很高。"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1037", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "使用管道和过滤器处理数据/Client-Server Pattern / 客户端-服务器 模式/Peer-to-Peer Pattern / P2P模式", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 587, "text": "\n\n- **Problem:** How can a set of “equal” distributed computational entities be connected to each other via a common protocol, such that they can organize and share their services with high availability and scalability? / 问题：如何将一组“平等”的分布式计算实体通过一个共同的协议连接在一起，使它们能够组织和共享服务，具有高可用性和可扩展性？\n\n - 解决方案涉及使用点对点（P2P）模式，其中组件直接作为对等体进行交互。所有对等体都是“平等”的。点对点通信通常是请求/回复交互，与客户端-服务器模式中的不对称性不同。\n- **Solution:** In the peer-to-peer (P2P) pattern, components directly interact as peers. All peers are “equal”. / 解决方案：在点对点（P2P）模式中，组件直接作为对等体进行交互。所有对等体都是“平等”的。"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1038", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "使用管道和过滤器处理数据/Client-Server Pattern / 客户端-服务器 模式/Peer-to-Peer Pattern / P2P模式", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 675, "text": "directly interact as peers. All peers are “equal”. / 解决方案：在点对点（P2P）模式中，组件直接作为对等体进行交互。所有对等体都是“平等”的。\n- Peer-to-peer communication is typically a request/reply interaction ***without the asymmetry*** found in the client-server pattern. / 点对点通信通常是请求/回复交互，与客户端-服务器模式中的不对称性不同。\n- **Weaknesses: / 弱点**\n\n - Managing data consistency, data/service availability, backup, and recovery are all more complex. 在点对点（P2P）系统中，有效维护数据一致性是一个基本挑战。由于P2P网络的动态性和去中心化特性，保持数据的一致性、可用性、备份和恢复变得更加复杂。\n - Small peer-to-peer systems may not be able to achieve quality goals such as performance and availability. 小型P2P系统可能无法实现性能和可用性等质量目标。这是因为P2P网络的性能和稳定性可能会受到连接对等体数量的影响，大型P2P网络可能会遭受响应时间变慢和延迟增加的影响，影响整体用户体验。"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1039", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "使用管道和过滤器处理数据/Client-Server Pattern / 客户端-服务器 模式/SOA: Service Oriented Architecture / 面向服务的架构", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 643, "text": "\n\n- Problem: How can we support ***interoperability*** of distributed components running on different platforms and written in different implementation languages, provided by different organizations, and distributed across the Internet? / 问题：我们如何支持在不同平台上运行、使用不同实现语言编写、由不同组织提供、并分布在互联网上的分布式组件之间的***互操作性***？\n\n - 解决方案涉及使用面向服务的架构（SOA）模式，它描述了一系列提供和/或消费服务的分布式组件。\n- Solution: The service-oriented architecture (SOA) pattern describes a collection of distributed components that provide and/or consume services. / 解决方案：面向服务的架构（SOA）模式描述了一系列提供和/或消费服务的分布式组件。\n- Elements: / 元素：\n\n - Components: / 组件："}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1040", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "使用管道和过滤器处理数据/Client-Server Pattern / 客户端-服务器 模式/SOA: Service Oriented Architecture / 面向服务的架构", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 696, "text": "ume services. / 解决方案：面向服务的架构（SOA）模式描述了一系列提供和/或消费服务的分布式组件。\n- Elements: / 元素：\n\n - Components: / 组件：\n\n - Service providers, which provide one or more services through published interfaces. / 服务提供者，通过发布的接口提供一项或多项服务。\n - Service consumers, which invoke services directly or through an intermediary. / 服务消费者，直接或通过中介调用服务。\n - Enterprise Service Bus (ESB), which is an ***intermediary element*** that can route and transform messages between service providers and consumers. / 企业服务总线（ESB），这是一个***中介元素***，可以在服务提供者和消费者之间路由和转换消息。\n - Registry of services, which may be used by providers to register their services and by consumers to discover services at runtime. / 服务注册表，提供者可以用它来注册服务，消费者可以用它在运行时发现服务。"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1041", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "使用管道和过滤器处理数据/Client-Server Pattern / 客户端-服务器 模式/SOA: Service Oriented Architecture / 面向服务的架构", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 623, "text": "ir services and by consumers to discover services at runtime. / 服务注册表，提供者可以用它来注册服务，消费者可以用它在运行时发现服务。\n- Connectors: / 连接器：\n\n - SOAP connector, which uses the SOAP protocol for synchronous communication between web services, typically over HTTP. / SOAP连接器，使用SOAP协议进行Web服务之间的同步通信，通常通过HTTP。\n - REST connector, which relies on the basic request/reply operations of the HTTP protocol. / REST连接器，依赖于HTTP协议的基本请求/回复操作。\n - Asynchronous messaging connector, which uses a messaging system to offer point-to-point or publish-subscribe ***asynchronous message exchanges***. / 异步消息连接器，使用消息系统提供点对点或发布-订阅的***异步消息交换***。\n- Weaknesses: / 弱点："}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1042", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "使用管道和过滤器处理数据/Client-Server Pattern / 客户端-服务器 模式/SOA: Service Oriented Architecture / 面向服务的架构", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 301, "text": "**asynchronous message exchanges***. / 异步消息连接器，使用消息系统提供点对点或发布-订阅的***异步消息交换***。\n- Weaknesses: / 弱点：\n\n - There is a ***performance overhead associated with middleware***, which may be performance bottlenecks, and typically do not provide performance guarantees. / ***中间件会带来性能开销，可能会导致性能瓶颈***，且通常不提供性能保证。"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1043", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "使用管道和过滤器处理数据/Client-Server Pattern / 客户端-服务器 模式/Publish-Subscribe Pattern / 订阅-发布者模式", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 249, "text": "• **Problem:** To transmit messages among the producers and consumers so they are ***unaware of each other’s identity, or even their existence*? /** 问题：我们如何在生产者和消费者之间传递信息，从而让他们对彼此的身份甚至存在都无法感知？\n\n"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1044", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "使用管道和过滤器处理数据/Client-Server Pattern / 客户端-服务器 模式/Publish-Subscribe Pattern / 订阅-发布者模式/Advantages / 优势", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 358, "text": "- Highly suited for mobile applications, ubiquitous computing and distributed embedded systems / 非常适合移动应用、普适计算和分布式嵌入式系统。\n- Robust – Failure of publishers or subscribers does not bring down the entire system / 健壮性 - 发布者或订阅者的失败不会使整个系统崩溃。\n- Scalability - Suited to build distributed applications consisting a large number of entities / 可扩展性 - 适合构建由大量实体组成的分布式应用。"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1045", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "使用管道和过滤器处理数据/Client-Server Pattern / 客户端-服务器 模式/Publish-Subscribe Pattern / 订阅-发布者模式/Disadvantages / 劣势", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 396, "text": "- Reliability – no strong guarantee on broker to deliver content to subscriber. After a publisher publishes the event, it assumes that all corresponding subscribers will receive it. / 可靠性 - 没有强烈保证经纪人会将内容传递给订阅者。发布者发布事件后，它假设所有相应的订阅者都会收到它。\n- Potential bottleneck in brokers when subscribers and publishers overload them. (Solve by load balancing techniques) / 当订阅者和发布者使经纪人过载时，可能会出现潜在的瓶颈。（通过负载均衡技术解决）"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1046", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "使用管道和过滤器处理数据/Client-Server Pattern / 客户端-服务器 模式/Shared-Data Pattern / 共享数据模式", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 570, "text": "- Context: Various computational components need to share and manipulate large amounts of data. This data does not belong solely to any one of those components. / 背景：各种计算组件需要共享和操作大量数据。这些数据并不完全属于任何一个组件。\n- Problem: How can systems store and manipulate persistent data that is accessed by multiple independent components? / 问题：系统如何存储和操作被多个独立组件访问的持久数据？\n- Solution: In the shared-data pattern, interaction is dominated by the exchange of persistent data between multiple data accessors and at least one shared-data store. / 解决方案：在共享数据模式中，交互主要通过多个数据访问器和至少一个共享数据存储之间的持久数据交换来实现。"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1047", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "使用管道和过滤器处理数据/Client-Server Pattern / 客户端-服务器 模式/Shared-Data Pattern / 共享数据模式", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 301, "text": "accessors and at least one shared-data store. / 解决方案：在共享数据模式中，交互主要通过多个数据访问器和至少一个共享数据存储之间的持久数据交换来实现。\n- Exchange may be initiated by the accessors or the data store. The connector type is data reading and writing. / 交换可以由访问器或数据存储发起。连接器类型是数据读取和写入。\n\n"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1048", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "使用管道和过滤器处理数据/Client-Server Pattern / 客户端-服务器 模式/Shared-Data Pattern / 共享数据模式/Solution / 解决方案", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 668, "text": "- Communication between data accessors is mediated by a shared data store. / 数据访问器之间的通信由共享数据存储介导。\n- Data is made persistent by the data store. / 数据存储使数据持久化。\n- Elements: / 元素：\n\n - Shared-data store. Concerns include types of data stored, data distribution, and number of accessors permitted. / 共享数据存储。关注点包括存储的数据类型、数据分布和允许的访问器数量。\n - Data accessor – Data reading and writing connector. / 数据访问器 - 数据读取和写入连接器。\n- Constraints: Data accessors interact only with the data store(s). / 约束：数据访问器仅与数据存储交互。\n- Weaknesses: / 弱点：\n\n - The shared-data store may be a performance bottleneck. / 共享数据存储可能是性能瓶颈。\n - The shared-data store may be a single point of failure. / 共享数据存储可能是单点故障。"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1049", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "使用管道和过滤器处理数据/Client-Server Pattern / 客户端-服务器 模式/Shared-Data Pattern / 共享数据模式/Solution / 解决方案", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 592, "text": "neck. / 共享数据存储可能是性能瓶颈。\n - The shared-data store may be a single point of failure. / 共享数据存储可能是单点故障。\n - Producers and consumers of data may be tightly coupled. E.g., concurrency control is needed in database. / 数据的生产者和消费者可能紧密耦合。例如，数据库中需要并发控制。\n\n\n\nShared-Data Pattern（共享数据模式）是一种设计模式，它允许多个组件或服务访问同一个数据存储。在后端架构中，这通常意味着不同的服务可以共享对数据库或缓存的访问。Redis 和 MySQL 是两种流行的数据存储系统，它们可以用于实现共享数据模式。\n\n**Redis**：作为一个内存数据结构存储，Redis 通常用作缓存层，以提高数据访问速度。多个服务可以同时连接到同一个 Redis 实例，共享缓存数据。\n\n\n\n```Python\nimport redis"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1050", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "连接到 Redis", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 50, "text": "r = redis.Redis(host='localhost', port=6379, db=0)"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1051", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "服务 B 获取数据", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 50, "text": "value = r.get('foo')\nprint(value) # 输出：b'bar'\n```"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1052", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "服务 B 获取数据/Allocation Patterns / 分配模式/Map-Reduce Pattern / 映射-消除模式", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 485, "text": "- Origin from Google, [OSDI’04] / 源自谷歌，[OSDI’04]（操作系统设计与实现研讨会，2004年）。\n- A simple programming model / 一个简单的编程模型。\n- For large-scale data processing / 用于大规模数据处理：\n\n - Exploits large set of commodity computers / 利用大量普通计算机。\n - Executes process in distributed manner / 以分布式方式执行进程。\n - Offers high availability / 提供高可用性。\n\n\n\n\n\n"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1053", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "服务 B 获取数据/Allocation Patterns / 分配模式/Map-Reduce Pattern / 映射-消除模式/Functions in the Model / 模型中的函数：", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 344, "text": "- Map\n\n - Process a key/value pair to generate intermediate key/value pairs / 处理键/值对以生成中间键/值对。\n- Reduce\n\n - Merge all intermediate values associated with the same key / 合并所有与同一键关联的中间值。\n- Partition\n\n - By default: hash(key) mod R / 默认情况下：hash(键) mod R（R是分区数）。\n - Well balanced / 均衡分布。\n\n"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1054", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "服务 B 获取数据/Allocation Patterns / 分配模式/Map-Reduce Pattern / 映射-消除模式/GFS: underlying storage system / GFS：底层存储系统", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 599, "text": "- Goal / 目标：\n\n - Global view / 全局视图\n - Make huge files available in the face of node failures / 在节点故障的情况下仍能提供巨大的文件\n- Master Node (meta server) / 主节点（元数据服务器）：\n\n - Centralized, index all chunks on data servers / 集中式，索引数据服务器上的所有块\n- Chunk server (data server) / 块服务器（数据服务器）：\n\n - File is split into contiguous chunks, typically 16-64MB / 文件被分割成连续的块，通常大小为16-64MB\n - Each chunk replicated (usually 2x or 3x) / 每个块都被复制（通常2倍或3倍）\n - Try to keep replicas in different racks / 尽量将副本保存在不同的机架上\n\n\n\n"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1055", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "服务 B 获取数据/Allocation Patterns / 分配模式/Map-Reduce Pattern / 映射-消除模式/**Locality issue / 局部性问题：**", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 478, "text": "- Master scheduling policy / 主节点调度策略：\n\n - Asks GFS for locations of replicas of input file blocks / 向GFS请求输入文件块副本的位置\n - Map tasks typically split into 64MB (== GFS block size) / Map任务通常分割成64MB（== GFS块大小）\n - Map tasks scheduled so GFS input block replica are on same machine or same rack / Map任务调度使得GFS输入块副本在同一台机器或同一机架上\n- Effect / 效果：\n\n - Thousands of machines read input at local disk speed / 数千台机器以本地磁盘速度读取输入\n - Without this, rack switches limit read rate / 否则，机架交换机限制读取速率"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1056", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "服务 B 获取数据/Allocation Patterns / 分配模式/Map-Reduce Pattern / 映射-消除模式/**Fault Tolerance / 容错：**/① Reactive way / 反应式方式：", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 278, "text": "- Worker failure / 工作节点故障\n- Heartbeat, Workers are periodically pinged by master / 心跳，工作节点定期被主节点ping\n- NO response = failed worker / 无响应 = 工作节点故障\n- If the processor of a worker fails, the tasks of that worker are reassigned to another worker / 如果工作节点的处理机失败，该工作节点的任务被重新分配给另一个工作节点"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1057", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "服务 B 获取数据/Allocation Patterns / 分配模式/Map-Reduce Pattern / 映射-消除模式/**Fault Tolerance / 容错：**/② Master failure / 主节点故障", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 213, "text": "- Master writes periodic checkpoints / 主节点定期写入检查点\n- Another master can be started from the last checkpointed state / 另一个主节点可以从最后一个检查点状态启动\n- If eventually the master dies, the job will be aborted / 如果主节点最终死亡，作业将被中止"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1058", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "服务 B 获取数据/Allocation Patterns / 分配模式/Map-Reduce Pattern / 映射-消除模式/**Fault Tolerance / 容错：**/③ Proactive way (Redundant Execution) / 积极方式（冗余执行）：", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 438, "text": "- The problem of “stragglers” (slow workers) / “落后者”（慢工作节点）的问题\n\n - Other jobs consuming resources on machine / 其他作业消耗机器资源\n - Bad disks transfer data very slowly / 坏磁盘传输数据非常慢\n - Weird things: processor caches disabled (!!) / 奇怪的事情：处理器缓存被禁用（!!）\n- When computation almost done, reschedule in-progress tasks / 当计算几乎完成时，重新调度进行中的任务\n- Whenever either the primary or the backup executions finishes, mark it as completed / 无论主执行还是备份执行完成，都标记为已完成"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1059", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "服务 B 获取数据/Allocation Patterns / 分配模式/Map-Reduce Pattern / 映射-消除模式/Points need to be emphasized / 需要强调的点：", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 403, "text": "- No reduce can begin until map is complete / 直到Map完成，Reduce才能开始\n- Master must communicate locations of intermediate files / 主节点必须通信中间文件的位置\n- Tasks scheduled based on location of data / 任务根据数据位置调度\n- If map worker fails any time before reduce finishes, task must be completely rerun / 如果Map工作节点在Reduce完成前任何时候失败，任务必须完全重新运行\n- MapReduce library does most of the hard work for us! / MapReduce库为我们完成了大部分艰苦的工作！"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1060", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "服务 B 获取数据/Allocation Patterns / 分配模式/Map-Reduce Pattern / 映射-消除模式/How to use it / 如何使用它：", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 286, "text": "- User to do list / 用户待办事项：\n\n - Indicate / 指明：\n\n - Input/output files / 输入/输出文件\n - M: number of map tasks / M：Map任务数量\n - R: number of reduce tasks / R：Reduce任务数量\n - W: number of machines / W：机器数量\n - Write map and reduce functions / 编写Map和Reduce函数\n - Submit the job / 提交作业"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1061", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "服务 B 获取数据/Allocation Patterns / 分配模式/Map-Reduce Pattern / 映射-消除模式/Detailed Example: Word Count (Python Version)/安装依赖", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 31, "text": "```Python\npip install mrjob\n```"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1062", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "服务 B 获取数据/Allocation Patterns / 分配模式/Map-Reduce Pattern / 映射-消除模式/Detailed Example: Word Count (Python Version)/Mapper", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 94, "text": "```Python\ndef mapper(self, _, line):\n for word in line.split():\n yield (word, 1)\n```"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1063", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "服务 B 获取数据/Allocation Patterns / 分配模式/Map-Reduce Pattern / 映射-消除模式/Detailed Example: Word Count (Python Version)/Reducer", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 70, "text": "```Python\ndef reducer(word, counts):\n yield (word, sum(counts))\n```"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1064", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "服务 B 获取数据/Allocation Patterns / 分配模式/Map-Reduce Pattern / 映射-消除模式/Detailed Example: Word Count (Python Version)/编写完整的作业", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 284, "text": "```Python\nfrom mrjob.job import MRJob\n\nclass MRWordCount(MRJob):\n\n def mapper(self, _, line):\n for word in line.split():\n yield (word, 1)\n\n def reducer(self, word, counts):\n yield (word, sum(counts))\n\nif __name__ == '__main__':\n MRWordCount.run()\n```"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1065", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "服务 B 获取数据/Allocation Patterns / 分配模式/Map-Reduce Pattern / 映射-消除模式/Detailed Example: Word Count (Python Version)/提交", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 56, "text": "```Python\npython wordcount.py input.txt > output.txt\n```"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1066", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "服务 B 获取数据/Allocation Patterns / 分配模式/Multi-Tier Pattern / （硬件）多层模式", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 194, "text": "- The execution structures of many systems are organized as a set of logical groupings of software and hardware. / 许多系统的执行结构被组织为软件和硬件的一组逻辑分组。\n- Each grouping is termed a tier. / 每个分组被称为一层（tier）。"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1067", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "服务 B 获取数据/Allocation Patterns / 分配模式/Multi-Tier Pattern / （硬件）多层模式/Layer vs. Tier / 层与层级：", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 675, "text": "\n\n- In computing, the terms \"layer\" and \"tier\" are often used to describe different levels of abstraction or organization within a system. However, they are sometimes used interchangeably, and their distinction can vary depending on context.\n- Layer\n\n - A layer typically refers to a level of abstraction within a system, where each layer has a specific purpose and communicates with the layers immediately above and below it. Layers are commonly found in network protocols (like the OSI model), software architectures (like the MVC pattern), and other systems where a clear separation of concerns is beneficial.\n- Tier"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1068", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "服务 B 获取数据/Allocation Patterns / 分配模式/Multi-Tier Pattern / （硬件）多层模式/Layer vs. Tier / 层与层级：", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 531, "text": "ike the MVC pattern), and other systems where a clear separation of concerns is beneficial.\n- Tier\n\n - A tier, on the other hand, often refers to a physical or logical separation of functionality across different servers or service groups. In a multi-tier architecture, tiers can be distributed across multiple machines or locations, and they define both the physical layout and the logical structure of the system. For example, a three-tier architecture might consist of a presentation tier, an application tier, and a data tier."}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1069", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "服务 B 获取数据/Allocation Patterns / 分配模式/Multi-Tier Pattern / （硬件）多层模式/Layer vs. Tier / 层与层级：", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 429, "text": "hree-tier architecture might consist of a presentation tier, an application tier, and a data tier.\n\nIn summary, while both terms can describe levels of organization, \"layer\" tends to emphasize the logical separation of concerns within a single system or component, whereas \"tier\" emphasizes the distribution of functionality across different physical or logical groupings.\n\n"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1070", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "服务 B 获取数据/Relationships Between Tactics and Patterns", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 661, "text": "\n\n- Patterns are built from tactics; if a pattern is a molecule, a tactic is an atom. / 模式是由策略构建的；如果模式是一个分子，策略是一个原子。\n\n - MVC, for example, utilizes the tactics: / 例如，MVC模式利用以下策略：\n\n - Increase semantic coherence / 提高语义一致性：这意味着增加系统各部分之间的逻辑联系，使得系统的行为和结构更加直观和易于理解。\n - Encapsulation / 封装：这是指将数据和操作数据的方法捆绑在一起，隐藏内部实现细节，仅对外提供必要的接口。\n - Use an intermediary / 使用中介：这涉及到引入一个中间层或中介来协调不同部分之间的通信，减少它们之间的直接依赖，提高系统的灵活性和可维护性。\n - Use run time binding / 使用运行时间绑定\n\n\n\n\n\n- Tactics Augment Patterns / 策略增强模式"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1071", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "服务 B 获取数据/Relationships Between Tactics and Patterns", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 654, "text": "n4e)\n\n\n\n- Tactics Augment Patterns / 策略增强模式\n\n - Patterns solve a specific problem but may have weaknesses with respect to other qualities. / 模式解决了特定问题，但可能在其他品质方面存在弱点。\n- Consider the broker pattern / 考虑经纪人模式\n\n - May have performance bottlenecks / 可能有性能瓶颈\n - May have a single point of failure / 可能有单点故障\n- Using tactics such as / 使用以下策略：\n\n - Increase resources will help performance / 增加资源将有助于提高性能：通过增加服务器的硬件资源，如CPU、内存或网络带宽，可以减轻性能瓶颈，提高系统处理能力。\n - Maintain multiple copies will help availability / 维护多个副本将有助于可用性：通过在不同的服务器或位置维护数据和服务的多个副本，可以减少单点故障的风险，提高系统的可用性和容错能力。\n- Tactics and Interactions / 策略与交互"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1072", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "服务 B 获取数据/Relationships Between Tactics and Patterns", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 699, "text": "多个副本将有助于可用性：通过在不同的服务器或位置维护数据和服务的多个副本，可以减少单点故障的风险，提高系统的可用性和容错能力。\n- Tactics and Interactions / 策略与交互\n\n - Each tactic has pluses (its reason for being) and minuses-side effects. / 每个策略都有其优点（存在的理由）和缺点——副作用。\n - Use of tactics can help alleviate the minuses. / 使用策略可以帮助减轻这些缺点。\n - But nothing is free… / 但没有什么是免费的……\n\n\n\n以下是关于Ping/Echo策略及其常见副作用的详细说明：\n\n1. **安全性（Security）**：\n\n - Ping/Echo策略可能会遭受“Ping洪泛攻击”（ping flood attack），这是一种拒绝服务攻击（DoS），攻击者通过发送大量的Ping请求来消耗目标系统的资源，导致其无法正常响应。为了防止这种攻击，可以采取一些安全措施，比如限制Ping请求的频率，或者在防火墙中设置规则来过滤ICMP流量。\n2. **性能（Performance）**：\n\n - 为了确保Ping/Echo的性能开销保持在较低水平，需要优化Ping/Echo消息的大小和发送频率。心跳包通常非常小，只包含简单的标识信息，这样可以减少网络和处理的负载。"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1073", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "服务 B 获取数据/Relationships Between Tactics and Patterns", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 667, "text": "nce）**：\n\n - 为了确保Ping/Echo的性能开销保持在较低水平，需要优化Ping/Echo消息的大小和发送频率。心跳包通常非常小，只包含简单的标识信息，这样可以减少网络和处理的负载。\n3. **可修改性（Modifiability）**：\n\n - 在现有架构中添加Ping/Echo机制可能会涉及到系统的改动。这可能需要对系统的网络通信模块进行调整，以便能够发送Ping请求并处理Echo响应。这种集成可以通过软件模块泛化、限制模块之间通信、使用中介和延迟绑定等架构设计策略来实现，以提高系统的可修改性。\n\n\n\n解决性能副作用的策略是\"增加可用资源\"。\n\n增加可用资源的常见副作用有:\n\n- 成本 : 增加的资源成本更高\n- 绩效 : 如何有效地利用增加的资源?\n\n\n\n\n\n\n\n\n\nHow does this process end ? / 这个过程是怎么终止的？"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1074", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "服务 B 获取数据/Relationships Between Tactics and Patterns", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 513, "text": "\n\nHow does this process end ? / 这个过程是怎么终止的？\n\n- Each use of tactic introduces new concerns. / 每次使用策略都会引入新的关注点。\n- Each new concern causes new tactics to be added. / 每个新关注点导致添加新的策略。\n- Are we in an infinite progression? / 我们是否处于一个无限循环中？\n- No. Eventually the side-effects of each tactic become small enough to ignore. / 不是的。最终，每个策略的副作用会变得足够小，可以忽略不计。\n\n\n\n"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1075", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "服务 B 获取数据/Summary / 总结", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 517, "text": "- An architectural pattern / 架构模式：\n\n - is a package of design decisions that is found repeatedly in practice / 是在实践中反复出现的设计决策包，\n - has known properties that permit reuse / 具有已知属性，允许重用，\n - describes a class of architectures / 描述了一类架构。\n- Tactics are simpler than patterns / 策略比模式更简单：\n\n - Patterns are underspecified with respect to real systems so they have to be augmented with tactics / 模式相对于实际系统是欠指定的，因此它们需要用策略来增强。\n - Augmentation ends when requirements for a specific system are satisfied / 当特定系统的需求得到满足时，增强结束。"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1076", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "Chapter 14 Quality Attribute Modeling and Analysis / 第十四章：质量属性建模和分析", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 683, "text": "- How do we know the quality attributes of software? / 我们应该如何知道软件的质量属性呢？\n\n - Experiment and measurement / 实验和度量\n - Analytic model / 分析性模型\n - Simulations / 模拟\n- Modeling Architectures to Enable Quality Attribute Analysis / 建模架构以支持质量属性分析：\n\n - Some quality attributes, most notably performance and availability, have well-understood, time-tested analytic models that can be used to assist in an analysis. / 一些质量属性，尤其是性能和可用性，有被广泛理解的、经过时间考验的分析模型，这些模型可以用来协助分析。\n - By analytic model, we mean one that supports quantitative analysis. / 通过分析模型，我们指的是支持定量分析的模型。\n\n\n\n您列举的这些参数是在进行系统性能和可用性分析时的关键因素，它们通常用于定量分析模型中，以预测和评估系统的行为。以下是每个参数的简要说明："}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1077", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "Chapter 14 Quality Attribute Modeling and Analysis / 第十四章：质量属性建模和分析", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 657, "text": "NNZ0bR5tto58tQxo0bbc2DxMnHJ)\n\n您列举的这些参数是在进行系统性能和可用性分析时的关键因素，它们通常用于定量分析模型中，以预测和评估系统的行为。以下是每个参数的简要说明：\n\n1. **Arrival rate of events (事件到达率)**\n2. **Chosen queuing discipline (选择的排队规则)**\n3. **Chosen scheduling algorithm (选择的调度算法)**\n4. **Network topology (网络拓扑)**\n5. **Network bandwidth (网络带宽)**\n6. **Routing algorithm chosen (选择的路由算法)**\n7. **Service time for events (事件的服务时间)**\n\n\n\n**前端可以看作（View），后端服务器可以看作（Controller），数据库服务器可以看作（Model）**\n\n\n\n\n\n"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1078", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "Chapter 14 Quality Attribute Modeling and Analysis / 第十四章：质量属性建模和分析", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 644, "text": "ishu.cn/file/Ul5GbsiPvozrdtx1ITpcL1WKnab)\n\n\n\n\n\n\n\n成本：确定之前提到的参数\n\n好处：估计延迟\n\n参数估计得越准确，对延迟的预测就越好。\n\n当延迟很重要且不确定时，这是值得的。\n\n当很明显有足够的容量来满足需求时，这是不值得的。\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd::1079", "page_id": "docx::JM1MwHmDqiG5zokFeMdcRGFrnxd", "title": "SA 讲义（三） Chapter 13 ~ 14", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（三） Chapter 13 ~ 14", "section": "Chapter 14 Quality Attribute Modeling and Analysis / 第十四章：质量属性建模和分析", "url": "https://a1npn29y3xu.feishu.cn/wiki/JM1MwHmDqiG5zokFeMdcRGFrnxd", "source_type": "docx", "n_chars": 155, "text": "ishu.cn/file/NDJ6bHtpHoXipWxAtmpcdxoPn6b)\n\n\n\n"}
{"id": "docx::O1pKws6sMibqyDkFdC7cXgXwnpg::1080", "page_id": "docx::O1pKws6sMibqyDkFdC7cXgXwnpg", "title": "SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性", "section": "SA 讲义（二） Chapter 04 \\~ 12 Quality Attributes / 质量属性", "url": "https://a1npn29y3xu.feishu.cn/wiki/O1pKws6sMibqyDkFdC7cXgXwnpg", "source_type": "docx", "n_chars": 700, "text": "在看之前想说的\n\n除了 04 和 12，所有的质量属性的行文规则是一样的，记住 SSEARR 和 Tactics Tree 即可\n\n\n\nChapter 4. Understanding Quality Attributes\n\n了解：系统的功能需求。功能需求与系统架构的关系。功能需求与质量需求的关系。系统约束。\n\n理解：系统的质量需求。战术的概念。\n\n掌握：质量属性场景的概念和举例。质量设计的7种决策。\n\nChapter 5. Availability\n\n理解：可用性概念。\n\n了解：可用性公式。可用性一般场景。\n\n掌握：可用性战术。可用性设计清单。\n\nChapter 6. Interoperability"}
{"id": "docx::O1pKws6sMibqyDkFdC7cXgXwnpg::1082", "page_id": "docx::O1pKws6sMibqyDkFdC7cXgXwnpg", "title": "SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（二） Chapter 04 ~ 12 Quality Attributes / 质量属性", "section": "SA 讲义（二） Chapter 04 \\~ 12 Quality Attributes / 质量属性", "url": "https://a1npn29y3xu.feishu.cn/wiki/O1pKws6sMibqyDkFdC7cXgXwnpg", "source_type": "docx", "n_chars": 652, "text": "pter 5. Availability\n\n理解：可用性概念。\n\n了解：可用性公式。可用性一般场景。\n\n掌握：可用性战术。可用性设计清单。\n\nChapter 6. Interoperability\n\n理解：互操作性概念。\n\n了解：互操作性一般场景。\n\n掌握：互操作性战术。互操作性设计清单。\n\nChapter 7. Modifiability\n\n理解：可修改性概念。\n\n了解：可修改性一般场景。\n\n掌握：可修改性战术。可修改性设计清单。\n\nChapter 8. Performance\n\n理解：性能概念。\n\n了解：性能公式。性能一般场景。\n\n掌握：性能战术。性能设计清单。\n\nChapter 9. Security\n\n理解：安全性概念。\n\n了解：安全一般场景。\n\n掌握：安全性战术。安全性设计清单。\n\nChapter 10. Testability\n\n理解：可测试性概念。\n\n了解：可测试性一般场景。\n\n掌握：可测试性战术。可测试性设计清单。\n\nChapter 11. Usability\n\n理解：易用性概念。\n\n了解：易用性一般场景。\n\n掌握：易用性战术。易用性设计清单。\n\nChapter 12. Other Quality Attributes\n\n了解：其它软件质量属性如可变性、可移植性、开发可分布性、伸缩性、可部署性、移动性、可监控性、生命财产安全性。其它类别的质量属性如架构质量属性、商业属性、系统质量属性。ISO/IEC FCD 25010 产品质量标准。\n\n理解：如何处理未知的质量属性。"}
{"id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt::1083", "page_id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt", "title": "SA 讲义（五）Chapter 19, 21", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（五）Chapter 19, 21", "section": "Chapter 19 Architecture, Implementation, and Testing / 架构，实现和测试/Architecture & Implementation / 架构与实现", "url": "https://a1npn29y3xu.feishu.cn/wiki/Q6ngwVkPKi2peOkCqpqcyI4dnjt", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt::1084", "page_id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt", "title": "SA 讲义（五）Chapter 19, 21", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（五）Chapter 19, 21", "section": "Chapter 19 Architecture, Implementation, and Testing / 架构，实现和测试/Embedding the Design in the Code / 在代码中嵌入设计", "url": "https://a1npn29y3xu.feishu.cn/wiki/Q6ngwVkPKi2peOkCqpqcyI4dnjt", "source_type": "docx", "n_chars": 580, "text": "\n\nArchitecture acts as a **blueprint** for implementation. This means\n\n- lmplementers know what **architectural structure** they are implementing.E.g.layer, pub/sub, MVC, broker, ...\n- They can **document** the architectural structure inthe code as **comments**. Then anyone picking up the code will know some of the constraints.\n- Then tools can automatically **relate** code and architecture.\n\n架构充当实施的蓝图。这意味着\n\n- 实现者知道他们正在实现什么架构结构。例如 layer、pub/sub、MVC、broker ...\n- 他们可以将代码中的架构结构记录为注释。然后，任何拿起代码的人都会知道一些约束。\n- 然后，工具可以自动关联代码和架构。"}
{"id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt::1085", "page_id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt", "title": "SA 讲义（五）Chapter 19, 21", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（五）Chapter 19, 21", "section": "Chapter 19 Architecture, Implementation, and Testing / 架构，实现和测试/Frameworks & Code Template / 框架和代码模板", "url": "https://a1npn29y3xu.feishu.cn/wiki/Q6ngwVkPKi2peOkCqpqcyI4dnjt", "source_type": "docx", "n_chars": 692, "text": "\n\nA framework is a reusable set of libraries or classes organized around a particular theme.\n\nA programmer uses the services provided by a framework.\n\n框架是围绕特定主题组织的一组可重用的库或类。程序员使用框架提供的服务。\n\n**拓展知识：各个语言的常用框架及其作用**\n\n\n\n代码模板是代码的集合，程序员在其中提供特定于应用程序的部分。\n\n例如：\n\n如果在 重要应用的组成部分 中检测到故障，则按如下方式进行切换：\n\n1. 在不同的处理器上后台并行执行的辅助副本被提升为新的主副本\n2. 新的主副本与应用程序的客户端一起重建\n3. 新的辅助数据库将启动，作为新的主副本的备份。\n4. 新启动的辅助副本向新的主副本宣布自己。如果在辅助处理器中检测到故障，则会在其他处理器上启动一个新的处理器。\n\n\n\n流程：\n\n- 对每个关键组件使用代码模板\n- 将应用程序特定的代码放置在模板内的固定位置。\n\n"}
{"id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt::1086", "page_id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt", "title": "SA 讲义（五）Chapter 19, 21", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（五）Chapter 19, 21", "section": "Chapter 19 Architecture, Implementation, and Testing / 架构，实现和测试/Frameworks & Code Template / 框架和代码模板", "url": "https://a1npn29y3xu.feishu.cn/wiki/Q6ngwVkPKi2peOkCqpqcyI4dnjt", "source_type": "docx", "n_chars": 169, "text": "- 对每个关键组件使用代码模板\n- 将应用程序特定的代码放置在模板内的固定位置。\n\n\n\n代码模板的优点：\n\n• 具有相似属性的组件表现方式相似。\n\n• 模板只需调试一次。\n\n• 复杂部分可以由熟练人员完成并交接给技能较低的人员。"}
{"id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt::1087", "page_id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt", "title": "SA 讲义（五）Chapter 19, 21", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（五）Chapter 19, 21", "section": "Chapter 19 Architecture, Implementation, and Testing / 架构，实现和测试/Architecture & Testing / 架构与测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/Q6ngwVkPKi2peOkCqpqcyI4dnjt", "source_type": "docx", "n_chars": 667, "text": "\n\n\n\n- 测试的两个层次\n- **单元测试：针对特定软件片段的测试。**\n\n - 组件或模块\n- 需要测试的内容：\n\n - **责任：**功能正确性\n - **性能：**通过合成负载测试\n - **可用性：**故障注入测试\n - **可修改性：**将变更分配给测试团队\n - **安全性：**测试执行各种攻击场景\n\n\n\n- **集成测试：测试当独立的软件单元开始协同工作时会发生什么**\n- 集成测试可以测试功能、性能、可用性和安全性。\n\n\n\n\n\n\n\n\n\n架构师应该积极参与\n\n- **测试规划：**分配资源，例如时间、劳动力、技术、工具、硬件或设备"}
{"id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt::1088", "page_id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt", "title": "SA 讲义（五）Chapter 19, 21", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（五）Chapter 19, 21", "section": "Chapter 19 Architecture, Implementation, and Testing / 架构，实现和测试/Architecture & Testing / 架构与测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/Q6ngwVkPKi2peOkCqpqcyI4dnjt", "source_type": "docx", "n_chars": 258, "text": "ttps://feishu.cn/file/KEitbtKoTonhTax73OYcCaCOnhg)\n\n架构师应该积极参与\n\n- **测试规划：**分配资源，例如时间、劳动力、技术、工具、硬件或设备\n- **测试开发：**编写测试、选择测试用例和创建测试训练集的过程\n\n - 测试驱动开发是一种技术，其中系统被开发以满足预定的测试。\n- **测试执行：**测试人员将测试应用于软件并捕获记录错误\n- **测试报告和缺陷分析**\n- **测试工具的创建：**包括测试引擎和测试脚本存储\n- 主要目的是自动化测试过程。"}
{"id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt::1089", "page_id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt", "title": "SA 讲义（五）Chapter 19, 21", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（五）Chapter 19, 21", "section": "Chapter 19 Architecture, Implementation, and Testing / 架构，实现和测试/Summary / 总结", "url": "https://a1npn29y3xu.feishu.cn/wiki/Q6ngwVkPKi2peOkCqpqcyI4dnjt", "source_type": "docx", "n_chars": 218, "text": "\n\n- 实施\n\n - 实施活动可以在代码中嵌入架构知识\n - 可以使用模板来处理重复出现的关键部分\n - 通过使用工具和管理流程可以防止架构侵蚀\n- 测试\n\n - 单元测试和集成测试依赖于架构知识和测试框架。\n - 当服务器被应用的数量级小于 K 时，网络的影响很难发现\n - 架构师应该参与各种各样的测试活动。"}
{"id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt::1090", "page_id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt", "title": "SA 讲义（五）Chapter 19, 21", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（五）Chapter 19, 21", "section": "Chapter 21 Architecture Evaluation / 架构评价/3 Forms of Evaluation / 评估的三种形式", "url": "https://a1npn29y3xu.feishu.cn/wiki/Q6ngwVkPKi2peOkCqpqcyI4dnjt", "source_type": "docx", "n_chars": 106, "text": "\n\n- 设计过程中的设计师评估。\n- 设计过程中的同行评估。\n- 建筑设计完成后由外部人员进行的分析。"}
{"id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt::1091", "page_id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt", "title": "SA 讲义（五）Chapter 19, 21", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（五）Chapter 19, 21", "section": "Chapter 21 Architecture Evaluation / 架构评价/3 Forms of Evaluation / 评估的三种形式/① Evaluation by the Designer / 设计者的评价", "url": "https://a1npn29y3xu.feishu.cn/wiki/Q6ngwVkPKi2peOkCqpqcyI4dnjt", "source_type": "docx", "n_chars": 214, "text": "\n\n每当**设计师**做出关键的设计决策时，都应该对所选择的替代方案进行评估。\n\n“生成和测试”方法中的**“测试”部分分析多少**?三个因素包括:\n\n- **决定的重要性。**\n- **潜在替代品的数量。**更多的替代品需要更多的时间来评估它们。\n- **足够好而不是完美。**不要在一项决定上花费超过其价值的时间。"}
{"id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt::1092", "page_id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt", "title": "SA 讲义（五）Chapter 19, 21", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（五）Chapter 19, 21", "section": "Chapter 21 Architecture Evaluation / 架构评价/3 Forms of Evaluation / 评估的三种形式/② Peer Review / 同行评审", "url": "https://a1npn29y3xu.feishu.cn/wiki/Q6ngwVkPKi2peOkCqpqcyI4dnjt", "source_type": "docx", "n_chars": 133, "text": "\n\n架构设计可以进行同行评审，就像代码一样。\n\n可以在设计过程中存在候选架构或至少一个可连贯审查部分的任何点上进行同行评审。\n\n至少分配几个小时，可能半天。"}
{"id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt::1093", "page_id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt", "title": "SA 讲义（五）Chapter 19, 21", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（五）Chapter 19, 21", "section": "Chapter 21 Architecture Evaluation / 架构评价/3 Forms of Evaluation / 评估的三种形式/② Peer Review / 同行评审/Steps / 步骤", "url": "https://a1npn29y3xu.feishu.cn/wiki/Q6ngwVkPKi2peOkCqpqcyI4dnjt", "source_type": "docx", "n_chars": 178, "text": "\n\n1. 评审员**确定**一系列**质量属性**场景来驱动评审。\n2. 架构师**展示**要评估的**架构部分**。\n\n– 目的是为了让评审员理解架构。\n\n1. 对于每个场景，设计者会遍历架构并**解释如何满足**该场景。\n2. 捕获潜在问题。"}
{"id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt::1094", "page_id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt", "title": "SA 讲义（五）Chapter 19, 21", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（五）Chapter 19, 21", "section": "Chapter 21 Architecture Evaluation / 架构评价/3 Forms of Evaluation / 评估的三种形式/③ Analysis By Outsiders", "url": "https://a1npn29y3xu.feishu.cn/wiki/Q6ngwVkPKi2peOkCqpqcyI4dnjt", "source_type": "docx", "n_chars": 537, "text": "- “Outside\" is **relative**; this may mean\n\n - outside the development project\n - outside the business unit where the project resides but within the same company\n - outside the company\n- Outsiders are chosen because they **possess specialized knowledge** or experience\n- Managers tend to be more inclined to listen to problems uncovered by an outside team.\n- Be used to evaluate **complete architectures**\n\n• “外部”是相对的；这可能意味着\n\n– 在开发项目之外\n\n– 在项目所在的业务单元之外，但在同一公司内\n\n– 在公司之外。\n\n• 外部人员被选中是因为他们拥有\n\n专业知识或经验\n\n• 管理者往往更愿意听取外部团队发现的问题。\n\n• 用于评估完整的架构。"}
{"id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt::1095", "page_id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt", "title": "SA 讲义（五）Chapter 19, 21", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（五）Chapter 19, 21", "section": "Chapter 21 Architecture Evaluation / 架构评价/3 Forms of Evaluation / 评估的三种形式/Contextual Factors for Evaluation / 评估的情境因素", "url": "https://a1npn29y3xu.feishu.cn/wiki/Q6ngwVkPKi2peOkCqpqcyI4dnjt", "source_type": "docx", "n_chars": 225, "text": "- Whether the result is public or private / 结果是公共的还是私有的\n- The number and skill of evaluators / 评估人员的数量和技能\n- Which stakeholders will participate / 哪些利益相关者将参与\n- How business goals are understood by the evaluators / 评估人员如何理解业务目标"}
{"id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt::1096", "page_id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt", "title": "SA 讲义（五）Chapter 19, 21", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（五）Chapter 19, 21", "section": "Chapter 21 Architecture Evaluation / 架构评价/⭐ ATAM Architecture Tradeoff Analysis Method / 架构权衡分析方法/Introduction / 介绍", "url": "https://a1npn29y3xu.feishu.cn/wiki/Q6ngwVkPKi2peOkCqpqcyI4dnjt", "source_type": "docx", "n_chars": 158, "text": "\n\n- 架构权衡分析方法(ATAM)已被使用超过十年，用于评估从汽车到金融到国防等多个领域的软件架构。\n- ATAM的设计使得评估者无需熟悉架构或其商业目标，系统甚至无需已经构建，且可能有大量的利益相关者。"}
{"id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt::1097", "page_id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt", "title": "SA 讲义（五）Chapter 19, 21", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（五）Chapter 19, 21", "section": "Chapter 21 Architecture Evaluation / 架构评价/⭐ ATAM Architecture Tradeoff Analysis Method / 架构权衡分析方法/Participants / 参与者", "url": "https://a1npn29y3xu.feishu.cn/wiki/Q6ngwVkPKi2peOkCqpqcyI4dnjt", "source_type": "docx", "n_chars": 218, "text": "\n\n- 评估团队\n\n - 3到5人\n - 能力强、公正无私的外部人员\n- 项目决策者\n\n - 项目经理、架构师以及为开发付费的客户\n- 架构利益相关者\n\n - 开发者、测试人员、集成人员、维护人员、性能工程师、用户、系统构建者\n - 明确表达特定质量属性目标\n - 对于大型企业关键架构，需要12到15名利益相关者"}
{"id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt::1098", "page_id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt", "title": "SA 讲义（五）Chapter 19, 21", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（五）Chapter 19, 21", "section": "Chapter 21 Architecture Evaluation / 架构评价/⭐ ATAM Architecture Tradeoff Analysis Method / 架构权衡分析方法/Outputs of the ATAM / ATAM 的输出/Primary Outputs of the ATAM / ATAM 的主要输出", "url": "https://a1npn29y3xu.feishu.cn/wiki/Q6ngwVkPKi2peOkCqpqcyI4dnjt", "source_type": "docx", "n_chars": 180, "text": "\n\n- 一组风险和非风险\n\n - 风险被定义为可能根据质量属性要求导致不良后果的架构决策。\n - 非风险是被认为安全的架构决策。\n- 一组风险主题\n\n - 检查所有风险以寻找识别架构中系统弱点的主题。\n - 这些风险主题将威胁项目的商业目标。"}
{"id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt::1099", "page_id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt", "title": "SA 讲义（五）Chapter 19, 21", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（五）Chapter 19, 21", "section": "Chapter 21 Architecture Evaluation / 架构评价/⭐ ATAM Architecture Tradeoff Analysis Method / 架构权衡分析方法/Outputs of the ATAM / ATAM 的输出/Other Outputs of the ATAM / ATAM 的其他输出", "url": "https://a1npn29y3xu.feishu.cn/wiki/Q6ngwVkPKi2peOkCqpqcyI4dnjt", "source_type": "docx", "n_chars": 161, "text": "\n\n1. 简洁的架构展示\n2. 明确的业务目标陈述。\n3. 以质量属性场景表达的优先级质量属性需求。\n4. 将架构决策映射到质量需求。\n5. 一组已识别的敏感性和权衡点：对一个或多个质量属性有显著影响的架构决策。"}
{"id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt::1100", "page_id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt", "title": "SA 讲义（五）Chapter 19, 21", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（五）Chapter 19, 21", "section": "Chapter 21 Architecture Evaluation / 架构评价/⭐ ATAM Architecture Tradeoff Analysis Method / 架构权衡分析方法/Steps of the ATAM / ATAM 的执行步骤/Present the ATAM / 展示 ATAM", "url": "https://a1npn29y3xu.feishu.cn/wiki/Q6ngwVkPKi2peOkCqpqcyI4dnjt", "source_type": "docx", "n_chars": 124, "text": "- The **evaluation leader** describes the ATAM steps in brief and the outputs of the evaluation\n- 评估领导者简要描述了ATAM步骤和评估的输出结果。"}
{"id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt::1101", "page_id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt", "title": "SA 讲义（五）Chapter 19, 21", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（五）Chapter 19, 21", "section": "Chapter 21 Architecture Evaluation / 架构评价/⭐ ATAM Architecture Tradeoff Analysis Method / 架构权衡分析方法/Steps of the ATAM / ATAM 的执行步骤/Present Business Drivers / 展示商业驱动者", "url": "https://a1npn29y3xu.feishu.cn/wiki/Q6ngwVkPKi2peOkCqpqcyI4dnjt", "source_type": "docx", "n_chars": 179, "text": "\n\n- 项目决策者（理想情况下是项目经理或系统的客户）从商业角度呈现系统概览\n- 演示应该描述\n\n - 重要的功能\n - 相关的技术、管理、经济或政治限制\n - 商业目标和背景\n - 主要利益相关者\n - 架构驱动因素（架构上重要的需求）"}
{"id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt::1102", "page_id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt", "title": "SA 讲义（五）Chapter 19, 21", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（五）Chapter 19, 21", "section": "Chapter 21 Architecture Evaluation / 架构评价/⭐ ATAM Architecture Tradeoff Analysis Method / 架构权衡分析方法/Steps of the ATAM / ATAM 的执行步骤/Present the Architecture / 展示架构", "url": "https://a1npn29y3xu.feishu.cn/wiki/Q6ngwVkPKi2peOkCqpqcyI4dnjt", "source_type": "docx", "n_chars": 159, "text": "\n\n- 主要建筑师进行演讲，描述架构\n\n - 技术限制，如规定使用的操作系统、硬件或中间件，以及其他系统必须与之交互。\n - 架构方法，即用于满足需求的模式和策略。\n- 应传达架构的本质，而不是深入细节。"}
{"id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt::1103", "page_id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt", "title": "SA 讲义（五）Chapter 19, 21", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（五）Chapter 19, 21", "section": "Chapter 21 Architecture Evaluation / 架构评价/⭐ ATAM Architecture Tradeoff Analysis Method / 架构权衡分析方法/Steps of the ATAM / ATAM 的执行步骤/Identify Architectural Approaches / 辨别架构方法", "url": "https://a1npn29y3xu.feishu.cn/wiki/Q6ngwVkPKi2peOkCqpqcyI4dnjt", "source_type": "docx", "n_chars": 117, "text": "\n\n- 理解其架构方法，特别是模式和策略。\n- 评估团队记录已识别的模式和策略。\n- 列表公开记录，并将作为后续分析的基础。"}
{"id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt::1104", "page_id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt", "title": "SA 讲义（五）Chapter 19, 21", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（五）Chapter 19, 21", "section": "Chapter 21 Architecture Evaluation / 架构评价/⭐ ATAM Architecture Tradeoff Analysis Method / 架构权衡分析方法/Steps of the ATAM / ATAM 的执行步骤/Generate Utility Tree / 生成效能树", "url": "https://a1npn29y3xu.feishu.cn/wiki/Q6ngwVkPKi2peOkCqpqcyI4dnjt", "source_type": "docx", "n_chars": 140, "text": "\n\n- 评估团队与项目决策者合作，以识别、优先排序并细化系统最重要的质量属性目标。\n- 质量属性目标通过质量属性效用树详细阐述。\n- 场景被赋予重要性等级（高、中、低）。"}
{"id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt::1105", "page_id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt", "title": "SA 讲义（五）Chapter 19, 21", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（五）Chapter 19, 21", "section": "Chapter 21 Architecture Evaluation / 架构评价/⭐ ATAM Architecture Tradeoff Analysis Method / 架构权衡分析方法/Steps of the ATAM / ATAM 的执行步骤/Analyze Architectural Approaches / 分析架构方法", "url": "https://a1npn29y3xu.feishu.cn/wiki/Q6ngwVkPKi2peOkCqpqcyI4dnjt", "source_type": "docx", "n_chars": 304, "text": "\n\n\n\n- 评估团队一次检查排名最高的场景；建筑师被要求解释架构如何支持每一个场景\n- 评估团队成员探究用于执行场景的架构方法\n- 评估团队记录相关的架构决策，并识别、分类它们的风险、非风险和权衡点。示例：\n\n - 风险：心跳频率影响系统检测故障组件的时间。\n - 权衡：心跳频率决定了检测故障的时间。更高的频率意味着更好的可用性，但会消耗更多的处理时间和通信带宽（可能会降低性能）。"}
{"id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt::1106", "page_id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt", "title": "SA 讲义（五）Chapter 19, 21", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（五）Chapter 19, 21", "section": "Chapter 21 Architecture Evaluation / 架构评价/⭐ ATAM Architecture Tradeoff Analysis Method / 架构权衡分析方法/Steps of the ATAM / ATAM 的执行步骤/Brainstorm and Prioritize Scenarios / 头脑风暴并且使场景优先化", "url": "https://a1npn29y3xu.feishu.cn/wiki/Q6ngwVkPKi2peOkCqpqcyI4dnjt", "source_type": "docx", "n_chars": 234, "text": "\n\n- 情景头脑风暴的目的是为了理解系统成功对利益相关者意味着什么。\n- 一旦收集了情景，通过投票对它们进行优先排序。\n- 将优先排序的情景列表与效用树练习中的情景进行比较。\n\n - 如果它们一致，这表明建筑师的想法与利益相关者实际想要的之间有良好的一致性。\n - 如果发现了额外的驱动情景，这本身可能是一个风险，表明利益相关者和建筑师之间存在一些分歧。"}
{"id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt::1107", "page_id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt", "title": "SA 讲义（五）Chapter 19, 21", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（五）Chapter 19, 21", "section": "Chapter 21 Architecture Evaluation / 架构评价/⭐ ATAM Architecture Tradeoff Analysis Method / 架构权衡分析方法/Steps of the ATAM / ATAM 的执行步骤/Present Results / 展示结果", "url": "https://a1npn29y3xu.feishu.cn/wiki/Q6ngwVkPKi2peOkCqpqcyI4dnjt", "source_type": "docx", "n_chars": 389, "text": "\n\n- 评估团队根据某些系统性缺陷将风险分组为风险主题。\n\n - 例如，一组关于系统在面对各种硬件和/或软件故障时无法正常运行的风险可能导致一个关于未给予足够关注以提供高可用性的风险主题。\n- 对于每个风险主题，评估团队识别出在第二步中列出的哪些业务驱动因素受到影响。\n\n\n\n- 从评估中收集的信息被总结并呈现给利益相关者。\n- 下列输出被展示：\n\n - 记录的架构方法\n - 从头脑风暴中得出的场景集及其优先级排序\n - 效用树\n - 发现的风险\n - 记录的非风险\n - 找到的敏感点和权衡点\n - 风险主题以及每个主题威胁的业务驱动因素"}
{"id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt::1108", "page_id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt", "title": "SA 讲义（五）Chapter 19, 21", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（五）Chapter 19, 21", "section": "Chapter 21 Architecture Evaluation / 架构评价/⭐ ATAM Architecture Tradeoff Analysis Method / 架构权衡分析方法/Phases of the ATAM / ATAM 的各个阶段", "url": "https://a1npn29y3xu.feishu.cn/wiki/Q6ngwVkPKi2peOkCqpqcyI4dnjt", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt::1109", "page_id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt", "title": "SA 讲义（五）Chapter 19, 21", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（五）Chapter 19, 21", "section": "Chapter 21 Architecture Evaluation / 架构评价/⭐ ATAM Architecture Tradeoff Analysis Method / 架构权衡分析方法/Lightweight Architectural Evaluation / 轻量级的架构评估", "url": "https://a1npn29y3xu.feishu.cn/wiki/Q6ngwVkPKi2peOkCqpqcyI4dnjt", "source_type": "docx", "n_chars": 237, "text": "\n\n- ATAM是一个重大的任务\n\n - 它需要评估团队付出大约20到30人天的努力，建筑师和利益相关者需要付出更多。\n - 在大型和成本高昂的项目上投入这么多时间是有意义的。\n- 一种适用于小型、风险较低项目的轻量级架构评估方法。\n\n - 可能在一天内，甚至半天的会议中完成。\n - 可能完全由组织内部的成员执行。\n - 当然，这可能不会深入探测架构。"}
{"id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt::1110", "page_id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt", "title": "SA 讲义（五）Chapter 19, 21", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（五）Chapter 19, 21", "section": "Chapter 21 Architecture Evaluation / 架构评价/⭐ ATAM Architecture Tradeoff Analysis Method / 架构权衡分析方法/Typical Agenda: 4 - 6 Hours / 常规的规划：4 \\~ 6 个小时", "url": "https://a1npn29y3xu.feishu.cn/wiki/Q6ngwVkPKi2peOkCqpqcyI4dnjt", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt::1111", "page_id": "docx::Q6ngwVkPKi2peOkCqpqcyI4dnjt", "title": "SA 讲义（五）Chapter 19, 21", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（五）Chapter 19, 21", "section": "Chapter 21 Architecture Evaluation / 架构评价/Summary / 总结", "url": "https://a1npn29y3xu.feishu.cn/wiki/Q6ngwVkPKi2peOkCqpqcyI4dnjt", "source_type": "docx", "n_chars": 240, "text": "\n\n- 如果一个系统对你来说足够重要，那么这个架构就应该被评估。\n- ATAM是一种全面的方法，用于评估软件架构。\n- 基于ATAM的轻量级架构评估，提供了一种可以在几个小时内完成的低成本架构评估。\n- 每次评估的数量和每次评估的范围可能会因项目而异。\n\n - 设计师应该在做出重要决策的过程中进行评估。\n - 在项目过程中可以多次进行轻量级评估，作为同行评审练习。"}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1112", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 15 Architectures in Agile Projects / 第十五章：架构在敏捷项目的应用", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 691, "text": "\n\n- 敏捷性是指在动荡的商业环境中创造和响应变化以获得利润的能力。\n- 敏捷软件开发是一种以人为中心的软件开发方法，它使人们能够有效地响应变化，并导致创建满足其利益相关者需求的可用系统。\n\n\n\n\n\n\n\n\n\n“架构应该做多少？”\n\n- 有两个活动可能会增加项目进度的时间：\n\n - 架构的前期设计工作以及前期风险识别、规划和解决工作。\n - 由于修复缺陷和处理修改请求而导致的返工。\n- 直观上，这两个活动是相互权衡的。\n- Boehm 和 Turner 针对三个假设项目将这两个值相互对比：\n\n - 一个项目是10千行源代码（KSLOC）。\n - 一个项目是100千行源代码（KSLOC）。\n - 一个项目是1,000千行源代码（KSLOC）。\n\n\n\nAgile Architect Advice – No.1"}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1113", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 15 Architectures in Agile Projects / 第十五章：架构在敏捷项目的应用", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 597, "text": "代码（KSLOC）。\n\n\n\nAgile Architect Advice – No.1\n\n\n\n- 如果您正在构建一个大型、复杂的系统，且需求相对稳定和已被充分理解，和/或涉及分布式开发，那么提前做大量的架构工作将是值得的。\n\nAgile Architect Advice – No.2\n\n\n\n- 在需求不稳定的大型项目上，首先快速设计一个候选架构，即使它遗漏了许多细节。\n\n - 要准备根据情况的变化修改和完善这个架构。\n - 这个早期架构将有助于：\n\n - 指导开发\n - 早期问题理解和分析\n - 团队协调\n - 创建编码模板\n\nAgile Architect Advice – No.3\n\n\n\n- 在需求不确定的小型项目上，至少尝试就将要使用的主要模式达成一致。\n\n - 不要提前在架构设计、文档或分析上花费太多时间。"}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1114", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 16 Architecture and Requirements / 第十六章：架构和需求/What is ASR? / 什么是架构重要需求？", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 166, "text": "\n\n- 对于一个架构师来说，尽管架构的存在是为了修建一个满足需求的系统，但是并不是所有的需求都是平等地被创建的\n- 一个**架构重要需求（简称 ASR）**就是将会对架构有重大影响的需求。\n- 我们应该如何发现这些需求呢？"}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1115", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 16 Architecture and Requirements / 第十六章：架构和需求/How to find ASR? / 如何找到项目需求？/① From Requirements Document / 从需求文档中", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 647, "text": "\n\n- Many projects don’t create or maintain the detailed, high-quality requirements documents. / 许多项目不创建或维护详细、高质量的需求文档。\n- Standard requirements pay more attention to functionality than quality attributes. / 标准需求更关注功能而非质量属性。\n- Architecture is driven by quality attribute requirements rather than functionalities. / 架构是由质量属性需求而非功能驱动的。\n- Most requirements specification does not affect architecture. / 大多数需求规格说明不影响架构。\n- Quality attributes are often captured poorly, e.g. / 质量属性通常捕捉得不好，例如\n\n - “The system shall be modular” / “系统应该是模块化的”\n - “The system shall exhibit high usability” / “系统应具有高可用性”"}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1116", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 16 Architecture and Requirements / 第十六章：架构和需求/How to find ASR? / 如何找到项目需求？/① From Requirements Document / 从需求文档中", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 408, "text": "system shall be modular” / “系统应该是模块化的”\n - “The system shall exhibit high usability” / “系统应具有高可用性”\n - “The system shall meet users’ performance expectations” / “系统应满足用户的性能期望”\n- Much of what is useful to an architect is not in even the best requirements document\n\n - 即使是最好的需求文档中，对架构师有用的东西也往往不在其中\n- ASRs often derive from business goals in the development organization itself\n\n - 架构需求规格（ASRs）通常源自开发组织本身的业务目标"}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1117", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 16 Architecture and Requirements / 第十六章：架构和需求/How to find ASR? / 如何找到项目需求？/② By Interviewing Stakeholders / 通过采访项目干系人", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 693, "text": "\n\n- Stakeholders often have no idea what QAs they want in a system\n\n - 利益相关者通常不清楚他们希望系统中包含哪些质量属性（QAs）\n - if you insist on quantitative QA requirements, you’re likely to get numbers that are arbitrary.\n\n - 如果你坚持要求量化的质量属性需求，你可能会得到一些随意的数字。\n - At least some of those requirements will be very difficult to satisfy.\n\n - 至少这些需求中有一些将很难满足。\n\n- Architects often have very good ideas about what QAs are reasonable to provide.\n\n - 架构师通常对提供哪些合理的质量属性有很好的想法。\n\n- Interviewing stakeholders is the surest way to learn what they know and need\n\n - 采访利益相关者是了解他们所知和所需最可靠的方式。\n\n- The results of stakeholder interviews should include\n\n - 利益相关者访谈的结果应包括"}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1118", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 16 Architecture and Requirements / 第十六章：架构和需求/How to find ASR? / 如何找到项目需求？/② By Interviewing Stakeholders / 通过采访项目干系人", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 487, "text": "采访利益相关者是了解他们所知和所需最可靠的方式。\n\n- The results of stakeholder interviews should include\n\n - 利益相关者访谈的结果应包括\n - A list of architectural drivers\n\n - 一份架构驱动因素的列表\n - a set of QA scenarios that the stakeholders (as a group) prioritized.\n\n - 一组利益相关者（作为一个群体）优先排序的质量属性场景。\n\n- The QAW is a facilitated, stakeholder-focused method to generate, prioritize, and refine quality attribute scenarios before the software architecture is completed\n\n - 质量属性工作坊（QAW）是一种在软件架构完成之前，引导利益相关者产生、优先排序和细化质量属性场景的方法。"}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1119", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 16 Architecture and Requirements / 第十六章：架构和需求/How to find ASR? / 如何找到项目需求？/以下是期末必考的质量属性场景样例，大家按照这些模板背就好/Availability / 可用性", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 554, "text": "The heartbeat monitor detects that the server is non-responsive during normal operations. The system informs the operator and continues to operate with no downtime. / 心跳监控器检测到服务器在正常运行期间无响应。系统通知操作员，并继续在没有停机的情况下运行。\n\n- **Stimulus**: non-responsiveness / **刺激**：无响应\n- **Response**: inform the operator / **响应**：通知操作员\n- **Response measure**: no downtime, or 100% availability percentage / **响应度量**：无停机时间，或100%的可用性百分比\n- **Environment**: normal operation / **环境**：正常运行\n- **Artifact**: heartbeat monitor / **工件**：心跳监控器\n- **Stimulus source**: server / **刺激源**：服务器"}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1120", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 16 Architecture and Requirements / 第十六章：架构和需求/How to find ASR? / 如何找到项目需求？/以下是期末必考的质量属性场景样例，大家按照这些模板背就好/Interoperability / 互操作性", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 658, "text": "① **Our vehicle information system** sends our current location to the **traffic monitoring system**. 我们的车辆信息系统将当前位置发送到交通监控系统。\n\n ② The traffic monitoring system combines our location with other information, overlays this information on a Google Map, and **broadcasts** it. 交通监控系统将我们的位置信息与其他信息结合，并将这些信息叠加在 Google 地图上，然后广播出去。\n\n ③ Our location information is correctly included with a probability of 99.9%. 我们的位置信息正确包含的概率为 99.9%。\n\n- **Source:** Our vehicle information system / 我们的车辆信息系统\n- **Stimulus:** A request to exchange information among system(s) / 系统间交换信息的请求\n- **Artifact:** The systems to exchange information among system(s) / 系统间交换信息的系统"}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1121", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 16 Architecture and Requirements / 第十六章：架构和需求/How to find ASR? / 如何找到项目需求？/以下是期末必考的质量属性场景样例，大家按照这些模板背就好/Interoperability / 互操作性", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 678, "text": "em(s) / 系统间交换信息的请求\n- **Artifact:** The systems to exchange information among system(s) / 系统间交换信息的系统\n- **Environment:** System(s) wishing to inter-operate are discovered at run time or known prior to run time / 希望互操作的系统在运行时被发现或在运行之前已知\n- **Response:** One or more of the following / 以下之一或多个：\n\nThe request is (appropriately) accepted and information is exchanged successfully / 请求被（适当地）接受，信息成功交换。\n\n- 车辆信息系统将位置信息发送给交通监控系统，并成功完成交换，交通监控系统成功接收并整合这些信息。\n\nThe request is logged by one or more of the involved systems / 请求被一个或多个相关系统记录。\n\n- 请求的信息交换被系统记录和追踪。\n- **Response Measure:** One or more of the following / 以下之一或多个：\n\nPercentage of information exchanges correctly processed / 正确信息交换的百分比"}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1122", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 16 Architecture and Requirements / 第十六章：架构和需求/How to find ASR? / 如何找到项目需求？/以下是期末必考的质量属性场景样例，大家按照这些模板背就好/Interoperability / 互操作性", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 300, "text": "of the following / 以下之一或多个：\n\nPercentage of information exchanges correctly processed / 正确信息交换的百分比\n\n- 在此场景中，99.9% of our location information is correctly included / 我们的位置信息正确包含的概率为 99.9%，即信息交换的正确处理率为 99.9%。\n\nPercentage of information exchanges rejected / 被拒绝的信息交换的百分比\n\n- 根据场景，未提及被拒绝的交换，因此可以假设该百分比为 0。"}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1123", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 16 Architecture and Requirements / 第十六章：架构和需求/How to find ASR? / 如何找到项目需求？/以下是期末必考的质量属性场景样例，大家按照这些模板背就好/Modifiability / 可修改性", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 480, "text": "The developer wishes to change the user interface by modifying the code at design time. The modifications are made with no side effects within three hours.\n\n 开发者希望通过在设计时修改代码来更改用户界面。修改在三小时内完成，并且没有副作用。\n\n- **Stimulus**: Wishes to change UI\n\n 刺激: 希望更改用户界面\n\n- **Artifact**: Code\n\n 工件: 代码\n\n- **Environment:** Design time\n- 环境：设计时\n- **Response:** Change made\n- 响应：已完成更改\n- **Response measure:** No side effects in three hours\n- 响应度量：三小时内无副作用\n- **Source:** Developer\n- 来源：开发者"}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1124", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 16 Architecture and Requirements / 第十六章：架构和需求/How to find ASR? / 如何找到项目需求？/以下是期末必考的质量属性场景样例，大家按照这些模板背就好/Performance / 性能", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 429, "text": "Users initiate transactions under normal operations. **The system** processes the transactions with an average latency of two seconds.\n\n用户在正常操作下发起交易。系统以平均两秒的延迟处理交易。\n\n- Stimulus: Transaction arrivals\n- 刺激：交易到达\n- Source: Users\n- 来源：用户\n- Artifact: The system\n- 工件：系统\n- Response: Process the transactions\n- 响应：处理交易\n- Response measure / Average latency of two seconds 平均延迟为两秒\n- 响应度量：\n- Environment / 环境: Under normal operation 正常操作下"}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1125", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 16 Architecture and Requirements / 第十六章：架构和需求/How to find ASR? / 如何找到项目需求？/以下是期末必考的质量属性场景样例，大家按照这些模板背就好/Security / 安全性", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 626, "text": "A disgruntled employee from a remote location attempts to modify the pay rate table during normal operations. The system maintains an audit trail and the correct data is restored within a day.\n\n一名不满的员工从远程位置试图在正常操作期间修改工资表。系统保持审计记录，并在一天内恢复正确的数据。\n\n- **Stimulus:** unauthorized attempts to modify the pay rate table 刺激：未授权的尝试修改工资表\n- **Stimulus source:** a disgruntled employee 刺激源：一名不满的员工\n- **Artifact:** the system with pay rate table 工件：包含工资表的系统\n- **Environment:** during normal operation 环境：正常操作期间\n- **Response:** maintains an audit trail 响应：保持审计记录\n- **Response measure:** correct data is restored within a day 响应度量：在一天内恢复正确的数据"}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1126", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 16 Architecture and Requirements / 第十六章：架构和需求/How to find ASR? / 如何找到项目需求？/以下是期末必考的质量属性场景样例，大家按照这些模板背就好/Testability / 可测试性", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 553, "text": "The unit tester completes a code unit during development and performs a test sequence whose results are captured and that gives 85% path coverage within 3 hours of testing.\n\n单元测试员在开发过程中完成一个代码单元，并执行一个测试序列，捕获其结果，并在 3 小时的测试内达到 85% 的路径覆盖率。\n\n- **Source / 来源:**\n\n - Unit tester 单元测试员\n- **Stimulus / 刺激:**\n\n - Code unit completed 代码单元完成\n- **Artifact / 工件:**\n\n - Code unit 代码单元\n- **Environment / 环境:**\n\n - Development 开发环境\n- **Response / 响应:**\n\n - Capture results 捕获结果\n- **Response measure / 响应度量:**\n\n - 85% path coverage in three hours 在三小时内达到 85% 的路径覆盖率"}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1127", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 16 Architecture and Requirements / 第十六章：架构和需求/How to find ASR? / 如何找到项目需求？/以下是期末必考的质量属性场景样例，大家按照这些模板背就好/Usability / 易用性", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 442, "text": "The user downloads a new application and is using it productively after two minutes of experimentation.\n\n用户下载一个新应用程序，并在两分钟的试验后开始高效使用它。\n\n- **Source / 来源:**\n- User 用户\n- **Stimulus / 刺激:**\n- Download a new application 下载新应用程序\n- **Artifact / 工件:**\n- System 系统\n- **Environment / 环境:**\n- Runtime 运行时\n- **Response / 响应:**\n- User uses application productively 用户高效使用应用程序\n- **Response measure / 响应度量:**\n- Within two minutes of experimentation 在两分钟的试验内"}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1128", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 16 Architecture and Requirements / 第十六章：架构和需求/How to find ASR? / 如何找到项目需求？/✨ (QAW) Quality Attribute Workshop / 质量属性研讨会", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 697, "text": "\n\n\n\n\n\n\n\n**第一步：QAW介绍和介绍。**\n\n- QAW协调员描述QAW的动机，并解释QAW的每一步。\n\n**第二步：业务/任务介绍。**\n\n- 代表业务关注的利益相关者介绍系统的业务背景、广泛的功能需求、约束和已知的质量属性需求。\n- 质量属性将主要从业务/任务需求中得出。\n\n**第三步：架构计划介绍。**\n\n- 架构师将介绍系统的架构计划。\n- 这让利益相关者了解当前的架构思路。\n\n**第四步：识别架构驱动因素。**\n\n- 协调员将分享在第二步和第三步中汇编的关键架构驱动因素列表。\n- 架构驱动因素包括总体需求、业务驱动因素、约束和质量属性。\n- 向利益相关者询问澄清、增加、删除和更正，并就架构驱动因素达成共识。\n\n\n\n\n\n**第五步：场景头脑风暴。**\n\n- 每位利益相关者提出一个场景，代表他或她对系统的关切。"}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1129", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 16 Architecture and Requirements / 第十六章：架构和需求/How to find ASR? / 如何找到项目需求？/✨ (QAW) Quality Attribute Workshop / 质量属性研讨会", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 326, "text": "(https://feishu.cn/file/X7AabM9I9oDHdJxEI4ucUzBCnZg)\n\n**第五步：场景头脑风暴。**\n\n- 每位利益相关者提出一个场景，代表他或她对系统的关切。\n- 协调员确保每个场景都有一个明确的刺激和响应。\n- 至少为第四步中列出的每个架构驱动因素制作一个代表性场景。\n\n**第六步：场景整合。**\n\n- 在合理的情况下，将类似的场景进行整合。\n\n**第七步：场景优先级排序。**\n\n- 为每位利益相关者分配相当于总场景数30%的投票数。\n- 每位利益相关者将他们的投票分配给不同的场景。\n\n**第八步：场景细化。**\n\n- 对排名前的场景进行细化和详述。\n- 协调员帮助利益相关者将场景以六部分场景形式表达。"}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1130", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 16 Architecture and Requirements / 第十六章：架构和需求/⭐ ④ In Utility Tree / 在效能树中", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 677, "text": "\n\n架构需求规格（ASR）必须具备以下特征：\n\n1. 对架构有深远影响：\n\n - 包含这一需求很可能导致与不包含它时完全不同的架构。\n2. 具有高商业或任务价值：\n\n - 如果架构要满足这一需求，它必须对重要的利益相关者具有高价值。\n\n\n\n- Utility Tree / 效用树：\n\n - A way to record ASRs all in one place. / 一种将ASRs集中记录在一个地方的方法。\n - Establishes priority of each ASR in terms of / 确定每个ASR的优先级，依据是：\n\n - Impact on architecture / 对架构的影响\n - Business or mission value / 商业或任务价值\n- ASRs are captured as scenarios. / ASRs被捕捉为场景。\n\n - Root of tree is placeholder node called “Utility” / 树的根节点是一个占位符节点，称为“效用”。\n - Second level of tree contains broad QA categories. / 树的第二层包含广泛的质量属性（QA）类别。"}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1131", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 16 Architecture and Requirements / 第十六章：架构和需求/⭐ ④ In Utility Tree / 在效能树中", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 661, "text": "的根节点是一个占位符节点，称为“效用”。\n - Second level of tree contains broad QA categories. / 树的第二层包含广泛的质量属性（QA）类别。\n - Third level of tree refines those categories / 树的第三层细化这些类别。\n - Leaf nodes are the concrete quality attribute scenarios / 叶节点是具体的品质属性场景。\n\n\n\n\n\nA QA or QA refinement without any ASR is not necessarily an error or omission / 一个没有对应ASR的质量属性（QA）或质量属性细化并不一定是错误或遗漏。\n\n- Attention should be paid to searching for unrecorded ASRs in that area / 应该关注寻找领域中未被记录的ASR\n\n**ASRs that rate a (H, H) rating are the ones that deserve the most attention** / 那些最值得关注的需求。"}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1132", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 16 Architecture and Requirements / 第十六章：架构和需求/⭐ ④ In Utility Tree / 在效能树中", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 340, "text": "ASR\n\n**ASRs that rate a (H, H) rating are the ones that deserve the most attention** / 那些最值得关注的需求。\n\n- A very large number of these might be a cause for concern: / 如果这类需求数量非常多，可能会引起关注：\n\n - Is the system achievable? / 系统是否可行？\n- Stakeholders can review the utility tree to make sure their concerns are addressed / 利益相关者可以审查效用树，以确保他们关注的问题得到解决。"}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1133", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 16 Architecture and Requirements / 第十六章：架构和需求/⭐ ④ In Utility Tree / 在效能树中/⑤ Typing the methods together / 将方法整合到一起", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 178, "text": "\n\n将方法结合起来使用：\n\n- 如何将需求文档、利益相关者访谈、质量属性工作坊和效用树一起使用？\n\n - 如果在需求收集过程中忽略了重要的利益相关者，使用访谈或质量属性工作坊（QAW）。\n - 使用质量属性效用树作为QAW产生的场景的存储库。"}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1134", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 16 Architecture and Requirements / 第十六章：架构和需求/Summary / 总结", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1135", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 17 Designing an Architecture / 第十七章：设计一个架构/Design Strategy / 设计策略", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 249, "text": "1. **Decomposition（分解）**：\n\n - 将复杂问题或系统分解成更小、更易于管理和理解的部分的过程。\n2. **Designing to Architecturally Significant Requirements（针对架构重要需求的设计）**：\n\n - 根据对架构有重大影响的需求来进行设计，确保架构能够满足这些关键需求。\n3. **Generate and Test（生成和测试）**：\n\n - 创建解决方案并进行测试，以验证它们是否满足既定的需求和质量属性。"}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1136", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 17 Designing an Architecture / 第十七章：设计一个架构/Design Strategy / 设计策略/Decomposition / 分解", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 513, "text": "\n\n- 架构决定质量属性。\n- 重要的质量属性是整个系统的特征。\n- 设计从整个系统开始。\n\n - 整个系统被分解成部分。\n - 每个部分可能会继承全部或部分的质量属性需求。\n\n\n\nHow Many ASRs Simultaneously? / 同时有多少个 ASR？\n\n• If you are inexperienced in design, then design for the ASRs one at a time, beginning with the most important. / 如果您对设计没有经验，那么从最重要的开始，一次设计一个 ASR。\n\n• As you gain experience, you will be able to design for multiple ASRs simultaneously. / 随着经验的积累，您将能够同时为多个 ASR 进行设计。"}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1137", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 17 Designing an Architecture / 第十七章：设计一个架构/Design Strategy / 设计策略/Generate and Test / 生成及测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1138", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 17 Designing an Architecture / 第十七章：设计一个架构/Design Strategy / 设计策略/Generate and Test / 生成及测试/Where Does the Initial Hypothesis Come From? / 初始设想的来源是？", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 168, "text": "\n\n- 现有系统\n\n– 很少有系统是完全从头开始构建的\n\n- 框架\n\n– 提供特定领域中通用服务的部分设计，例如 Web 应用程序、中间件\n\n– 设计框架可能会限制沟通\n\n通过代理或发布-订阅系统\n\n- 其他来源：模式和策略"}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1139", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 17 Designing an Architecture / 第十七章：设计一个架构/Design Strategy / 设计策略/Generate and Test / 生成及测试/How do I Test a Hypothesis? / 我应该如何测试设想？", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 232, "text": "• The **analysis technique** described previously\n\n• What is the output of the tests?\n\n– List of requirements – either responsibilities or quality – **not met** by current design.\n\n• 前面描述的分析技术\n\n• 测试的输出是什么？\n\n– 要求清单 – 责任或质量 – 当前设计未满足。"}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1140", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 17 Designing an Architecture / 第十七章：设计一个架构/Design Strategy / 设计策略/Generate and Test / 生成及测试/How Do I Generate the Next Hypothesis? / 我应该如何生成下一个设想？", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 305, "text": "• Add missing responsibilities.\n\n• Use tactics to adjust quality attribute behavior of hypothesis.\n\n– The choice of tactics will depend on which quality attribute requirements are not met.\n\n– Be mindful of the side effects of a tactic.\n\n• 添加缺失的职责。\n\n• 使用策略调整假设的质量属性行为。\n\n– 策略的选择将取决于未满足哪些质量属性要求。\n\n– 注意策略的副作用。"}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1141", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 17 Designing an Architecture / 第十七章：设计一个架构/Design Strategy / 设计策略/Generate and Test / 生成及测试/What Am I Done? / 我做了什么？", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1142", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 17 Designing an Architecture / 第十七章：设计一个架构/(ADD) Attribute-Driven Design Method / 属性驱动设计方法", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 169, "text": "\n\n\n\n"}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1143", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 17 Designing an Architecture / 第十七章：设计一个架构/(ADD) Attribute-Driven Design Method / 属性驱动设计方法/Inputs / 输入", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 332, "text": "Requirements / 需求\n\n- **Functional, quality, constraints / 功能、质量、约束**\n\nA context description / 上下文描述\n\n- What are the boundary of the system being designed? / 正在设计的系统的边界是什么？\n- What are the external systems, devices, users and environment conditions with which the system being designed must interact? / 被设计的系统必须与哪些外部系统、设备、用户和环境条件进行交互？"}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1144", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 17 Designing an Architecture / 第十七章：设计一个架构/(ADD) Attribute-Driven Design Method / 属性驱动设计方法/Outputs / 输出", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 177, "text": "Architectural elements and their relationship / 架构元素和它们的关系\n\n- **Responsibility** of elements / 元素的职责\n- **Interactions** / 交互\n- **Information flow** among the elements / 元素之间的信息流"}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1145", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 17 Designing an Architecture / 第十七章：设计一个架构/(ADD) Attribute-Driven Design Method / 属性驱动设计方法/Steps / 步骤", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1146", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 17 Designing an Architecture / 第十七章：设计一个架构/(ADD) Attribute-Driven Design Method / 属性驱动设计方法/Steps / 步骤/① Choose an element of the system to design / 选择系统的一个元素去设计", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 445, "text": "\n\nFor green field designs, the element chosen is usually the whole system.\n\n对于绿地设计，选择的元素通常是整个系统。\n\nFor legacy designs, the element is the portion to be added.\n\n对于遗留设计，元素是要添加的部分。\n\n\n\n\n\n\n\nBFS DFS\n\n使用了新技术：DFS\n\n团队需要工作：DFS\n\n其他情况：BFS"}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1147", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 17 Designing an Architecture / 第十七章：设计一个架构/(ADD) Attribute-Driven Design Method / 属性驱动设计方法/Steps / 步骤/② Identify the ASRs for the chosen part / 为被选择的部分定义 ASR（架构重要需求）", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 350, "text": "\n\nIf the chosen element is the whole system,then use a utility tree (as described earlier).\n\n如果选择的元素是整个系统，那么使用一个实用工具树（如前面所述）。\n\nIf the chosen element is further down the decomposition tree, then generate a utility tree from the requirements for that element.\n\n如果选择的元素在分解树的更下面，那么根据该元素的需求生成一个实用工具树。"}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1148", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 17 Designing an Architecture / 第十七章：设计一个架构/(ADD) Attribute-Driven Design Method / 属性驱动设计方法/Steps / 步骤/③ Generate a design solution for the chosen element / 为被选择的部分生成一个设计解决方案", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 140, "text": "Apply generate and test to the chosen element with its ASRs. / 将生成和测试应用于所选元素及其 ASR。\n\n"}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1149", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 17 Designing an Architecture / 第十七章：设计一个架构/(ADD) Attribute-Driven Design Method / 属性驱动设计方法/Steps / 步骤/④ Inventory remaining requirements and select the input for the next iteration / 清点剩余要求并选择下一次迭代的输入", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 199, "text": "\n\n对于每个功能需求\n\n- 确保满足该需求。\n- 如果不是，则添加职责以满足需求：\n\n - 将它们添加到具有类似要求的容器中\n - 如果没有这样的容器，可能需要创建新的容器或添加到具有不同职责的容器中（连贯性）\n - 如果容器对团队的要求太多，请将其分成两部分。拆分时尽量实现松耦合"}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1150", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 17 Designing an Architecture / 第十七章：设计一个架构/(ADD) Attribute-Driven Design Method / 属性驱动设计方法/Steps / 步骤/Quality Attribute Requirements / 质量属性需求", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 193, "text": "\n\n- 如果已经满足了质量属性需求，则不需要进一步考虑\n- 如果质量属性要求未得到满足，则采取任意一种操作\n\n - 将其**委派**给其中一名子元素\n - 将其在子元素之间进行**分割**\n- 如果质量属性不能得到满足，请检查是否可以弱化。如果不能满足或弱化，则不能满足。"}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1151", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 17 Designing an Architecture / 第十七章：设计一个架构/(ADD) Attribute-Driven Design Method / 属性驱动设计方法/Steps / 步骤/Repeat steps 1 \\~ 4 until all ASRs have been satisfied.", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 287, "text": "At the end of step 4, each child element will have associated with it a set of:\n\n- functional requirements\n- quality attribute requirements, and\n- constraints.\n\nThis sets up the child element for the next iteration of the method\n\n在第4步的末尾，每个子元素将有一组与之相关联的：功能需求、质量属性需求和约束。\n\n这将为方法的下一次迭代设置子元素"}
{"id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f::1152", "page_id": "docx::Kxggw6yRZixCWIkbdsfcW2Pcn3f", "title": "SA 讲义（四）Chapter 15 ~ 17", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/SA 讲义（四）Chapter 15 ~ 17", "section": "Chapter 17 Designing an Architecture / 第十七章：设计一个架构/Summary", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kxggw6yRZixCWIkbdsfcW2Pcn3f", "source_type": "docx", "n_chars": 186, "text": "\n\n- 设计策略\n\n - 分解\n - 根据具有重要建筑意义的要求进行设计\n - 生成和测试\n- 属性驱动设计\n\n - **选择系统中的某一部分**进行设计。\n - **满足**该部分的所有建筑重要需求。\n - **生成并测试**该零件的**设计**。"}
{"id": "docx::Y5enw8LfZiZJqikMpsscmPq5nlb::1153", "page_id": "docx::Y5enw8LfZiZJqikMpsscmPq5nlb", "title": "ST PPT 2025", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025", "section": "2025 新版 PPT", "url": "https://a1npn29y3xu.feishu.cn/wiki/Y5enw8LfZiZJqikMpsscmPq5nlb", "source_type": "docx", "n_chars": 700, "text": "\n\n\n\n> 2025年4月20日18时后，相关PDF应该已经可见了"}
{"id": "docx::DQG7wqJ6fiqIOekOerScFbZLnxb::1156", "page_id": "docx::DQG7wqJ6fiqIOekOerScFbZLnxb", "title": "ST 概念题专项复习", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 概念题专项复习", "section": "官方术语表", "url": "https://a1npn29y3xu.feishu.cn/wiki/DQG7wqJ6fiqIOekOerScFbZLnxb", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::Waj8wO2yyiuGj0kzq3EcQY2wnsc::1157", "page_id": "docx::Waj8wO2yyiuGj0kzq3EcQY2wnsc", "title": "ST 考点对比 2024 vs 2025", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 考点对比 2024 vs 2025", "section": "ST 考点对比 2024 vs 2025/考点差异/一、敏捷模型", "url": "https://a1npn29y3xu.feishu.cn/wiki/Waj8wO2yyiuGj0kzq3EcQY2wnsc", "source_type": "docx", "n_chars": 226, "text": "\n\n\n\n\n\n"}
{"id": "docx::Waj8wO2yyiuGj0kzq3EcQY2wnsc::1158", "page_id": "docx::Waj8wO2yyiuGj0kzq3EcQY2wnsc", "title": "ST 考点对比 2024 vs 2025", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 考点对比 2024 vs 2025", "section": "ST 考点对比 2024 vs 2025/考点差异/二、TDD 的侧重点不同", "url": "https://a1npn29y3xu.feishu.cn/wiki/Waj8wO2yyiuGj0kzq3EcQY2wnsc", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::Waj8wO2yyiuGj0kzq3EcQY2wnsc::1159", "page_id": "docx::Waj8wO2yyiuGj0kzq3EcQY2wnsc", "title": "ST 考点对比 2024 vs 2025", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 考点对比 2024 vs 2025", "section": "ST 考点对比 2024 vs 2025/考点差异/三、Unit Test 考得浅了", "url": "https://a1npn29y3xu.feishu.cn/wiki/Waj8wO2yyiuGj0kzq3EcQY2wnsc", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::Waj8wO2yyiuGj0kzq3EcQY2wnsc::1160", "page_id": "docx::Waj8wO2yyiuGj0kzq3EcQY2wnsc", "title": "ST 考点对比 2024 vs 2025", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 考点对比 2024 vs 2025", "section": "ST 考点对比 2024 vs 2025/考点差异/四、新增容量测试的对比信息", "url": "https://a1npn29y3xu.feishu.cn/wiki/Waj8wO2yyiuGj0kzq3EcQY2wnsc", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::Waj8wO2yyiuGj0kzq3EcQY2wnsc::1161", "page_id": "docx::Waj8wO2yyiuGj0kzq3EcQY2wnsc", "title": "ST 考点对比 2024 vs 2025", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 考点对比 2024 vs 2025", "section": "ST 考点对比 2024 vs 2025/考点差异/五、Code Review 重心在正式的回顾上", "url": "https://a1npn29y3xu.feishu.cn/wiki/Waj8wO2yyiuGj0kzq3EcQY2wnsc", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::Waj8wO2yyiuGj0kzq3EcQY2wnsc::1162", "page_id": "docx::Waj8wO2yyiuGj0kzq3EcQY2wnsc", "title": "ST 考点对比 2024 vs 2025", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 考点对比 2024 vs 2025", "section": "ST 考点对比 2024 vs 2025/考点差异/六、需要举出数据引用的错误有哪些", "url": "https://a1npn29y3xu.feishu.cn/wiki/Waj8wO2yyiuGj0kzq3EcQY2wnsc", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::Waj8wO2yyiuGj0kzq3EcQY2wnsc::1163", "page_id": "docx::Waj8wO2yyiuGj0kzq3EcQY2wnsc", "title": "ST 考点对比 2024 vs 2025", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 考点对比 2024 vs 2025", "section": "ST 考点对比 2024 vs 2025/考点差异/七、自动化测试不考", "url": "https://a1npn29y3xu.feishu.cn/wiki/Waj8wO2yyiuGj0kzq3EcQY2wnsc", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1164", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "ST 讲义（一）测试介绍", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 41, "text": "ST 讲义（一）测试介绍\n\n初稿已完成更新，重点是打🌟的几个概念，很有可能考概念题"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1165", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "Ch0 Course Overview 课程概览/软件测试：判断质量 + 发现错误", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 82, "text": "A systematic approach to **judge quality and discover bugs**.\n\n**判断质量和发现错误**的系统方法。"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1166", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "Ch0 Course Overview 课程概览/课程目标", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 590, "text": "Ø Understand the **concepts and theory** related to software testing and quality assurance\n\nØ Understand the relationship between **black-box and white-box** testing, and know how to apply as appropriate\n\nØ Understand different **testing techniques and processes** used for developing test cases and evaluating test adequacy\n\nØ Learn to use **automated testing tools** efficiently and effectively\n\nØ Understand current state of software testing and maintenance\n\nØ 了解软件测试和质保相关的**概念和理论**\n\nØ 了解**黑盒和白盒测试**的关系，知道如何酌情申请\n\nØ 了解用于开发测试用例和评估测试充分性的不同**测试技术和流程**\n\nØ 学会**高效有效的使用**自动化测试工具\n\nØ 了解软件测试和维护的现状"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1167", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "Ch0 Course Overview 课程概览/课程与课本对应", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 77, "text": "上课的顺序和原本课本的行文思路是不一样的\n\n"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1168", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "Ch1-1 Introduction/序、软件工程知识体系：SWEBOK", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 150, "text": "\n\n软件工程知识体系：SWEBOK https://www.ieee.org/about/ieee-india/ieee-computer-society-india/swebok.html"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1169", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "Ch1-1 Introduction/1.1 什么是软件？", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 677, "text": "软件通常包括一系列的：**指令、数据结构、配置文件、系统文档、用户文档**\n\nØ A software system usually consists of a number of :\n\n§ **Instructions** within separate programs that when executed some desired function\n\n§ **Data structures** that enable the programs to adequately manipulate information\n\n§ **Configuration files** which are used to set up these programs\n\n§ **System documentation** which describes the structure of the system\n\n§ **User documentation** which explains how to use the system and websites for users to download recent product information\n\nØ 一个软件系统通常由多个...组成：\n\n§ 单独程序中的**指令**，当执行某些所需功能时\n\n§ 使程序能够充分操作信息的**数据结构**\n\n§ 用于设置这些程序的**配置文件**\n\n§ 描述系统结构的**系统文档**\n\n§ **用户文档**，解释了如何使用系统和网站，供用户下载最近的产品信息"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1170", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "Ch1-1 Introduction/1.1 什么是软件？", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 682, "text": "使程序能够充分操作信息的**数据结构**\n\n§ 用于设置这些程序的**配置文件**\n\n§ 描述系统结构的**系统文档**\n\n§ **用户文档**，解释了如何使用系统和网站，供用户下载最近的产品信息\n\n\n\n- 软件定义行为（服务器、存储、网络路由、交换网络、其他基础架构）\n- 今天的软件市场更大、竞争更多、用户更多\n- 嵌入式控制软件越来越多（飞机航空、航天飞船、手表、烤炉、远程控制器）\n- **敏捷开发为测试人员保障质量增加了压力**\n\nIndustry is going through a revolution in what testing means to the success of software products\n\n行业正在经历一场革命，即测试对软件产品的成功意味着什么\n\n**QUALITY AND SOFTWARE**\n\nØ There are risks associated with Software Development\n\n§ Modern programs are complex and have ten thousands of lines of code\n\n§ The customer’s requirements can be vague, lacking in exactness\n\n§ Deadlines and budgets put pressure on the development team"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1171", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "Ch1-1 Introduction/1.1 什么是软件？", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 689, "text": "s can be vague, lacking in exactness\n\n§ Deadlines and budgets put pressure on the development team\n\nØ The combination of these factors can lead to a lack emphasis being placed on the final quality of the software product\n\n§ Poor quality can result in software failure resulting in high maintenance costs and long delays before the final deployment\n\n§ The impact on the business can be loss of reputation, legal claims, decrease in market share\n\nØ 软件开发存在风险\n\n§ 现代程序很复杂，有一万行代码\n\n § 客户的要求可能含糊不清，缺乏准确性\n\n§ 截止日期和预算给开发团队带来压力\n\nØ 这些因素的结合可能导致对软件产品的最终质量缺乏重视\n\n § 质量差可能导致软件故障，导致最终部署前的高维护成本和长时间延迟\n\n § 对业务的影响可能是声誉损失、法律索赔、市场份额下降\n\nØ The International Standard can provide\n\n§ support for setting quality goals"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1172", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "Ch1-1 Introduction/1.1 什么是软件？", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 599, "text": "可能是声誉损失、法律索赔、市场份额下降\n\nØ The International Standard can provide\n\n§ support for setting quality goals\n\n§ support for design review, verification and validation.\n\nØ The International Standard\n\n1. A quality in use model composed of five characteristics\n2. A product quality model composed of eight characteristics (which are further subdivided into\n\nsubcharacteristics)\n\nØ Be applicable to all software products and computer systems\n\nØ 国际标准可提供\n\n§ 支持设定质量目标\n\n§ 支持设计审查、验证和确认。\n\nØ 国际标准\n\n1. 由五个特征组成的使用质量模型\n2. 由八个特征组成的产品质量模型（进一步细分为子特征）\n\nØ 适用于所有软件产品和计算机系统\n\n"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1173", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "Ch1-1 Introduction/1.2 什么是 BUG？", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 68, "text": "BUG 是非正式的统称\n\n"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1174", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "Ch1-1 Introduction/🌟 1.3 Fault（故障）Error（错误） Failure（失效）/定义（必考！）/Error 错误 错误的内部状态（内部 ROR）", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 401, "text": "\n\nSoftware Fault（软件故障）：A static defect in the software 软件的静态缺陷\n\nSoftware Failure（软件失效）：**External, incorrect behavior** with respect to the requirements or other description of the expected behavior 与需求或预期行为的其他描述相关的**外部的、不正确的行为**\n\nSoftware Error（软件错误）：An **incorrect internal state** that is the manifestation of some fault\n\n**不正确的内部状态**，是某些故障的表现"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1175", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "Ch1-1 Introduction/🌟 1.3 Fault（故障）Error（错误） Failure（失效）/定义（必考！）/DS 解析", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 60, "text": "软件故障（Fault）、软件错误（Error）、软件失效（Failure）的关系可以通过以下类比和定义来解析：\n\n---"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1176", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "Ch1-1 Introduction/🌟 1.3 Fault（故障）Error（错误） Failure（失效）/定义（必考！）/DS 解析/**1. 核心定义与关系**", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 348, "text": "**软件故障（Fault）**\n\n相当于软件中的“先天缺陷”，是静态存在于代码、设计或文档中的偏差。例如：需求遗漏、逻辑错误、未处理的异常分支等。\n\n**类比**：医生发现的“根本病因”（如基因缺陷或器官结构异常），可能潜伏多年未被激活。\n\n**软件错误（Error）**\n\n是软件运行时因故障被激活导致的**内部状态异常**。例如：变量值越界、内存溢出、信号逻辑错误等。\n\n**类比**：医生检测到的异常指标（如高血压、细菌感染），代表系统内部已偏离正常状态。\n\n**软件失效（Failure）**\n\n是错误未被处理时，软件**外部可感知的功能丧失**。例如：系统崩溃、功能输出错误、用户请求超时等。\n\n**类比**：患者表现出的症状（如疼痛、器官衰竭），是内部问题传递到外部的结果。\n\n---"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1177", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "Ch1-1 Introduction/🌟 1.3 Fault（故障）Error（错误） Failure（失效）/定义（必考！）/DS 解析/**2. 因果链与动态过程**", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 302, "text": "三者遵循 **Fault → Error → Failure** 的传导路径：\n\n- **Fault**（缺陷存在）→ 被特定条件激活 → **Error**（内部异常）→ 未及时修复/容错 → **Failure**（外部失效）\n\n例如：\n\n- **Fault**：代码未处理除零异常 → **Error**：运行时变量值变为无穷大 → **Failure**：系统返回错误结果或崩溃\n\n**关键区别**：\n\n- **软件故障是静态的**，可能长期存在而不引发失效（如冗余系统中的未激活缺陷）；\n- **硬件故障可能是动态的**（如元件老化、物理磨损），但软件故障仅由设计/实现时的错误导致。\n\n---"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1178", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "Ch1-1 Introduction/🌟 1.3 Fault（故障）Error（错误） Failure（失效）/定义（必考！）/DS 解析/**3. 与医疗类比的对应**", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 312, "text": "| 概念 | 软件领域 | 医疗类比 |\n|-|-|-|\n| **Fault（故障 - 静态缺陷）** | 代码/设计缺陷（如未处理异常分支） | 先天基因缺陷、器官结构异常 |\n| **Error（错误 - 外部错误）** | 运行时内部状态异常（如内存泄漏、信号冲突） | 检测到的异常指标（细菌感染、电解质失衡） |\n| **Failure（失效 - 中间内部）** | 用户可见的功能失效（如系统崩溃、输出错误） | 外显症状（疼痛、器官衰竭） |\n\n**差异点**：\n\n- 软件故障不会“随时间退化”，而是从开发阶段就存在；\n- 硬件故障可能因物理老化（类似人体器官衰老），但软件失效仅由激活的缺陷引起。\n\n---"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1179", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "Ch1-1 Introduction/🌟 1.3 Fault（故障）Error（错误） Failure（失效）/定义（必考！）/DS 解析/**4. 实际场景举例**", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 243, "text": "**案例1：自动驾驶制动系统**\n\n- **Fault**：软件未考虑传感器信号突变（设计缺陷）\n\n→ **Error**：ECU接收到不合理的制动踏板信号（内部状态异常）\n\n→ **Failure**：车辆意外紧急制动（用户可感知的危险行为）。\n\n**案例2：金融交易系统**\n\n- **Fault**：代码中未处理浮点数精度问题（编码错误）\n\n→ **Error**：计算利息时产生微小偏差（内部数据错误）\n\n→ **Failure**：用户账户余额显示异常（功能失效）。\n\n---"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1180", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "Ch1-1 Introduction/🌟 1.3 Fault（故障）Error（错误） Failure（失效）/定义（必考！）/DS 解析/**总结**", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 150, "text": "- **Fault是根源**，需通过代码审查、静态分析预防；\n- **Error是中间态**，需依赖运行时监控和容错机制拦截；\n- **Failure是终点**，需通过用户反馈和测试回溯修复。\n\n三者关系类似于疾病从病因到症状的传导，但软件缺陷的“先天固化性”使其与硬件/生物系统的动态退化本质不同。"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1181", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "Ch1-1 Introduction/🌟 1.3 Fault（故障）Error（错误） Failure（失效）/定义（必考！）/例题 1", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 583, "text": "```Java\npublic static int numZero (int[] arr) {\n // Effects: If arr is null throw NullPointerException\n // else return the number of occurrences of 0 in arr\n int count = 0;\n // Fault（静态）: 数组遍历应该从 0 开始遍历，不是 1\n for (int i = 1; i < arr.length; i++)\n {\n if (arr[i] == 0)\n {\n count++;\n }\n }\n return count;\n}\n```\n\n测试用例 1\n\n[2, 7, 0]\n\n预期输出：1\n\n实际输出：1\n\nError（内部状态）：i = 1, 不是 0，在第一轮循环\n\nFailure（外部错误）：无\n\n测试用例 2\n\n[0, 2, 7, 0]\n\n预期输出：2\n\n实际输出：1\n\nError（内部状态）：i = 1, 不是 0，在第一轮循环\n\n**错误感染（propagates）到了变量 count**\n\nFailure（外部错误）：在返回的时候，count 的结果为 1"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1182", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "Ch1-1 Introduction/🌟 1.3 Fault（故障）Error（错误） Failure（失效）/PIE Model/Execution 执行（Fault） - Infection 感染（Error） - Propagation 传播（Failure）", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 544, "text": "Execution/Reachability:\n\nThe location or locations in the program that contain the faults must be reached.\n\n执行/触达能力：\n\n必须到达程序中包含故障的一个或多个位置\n\nA test may not execute the location of the fault !（测试可能无法执行故障位置！）\n\nInfection:\n\nThe state of the program must be incorrect.\n\n感染：\n\n程序的状态一定不正确\n\nA test executing the fault may not produce an error !（执行故障的测试可能不会产生错误！）\n\nPropagation:\n\nThe infected state must propagate to cause some output of the program to be incorrect.\n\n传播：\n\n感染状态必须传播以导致程序的某些输出不正确。\n\nAn error may not be propagated to the output !（错误可能不会传播到输出！）"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1183", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "Ch1-1 Introduction/🌟 1.3 Fault（故障）Error（错误） Failure（失效）/PIE Model/例题 2：设计测试用例", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 513, "text": "1. T1 执行故障，但没有错误\n2. T2 执行故障且产生错误，但是没有失效\n3. T3 出现失效\n\n```Java\npublic static double computeMean (int[] arr) {\n // Effects: If arr is null throw NullPointerException\n // else return the number of occurrences of 0 in arr\n int length = arr.length - 1; // Fault（静态）：应该被设置为数组长度 arr.length\n double mean, sum;\n sum = 0.0;\n\n for (int i = 0; i < length; i++)\n {\n sum += arr[i];\n }\n mean = sum / (double) length;\n return mean;\n}\n```\n\n"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1184", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "Ch1-1 Introduction/🌟 1.3 Fault（故障）Error（错误） Failure（失效）/PIE Model/例题 2：设计测试用例/参考答案", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 264, "text": "| CASE ID | Input | Fault | Error | Failure | sum（中间态） | mean（结果） |\n|-|-|-|-|-|-|-|\n| 1（执行故障无错误） | [-3, 3, 0] | ！ | | | 0（✅） | 0（✅） |\n| 2（执行故障且产生错误，但是没有失效） | [3, 5, 4] | ！ | ！ | | 8（✖，12 才对） | 4（✅） |\n| 3（失效了） | [3, 4, 5] | ！ | ！ | ！ | 7（✖，12 才对） | 3.5（✖，4 才对） |"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1185", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "Ch1-2 Introduction/🌟 2.1 Validation（结果导向，符合预期） & Verification（过程导向，满足需求）", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 684, "text": "- **Verification** : The process of determining whether the products of a given phase of the software development process **fulfill the requirements** established during the previous phase.\n- 验证：确定软件开发过程给定阶段的产品是否**满足上一阶段建立的需求**的过程。\n- 换句话说：我们正确地生产了产品吗？（强调过程）\n- **Validation** : The process of evaluating software at the end of software development to ensure **compliance with intended usage**.\n- 确认：在软件开发结束时评估软件以确保**符合预期用途**的过程。\n- 换句话说：我们生产的产品是正确的吗？（强调结果）\n\n**🌟 Specifications / 规范**\n\n Specifications play a key role. / 规范起着关键作用\n\n Detailed specifications provide the correct behavior of the software. / 详细规范提供了软件的正确行为\n\n They must describe normal and error behavior. / 它们必须描述正常和错误行为"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1186", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "Ch1-2 Introduction/🌟 2.1 Validation（结果导向，符合预期） & Verification（过程导向，满足需求）/**🌟 规范和 BUG 的关系？**", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 535, "text": "The software does not do something that the specification says it should do.\n\nThe software does something that the specification says it should not do.\n\nThe software does something that the specification does not mention.\n\nThe software does not do something that the product specification does not mention but should.\n\nThe software is difficult to understand, hard to use, slow ...\n\n规范应该做的没做，不该做的做了，未提及的做了，默认做的没做\n\n软件太慢太难用/理解\n\n\n\nVery - Verification - 过程导向\n\nVali - Validation - 结果导向"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1187", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "Ch1-2 Introduction/🌟 2.1 Validation（结果导向，符合预期） & Verification（过程导向，满足需求）/DS ：**如何区分 Verification（验证）与 Validation（确认）？**", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 85, "text": "Verification 和 Validation 虽然都以 \"V\" 开头，但核心差异在于**焦点和目标**。以下是基于 ISO 标准和实际场景的清晰区分方法：\n\n---"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1188", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "Ch1-2 Introduction/🌟 2.1 Validation（结果导向，符合预期） & Verification（过程导向，满足需求）/DS ：**如何区分 Verification（验证）与 Validation（确认）？**/**1. 核心区别：过程 vs 结果**", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 313, "text": "| **维度** | **Verification（验证）** | **Validation（确认）** |\n|-|-|-|\n| **焦点** | **过程正确性**（是否按规范做） | **结果正确性**（是否满足用户需求） |\n| **问题** | “我们是否正确地构建了产品？” | “我们构建的是正确的产品吗？” |\n| **验证对象** | 设计规范、代码逻辑、技术文档等 | 用户实际需求、场景适用性 |\n| **阶段** | **开发过程中**（如代码审查、单元测试） | **开发完成后**（如用户测试、临床评估） |\n| **类比** | 按菜谱检查食材用量和火候 | 品尝菜品是否符合食客口味 |\n\n---"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1189", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "Ch1-2 Introduction/🌟 2.1 Validation（结果导向，符合预期） & Verification（过程导向，满足需求）/DS ：**如何区分 Verification（验证）与 Validation（确认）？**/**2. 记忆技巧**/**（1）口诀法**", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 44, "text": "**口诀**：\n\n> **“Veri过程，Valid结果；前者对步骤，后者对用途。”**"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1190", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "Ch1-2 Introduction/🌟 2.1 Validation（结果导向，符合预期） & Verification（过程导向，满足需求）/DS ：**如何区分 Verification（验证）与 Validation（确认）？**/**2. 记忆技巧**/**（2）生活场景类比**", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 184, "text": "- **自动驾驶系统**：\n\n - **Verification**：测试传感器代码是否按规范处理信号；\n - **Validation**：车辆在真实道路中能否安全避障。\n- **医疗设备**：\n\n - **Verification**：检查除颤器是否输出指定电压脉冲；\n - **Validation**：医生在手术室中能否用该设备成功抢救患者。\n\n---"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1191", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "Ch1-2 Introduction/🌟 2.1 Validation（结果导向，符合预期） & Verification（过程导向，满足需求）/DS ：**如何区分 Verification（验证）与 Validation（确认）？**/**3. 实际应用场景**/**（1）软件开发**", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 91, "text": "- **Verification**：通过单元测试、静态代码分析确保代码符合设计文档；\n- **Validation**：通过**用户验收测试（UAT）**验证软件是否解决用户痛点。"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1192", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "Ch1-2 Introduction/🌟 2.1 Validation（结果导向，符合预期） & Verification（过程导向，满足需求）/DS ：**如何区分 Verification（验证）与 Validation（确认）？**/**3. 实际应用场景**/**（2）医疗器械**", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 102, "text": "- **Verification**：按 IEC 62304 进行可用性验证（如字体大小是否符合人体工学规范）；\n- **Validation**：通过临床评估证明设备在真实医疗环境中安全有效。\n\n---"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1193", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "Ch1-2 Introduction/🌟 2.1 Validation（结果导向，符合预期） & Verification（过程导向，满足需求）/DS ：**如何区分 Verification（验证）与 Validation（确认）？**/**4. 常见误区与注意事项**", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 221, "text": "- **误区1**：认为 Validation 比 Verification 更重要。\n\n - **纠正**：两者互补！未通过 Verification 的软件可能无法进入 Validation 阶段（如代码漏洞导致功能崩溃）。\n- **误区2**：将 Verification 等同于测试。\n\n - **纠正**：Verification 包括代码审查、设计评审等非测试手段；Validation 需用户参与（如可用性测试）。\n\n---"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1194", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "Ch1-2 Introduction/🌟 2.1 Validation（结果导向，符合预期） & Verification（过程导向，满足需求）/DS ：**如何区分 Verification（验证）与 Validation（确认）？**/**5. 终极记忆法**", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 104, "text": "> **“Verification是‘做对事’，Validation是‘做对的事’。”**\n>\n> （前者确保步骤正确，后者确保方向正确）\n\n通过以上方法，可以快速区分两者的核心差异，并在实际项目中精准应用。"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1195", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "Ch1-2 Introduction/2.2 Software Testing Axioms / 测试公理（公理无需证明）", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 581, "text": "\n\n1. 输入太大、输出太大、路径太多、定义开放\n2. 既然无法穷举测试，无论怎么测，都会有经济风险、安全风险。所以这门课的目的是教软件测开的工作人员如何在不破产的前提下尽量降低风险\n\n\n\n1. Dijkstra 老爷子的原话，不解释\n2. 杀虫剂效应（如果程序员在某个点粗心，那么很有可能在一片代码都会粗心犯错，所以 bug 很有可能只是冰山一角，需要持续的写新的、不同的测试用例）\n3. 没时间了、不一定是 BUG（万一是定义出错了呢？）、修复风险太大、不值得修\n4. Bugs that are undiscovered are called latent bugs. 未被发现的错误称为潜在错误。\n5. 软件工程的目标是“移动的、快速变化的”，但是传统工程是谋定而后动\n6. 测试人员是绿叶，做好三件事：发现bug，尽早发现bug，确保bug被修复\n\n\n\n1. 如果软件 BUG 太多，积重难返成本就太高了，所以要有职业精神"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1196", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "Ch1-2 Introduction/2.3 Goals of a Software Tester / 软件测试人员的目标", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 260, "text": "find early fixed\n\n- 发现 BUGS\n- 越早发现 BUGS 越好\n- 确保这些 BUG 被修复\n\n请注意，我们并不是*消除所有的 BUG*，目前来看这个情况不现实\n\nTo **identify the ideal test** – that is, the **minimum test data** required to ensure that the software works for all inputs. / 确定**理想的测试**，即确保软件适用于所有输入所需的**最少测试数据**。"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1197", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "🌟 Ch2 Test Process 测试流程/ Waterfall Model 瀑布模型", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 612, "text": "- 所有的计划在一开始就完成了，一旦被创建了以后就无法被改变\n- There is **no overlap** between any of the subsequent phases.\n\n任何后续阶段之间都**没有重叠**。\n\n- Often anyone’s first chance to “see” the program is at the very end once the testing is complete.\n\n通常任何人第一次“看到”该计划的机会是在测试完成后的最后。\n\n优势If time is spent early on making sure that the requirements and design are absolutely correct, then this will save much time and effort later.（如果早期设计是完全正确的，那么之后能节约很多时间）There is an emphasis on documentation which keeps all knowledge in a central repository and can be referenced easily by new members joining the team.（重点是文档，它将所有知识保存在一个中央存储库中，并且可以很容易地被加入团队的新成员引用。"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1198", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "🌟 Ch2 Test Process 测试流程/ Waterfall Model 瀑布模型", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 700, "text": "n be referenced easily by new members joining the team.（重点是文档，它将所有知识保存在一个中央存储库中，并且可以很容易地被加入团队的新成员引用。）不足Few visible signs of progress until the end of the project （直到项目结束，几乎没有明显的进展迹象）It is not flexible to changes （针对变化不灵活）Time-consuming to produce all the documentation（文档生成耗时）Tests are only carried out at the end – this could mean a compromise if time or budgetary constraints exist（测试只在最终环节被实施：如果存在时间或预算限制，这可能意味着妥协）Having to test the program as a whole could result in incomplete testing （将程序作为一个整体进行测试会导致不完全的测试）If testing does identify a fault that suggests a redesign it may be ignored because of the trouble involved（如果测试确实发现了建议重新设计的故障，则可能会因为涉及的问题而被忽略）If the customer is unhappy it may incur a l"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1199", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "🌟 Ch2 Test Process 测试流程/ Waterfall Model 瀑布模型", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 169, "text": "the trouble involved（如果测试确实发现了建议重新设计的故障，则可能会因为涉及的问题而被忽略）If the customer is unhappy it may incur a long maintenance phase resolving their issues（顾客不满意的话，需要长时间的维护需解决他们的诉求）"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1200", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "🌟 Ch2 Test Process 测试流程/ Spiral Model 螺旋模型", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 332, "text": "开发 → 迭代：对**每一个迭代模型进行评审以及验证**\n\n- **风险驱动**的开发流程\n- 组合了**瀑布模型**以及**快速原型迭代模型**\n- 从**目标设计**开始，从客户回顾流程结束\n\n1. 决定目标\n2. 识别风险\n3. 开发 & 测试\n4. 计划下一轮迭代\n\n\n\n\n\n优势：功能更改可适当推后、成本估计简单、风险管理有效、开发快、有用户反馈空间\n\n缺点：可能无法按时 + 平账、只适用于大项目、管理严格、文档更多、对小项目不可取"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1201", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "🌟 Ch2 Test Process 测试流程/🌟 V Model", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 700, "text": "这是瀑布模型的扩展\n\n通过 **标记每一个阶段的生命周期以及测试活动** 来强调 Verification & Validation\n\n一旦编码完成，测试就随之开始了\n\n**从单元测试开始，然后测试层级逐步提高，直到验收测试完成。**\n\n\n\n优势It is simple and easy to manage due to the rigidity of the model. （由于模型的刚性，它简单易管理）It encourages verification and validation at all phases. （它鼓励在所有阶段进行验证和校验）Each phase has specific deliverables and a review process. （每个阶段都有特定的可交付成果和审查流程）It gives equal weight to testing alongside development rather than treating it as an afterthought at the end.（它将测试与开发同等重视，而不是在最后将其视为事后的想法）不足Like the Waterfall model , there is no working software produced until late during the life cycle.（和瀑布模型一样，直到生命周期后期才生产出工作软件）It is unsuitable where"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1202", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "🌟 Ch2 Test Process 测试流程/🌟 V Model", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 296, "text": "software produced until late during the life cycle.（和瀑布模型一样，直到生命周期后期才生产出工作软件）It is unsuitable where the requirements are at a moderate to high risk of changing. （不适合需求处于中度到高度变更风险的情况。）The tight link between test, debug and change tasks during the test phase is not clear.（测试阶段的测试、DEBUG 和变更任务是不清晰的）"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1203", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "🌟 Ch2 Test Process 测试流程/🌟 W Model", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 106, "text": "别名：V 模型拓展 / 双 V 模型\n\n测试并不是在编码完成后进行的，而是和开发过程**平行（PARALLEL）**\n\n强调开发和测试的协作**（CO-OPERATION）**\n\n测试不只是构建，还包括执行和评估"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1204", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "🌟 Ch2 Test Process 测试流程/ Agile Model – XP 敏捷模型：极限编程", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 192, "text": "在去年的 SA 学习中，我们对敏捷模型已经有了一定的理解，详情：\n\n"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1205", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "🌟 Ch2 Test Process 测试流程/ Agile Model – XP 敏捷模型：极限编程/极限编程的理念", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 174, "text": "- 迭代和增量开发\n\n - 将大项目拆分成小的周期，**每个交付一个功能增量以迭代细化特征**\n- 以消费者为中心的价值交付\n\n - 经常交付工作软件以适应不断变化的需求\n- 拥抱变化\n\n - 将需求变更视为改进的机会，通过持续反馈调整优先级，而不是严格遵守最初的计划\n- 自组织的团队和组织\n\n - 赋能跨职能团队自我管理，强调面对面沟通"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1206", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "🌟 Ch2 Test Process 测试流程/ Agile Model – XP 敏捷模型：极限编程/极限编程的价值", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 535, "text": "\n\n**Communication:**\n\n- XP programmers communicate with their customers and fellow programmers\n\n沟通：\n\n极限编程的程序员与他们的客户和其他程序员交流\n\n**Simplicity:**\n\n- they keep their design simple and clean\n\n简单：\n\n他们保持设计简单干净\n\n**Feedback:**\n\n- Get feedback by software testing from the start\n\n反馈：\n\n从一开始就通过软件测试获得反馈\n\n**Courage:**\n\n- Deliver the system to customers as early as possible\n- Implement changes as suggested, responding with courage to changing requirements\n\n勇气：\n\n尽早将系统交付给客户\n\n按照建议实施变更，勇于响应不断变化的需求"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1207", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "🌟 Ch2 Test Process 测试流程/ Agile Model – XP 敏捷模型：极限编程/🌟 极限编程的软件测试/生命周期测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 91, "text": "- 软件生命周期的测试\n\n - **左移测试：**在需求阶段过程中开始测试，和开发相互平行\n - **持续测试：**将测试集成到每一个迭代上，从而保证每一次增量发布的质量稳步提升"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1208", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "🌟 Ch2 Test Process 测试流程/ Agile Model – XP 敏捷模型：极限编程/🌟 极限编程的软件测试/🌟 TDD/定义", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 278, "text": "- **TDD（Test-Driven Development） 测试驱动开发**开始 —— 编写测试 —— 编译 —— 修复编译错误 —— 运行代码观察其失败 —— 编写代码 —— 运行代码观察其通过 —— 根据需求重构代码 —— 重复编写测试\n\n - 先写测试 —— 然后编译 —— 接下来跑测试 —— 写代码 —— 跑测试 —— 测试通过再重构\n - **在编码之前写测试用例：帮助开发者思考接口设计以及边界条件**\n - 先书写单元测试 — 然后开发代码去通过测试 — 最后重构代码\n - 通过测试定义需求去保证代码符合预期并且保持可维护性"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1209", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "🌟 Ch2 Test Process 测试流程/ Agile Model – XP 敏捷模型：极限编程/🌟 极限编程的软件测试/🌟 TDD/实现细节", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 551, "text": "Ø Write code only when an automated test fails\n\nØ If you find a bug through other means, first write a test that fails, then fix the bug\n\n§ Bug won’t resurface later\n\nØ **Run tests as often as possible**, ideally every time the code is changed\n\n§ Having comprehensive unit tests allows you to refactor code with confidence\n\n§ Without unit tests, code is fragile – changes might break clients\n\nØ 仅在自动化测试失败时编写代码\n\nØ 如果你通过其他方式找到bug，先写一个失败的测试，然后修复bug\n\n§ Bug以后不会重新出现\n\nØ **尽可能经常地运行测试**，理想情况下每次更改代码时都要运行测试\n\n§ 拥有全面的单元测试可以让您自信地重构代码\n\n§ 没有单元测试，代码很脆弱 —— 更改可能会破坏客户端"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1210", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "🌟 Ch2 Test Process 测试流程/ Agile Model – XP 敏捷模型：极限编程/🌟 极限编程的软件测试/🌟 TDD/好处", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 154, "text": "\n\n1. **单元测试**实际上被编写了\n2. 程序员的满意能让测试用例编写变得更有持续性\n3. 让**接口和行为**的细节更加清晰\n4. 可证明、可重复、自动化的验证\n5. 为程序员提供重构的自信"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1211", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "🌟 Ch2 Test Process 测试流程/ Agile Model – XP 敏捷模型：极限编程/🌟 极限编程的软件测试/验收测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 185, "text": "- **Acceptance Testing Aligned with User Stories**\n\nDefine acceptance criteria for each user story, with tests designed around these criteria.\n\n- 与用户故事对齐验收测试\n\n为每个用户故事定义验收标准，并围绕这些标准设计测试。"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1212", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "🌟 Ch2 Test Process 测试流程/ Agile Model – XP 敏捷模型：极限编程/🌟 极限编程的软件测试/CI（持续集成）", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 152, "text": "- **Continuous Feedback and Improvement**\n\nUse daily builds and continuous integration (CI 持续集成) to automate tests\n\n- 持续反馈和改进\n\n使用每日构建和持续集成（CI持续集成）来自动化测试"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1213", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "🌟 Ch2 Test Process 测试流程/ Agile Model – XP 敏捷模型：极限编程/🌟 极限编程的软件测试/测试金字塔", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 407, "text": "- Automation as the Backbone\n\n测试金字塔（自顶向下）UI 测试 → 集成测试 → 单元测试\n\n\n\nFidelity Execution time Maintenance Debugging / 准确性、执行时间、维护、调试\n\nHigh: volume of unit tests (fast, low-cost, code-level coverage).\n\nMiddle: Integration/API tests (validate module interactions).\n\nTop: Fewer end-to-end (UI) tests (simulate user workflows, costly but critical for key paths)."}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1214", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "🌟 Ch2 Test Process 测试流程/ DevOps （就业很有用，复习 PPT 没提）", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 69, "text": "感兴趣的同学可看：[zhuanlan.zhihu.com](https://zhuanlan.zhihu.com/p/562036793)"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1215", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "Ch3 Test Principle 测试原理", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 30, "text": "这一章内容比较精简，集中解决一个问题：**怎么进行测试？**"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1216", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "Ch3 Test Principle 测试原理/3.1 静态和动态验证", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 699, "text": "静态验证 （Static Verification）动态验证（Dynamic Verification）是否需要执行代码？✖✅怎么做的？Reading through the code (straightforward)直接通读代码Executing执行代码包含步骤static analysis, code reviews, checks against coding standards and guidelines, and other techniques静态分析、代码审查、根据编码标准和指南进行检查以及其他技术![](\"HvDwbAPPDoYMXPxFfVgcDf0cnud\"/)
\n\n静态验证\n\na formal approach consisting of symbolic verification of the translation between the specification and the source code\n\n一种正式的方法，包括对规范和源代码之间的转换进行符号验证\n\n动态验证\n\n**Test Cases** are created that guide the selection of suitable Test Data (consisting of Input values and Expected Output values ) / 创建测试用例以指导选择合适的测试数据（由输入值和预期输出值组成）"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1217", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "Ch3 Test Principle 测试原理/3.1 静态和动态验证", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 170, "text": "st Data (consisting of Input values and Expected Output values ) / 创建测试用例以指导选择合适的测试数据（由输入值和预期输出值组成）\n\nInput values.\n\nActual Outputs are compared with the Expected Outputs."}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1218", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "Ch3 Test Principle 测试原理/3.2 🌟 对比黑盒测试和白盒测试（部分内容移动到讲义二和三里）", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 527, "text": "\n\n| | 黑盒测试 | 白盒测试 |\n|-|-|-|\n| 依赖内容 | 只依赖需求说明书 | 依赖源代码实现 + 需求说明书 |\n| 代码更改后 测试用例 能否重用 | 可以 | 一般情况下不可以 |\n| 需要什么 | 只需要指定规范 | 需要在测试之前写好代码 |\n| 自动化测试难度 | 较难 | 较易 |\n\nØ White box testing does **not** find faults related to **missing** functionality. These are errors of **omission**.\n\nØ 白盒测试没有发现与**功能缺失**相关的故障。这些是**遗漏错误**。\n\nØ Black box testing does **not** find faults related to **extra** functionality. These are errors of **commission**.\n\nØ 黑盒测试未发现与**额外功能**相关的故障。这些是**委托错误**。"}
{"id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve::1219", "page_id": "docx::ARw3wQyggijXsnk5Z1dc5K3Cnve", "title": "ST 讲义（一）测试介绍", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（一）测试介绍", "section": "Ch3 Test Principle 测试原理/3.3 错误注入与测试制品（仅供了解）", "url": "https://a1npn29y3xu.feishu.cn/wiki/ARw3wQyggijXsnk5Z1dc5K3Cnve", "source_type": "docx", "n_chars": 226, "text": "\n\n\n\n\n\n"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1220", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "ST 讲义（三）🌟 白盒测试 ✅", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 150, "text": "ST 讲义（三）🌟 白盒测试 ✅\n\n白盒测试初稿已经更新完毕，期末的重点是理解白盒测试从简略到详细的思维流程，在期末考试的时候一定要审题，看清楚老师究竟要让我们使用哪种方法。\n\n画程序流程图相信大家能稳稳拿下，但是画 CFG 控制流图还是有很多需要注意事项的，大家复习的时候可以在白纸上多写写多画画。"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1221", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "序、白盒测试概念/什么是白盒测试？", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 670, "text": "**White box testing** uses the **implementation** of the software to derive the tests. The tests are designed to exercise some aspect of the program code.\n\n**白盒测试**使用软件的**实现**来推导测试。这些测试旨在考察程序代码的某些方面。\n\n**White-Box testing** provides for **coverage of the implementation**, but not of the specification. That is there may be behaviour stated in the specification for which there is no code in the implementation.\n\n白盒测试提供了实现的覆盖范围，但没有提供规范的覆盖范围。也就是说，规范中可能规定了实现中没有代码的行为。\n\nref: [白盒测试 百度百科](https://baike.baidu.com/item/%E7%99%BD%E7%9B%92%E6%B5%8B%E8%AF%95/934440)\n\n\n\n"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1222", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "序、白盒测试概念/白盒测试的原则（principle）", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 274, "text": "\n\n1. Test against the implementation 测试执行情况\n2. Use test coverage criteria based on the implementation 根据实现使用测试覆盖率标准\n3. Develop test cases derived from the implementation 开发从实现中得出的测试用例\n4. “Exercise” implementation “演习”执行"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1223", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "序、白盒测试概念/什么是控制流测试？", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 420, "text": "Ø Control-flow testing is a structural testing strategy that uses the program’s control flow as a model.\n\n Ø 控制流测试是一种以程序的控制流为模型的结构测试策略。\n\n Ø Requires the tester to have a clear understanding of the logical structure of the program, and even to be able to master all the **details of the source program**.\n\n Ø 要求测试人员对程序的逻辑结构有清晰的认识，甚至能够掌握源程序的所有细节。\n\n Ø Most applicable to new software for **unit testing**.\n\n Ø 最适用于新软件的单元测试。"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1224", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-1 Logic Coverage（逻辑覆盖）/Source Code（本节课使用的源代码）", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 342, "text": "```Java\npublic static float example(float A, B, X) {\n if (A > 1 && B == 0) {\n X = X / A;\n }\n if (A == 2 || X > 1) {\n X = X + 1;\n }\n return X;\n}\n```\n\n```Python\ndef example(A: float, B: float, X: float) -> float:\n if A > 1 and B == 0:\n X = X // A\n if A == 2 or X > 1:\n X = X + 1\n return X\n```"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1225", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-1 Logic Coverage（逻辑覆盖）/Statement/Point Coverage 语句/点覆盖/定义", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 306, "text": "- Design test cases and work out input values required to ensure that **every source code statement is executed**.（设计测试用例以及需求的输入值确保**源代码的每一行都能被执行到**）\n\n - Also known as **point coverage（点覆盖）**\n- The **weakest logical coverage**, be used interoperatively with other testing methods.（最弱的逻辑覆盖，一般结合其他的测试方法进行使用）"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1226", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-1 Logic Coverage（逻辑覆盖）/Statement/Point Coverage 语句/点覆盖/例题", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 72, "text": "| 用例编号 | 输入（A, B, X） | 路径 | 输出（X） |\n|-|-|-|-|\n| 1 | 2,0,4 | sacbed | 3 |"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1227", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-1 Logic Coverage（逻辑覆盖）/Decision/Branch/Edge Coverage 决策/分支/边覆盖/定义", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 299, "text": "- Design test cases and work out input values required to ensure that **every source code branch is taken**.（设计测试用例并且输入需要的的输入值去确保**每一个源代码的分支都可以被执行到**）\n\n - Each true and false branch of the program is executed at least once（程序中的每一个 true 和 false 分支都可以至少被执行一次）\n- Also known as **edge coverage**.（边覆盖）"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1228", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-1 Logic Coverage（逻辑覆盖）/Decision/Branch/Edge Coverage 决策/分支/边覆盖/例题", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 171, "text": "I 用蓝笔表示：A = 3, B = 0, X = 1, sacbd\n\nII 用红笔表示：A = 2, B = 1, X = 1, sabed\n\n**满足分支覆盖一定满足语句覆盖**\n\n**但是满足语句覆盖不一定满足分支覆盖**\n\n"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1229", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-1 Logic Coverage（逻辑覆盖）/Condition Coverage 条件覆盖/定义", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 188, "text": "- 一个复杂的**决策**是由**许多布尔条件**组合而成的\n- 条件覆盖在分支覆盖的基础上做了拓展：**对于复杂的决策，每一个布尔条件的 True 和 False 都应该被测试**\n- 这存在一个 caveat （警告）：决策本身的 True 和 False 并没有必要被考虑进去\n- 测试数据被选择去确保每一个决策的每一个条件的 True 和 False 都应该被考虑进去"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1230", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-1 Logic Coverage（逻辑覆盖）/Condition Coverage 条件覆盖/例题", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 129, "text": "根据条件覆盖的定义可以得出真值表\n\nA > 1 and B == 0A == 2 or X > 1A > 1B == 0A == 2X > 1TFTFTFTF\n\n**我们只需要保证设计的测试用例能涵盖真值表的所有 T 和 F 即可**"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1231", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-1 Logic Coverage（逻辑覆盖）/Condition Coverage 条件覆盖/例题/情景一：条件覆盖满足语句覆盖和分支覆盖", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1232", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-1 Logic Coverage（逻辑覆盖）/Condition Coverage 条件覆盖/例题/情景二：条件覆盖满足语句覆盖，不满足分支覆盖", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1233", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-1 Logic Coverage（逻辑覆盖）/Condition Coverage 条件覆盖/例题/情景三：条件覆盖不满足语句覆盖，也不满足分支覆盖", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1234", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-1 Logic Coverage（逻辑覆盖）/Condition Coverage 条件覆盖/优势和不足", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1235", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-1 Logic Coverage（逻辑覆盖）/Decision Condition Coverage 决策/条件覆盖/定义", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 687, "text": "Ø Generate test data such that all conditions in a decision take on both outcomes (if possible) at least once and exercise the true and false outcomes of every decision.\n\n§ **Each decision** has True and False test cases\n\n§ In addition, **each condition** in a decision has True and False test cases (if possible)\n\nØ 生成测试数据，使决策中的所有条件至少对两个结果（如果可能）进行一次，并练习每个决策的真假结果。\n\n§ **每个决策**都有True和False测试用例\n\n§ 此外，决策中的**每个条件**都有True和False测试用例（如果可能）\n\nØ It is a **combination of Condition Coverage and Branch Testing**. It uses the same test data as for Condition Coverage but must additionally ensure that each branch or decision takes a true or false outcome.\n\n§ Single condition decision: 2 test cases"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1236", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-1 Logic Coverage（逻辑覆盖）/Decision Condition Coverage 决策/条件覆盖/定义", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 236, "text": "each branch or decision takes a true or false outcome.\n\n§ Single condition decision: 2 test cases\n\n§ 2-condition decisions: 2+ test cases\n\nØ 它是**条件覆盖和分支测试的组合**。它使用与条件覆盖相同的测试数据，但必须额外确保每个分支或决策都得出真或假的结果。\n\n§ 单条件决策：2 个测试用例\n\n§ 2-条件决策：2+ 个测试用例"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1237", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-1 Logic Coverage（逻辑覆盖）/Decision Condition Coverage 决策/条件覆盖/例题/书接上文", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 180, "text": "在上一节的例题中，我们得到了这张表\n\nA > 1 and B == 0A == 2 or X > 1A > 1B == 0A == 2X > 1TFTFTFTF\n\n如何做到**边覆盖**且让**八个布尔值同时被测试**呢？\n\n"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1238", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-1 Logic Coverage（逻辑覆盖）/Decision Condition Coverage 决策/条件覆盖/例题/航空座位预定样例", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 573, "text": "```Java\npublic static Boolean seatsAvailable(int freeSeats, int seatsRequired) {\n boolean rv = false;\n if ((freeSeats >= 0) && (seatsRequired >= 1) && (seatsRequired <= freeSeats)) {\n rv = true;\n }\n return rv; // Java 的自动装箱机制\n}\n```\n\n如何实现分支覆盖？\n\n(freeSeats >= 0) && (seatsRequired >= 1) && (seatsRequired <= freeSeats)T（1）F（2）\n\n如何实现条件覆盖？\n\n(freeSeats >= 0)(seatsRequired >= 1)(seatsRequired <= freeSeats)T（3）F（4）T（5）F（6）T（7）F（8）\n\n如何实现 决策/条件覆盖呢？\n\n测试用例真值表覆盖条件输入预计输出freeSeatsseatsRequired返回值11,3,5,75025true22,4,6,8-50-25false"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1239", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-1 Logic Coverage（逻辑覆盖）/Decision Condition Coverage 决策/条件覆盖/小结", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 178, "text": "决策/条件覆盖的实现步骤\n\n① 确定程序中所有的决策（decisions）\n\n② 将程序中所有的条件（conditions）列出来\n\n③ 生成测试数据去**覆盖以上的所有决策和条件的布尔值**\n\n通过强制执行每个分支来解决条件覆盖率的缺陷之一\n\n"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1240", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-1 Logic Coverage（逻辑覆盖）/Decision Condition Coverage 决策/条件覆盖/优势和不足/优势", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 216, "text": "Ø The true and false outcomes of every decision and every condition are covered\n\nØ This gives **stronger coverage** than just Condition Coverage or Decision Coverage\n\nØ 覆盖每一个决策、每一个条件的真假结果\n\nØ 这提供了比条件覆盖或决策覆盖**更强的覆盖范围**"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1241", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-1 Logic Coverage（逻辑覆盖）/Decision Condition Coverage 决策/条件覆盖/优势和不足/不足", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 179, "text": "Ø Even though every decision is tested, and every condition is tested, **not every possible combination of conditions is tested**.\n\nØ 即使每个决策都经过测试，每个条件都经过测试，但**并不是每个可能的条件组合都经过测试**。"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1242", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-1 Logic Coverage（逻辑覆盖）/Condition Combination Coverage 条件组合覆盖/定义", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 346, "text": "Ø Tests are generated to cause **every possible combination** of conditions for **every decision to be tested**.\n\nØ 生成测试以导致测试**每个决策**的**每个可能条件组合**。\n\nØ The goal is to achieve **100% coverage** of every decision and **100% coverage** of every condition.\n\nØ A **Truth-Table（真值表）** is the best way to identify all the possible combinations of values."}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1243", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-1 Logic Coverage（逻辑覆盖）/Condition Combination Coverage 条件组合覆盖/例题/书接上文", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 220, "text": "\n\n\n\n\n\n**注意到：即使是双重笛卡尔积，程序中也不是所有的路径都可以被执行到的，比如说 `sacbd`**"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1244", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-1 Logic Coverage（逻辑覆盖）/Condition Combination Coverage 条件组合覆盖/例题/`seatsAvailable()`", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 694, "text": "```Java\npublic static Boolean seatsAvailable(int freeSeats, int seatsRequired) {\n boolean rv = false;\n if ((freeSeats >= 0) && (seatsRequired >= 1) && (seatsRequired <= freeSeats)) {\n rv = true;\n }\n return rv; // Java 的自动装箱机制\n}\n```\n\n如何实现分支覆盖？\n\n(freeSeats >= 0) && (seatsRequired >= 1) && (seatsRequired <= freeSeats)T（1）F（2）\n\n如何实现条件覆盖？\n\n(freeSeats >= 0)(seatsRequired >= 1)(seatsRequired <= freeSeats)T（3）F（4）T（5）F（6）T（7）F（8）\n\n如何实现条件组合覆盖呢？（理论上 2^3 = 8，但实际上有些条件根本不可能达成，被删掉）\n\n| **测试用例** | ***(freeSeats >= 0)*** | ***(seatsRequired >= 1)*** | ***(seatsRequired <= freeSeats)*** |\n|-|-|-|-|\n| 1 | T | T | T |\n| 2 | T | T | F |\n| 3 | T | F | T |"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1245", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-1 Logic Coverage（逻辑覆盖）/Condition Combination Coverage 条件组合覆盖/例题/`seatsAvailable()`", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 278, "text": "**(seatsRequired <= freeSeats)*** |\n|-|-|-|-|\n| 1 | T | T | T |\n| 2 | T | T | F |\n| 3 | T | F | T |\n| ~~4~~ | ~~T~~ | ~~F~~ | ~~F~~ |\n| ~~5~~ | ~~F~~ | ~~T~~ | ~~T~~ |\n| 6 | F | T | F |\n| 7 | F | F | T |\n| 8 | F | F | F |\n\n"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1246", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-1 Logic Coverage（逻辑覆盖）/Condition Combination Coverage 条件组合覆盖/优势和不足/优势", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 91, "text": "Ø Tests all possible **combinations of conditions** in every decision.\n\nØ 测试每个决策中所有可能的条件组合。"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1247", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-1 Logic Coverage（逻辑覆盖）/Condition Combination Coverage 条件组合覆盖/优势和不足/不足", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 412, "text": "Ø Can be **expensive**: n conditions in a decision give 2^n test cases.\n\nØ 可能很昂贵：决策中的n个条件给出2^n个测试用例。\n\nØ Can be **difficult** to determine the required input parameter values.\n\nØ 可能难以确定所需的输入参数值。\n\nØ Even though multiple condition testing covers every possible combination of conditions in a decision, it does **not cause every possible execution path** to be taken.\n\nØ 即使多个条件测试涵盖了决策中所有可能的条件组合，**也不会导致采取所有可能的执行路径**。"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1248", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-1 Logic Coverage（逻辑覆盖）/🌟 期末真题：打分系统测试/题干", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 439, "text": "The program Grade combines an exam and coursework mark into a single grade. The values for exam and coursework are integers.\n\nIf the exam or coursework mark is less than 50 then the grade returned is a ‘Fail’.\n\nTo pass the course with a ‘Pass, C’, the student must score between 50 and 60 in the exam, and at least 50 in the coursework.\n\nThey will pass the course with ‘Pass, B’, if they score over 60 in the exam and 50 in the coursework."}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1249", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-1 Logic Coverage（逻辑覆盖）/🌟 期末真题：打分系统测试/题干", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 686, "text": "y will pass the course with ‘Pass, B’, if they score over 60 in the exam and 50 in the coursework.\n\nIn addition to this, if the average of the exam and the coursework is at least 70, then they are awarded a ‘Pass, A’. Input values that are less than 0 or greater than 100 for either the exam or coursework are invalid and the program will return a message to say ‘Marks out of range’.\n\n程序成绩将考试和课程成绩合并为一个成绩。考试和课程成绩的值为整数。\n\n如果考试或课程成绩低于50分，则返回的成绩为“不及格”。\n\n要以“通过，C”的成绩通过课程，学生必须在考试中得分在50到60之间，并且在课程作业中至少得分50分。\n\n如果他们在考试中得分超过60分，在课程作业中得分超过50分，他们将以“通过，B”的成绩通过课程。\n\n此外，如果考试和课程的平均值至少为70，则授予“及格，A”。考试或课程的输入值小于0或大于100无效，程序将返回一条消息，显示“分数超出范围”。\n\n```Java\npublic static String grade(int exam, int course) {"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1250", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-1 Logic Coverage（逻辑覆盖）/🌟 期末真题：打分系统测试/题干", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 657, "text": "课程的输入值小于0或大于100无效，程序将返回一条消息，显示“分数超出范围”。\n\n```Java\npublic static String grade(int exam, int course) {\n String result = \"null\";\n long average;\n average = Math.round((exam + course) / 2);\n if ((exam 100) || (course 100))\n result = \"Marks out of range\";\n else {\n if ((exam < 50) || (course < 50)) {\n result = \"Fail\";\n }\n else if (exam = 70) {\n result = \"Pass, A\";\n }\n else {\n result = \"Pass, B\";\n }\n }\n return result;\n}\n```\n\n1. Please draw the program flow chart of the above code.\n2. Please list all the decisions and their conditions of the above program."}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1251", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-1 Logic Coverage（逻辑覆盖）/🌟 期末真题：打分系统测试/题干", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 207, "text": "hart of the above code.\n2. Please list all the decisions and their conditions of the above program.\n3. Please use the Condition Combination coverage testing method to design the testcases for the above code."}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1252", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-1 Logic Coverage（逻辑覆盖）/🌟 期末真题：打分系统测试/参考答案/根据代码画流程图", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1253", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-1 Logic Coverage（逻辑覆盖）/🌟 期末真题：打分系统测试/参考答案/列举 “决策” 和 “条件”", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 233, "text": "\n\n| decision 多层括号 | condition 每个条件单层括号 |\n|-|-|\n| ((exam 100) \\|\\| (course 100)) | (exam (exam > 100) 2 (course (course > 100) 4 |\n| ((exam (course = 70)) | (average >= 70) 8 |"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1254", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-1 Logic Coverage（逻辑覆盖）/🌟 期末真题：打分系统测试/参考答案/条件组合覆盖测试（以决策为单位，每个决策下面的条件画出 2^N 行的真值表，删掉相互矛盾的行，剩下的写出对应的测试用例进行测试即可）", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 696, "text": "\n\n| 用例编号 | 1 | 2 | 3 | 4 |\n|-|-|-|-|-|\n| ~~1~~ | ~~1~~ | ~~1~~ | ~~1~~ | ~~1~~ |\n| ~~2~~ | ~~1~~ | ~~1~~ | ~~1~~ | |\n| ~~3~~ | 1 | 1 | | 1 |\n| ~~4~~ | 1 | 1 | | |\n| ~~5~~ | 1 | | 1 | 1 |\n| 6 | 1 | | 1 | |\n| 7 | 1 | | | 1 |\n| 8 | 1 | | | |\n| ~~9~~ | | ~~1~~ | ~~1~~ | ~~1~~ |\n| 10 | | 1 | 1 | |\n| 11 | | 1 | | 1 |\n| 12 | | 1 | | |\n| ~~13~~ | | | ~~1~~ | ~~1~~ |\n| 14 | | | 1 | |\n| 15 | | | | 1 |\n| 16 | | | | |\n\n\n\n| 用例编号 | 5 | 6 |\n|-|-|-|\n| 17 | 1 | 1 |\n| 18 | 1 | |\n| 19 | | 1 |\n| 20 | | |\n\n| 用例编号 | 7 |\n|-|-|\n| 21 | 1 |\n| 22 | |\n\n| 用例编号 | 8 |\n|-|-|"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1255", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-1 Logic Coverage（逻辑覆盖）/🌟 期末真题：打分系统测试/参考答案/条件组合覆盖测试（以决策为单位，每个决策下面的条件画出 2^N 行的真值表，删掉相互矛盾的行，剩下的写出对应的测试用例进行测试即可）", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 291, "text": "18 | 1 | |\n| 19 | | 1 |\n| 20 | | |\n\n| 用例编号 | 7 |\n|-|-|\n| 21 | 1 |\n| 22 | |\n\n| 用例编号 | 8 |\n|-|-|\n| 23 | 1 |\n| 24 | |\n\n\n\n\n\n"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1256", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-1 Logic Coverage（逻辑覆盖）/方法论小结/**先画流程图**", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 65, "text": "画了流程图可以解决哪两种覆盖呢？**语句覆盖（点覆盖）**、**条件覆盖（边覆盖）**\n\n条件覆盖一定能保证语句覆盖，反之不成立。"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1257", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-1 Logic Coverage（逻辑覆盖）/方法论小结/**拆解决策和条件**", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 325, "text": "**条件覆盖：**只需要让测试用例覆盖确保**条件表**所有的 True 和 False 至少出现一次\n\n**决策条件覆盖**：让测试用例覆盖确保**决策表和条件表**所有的 True 和 False 至少出现一次\n\n**条件组合覆盖**：以决策为单位，每个决策下面的条件画出 2^N 行的真值表，删掉相互矛盾的行，剩下的写出对应的测试用例进行测试即可\n\n至此，白盒测试中的逻辑覆盖暂时告一段落了。\n\n但是，白盒测试真的只需要做到这样就可以了吗？如果说这段代码量特别长，分支条件特别特别多，而且还有循环嵌套呢？怎么办？~~嗯？look in my eyes...~~\n\n**这个时候，路径覆盖就要派上大用场了，让我们继续白盒测试 —— 路径覆盖。**"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1258", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-2 Path Coverage（路径覆盖）/Control Flow Graphs （控制流图）/什么是控制流图？", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 122, "text": "\n\n每个节点表示一个或者多个语句\n\n每一条边表示一个'jump（跳跃）'或者'branch（分支）'\n\n两个离开表示一个决策（对或错）"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1259", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-2 Path Coverage（路径覆盖）/Control Flow Graphs （控制流图）/控制流图怎么画？（建议在白纸上捋一遍，清晰）/顺序语句", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1260", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-2 Path Coverage（路径覆盖）/Control Flow Graphs （控制流图）/控制流图怎么画？（建议在白纸上捋一遍，清晰）/if 语句", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1261", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-2 Path Coverage（路径覆盖）/Control Flow Graphs （控制流图）/控制流图怎么画？（建议在白纸上捋一遍，清晰）/if-else 语句", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1262", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-2 Path Coverage（路径覆盖）/Control Flow Graphs （控制流图）/控制流图怎么画？（建议在白纸上捋一遍，清晰）/switch-case 语句", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1263", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-2 Path Coverage（路径覆盖）/Control Flow Graphs （控制流图）/控制流图怎么画？（建议在白纸上捋一遍，清晰）/while 语句", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1264", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-2 Path Coverage（路径覆盖）/Control Flow Graphs （控制流图）/控制流图怎么画？（建议在白纸上捋一遍，清晰）/do-while 语句", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1265", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-2 Path Coverage（路径覆盖）/Control Flow Graphs （控制流图）/控制流图怎么画？（建议在白纸上捋一遍，清晰）/for 语句", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 184, "text": "细节一：第几行 for (a; b; c)\n\n细节二：先执行 5，再执行 4c\n\n\n\n```Java\nfor (int i = 0; i < a; i++)\n⬆️ 等价 ⬇️\nint i = 0;\nwhile (i < a) {\n i++;\n}\n```"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1266", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-2 Path Coverage（路径覆盖）/Control Flow Graphs （控制流图）/控制流图怎么画？（建议在白纸上捋一遍，清晰）/批注", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 347, "text": "1. 一定要注意所有导致“跳跃”的条件（决策）：\n\n**if, while, switch/case, for**\n\n1. 以下是控制流图的执行步骤：\n\n- Start at the top of the code （从代码的顶部开始 ）\n- Work your way down to the next jump point （向下工作到下一个跳转点 ）\n- Create a new node （创建新节点 ）\n- For each decision identify the destination node if (a) True and (b) False （对于每个决策，如果（a）True和（b）False，则识别目标节点 ）\n- Connect the nodes （连接节点）"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1267", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-2 Path Coverage（路径覆盖）/Control Flow Graphs （控制流图）/控制流图怎么画？（建议在白纸上捋一遍，清晰）/期末例题 + 解析", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1268", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-2 Path Coverage（路径覆盖）/Control Flow Graphs （控制流图）/程序流图 vs 控制流图", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 160, "text": "一句话总结：控制流图就是简化版本的程序流图，它只描述了程序的控制流\n\n什么是控制流？控制流是计算机执行一个程序中**语句的顺序**\n\n请注意：控制流并没有展示对数据的特定操作以及分支或者循环的特定条件！！！\n\n"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1269", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-2 Path Coverage（路径覆盖）/Path Coverage 路径覆盖/定义", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 692, "text": "Ø Generate test data to exercise all the distinct paths in a program. This is called “**path coverage**”\n\nØ 生成测试数据以练习程序中所有不同的路径。这称为“路径覆盖”\n\nØ Path coverage causes every possible path from entry to exit of the program to be taken during test execution.\n\nØ 路径覆盖导致在测试执行期间采取从程序进入到退出的所有可能路径。\n\nØ The goal is to achieve **100% coverage of every start-to-finish path** in the code.\n\nØ 目标是实现代码中每个从头到尾的路径100%覆盖。\n\nØ A path that makes i iterations through a loop is distinct from a path that makes i+1 iterations through a loop, even if the same nodes are visited in both iterations\n\nØ 通过循环进行i次迭代的路径与通过循环进行i+1次迭代的路径不同，即使在两次迭代中都访问了相同的节点\n\nThus, there can be an **infinite number of paths** in some programs!"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1270", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-2 Path Coverage（路径覆盖）/Path Coverage 路径覆盖/定义", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 120, "text": "+1次迭代的路径不同，即使在两次迭代中都访问了相同的节点\n\nThus, there can be an **infinite number of paths** in some programs!\n\n因此，在某些程序中可能有无限数量的路径！"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1271", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-2 Path Coverage（路径覆盖）/Path Coverage 路径覆盖/路径等价类", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 425, "text": "Ø Need to limit the number of paths: choose equivalence classes of paths（需要限制路径的数量，可以**选择路径的等价类**）\n\nØ Two paths are considered equivalent **if they differ only in the number of loop iterations**, giving two classes of loops:\n\n§ one with 0 iterations\n\n§ one with n iterations (n > 0)\n\nØ Other equivalence paths can also be chosen if required\n\nØ 如果两条路径仅在循环迭代次数上不同，则认为它们是等效的，给出了两类循环：\n\n§ 一个0次迭代\n\n§ 一个有n次迭代（n>0）\n\nØ 如有需要，也可选择其他等价路径"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1272", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-2 Path Coverage（路径覆盖）/Path Coverage 路径覆盖/CFG 与 正则表达式的翻译/翻译规则", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 327, "text": "The CFG of a program can be described by a **regular expression** that uses the following operations:\n\n 程序的CFG可以通过使用以下操作的正则表达式来描述：\n\n**.** is the concatenation of a sequence of nodes （节点的拼接）\n\n**+** is a decision in the graph (i.e. an if statement) （图形的决策）\n\n**\\*** is iteration (0 or more times, e.g. a while statement) （迭代 1+ 次）"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1273", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-2 Path Coverage（路径覆盖）/Path Coverage 路径覆盖/CFG 与 正则表达式的翻译/计算样例", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 185, "text": "```Java\ni = 0;\nwhile (i < list.length) {\n if (list[i] == target)\n match++;\n else\n mismatch++;\n i++;\n}\n```\n\n"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1274", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-2 Path Coverage（路径覆盖）/Path Coverage 路径覆盖/CFG 与 正则表达式的翻译/循环化简", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 182, "text": "(expression)\\* 变成 (expression **+ 0**)\n\n为什么要 +0 呢？\n\n因为 0 可以表示没有循环的情况！\n\n1.2.(3.(4 **+** 5).6.2)\\*.7\n\n1.2.(3.(4 **+** 5).6.2 **+ 0**).7\n\n从而可以得到路径为：\n\n1.2.7\n\n1.2.3.4.6.2.7\n\n1.2.3.5.6.6.7"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1275", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-2 Path Coverage（路径覆盖）/Path Coverage 路径覆盖/CFG 与 正则表达式的翻译/路径数目计算", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 355, "text": "1. 将所有节点的数字（包括 NULL）变成 1\n2. 把 + 变为加法，把 . 变为乘法\n3. 计算路径总数\n\n原来的正则表达式：1.2.(3.(4 **+** 5).6.2 **+ 0**).7\n\n计算路径总数 1·1·(1·(1 + 1)·1·1 + 1)·1 = **3**\n\nNote for “null else” statements where there is an if and no else the expression (node +0) is used where 0 represents the “null else” decision.\n\n注意“null else”语句，其中有 if 和 no else 表达式（node+0），**其中0表示“null else”决定**。"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1276", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-2 Path Coverage（路径覆盖）/Path Coverage 路径覆盖/例题/题目要求", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 29, "text": "① 阅读代码，画出控制流图\n\n② 根据控制流图设计测试用例"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1277", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-2 Path Coverage（路径覆盖）/Path Coverage 路径覆盖/例题/`seatsAvailable()`", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 222, "text": "\n\n将其翻译成正则表达式：1.(2 + 0).3\n\n从正则表达式推导出路径计算：1·（1+1）·1 = 2\n\n\n\n"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1278", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-2 Path Coverage（路径覆盖）/Path Coverage 路径覆盖/例题/成绩统计", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 482, "text": "```Java\npublic static String grade(int exam, int course) {\n String result = \"null\";\n long average;\n average = Math.round((exam + course) / 2);\n if ((exam 100) || (course 100))\n result = \"Marks out of range\";\n else {\n if ((exam < 50) || (course < 50)) {\n result = \"Fail\";\n }\n else if (exam = 70) {\n result = \"Pass, A\";\n }\n else {\n result = \"Pass, B\";\n }\n }\n return result;\n}\n```"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1279", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-2 Path Coverage（路径覆盖）/Path Coverage 路径覆盖/例题/成绩统计/语句（点）覆盖", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1280", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-2 Path Coverage（路径覆盖）/Path Coverage 路径覆盖/例题/成绩统计/决策（分支，边）覆盖", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1281", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-2 Path Coverage（路径覆盖）/Path Coverage 路径覆盖/例题/成绩统计/路径覆盖", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 220, "text": "1.(2+3.(4+5.(6+7.(8+9)))).10\n\n路径总数\n\n1.(1+1.(1+1.(1+1.(1+1)))).1 = 5\n\n具体路径\n\n1-2-10\n\n1-3-4-10\n\n1-3-5-6-10\n\n1-3-5-7-8-10\n\n1-3-5-7-9-10\n\n\n\n路径覆盖可以达到 100% 语句覆盖 和 100% 分支覆盖"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1282", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-2 Path Coverage（路径覆盖）/Path Coverage 路径覆盖/例题/`example`", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 164, "text": "```Python\ndef example(A: float, B: float, X: float) -> float:\n if A > 1 and B == 0:\n X = X // A\n if A == 2 or X > 1:\n X = X + 1\n return X\n```"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1283", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-2 Path Coverage（路径覆盖）/Path Coverage 路径覆盖/例题/`example`/路径覆盖", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1284", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-2 Path Coverage（路径覆盖）/Path Coverage 路径覆盖/例题/`example`/测试用例设计", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1285", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-2 Path Coverage（路径覆盖）/Path Coverage 路径覆盖/优势和不足/优势", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 259, "text": "Ø It does create **combinations of paths** not exercised by other methods\n\n§ Creating and executing tests for all possible paths results in 100% statement coverage and 100% branch coverage.\n\nØ 它确实创建了其他方法未行使的**路径组合**\n\n§ 为所有可能的路径创建和执行测试会导致100%的语句覆盖率和100%的分支覆盖率。"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1286", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-2 Path Coverage（路径覆盖）/Path Coverage 路径覆盖/优势和不足/不足", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 418, "text": "Ø However, it can be **computationally intensive** if the program is complex and many paths are found.\n\nØ 但是，如果程序很复杂并且找到了许多路径，则可能需要**大量计算**。\n\nØ Also, it does **not explicitly evaluate the conditions** in each decision.\n\nØ 此外，它**没有明确评估每个决策中的条件**。\n\nØ If path coverage and condition combination coverage are combined, test cases with stronger fault detection ability can be designed.\n\nØ 如果结合路径覆盖和条件组合覆盖，可以设计故障检测能力更强的测试用例。"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1287", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-2 Path Coverage（路径覆盖）/Basis Path Testing 基础路径测试/定义", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 633, "text": "Ø **Basis Path Testing** is a White Box Testing method in which test cases are defined based on flows or logical paths that can be taken through the program.\n\nØ 基础路径测试是一种白盒测试方法，其中测试用例是根据可以通过程序的流程或逻辑路径定义的。\n\nØ The objective of basis path testing is to **define the number of independent paths**, so the number of test cases needed can be defined explicitly to maximize test coverage.\n\nØ 基础路径测试的目标是定义独立路径的数量，因此可以明确定义所需的测试用例数量，以最大限度地提高测试覆盖率。\n\nØ Basis path testing involves execution of all possible blocks in a program and achieves **maximum path coverage with the least number of test cases**.\n\nØ 基础路径测试涉及执行程序中所有可能的块，并以最少的测试用例实现最大的路径覆盖。"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1288", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-2 Path Coverage（路径覆盖）/Basis Path Testing 基础路径测试/什么是独立路径？", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 258, "text": "**An independent path** is defined as a path from entry to exit that has at least one edge which **has not been traversed before in any other paths**.\n\n独立路径被定义为从入口到出口的路径，该路径至少有一条边缘在任何其他路径中以前**没有被遍历过**。\n\n"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1289", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-2 Path Coverage（路径覆盖）/Basis Path Testing 基础路径测试/独立路径的步骤", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 103, "text": "（1）画**控制流图**（或者决定不同程序路线）\n\n（2）计算**圈复杂度**（确定独立路径数量的指标）\n\n（3）（从简单的路径开始）寻找**基本路径的集合**\n\n（4）根据基本路径路径**生成测试用例**"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1290", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-2 Path Coverage（路径覆盖）/Basis Path Testing 基础路径测试/期末例题", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 312, "text": "\n\n```Java\nvoid function(int x, int y)\n{\n while (x > 0) {\n int s = x + y;\n if (s > 1)\n {\n x--;\n y--;\n }\n else\n {\n if (s < -1) x -= 2;\n else x -= 4;\n }\n }\n}\n```"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1291", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-2 Path Coverage（路径覆盖）/Basis Path Testing 基础路径测试/期末例题/画控制流图", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1292", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-2 Path Coverage（路径覆盖）/Basis Path Testing 基础路径测试/期末例题/计算圈复杂度（MaCabe's Cyclomatic complexity 麦凯布圈复杂度）", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 604, "text": "Ø Question:\n\nHow many paths should be found to cover the basis path set?\n\nØ 问题：\n\n应该找到多少路径来覆盖基本路径集？\n\nØ Cyclomatic Complexity provides a basis for determining the **upper bound of the basis path set**.\n\nØ Cyclomatic Complexity is the maximum number of independent paths\n\n§ Note: The basis path set is not unique.\n\nØ 圈复杂度为确定基路径集的**上界提供了基础**。\n\nØ 圈复杂度是最大独立路径数\n\n§ 注意：基本路径集不是唯一的。\n\nBasis Path Testing checks each linearly independent path through the program, which means **number of test cases, will be equivalent to the cyclomatic complexity of the program.**\n\n基础路径测试检查通过程序的每个线性独立路径，这意味着**测试用例的数量将等同于程序的圈复杂度**。"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1293", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-2 Path Coverage（路径覆盖）/Basis Path Testing 基础路径测试/期末例题/计算圈复杂度（MaCabe's Cyclomatic complexity 麦凯布圈复杂度）/三种方法计算圈复杂度", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 130, "text": "V(G) = E - N + 2 （边数 - 节点数 + 2）\n\nV(G) = P + 1 （决策节点 + 1）\n\nV(G) = R （区域数目）\n\n"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1294", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-2 Path Coverage（路径覆盖）/Basis Path Testing 基础路径测试/期末例题/寻找基本路径集", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1295", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-2 Path Coverage（路径覆盖）/Basis Path Testing 基础路径测试/期末例题/设计测试用例", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1296", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "Ch 5-2 Path Coverage（路径覆盖）/Basis Path Testing 基础路径测试/**Compound condition decomposition 复合条件分解**", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 432, "text": "Ø If the compound condition is included, the compound condition should be decomposed into several simple conditions.\n\nØ 如果包含复合条件，则应将复合条件分解为几个简单条件。\n\nØ Each simple condition corresponds to a node in the flow diagram.\n\nØ 每个简单条件对应流程图中的一个节点。\n\n\n\n**决定覆盖 = 条件覆盖**\n\n路径表达式：a.(b.(c+0)+0).d.(e.(f+0)+f).g\n\n路径数目：9\n\n独立路径的数目：E - V + 2 = 10 - 7 + 2 = 5\n\n独立路径：\n\nadeg\n\nabdeg\n\nabcdeg\n\nadfg\n\nadefg"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1297", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "拓展：实验课 BigInteger 函数测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 664, "text": "1. 语句覆盖/点覆盖（只要做到源代码的每一行都被执行到）\n2. 判定覆盖/边覆盖（做到每一个源代码的分支都被执行到）\n3. 条件覆盖（每一个条件的 True 或 False 都至少被执行一次）\n4. 决策/条件覆盖（条件覆盖 + 判定覆盖）\n5. 条件组合覆盖（最强，开销最大，对于每一个将要被测试的 decision，需要考虑到每一个场景）\n6. 路径覆盖\n\n必修：完成判定覆盖、条件组合覆盖、基本路径覆盖\n\n三选一：语句覆盖、决策/条件覆盖、路径覆盖\n\n待测试的四个方法（BigInteger 类的四种计算）\n\n```java\npublic BigInteger add(BigInteger val) {\n if (val.signum == 0)\n return this;\n if (signum == 0)\n return val;\n if (val.signum == signum)\n return new BigInteger(add(mag, val.mag), signum);\n\n int cmp = compareMagnitude(val);\n if (cmp == 0)\n return ZERO;\n int[] resultMag = (cmp > 0 ? subtract(mag, val.mag)\n : subtract(val.mag, mag));"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1298", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "拓展：实验课 BigInteger 函数测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 676, "text": "t[] resultMag = (cmp > 0 ? subtract(mag, val.mag)\n : subtract(val.mag, mag));\n resultMag = trustedStripLeadingZeroInts(resultMag);\n\n return new BigInteger(resultMag, cmp == signum ? 1 : -1);\n}\n```\n\n```java\nprivate BigInteger multiply(BigInteger val, boolean isRecursion) {\n if (val.signum == 0 || signum == 0)\n return ZERO;\n\n int xlen = mag.length;\n\n if (val == this && xlen > MULTIPLY_SQUARE_THRESHOLD) {\n return square();\n }\n\n int ylen = val.mag.length;\n\n if ((xlen < KARATSUBA_THRESHOLD) || (ylen < KARATSUBA_THRESHOLD)) {\n int resultSign = signum == val.signum ? 1 : -1;\n if (val.mag.length == 1) {"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1299", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "拓展：实验课 BigInteger 函数测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 656, "text": "HOLD)) {\n int resultSign = signum == val.signum ? 1 : -1;\n if (val.mag.length == 1) {\n return multiplyByInt(mag,val.mag[0], resultSign);\n }\n if (mag.length == 1) {\n return multiplyByInt(val.mag,mag[0], resultSign);\n }\n int[] result = multiplyToLen(mag, xlen,\n val.mag, ylen, null);\n result = trustedStripLeadingZeroInts(result);\n return new BigInteger(result, resultSign);\n } else {\n if ((xlen < TOOM_COOK_THRESHOLD) && (ylen < TOOM_COOK_THRESHOLD)) {\n return multiplyKaratsuba(this, val);\n } else {\n //"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1300", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "拓展：实验课 BigInteger 函数测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 694, "text": "COOK_THRESHOLD)) {\n return multiplyKaratsuba(this, val);\n } else {\n //\n // In \"Hacker's Delight\" section 2-13, p.33, it is explained\n // that if x and y are unsigned 32-bit quantities and m and n\n // are their respective numbers of leading zeros within 32 bits,\n // then the number of leading zeros within their product as a\n // 64-bit unsigned quantity is either m + n or m + n + 1. If\n // their product is not to overflow, it cannot exceed 32 bits,\n // and so the number of leading zeros of the product within 64\n // bits must be at least 32, i.e., the leftmost set bit is at"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1301", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "拓展：实验课 BigInteger 函数测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 644, "text": "of the product within 64\n // bits must be at least 32, i.e., the leftmost set bit is at\n // zero-relative position 31 or less.\n //\n // From the above there are three cases:\n //\n // m + n leftmost set bit condition\n // ----- ---------------- ---------\n // >= 32 x = 64 - 32 = 32 possible overflow\n // = 64 - 31 = 33 definite overflow\n //\n // The \"possible overflow\" condition cannot be detected by\n // examning data lengths alone and requires further calculation.\n //"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1302", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "拓展：实验课 BigInteger 函数测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 651, "text": "cted by\n // examning data lengths alone and requires further calculation.\n //\n // By analogy, if 'this' and 'val' have m and n as their\n // respective numbers of leading zeros within 32*MAX_MAG_LENGTH\n // bits, then:\n //\n // m + n >= 32*MAX_MAG_LENGTH no overflow\n // m + n == 32*MAX_MAG_LENGTH - 1 possible overflow\n // m + n <= 32*MAX_MAG_LENGTH - 2 definite overflow\n //\n // Note however that if the number of ints in the result\n // were to be MAX_MAG_LENGTH and mag[0] < 0, then there would"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1303", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "拓展：实验课 BigInteger 函数测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 635, "text": "ber of ints in the result\n // were to be MAX_MAG_LENGTH and mag[0] < 0, then there would\n // be overflow. As a result the leftmost bit (of mag[0]) cannot\n // be used and the constraints must be adjusted by one bit to:\n //\n // m + n > 32*MAX_MAG_LENGTH no overflow\n // m + n == 32*MAX_MAG_LENGTH possible overflow\n // m + n < 32*MAX_MAG_LENGTH definite overflow\n //\n // The foregoing leading zero-based discussion is for clarity\n // only. The actual calculations use the estimated bit length"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1304", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "拓展：实验课 BigInteger 函数测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 651, "text": "discussion is for clarity\n // only. The actual calculations use the estimated bit length\n // of the product as this is more natural to the internal\n // array representation of the magnitude which has no leading\n // zero elements.\n //\n if (!isRecursion) {\n // The bitLength() instance method is not used here as we\n // are only considering the magnitudes as non-negative. The\n // Toom-Cook multiplication algorithm determines the sign\n // at its end from the two signum values.\n if (bitLength(mag, mag.length) +"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1305", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "拓展：实验课 BigInteger 函数测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 658, "text": "// at its end from the two signum values.\n if (bitLength(mag, mag.length) +\n bitLength(val.mag, val.mag.length) >\n 32L*MAX_MAG_LENGTH) {\n reportOverflow();\n }\n }\n\n return multiplyToomCook3(this, val);\n }\n }\n}\n```\n\n```java\npublic BigInteger pow(int exponent) {\n if (exponent < 0) {\n throw new ArithmeticException(\"Negative exponent\");\n }\n if (signum == 0) {\n return (exponent == 0 ? ONE : this);\n }\n\n BigInteger partToSquare = this.abs();\n\n // Factor out powers of two from the base, as the exponentiation of"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1306", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "拓展：实验课 BigInteger 函数测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 688, "text": "partToSquare = this.abs();\n\n // Factor out powers of two from the base, as the exponentiation of\n // these can be done by left shifts only.\n // The remaining part can then be exponentiated faster. The\n // powers of two will be multiplied back at the end.\n int powersOfTwo = partToSquare.getLowestSetBit();\n long bitsToShiftLong = (long)powersOfTwo * exponent;\n if (bitsToShiftLong > Integer.MAX_VALUE) {\n reportOverflow();\n }\n int bitsToShift = (int)bitsToShiftLong;\n\n int remainingBits;\n\n // Factor the powers of two out quickly by shifting right, if needed.\n if (powersOfTwo > 0) {\n partToSquare = partToSquare.shiftRight(powersOfTwo);"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1307", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "拓展：实验课 BigInteger 函数测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 693, "text": "if needed.\n if (powersOfTwo > 0) {\n partToSquare = partToSquare.shiftRight(powersOfTwo);\n remainingBits = partToSquare.bitLength();\n if (remainingBits == 1) { // Nothing left but +/- 1?\n if (signum < 0 && (exponent&1) == 1) {\n return NEGATIVE_ONE.shiftLeft(bitsToShift);\n } else {\n return ONE.shiftLeft(bitsToShift);\n }\n }\n } else {\n remainingBits = partToSquare.bitLength();\n if (remainingBits == 1) { // Nothing left but +/- 1?\n if (signum < 0 && (exponent&1) == 1) {\n return NEGATIVE_ONE;\n } else {\n return ONE;\n }"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1308", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "拓展：实验课 BigInteger 函数测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 630, "text": "return NEGATIVE_ONE;\n } else {\n return ONE;\n }\n }\n }\n\n // This is a quick way to approximate the size of the result,\n // similar to doing log2[n] * exponent. This will give an upper bound\n // of how big the result can be, and which algorithm to use.\n long scaleFactor = (long)remainingBits * exponent;\n\n // Use slightly different algorithms for small and large operands.\n // See if the result will safely fit into a long. (Largest 2^63-1)\n if (partToSquare.mag.length == 1 && scaleFactor <= 62) {\n // Small number algorithm. Everything fits into a long."}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1309", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "拓展：实验课 BigInteger 函数测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 628, "text": "ength == 1 && scaleFactor <= 62) {\n // Small number algorithm. Everything fits into a long.\n int newSign = (signum <0 && (exponent&1) == 1 ? -1 : 1);\n long result = 1;\n long baseToPow2 = partToSquare.mag[0] & LONG_MASK;\n\n int workingExponent = exponent;\n\n // Perform exponentiation using repeated squaring trick\n while (workingExponent != 0) {\n if ((workingExponent & 1) == 1) {\n result = result * baseToPow2;\n }\n\n if ((workingExponent >>>= 1) != 0) {\n baseToPow2 = baseToPow2 * baseToPow2;\n }\n }"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1310", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "拓展：实验课 BigInteger 函数测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 642, "text": "nent >>>= 1) != 0) {\n baseToPow2 = baseToPow2 * baseToPow2;\n }\n }\n\n // Multiply back the powers of two (quickly, by shifting left)\n if (powersOfTwo > 0) {\n if (bitsToShift + scaleFactor <= 62) { // Fits in long?\n return valueOf((result << bitsToShift) * newSign);\n } else {\n return valueOf(result*newSign).shiftLeft(bitsToShift);\n }\n } else {\n return valueOf(result*newSign);\n }\n } else {\n if ((long)bitLength() * exponent / Integer.SIZE > MAX_MAG_LENGTH) {\n reportOverflow();\n }"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1311", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "拓展：实验课 BigInteger 函数测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 699, "text": ")bitLength() * exponent / Integer.SIZE > MAX_MAG_LENGTH) {\n reportOverflow();\n }\n\n // Large number algorithm. This is basically identical to\n // the algorithm above, but calls multiply() and square()\n // which may use more efficient algorithms for large numbers.\n BigInteger answer = ONE;\n\n int workingExponent = exponent;\n // Perform exponentiation using repeated squaring trick\n while (workingExponent != 0) {\n if ((workingExponent & 1) == 1) {\n answer = answer.multiply(partToSquare);\n }\n\n if ((workingExponent >>>= 1) != 0) {\n partToSquare = partToSquare.square();"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1312", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "拓展：实验课 BigInteger 函数测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 681, "text": "if ((workingExponent >>>= 1) != 0) {\n partToSquare = partToSquare.square();\n }\n }\n // Multiply back the (exponentiated) powers of two (quickly,\n // by shifting left)\n if (powersOfTwo > 0) {\n answer = answer.shiftLeft(bitsToShift);\n }\n\n if (signum < 0 && (exponent&1) == 1) {\n return answer.negate();\n } else {\n return answer;\n }\n }\n}\n```\n\n```java\nprivate BigInteger square(boolean isRecursion) {\n if (signum == 0) {\n return ZERO;\n }\n int len = mag.length;\n\n if (len < KARATSUBA_SQUARE_THRESHOLD) {\n int[] z = squareToLen(mag, len, null);"}
{"id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh::1313", "page_id": "docx::Kycdw8RZBiGEJpked0zcqHv7nOh", "title": "ST 讲义（三）🌟 白盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（三）🌟 白盒测试 ✅", "section": "拓展：实验课 BigInteger 函数测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/Kycdw8RZBiGEJpked0zcqHv7nOh", "source_type": "docx", "n_chars": 614, "text": "length;\n\n if (len < KARATSUBA_SQUARE_THRESHOLD) {\n int[] z = squareToLen(mag, len, null);\n return new BigInteger(trustedStripLeadingZeroInts(z), 1);\n } else {\n if (len < TOOM_COOK_SQUARE_THRESHOLD) {\n return squareKaratsuba();\n } else {\n //\n // For a discussion of overflow detection see multiply()\n //\n if (!isRecursion) {\n if (bitLength(mag, mag.length) > 16L*MAX_MAG_LENGTH) {\n reportOverflow();\n }\n }\n\n return squareToomCook3();\n }\n }\n}\n```"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1314", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "ST 讲义（二）🌟 黑盒测试 ✅", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 54, "text": "ST 讲义（二）🌟 黑盒测试 ✅\n\n初稿已完成更新，期末考试黑盒测试必考一题，重点是黑盒测试的分类 + 推导"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1315", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "序、黑盒测试概念/什么是黑盒测试？", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 441, "text": "**Black Box testing** is based entirely on the program specification and aims to verify that the program meets the specified requirements. / **黑盒测试**完全基于程序规范，旨在验证程序是否满足指定要求。\n\nBlack-Box testing provides for **coverage of the specification**, but not full coverage of the implementation. That is, there may be code in the implementation that produces results not stated in the specification.\n\n黑盒测试提供了规范的覆盖，但没有实现的完全覆盖。也就是说，实现中可能存在产生规范中未说明结果的代码。"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1316", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "序、黑盒测试概念/黑盒测试的原则（principle）", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 346, "text": "\n\n1. Test **against** the specification（**对照**规范进行测试）\n2. Use test coverage criteria based on the specification（基于需求使用测试覆盖准则）\n3. Develop test cases derived from the specification （开发根据规范导出的测试用例）\n4. \"Exercise\" the specification （“行使”规范）\n\n"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1317", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Equivalence Partitioning 等价类划分/什么是等价类划分？", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 414, "text": "An Equivalence Partition (EP) is **a range of values** for a parameter for which the specification states equivalent processing.\n\n定义：等价划分 （EP） 是规范中规定的等效处理的**参数的值范围**。\n\n例子：\n\n```Java\n/*\n可以划分为两个等价类，分别是\n[Integer.MIN_VALUE, -1]\n[0, Integer.MAX_VALUE]\n*/\nboolean isNegative(int x) {\n return x < 0;\n}\n```\n\n\n\n"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1318", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Equivalence Partitioning 等价类划分/什么是等价类？", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 106, "text": "\n\n等价类形成集合的分区。\n\nPartition：相互不相交的子集的集合，其 Union 是整个集合。"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1319", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Equivalence Partitioning 等价类划分/什么是等价类？/等价类的分类", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 205, "text": "\n\n**Valid Equivalence Class（有效等价类）**\n\n- 输入域中有意义的一组数据\n- 用于验证系统功能和性能是否能被**准确地实施**\n\n**Invalid Equivalence Class（无效等价类）**\n\n- 输入域中无意义的一组数据\n- 用于测试系统的**容错性**"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1320", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Equivalence Partitioning 等价类划分/什么是等价类？/识别测试用例的步骤", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1321", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Equivalence Partitioning 等价类划分/什么是等价类？/识别测试用例的步骤/根据**被定义的** **输入/输出** 识别等价类", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 263, "text": "- 范围识别\n\n```Java\n/*\n可以划分为三等价类，其中，一个有效等价类，两个无效等价类\n有效等价类\n[0, 100]\n无效等价类\n[Integer.MIN_VALUE, 0)\n(100, Integer.MAX_VALUE]\n*/\nboolean isValidScore(int x) {\n return x >= 0 and x <= 100;\n}\n```\n\n- 集合识别（有效集合、无效集合）\n\n"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1322", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Equivalence Partitioning 等价类划分/什么是等价类？/识别测试用例的步骤/根据**被定义的** **输入/输出** 识别等价类/布尔类型划分等价类", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 29, "text": "一个有效等价类（true）\n\n一个无效等价类（false）"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1323", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Equivalence Partitioning 等价类划分/什么是等价类？/识别测试用例的步骤/根据**被定义的** **输入/输出** 识别等价类/强制输入划分等价类", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 31, "text": "一个有效等价类（valid）\n\n至少一个无效等价类（null）"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1324", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Equivalence Partitioning 等价类划分/什么是等价类？/识别测试用例的步骤/根据**被定义的** **输入/输出** 识别等价类/符合规则划分等价类", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 34, "text": "一个有效等价类（符合所有规则）\n\n多个无效等价类（违背任意一个规则）"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1325", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Equivalence Partitioning 等价类划分/什么是等价类？/识别测试用例的步骤/将每一个输入划分为等价类，并且形成一张**等价类表**，为每一个等价类形成一个**独特的 ID**", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 213, "text": "例 1：百分制评分\n\n参数有效等价类无效等价类Score0 <= X <= 100 (1)X < 0 (2)X > 100 (3)\n\n例 2：考研 408 的四大件是谁？\n\n参数有效等价类无效等价类Course计算机组成原理（1）其他课程（5）数据结构（2）操作系统（3）计算机网络（4）\n\n"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1326", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Equivalence Partitioning 等价类划分/什么是等价类？/识别测试用例的步骤/为有效等价类和无效等价类书写测试用例（备注：有时候会出现 overlap 重叠的现象）", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 136, "text": "- 针对有效等价类设计测试用例\n\n - **每个测试用例**都**涵盖尽可能多的有效类**，然后**重复**，直到测试用例集**覆盖所有有效类**。\n- 针对无效等价类设计测试用例\n\n - **每个测试用例**仅涵盖**一个无效类**（包括一个无效值，其余值都将有效）"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1327", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Equivalence Partitioning 等价类划分/什么是等价类？/等价类测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 392, "text": "等价类测试：从每一个等价类中使用一个元素\n\n\n\n弱等价类：只需要 4 个用例即可全覆盖（毕竟是 or 嘛；A, B, C 选最长的那一个即可咯）\n\n#test cases = #classes in the partition with the largest numbering of subsets\n\n#测试用例 = #classes 个子集编号最大的分区\n\n| Test Case | A | B | C |\n|-|-|-|-|\n| 1 | a1 | b1 | c1 |\n| 2 | a2 | b2 | c2 |\n| 3 | a3 | b3 | c1 |\n| 4 | a1 | b4 | c2 |\n\n强等价类：需要 3 \\* 4 \\* 2 = 24 个用例（笛卡尔积）"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1328", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Equivalence Partitioning 等价类划分/什么是等价类？/例题/External Dial PhoneNumber , “9 - eight digits”", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 321, "text": "参数有效等价类无效等价类Phone Number\"9\"digit string beginning with \"9\"（1）Not beginning with \"9\" （2）Not digits string （3）Not 9 （4）\n\n根据等价类表进一步设计测试用例\n\n| 测试用例 ID | 电话号码 | 期待输出 | 实际输出 | 等价类覆盖 |\n|-|-|-|-|-|\n| 1 | 912345678 | OK | | （1） |\n| 2 | 874563210 | ERROR | | （2） |\n| 3 | 9qwerasdf | ERROR | | （3） |\n| 4 | 98765 | ERROR | | （4） |"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1329", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Equivalence Partitioning 等价类划分/什么是等价类？/例题/WindowsXP 文件名称判定机制：不包含特殊字符且长度在 256 字符以内", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 242, "text": "参数有效等价类无效等价类File Name不包含特殊字符且长度合法（1）包含特殊字符 （2）长度为 0 （3）长度超过 256 字符 （4）\n\n根据等价类表进一步设计测试用例\n\n| 测试用例 ID | 文件名称 | 期待输出 | 实际输出 | 等价类覆盖 |\n|-|-|-|-|-|\n| 1 | | OK | | （1） |\n| 2 | | ERROR | | （2） |\n| 3 | | ERROR | | （3） |\n| 4 | | ERROR | | （4） |"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1330", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Equivalence Partitioning 等价类划分/什么是等价类？/例题/**🌟 经典真题：已知三条边 A B C，判定三角形的类型**", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 288, "text": "| 输入条件 | 有效等价类 | 无效等价类 |\n|-|-|-|\n| 是否为**一般**三角形 | A > 0 B > 0 C > 0 A + B > C A + C > B B + C > A (1) | A B C A + B B + C A + C B == C (9) C == A (10) | A != B && B != C && A != C (11) |\n| 是否为**等边**三角形 | A == B && B == C && C == A (12) | A != B (13) B != C (14) C != A (15) |"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1331", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Equivalence Partitioning 等价类划分/什么是等价类？/例题/NextDate Program（会反复用！）", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 696, "text": "**描述**\n\n给定一系列日期，对于每个日期，你需要计算出下一个有效的日期。如果给定的日期是无效的（例如2008年2月29日不是闰年），则输出\"Invalid\"。\n\n**输入格式**\n\n第一行是一个整数N，表示接下来有N个日期需要处理。\n\n接下来的N行，每行包含三个整数Y M D，分别代表年份、月份和日期。\n\n1 <= N <= 10\n\n1812 <= Y <= 2012\n\n1 <= M <= 12\n\n1 <= D <= 31\n\n**输出格式**\n\n对于每一个输入的日期，输出下一天的有效日期，或者输出\"Invalid\"如果输入的日期无效。\n\n**样例输入**\n\n```Plain Text\n3\n2003 12 31\n1000 01 01\n2008 02 29\n```\n\n**样例输出**\n\n```Plain Text\n2004 01 01\nInvalid\n2008 03 01\n```\n\n**参考代码**\n\n```Python\ndef is_leap_year(year):\n return (year % 4 == 0 and year % 100 != 0) or (year % 400 == 0)\n\ndef days_in_month(month, year):\n days = [-1, 31, 28 + is_leap_year(year), 31, 30, 31, 30, 31, 31, 30, 31, 30, 31]\n return days[month]\n\ndef next_date(year, month, day):\n day += 1"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1332", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Equivalence Partitioning 等价类划分/什么是等价类？/例题/NextDate Program（会反复用！）", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 689, "text": ", 30, 31, 31, 30, 31, 30, 31]\n return days[month]\n\ndef next_date(year, month, day):\n day += 1\n if day > days_in_month(month, year):\n day = 1\n month += 1\n if month > 12:\n month = 1\n year += 1\n return year, month, day\n\ndef main():\n n = int(input())\n for _ in range(n):\n year, month, day = map(int, input().split())\n if not (1812 <= year <= 2012) or not (1 <= month <= 12) or not (1 <= day <= days_in_month(month, year)):\n print(\"Invalid\")\n else:\n year, month, day = next_date(year, month, day)\n print(f\"{year} {month:02d} {day:02d}\")\n\nif __name__ == \"__main__\":\n main()\n```"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1333", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Equivalence Partitioning 等价类划分/什么是等价类？/例题/NextDate Program（会反复用！）", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 225, "text": "day)\n print(f\"{year} {month:02d} {day:02d}\")\n\nif __name__ == \"__main__\":\n main()\n```\n\n**传统等价类划分**\n\n\n\n"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1334", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Equivalence Partitioning 等价类划分/什么是等价类？/例题/课本原题：`seatsAvailable()`", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 573, "text": "\n\n1. 输入分类\n\n| 参数 | 取值范围（打\\*表示无效等价类） |\n|-|-|\n| 空余座位 | Integer.MIN_VALUE...-1 (1\\*) 0...需求座位 - 1 (2) 需求座位...座位总数（3） 座位总数 + 1...Integer.MAX_VALUE (4\\*) |\n| 需求座位 | Integer.MIN_VALUE...0（5\\*） 1...空余座位（6） 空余座位 + 1...座位总数（7） 座位总数 + 1...Integer.MAX_VALUE（8\\*） |\n\n1. 输出分类\n\n| 参数 | 取值范围 |\n|-|-|\n| 返回值 | True False |\n\n1. 书写测试用例\n\n测试用例 ID输入（空余座位）输入（需求座位）预计输出实际输出等价类覆盖有效等价类：使用尽量少的测试用例覆盖尽量多的有效等价类（1 - 1...N）15075False（2）（7）25025True（3）（6）无效等价类：一个测试用例覆盖一个无效等价类（1 - 1）3-10025False（1*）420025False（4*）550-100False（5*）650200False（8*）"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1335", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Equivalence Partitioning 等价类划分/什么是等价类？/总结", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 227, "text": "\n\n1. 等价类划分**是最低限度的黑盒测试**，每一个输入和输出的划分都至少会有一个值会被测试，使用**最小数目的测试用例。**\n2. 这些测试很可能确保代码的基本数据处理方面是正确的，但它们并没有测试代码中做出的各种决策。\n3. 这很重要，因为决策是代码中错误的常见来源。这些决策通常反映了输入分区的边界，或是需要特别处理的输入组合的识别。"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1336", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Equivalence Partitioning 等价类划分/什么是等价类？/优势和不足", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 641, "text": "| 优势 | 不足 |\n|-|-|\n| Ø Provides a good basic level of testing. Ø Well suited to data processing applications where input variables may be easily identified and take on distinct values allowing easy partitioning. Ø Provides a structured means for identifying basic Test Cases. | Ø Correct processing at the edges of partitions is not tested. Ø Combinations of inputs are not tested. Ø The technique does not provide an algorithm for finding the partitions or selecting the test data. |\n| Ø 提供良好的基本测试水平。 Ø 非常适合数据处理应用程序，其中输入变量可以很容易地识别并具有不同的值，从而可以轻松分区。 Ø 提供识别基本测试用例的结构化方法。 | Ø 未测试分区边缘的正确处理。 Ø 不测试输入组合。 Ø 该技术没有提供用于查找分区或选择测试数据的算法。 |"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1337", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Boundary Value Analysis BVA 边界值分析/什么是边界值分析？", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 301, "text": "\n\n- Boundary conditions are situations at the edge of the planned operational limits of the software.\n\n边界条件是软件计划操作**极限边缘的情况**。\n\n- Security flaws such as buffer overflow attacks exploit boundaries of array buffers.\n\n缓冲区溢出攻击等**安全漏洞**利用数组缓冲区的**边界**。"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1338", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Boundary Value Analysis BVA 边界值分析/如何选取边界值？", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 400, "text": "1. Every parameter has a boundary value at the top and bottom of every equivalence partition. （每个参数在每个等价分区的顶部和底部都有一个边界值。 ）\n2. For a contiguous data type, the successor to the value at the top of one partition must be the value at the bottom of the next. （对于连续数据类型，一个分区顶部值的后继值必须是下一个分区底部的值。 ）\n3. The natural range of the parameter provides the ultimate maximum and minimum values.（参数的自然范围提供最终的最大值和最小值。）"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1339", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Boundary Value Analysis BVA 边界值分析/如何选取边界值？/常用的边界值", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 650, "text": "1. **循环**：0，1，len(arr) - 1，len(arr)\n\n经典习题：[704. 二分查找 - 力扣（LeetCode）](https://leetcode.cn/problems/binary-search/description/)\n\n```Python\nclass Solution:\n def search(self, nums: List[int], target: int) -> int:\n left = 0\n right = len(nums) - 1\n while (left <= right):\n mid = (left + right) // 2\n if (nums[mid] == target):\n return mid\n elif (nums[mid] < target):\n left = mid + 1\n elif (target < nums[mid]):\n right = mid - 1\n return -1\n```\n\n1. **数组**：第一个元素 arr[0]，最后一个元素 arr[-1]\n2. **变量**：最小值和最大值\n\n经典 Java 八股文：\n\n1. **链表**：第一个节点和最后一个节点"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1340", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Boundary Value Analysis BVA 边界值分析/如何选取边界值？/常用的边界值", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 692, "text": "```\n\n1. **数组**：第一个元素 arr[0]，最后一个元素 arr[-1]\n2. **变量**：最小值和最大值\n\n经典 Java 八股文：\n\n1. **链表**：第一个节点和最后一个节点\n\n经典习题：[206. 反转链表 - 力扣（LeetCode）](https://leetcode.cn/problems/reverse-linked-list/description/)\n\n```Python\nclass Solution:\n def reverseList(self, head: Optional[ListNode]) -> Optional[ListNode]:\n if not head or not head.next:\n return head\n\n cur = head\n pre = None\n nex = None\n\n while cur:\n nex = cur.next\n cur.next = pre\n pre = cur\n cur = nex\n\n return pre\n\n def reverseList(self, head: Optional[ListNode]) -> Optional[ListNode]:\n if not head or not head.next:\n return head"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1341", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Boundary Value Analysis BVA 边界值分析/如何选取边界值？/常用的边界值", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 696, "text": "al[ListNode]) -> Optional[ListNode]:\n if not head or not head.next:\n return head\n\n new_head = self.reverseList(head.next)\n head.next.next = head\n head.next = None\n return new_head\n```\n\n1. **可接受字符（串）的最大长度和最小长度：**用户名/密码\n2. **表格/报告的：**第一行、第一列、最后一行、最后一列\n\n经典习题：\n\n🌟 [54. 螺旋矩阵 - 力扣（LeetCode）](https://leetcode.cn/problems/spiral-matrix/)\n\n```Java\nclass Solution {\n public List spiralOrder(int[][] matrix) {\n if (matrix == null || matrix.length == 0 || matrix[0].length == 0) {\n return new ArrayList();\n }\n\n List result = new ArrayList<>();\n int top = 0;\n int bottom = matrix.length - 1;\n int left = 0;"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1342", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Boundary Value Analysis BVA 边界值分析/如何选取边界值？/常用的边界值", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 679, "text": "w ArrayList<>();\n int top = 0;\n int bottom = matrix.length - 1;\n int left = 0;\n int right = matrix[0].length - 1;\n\n while (top <= bottom && left <= right) {\n // Traverse from left to right along the top row.\n for (int i = left; i <= right; i++) {\n result.add(matrix[top][i]);\n }\n top++;\n\n // Traverse downwards along the right column.\n for (int i = top; i <= bottom; i++) {\n result.add(matrix[i][right]);\n }\n right--;\n\n // Check if there are still rows and columns left to traverse.\n if (top <= bottom) {"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1343", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Boundary Value Analysis BVA 边界值分析/如何选取边界值？/常用的边界值", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 625, "text": "// Check if there are still rows and columns left to traverse.\n if (top <= bottom) {\n // Traverse from right to left along the bottom row.\n for (int i = right; i >= left; i--) {\n result.add(matrix[bottom][i]);\n }\n bottom--;\n }\n\n if (left <= right) {\n // Traverse upwards along the left column.\n for (int i = bottom; i >= top; i--) {\n result.add(matrix[i][left]);\n }\n left++;\n }\n }\n\n return result;\n }\n}\n```"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1344", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Boundary Value Analysis BVA 边界值分析/如何选取边界值？/常用的边界值", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 656, "text": "}\n left++;\n }\n }\n\n return result;\n }\n}\n```\n\n[200. 岛屿数量 - 力扣（LeetCode）](https://leetcode.cn/problems/number-of-islands/description/)\n\n```Python\nclass Solution:\n def numIslands(self, grid: List[List[str]]) -> int:\n def dfs(i, j):\n if i = len(grid) or j = len(grid[0]) or grid[i][j] == '0':\n return\n grid[i][j] = '0'\n for d in [(0, 1), (0, -1), (1, 0), (-1, 0)]:\n nx = i + d[0]\n ny = j + d[1]\n dfs(nx, ny)\n if not grid or not grid[0]:\n return 0\n cnt = 0\n for i in range(len(grid)):"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1345", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Boundary Value Analysis BVA 边界值分析/如何选取边界值？/常用的边界值", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 695, "text": "if not grid or not grid[0]:\n return 0\n cnt = 0\n for i in range(len(grid)):\n for j in range(len(grid[0])):\n if grid[i][j] == '1':\n cnt += 1\n dfs(i, j)\n return cnt\n```\n\n```Python\nfrom collections import deque\nfrom typing import List\n\nclass Solution:\n directions = [[0, 1], [0, -1], [-1, 0], [1, 0]]\n\n def numIslands(self, grid: List[List[str]]) -> int:\n if not grid or not grid[0]:\n return 0\n\n def bfs(grid: List[List[str]], startX: int, startY: int) -> None:\n q = deque([[startX, startY]]) # 修改这里\n grid[startX][startY] = \"0\"\n\n while q:"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1346", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Boundary Value Analysis BVA 边界值分析/如何选取边界值？/常用的边界值", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 672, "text": "q = deque([[startX, startY]]) # 修改这里\n grid[startX][startY] = \"0\"\n\n while q:\n node = q.popleft()\n\n curX = node[0]\n curY = node[1]\n\n for dire in self.directions: # 使用 self 来引用类变量\n nX = curX + dire[0]\n nY = curY + dire[1]\n\n if 0 <= nX < len(grid) and 0 <= nY < len(grid[0]) and grid[nX][nY] == \"1\": # 修改这里，确保 nY 的比较是小于 len(grid[0])\n q.append([nX, nY]) # 修改这里，确保添加到队列的是列表\n grid[nX][nY] = \"0\"\n\n count = 0\n for i in range(len(grid)):\n for j in range(len(grid[0])):"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1347", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Boundary Value Analysis BVA 边界值分析/如何选取边界值？/常用的边界值", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 653, "text": "\"0\"\n\n count = 0\n for i in range(len(grid)):\n for j in range(len(grid[0])):\n if grid[i][j] == \"1\":\n # dfs(grid, i, j)\n bfs(grid, i, j)\n count += 1\n return count\n```\n\nØ Typically, software testing involves several types of boundary checks: numbers, characters, position, weight, size, speed, orientation, dimension, space, and so on.\n\nØ 通常，软件测试涉及几种类型的边界检查：数字、字符、位置、重量、大小、速度、方向、尺寸、空间等。\n\nØ Accordingly, the boundary values of the above types should be in: max/min, first/last, up/down, fastest/slowest, highest/lowest, shortest/longest, empty/full, etc."}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1348", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Boundary Value Analysis BVA 边界值分析/如何选取边界值？/常用的边界值", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 153, "text": "max/min, first/last, up/down, fastest/slowest, highest/lowest, shortest/longest, empty/full, etc.\n\nØ 相应地，上述类型的边界值应为：最大/最小、前/后、上/下、最快/最慢、最高/最低、最短/最长、空/满等。"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1349", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Boundary Value Analysis BVA 边界值分析/如何选取边界值？/例题/判定是否为负", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 186, "text": "```Java\n/*\n可以划分为两个等价类，分别是\n[Integer.MIN_VALUE, -1]\n[0, Integer.MAX_VALUE]\nBVA 边界值分析的四个取值\nInteger.MIN_VALUE, -1, 0, Integer.MAX_VALUE\n*/\nboolean isNegative(int x) {\n return x < 0;\n}\n```"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1350", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Boundary Value Analysis BVA 边界值分析/如何选取边界值？/例题/`seatsAvailable()`", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1351", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Boundary Value Analysis BVA 边界值分析/如何选取边界值？/优势和不足", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 291, "text": "\n\n| 优势 | 不足 |\n|-|-|\n| Ø Test Data values are provided by the technique. Ø Tests focus on areas where faults are more likely to be found. | Ø Combinations of inputs are not tested. |\n| Ø 测试数据值由技术提供。 Ø 测试重点放在更容易发现故障的区域。 | Ø 不测试输入组合。 |"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1352", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Combinational Testing 组合测试/什么是组合测试？", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 674, "text": "Ø There are a number of different techniques for identifying relevant combinations, such as ***Cause-Effect Graphs*, *Decision Tables* and *Truth Tables***.\n\nØ 有许多不同的技术可以识别相关组合，例如因果图、决策表和真值表。\n\nØ The analysis of combinations involves identifying all the different combinations of input **causes** to the software and their associated output **effects**.\n\nØ 组合分析涉及识别软件输入原因的所有不同组合及其相关的输出效果。\n\nØ The causes and effects are described as **logical statements (or predicates)**, based on the specification of the software. These expressions specify the conditions required for a particular variable to cause a particular effect.\n\nØ 因果关系被描述为逻辑语句（或谓词），基于软件的规范。这些表达式指定了特定变量引起特定影响所需的条件。"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1353", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Combinational Testing 组合测试/真值表", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 691, "text": "Ø To test all the **different behaviors of the program**, a Truth Table is created. The inputs (“Causes”) and outputs (“Effects”) are specified as Boolean expressions (using predicate logic).\n\nØ 为了测试程序的所有不同行为，创建了一个真值表。输入（“原因”）和输出（“影响”）被指定为布尔表达式（使用谓词逻辑）。\n\nØ **Combinations of the causes** are the inputs that will generate a particular response from the program.\n\nØ **Test Cases** are then constructed that will **cover all possible combinations of Cause and Effect**. For N independent causes, there will therefore be a total of **2^N** different combinations. The Truth Table specifies how the software should behave for each combination.\n\nØ **原因的组合**是将从程序中产生特定响应的输入。然后构建测试用例，涵盖因果关系的所有可能组合。"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1354", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Combinational Testing 组合测试/真值表", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 145, "text": "the software should behave for each combination.\n\nØ **原因的组合**是将从程序中产生特定响应的输入。然后构建测试用例，涵盖因果关系的所有可能组合。对于N个独立的原因，因此总共会有2^N个不同的组合。真值表指定了软件对每个组合的行为方式。"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1355", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Combinational Testing 组合测试/真值表/例 1：`isNegative(int x)`", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 121, "text": "\n\n| | if x < 0 then return true | if not x return value | T | F |"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1356", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Combinational Testing 组合测试/真值表/例 2：`largest(int x, int y)`", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 160, "text": "```Java\npublic int largest(int x, int y) {\n return x >= y ? x : y;\n}\n```\n\nRulesCauses123x > yTFFx < yFTFEffectsreturn value == xTFTreturn value == yFTT"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1357", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Combinational Testing 组合测试/真值表/Don't Care Conditions", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 586, "text": "Ø “Don’t care” conditions exist where the value of ***a cause has no impact on the effect***.\n\nØ “不在乎”条件存在，其中原因的价值对结果没有影响。\n\nØ These “Don’t care” conditions are used to reduce the number of rules ***where the same output will be generated*** irrespective of whether the **Cause is true or false**.\n\nØ 这些“不关心”条件用于减少无论原因是真还是假都会生成相同输出的规则数量。\n\nØ In the worst case, if there are no “Don’t care” conditions, N Causes will create 2^N Rules.\n\nØ 在最坏的情况下，如果没有“不关心”的条件，N个原因将创建2^N个规则。\n\nØ “Don’t care” conditions are represented by a **“\\*”** for the causes in a Truth Table.\n\nØ “不关心”条件在真值表中用“\\*”表示原因。"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1358", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Combinational Testing 组合测试/真值表/例 3：`condIsNegt(int x, boolean flag)`", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 121, "text": "```Java\npublic boolean largest(int x, boolean flag) {\n return x RulesCauses123x < 0TF*falgTTFEffectsreturn valueTFF"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1359", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Combinational Testing 组合测试/真值表/优势和不足", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 443, "text": "Ø The truth tables can sometime **be very large**. The solution is to identify subproblems and develop **separate tables** for each.\n\n真值表有时可能**非常大**。解决方案是识别子问题并为每个子问题开发**单独的表**。\n\nØ **Very dependent on the quality of the specification** - more detail means more causes and effects, which takes more time to test; less detail means less causes and effects, but less effective testing\n\n**非常依赖规范的质量**——细节越多意味着前因后果越多，需要花更多时间测试；细节越少意味着前因后果越少，但测试效果越差"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1360", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Combinational Testing 组合测试/决定表 Decision Tables", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 360, "text": "Ø precise yet compact way to model complicated logic\n\nØ 精确而紧凑的方式来建模复杂的逻辑\n\nØ Associate conditions with actions to perform\n\nØ 将条件与要执行的操作相关联\n\nØ Can associate many independent conditions with several actions in an elegant way\n\nØ 可以优雅地将多个独立条件与多个动作关联起来\n\n\n\n"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1361", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Combinational Testing 组合测试/决定表 Decision Tables/例 1：NextDate Program", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 692, "text": "回顾一下我们之前的等价类划分设计\n\nM1 = { 30 天 的月份 }\n\nM2 = { 31 天 的月份 }\n\nM3 = { 2 月 }\n\nD1 = { 1..28 天 }\n\nD2 = { 29 天 }\n\nD3 = { 30 天 }\n\nD4 = { 31 天 }\n\nY1 = { 1812 \\~ 2012 年之间的闰年 }\n\nY2 = { 1812 \\~ 2012 年之间的平年 }\n\n如果按照真值表对不同的条件进行设计，难道要设计 2^9 = 512 种不同的组合吗？\n\n可以观察到，月份的设计是 “互斥” 的，三种月份我们只能抽取其中一种\n\n| C1：M1 月 | T | —— | —— |\n|-|-|-|-|\n| C2：M2 月 | —— | T | —— |\n| C3：M3 月 | —— | —— | T |\n| A1：不可能 | | | |\n| A2：下一天 | | | |\n\n\n\n\n\n**我们又可以发现：如果我们对 nextDay 这个函数进行细化，又可以有很多种不同的情况，原本的分类无法妥善处理，这就提示我们进行再次拆分，如下所示：**\n\nM1 = { 30 天 的月份 }\n\nM2 = { 31 天 的月份（排除 12 月） }\n\n**M3 = { 12 月 }**\n\nM4 = { 2 月 }\n\nD1 = { 1..27 天 }"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1362", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Combinational Testing 组合测试/决定表 Decision Tables/例 1：NextDate Program", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 689, "text": "M1 = { 30 天 的月份 }\n\nM2 = { 31 天 的月份（排除 12 月） }\n\n**M3 = { 12 月 }**\n\nM4 = { 2 月 }\n\nD1 = { 1..27 天 }\n\n**D2 = { 28 天 }**\n\nD3 = { 29 天 }\n\nD4 = { 30 天 }\n\nD5 = { 31 天 }\n\nY1 = { 1812 \\~ 2012 年之间的闰年 }\n\nY2 = { 1812 \\~ 2012 年之间的平年 }\n\n注意到：除了 2 月份要考虑闰年和平年，其他的月份都没有必要进行额外的考虑，排列组合精简为 22 列\n\n**为什么是 22 列呢？**\n\nM 有 4 列，D 有 5 列，笛卡尔积 20 列\n\n**涉及到二月份的 D2 和 D3，需要考虑平年和闰年，多加 2 列**\n\n所以一共是 22 列\n\n\n\n请观察荧光笔的条件合并，总结设计用例的设计规律\n\n为什么 M4 涉及不同 Y 的类型无法合并，但是 M1 和 M2 涉及不同的 D 可以合并呢？\n\n\n\n| Case ID | Year | Month | Day | Expected Output |\n|-|-|-|-|-|\n| 1 - 3 | 2001 | 4 | 15 | 2001 4 16 |\n| 4 | 2001 | 4 | 30 | 2001 5 1 |"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1363", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Combinational Testing 组合测试/决定表 Decision Tables/例 1：NextDate Program", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 486, "text": "xpected Output |\n|-|-|-|-|-|\n| 1 - 3 | 2001 | 4 | 15 | 2001 4 16 |\n| 4 | 2001 | 4 | 30 | 2001 5 1 |\n| 5 | 2001 | 4 | 31 | Invalid |\n| 6 - 9 | 2001 | 1 | 15 | 2001 1 16 |\n| 10 | 2001 | 1 | 31 | 2001 2 1 |\n| 11 - 14 | 2001 | 2 | 15 | 2001 2 16 |\n| 15 | 2001 | 12 | 31 | 2002 1 1 |\n| 16 | 2001 | 2 | 15 | 2001 2 16 |\n| 17 | 2004 | 2 | 28 | 2004 2 29 |\n| 18 | 2001 | 2 | 28 | Invalid |\n| 19 | 2004 | 2 | 29 | 2004 3 1 |\n| 20 | 2001 | 2 | 29 | Invalid |\n| 21 - 22 | 2001 | 2 | 30 | Invalid |"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1364", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Combinational Testing 组合测试/决定表 Decision Tables/例 2：超市会员例题", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 404, "text": "\n\n| 会员 | T | T | F | F | F | T |\n|-|-|-|-|-|-|-|\n| 购买金额 >= 1000 | F | T | F | F | T | T |\n| 现场办理会员卡 | - | - | F | - | F | T |\n| 九折 | ✖ | | | | ✖ | |\n| 七折 | | ✖ | | | | ✖ |\n| 原价 | | | ✖ | ✖ | | |\n\n\n\n等价类和决策表是紧密关联的\n\n决策表与程序是最接近的\n\n- 有许多决策制定\n- 有输入变量的重要逻辑关系\n- 有输入变量的子集的计算\n- 有复杂的计算逻辑（高圈复杂度）"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1365", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Random Testing and Error Guessing/随机测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 572, "text": "\n\n- Each Test Case is represented by **a set of (random) input values**, one for each parameter.每个测试用例由一组（随机）输入值表示，每个参数一个。\n- If the test is fully **automated**, then each Test Case is represented by a distribution of values for a particular parameter.\n\n如果测试是完全自动化的，那么每个测试用例都由特定参数的值分布表示。\n\n- This will normally include **the upper and lower limits, and the distribution** to be used between these limits to select a random value.\n\n这通常包括上限和下限，以及在这些限制之间用于选择随机值的分布。\n\n"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1366", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Random Testing and Error Guessing/错误推测", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 677, "text": "\n\n- 空值、空字符串、空数组、空列表、空的类引用\n- 0 值\n- 字符串的空格或者空字符串\n- 负值\n\n例：[912. 排序数组 - 力扣（LeetCode）](https://leetcode.cn/problems/sort-an-array/description/)\n\n```Python\nclass Solution:\n def sortArray(self, nums: List[int]) -> List[int]:\n return self.merge_sort(nums)\n\n def merge_sort(self, nums):\n if len(nums) == 1:\n return nums\n mid = len(nums) // 2\n left = self.merge_sort(nums[:mid])\n right = self.merge_sort(nums[mid:])\n return self.merge(left, right)\n\n def merge(self, left, right):\n sorted_arr = []\n i = j = 0\n\n while i < len(left) and j < len(right):"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1367", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Random Testing and Error Guessing/错误推测", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 681, "text": "right):\n sorted_arr = []\n i = j = 0\n\n while i < len(left) and j < len(right):\n if left[i] < right[j]:\n sorted_arr.append(left[i])\n i += 1\n else:\n sorted_arr.append(right[j])\n j += 1\n\n sorted_arr.extend(left[i:])\n sorted_arr.extend(right[j:])\n\n return sorted_arr\n```\n\n在 Debug 这一道题的时候，测试人员会考虑 5 中特殊情况\n\n1. 数组为空 []\n2. 数组只有一个元素 [1]\n3. 所有的元素在数组已经被排序了 [1, 2, 3, 4, 5]\n4. 所有的元素在数组已经是逆序了 [9, 7, 5, 4, 3]\n5. 部分/所有 元素在数组中是相同的 [3, 4, 4, 3, 9]\n\nØ The tester selects values which are **likely to produce errors**. Each value is a Test Case.\n\nØ 测试人员选择可能产生错误的值。每个值都是一个测试用例。"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1368", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Random Testing and Error Guessing/错误推测", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 680, "text": "which are **likely to produce errors**. Each value is a Test Case.\n\nØ 测试人员选择可能产生错误的值。每个值都是一个测试用例。\n\nØ This technique can produce **both normal and error Test Cases**. The values selected are those that are likely to expose faults in the code, they are not necessarily illegal values.\n\nØ 这种技术可以产生正常和错误的测试用例。选择的值是那些可能暴露代码中故障的值，它们不一定是非法值。\n\nØ Input Test Data is selected, based on Test Cases which are **not yet covered**. As with the other test techniques, error cases should be executed **individually**.\n\nØ 根据尚未涵盖的测试用例选择输入测试数据。与其他测试技术一样，错误用例应单独执行。\n\nØ With experienced testers, this can be a very **effective complement** to other testing techniques.\n\nØ 有经验的测试人员，这可以成为其他测试技术的非常有效的补充。"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1369", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Random Testing and Error Guessing/错误推测", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 309, "text": "n be a very **effective complement** to other testing techniques.\n\nØ 有经验的测试人员，这可以成为其他测试技术的非常有效的补充。\n\nØ It depends on **how well the testers know the types of mistakes** that the developers are likely to make, or mistakes that have a high impact on the final product.\n\nØ 这取决于测试人员对开发人员可能犯的错误类型或对最终产品影响大的错误的了解程度。"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1370", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Scenario Testing 场景测试/定义", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1371", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Scenario Testing 场景测试/用例场景解析", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 312, "text": "\n\n\n\n在上面的题目中，我们可以设计 8 个场景\n\n| 1 | B |\n|-|-|\n| 2 | B - A1 |\n| 3 | B - A1 - A2 |\n| 4 | B - A3 |\n| 5 | B - A3 - A1 |\n| 6 | B - A3 - A1 - A2 |\n| 7 | B - A4 |\n| 8 | B - A3 - A4 |\n\n为了简化问题分析，只有一个循环执行的可选流 3 被考虑进去"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1372", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Scenario Testing 场景测试/执行步骤", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 634, "text": "**Scenario Testing Goal**\n\n- Simulate the user to complete the operation of normal functions and core business logic to **verify the correctness of software functions**;\n- Simulate the main errors in user operation to **verify the abnormal error handling ability of software**.\n\n场景测试目标\n\n- 模拟用户完成正常功能和核心业务逻辑的操作，验证软件功能的正确性；\n- 模拟用户运营中的主要错误，验证软件的异常错误处理能力。\n\nAlternative flows, like the program execution paths, will cause the scenario explosion.\n\nTypical scenarios need to be selected for testing.\n\n(1) One and only one scenario contains the basic flow;\n\n(2) The minimum number of scenarios: the total of basic flows and alternative flows;"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1373", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Scenario Testing 场景测试/执行步骤", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 665, "text": "basic flow;\n\n(2) The minimum number of scenarios: the total of basic flows and alternative flows;\n\n(3) For an alternative flow: at least one scenario covering it, which try to avoid covering other alternative flows\n\n替代流程，如程序执行路径，将导致场景爆炸。\n\n需要选择典型场景进行测试。\n\n（1）有且仅有一个场景包含基本流程；\n\n（2）最小场景数：基础流、备选流合计；\n\n（3）对于备选流：至少覆盖一个场景，尽量避免覆盖其他备选流\n\n1. According to the specification, **describe the basic flow and alternative flow** of the software under test. 根据规范，描述被测软件的基本流程和备选流程。\n2. **Construct different scenarios** to meet the requirements of test completeness and no redundancy.\n\n构造不同的场景，满足测试完备性和无冗余的要求。\n\n1. **Design corresponding test cases** for each scenario.\n\n为每个场景设计相应的测试用例。"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1374", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Scenario Testing 场景测试/执行步骤", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 318, "text": "造不同的场景，满足测试完备性和无冗余的要求。\n\n1. **Design corresponding test cases** for each scenario.\n\n为每个场景设计相应的测试用例。\n\n1. Re-examine all generated test cases and remove redundant test cases. After the test cases are determined, **the test data values are determined** for each test case.\n\n重新检查所有生成的测试用例，去除冗余的测试用例。测试用例确定后，为每个测试用例确定测试数据值。"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1375", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Scenario Testing 场景测试/例题：酒店订购", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 679, "text": "A hotel system supports online reservations.\n\nCustomers visit the website for room reservation operation, select a reservation date, suitable room, online reservation.\n\nIn this case, you need to login to the system using your personal account.\n\nAfter the login succeeds, you can make the deposit payment.\n\nAfter the deposit is paid successfully, the room reservation form will be generated to complete the whole room reservation process.\n\nThe system allows a reservation period of 30 days and a deposit of 400 dollars.\n\n酒店系统支持在线预订。\n\n客户访问网站进行房间预订操作，选择预订日期、合适的房间、在线预订。\n\n在这种情况下，您需要使用您的个人帐户登录系统。\n\n登录成功后，您可以支付押金。\n\n支付押金成功后会生成房间预订表单，完成整个房间预订流程。\n\n该系统允许30天的预订期和400美元的押金。\n\n如何根据场景流动设计测试用例呢？"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1376", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Scenario Testing 场景测试/例题：酒店订购", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 682, "text": "的个人帐户登录系统。\n\n登录成功后，您可以支付押金。\n\n支付押金成功后会生成房间预订表单，完成整个房间预订流程。\n\n该系统允许30天的预订期和400美元的押金。\n\n如何根据场景流动设计测试用例呢？\n\nV：为了让基本流被执行，条件必须为有效的\n\nI：如果条件无效，那么就会激活可选流\n\nNA：Not Applicable 条件无法被应用到测试用例中\n\n| 测试用例 | 场景 | 日期 | 房间 | 账户 | 密码 | 账户 | 预计输出 |\n|-|-|-|-|-|-|-|-|\n| 1 | 1 | V | V | V | V | V | 成功订购 账户余额扣减相应的值 |\n| 2 | 2 | I | NA | NA | NA | NA | 预定时间失效 请重新选择日期 |\n| 3 | 3 | V | I | NA | NA | NA | 客房已满 请重新选择日期 |\n| 4 | 4 | V | V | I | NA | NA | 账户不存在 请重新选择账户 |\n| 5 | 5 | V | V | V | I | NA | 密码错误 请重新输入密码 |\n| 6 | 6 | V | V | V | V | I | 账户余额不足，请重新提取 |\n\n**根据可选流，结合题目的具体数据设计测试用例即可**\n\n| 测试用例 | 场景 | 日期 | 房间 | 账户 | 密码 | 账户 | 预计输出 |\n|-|-|-|-|-|-|-|-|\n| 1 | 1 | V | 未满 | USER | 1234 | 1000 | 成功订购 账户余额扣减相应的值 |"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1377", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "Scenario Testing 场景测试/例题：酒店订购", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 355, "text": "账户 | 密码 | 账户 | 预计输出 |\n|-|-|-|-|-|-|-|-|\n| 1 | 1 | V | 未满 | USER | 1234 | 1000 | 成功订购 账户余额扣减相应的值 |\n| 2 | 2 | I | NA | NA | NA | NA | 预定时间失效 请重新选择日期 |\n| 3 | 3 | V | 已满 | NA | NA | NA | 客房已满 请重新选择日期 |\n| 4 | 4 | V | 未满 | ??? | NA | NA | 账户不存在 请重新选择账户 |\n| 5 | 5 | V | 未满 | USER | 空 | NA | 密码错误 请重新输入密码 |\n| 6 | 6 | V | 未满 | USER | 1234 | 0 | 账户余额不足，请重新提取 |"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1378", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "黑盒测试总结", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 664, "text": "**业务功能点 —— 哪些是比较合适的业务功能点 —— 完成完整的业务功能**\n\n1. For the specific input field in the specific function page, the refined test is carried out, using **equivalence class and boundary value**; Use static testing to check buttons, links, content, images, etc;\n\n针对具体功能页面中的具体输入字段，进行精细化测试，使用等价类和边界值;使用静态测试来检查按钮、链接、内容、图像等;\n\n1. If the function description contains a combination of input conditions, and the business logic is complex, **decision table** can be used.\n\n如果函数描述中包含多个输入条件的组合，且业务逻辑复杂，可以使用决策表。\n\n1. **Boundary value analysis** should be considered in any case, as it is one of the most effective methods to find software defects. 无论如何都应该考虑边界值分析，因为它是发现软件缺陷的最有效方法之一。"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1379", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "黑盒测试总结", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 404, "text": "is one of the most effective methods to find software defects. 无论如何都应该考虑边界值分析，因为它是发现软件缺陷的最有效方法之一。\n2. Test cases can be expanded by **error guessing** method, and the valuable experience of test engineers is emphasized.\n\n可以通过错误猜测方法扩展测试用例，强调测试工程师的宝贵经验。\n\n1. For the system with **clear business process, the scenario testing** can be used throughout the whole testing process\n\n对于业务流程清晰的系统，场景测试可以贯穿整个测试过程"}
{"id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc::1380", "page_id": "docx::U3FDw3t5nigGE8kHzFacpxxonOc", "title": "ST 讲义（二）🌟 黑盒测试 ✅", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（二）🌟 黑盒测试 ✅", "section": "笔记补充", "url": "https://a1npn29y3xu.feishu.cn/wiki/U3FDw3t5nigGE8kHzFacpxxonOc", "source_type": "docx", "n_chars": 158, "text": "\n\n用户与界面的交互事实上也是输入\n\n例：选课系统怎么进行黑盒测试呢？\n\n注册登录\n\n选课逻辑（业务规则）\n\n课程状态（跟踪课程变化的情况）\n\n边界条件（选课成功的业务流程怎么走，选课失败的业务流程怎么走）"}
{"id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd::1381", "page_id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd", "title": "ST 讲义（五）测试文档、静态测试与软件维护", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（五）测试文档、静态测试与软件维护", "section": "Ch6 测试文档/Test Plan 测试计划/什么是测试计划？", "url": "https://a1npn29y3xu.feishu.cn/wiki/XLhZwD9V7ibz7KkZWaycRUyXnLd", "source_type": "docx", "n_chars": 312, "text": "- **测试计划**是一个描述软件测试**范围以及行为**的**文档。**这是在项目中**正式地测试**任意的软件/产品的**基础**\n\n - 范围、方法、资源以及日程的试验活动\n- **Master Test Plan（主要测试计划）**：针对一个项目/产品的一个单独的高层级测试计划，它统一了所有其他测试计划\n- Testing Level Specific（测试级别特定）：针对每一层的测试设计测试计划\n\n - 单元测试计划 —— 集成测试计划 —— 系统测试计划 —— 验收测试计划\n- Testing Type Specific（测试类型特定）：针对特定领域进行测试\n\n - 性能测试计划 —— 安全测试计划"}
{"id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd::1382", "page_id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd", "title": "ST 讲义（五）测试文档、静态测试与软件维护", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（五）测试文档、静态测试与软件维护", "section": "Ch6 测试文档/Test Case 测试用例/什么是测试用例？", "url": "https://a1npn29y3xu.feishu.cn/wiki/XLhZwD9V7ibz7KkZWaycRUyXnLd", "source_type": "docx", "n_chars": 246, "text": "- **测试用例**是由文档整理出来的一系列：**前置条件（前置需求）、流程（输入/行为）、后置条件（预期输出）**。这些内容都是测试人员用来决定系统是否符合需求或者是否正确运行的。\n- 一个测试用例可以有一个或者多个**测试脚本（test scripts）**\n\n - 测试脚本是用于执行测试的一系列指令\n- 一个测试用例的集合被称为**测试包 (test suite)**\n\n"}
{"id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd::1383", "page_id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd", "title": "ST 讲义（五）测试文档、静态测试与软件维护", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（五）测试文档、静态测试与软件维护", "section": "Ch6 测试文档/Bug Report 故障报告/缺陷报告/什么是故障报告？", "url": "https://a1npn29y3xu.feishu.cn/wiki/XLhZwD9V7ibz7KkZWaycRUyXnLd", "source_type": "docx", "n_chars": 244, "text": "- 一个用于**指出软件究竟出了什么问题的信息**的文档\n- 它列出了原因或看到的错误，以指出什么被视为错误，还包括请求 和/或 如何解决它的详细信息。\n- 清晰、可执行、易于完成\n- 写故障报告（缺陷报告）的目的是 **`get bugs fixed`**\n\n“This is what we have, this is what we should have instead, so fix it.”\n\n“这是我们拥有的，**（但）**这**（才）**是我们应该拥有的，所以修复它。”"}
{"id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd::1384", "page_id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd", "title": "ST 讲义（五）测试文档、静态测试与软件维护", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（五）测试文档、静态测试与软件维护", "section": "Ch6 测试文档/Test Summary Report 测试总结报告/什么是测试总结报告？", "url": "https://a1npn29y3xu.feishu.cn/wiki/XLhZwD9V7ibz7KkZWaycRUyXnLd", "source_type": "docx", "n_chars": 438, "text": "- 测试总结报告是在测试项目结束时或测试完成后准备的**重要可交付成果（important deliverable）**。\n- 测试总结报告的主要目的是**向项目干系人**去**解释**项目中**关于被执行测试的**各种细节以及活动。\n\nAfter performing **exhaustive testing**, **publishing the test results, metrics, best practices, lessons learned, conclusions on ‘Go Live’ etc**. are extremely important to produce that as evidence for the Testing performed and the Testing conclusion.\n\n在进行**详尽的测试**后，发布**测试结果、指标、最佳实践、经验教训、“上线”结论**等对于作为测试执行和测试结论的证据非常重要。"}
{"id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd::1385", "page_id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd", "title": "ST 讲义（五）测试文档、静态测试与软件维护", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（五）测试文档、静态测试与软件维护", "section": "Ch10 静态测试/考试范围 2025 PPT 1 - 15", "url": "https://a1npn29y3xu.feishu.cn/wiki/XLhZwD9V7ibz7KkZWaycRUyXnLd", "source_type": "docx", "n_chars": 38, "text": "**请注意，静态测试不考 Static Program Analysis**"}
{"id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd::1386", "page_id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd", "title": "ST 讲义（五）测试文档、静态测试与软件维护", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（五）测试文档、静态测试与软件维护", "section": "Ch10 静态测试/什么是静态测试？", "url": "https://a1npn29y3xu.feishu.cn/wiki/XLhZwD9V7ibz7KkZWaycRUyXnLd", "source_type": "docx", "n_chars": 302, "text": "Static testing is the process of carefully and methodically reviewing and analyzing the software for bugs without executing it. （静态测试是不执行代码、而是仔细地且**有条不紊地（methodically）**回顾且分析软件，从而找到 BUGS 的流程）\n\n这种测试非常有价值并且相比于基于执行的测试有好处。**根据研究，大量的错误可以通过静态测试被发现。**\n\n从成本和生产力的角度来看，这种测试很有好处，因为错误很早被发现（并且纠正），且相比基于执行的测试来说更节省时间。"}
{"id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd::1387", "page_id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd", "title": "ST 讲义（五）测试文档、静态测试与软件维护", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（五）测试文档、静态测试与软件维护", "section": "Ch10 静态测试/Code Review / 代码评审/代码评审的重要元素", "url": "https://a1npn29y3xu.feishu.cn/wiki/XLhZwD9V7ibz7KkZWaycRUyXnLd", "source_type": "docx", "n_chars": 137, "text": "- 发现问题\n\n - 发现软件的问题，比如说忽略的条目，错误等\n- 遵守规则\n\n - 被评审的代码量，以及被评审的代码将要被花费的时间等\n- 准备\n\n - 为了贡献评审，每一个参与者应该提前做准备\n- 书写报告\n\n - 总结审查结果，向开发团队提供报告。\n\n文贵被告"}
{"id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd::1388", "page_id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd", "title": "ST 讲义（五）测试文档、静态测试与软件维护", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（五）测试文档、静态测试与软件维护", "section": "Ch10 静态测试/Code Review / 代码评审/非正式的代码评审", "url": "https://a1npn29y3xu.feishu.cn/wiki/XLhZwD9V7ibz7KkZWaycRUyXnLd", "source_type": "docx", "n_chars": 211, "text": "Ø 同行评审\n\n§ 一小群非正式的程序员和/或测试人员充当审阅者。\n\n§ 参与者应遵循4个基本要素，即使审查是非正式的。\n\nØ 演练\n\n§ 一个更正式的过程，代码的作者将代码正式地呈现给一小群程序员和/或测试人员。\n\n§ 作者逐行阅读代码解释它的作用，审阅者倾听并提出问题。\n\n§ 参与者应遵循4个基本要素。\n\n"}
{"id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd::1389", "page_id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd", "title": "ST 讲义（五）测试文档、静态测试与软件维护", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（五）测试文档、静态测试与软件维护", "section": "Ch10 静态测试/Code Review / 代码评审/代码评审检查表/数据引用错误", "url": "https://a1npn29y3xu.feishu.cn/wiki/XLhZwD9V7ibz7KkZWaycRUyXnLd", "source_type": "docx", "n_chars": 274, "text": "扩展知识，什么叫 OFF-BY-ONE 错误？\n\n\n\n\n\nAre data structures that are referenced in different functions defined identically? 不同函数中引用的数据结构定义是否相同？（比如说 Node 在链表、二叉树、N 叉树、图的定义是不同的）"}
{"id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd::1390", "page_id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd", "title": "ST 讲义（五）测试文档、静态测试与软件维护", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（五）测试文档、静态测试与软件维护", "section": "Ch10 静态测试/Code Review / 代码评审/代码评审检查表/数据声明错误", "url": "https://a1npn29y3xu.feishu.cn/wiki/XLhZwD9V7ibz7KkZWaycRUyXnLd", "source_type": "docx", "n_chars": 138, "text": "\n\nAre all variables explicitly declared within a specific module? 所有变量都在特定模块中显式声明吗？"}
{"id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd::1391", "page_id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd", "title": "ST 讲义（五）测试文档、静态测试与软件维护", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（五）测试文档、静态测试与软件维护", "section": "Ch10 静态测试/Code Review / 代码评审/代码评审检查表/计算错误", "url": "https://a1npn29y3xu.feishu.cn/wiki/XLhZwD9V7ibz7KkZWaycRUyXnLd", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd::1392", "page_id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd", "title": "ST 讲义（五）测试文档、静态测试与软件维护", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（五）测试文档、静态测试与软件维护", "section": "Ch10 静态测试/Code Review / 代码评审/代码评审检查表/对比错误", "url": "https://a1npn29y3xu.feishu.cn/wiki/XLhZwD9V7ibz7KkZWaycRUyXnLd", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd::1393", "page_id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd", "title": "ST 讲义（五）测试文档、静态测试与软件维护", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（五）测试文档、静态测试与软件维护", "section": "Ch10 静态测试/Code Review / 代码评审/代码评审检查表/控制流错误", "url": "https://a1npn29y3xu.feishu.cn/wiki/XLhZwD9V7ibz7KkZWaycRUyXnLd", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd::1394", "page_id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd", "title": "ST 讲义（五）测试文档、静态测试与软件维护", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（五）测试文档、静态测试与软件维护", "section": "Ch10 静态测试/Code Review / 代码评审/代码评审检查表/子程序参数错误", "url": "https://a1npn29y3xu.feishu.cn/wiki/XLhZwD9V7ibz7KkZWaycRUyXnLd", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd::1395", "page_id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd", "title": "ST 讲义（五）测试文档、静态测试与软件维护", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（五）测试文档、静态测试与软件维护", "section": "Ch10 静态测试/Code Review / 代码评审/代码评审检查表/输入输出错误", "url": "https://a1npn29y3xu.feishu.cn/wiki/XLhZwD9V7ibz7KkZWaycRUyXnLd", "source_type": "docx", "n_chars": 195, "text": "\n\nDoes the software adhere to the specified format of the date being read from or written to the external device? / 软件是否遵循从外部设备读取或写入日期的指定格式？"}
{"id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd::1396", "page_id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd", "title": "ST 讲义（五）测试文档、静态测试与软件维护", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（五）测试文档、静态测试与软件维护", "section": "Ch10 静态测试/Code Review / 代码评审/代码评审检查表/其他错误项", "url": "https://a1npn29y3xu.feishu.cn/wiki/XLhZwD9V7ibz7KkZWaycRUyXnLd", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd::1397", "page_id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd", "title": "ST 讲义（五）测试文档、静态测试与软件维护", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（五）测试文档、静态测试与软件维护", "section": "Ch12 软件维护/什么是软件维护", "url": "https://a1npn29y3xu.feishu.cn/wiki/XLhZwD9V7ibz7KkZWaycRUyXnLd", "source_type": "docx", "n_chars": 675, "text": "When the transition from development to evolution is **not seamless**, ***the process of changing the software after delivery*** is often called software maintenance.\n\n当从开发到演进的过渡**不是无缝的**，**交付后更改软件**的过程通常称为软件维护。\n\nMaintenance is the process of **modifying a software system** or component after delivery to correct faults, **improve performance or other attributes**, or **adapt to a changed environment**.\n\n维护是在交付后**修改软件系统**或组件以纠正故障、**提高性能**或其他属性或**适应变化环境**的过程。\n\nØ Maintenance does not normally involve major changes to the system’s architecture\n\nØ 维护一般不涉及系统架构的大改动\n\nØ Maintenance requires program understanding\n\nØ 维护需要程序理解\n\n| 软件维护 Maintenance | 在软件部署之后保持软件系统可操作所需求的活动 |\n|-|-|"}
{"id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd::1398", "page_id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd", "title": "ST 讲义（五）测试文档、静态测试与软件维护", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（五）测试文档、静态测试与软件维护", "section": "Ch12 软件维护/什么是软件维护", "url": "https://a1npn29y3xu.feishu.cn/wiki/XLhZwD9V7ibz7KkZWaycRUyXnLd", "source_type": "docx", "n_chars": 247, "text": "nce requires program understanding\n\nØ 维护需要程序理解\n\n| 软件维护 Maintenance | 在软件部署之后保持软件系统可操作所需求的活动 |\n|-|-|\n| 软件演变 Evolution | 将软件不断变好的持续改变 |\n\n\n\n"}
{"id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd::1399", "page_id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd", "title": "ST 讲义（五）测试文档、静态测试与软件维护", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（五）测试文档、静态测试与软件维护", "section": "Ch12 软件维护/🌟 必考：软件维护的类型（CAPP）", "url": "https://a1npn29y3xu.feishu.cn/wiki/XLhZwD9V7ibz7KkZWaycRUyXnLd", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd::1400", "page_id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd", "title": "ST 讲义（五）测试文档、静态测试与软件维护", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（五）测试文档、静态测试与软件维护", "section": "Ch12 软件维护/🌟 必考：软件维护的类型（CAPP）/Corrective \\~ 纠错性", "url": "https://a1npn29y3xu.feishu.cn/wiki/XLhZwD9V7ibz7KkZWaycRUyXnLd", "source_type": "docx", "n_chars": 56, "text": "- 修复**潜在的**错误（包括了临时的**补丁和变通方法** patches and workarounds）"}
{"id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd::1401", "page_id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd", "title": "ST 讲义（五）测试文档、静态测试与软件维护", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（五）测试文档、静态测试与软件维护", "section": "Ch12 软件维护/🌟 必考：软件维护的类型（CAPP）/Adaptive \\~ 适应性", "url": "https://a1npn29y3xu.feishu.cn/wiki/XLhZwD9V7ibz7KkZWaycRUyXnLd", "source_type": "docx", "n_chars": 29, "text": "- 处理外部的变化（包括硬件平台的改变以及支持软件的改变）"}
{"id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd::1402", "page_id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd", "title": "ST 讲义（五）测试文档、静态测试与软件维护", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（五）测试文档、静态测试与软件维护", "section": "Ch12 软件维护/🌟 必考：软件维护的类型（CAPP）/Preventative \\~ 预防性", "url": "https://a1npn29y3xu.feishu.cn/wiki/XLhZwD9V7ibz7KkZWaycRUyXnLd", "source_type": "docx", "n_chars": 133, "text": "- 提升未来的可维护性（文档、注释等）\n\n\n\n"}
{"id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd::1403", "page_id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd", "title": "ST 讲义（五）测试文档、静态测试与软件维护", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（五）测试文档、静态测试与软件维护", "section": "Ch12 软件维护/软件维护的生命周期（SMLC）", "url": "https://a1npn29y3xu.feishu.cn/wiki/XLhZwD9V7ibz7KkZWaycRUyXnLd", "source_type": "docx", "n_chars": 112, "text": "Changes are implemented in the software system by following a software maintenance process\n\n通过遵循软件维护过程在软件系统中实施变更"}
{"id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd::1404", "page_id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd", "title": "ST 讲义（五）测试文档、静态测试与软件维护", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（五）测试文档、静态测试与软件维护", "section": "Ch12 软件维护/额外的维护专有名词", "url": "https://a1npn29y3xu.feishu.cn/wiki/XLhZwD9V7ibz7KkZWaycRUyXnLd", "source_type": "docx", "n_chars": 609, "text": "Ø Maintainability : The ease with which software can be modified\n\nØ Ripple effect : Changes in one software location can impact other components\n\nØ Impact analysis : Process of identifying how a change in terms of how a change will affect the rest of the system\n\nØ Traceability : The degree to which a relationship can be established between two or more software artifacts\n\nØ Legacy systems : A software system that is still in use, but the development team is no longer active\n\nØ 可维护性：修改软件的难易程度\n\nØ 涟漪效应：一个软件位置的变化会影响其他组件\n\nØ 影响分析：根据变化将如何影响系统的其余部分来确定变化的过程\n\nØ 可追溯性：两个或多个软件工件之间可以建立关系的程度\n\nØ 遗留系统：仍在使用但开发团队不再活跃的软件系统"}
{"id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd::1405", "page_id": "docx::XLhZwD9V7ibz7KkZWaycRUyXnLd", "title": "ST 讲义（五）测试文档、静态测试与软件维护", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（五）测试文档、静态测试与软件维护", "section": "Ch12 软件维护/🌟 软件维护的主要活动（major main activities）", "url": "https://a1npn29y3xu.feishu.cn/wiki/XLhZwD9V7ibz7KkZWaycRUyXnLd", "source_type": "docx", "n_chars": 128, "text": "\n\n识别变化（是啥？为啥？）→ 管理过程（要啥资源？） → 理解程序（咋办？决定涟漪效应） → 做出改变 → 测试改变 → 文档记录 + 记录改变"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1406", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "ST 讲义（四）V 模型四大测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 173, "text": "ST 讲义（四）V 模型四大测试\n\n后面的章节很符合软件学院四大文科的特点：章节切分详细 + 记忆为主\n\n因此，讲义（四）和 讲义（五）都会**基于 REVIEW 进行复习**，讲义仅供参考，大家复习还是得以 PPT 为主\n\n不考的内容讲义只会写标题，不会写正文\n\n讲义（四）会按照 V 模型的测试顺序进行复习，而讲义（五）会补充一系列测试的细节"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1407", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "序、测试层级划分", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1408", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch7 单元测试（白） Unit", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 94, "text": "不管以后是否从事测开岗，单元测试都是必须要掌握的。\n\n单元测试指的是针对可独立运行模块进行测试，关注程序内部的执行逻辑、内存占用、异常处理、数据 CRUD\n\n单元测试的典型框架：XUnit"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1409", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch7 单元测试（白） Unit/🌟 什么是单元测试？", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 320, "text": "- 单元测试主要是由**开发者**写的**白盒测试**，它被设计用于**验证小单元程序的功能**。\n\n - Key Metaphor: I.C. Testing（关键隐喻：I.C. 测试/集成电路测试）\n - 集成电路在整个电路被测试之前，会单独地测试模块的功能\n- 定义关键词\n\n \n\n - **Whitebox** 白盒\n - **Developers** 开发者\n - **Small Units** 小单元\n - **Verify** 验证（经典 Verification 和 Validation 的对比）"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1410", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch7 单元测试（白） Unit/单元测试的任务？", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1411", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch7 单元测试（白） Unit/🌟 单元测试的作用？", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 616, "text": "- Helps **localize errors** （帮助定位错误）\n\n - Failure indicates problem in the unit undet test（失败表示单元测试存在问题）\n- Find errors **early**（尽早发现错误）\n\n - Unit tests are written during development, usually by developer（单元测试在开发过程中一般由开发人员编写）\n - More expensive to fix defects found later by another team（修复其他团队后来发现的缺陷成本更高）\n- Avoid **unnecessary functionality**（避免不必要的功能）\n\n - Write test first, only write enough code to get it working（先写测试，只写足够的代码让它工作）\n- Improve **code quality**（提高代码质量）\n\n - Helps developer deliver working code （帮助开发者发布工作代码）\n - Assure minimum quality of units before integration into system （在集成系统之前确保代码单元的最小质量）"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1412", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch7 单元测试（白） Unit/单元测试的流程？", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 50, "text": "单元测试是软件开发中针对代码最小可测试单元（如函数、方法、类）的验证过程，其核心流程如下：\n\n---"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1413", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch7 单元测试（白） Unit/单元测试的流程？/**1. 计划阶段**", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 147, "text": "- **确定测试范围**：明确需要测试的代码单元（如函数、类或模块）。\n- **选择测试框架**：根据语言选择工具（如 Java 用 JUnit，Python 用 pytest，JavaScript 用 Jest）。\n- **定义测试目标**：明确要验证的功能、边界条件、异常场景等。\n\n---"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1414", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch7 单元测试（白） Unit/单元测试的流程？/**2. 编写测试用例**", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 348, "text": "- **覆盖三种场景**：\n\n - **正常输入**：验证预期结果（如 `add(2,3)` 返回 `5`）。\n - **异常输入**：测试错误处理（如传递空值或非法参数）。\n - **边界条件**：测试极端值（如数组越界、零值、最大最小值）。\n- **隔离依赖**：使用 Mock/Stub 技术模拟外部依赖（如数据库、API）。\n\n**示例（Python/pytest）：**\n\n```Python\ndef test_divide():\n # 正常场景\n assert divide(10, 2) == 5\n # 异常场景（除数为零）\n with pytest.raises(ValueError):\n divide(10, 0)\n```\n\n---"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1415", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch7 单元测试（白） Unit/单元测试的流程？/**3. 执行测试**", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 118, "text": "- **运行测试套件**：通过命令行或 IDE 执行测试（如 `pytest test_math.py`）。\n- **生成报告**：查看通过/失败的用例，分析代码覆盖率（使用工具如 `coverage.py`、JaCoCo）。\n\n---"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1416", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch7 单元测试（白） Unit/单元测试的流程？/**4. 分析结果**", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 73, "text": "- **定位失败用例**：根据错误信息定位代码问题（如逻辑错误、未处理的异常）。\n- **优化测试用例**：补充遗漏场景或修复测试逻辑。\n\n---"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1417", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch7 单元测试（白） Unit/单元测试的流程？/**5. 修复与回归测试**", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 66, "text": "- **修改代码**：修复缺陷后重新运行相关测试。\n- **回归验证**：确保修复未破坏其他功能（自动化工具可快速执行）。\n\n---"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1418", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch7 单元测试（白） Unit/单元测试的流程？/**6. 自动化与持续集成（CI）**", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 94, "text": "- **集成到 CI/CD**：通过 Jenkins、GitHub Actions 等工具自动触发测试。\n- **监控覆盖率**：设定覆盖率阈值（如 ≥80%），确保测试有效性。\n\n---"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1419", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch7 单元测试（白） Unit/单元测试的流程？/**7. 维护测试用例**", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 65, "text": "- **同步代码变更**：当业务逻辑调整时，同步更新测试用例。\n- **定期重构**：合并重复用例，提升测试代码可读性。\n\n---"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1420", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch7 单元测试（白） Unit/单元测试的流程？/**流程图**", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 75, "text": "```Plain Text\n计划 → 编写用例 → 执行测试 → 分析结果 → 修复问题 → 回归测试 → 自动化集成 → 持续维护\n```\n\n---"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1421", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch7 单元测试（白） Unit/单元测试的流程？/**关键原则**", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 217, "text": "- **FIRST 原则**：\n\n - **Fast**（快速）：测试应秒级完成。\n - **Isolated**（隔离）：用例间无依赖。\n - **Repeatable**（可重复）：结果稳定不随机。\n - **Self-Validating**（自验证）：自动判断通过/失败。\n - **Timely**（及时）：测试与代码同步编写。\n\nFIRST 快歌冲演技\n\n通过规范流程，单元测试可显著提升代码质量，降低维护成本。"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1422", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch7 单元测试（白） Unit/单元测试的组成？", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 128, "text": "\n\n在单元测试中，**STUB**（桩单元）、**UNIT**（被测代码）和**DRIVER**（驱动模块）是构成测试环境的核心组件，其作用如下："}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1423", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch7 单元测试（白） Unit/单元测试的组成？/1. STUB（桩单元）", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 175, "text": "用于**替代被测代码依赖的下层模块**，模拟其行为并返回预设结果，以实现被测代码的**逻辑隔离**。\n\n- **特点**：\n\n - 模拟被调用函数的功能，返回硬编码的预期值。\n - 当依赖的模块未完成或需要特定场景模拟时使用（如异常处理、边界条件）。\n- **示例**：若被测函数调用未实现的子函数，需编写桩函数模拟返回值（如返回固定值或异常）。"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1424", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch7 单元测试（白） Unit/单元测试的组成？/2. UNIT（被测代码）", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 145, "text": "即需验证的**最小功能单元**（如函数、类），需覆盖其所有逻辑分支和边界条件。\n\n- **测试重点**：\n\n - **功能性**：输入输出是否符合预期。\n - **健壮性**：异常输入或环境下的行为（如空指针、越界）。\n - **性能**：执行时间和资源占用（特殊场景需针对性测试）。"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1425", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch7 单元测试（白） Unit/单元测试的组成？/3. DRIVER（驱动模块）", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 154, "text": "作为**被测代码的调用入口**，负责传递测试输入、触发执行并验证结果。\n\n- **功能**：\n\n - 接收测试用例的输入和预期输出。\n - 调用被测单元并传递参数。\n - 比较实际输出与预期结果，生成测试报告。\n- **适用场景**：当被测代码无法独立运行（如非顶层模块）时，需驱动模块模拟主程序逻辑。"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1426", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch7 单元测试（白） Unit/单元测试的组成？/4. 测试支持代码的替代关系", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 200, "text": "- **STUB**和**DRIVER**共同构成**测试支持代码**，替代真实依赖以实现隔离测试：\n\n - **STUB**替代下层依赖（如数据库、外部接口），避免外部不确定性。\n - **DRIVER**替代上层调用者，控制被测代码的执行流程。\n- **协作示例**： 当测试函数A时，若其依赖函数B未完成，需用STUB模拟B的返回值；同时通过DRIVER调用A，传入不同参数验证逻辑分支。"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1427", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch7 单元测试（白） Unit/单元测试的组成？/5. 何时使用这些组件？", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 169, "text": "- **需编写STUB**：依赖模块未测试、需模拟复杂场景（如网络超时）。\n- **需编写DRIVER**：被测代码非独立可执行（如中间层函数）。\n- **无需STUB/DRIVER**：被测代码为最底层函数（无依赖）或依赖已通过测试且稳定。\n\n通过合理设计这三者，可实现**高内聚、低耦合的单元测试**，确保被测代码的独立性和可重复性。"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1428", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch7 单元测试（白） Unit/TDD（测试驱动开发）", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 105, "text": "详情请搜索关键词 TDD："}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1429", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch7 单元测试（白） Unit/XUnit（自动化测试框架）【2025 PPT 20-34】", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 85, "text": "\n\n具体到特定语言的 XUnit，感兴趣的同学多多实操即可。"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1430", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch8 集成测试（黑 + 白） Integration/考试范围 2025 PPT 1 - 26", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 168, "text": "**请注意，集成测试不考 Call-Graph（调用图），不考 MM based Integration**\n\n\n\n"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1431", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch8 集成测试（黑 + 白） Integration/什么是集成测试？", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1432", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch8 集成测试（黑 + 白） Integration/🌟 Drivers and Stubs 驱动模块和桩单元", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 698, "text": "\n\nØ Drivers\n\n§ Drivers can have varying levels of sophistication.\n\n§ It could be **hard-coded** to run through a fixed series of input values, read data from **a prepared file**, contain a suitable **random number generator** etc.\n\nØ 驱动程序\n\n§ 驱动程序可以有不同程度的复杂程度。\n\n§ 它可以被**硬编码**以运行一系列固定的输入值，从**准备好的文件**中读取数据，包含合适的**随机数生成器**等。\n\nØ Stubs\n\n§ A stub is a **temporary or dummy software** that is required by the software under test to operate properly.\n\n§ This is a **throw-away version** to allow testing to take place.\n\n§ It will provide a **fixed or limited set of values** to be passed to the software under test.\n\nØ 存根\n\n§ 存根是被测软件正常运行所需的**临时或虚拟软件**。"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1433", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch8 集成测试（黑 + 白） Integration/🌟 Drivers and Stubs 驱动模块和桩单元", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 153, "text": "mited set of values** to be passed to the software under test.\n\nØ 存根\n\n§ 存根是被测软件正常运行所需的**临时或虚拟软件**。\n\n§ 这是一个**一次性版本**，允许进行测试。\n\n§ 它将提供一组**固定或有限的值**以传递给被测软件。"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1434", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch8 集成测试（黑 + 白） Integration/基于功能分解的集成测试/方法集", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1435", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch8 集成测试（黑 + 白） Integration/基于功能分解的集成测试/方法集/Big bang", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 226, "text": "\n\n\n\n\n\n"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1436", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch8 集成测试（黑 + 白） Integration/🌟 期末例题：NextDate Program/Python 实现", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 692, "text": "```Python\ndef is_leap_year(year):\n return (year % 4 == 0 and year % 100 != 0) or (year % 400 == 0)\n\ndef days_in_month(month, year):\n days = [-1, 31, 28 + is_leap_year(year), 31, 30, 31, 30, 31, 31, 30, 31, 30, 31]\n return days[month]\n\ndef next_date(year, month, day):\n day += 1\n if day > days_in_month(month, year):\n day = 1\n month += 1\n if month > 12:\n month = 1\n year += 1\n return year, month, day\n\ndef print_date(year, month, day):\n print(f\"{year} {month:02d} {day:02d}\")\n\ndef is_valid(year, month, day):\n return (1812 <= year <= 2012) or not (1 <= month <= 12) or not (1 <= day <= days_in_month(month, year))\n\ndef main():"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1437", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch8 集成测试（黑 + 白） Integration/🌟 期末例题：NextDate Program/Python 实现", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 491, "text": "ear <= 2012) or not (1 <= month <= 12) or not (1 <= day <= days_in_month(month, year))\n\ndef main():\n year, month, day = map(int, input().split()) # get_date(today)\n print(f\"{year} {month:02d} {day:02d}\") # print_date(today)\n if not is_valid(year, month, day):\n print(\"Invalid\")\n else:\n year, month, day = next_date(year, month, day) # tomorrow = next_date(today)\n print_date(year, month, day) # print_date(tomorrow)\n\nif __name__ == \"__main__\":\n main()\n```"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1438", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch8 集成测试（黑 + 白） Integration/🌟 期末例题：NextDate Program/集成测试/BIGBANG", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 74, "text": "编译所有的模块，并且测试整一个系统\n\n"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1439", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch8 集成测试（黑 + 白） Integration/🌟 期末例题：NextDate Program/集成测试/自顶向下", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 492, "text": "从 Main 方法开始测试，然后逐个桩单元进行测试。\n\n我们必须构建存根，使其向真实模块返回正确的值并与测试用例兼容。\n\n```Python\ndef increment_date(year, month, day):\n if year == 1999 and month == 12 and day == 31:\n year += 1\n month = 1\n day = 1\n elif year == 2000 and month == 2 and day == 28:\n day += 1\n elif year == 2000 and month == 2 and day == 29:\n month += 1\n day = 1\n return year, month, day # 先面向结果编程，然后再替换成真实方法，不会直接调用 main 函数\n```\n\n"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1440", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch8 集成测试（黑 + 白） Integration/🌟 期末例题：NextDate Program/集成测试/自底向上", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 249, "text": "```Python\ndef test_is_leap_year():\n assert is_leap_year(1900) == False\n assert is_leap_year(1999) == False\n assert is_leap_year(2000) == True\n assert is_leap_year(2004) == True\n```\n\n"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1441", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch8 集成测试（黑 + 白） Integration/🌟 期末例题：NextDate Program/集成测试/三明治测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1442", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch8 集成测试（黑 + 白） Integration/🌟 期末例题：NextDate Program/优势和不足", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 335, "text": "优势Intuitively clear 清晰直观\"build\" with proven components 使用经过验证的组件进行“构建”Fault isolation varies with the number of units being Integrated 故障隔离随着被集成的单元数量而变化不足some branches in a functional decomposition may not correspond with actual interfaces. 函数分解中的某些分支可能与实际接口不对应stub and driver development can be extensive 每次加一个模块，就要加 stub 和 driver，消耗大"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1443", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch9 系统测试（黑） System/什么是系统测试？", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 212, "text": "\n\n使用了**黑盒测试**技术\n\n§ Reconciles software against top-level requirements\n\n§ Tests stem from concrete use cases in the requirements\n\n§ 根据顶级要求协调软件\n\n§ 测试源于需求中的具体用例"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1444", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch9 系统测试（黑） System/系统测试的类型", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 87, "text": "- 按照测试的目的做区分，而不是它的范围或者机制（mechanism）\n\n - 功能测试：确保功能需求符合预期\n - 非功能测试：确保非功能需求符合预期\n - 回归测试"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1445", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch9 系统测试（黑） System/系统测试的类型/🌟 功能测试/定义", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 169, "text": "测试的默认假设\n\n- 功能测试验证软件的行为是否符合预期\n- 它也包括了测试**坏的输入**，去校验**隐含假设（implicit assumptions）**\n\n - 例：即使给了一个离谱的输入，程序也应该做出合理的回复\n- 削减所有级别的测试，但**重在单元测试**\n\n - 系统测试使用的接口：用户接口、网络接口、专用硬件接口等"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1446", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch9 系统测试（黑） System/系统测试的类型/🌟 功能测试/策略", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 185, "text": "\n\n基于黑盒测试（等价类划分、边界值分析、场景测试、错误估计、决策表测试、随机测试等）=> 直接\n\n类似单元测试，测试用例和测试数据都使用正在使用的技术进行选择。\n\n唯一不同的是，不是调用指定参数的方法，而是要**视情况将数据输入接口，然后从接口收集结果**。"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1447", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch9 系统测试（黑） System/系统测试的类型/非功能测试/定义", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 75, "text": "测试软件的质量 \"-ilities\"\n\n"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1448", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch9 系统测试（黑） System/系统测试的类型/🌟 回归测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 391, "text": "Making sure that code changes haven’t broken existing functionality, performance, security, etc.（确保代码更改没有破坏现有功能、性能、安全性等。）\n\n回归测试的必要性是：无论是修复过往的 BUG 还是新增某个特性，引入新 BUG 是很常见的。\n\n在实际应用中，这意味着在代码发生变更以后**要重新跑测试用例**。\n\nWith good **test automation** and good **unit/integration/system/**etc. tests. This is literally running tests again after a change.\n\n通过良好的**测试自动化**和良好的**单元/集成/系统**/等测试。这实际上是在更改后再次运行测试。"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1449", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch9 系统测试（黑） System/系统测试的类型/测试自动化【2025 PPT 13 - 17】", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1450", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch9 系统测试（黑） System/系统测试的类型/测试自动化【2025 PPT 13 - 17】/🌟 测试自动化的优缺点", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1451", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch9 系统测试（黑） System/系统测试的类型/测试自动化【2025 PPT 13 - 17】/🌟 测试自动化的优缺点/**优点**", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 139, "text": "- **高投资回报率（ROI） & 加快产品上市速度**\n\n - 支持重复测试用例的执行\n - 支持大规模测试矩阵的覆盖测试\n - 支持并行执行（如多环境同步测试）\n - 支持无人值守执行（自动化脚本可定时运行）\n - 提高准确性，减少人为错误\n - 节省时间和成本"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1452", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch9 系统测试（黑） System/系统测试的类型/测试自动化【2025 PPT 13 - 17】/🌟 测试自动化的优缺点/**缺点**", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 239, "text": "- 自动化工具通常成本高昂；\n- 无法有效评估应用的用户体验（如界面友好性、交互流畅度）；\n- 必须掌握编程知识及相关经验。\n\n---\n\n**注**：\n\n- **术语对照**：\n\n - *Test Matrix* → 测试矩阵（指多环境、多配置组合的测试场景）。\n - *Unattended Execution* → 无人值守执行（无需人工干预的自动化运行）。\n- **适用场景**：\n\n - 自动化测试适用于回归测试、负载测试等重复性任务，但需权衡初期投入与长期收益。"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1453", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch9 系统测试（黑） System/🌟 性能测试/定义", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 236, "text": "\n\n用于检查应用程序或软件**在工作负载下**在响应性和稳定性方面表现的测试类型。\n\n性能测试的目标是从应用中识别并且移除性能瓶颈。这是**性能工程的子集。**\n\n这一种测试主要用于检查软件的速度、可扩展性和稳定性是否符合预期需求。\n\n**速度：**应用的响应快不快\n\n**可扩展性：**软件应用能处理的最大用户负载\n\n**稳定性：**在不同的负载下应用是否稳定"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1454", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch9 系统测试（黑） System/🌟 性能测试/常见的性能问题", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1455", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch9 系统测试（黑） System/🌟 性能测试/性能测试指标：监控的参数", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 652, "text": "**Processor Usage –** an amount of time processor spends executing non-idle threads.\n\n处理器使用率：处理器用于执行非空闲线程的时间量\n\n**Memory use –** amount of physical memory available to processes on a computer.\n\n内存利用率：计算机上进程的物理可用存储器量\n\n**Disk time –** amount of time disk is busy executing a read or write request.\n\n磁盘时间：磁盘忙于执行读或写请求的时间量\n\n**Bandwidth –** shows the bits per second used by a network interface.\n\n带宽：展示了一个网络接口每秒钟使用的比特位\n\n**Response time –** time from when a user enters a request until the first character of the response is received.\n\n响应时间：从用户输入请求到收到响应的第一个字符的时间。\n\n**Throughput –** rate a computer or network receives requests per second.\n\n吞吐量：每秒钟电脑或者网络获取请求的比率"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1456", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch9 系统测试（黑） System/🌟 性能测试/性能测试指标：监控的参数", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 231, "text": "。\n\n**Throughput –** rate a computer or network receives requests per second.\n\n吞吐量：每秒钟电脑或者网络获取请求的比率\n\n**Hits per second –** the no. of hits on a web server during each second of a load test.\n\n每秒命中数：在负载测试的每一秒期间 Web服务器 上的命中数\n\n§ …… 其他参数"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1457", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch9 系统测试（黑） System/🌟 性能测试/性能测试样例（基线测试 ）", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 97, "text": "\n\n以下是 **基线测试（Baseline Test）** 的翻译与说明：\n\n---"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1458", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch9 系统测试（黑） System/🌟 性能测试/性能测试样例（基线测试 ）/定义", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 67, "text": "- 通过 **1个虚拟用户（Vuser）** 执行多轮次场景，验证应用程序性能是否符合业务 **服务级别协议（SLA）**。\n\n---"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1459", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch9 系统测试（黑） System/🌟 性能测试/性能测试样例（基线测试 ）/测试目标", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 588, "text": "1. **验证响应时间**\n\n - 当 **1000名用户同时访问网站** 时，响应时间不超过4秒。\n - 在网络连接缓慢时，验证 **负载下应用程序的响应时间** 是否在可接受范围内。\n - 在 **低、中、高负载条件** 下，检查应用程序的响应时间。\n2. **验证系统极限**\n\n - 检查应用程序在崩溃前能处理的最大用户数。\n - 验证 **同时读写500条记录时** 的数据库执行时间。\n3. **资源监控**\n\n - 在峰值负载条件下，检查应用程序和数据库服务器的 **CPU及内存使用率**。\n\n---\n\n**注**：\n\n- **基线测试的核心作用**：\n\n - 建立性能基准，用于后续压力测试、负载测试的对比参照。\n - 确保系统在基础场景中满足业务 SLA 要求（如响应时间、资源占用）。\n- **关键指标**：\n\n - *SLA*：服务级别协议（例如响应时间、系统可用性等承诺）。\n - *Vuser*：虚拟用户（模拟真实用户行为的测试工具配置）。\n- **适用场景**：\n\n - 上线前性能验收测试、系统优化后的基准验证。\n\n---\n\n此翻译可直接用于技术文档或测试报告，重点保留了原始技术细节和测试逻辑。\n\n"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1460", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch9 系统测试（黑） System/🌟 性能测试/性能测试的类型", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 611, "text": "| 负载测试 | Checks the application’s ability to perform under anticipated user loads. The objective is to identify **performance bottlenecks** before the software application goes live. 检查应用程序在预期用户负载下执行的能力。 目标是在软件应用程序上线之前识别**性能瓶颈**。 |\n|-|-|\n| 压力测试 | Involves testing an application under extreme workloads to see how it handles high traffic or data processing. The objective is to identify the **breaking point** of an application. 涉及在极端工作负载下测试应用程序，以了解它如何处理高流量或数据处理。目标是确定应用程序的**崩溃点**。 |\n| 持久测试 | To make sure the software can handle the expected load over a **long period of time**. 确保软件能够**长时间处理预期负载**。 |"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1461", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch9 系统测试（黑） System/🌟 性能测试/性能测试的类型", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 533, "text": "e the software can handle the expected load over a **long period of time**. 确保软件能够**长时间处理预期负载**。 |\n| 尖锋测试 | Tests the software’s reaction to **sudden large spikes** in the load generated by users. 测试软件对用户产生的**突然大负载峰值**的反应。 |\n| 容量测试 | Under Volume Testing **large no. of. Data** is populated in a database and the overall software system’s behavior is monitored. The objective is to check software application’s performance under varying **database volumes**. 在容量测试下，**大量数据**被填充到数据库中，并监控整个软件系统的行为。 目标是检查软件应用程序在不同**数据库卷**下的性能。 |"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1462", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch9 系统测试（黑） System/🌟 性能测试/性能测试的类型/🌟 性能测试 vs 负载测试 vs 压力测试 vs 容量测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 679, "text": "性能测试是负载测试和压力测试的**父集**\n\n\n\n\n\n\n\n| | **性能测试** | **负载测试** | **压力测试** |\n|-|-|-|-|\n| 领域 | 父集 | 子集 | 子集 |\n| 范围 | 广泛（负载、压力、容量、持续、尖峰、可扩展性、可靠性） | 更窄 | 更窄 |\n| 目标 | 为应用设计 benchmark 规则 以及标准 | 要确定系统的上限，可设置应用程序的 SLA 并查看系统如何处理重负载卷。 | 确定系统在负载不足时的行为方式以及它如何从故障中恢复。基本上，让您的应用程序为意外的流量高峰做好准备。 |\n| 负载极限 | 都在突破阈值以下和突破阈值以上 | 直到崩溃的为止 | 高于崩溃阈值 |\n| 考察属性 | 项目使用、可靠性、可扩展性、资源使用、响应时间、吞吐量、速度等 | 峰值性能、服务器吞吐量、各种负载水平下的响应时间**（低于崩溃的阈值），**H/W 环境的充足性 | 超出带宽容量、响应时间**（超过崩溃阈值）**等的稳定性。 |\n| 发现的问题 | 所有性能问题，包括运行时膨胀与速度、延迟、吞吐量等有关的问题等。负载平衡问题、带宽问题、系统容量过载、数据吞吐量问题等。"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1463", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch9 系统测试（黑） System/🌟 性能测试/性能测试的类型/🌟 性能测试 vs 负载测试 vs 压力测试 vs 容量测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 577, "text": "带宽容量、响应时间**（超过崩溃阈值）**等的稳定性。 |\n| 发现的问题 | 所有性能问题，包括运行时膨胀与速度、延迟、吞吐量等有关的问题等。负载平衡问题、带宽问题、系统容量过载、数据吞吐量问题等。 | 负载平衡问题、带宽问题、系统容量过载、数据吞吐量问题等。 | 安全漏洞，存在腐败问题，在过载、缓慢、内存泄漏等情况下。 |\n\n| | **容量测试** | **负载测试** | **压力测试** |\n|-|-|-|-|\n| 领域 | 大量数据 | 大量用户 | 过多用户、过多数据，towards 系统崩溃 |\n\nIn volume testing, it is checked as to how the system behaves against a certain volume of data.\n\n在容量测试中，检查系统对一定数据量的行为。\n\nThus, **the databases are stuffed with their maximum capacity** and their performance levels, like response time and server throughput, are monitored.\n\n因此，数据库**充满了最大容量**，并且监控了响应时间和服务器吞吐量等**性能水平**。"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1464", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch9 系统测试（黑） System/🌟 性能测试/性能测试步骤", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 283, "text": "\n\n\n\n\n\n\n\n"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1465", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch9 系统测试（黑） System/🌟 性能测试/自动化性能测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1466", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch11 验收测试（黑） Acceptance/🌟 什么是验收测试？", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 119, "text": "- 验收测试是**软件测试的最终阶段**，此时系统被测试去检验**是否符合其业务要求。**\n- 验收测试通常由客户或者终端用户实施，目的是为了检验产品是否符合发行标准。\n- 时间点在系统测试之后，最终发布之前\n- **使用黑盒测试方法**"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1467", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch11 验收测试（黑） Acceptance/验收测试的组成部分/*Software Configuration Review 软件配置审查*", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 201, "text": "通常的软件配置项包括：\n\n① 主要的软件程序配置，通常包括源代码、可执行程序、软件安装以及配置脚本，核心的测试脚本或者测试程序\n\n② 主要的技术文档\n\n③ 主要的开发管理文档\n\n\n\n"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1468", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch11 验收测试（黑） Acceptance/验收测试的组成部分/*Software Validity Testing 软件有效性测试*", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1469", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch11 验收测试（黑） Acceptance/Alpha 测试 和 Beta 测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 152, "text": "他们都是验收测试的类型，都是客户确认方法（Customer Validation methodologies）。这两种测试方法都可以在产品上线的时候帮忙建立信心，从而在市场的产品上取得成功。\n\n"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1470", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch11 验收测试（黑） Acceptance/Alpha 测试 和 Beta 测试/Alpha 测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 50, "text": "验收测试，开发者视角。\n\n要么开发者内部进行测试，要么给潜在的终端用户进行测试，不对外开放测试渠道。"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1471", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch11 验收测试（黑） Acceptance/Alpha 测试 和 Beta 测试/Beta 测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 188, "text": "验收测试，在客户或者终端用户的视角进行测试。一般来说会对外开放测试渠道。\n\nIt is performed after alpha testing and in the real-world environment without the presence or control of developers. / 它是在公司内测后在真实环境中执行的，没有开发人员的存在或控制。"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1472", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "Ch11 验收测试（黑） Acceptance/Alpha 测试 和 Beta 测试/对比表格", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 291, "text": "Alpha TestingBeta Testing基本概念方面客户确认的第一步客户确认的第二步开发者视角：测试环境真实的市场环境活动可被控制活动不可被控制Alpha ReleaseBeta ReleaseIssues / Bugs 直接在被定义的工具上打日志，被开发者高优先级地修复Issues / Bugs 从真实的用户中以建议或者反馈的形式提出，它们将会被考虑成为未来发布版本的改进和优化参与人员方面技术专家、掌握好的领域知识专业测试人员、项目主要专家目标受众终端用户测试时长方面执行了许多测试周期只执行了 1 或 2 个测试周期奖励方面对参与者没有特别的奖励参与者有特别的奖励"}
{"id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb::1473", "page_id": "docx::Hf4VwXMvjirYXOkFoQbcNpeQnnb", "title": "ST 讲义（四）V 模型四大测试", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST 讲义（四）V 模型四大测试", "section": "🌟 必考：软件测试四大阶段的对比", "url": "https://a1npn29y3xu.feishu.cn/wiki/Hf4VwXMvjirYXOkFoQbcNpeQnnb", "source_type": "docx", "n_chars": 482, "text": "\n\n| | 单元测试 | 集成测试 | 系统测试 | 验收测试 |\n|-|-|-|-|-|\n| 测试对象 | 软件单元（函数、类、组件、模块） | 模块之间的接口，比如说参数传递 | 整一个系统，包括硬件和软件 | 整一个系统，包括硬件和软件 |\n| 测试基础 | 细致的软件设计 | 软件架构设计 | 软件需求确认 | 需求确认，协议，验收协议 |\n| 测试人员 | 开发人员或白盒测试工程师 | 开发人员和一起工作的测试人员 | 主要是专业测试人员 | 用户主导，开发者和测试人员共同工作 |\n| 测试方法 | 白 1 黑 2 | 黑 1 白 2 | 黑 | 黑 |\n| 测试数据 | 真实数据一般不使用 | 真实数据**一般不使用** | **尽可能使用**或者模拟真实业务数据 | **尽可能使用**或者模拟真实业务数据 |\n\nUse or simulate real business data **whenever possible**"}
{"id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe::1474", "page_id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe", "title": "上半场", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/最后一夜/上半场", "section": "上半场", "url": "https://a1npn29y3xu.feishu.cn/wiki/Bt1xwPFANiMCcekSXT2cjpFEnpe", "source_type": "docx", "n_chars": 102, "text": "上半场\n\n施工完毕前推荐看 "}
{"id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe::1475", "page_id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe", "title": "上半场", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/最后一夜/上半场", "section": "Chapter 1-3/什么是系统方法", "url": "https://a1npn29y3xu.feishu.cn/wiki/Bt1xwPFANiMCcekSXT2cjpFEnpe", "source_type": "docx", "n_chars": 253, "text": "- **系统方法**(systems approach) ,用于描述一种在解决复杂问题时所需的整体性的和分析性的方法。\n- **系统哲学**(systems philosophy) 是将事情作为系统考虑的整体模型。\n- **系统分析**(systems analysis) 是一种解决问题的方法,该方法需要定义系统的范围,将其分解为各个组成部分,然后识别和估计其问题、机会、约束和需求。\n- **系统管理**(systems management) 解决与系统开发、维护和变更相关的业务、技术和组织的问题。"}
{"id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe::1476", "page_id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe", "title": "上半场", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/最后一夜/上半场", "section": "Chapter 1-3/三种常见的组织架构", "url": "https://a1npn29y3xu.feishu.cn/wiki/Bt1xwPFANiMCcekSXT2cjpFEnpe", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe::1477", "page_id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe", "title": "上半场", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/最后一夜/上半场", "section": "Chapter 1-3/五个过程组", "url": "https://a1npn29y3xu.feishu.cn/wiki/Bt1xwPFANiMCcekSXT2cjpFEnpe", "source_type": "docx", "n_chars": 446, "text": "**过程**(process) 是指朝向特定结果的一系列行动。 **项目管理过程组**(project management process groups) 包括启动活动、计划活动、执行活动、监控活动和以收尾活动。\n\n- 启动过程 (initiating processes): 识别所有项目干系人,并制定项目章程\n- 计划过程 (planning processes): 指导项目的执行\n- 执行过程 (executing processes): 协调、执行\n- 监控过程 (monitoring and controlling processes): 一个针对项目目标来衡量进展情况、监测计划的偏离情况,并采取纠正措施使项目进展与计划相匹配的过程\n- 收尾过程 (closing processes): 获得干系人和客户对最终产品和服务的验收,并使得项目或项目阶段有序地结束\n\n"}
{"id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe::1478", "page_id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe", "title": "上半场", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/最后一夜/上半场", "section": "Chapter 4/NPV 净值计算", "url": "https://a1npn29y3xu.feishu.cn/wiki/Bt1xwPFANiMCcekSXT2cjpFEnpe", "source_type": "docx", "n_chars": 122, "text": "> 算表格\n\n$$NPV = \\Sigma_{t=0..n}\\frac{A_t}{(1+r)^t}$$\n\n$A_t $ = cash flow\n\n r = discount rate\n\nNPV > 0 stand for 投资价值 > 投资成本"}
{"id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe::1479", "page_id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe", "title": "上半场", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/最后一夜/上半场", "section": "Chapter 4/ROI Return on Investment", "url": "https://a1npn29y3xu.feishu.cn/wiki/Bt1xwPFANiMCcekSXT2cjpFEnpe", "source_type": "docx", "n_chars": 126, "text": "$$ROI = \\frac{total\\_discounted\\_benefits - total\\_discounted\\_costs}{total\\_discounted\\_costs} \\times 100%$$\n\nROI > 1 => 值得投资"}
{"id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe::1480", "page_id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe", "title": "上半场", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/最后一夜/上半场", "section": "Chapter 5 **范围管理 scope management**/主过程（六个）", "url": "https://a1npn29y3xu.feishu.cn/wiki/Bt1xwPFANiMCcekSXT2cjpFEnpe", "source_type": "docx", "n_chars": 660, "text": "- 制定范围管理计划 **Planning scope:**\n\ndetermining how the project’s scope and requirements will be managed\n\n- 收集需求 **Collecting requirements:**\n\ndefining and documenting the features and functions of the products produced during the project as well as the processes used for creating them\n\n- 定义范围 **Defining scope:**\n\nreviewing the project charter, requirements documents, and organizational process assets to create a scope statement\n\n- 创建工作分解结构 **Creating the WBS:**\n\nsubdividing the major project deliverables into smaller, more manageable components\n\n- 验证范围 **Validating scope**:\n\nformalizing acceptance of the project deliverables\n\n- 控制范围 **Controlling scope:**"}
{"id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe::1481", "page_id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe", "title": "上半场", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/最后一夜/上半场", "section": "Chapter 5 **范围管理 scope management**/主过程（六个）", "url": "https://a1npn29y3xu.feishu.cn/wiki/Bt1xwPFANiMCcekSXT2cjpFEnpe", "source_type": "docx", "n_chars": 171, "text": "dating scope**:\n\nformalizing acceptance of the project deliverables\n\n- 控制范围 **Controlling scope:**\n\ncontrolling changes to project scope throughout the life of the project"}
{"id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe::1482", "page_id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe", "title": "上半场", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/最后一夜/上半场", "section": "Chapter 5 **范围管理 scope management**/WBS Work Breakdown Structure/Definition", "url": "https://a1npn29y3xu.feishu.cn/wiki/Bt1xwPFANiMCcekSXT2cjpFEnpe", "source_type": "docx", "n_chars": 417, "text": "A **WBS** is a deliverable-oriented grouping of the work involved in a project that defines the total scope of the project.\n\n**工作分解结构**（WBS）是 对项目所涉及的工作 面向交付成果**分组** 的产物，定义了项目的**全部范围**。\n\n> ~~让我们说中文，有时候翻译真的很想报警~~\n\n> WBS is a foundation document that provides the basis for planning and managing project schedules, costs, resources, and changes.\n>\n> WBS 是项目管理中的基础文档，因为它提供了计划和管理项目进度、成本、资源和变更的基础。\n>\n> 并且 WBS 也是 Gantte 图的基础"}
{"id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe::1483", "page_id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe", "title": "上半场", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/最后一夜/上半场", "section": "Chapter 5 **范围管理 scope management**/WBS Work Breakdown Structure/Decomposition", "url": "https://a1npn29y3xu.feishu.cn/wiki/Bt1xwPFANiMCcekSXT2cjpFEnpe", "source_type": "docx", "n_chars": 115, "text": "**Decomposition** is subdividing project deliverables into smaller pieces.\n\n**分解**（Decomposition）是把项目可交付成果划分为更小的部分。"}
{"id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe::1484", "page_id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe", "title": "上半场", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/最后一夜/上半场", "section": "Chapter 5 **范围管理 scope management**/WBS Work Breakdown Structure/Work Package", "url": "https://a1npn29y3xu.feishu.cn/wiki/Bt1xwPFANiMCcekSXT2cjpFEnpe", "source_type": "docx", "n_chars": 101, "text": "A **work package** is a task at the lowest level of the WBS.\n\n一个**工作包**（work package）即为 WBS 最底层的一项任务。"}
{"id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe::1485", "page_id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe", "title": "上半场", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/最后一夜/上半场", "section": "Chapter 5 **范围管理 scope management**/WBS Work Breakdown Structure/Scope Baseline", "url": "https://a1npn29y3xu.feishu.cn/wiki/Bt1xwPFANiMCcekSXT2cjpFEnpe", "source_type": "docx", "n_chars": 242, "text": "The **scope baseline** includes the approved project scope statement and its associated WBS and WBS dictionary.\n\n**范围目标计划**（scope baseline）包括已批准的项目范围声明及其关联的 WBS 和 WBS 字典。\n\n> 三层结构，从粗略到精细\n\n"}
{"id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe::1486", "page_id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe", "title": "上半场", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/最后一夜/上半场", "section": "Chapter 5 **范围管理 scope management**/WBS Work Breakdown Structure/WBS dictionary WBS 字典", "url": "https://a1npn29y3xu.feishu.cn/wiki/Bt1xwPFANiMCcekSXT2cjpFEnpe", "source_type": "docx", "n_chars": 121, "text": "A **WBS dictionary** is a document that describes detailed information about each WBS item.\n\nWBS 字典是一个描述 WBS 每项条目详细信息的文件。"}
{"id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe::1487", "page_id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe", "title": "上半场", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/最后一夜/上半场", "section": "Chapter 6 Time", "url": "https://a1npn29y3xu.feishu.cn/wiki/Bt1xwPFANiMCcekSXT2cjpFEnpe", "source_type": "docx", "n_chars": 97, "text": "- Project schedule management\n\n - 概念（？）\n - **阶段&产出**\n- Sequence Activity\n\n - ADM (AOA)\n - PDM"}
{"id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe::1488", "page_id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe", "title": "上半场", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/最后一夜/上半场", "section": "Chapter 6 Time/Importance of Project schedule management/Summary", "url": "https://a1npn29y3xu.feishu.cn/wiki/Bt1xwPFANiMCcekSXT2cjpFEnpe", "source_type": "docx", "n_chars": 646, "text": "Managers often cite delivering projects on time as one of their biggest challenges.\n\nTime has the least amount of flexibility; it passes no matter what happens on a project.\n\nSchedule issues are the main reason for conflicts on projects, especially during the second half of projects.\n\n管理者经常将按时交付项目作为他们面临的最大挑战之一。\n\n时间的灵活性最小;无论项目发生什么，它都会通过。\n\n进度问题是项目冲突的主要原因，尤其是在项目的后半部分。\n\n**Individual Work Styles and Cultural Differences Cause Schedule Conflicts**\n\nOne dimension of the Meyers-Briggs Type Indicator focuses on peoples’ attitudes toward structure and deadline\n\nSome people prefer to follow schedules and meet deadlines while others do not (J vs. P)"}
{"id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe::1489", "page_id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe", "title": "上半场", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/最后一夜/上半场", "section": "Chapter 6 Time/Importance of Project schedule management/Summary", "url": "https://a1npn29y3xu.feishu.cn/wiki/Bt1xwPFANiMCcekSXT2cjpFEnpe", "source_type": "docx", "n_chars": 185, "text": "deadline\n\nSome people prefer to follow schedules and meet deadlines while others do not (J vs. P)\n\nDifferent cultures and even entire countries have different attitudes about schedules"}
{"id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe::1490", "page_id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe", "title": "上半场", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/最后一夜/上半场", "section": "Chapter 6 Time/Importance of Project schedule management/Process & Outputs", "url": "https://a1npn29y3xu.feishu.cn/wiki/Bt1xwPFANiMCcekSXT2cjpFEnpe", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe::1491", "page_id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe", "title": "上半场", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/最后一夜/上半场", "section": "Chapter 6 Time/Sequence Activity", "url": "https://a1npn29y3xu.feishu.cn/wiki/Bt1xwPFANiMCcekSXT2cjpFEnpe", "source_type": "docx", "n_chars": 196, "text": "见 \n\n这里之后详情请看 "}
{"id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe::1492", "page_id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe", "title": "上半场", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/最后一夜/上半场", "section": "Chapter 7 Cost/Summary", "url": "https://a1npn29y3xu.feishu.cn/wiki/Bt1xwPFANiMCcekSXT2cjpFEnpe", "source_type": "docx", "n_chars": 238, "text": "- Budget\n- EVM \n\n - ETC Estimation to complete: ETC = EAC - AC\n - TCPI To-complete performance index: $TCPI = \\frac{BAC - EV}{BAC - AC}$"}
{"id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe::1493", "page_id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe", "title": "上半场", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/最后一夜/上半场", "section": "Chapter 8 Quality", "url": "https://a1npn29y3xu.feishu.cn/wiki/Bt1xwPFANiMCcekSXT2cjpFEnpe", "source_type": "docx", "n_chars": 270, "text": "- What is 项目质量管理\n- Main process\n- 作了解\n\n - Cause-and-effect Diagram\n - Control chart\n - Check Sheet?\n - Scatter Diagram\n- Six Sigma \n- Testing\n\n - Types of testing"}
{"id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe::1494", "page_id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe", "title": "上半场", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/最后一夜/上半场", "section": "Chapter 10 Human Resource 人力资源管理/4 Main Process", "url": "https://a1npn29y3xu.feishu.cn/wiki/Bt1xwPFANiMCcekSXT2cjpFEnpe", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe::1495", "page_id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe", "title": "上半场", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/最后一夜/上半场", "section": "Chapter 10 Human Resource 人力资源管理/激励理论", "url": "https://a1npn29y3xu.feishu.cn/wiki/Bt1xwPFANiMCcekSXT2cjpFEnpe", "source_type": "docx", "n_chars": 103, "text": ""}
{"id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe::1496", "page_id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe", "title": "上半场", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/最后一夜/上半场", "section": "Chapter 10 Human Resource 人力资源管理/Tuckman model", "url": "https://a1npn29y3xu.feishu.cn/wiki/Bt1xwPFANiMCcekSXT2cjpFEnpe", "source_type": "docx", "n_chars": 60, "text": "**塔克曼模型描述的团队建设的5个阶段？**\n\n**形成阶段 - 震荡阶段 - 规范阶段 - 执行阶段 - 终止阶段**"}
{"id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe::1497", "page_id": "docx::Bt1xwPFANiMCcekSXT2cjpFEnpe", "title": "上半场", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/最后一夜/上半场", "section": "Chapter 11 Risk", "url": "https://a1npn29y3xu.feishu.cn/wiki/Bt1xwPFANiMCcekSXT2cjpFEnpe", "source_type": "docx", "n_chars": 92, "text": "\n\n- 评估项目风险 蒙特卡洛方法（won't need to draw）"}
{"id": "docx::JNQiwqsLniMsbnkoS8ac05ITnQg::1498", "page_id": "docx::JNQiwqsLniMsbnkoS8ac05ITnQg", "title": "下半场", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/最后一夜/下半场", "section": "第七章 成本管理/主要过程/计划", "url": "https://a1npn29y3xu.feishu.cn/wiki/JNQiwqsLniMsbnkoS8ac05ITnQg", "source_type": "docx", "n_chars": 89, "text": "过程：计划成本管理\n\n输出：成本管理计划\n\n过程：成本估算\n\n输出：活动的成本估算、估算的基础以及更新的项目文档\n\n过程：确定预算\n\n输出：成本基线、项目资金需求和更新的项目文档"}
{"id": "docx::JNQiwqsLniMsbnkoS8ac05ITnQg::1499", "page_id": "docx::JNQiwqsLniMsbnkoS8ac05ITnQg", "title": "下半场", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/最后一夜/下半场", "section": "第七章 成本管理/主要过程/监测和控制", "url": "https://a1npn29y3xu.feishu.cn/wiki/JNQiwqsLniMsbnkoS8ac05ITnQg", "source_type": "docx", "n_chars": 56, "text": "过程：成本控制\n\n输出：工作绩效信息、成本预测、请求变更、更新的项目管理计划、更新的项目文档、更新的组织过程资产"}
{"id": "docx::JNQiwqsLniMsbnkoS8ac05ITnQg::1500", "page_id": "docx::JNQiwqsLniMsbnkoS8ac05ITnQg", "title": "下半场", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/最后一夜/下半场", "section": "第七章 成本管理/EV 计算一图流", "url": "https://a1npn29y3xu.feishu.cn/wiki/JNQiwqsLniMsbnkoS8ac05ITnQg", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::JNQiwqsLniMsbnkoS8ac05ITnQg::1501", "page_id": "docx::JNQiwqsLniMsbnkoS8ac05ITnQg", "title": "下半场", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/最后一夜/下半场", "section": "第八章 质量管理/主要过程/计划", "url": "https://a1npn29y3xu.feishu.cn/wiki/JNQiwqsLniMsbnkoS8ac05ITnQg", "source_type": "docx", "n_chars": 45, "text": "过程：计划质量管理\n\n输出：质量管理计划、过程改进计划，质量度量，质量检查表和项目文档更新"}
{"id": "docx::JNQiwqsLniMsbnkoS8ac05ITnQg::1502", "page_id": "docx::JNQiwqsLniMsbnkoS8ac05ITnQg", "title": "下半场", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/最后一夜/下半场", "section": "第八章 质量管理/主要过程/执行", "url": "https://a1npn29y3xu.feishu.cn/wiki/JNQiwqsLniMsbnkoS8ac05ITnQg", "source_type": "docx", "n_chars": 43, "text": "过程：实施质量保证\n\n输出：变更请求，项目管理计划更新，项目文档更新和组织过程资产更新"}
{"id": "docx::JNQiwqsLniMsbnkoS8ac05ITnQg::1503", "page_id": "docx::JNQiwqsLniMsbnkoS8ac05ITnQg", "title": "下半场", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/最后一夜/下半场", "section": "第八章 质量管理/主要过程/监控", "url": "https://a1npn29y3xu.feishu.cn/wiki/JNQiwqsLniMsbnkoS8ac05ITnQg", "source_type": "docx", "n_chars": 70, "text": "过程：控制质量\n\n输出：质量控制度量，有效地变更，有效的可交付成果，工作绩效信息，变更请求，项目管理计划更新，项目文档更新和组织过程资产更新"}
{"id": "docx::JNQiwqsLniMsbnkoS8ac05ITnQg::1504", "page_id": "docx::JNQiwqsLniMsbnkoS8ac05ITnQg", "title": "下半场", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/最后一夜/下半场", "section": "第八章 质量管理/因果图", "url": "https://a1npn29y3xu.feishu.cn/wiki/JNQiwqsLniMsbnkoS8ac05ITnQg", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::JNQiwqsLniMsbnkoS8ac05ITnQg::1505", "page_id": "docx::JNQiwqsLniMsbnkoS8ac05ITnQg", "title": "下半场", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/最后一夜/下半场", "section": "第八章 质量管理/六西格玛", "url": "https://a1npn29y3xu.feishu.cn/wiki/JNQiwqsLniMsbnkoS8ac05ITnQg", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::JNQiwqsLniMsbnkoS8ac05ITnQg::1506", "page_id": "docx::JNQiwqsLniMsbnkoS8ac05ITnQg", "title": "下半场", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/最后一夜/下半场", "section": "第八章 质量管理/测试的类型", "url": "https://a1npn29y3xu.feishu.cn/wiki/JNQiwqsLniMsbnkoS8ac05ITnQg", "source_type": "docx", "n_chars": 140, "text": "单元测试 —— 对每一个独立组件进行测试，以确保其尽可能无缺陷\n\n集成测试 —— 在单元测试和系统测试之间进行，用来测试功能性的成组的组件，以确保整个系统的各子集模块协同运行\n\n系统测试 —— 将整个系统作为一个整体进行测试\n\n用户验收测试 —— 在系统交付验收之前由最终用户执行"}
{"id": "docx::JNQiwqsLniMsbnkoS8ac05ITnQg::1507", "page_id": "docx::JNQiwqsLniMsbnkoS8ac05ITnQg", "title": "下半场", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/最后一夜/下半场", "section": "第九章 人力资源管理/主要过程/执行", "url": "https://a1npn29y3xu.feishu.cn/wiki/JNQiwqsLniMsbnkoS8ac05ITnQg", "source_type": "docx", "n_chars": 120, "text": "方法：组建项目团队\n\n输出：项目人员分配，资源日历，项目管理计划更新\n\n方法：建设项目团队\n\n输出：团队绩效评估，企业环境因素更新\n\n过程：管理项目团队\n\n输出：请求变更、项目管理计划更新、项目文档更新、企业环境因素、更新和组织过程资产更新"}
{"id": "docx::JNQiwqsLniMsbnkoS8ac05ITnQg::1508", "page_id": "docx::JNQiwqsLniMsbnkoS8ac05ITnQg", "title": "下半场", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/最后一夜/下半场", "section": "第九章 人力资源管理/需求理论", "url": "https://a1npn29y3xu.feishu.cn/wiki/JNQiwqsLniMsbnkoS8ac05ITnQg", "source_type": "docx", "n_chars": 96, "text": "1. 生理需求\n2. 安全需求\n3. 社交需求\n4. 尊重需求\n5. 自我实现\n\n"}
{"id": "docx::JNQiwqsLniMsbnkoS8ac05ITnQg::1509", "page_id": "docx::JNQiwqsLniMsbnkoS8ac05ITnQg", "title": "下半场", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/最后一夜/下半场", "section": "第九章 人力资源管理/塔克曼模型", "url": "https://a1npn29y3xu.feishu.cn/wiki/JNQiwqsLniMsbnkoS8ac05ITnQg", "source_type": "docx", "n_chars": 36, "text": "形成阶段 —— 震荡阶段 —— 规范阶段 —— 执行阶段 —— 终止阶段"}
{"id": "docx::JNQiwqsLniMsbnkoS8ac05ITnQg::1510", "page_id": "docx::JNQiwqsLniMsbnkoS8ac05ITnQg", "title": "下半场", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/最后一夜/下半场", "section": "第十一章 风险管理/三种对待风险的态度", "url": "https://a1npn29y3xu.feishu.cn/wiki/JNQiwqsLniMsbnkoS8ac05ITnQg", "source_type": "docx", "n_chars": 74, "text": "风险厌恶型、风险中性型、风险喜好型\n\n"}
{"id": "docx::MfX5w3tyGipMlekeMdac1ZojnXe::1511", "page_id": "docx::MfX5w3tyGipMlekeMdac1ZojnXe", "title": "专业术语表（ASCII 序）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/专业术语表（ASCII 序）", "section": "专业术语表（ASCII 序）", "url": "https://a1npn29y3xu.feishu.cn/wiki/MfX5w3tyGipMlekeMdac1ZojnXe", "source_type": "docx", "n_chars": 682, "text": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::MfX5w3tyGipMlekeMdac1ZojnXe::1512", "page_id": "docx::MfX5w3tyGipMlekeMdac1ZojnXe", "title": "专业术语表（ASCII 序）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/专业术语表（ASCII 序）", "section": "专业术语表（ASCII 序）", "url": "https://a1npn29y3xu.feishu.cn/wiki/MfX5w3tyGipMlekeMdac1ZojnXe", "source_type": "docx", "n_chars": 212, "text": "ishu.cn/file/KYqJbbQ8hoRViYxmdg9chOQTndb)\n\n\n\n\n\n"}
{"id": "docx::Ml1Cwzt7ciUmdgkjlkNcCRy3nib::1513", "page_id": "docx::Ml1Cwzt7ciUmdgkjlkNcCRy3nib", "title": "专项突破：概念默写题（章节划分）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：概念默写题（章节划分）", "section": "Main Key Terms", "url": "https://a1npn29y3xu.feishu.cn/wiki/Ml1Cwzt7ciUmdgkjlkNcCRy3nib", "source_type": "docx", "n_chars": 587, "text": "**Part One： IT Project Management**\n\n1. **Introduction To Project Management**\n\n project, project management, project attributes, project manager (hard and soft skills), triple constraint, PMI, PMO, PMP\n\n1. **The Project Management and Information Technology Context**\n\nDeliverable, project life cycle, systems development life cycle (SDLC), Organizational Structures (Functional, Project, and Matrix)\n\n1. **Project Management Process Groups: A Case Study**\n\n5 process groups, process groups and KAs mapping, remember all processes in each KA\n\n1. **Project Integration Management**"}
{"id": "docx::Ml1Cwzt7ciUmdgkjlkNcCRy3nib::1514", "page_id": "docx::Ml1Cwzt7ciUmdgkjlkNcCRy3nib", "title": "专项突破：概念默写题（章节划分）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：概念默写题（章节划分）", "section": "Main Key Terms", "url": "https://a1npn29y3xu.feishu.cn/wiki/Ml1Cwzt7ciUmdgkjlkNcCRy3nib", "source_type": "docx", "n_chars": 592, "text": "s groups and KAs mapping, remember all processes in each KA\n\n1. **Project Integration Management**\n\nproject integration management processes, project charter, develop project management plan, NPV and Return Of Investment（ROI）calculate, Weighted Scoring Model, Performing Integrated Change Control process, change control board (CCB)\n\n1. **Project Scope Management**\n\nproject scope management processes, scope planning, scope control, scope definition, scope statement, work breakdown structure(WBS), WBS dictionary, scope statement, WBS package, scope baseline\n\n1. **Project Time Management**"}
{"id": "docx::Ml1Cwzt7ciUmdgkjlkNcCRy3nib::1515", "page_id": "docx::Ml1Cwzt7ciUmdgkjlkNcCRy3nib", "title": "专项突破：概念默写题（章节划分）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：概念默写题（章节划分）", "section": "Main Key Terms", "url": "https://a1npn29y3xu.feishu.cn/wiki/Ml1Cwzt7ciUmdgkjlkNcCRy3nib", "source_type": "docx", "n_chars": 628, "text": "WBS), WBS dictionary, scope statement, WBS package, scope baseline\n\n1. **Project Time Management**\n\nProject time management processes, Activity definition, activity sequencing (FS,SF,FF,SS), activity resource estimating, activity duration estimating, schedule development, milestone, Gantt chart, critical path analysis, Critical chain scheduling, Schedule network analysis: ES, EF, LS, LF, TF; PERT, network diagram: AOA (ADM), AON network diagram (PDM, Precedence Diagramming Method); types of dependencies between activities, time baseline, shorten a project schedule: Crashing, Fast tracking,\n\n1. **Project Cost Management**"}
{"id": "docx::Ml1Cwzt7ciUmdgkjlkNcCRy3nib::1516", "page_id": "docx::Ml1Cwzt7ciUmdgkjlkNcCRy3nib", "title": "专项突破：概念默写题（章节划分）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：概念默写题（章节划分）", "section": "Main Key Terms", "url": "https://a1npn29y3xu.feishu.cn/wiki/Ml1Cwzt7ciUmdgkjlkNcCRy3nib", "source_type": "docx", "n_chars": 633, "text": "ime baseline, shorten a project schedule: Crashing, Fast tracking,\n\n1. **Project Cost Management**\n\nproject cost management processes, internal rate of return (IRR), payback period , cost estimating, cost budgeting, sunk cost, Reserves(Contingency reserves, Management reserves), Intangible costs , Tangible costs, Direct costs , Indirect costs, cost baseline\n\n1. **Project Quality Management**\n\nproject quality management processes, quality assurance, seven run rule , Six Sigma rule , six 9s of quality rule , 20/80 Pareto analysis, fishbone diagrams, conformance cost, Nonconformance cost\n\n1. **Project Human resource Management**"}
{"id": "docx::Ml1Cwzt7ciUmdgkjlkNcCRy3nib::1517", "page_id": "docx::Ml1Cwzt7ciUmdgkjlkNcCRy3nib", "title": "专项突破：概念默写题（章节划分）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：概念默写题（章节划分）", "section": "Main Key Terms", "url": "https://a1npn29y3xu.feishu.cn/wiki/Ml1Cwzt7ciUmdgkjlkNcCRy3nib", "source_type": "docx", "n_chars": 515, "text": "fishbone diagrams, conformance cost, Nonconformance cost\n\n1. **Project Human resource Management**\n\nProject human resource management processes, Acquiring the project team, Developing the project team, Managing the project team, Maslow’s Hierarchy of Needs, Resource Leveling technique , conflict Handling modes\n\n1. **Project Communications Management**\n\nProject communications management processes, Performance Reporting, Communications channels, Effective face-to-face interactions\n\n1. **Project Risk Management**"}
{"id": "docx::Ml1Cwzt7ciUmdgkjlkNcCRy3nib::1518", "page_id": "docx::Ml1Cwzt7ciUmdgkjlkNcCRy3nib", "title": "专项突破：概念默写题（章节划分）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：概念默写题（章节划分）", "section": "Main Key Terms", "url": "https://a1npn29y3xu.feishu.cn/wiki/Ml1Cwzt7ciUmdgkjlkNcCRy3nib", "source_type": "docx", "n_chars": 683, "text": "ting, Communications channels, Effective face-to-face interactions\n\n1. **Project Risk Management**\n\nProject risk management processes, Negative risk, Positive risk, risk utility, risk-averse, Watch list , Decision tree and EMV, Monte Carlo , Contingency plans, Risk identification, Risk register, Top Ten Risk Item Tracking , risk response\n\n1. **Project Procurement management**\n\nProject Procurement management processes, Planning purchases and acquisitions, Request for Proposal (RFP), Requests for Quotes (RFQ), Conducting contracting (5 steps), Controlling the contract, Closing the contract, Contract Statement of Work (SOW), Types of contracts: CPIF, CPFF, CPAF, CPPC, FFP, FPIF"}
{"id": "docx::Ml1Cwzt7ciUmdgkjlkNcCRy3nib::1519", "page_id": "docx::Ml1Cwzt7ciUmdgkjlkNcCRy3nib", "title": "专项突破：概念默写题（章节划分）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：概念默写题（章节划分）", "section": "Main Key Terms", "url": "https://a1npn29y3xu.feishu.cn/wiki/Ml1Cwzt7ciUmdgkjlkNcCRy3nib", "source_type": "docx", "n_chars": 271, "text": "contract, Contract Statement of Work (SOW), Types of contracts: CPIF, CPFF, CPAF, CPPC, FFP, FPIF\n\n1. **Project Stakeholder Management**\n\nProject stakeholder management processes, Identifying stakeholders, Classifying Stakeholders, Interpersonal Skills of Project Manager"}
{"id": "docx::Ml1Cwzt7ciUmdgkjlkNcCRy3nib::1520", "page_id": "docx::Ml1Cwzt7ciUmdgkjlkNcCRy3nib", "title": "专项突破：概念默写题（章节划分）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：概念默写题（章节划分）", "section": "注：中文第七版术语表", "url": "https://a1npn29y3xu.feishu.cn/wiki/Ml1Cwzt7ciUmdgkjlkNcCRy3nib", "source_type": "docx", "n_chars": 682, "text": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::Ml1Cwzt7ciUmdgkjlkNcCRy3nib::1521", "page_id": "docx::Ml1Cwzt7ciUmdgkjlkNcCRy3nib", "title": "专项突破：概念默写题（章节划分）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：概念默写题（章节划分）", "section": "注：中文第七版术语表", "url": "https://a1npn29y3xu.feishu.cn/wiki/Ml1Cwzt7ciUmdgkjlkNcCRy3nib", "source_type": "docx", "n_chars": 383, "text": "ishu.cn/file/XoTXbzrzDodXUTxnLIScULqVnOh)\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::JdKswAFmnir4BUk5h3JcBQ2JnPg::1522", "page_id": "docx::JdKswAFmnir4BUk5h3JcBQ2JnPg", "title": "专项突破：简答题", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：简答题", "section": "专项突破：简答题", "url": "https://a1npn29y3xu.feishu.cn/wiki/JdKswAFmnir4BUk5h3JcBQ2JnPg", "source_type": "docx", "n_chars": 511, "text": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::TyeMw0aRViXfuMkPIZncZNLmnqh::1523", "page_id": "docx::TyeMw0aRViXfuMkPIZncZNLmnqh", "title": "专项突破：计算题", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：计算题", "section": "手写笔记", "url": "https://a1npn29y3xu.feishu.cn/wiki/TyeMw0aRViXfuMkPIZncZNLmnqh", "source_type": "docx", "n_chars": 226, "text": "\n\n\n\n\n\n"}
{"id": "docx::TyeMw0aRViXfuMkPIZncZNLmnqh::1524", "page_id": "docx::TyeMw0aRViXfuMkPIZncZNLmnqh", "title": "专项突破：计算题", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：计算题", "section": "第四章课后习题", "url": "https://a1npn29y3xu.feishu.cn/wiki/TyeMw0aRViXfuMkPIZncZNLmnqh", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::TyeMw0aRViXfuMkPIZncZNLmnqh::1525", "page_id": "docx::TyeMw0aRViXfuMkPIZncZNLmnqh", "title": "专项突破：计算题", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：计算题", "section": "第六章课后习题", "url": "https://a1npn29y3xu.feishu.cn/wiki/TyeMw0aRViXfuMkPIZncZNLmnqh", "source_type": "docx", "n_chars": 169, "text": "\n\n\n\n"}
{"id": "docx::TyeMw0aRViXfuMkPIZncZNLmnqh::1526", "page_id": "docx::TyeMw0aRViXfuMkPIZncZNLmnqh", "title": "专项突破：计算题", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：计算题", "section": "第七章课后习题", "url": "https://a1npn29y3xu.feishu.cn/wiki/TyeMw0aRViXfuMkPIZncZNLmnqh", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::TyeMw0aRViXfuMkPIZncZNLmnqh::1527", "page_id": "docx::TyeMw0aRViXfuMkPIZncZNLmnqh", "title": "专项突破：计算题", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：计算题", "section": "第十一章课后习题", "url": "https://a1npn29y3xu.feishu.cn/wiki/TyeMw0aRViXfuMkPIZncZNLmnqh", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::AuKPwOQaei7pJ7kczCwcUaK9nVc::1528", "page_id": "docx::AuKPwOQaei7pJ7kczCwcUaK9nVc", "title": "专项突破：选择题（课本）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（课本）", "section": "专项突破：选择题（课本）", "url": "https://a1npn29y3xu.feishu.cn/wiki/AuKPwOQaei7pJ7kczCwcUaK9nVc", "source_type": "docx", "n_chars": 682, "text": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::AuKPwOQaei7pJ7kczCwcUaK9nVc::1529", "page_id": "docx::AuKPwOQaei7pJ7kczCwcUaK9nVc", "title": "专项突破：选择题（课本）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（课本）", "section": "专项突破：选择题（课本）", "url": "https://a1npn29y3xu.feishu.cn/wiki/AuKPwOQaei7pJ7kczCwcUaK9nVc", "source_type": "docx", "n_chars": 155, "text": "ishu.cn/file/CB4bbwnKyou2pTxohbjcFCYBnLe)\n\n\n\n"}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1530", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "题库 A ：官方的选择题参考材料/好题萃取", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 668, "text": "1. **What are the 4 stages of team development?**\n\n 1. **Forming, Storming, Norming, Performing.**\n2. **Which of the following is not normally an element of the Project Charter?**\n\n 1. The formal authorization to apply organizational resources to project activities.\n 2. **Work package descriptions.**\n 3. The business needs that the project was undertaken to address.\n 4. The product description or a reference to this document\n3. **Which process is applied to break down the project into smaller, more manageable elements?**\n\n 1. Scope Planning.\n 2. Activity Duration Estimating.\n 3. **Scope Definition.**\n 4. Scope Verification."}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1531", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "题库 A ：官方的选择题参考材料/好题萃取", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 650, "text": "g.\n 2. Activity Duration Estimating.\n 3. **Scope Definition.**\n 4. Scope Verification.\n4. **All of the following statements concerning project stakeholders are true except**\n\n 1. Differences between or among stakeholders should be resolved in favor of the customer.\n 2. Managing stakeholder expectations may be difficult because stakeholders often have very different objectives, that may come into conflict.\n 3. Project stakeholders may influence the course of the project and its results.\n 4. **Differences between or among stakeholders should be resolved in the most cost-efficient manner consistent with project objectives.**"}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1532", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "题库 A ：官方的选择题参考材料/好题萃取", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 588, "text": "eholders should be resolved in the most cost-efficient manner consistent with project objectives.**\n5. **Which of the following is the output of Source Selection?**\n\n 1. Proposals.\n 2. Evaluation criteria.\n 3. Contract negotiation.\n 4. **Contract.**\n6. **Where is the result node (outcome) shown on a typical Ishikawa or Fishbone diagram?**\n\n 1. Top.\n 2. Bottom.\n 3. **Right hand side.**\n 4. Center.\n7. **During execution of a project which is performed for a customer on a T&M (Time and Material) contract base a new project manager is taking over the assignment.**"}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1533", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "题库 A ：官方的选择题参考材料/好题萃取", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 643, "text": "on a T&M (Time and Material) contract base a new project manager is taking over the assignment.**\n\n[How T&M Contracts Work](https://www.netsuite.com/portal/resource/articles/accounting/time-materials-contract.shtml)\n\n**He discovers that two members assigned to the project have charged time without performing any work. Upon further investigation, he determined that this occurred because there were no other project assignments available for these people. The customer is unaware of these facts.**\n\n**What should the project manager do?**\n\n1. Try to find some productive work for these staff members in the project and leave them on the team."}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1534", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "题库 A ：官方的选择题参考材料/好题萃取", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 676, "text": "Try to find some productive work for these staff members in the project and leave them on the team.\n2. The best thing is to do nothing. The customer will not realize the problem anyway.\n3. Try to find a responsible person for the over-assignment who can be made accountable.\n4. **Take the two people off the team immediately and arrange for the refund of the excess charges to the customer.**\n\n1. **In the following network logic diagram, start dates are defined as early morning, finish dates are evening. If tasks are scheduled to begin at an early start date, what is true?**\n\n\n\n1. Activity B has a free float of 10 d."}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1535", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "题库 A ：官方的选择题参考材料/好题萃取", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 609, "text": "*\n\n\n\n1. Activity B has a free float of 10 d.\n2. Activity B has a total float of 10 d.\n3. Activity A has a free float of 10 d.\n4. Activity A has a total float of 10 d.\n\n\n\n1. **Tools and Techniques of Risk Response Planning include**\n\n 1. Identifying, quantitative and qualitative analysis, monitoring and control.\n 2. **Avoidance, transference, mitigation, acceptance.**\n 3. Identification, assessment of magnitude and probability, assessment of costs of response.\n 4. Risk management reviews"}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1536", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "题库 A ：官方的选择题参考材料/好题萃取", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 672, "text": "ssment of magnitude and probability, assessment of costs of response.\n 4. Risk management reviews\n2. **During a project the scope of product purchased on a cost reimbursable contract has increased. In the contract the contractor ‘s indirect costs are calculated as 20 % of the direct costs. What is most likely to be true?**\n\n 1. The contractor ‘s indirect costs will increase and the customer ‘s payment for them will increase, too.\n 2. The contractor ‘s indirect costs will increase but the customer ‘s payment for them not.\n 3. Neither the indirect costs nor the customer ‘s payment for indirect costs will increase."}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1537", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "题库 A ：官方的选择题参考材料/好题萃取", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 652, "text": "either the indirect costs nor the customer ‘s payment for indirect costs will increase.\n 4. **The contractor ‘s indirect costs will not increase but the customer ‘s payment for them will.**\n3. **What is active risk acceptance?**\n\n 1. **Creating contingency reserves in money and time.**\n 2. Developing a plan to minimize potential impact.\n 3. Developing a plan to minimize probability.\n 4. Making additional resources available\n4. **What is a quality audit?**\n\n 1. A team meeting dedicated to measuring and examinations.\n 2. A quality-based inspection of work results."}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1538", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "题库 A ：官方的选择题参考材料/好题萃取", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 554, "text": "dedicated to measuring and examinations.\n 2. A quality-based inspection of work results.\n 3. **A structured review of quality management activities.**\n 4. A meeting with the customer to identify quality requirements.\n5. **You are assigned as the project manager in a project with an aggressive schedule. During a recent meeting your team complained about the high pressure applied and the many hours of overwork time. What is the preferred solution to handle the problem?**\n\n 1. **Try to obtain additional budget and time.**"}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1539", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "题库 A ：官方的选择题参考材料/好题萃取", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 655, "text": "he preferred solution to handle the problem?**\n\n 1. **Try to obtain additional budget and time.**\n 2. Improve team communication and availability of high-quality data on risks. Use this information to enable you to make well-founded decisions earlier.\n 3. The problem might be the customer disturbing project rhythm. Keep him at a distance from the team.\n 4. Apply fast tracking to shorten project duration without additional work.\n6. **Which of the following statements is TRUE concerning Scope Definition?**\n\n 1. The Activity List is a principal output used for resource allocation and is an input to network diagramming."}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1540", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "题库 A ：官方的选择题参考材料/好题萃取", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 552, "text": "is a principal output used for resource allocation and is an input to network diagramming.\n 2. The Scope Statement is a principal output containing a narrative description of project work and deliverables.\n 3. The Project Charter is a principal output and authorizes the project.\n 4. **The Work Breakdown Structure is a principal output and should be broken down to a level which allows sufficient accuracy in planning.**\n7. **All the following statements regarding \"whistleblowing\" are true except**"}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1541", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "题库 A ：官方的选择题参考材料/好题萃取", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 623, "text": "anning.**\n7. **All the following statements regarding \"whistleblowing\" are true except**\n\n 1. It is the term used to define an employee’s decision to disclose information on unethical, immoral or illegal actions at work to an authority figure.\n 2. **An employee should always discuss the matter with people external to the company before following the \"chain of command\" and discuss it with the immediate superior.**\n 3. The consequences of whistleblowing are often extreme and include possible being branded as having bad judgment, firing, civil action and imprisonment."}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1542", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "题库 A ：官方的选择题参考材料/好题萃取", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 684, "text": "include possible being branded as having bad judgment, firing, civil action and imprisonment.\n 4. Carefully considered whistleblowing can lead to the end of unethical business practices.\n8. **Which of the following statements is not true?**\n\n 1. Attribute sampling is the process of assessing whether results conform to specifications or not.\n 2. Prevention means keeping errors out of the process\n 3. **Variables sampling means that the result is classified into one of the 3 categories: \"acceptable\" - \"acceptable after rework\" - \"rejected\".**\n 4. Inspection means keeping errors out of the hands of the customer."}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1543", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "题库 A ：官方的选择题参考材料/好题萃取", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 674, "text": "work\" - \"rejected\".**\n 4. Inspection means keeping errors out of the hands of the customer.\n9. **Why should assumptions be documented?**\n\n 1. Assumptions might prove to be wrong. Knowing which assumptions were incorrect allows baseline adjustments in case of project crisis.\n 2. **Assumption analysis is a valuable tool and technique of Risk Identification.**\n 3. Assumptions limit the project management team's options for decision making.\n 4. In case of schedule or budget overruns, the documentation of assumptions supports a clear assignment of responsibility.\n10. **All the following statements are true except**"}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1544", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "题库 A ：官方的选择题参考材料/好题萃取", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 679, "text": "s a clear assignment of responsibility.\n10. **All the following statements are true except**\n\n 1. It is axiomatic of quality management discipline that the benefits outweigh the costs.\n 2. **Quality should be tested and inspected into work results on a regular basis.**\n 3. The primary cost of meeting quality requirements is the expense associated with project quality management activities.\n 4. The primary benefit of meeting quality requirements is less rework, which means higher productivity, lower costs, and increased stakeholder satisfaction.\n\nThe statement that is not universally true among the options provided is:"}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1545", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "题库 A ：官方的选择题参考材料/好题萃取", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 700, "text": "akeholder satisfaction.\n\nThe statement that is not universally true among the options provided is:\n\nB. Quality should be tested and inspected into work results on a regular basis.\n\nThis statement is not necessarily true because the approach to quality management has evolved over time. While regular testing and inspection are important, they are not the only methods for ensuring quality. Modern quality management practices emphasize prevention and continuous improvement over inspection and testing. The philosophy of \"quality by design\" suggests that quality should be built into the product or process from the beginning, rather than relying solely on testing and inspection to find and fix defe"}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1546", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "题库 A ：官方的选择题参考材料/好题萃取", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 686, "text": "rocess from the beginning, rather than relying solely on testing and inspection to find and fix defects after they occur.\n\n这种说法不一定正确，因为质量管理的方法随着时间的推移而发展。虽然定期测试和检查很重要，但它们并不是确保质量的唯一方法。现代质量管理实践强调预防和持续改进，而不是检查和测试。“设计质量”的哲学建议从一开始就将质量融入产品或过程中，而不是仅仅依靠测试和检查来发现和修复缺陷。\n\n1. **Which of the following statements about diagramming methods is not TRUE**\n\n 1. PDM is the same as AON.\n 2. ADM is the same as AOA.\n 3. **GERT is the same as System Dynamics Model.**\n 4. GERT and System Dynamic Model are examples of conditional diagramming methods\n\n\n\n在项目管理中，资源池通常指的是：\n**人力资源池**：项目管理中，资源池是指可供项目使用的所有人力资源，包括团队成员、顾问和外部承包商。"}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1547", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "题库 A ：官方的选择题参考材料/好题萃取", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 611, "text": "e/DIUSb93kmo2haXxcWEZcozh4nEb)\n\n在项目管理中，资源池通常指的是：\n**人力资源池**：项目管理中，资源池是指可供项目使用的所有人力资源，包括团队成员、顾问和外部承包商。项目经理根据项目的需要，从资源池中分配人员到不同的任务。\n\n1. **The construction of a residential home will cost a certain amount per square foot of living space. This is an example of what type of estimating?**\n\n 1. Analogous estimating.\n 2. Bottom-up estimating.\n 3. Top-down estimating.\n 4. **Parametric modeling.**\n2. **Which of the following should not be reason for “rebase lining” in a project?**\n\n 1. Scope changes.\n 2. **Cost variances.**\n 3. Major schedule changes."}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1548", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "题库 A ：官方的选择题参考材料/好题萃取", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 677, "text": "roject?**\n\n 1. Scope changes.\n 2. **Cost variances.**\n 3. Major schedule changes.\n 4. New information indicating that the basis for the original project cost estimates was incorrect\n3. **Which of the following is generally not regarded to be a motivator according to Frederick Herzberg?**\n\n 1. **Working conditions and interpersonal relations.**\n 2. Responsibility for enlarged task.\n 3. Interest in the task.\n 4. Recognition for achievement.\n4. **Companies and institutions commonly hire leaders with**\n\n 1. A strong position in negotiating.\n 2. Experience in tricking business partners."}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1549", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "题库 A ：官方的选择题参考材料/好题萃取", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 602, "text": "1. A strong position in negotiating.\n 2. Experience in tricking business partners.\n 3. **Integrity and expertise.**\n 4. A strong link to local traditions.\n5. **Which of the following is true in regard to the Code of Accounts?**\n\n 1. It allows one to easily identify the breakdown level of the item in the resource structure.\n 2. It describes the coding structure used by the performing organization to report financial information in its general ledger.\n 3. **It is the collection of unique identifiers generally assigned to WBS items.**"}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1550", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "题库 A ：官方的选择题参考材料/好题萃取", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 687, "text": "ledger.\n 3. **It is the collection of unique identifiers generally assigned to WBS items.**\n 4. It defines ethical behavior in the project and the responsibilities to the customer and the profession.\n6. **Which is true regarding projects?A project is a temporary endeavor undertaken to create a unique product or service.**\n7. **Which of the following statements describes the relationship between project phases and the project life cycle?Collectively, the project phases are known as the project life cycle.**\n8. **A project management team discusses what scope means in a project. All of the following statements are true except**"}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1551", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "题库 A ：官方的选择题参考材料/好题萃取", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 646, "text": "nt team discusses what scope means in a project. All of the following statements are true except**\n\n 1. **The processes, tools, and techniques used by project scope management are mostly depending on the application area.**\n 2. Product scope includes features and functions that are to be included in a product or service.\n 3. Project scope includes the work that must be done in order to deliver a product with the specified features and functions.\n 4. Project Scope Management includes the processes required to ensure that the project includes all the work required and only the work required."}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1552", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "题库 A ：官方的选择题参考材料/好题萃取", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 617, "text": "quired to ensure that the project includes all the work required and only the work required.\n\n\n\n1. **Regarding Delphi Technique all of the following statements are true except**\n\n 1. It is a way to reach a consensus of experts.\n 2. Experts are identified but participate anonymously while a facilitator uses a questionnaire to solicit ideas.\n 3. **The experts are encouraged by the facilitator to make direct contact with each other during the assessment process to create a higher number of feedback loops.**"}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1553", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "题库 A ：官方的选择题参考材料/好题萃取", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 582, "text": "each other during the assessment process to create a higher number of feedback loops.**\n 4. The responses are submitted and are then circulated to the experts for further comment.\n2. **Network templates which contain only portions of a network are often referred to as**\n\n 1. Subnets or fragments\n 2. **Subprojects**\n 3. Programs\n 4. WBS items\n3. **In making an investment in a project, investors require compensation for which of the following?**\n\n 1. The risk-free rate of return plus a risk premium plus a premium for inflation."}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1554", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "题库 A ：官方的选择题参考材料/好题萃取", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 652, "text": "wing?**\n\n 1. The risk-free rate of return plus a risk premium plus a premium for inflation.\n 2. **Sacrifice of immediate use of cash for consumption or other investments, possibility of inflation and risk.**\n 3. Payback period in years x investment x (1 + discount rate) periods.\n 4. Inflation and depreciation.\n4. **A summary activity in a network logic diagram is often referred to as a**\n\n 1. **Hammock.**\n 2. Dangler.\n 3. Milestone.\n 4. Subtask.\n5. **When a project phase is finished, this is also known as a \\_\\_\\_\\_.**\n\n 1. **Kill point**\n 2. Milestone\n 3. Scope creep\n 4. Quality metrics"}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1555", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "题库 A ：官方的选择题参考材料/好题萃取", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 623, "text": "nown as a \\_\\_\\_\\_.**\n\n 1. **Kill point**\n 2. Milestone\n 3. Scope creep\n 4. Quality metrics\n6. **Ongoing project planning is also known as \\_\\_\\_\\_\\_\\_\\_\\_.**\n\n 1. **Rolling wave planning**\n 2. Buildup planning\n 3. Activity planning\n 4. Project processes\n7. **The process of establishing clear and achievable objectives, measuring their achievement, and adjusting performance in accordance with the results of the measurement is called:**\n\n 1. strategic planning.\n 2. alternative objectives inventory.\n 3. **management by objectives.**\n 4. contingency planning."}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1556", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "题库 A ：官方的选择题参考材料/好题萃取", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 658, "text": "e objectives inventory.\n 3. **management by objectives.**\n 4. contingency planning.\n8. **A fundamental tenet of modern quality management holds that quality is most likely to be achieved by:planning it into the project.**\n9. **Learning curve theory emphasizes that in producing many goods:**\n\n 1. cost decreases as production rates increase.\n 2. **average unit cost decreases as more units are produced.**\n10. **Rearranging resources so that constant resource levels are maintained is called:**\n\n 1. floating.\n 2. **leveling.**\n 3. restructuring.\n 4. crashing.\n11. **Theory X holds that:**"}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1557", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "题库 A ：官方的选择题参考材料/好题萃取", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 693, "text": "ing.\n 2. **leveling.**\n 3. restructuring.\n 4. crashing.\n11. **Theory X holds that:**\n\n 1. quality improvements lie in the hands of quality circles.\n 2. profits are tied to meeting schedule deadlines.\n 3. absenteeism is tied to poor working conditions.\n 4. **workers are inherently unmotivated and need strong guidance.**\n12. **Inputs to cost budgeting include all of the following except:**\n\n 1. **cost baseline**\n 2. cost estimate\n 3. work breakdown structure\n 4. project schedule\n13. **Risk identification outputs include the following except:**\n\n 1. **decision trees.**\n 2. inputs to other processes."}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1558", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "题库 A ：官方的选择题参考材料/好题萃取", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 650, "text": "include the following except:**\n\n 1. **decision trees.**\n 2. inputs to other processes.\n 3. risk symptoms.\n 4. potential risk events.\n14. **Inputs into overall change control include all of the following except:**\n\n 1. project plan.\n 2. change requests.\n 3. **change control system.**\n 4. performance reports\n15. **The process of performance reporting includes all of the following except:**\n\n 1. status reporting.\n 2. progress reporting.\n 3. forecasting.\n 4. **product analysis.**\n16. **A Work Breakdown Structure (WBS) numbering system should allow project staff to:**"}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1559", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "题库 A ：官方的选择题参考材料/好题萃取", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 581, "text": "16. **A Work Breakdown Structure (WBS) numbering system should allow project staff to:**\n\n 1. **identify the level at which individual WBS elements are found.**\n 2. identify configuration management milestones.\n 3. estimate the costs of WBS elements.\n 4. provide project justification.\n17. **Of the following estimates, which most accurately reflect the actual cost of the project?**\n\n 1. conceptual estimates.\n 2. order of magnitude estimates.\n 3. preliminary estimates.\n 4. **bottom-up estimates.**"}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1560", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "题库 A ：官方的选择题参考材料/好题萃取", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 657, "text": "r of magnitude estimates.\n 3. preliminary estimates.\n 4. **bottom-up estimates.**\n18. **When there is uncertainty associated with one or more aspects of the project, one of the first steps to take is to:**\n\n 1. revise project plan.\n 2. **conduct a risk-benefit analysis.**\n 3. conduct a needs analysis.\n 4. increase the estimated cost of the project.\n19. **One common way to compute estimated at completion (EAC) is to take the project budgeted-at-completion(BAC) and:**\n\n 1. divide it by the schedule performance index. (SPI)\n 2. multiply it by the schedule performance index. (SPI)"}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1561", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "题库 A ：官方的选择题参考材料/好题萃取", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 697, "text": "y the schedule performance index. (SPI)\n 2. multiply it by the schedule performance index. (SPI)\n 3. multiply it by the cost performance. (CPI)\n 4. **divide it by the cost performance index. (CPI)**\n20. **What kind of a relationship is implied when completion of a successor is dependent on initiation of its predecessor?**\n\n 1. finish-to-start (FS)\n 2. finish-to-finish (FF)\n 3. start-to-start (SS)\n 4. **start-to-finish (SF)**\n\n**有英文解析的题停更**\n\n1. **Which of the following it the logical flow of any project?**\n\n 1. Planning, Initiating, Executing, Controlling, Closing\n 2. Initiating, Planning, Controlling, Executing, Closing"}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1562", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "题库 A ：官方的选择题参考材料/好题萃取", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 687, "text": ", Executing, Controlling, Closing\n 2. Initiating, Planning, Controlling, Executing, Closing\n 3. Planning, Initiating, Executing, Controlling, Closing\n 4. **Initiating, Planning, Executing, Controlling, Closing**\n\nAnswer: D\n\n1. **Refinements are considered updates for the \\_\\_\\_\\_.**\n\n 1. GERT\n 2. ADM\n 3. **WBS**\n 4. CQM\n2. **Which of the following is a key aspect of quality control?**\n\n 1. Limited in scope\n 2. Minimal planning resources\n 3. Generic cost controls\n 4. **Project wide focus**\n3. **The creator of the project charter is identified as the \\_\\_\\_\\_\\_\\_.**\n\n 1. Project manager\n 2. **Outside senior manager**"}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1563", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "题库 A ：官方的选择题参考材料/好题萃取", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 314, "text": "harter is identified as the \\_\\_\\_\\_\\_\\_.**\n\n 1. Project manager\n 2. **Outside senior manager**\n 3. Internal control expert\n 4. Quality control expert\n4. **Phase end review of projects is also referred to as:**\n\n 1. Phase Exits\n 2. Kill Points\n 3. Stage Gates\n 4. **All the above**"}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1564", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "如果有冲突，以课本为准", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 692, "text": "[IT项目管理复习题目整理一 CSDN博客](https://blog.csdn.net/qq_47112287/article/details/125004585?ops_request_misc=%257B%2522request%255Fid%2522%253A%2522170307175516800185835318%2522%252C%2522scm%2522%253A%252220140713.130102334..%2522%257D&request_id=170307175516800185835318&biz_id=0&utm_medium=distribute.pc_search_result.none-task-blog-2~all~baidu_landing_v2~default-4-125004585-null-null.142^v96^pc_search_result_base9&utm_term=IT%E9%A1%B9%E7%9B%AE%E7%AE%A1%E7%90%86%E5%A4%8D%E4%B9%A0%E9%A2%98&spm=1018.2226.3001.4187)\n\n测试一\n\n1.（）是项目沟通中最主要的参与者\n\n项目团队成员\n\n项目经理\n\n项目业主\n\n项目发起人\n\n正确答案: B\n\n2由于发生火灾，供应商无法完成合同。项目经理从风险登记册中选择后备供应商来提供支持，这是执行：\n\n应急计划\n\n弹回计划\n\n权变措施\n\n风险再评估\n\n正确答案: A\n\n答案解析：答案：A。当已识别的风险发生时，及时采取风险登记册中的应急计划。"}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1565", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "如果有冲突，以课本为准", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 695, "text": "经理从风险登记册中选择后备供应商来提供支持，这是执行：\n\n应急计划\n\n弹回计划\n\n权变措施\n\n风险再评估\n\n正确答案: A\n\n答案解析：答案：A。当已识别的风险发生时，及时采取风险登记册中的应急计划。当主选策略失败，使用备选策略时选B。\n\n3.进度偏差SV<0（为负值）时，表示（ ）\n\nA.进度提前\n\nB. 表示进度延误\n\nC.实际消耗工时（或成本）低于预算值，即项目有结余或效率高\n\nD.实施成本过高，即实际消耗工时（或成本）超过预算值，即项目超支\n\n正确答案: B\n\n1. 要求冲突的双方寻求一个调和折衷解决方案，使各方得到某种程度的满足，从而消除冲突，共同合作，这是解决冲突的（）\n\n回避的方法\n\n妥协与合作的方法\n\n竞争或逼迫的方法\n\n调停或消除的方法\n\n正确答案: B\n\n5.在你作为项目经理的项目中，存在某种导致与顾客发生利益冲突的事件，如果你向顾客透漏这一情况，会使你们公司遭受一定得经济损失。这种情况下，你应当（）\n\nA.隐瞒情况\n\nB.向公司高级管理层汇报，寻求解决方案\n\nC.如实向顾客讲明情况，共同寻找解决方案\n\nD. 佯装不知\n\n正确答案: B\n\n(单选题,2.0分)在项目施工阶段，供应商发生火灾，导致原材的供应延迟了—周。项目经理已经识别到延迟的风险，并包含在计划当中。发生这个事件后，项目经理首先应该怎么做？\n\n执行风险应对计划\n\n由于材料延误，要求项目延期\n\n更新项目基准\n\n更新风险登记册\n\n正确答案: A\n\n答案解析：A. 风险已识别，并且已发生，所以要实施风险应对计划。\n\n7.从化解项目风险产生出发，去控制和消除项目具体风险的引发原因，属于（）措施"}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1566", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "如果有冲突，以课本为准", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 693, "text": "更新项目基准\n\n更新风险登记册\n\n正确答案: A\n\n答案解析：A. 风险已识别，并且已发生，所以要实施风险应对计划。\n\n7.从化解项目风险产生出发，去控制和消除项目具体风险的引发原因，属于（）措施\n\n风险化解\n\n风险遏制\n\n风险规避\n\n风险应急\n\n正确答案: A\n\n1. (单选题,2.0分)\n\n某项活动的最乐观时间是1周，最可能时间是5周，最悲观时间是15周，根据PERT 方法计算，该项目活动的工期期望值是（）\n\n5周\n\n6周\n\n10周\n\n15周\n\n正确答案: B\n\n(单选题,2.0分)质量审计风险审计和采购审计，虽然分属不同的知识领域，但都具有一个共同点是（）。\n\n都属于执行过程组\n\n都属于监控过程组\n\n都属于收尾过程组\n\n都涉及经验教训总结\n\n正确答案: D\n\n答案解析：答案D，考点“审计”。审计都会形成经验教训，但来自不同过程组。\n\n(单选题,2.0分)采购审计应该包括下列哪项？\n\n包含建设图纸在内的一套完整的合同清单\n\n客户对项目工作的评估\n\n团队对选中的合同类型进行评估\n\n评价哪些是失败的做法、哪些是成功的做法\n\n正确答案: D\n\n答案解析：\n\n答案解析：答案：D。采购审计是审查整个采购管理过程，评估应吸取的教训，包括总结成功的经验和错误的教训，目的是建立历史记录和改善未来采购合同与项目的绩效。\n\n(单选题,2.0分)项目计划应分给（）\n\nA.所有项目干系人\n\nB.具有一个独特标识的任务\n\nC.所需的汇报层次\n\nD. 可以被分派给一个以上组织单元的任务\n\n正确答案: A\n\n1. (单选题,2.0分)\n\n不属于项目初始阶段的工作模块是（ ）\n\nA.方案策划"}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1567", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "如果有冲突，以课本为准", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 693, "text": "B.具有一个独特标识的任务\n\nC.所需的汇报层次\n\nD. 可以被分派给一个以上组织单元的任务\n\n正确答案: A\n\n1. (单选题,2.0分)\n\n不属于项目初始阶段的工作模块是（ ）\n\nA.方案策划\n\nB.项目评估\n\nC.商业计划书的编写\n\nD. 工作分解\n\n正确答案: D\n\n1. 应为项目范围发生了重大变更，所以已批准的成本基准计划也发生了变更。如果你是项目经理，你的第一个应对措施应该是（）\n\nA.估算范围变更的大小\n\nB.进行预算更新\n\nC.用文件形式纪律应吸取的教训\n\nD. 实施以核准的范围变更\n\n正确答案: B\n\n1. “我们双方为什么不能各做一些让步，来解决这个问题呢？“这是项目管理中冲突处理的哪种办法？（ ）\n\n回避\n\n强制\n\n调停\n\n妥协\n\n正确答案: D\n\n1. （）即前面的活动必须结束以后，后面的活动才能开始\n\n结束——开始\n\n结束——结束\n\n开始——开始\n\n开始——结束\n\n正确答案: A\n\n(单选题,2.0分)项目经理想要知道干系人有没有识别出最重要的风险，要看哪个文件？\n\n项目章程\n\n风险登记册\n\n风险管理计划\n\n项目管理计划\n\n正确答案: B\n\n答案解析：答案：B。风险登记册是识别风险的输出，它包含了风险清单、潜在应对措施清单。\n\n1. (单选题,2.0分)\n\n作为项目经理，你建立了一个变更控制委员会，负责批准、推迟或驳回对电子设备项目的变更申请。在建立委员会的时候，你设立了具体的程序来控制它的运作，该程序要求所有已批准的变更都要在（)反映出来\n\nA.绩效衡量基本准则\n\nB.变更管理计划\n\nC.项目保证计划\n\nD. 项目计划\n\n正确答案: B"}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1568", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "如果有冲突，以课本为准", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 653, "text": "建立委员会的时候，你设立了具体的程序来控制它的运作，该程序要求所有已批准的变更都要在（)反映出来\n\nA.绩效衡量基本准则\n\nB.变更管理计划\n\nC.项目保证计划\n\nD. 项目计划\n\n正确答案: B\n\n1. (单选题,2.0分)\n\n最近客户要求变更设计，这将影响到项目进度安排，项目经理应该：（ ）\n\nA.不理会客户的要求，继续按计划进行项目\n\nB.忠告客户，说明进度计划不能变更\n\nC.按照项目变更控制系统的要求，获得变更批准\n\nD. 进行更加严密的进度控制\n\n正确答案: C\n\n1. (单选题,2.0分)\n\n下列不属于项目全局性、综合性管理的是（）\n\n项目进度管理\n\n项目成本管理\n\n项目风险管理\n\n项目范围管理\n\n正确答案: B\n\n1. 在合同执行过程中，买方的一名团队成员要求卖方编制并提交了一份合同规定之外的特殊的项目工作绩效报告。卖方为此向买方提出了额外费用索赔，以弥补它编制报告的支出。针对这种情况，买方的采购管理员应该（）。\n\nA.拒绝卖方的索赔要求，并调查团队成员为什么索要这份报告\n\nB.请团队成员提出变更请求，以便把该报告加进合同中\n\nC.向卖方支付费用补偿，并采取合理措施\n\nD.防止团队成员以后再索要类似报告\n\n正确答案: C\n\n答案解析：\n\nA.由于卖方已经多做了事情，理应收到额外的付款。\n\nB.首先要补偿卖方编写报告的成本，然后才考虑是否需要变更合同。\n\nC.正确答案。"}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1569", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "如果有冲突，以课本为准", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 687, "text": ".防止团队成员以后再索要类似报告\n\n正确答案: C\n\n答案解析：\n\nA.由于卖方已经多做了事情，理应收到额外的付款。\n\nB.首先要补偿卖方编写报告的成本，然后才考虑是否需要变更合同。\n\nC.正确答案。先支付卖方的合理索赔金额，再进行后续的其他处理（把这个报告加入合同中，或者要求团队成员不再索要这个报告）。\n\nD.也许在支付索赔金额后，可以做这个。\n\n参见：PMBOK®指南第384页。考点与答题技巧：控制采购过程，索赔管理。\n\n1. 当项目经理发现计划过程中有部分工作范围没有限定，他应当（）\n\nA.继续执行计划\n\nB.等到项目工作范围限定，然后开始工作\n\nC.尽其所能来定义工作范围\n\nD. 向客户抱怨\n\n正确答案: C\n\n1. (单选题,2.0分)\n\n从根本上放弃项目或放弃使用有风险的项目资源、项目技术等，从而避开项目风险的方法是（）措施\n\n风险化解\n\n风险遏制\n\n风险规避\n\n风险应急\n\n正确答案: C\n\n1. (单选题,2.0分)\n\n( )是用来分析和发现项目质量问题的关键影响因素\n\n流程图法\n\n质量检验法\n\n控制图法\n\n帕累斯图法\n\n正确答案: D\n\n1. (单选题,2.0分)\n\n在项目国力过程的说明中，不正确的是（\n\nA.不同项目选用不同的管理过程\n\nB.当项目发生变更时，项目的管理过程也发生变\n\nC.所有项目的管理过程都会有相同的顺序\n\nD. 不同的项目，其生命周期的各阶段也会有所不同\n\n正确答案: C\n\n1. (单选题,2.0分)\n\n变更请求的提出方式有多种，但它不能以（）形式提出\n\nA.口头或书写\n\nB.法律强制或自主决定\n\nC.正式或非正式"}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1570", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "如果有冲突，以课本为准", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 687, "text": "，其生命周期的各阶段也会有所不同\n\n正确答案: C\n\n1. (单选题,2.0分)\n\n变更请求的提出方式有多种，但它不能以（）形式提出\n\nA.口头或书写\n\nB.法律强制或自主决定\n\nC.正式或非正式\n\nD. 外部提出或内部提出\n\n正确答案: C\n\n1. (单选题,2.0分)\n\n假如那是项目经理，你需要向公司高层管理者汇报项目的月进度情况，你的报告采取的最合适的方式是：（ ）\n\n双代号图\n\n节点式网络图\n\n里程碑图\n\n甘特图\n\n正确答案: D\n\n1. (单选题,2.0分)\n\n挣值是：（ ）\n\nA.已执行工作的预算成本\n\nB.已执行工作的实际成本\n\nC. 计划工作的预算成本\n\nD. 到工作完成时的成本\n\n正确答案: B\n\n1. 项目的（）是项目活动不同于一般日常运营活动的关键特性。\n\n目的性\n\n独特性\n\n制约性\n\n一次性\n\n正确答案: D\n\n1. (单选题,2.0分)\n\n项目经理了解到主题专家(SME)正在考虑离开公司。该专家资源在其主题领域拥有深厚的知识,很难被替代。为确保主题专家能在整个项目期间留在项目中，项目经理与主题专家的经理讨论可能的措施。这些措施应该记录在哪个文件中？\n\nA.人力资源计划\n\nB.风险登记册\n\nC.风险管理计划\n\nD. 组轵分解结构\n\n正确答案: B\n\n答案解析：\n\n答案解析：参考答案：B解析：风险应对措施应该记录在风险登记册。参见《项目管理知识体系指南》第5版第327页。\n\n1. 在项目管理的概念中， 项目团队应（）\n\nA.对范围、时间、成本、风险和质量的不同要求进行管理\n\nB.对不同需求与期望的项目厉害关系者进行管理"}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1571", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "如果有冲突，以课本为准", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 683, "text": "参见《项目管理知识体系指南》第5版第327页。\n\n1. 在项目管理的概念中， 项目团队应（）\n\nA.对范围、时间、成本、风险和质量的不同要求进行管理\n\nB.对不同需求与期望的项目厉害关系者进行管理\n\nC.对已识别的项目需求进行管理\n\nD.上述所有项\n\n正确答案: D\n\n1. 你的团队没有采用你所提议的工作分解结构（WBS），而是制定了一份材料清单来定义项目的工作组成部分。客户在看了这份文件以后发现有必要进行一个范围变 更，并随后撰写了一份变更申请。在这个例子中，这份变更申请时（）结果。\n\nA.一个外事部件\n\nB.在定义产品范围时所犯的一个错误或疏忽\n\nC.一个增值的变化\n\nD. 在定义项目范围时所犯的一个错误或疏忽。\n\n正确答案: D\n\n1. (单选题,2.0分)\n\n一位项目经理说：“通过采取措施以不间断进行风险评估来将风险降低到最低，如果风险事件真的发生，就要采取相应的行动方案”。实际上，他是在使用风险控制的（ ）方式。\n\n风险转移\n\n风险降低\n\n风险接受\n\n风险规避\n\n正确答案: D\n\n1. (单选题,2.0分)\n\n克服分歧、解决冲突的有效途径是（）\n\nA.回避或撤出\n\nB.缓和与调停\n\nC.面对与正视\n\nD. 妥协\n\n正确答案: C\n\n(单选题,2.0分)项目团队发现项目有可能暴露于重大财务风险当中。若要管理这类风险，应使用何种策略?\n\n回避\n\n分享\n\n转移\n\n接受\n\n正确答案: C\n\n答案解析：C。p344 书上原话”风险转移策略对处理风险的财务后果最有效“。\n\n(单选题,2.0分)项目经理接到一个变更请求。该变更请求会影响到项目进度。"}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1572", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "如果有冲突，以课本为准", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 685, "text": "分享\n\n转移\n\n接受\n\n正确答案: C\n\n答案解析：C。p344 书上原话”风险转移策略对处理风险的财务后果最有效“。\n\n(单选题,2.0分)项目经理接到一个变更请求。该变更请求会影响到项目进度。对于谁应该对变更请求的执行做出决定存在不确定性。下列哪一个文件需要更新？\n\n质量计划和风险登记册\n\n沟通计划和风险登记册\n\n项目计划和变更管理计划\n\n变更管理计划和风险登记册\n\n正确答案: D\n\n(单选题,2.0分)项目的阶段性成果我们称为：\n\n里程碑\n\n可交付成果\n\n项目产品\n\n项目结论\n\n正确答案: A\n\n1. (单选题,2.0分)\n\n下列哪种类型的合同为买方提供了最小的风险？( )\n\nA.固定总价合同\n\nB.成本补偿合同\n\nC.工时和材料费合同\n\nD. 单价合同\n\n正确答案: A\n\n1. (单选题,2.0分)\n\n项目成本管理包括的主要过程有 ( )。\n\nA.成本估算\n\nB.成本预算\n\nC.成本控制\n\nD. 以上都是\n\n正确答案: D\n\n1. (单选题,2.0分)\n\n一个由7个人组成的项目组，其沟通渠道的条数是。 ( )\n\nA.14条\n\nB.21 条\n\nC.38 条\n\nD. 49 条\n\n正确答案: B\n\n(单选题,2.0分)项目经理和项目团队发现某个零部件容易产生缺陷，于是决定交由第三方负责，在合同中指明由供应商提供零部件的保修。请问这是什么风险应对措\n\n施？\n\n回避\n\n转移\n\n减轻\n\n接受\n\n正确答案: B\n\n答案解析：参考答案：B解析：风险转移是指项目团队把威胁造成的影响连同应对责任一起转移给第三方。参见PMBOK指南第5版第344页。\n\n1."}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1573", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "如果有冲突，以课本为准", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 696, "text": "施？\n\n回避\n\n转移\n\n减轻\n\n接受\n\n正确答案: B\n\n答案解析：参考答案：B解析：风险转移是指项目团队把威胁造成的影响连同应对责任一起转移给第三方。参见PMBOK指南第5版第344页。\n\n1.\n\n在关键路线上增加资源不总是缩短项目的持续时间，这是因为：（ ）\n\nA.增加资源有可能导致效率低下\n\nB.在项目计划时总以最佳的资源数量来安排活动\n\nC.项目经理总是选择具有高技能水平的人员\n\nD.增加跟多的资源可能产生额外的工作\n\n正确答案: D\n\n(单选题,2.0分)范围基线一旦被确立立功批准，将被（）。\n\nA.用于评价潜在变化\n\nB.用于完成有效性衡量\n\nC.作为未来决策的基础\n\nD.以上皆是\n\n正确答案: D\n\n(单选题,2.0分)若要管理不确定性的成本，项目资金应包括下列哪—项？\n\n额外成本\n\n应急储备\n\n缓冲\n\n估算成本\n\n正确答案: B\n\n答案解析：B。应急储备用于已知-未知风险\n\n(单选题,2.0分)项目的三要素包括（）。\n\nA.风险、费用和进度\n\nB.质量、进度和成本\n\nC. 质量、进度和时间\n\nD. 直接成本、间接成本和可用资源\n\n正确答案: B\n\n1. (单选题,2.0分)\n\n用来描述项目的目标、工作内容、可交付成果和最终产品的文件是（）\n\n项目章程\n\n项目范围说明书\n\n产品描述\n\n项目活动清单\n\n正确答案: B\n\n(单选题,2.0分)项目沟通计划的主要编写方法是:\n\n利益相关者分析\n\n周围环境分析\n\n原始材料的分析\n\n领导意图分析\n\n正确答案: A"}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1574", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "如果有冲突，以课本为准", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 692, "text": "范围说明书\n\n产品描述\n\n项目活动清单\n\n正确答案: B\n\n(单选题,2.0分)项目沟通计划的主要编写方法是:\n\n利益相关者分析\n\n周围环境分析\n\n原始材料的分析\n\n领导意图分析\n\n正确答案: A\n\n(单选题,2.0分)每个阶段起点的核准，对启动过程有何帮助？\n\n没有帮助，可以取消\n\n有利于控制每个阶段的风险\n\n重新任命项目经理\n\n每个项目仅需一个启动即可\n\n正确答案: B\n\n答案解析： 为了确认原定的假设和决策是否合理，降低风险。\n\n1. (单选题,2.0分)\n\n某项活动的最乐观时间是2周，最可能时间是6周，最悲观时间是10周，根据PERT 方法计算，该项目活动的工期期望值是（）\n\n4周\n\n5周\n\n6周\n\n7周\n\n正确答案: C\n\n(单选题,2.0分)风险概率和影响评估通常用于（）\n\n实施定性风险分析\n\n实施定量风险分析\n\n规划风险应对\n\n控制风险\n\n正确答案: A\n\n答案解析：A.正确答案。风险概率和影响评估是实施定性风险分析过程的工具与技术。\n\nB.不是实施定量风险分析过程的工具。实施定量风险分析过程使用了数据收集和展示技术、定量风险分析和建模技术、专家判断等工具。\n\nC.不是规划风险应对过程的工具。规划风险应对过程使用消极风险或威胁的应对策略、 积极风险或机会的应对策略、应急应对策略和专家判断。\n\nD.不是控制风险过程的工具。控制风险过程使用风险再评估、风险审计、偏差和趋势分析、技术绩效测量、储备分析和会议。\n\n参见：PMBOK®指南第330页。考点与答题技巧：实施定性风险分析过程的工具。\n\n1. 下列项目管理过程组中，哪一个最耗费时间与资金？ ( C)"}
{"id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9::1575", "page_id": "docx::XYEkwby3Li2hBkk3rtZciOiYnO9", "title": "专项突破：选择题（题库）", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/PM 专项突破/专项突破：选择题（题库）", "section": "如果有冲突，以课本为准", "url": "https://a1npn29y3xu.feishu.cn/wiki/XYEkwby3Li2hBkk3rtZciOiYnO9", "source_type": "docx", "n_chars": 278, "text": "、偏差和趋势分析、技术绩效测量、储备分析和会议。\n\n参见：PMBOK®指南第330页。考点与答题技巧：实施定性风险分析过程的工具。\n\n1. 下列项目管理过程组中，哪一个最耗费时间与资金？ ( C)\n\nA.启动过程\n\nB.计划过程\n\nC.执行过程\n\nD. 收尾过程\n\n正确答案: C\n\n————————————————\n\n版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。\n\n原文链接：https://blog.csdn.net/qq_47112287/article/details/125004585"}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1576", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "2026 软件测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 664, "text": "**名词解释：**\n\n1.V Model\n\n2.Code Review\n\n3.Topdown Intergration Test\n\n4.Unit Testing\n\n5.Prevention Mantianance\n\n**简答：**\n\n1.verification vs validation\n\n2.dataflow testing（没听过）\n\n3.alpha test vs beta test\n\n4.security test 是什么，以及一种常见的方法\n\n5.TDD是什么以及与test的关系\n\n**白盒：循环版二分搜索**\n\n1.control flow graph\n\n2.condition coveration，写出：caseID,Input,Condition,Output\n\n3.圈复杂度，基本路径以及用例，写出：caseID,Input,Path,Output\n\n**黑盒：图书馆借书系统**\n\nReader type: Teacher Student\n\nBook type:Hoot,Normal\n\nIs vaction: T,F\n\nAction：能借多少天\n\n关键规则：Vaction与否不影响 另外两个因素对 action 的规则\n\n1.写出所有 condition stub 和 action stub，不写无效的。\n\n2.写出Decision Table，并根据规则写出一个化简的Decision Table\n\n3.给出 test case，并加上无效condition\n\n**综合大题：医院系统**"}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1577", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "2026 软件测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 434, "text": "写无效的。\n\n2.写出Decision Table，并根据规则写出一个化简的Decision Table\n\n3.给出 test case，并加上无效condition\n\n**综合大题：医院系统**\n\n医院系统，分好几个模块，四个功能(选择科室，查看医生排班，预约挂号，取消预约)，最关键的是挂号预约模块。且有 web 端和微信小程序。\n\n关键规则：每周一早上会有 2000 用户高峰\n\n1.判断需要哪些类型的 system test，并给出理由\n\n2.设计system test的流程：test plan，系统环境，tool...\n\n3.设计挂号预约系统的 functional system test，正常场景和异常场景各一个，需要：caseID,input,operation,output\n\n4.设计挂号预约系统，专门针对每周一早上的 performance test。写两个性能测试用例，描述objective(测试目标?)和passing threshold"}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1578", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "2025", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 96, "text": ""}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1579", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "新高考 A", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 25, "text": "感谢学长开源！遵循 CC BY-NC 4.0 协议"}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1580", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "新高考 A/一、名词解析（5 \\* 5）", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 97, "text": "1. Validation & Verification\n2. Drivers & Stubs\n3. Error Guessing\n4. Bug Report\n5. Volume Testing"}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1581", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "新高考 A/二、简答题（4 \\* 5）/为什么软件测试不只是一个技术问题？", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 193, "text": "讲义没有把这个内容汇总到一起，漏了？\n\n **组织管理与资源协调的复杂性**\n\n**流程规范与文档化的必要性**\n\n**质量文化与团队认知的影响**\n\n**经济成本与风险权衡**\n\n**法规与行业标准的约束**\n\n总结\n\n软件测试是技术、管理、流程、文化等多维度的综合体。技术手段（如自动化测试工具）仅解决部分问题，而组织协作、流程规范、资源管理、法规合规等非技术因素同样决定测试成败。"}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1582", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "新高考 A/二、简答题（4 \\* 5）/为什么我们需要自动化测试？", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1583", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "新高考 A/二、简答题（4 \\* 5）/🌟 主要的软件维护活动有哪些？", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1584", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "新高考 A/三、黑白盒测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 689, "text": "（一）白盒测试\n\n```C++\nvoid MyFunction (int& x, int& y, int& z) {\n while (x > -10 && y > -10)\n {\n z = x - y;\n if (z > 0)\n {\n x--;\n y--;\n }\n else\n {\n if (z < -12) x -= 12;\n else x -= 14;\n }\n }\n}\n```\n\n1. 画控制流图\n\n\n\n1. 设计测试用例（全流程）针对决策针对条件条件分支覆盖，意味着这 10 个 T/F 至少只需要出现一次即可设计测试用例 设计测试用例\n\n 1. 决策覆盖（Decision Coverage）也叫做边覆盖\n\n | x | y | z = x - y | path |\n |-|-|-|-|\n | -11 | -11 | 0 | ab |\n | -9 | -8 | 1 | acdeb |\n | 2 | 12 | -10 | acfijb |\n | 1 | 14 | -13 | acfghb |\n\n 1. 条件分支覆盖\n\n | x > -10 and y > -10 | F（1） | T（2） |\n |-|-|-|"}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1585", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "新高考 A/三、黑白盒测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 688, "text": "b |\n | 1 | 14 | -13 | acfghb |\n\n 1. 条件分支覆盖\n\n | x > -10 and y > -10 | F（1） | T（2） |\n |-|-|-|\n | z=x-y > 0 | F（3） | T（4） |\n | z=x-y -10 | F（7） | T（8） |\n |-|-|-|\n | y > -10 | F（9） | T（10） |\n\n | x | y | z=x-y | condition |\n |-|-|-|-|\n | -11 | -11 | 0 | （1）~~（3）（5）~~（7）（9） |\n | 15 | 3 | 12 | （2）（4）（8）（10） |\n | 0 | 30 | -30 | （2）（3）（6）（7）（9） |\n | | | | |\n\n 1. 条件覆盖\n\n | x > -10 | F（1） | T（2） |\n |-|-|-|\n | y > -10 | F（3） | T（4） |\n | z > 0 | F（5） | T（6） |\n | z < -12 | F（7） | T（8） |\n\n | x | y | z=x-y | 符合的条件 |\n |-|-|-|-|\n | 20 | 10 | 10 | （2）（4）（6） |\n | -21 | -11 | -10 | （1）（3） |\n | 30 | 50 | -20 | （2）（4）（8） |\n | | | | |\n2. 基本路径覆盖"}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1586", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "新高考 A/三、黑白盒测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 671, "text": "）（6） |\n | -21 | -11 | -10 | （1）（3） |\n | 30 | 50 | -20 | （2）（4）（8） |\n | | | | |\n2. 基本路径覆盖\n\n要算基本路径覆盖，首先需要计算计算圈复杂度（不要跳步，圈复杂度是有分的）\n\nE - V + 2 = 11 - 9 + 2 = 4\n\n咱们再数一数，确实是四个\n\nOK，开始翻译成正则表达式\n\na.b.(c.(d.(f + g) + e).h + 0).i\n\n全部改成 1：1 \\* 1 \\* （1 \\* （1\\*（1 + 1）+ 1）1 + 1） \\*1 = 4\n\n确认翻译没有错以后，由简到难把四条路径写出来\n\na-b-i\n\na-b-c-e-h-i\n\na-b-c-d-f-h-i\n\na-b-c-d-g-h-i\n\n设计测试用例\n\n| x | y | z=x-y | 符合的条件 |\n|-|-|-|-|\n| -11 | -11 | 0 | a-b-i |\n| -9 | -8 | 1 | a-b-c-e-h-i |\n| 1 | 14 | -13 | a-b-c-d-g-h-i |\n| 2 | 12 | -10 | a-b-c-d-f-h-i |\n\n（二）等价类划分\n\n业务需求：保险公司参保人需要满足三个要求：单身、男性、出生日期为 19840430 \\~ 20060501\n\n有效等价类无效等价类单身男性出生日期符合规则非单身非男性年龄太大年龄太小\n\n根据需求分析，以下是完善后的等价类划分及测试用例设计：\n\n**DS 解析：测试用例设计**"}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1587", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "新高考 A/三、黑白盒测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 665, "text": "0 \\~ 20060501\n\n有效等价类无效等价类单身男性出生日期符合规则非单身非男性年龄太大年龄太小\n\n根据需求分析，以下是完善后的等价类划分及测试用例设计：\n\n**DS 解析：测试用例设计**\n\n根据需求分析，以下是完善后的等价类划分及测试用例设计：\n\n完善后的等价类划分表\n\n| 有效等价类 | 无效等价类 |\n|-|-|\n| 单身、男性、出生日期在范围内 | 非单身（如已婚、离异、丧偶） |\n| | 非男性（如女性、其他性别） |\n| | 出生日期早于1984-04-30 |\n| | 出生日期晚于2006-05-01 |\n\n测试用例设计\n\n**有效等价类测试用例**\n\n1. 用例编号: TC1 描述: 满足所有有效条件\n\n输入: 性别=男，婚姻状态=单身，出生日期=2000-01-01 预期结果: 符合参保条件，允许投保\n\n1. 用例编号: TC2 描述: 出生日期为下限边界值\n\n输入: 性别=男，婚姻状态=单身，出生日期=1984-04-30 预期结果: 符合参保条件，允许投保\n\n1. 用例编号: TC3 描述: 出生日期为上限边界值\n\n输入: 性别=男，婚姻状态=单身，出生日期=2006-05-01 预期结果: 符合参保条件，允许投保\n\n---\n\n**无效等价类测试用例**\n\n1. 用例编号: TC4 描述: 非单身（已婚）\n\n输入: 性别=男，婚姻状态=已婚，出生日期=2000-01-01 预期结果: 不满足条件，拒绝投保\n\n1. 用例编号: TC5 描述: 非男性（女性）"}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1588", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "新高考 A/三、黑白盒测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 508, "text": "号: TC4 描述: 非单身（已婚）\n\n输入: 性别=男，婚姻状态=已婚，出生日期=2000-01-01 预期结果: 不满足条件，拒绝投保\n\n1. 用例编号: TC5 描述: 非男性（女性）\n\n输入: 性别=女，婚姻状态=单身，出生日期=2000-01-01 预期结果: 不满足条件，拒绝投保\n\n1. 用例编号: TC6 描述: 出生日期早于下限（年龄太大）\n\n输入: 性别=男，婚姻状态=单身，出生日期=1984-04-29 预期结果: 不满足条件，拒绝投保\n\n1. 用例编号: TC7 描述: 出生日期晚于上限（年龄太小）\n\n输入: 性别=男，婚姻状态=单身，出生日期=2006-05-02 预期结果: 不满足条件，拒绝投保\n\n---\n\n说明\n\n1. 边界值覆盖：有效用例（TC2、TC3）和无效用例（TC6、TC7）明确测试了出生日期的边界条件，确保逻辑正确处理临界值。\n2. 单一无效条件：每个无效用例仅违反一个条件（如仅非单身、仅非男性），避免多条件干扰，便于定位问题。\n3. 数据格式假设：假设输入数据格式正确（如日期为`YYYY-MM-DD`），若需验证格式合法性，需补充额外测试用例。"}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1589", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "新高考 A/四、场景题（DS 改编版）/文本材料", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 687, "text": "---\n\n**材料背景：**\n\n\"多多买菜\"是某公司推出的社区团购平台，主要面向社区居民提供生鲜蔬果、日用品等商品的线上团购服务。系统采用微服务架构，包含以下核心模块：\n\n**业务功能详述：**\n\n1. **用户端功能**：\n\n - **商品浏览与搜索**：\n\n - 按分类（蔬菜/水果/肉类）、促销标签（限时秒杀、团长推荐）筛选商品\n - 支持关键词模糊搜索（如“红富士苹果”）\n - **拼团与下单**：\n\n - 普通购买：直接按零售价下单\n - 拼团购买：2人成团，成团失败自动退款\n - 订单合并：同一配送点的多个订单可合并支付\n - **支付与优惠**：\n\n - 支持微信支付、支付宝、余额支付\n - 优惠券叠加使用（平台券+团长专属券）\n - 满减规则（如满50减5，满100减15）\n - **售后与物流**：\n\n - 订单取消：未支付订单30分钟内可取消\n - 退款申请：商品质量问题支持部分/全额退款\n - 物流追踪：实时显示配送员位置与预计到达时间\n\n1. **管理端功能**：\n\n - **团长管理**：\n\n - 团长资质审核（身份证、社区住址验证）\n - 团长佣金计算（按订单金额的3%\\~5%提成）\n - **库存管理**：\n\n - 库存预警：商品库存低于阈值时自动通知补货\n - 批次管理：生鲜商品按批次记录保质期\n - **营销活动配置**：\n\n - 秒杀活动设置（时间、库存、限购数量）"}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1590", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "新高考 A/四、场景题（DS 改编版）/文本材料", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 270, "text": "：\n\n - 库存预警：商品库存低于阈值时自动通知补货\n - 批次管理：生鲜商品按批次记录保质期\n - **营销活动配置**：\n\n - 秒杀活动设置（时间、库存、限购数量）\n - 拼团规则配置（成团人数、有效期）\n\n---\n\n**问题**：\n\n1. （10分）请结合上述业务功能与技术挑战，设计功能测试策略（至少 5 点）和性能测试策略（5 个要点）。\n2. （10分）针对社区团购的典型场景（如拼团失败、秒杀超卖），描述完整的测试流程（需包含需求分析到上线验证的全过程）以及需要输出的测试文档（4 种）。"}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1591", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "新高考 A/四、场景题（DS 改编版）/解题思路", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 364, "text": "1. 系统功能测试策略以及系统性能测试策略？（10 分）\n\n功能测试：验证软件的行为是否符合预期\n\n包括了离谱的输入，但是回复要合理\n\n削减所有级别的测试，重心在单元测试\n\n**根据题目要求**将输入输出接口，从接口收集结果\n\n性能测试：检查应用程序或软件在工作负载下在响应性和稳定性方面表现的测试类型\n\n三 S：Speed Scalability Stability\n\n**负载、压力、持久、尖峰、容量**\n\n1. 结合材料，描述本场景的测试流程以及测试文档？（10 分）\n\n测试流程：定义策略 —— 定义系统 —— 预估成本 —— 准备计划 —— 执行计划 —— 发现问题 —— 解决问题 —— 总结测试流程\n\n测试文档包括哪四个？测试计划 —— 测试用例 —— 测试报告 —— 总结报告（回顾一下当时你实验课写的四份文档）"}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1592", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "新高考 A/四、场景题（DS 改编版）/**一、功能测试策略与性能测试策略设计**/**1. 功能测试策略（5点）**", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 657, "text": "1. **核心业务流程验证**\n\n - **拼团与订单合并流程**：验证用户发起拼团、邀请参团、成团失败自动退款（24小时未成团）、同一配送点订单合并支付等功能的完整性。需模拟多人并发拼团场景，检查订单状态流转（拼团中→成功/失败）。\n - **支付与优惠叠加**：测试微信/支付宝/余额支付的兼容性，验证优惠券（平台券+团长券）叠加规则与满减逻辑（如满50减5）的正确性。需覆盖边界值（如订单金额刚好满足满减条件）。\n\n1. **异常场景与边界测试**\n\n - **拼团失败处理**：模拟成团人数不足、超时未支付等场景，验证自动退款流程及通知机制（如短信/微信提醒）的可靠性。\n - **秒杀超卖控制**：通过高并发请求测试库存扣减逻辑，确保秒杀商品在售罄后不再可下单，避免超卖问题（如使用Redis原子操作或数据库悲观锁）。\n\n1. **搜索与筛选功能覆盖**\n\n - **分类筛选与模糊搜索**：验证按商品分类（蔬菜/水果）、促销标签（限时秒杀）筛选的准确性，测试关键词模糊搜索的容错能力（如“红富士苹果”匹配“富士”）。\n\n1. **售后与物流全链路测试**\n\n - **退款与物流追踪**：模拟商品质量问题部分退款、订单取消（30分钟内未支付自动关闭），检查退款金额计算逻辑；验证物流位置实时更新与预计到达时间的准确性。\n\n1. **兼容性与安全性测试**\n\n - **多设备兼容性**：测试小程序在iOS/Android不同机型、微信版本下的兼容性，确保UI布局与交互一致。"}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1593", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "新高考 A/四、场景题（DS 改编版）/**一、功能测试策略与性能测试策略设计**/**1. 功能测试策略（5点）**", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 169, "text": "流位置实时更新与预计到达时间的准确性。\n\n1. **兼容性与安全性测试**\n\n - **多设备兼容性**：测试小程序在iOS/Android不同机型、微信版本下的兼容性，确保UI布局与交互一致。\n - **安全漏洞防护**：对用户输入（如搜索框、支付参数）进行SQL注入、XSS攻击模拟，验证后端过滤与加密机制的有效性。\n\n---"}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1594", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "新高考 A/四、场景题（DS 改编版）/**一、功能测试策略与性能测试策略设计**/**2. 性能测试策略（5要点）**", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 506, "text": "1. **高并发场景负载测试**\n\n - 使用JMeter模拟秒杀活动期间瞬时流量（如10万用户同时抢购），监测服务器响应时间（目标≤1秒）、吞吐量及错误率。\n - 验证订单合并支付接口的并发处理能力，确保资源争用（如库存扣减）时事务一致性。\n\n1. **压力与稳定性测试**\n\n - 持续施压至系统极限（如CPU利用率≥90%），观察服务降级策略（如限流熔断）是否生效，确保核心功能（支付、拼团）优先可用。\n - 测试长时间运行（如24小时）下的内存泄漏与数据库连接池稳定性。\n\n1. **数据库性能优化验证**\n\n - 针对生鲜商品批次管理、库存预警模块，测试批量读写操作（如每日补货数据更新）的SQL执行效率，优化索引与分表策略。\n\n1. **网络与CDN容灾测试**\n\n - 模拟弱网环境（3G/高延迟），验证页面加载速度与超时重试机制；通过CDN节点故障切换测试，确保静态资源（商品图片）高可用。\n\n1. **横向扩展能力评估**\n\n - 验证微服务架构的弹性伸缩能力（如自动扩容ECS实例），通过Kubernetes集群负载均衡测试，确保促销期间服务无单点故障。\n\n---"}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1595", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "新高考 A/四、场景题（DS 改编版）/**二、典型场景测试流程与文档输出**/**1. 测试流程（以拼团失败为例）**", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 378, "text": "1. **需求分析**\n\n - 明确业务规则：2人成团、24小时未成团自动退款，订单状态需同步更新。\n\n1. **测试用例设计**\n\n - **正常场景**：2人成功参团→订单状态为“拼团成功”→生成配送任务。\n - **异常场景**：单人开团超时→状态变更为“失败”→退款至原支付渠道。\n\n1. **测试执行与工具**\n\n - 使用Postman模拟API请求，验证退款接口幂等性（重复调用不重复退款）。\n - 通过Selenium自动化测试前端页面状态提示（如倒计时、参团提醒）。\n\n1. **缺陷管理与回归**\n\n - 记录并发拼团时可能出现的订单状态不一致问题，修复后通过Jenkins触发回归测试。\n\n1. **上线验证与监控**\n\n - 灰度发布后，通过日志监控退款成功率，确保实际业务数据与测试结果一致。\n\n---"}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1596", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "新高考 A/四、场景题（DS 改编版）/**二、典型场景测试流程与文档输出**/**2. 测试文档（4种）**", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 207, "text": "1. **测试计划**：定义测试范围（拼团、秒杀模块）、资源分配（测试环境、工具）、进度安排。\n2. **测试用例文档**：详细描述场景步骤、输入数据、预期结果（如拼团失败退款金额=订单金额）。\n3. **测试报告**：记录执行结果（通过率、缺陷分布）、性能指标（TPS、响应时间）及风险分析。\n4. **缺陷跟踪报告**：汇总Bug优先级、修复状态、回归验证记录，提供优化建议（如优化库存扣减锁机制）。\n\n---"}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1597", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "新高考 A/四、场景题（DS 改编版）/**引用说明**", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 90, "text": "- 功能测试策略结合了业务流程验证、异常处理、安全防护等要点。\n- 性能测试参考了高并发处理、数据库优化、弹性伸缩等内容。\n- 测试流程与文档设计依据全链路测试方法及缺陷管理实践。"}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1598", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "新高考 B/一、名词解析（4 \\* 5）", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 82, "text": "1. Bottom-up integration\n2. Scenario testing\n3. Load testing\n4. Acceptance testing"}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1599", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "新高考 B/二、简答题（5 \\* 5）", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 258, "text": "1. TDD,advantage\n2. What's Unit testing?Who is response for?What is the process of unit testing？\n3. What's regression testing?\n4. What is Software Testing Automation?\n5. What is Software Maintenance？List some method to improve the maintainance of the system?"}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1600", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "新高考 B/三、白盒测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 432, "text": "```Java\nvoid Sort(int iRecordNum,int iType)\n{\n int x=0; int y=0;\n while (iRecordNum-- > 0)\n {\n if(0 == iType)\n {\n x=y+2;\n break;\n }\n else if (1==iType) x=y+10;\n else x=y+20;\n }\n}\n```\n\n1. 画出 Control Flow Graphs\n2. 根据上面的程序，decision branch and condition branch\n3. 设计测试用例，满足条件覆盖\n4. 设计测试用例，满足 Basis Path Testing\n\n"}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1601", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "新高考 B/四、黑盒测试", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 212, "text": "酒店有会员积分机制，输入是\n\n酒店星级 L（正整数1\\~10十种情况）\n\n会员等级 C（单个字母，大小写敏感，只有三种情况 P G O）\n\n消费的金额 A（十进制正实数，两位小数），\n\n还有一个计算会员积分的算法，此处忽略掉，大概意思是：\n\n酒店等级对应的欢迎积分（会给一个表格，此处省略）+ 消费金额A\\*会员等级对应的百分比（会给一个表格，此处省略）\n\n1）有效等价类和无效等价类\n\n2）根据第1）问的情况，设计测试用例"}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1602", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "新高考 B/五、场景题", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 191, "text": "给你一个校园电影院票的预订系统，可以进行订票，查询，取消订票等功能，之后有详细的功能描述，回答以下问题。\n\n1) 说一下你的functional testing strategy and system performance testing strategy.\n\n2) 如果让你对这个系统进行测试，描述一下 testing process and testing document."}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1603", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "新高考 B/附一：黑盒测试（DS 魔改版）", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 319, "text": "**材料背景**： 某酒店**会员积分是欢迎积分和消费积分的总和**，计算规则如下：\n\n- **欢迎积分**根据酒店星级（L）和会员等级（C）查表获得，表格示例如下（省略了部分信息）：\n\n- **消费积分**=消费金额 A × 会员等级对应百分比，查表如下：\n\n**输入参数**：\n\n- 酒店星级 L：正整数，取值范围1\\~10\n- 会员等级 C：单个字母（仅允许大写P/G/O）\n- 消费金额 A：正实数，保留两位小数（A ≥ 0.01）\n\n**问题补充**：\n\n1. （10分）划分输入参数的有效等价类与无效等价类，需覆盖所有边界和异常情况。\n2. （10分）根据等价类划分结果，设计测试用例（至少5个），需体现参数组合与预期结果。"}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1604", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "新高考 B/附一：黑盒测试（DS 魔改版）/手工速搓版", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 355, "text": "等价类划分\n\n| | 有效等价类 | 无效等价类 |\n|-|-|-|\n| 针对酒店星级 | 1 \\~ 10 范围内的正整数 | 非数字、零、非整数、负整数、大于 10 的正整数 |\n| 针对会员等级 | 仅允许大写 P/G/O | 小写 p g o、大小写的其他字母、非字母 |\n| 针对消费金额 | 两位小数的正实数 | 正的多位小数、正的一位小数、正整数、零、负数 |\n\n边界值分析\n\n| 针对酒店星级 | -1 0 1 9 10 11 |\n|-|-|\n| 针对会员等级 | P p G g O o |\n| 针对消费金额 | -0.01 0 0.001 0.01 0.1 99.99 99.9 99 |\n\n有效等价类一条测试用例就可以覆盖了，但是无效等价类每一种特例都要额外写一个测试用例触发异常情景"}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1605", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "新高考 B/附一：黑盒测试（DS 魔改版）/问题1：输入参数的有效等价类与无效等价类划分（覆盖边界和异常情况）/**1. 酒店星级 L（正整数，1\\~10）**", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 129, "text": "- **有效等价类**：\n\n - L ∈ {1, 2, ..., 10}（符合取值范围的正整数）。\n- **无效等价类**：\n\n - L 10（如11、100）；\n - 非整数（如5.5、字符串\"abc\"）；\n - 非数字输入（如空值、特殊字符）。"}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1606", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "新高考 B/附一：黑盒测试（DS 魔改版）/问题1：输入参数的有效等价类与无效等价类划分（覆盖边界和异常情况）/**2. 会员等级 C（仅允许大写P/G/O）**", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 127, "text": "- **有效等价类**：\n\n - C ∈ {P, G, O}（大写字母）。\n- **无效等价类**：\n\n - 其他大写字母（如A、B）；\n - 小写字母（如p、g）；\n - 非字母字符（如数字、符号、空格）；\n - 空值或多字符（如\"PG\"）。"}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1607", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "新高考 B/附一：黑盒测试（DS 魔改版）/问题1：输入参数的有效等价类与无效等价类划分（覆盖边界和异常情况）/**3. 消费金额 A（正实数，A ≥ 0.01，保留两位小数）**", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 193, "text": "- **有效等价类**：\n\n - A = 0.01（最小值边界）；\n - 0.01 < A ≤ 极大正实数（如100.00、999.99）；\n - 两位小数（如50.00、123.45）。\n- **无效等价类**：\n\n - A < 0.01（如0.00、-100.00）；\n - 非两位小数（如0.1、5.555）；\n - 非数字输入（如字符串\"abc\"、空值）。\n\n---"}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1608", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "新高考 B/附一：黑盒测试（DS 魔改版）/问题2：测试用例设计（覆盖参数组合与预期结果）", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 685, "text": "| **测试用例编号** | **输入参数（L, C, A）** | **覆盖等价类** | **预期结果** |\n|-|-|-|-|\n| **TC01** | L=5, C=G, A=200.00 | 有效L（5）、有效C（G）、有效A（200.00） | 计算积分：欢迎积分（查表）+ 消费积分（200×C对应百分比） |\n| **TC02** | L=0, C=P, A=100.00 | 无效L（0）、有效C（P）、有效A（100.00） | 提示错误：“酒店星级无效” |\n| **TC03** | L=10, C=X, A=50.00 | 有效L（10）、无效C（X）、有效A（50.00） | 提示错误：“会员等级无效” |\n| **TC04** | L=7, C=O, A=0.005 | 有效L（7）、有效C（O）、无效A（0.005，小数位超限且值<0.01） | 提示错误：“消费金额需≥0.01且保留两位小数” |\n| **TC05** | L=\"abc\", C=G, A=300.00 | 无效L（非数字）、有效C（G）、有效A（300.00） | 提示错误：“酒店星级需为1\\~10的正整数” |\n| **TC06** | L=3, C=p, A=150.00 | 有效L（3）、无效C（小写p）、有效A（150.00） | 提示错误：“会员等级仅允许大写P/G/O” |\n| **TC07** | L=10, C=O, A=-50.00 | 有效L（10）、有效C（O）、无效A（负数） | 提示错误：“消费金额需≥0.01” |\n\n---"}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1609", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "新高考 B/附一：黑盒测试（DS 魔改版）/**设计说明**：", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 286, "text": "1. **覆盖原则**：\n\n - 每个测试用例仅覆盖一个无效等价类，避免多个无效参数干扰错误定位。\n - 边界值用例（如L=1、L=10、A=0.01）需包含有效和无效情况。\n2. **组合策略**：\n\n - 有效参数组合（TC01）验证功能正常；\n - 单个参数无效组合（TC02-TC07）验证异常处理逻辑；\n - 隐含需求：参数缺失、格式错误（如非数字）需明确提示。\n3. **扩展建议**：\n\n - 补充覆盖会员等级对应百分比表（如C=P时消费积分比例）的具体计算；\n - 增加多参数同时无效的用例（如L=0且C=X）以测试错误优先级。"}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1610", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "新高考 B/附二：场景题（DS 魔改版）", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 308, "text": "**材料背景**： 某校园电影院订票系统支持以下功能：\n\n1. **用户端功能**：\n\n - 学生身份认证（需验证学号与教务系统同步）\n - 影片查询（按时间、影厅、影片名筛选）\n - 在线选座购票（座位状态实时更新）\n - 订单取消（开场前1小时可免费取消）\n - 电子票二维码生成与核销\n2. **管理端功能**：\n\n - 影厅排期管理\n - 票价动态调整（学生票8折）\n - 售票数据统计\n\n**问题补充**：\n\n1. （10分）请说明功能测试策略（至少3点）和系统性能测试策略（至少3点）。\n2. （10分）描述完整的测试流程（含关键活动）及需要提交的测试文档（至少4类）。"}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1611", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "新高考 B/附二：场景题（DS 魔改版）/手工速搓版", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 339, "text": "1.\n\n功能测试的策略包括：利用黑盒测试的等价类划分测试...，利用白盒测试的coverage测试...，针对...功能构造...的测试用例\n\n性能测试的策略：负载测试（虚拟学生用户逐步增加）、压力测试（比预期的校园服务人数多一倍）、尖峰测试（选在热门电影开播前的特定抢票时段进行测试）、持久测试（划定一个时间范围进行购票）、容量测试（sharding 分库分表、redis 缓存击穿缓存雪崩缓存穿透）\n\n1.\n\n完成的测试流程：搭建测试团队 —— 明确测试需求 —— 定义测试策略 —— 编写测试用例 —— 根据测试策略执行测试流程 —— 总结测试中存在的问题 —— 反馈给开发团队进行修复\n\n测试文档：测试计划、测试用例、BUG 报告、总结报告（Chapter 6 的标题）"}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1612", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "新高考 B/附二：场景题（DS 魔改版）/问题1：功能测试策略与性能测试策略/**功能测试策略**（至少3点）：", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 578, "text": "1. **用户端核心功能验证**\n\n - **学生身份认证测试**：验证学号与教务系统同步的准确性，包括合法学号登录、非法学号拦截、教务系统接口异常时的容错处理。\n - **在线选座与实时更新测试**：模拟多用户同时选座场景，确保座位状态实时同步，避免重复购票；测试座位图在不同设备（PC/移动端）的展示兼容性。\n - **订单取消与电子票核销测试**：验证开场前1小时免费取消的边界条件（如59分钟取消成功，61分钟失败）；测试二维码生成唯一性及核销后状态更新（如防止重复核销）。\n\n1. **管理端业务逻辑覆盖**\n\n - **影厅排期冲突检测**：测试同一影厅不同场次的时间重叠场景，系统是否自动提示冲突并禁止排期。\n - **动态票价策略验证**：检查学生票8折规则的正确性（如普通用户原价、学生用户自动折扣），以及价格调整后历史订单的金额一致性。\n - **数据统计完整性测试**：验证售票数据统计的实时性与准确性（如退票率计算、分时段销量汇总）。\n\n1. **异常场景与边界条件测试**\n\n - **高并发购票压力测试**：模拟选座高峰期（如热门影片首映）的多用户并发操作，确保系统无卡顿或数据丢失。\n - **网络异常恢复测试**：在选座过程中断网后恢复，验证系统是否自动同步最新座位状态并提示用户。\n\n---"}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1613", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "新高考 B/附二：场景题（DS 魔改版）/问题1：功能测试策略与性能测试策略/**性能测试策略**（至少3点）：", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 252, "text": "1. **并发用户承载能力测试**\n\n - 模拟1000+用户同时访问系统，测试购票流程的响应时间（如页面加载≤1秒，支付完成≤3秒），并监控服务器CPU/内存使用率是否在安全阈值内。\n\n1. **长时间稳定性测试**\n\n - 连续运行系统48小时，监测内存泄漏、数据库连接池耗尽等问题，确保无崩溃或性能衰减。\n\n1. **第三方接口性能验证**\n\n - 测试与教务系统接口的同步效率（如学号验证延迟≤500ms），以及支付网关（如支付宝/微信）在高并发下的成功率（≥99.9%）。\n\n---"}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1614", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "新高考 B/附二：场景题（DS 魔改版）/问题2：测试流程与测试文档/**完整的测试流程及关键活动**：", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 578, "text": "1. **需求分析与测试计划制定**\n\n - **关键活动**：梳理用户端与管理端需求，确定测试范围（如功能模块优先级）、资源分配（如测试环境搭建）。\n - **输出文档**：《测试计划书》（含测试目标、范围、资源、进度）。\n\n1. **测试用例设计与评审**\n\n - **关键活动**：编写覆盖正常/异常场景的测试用例（如学生认证成功/失败、票价动态调整验证），并组织开发与业务团队评审用例完整性。\n - **输出文档**：《测试用例集》（含步骤、预期结果、优先级）。\n\n1. **测试环境搭建与数据准备**\n\n - **关键活动**：部署与生产环境一致的测试环境（如Tomcat+MySQL），导入真实影厅排期、学生学号等测试数据。\n\n1. **测试执行与缺陷管理**\n\n - **关键活动**：分阶段执行功能测试（冒烟测试→全面测试→回归测试）与性能测试，使用JIRA等工具记录缺陷并跟踪修复。\n - **输出文档**：《缺陷跟踪报告》（含缺陷描述、严重等级、修复状态）。\n\n1. **验收测试与报告总结**\n\n - **关键活动**：邀请业务方进行用户验收测试（UAT），验证系统是否符合实际运营需求；汇总测试结果并分析风险。\n - **输出文档**：《测试总结报告》（含通过率、遗留问题、优化建议）。\n\n---"}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1615", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "新高考 B/附二：场景题（DS 魔改版）/问题2：测试流程与测试文档/**需要提交的测试文档**（至少4类）：", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 140, "text": "1. **《测试计划书》**：明确测试目标、范围、资源与时间表。\n2. **《测试用例集》**：详细描述测试场景、步骤及预期结果。\n3. **《缺陷跟踪报告》**：记录缺陷状态、修复进度与验证结果。\n4. **《性能测试报告》**：包含并发性能、响应时间、稳定性等指标。\n\n---"}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1616", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "新高考 B/附二：场景题（DS 魔改版）/**总结**", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 99, "text": "功能测试需覆盖用户端与管理端的核心逻辑与异常场景，性能测试需验证系统在高并发与长期运行下的稳定性。测试流程需遵循需求分析→用例设计→执行→验收的标准化路径，并提交完整的文档以支持系统上线与后续优化。"}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1617", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "样板卷 A/⚠️ 为什么条件组合的最小用例集是 7 个？", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 539, "text": "我们先来看最基本的分支覆盖的定义\n\n| a > 0 && b > 1 | F（1） | T（2） |\n|-|-|-|\n\n| c > 0 && a 0 ? | F（5） | T（7） | F（9） | T（11） |\n|-|-|-|-|-|\n| b > 1 ? | F（6） | F（8） | T（10） | T（12） |\n\n| c < 0 ? | F（13） | T（15） | F（17） | T（19） |\n|-|-|-|-|-|\n| a < 0 ? | F（14） | F（16） | T（18） | T（20） |\n\n条件组合覆盖。要求真值表这 20 种 T 和 F 至少出现一次\n\n| a | b | c | 覆盖的情况 |\n|-|-|-|-|\n| -1 | -2 | | （1）（5）（6）（8）（9）（18）（20） |\n| 1 | 2 | | （2）（7）（10）（11）（12）（14）（16） |\n| 1 | | -1 | （3）（7）（11）（15）（19） |\n| -1 | | 1 | （4）（13）（17）（18）（20） |\n| | | | |\n| | | | |\n| | | | |\n| | | | |"}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1618", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "样板卷 A/⚠️ 样板卷 A 的黑盒测试有笔误，在这里纠正一下", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 213, "text": "地区码地区码为 0086（剩下的照抄）地区码不为空且不为 0086prefixPrefix 存在非数字字符Prefix 不为 3 位Prefix 首位不为 1地区码为空（剩下的照抄）Prefix 次位小于 3postfixPostfix 有非数字字符Postfix 不为 8 位数字\n\n边界值：\n\nArea 为空\n\nArea 为 0086\n\nPrefix 为 130\n\nprefix 为 199\n\n后缀八个 0\n\n后缀八个 9"}
{"id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c::1619", "page_id": "docx::XVJ7wPRKDiGInlkxo1xc6DjPn0c", "title": "历年真题解析", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析", "section": "样板卷 A/⚠️ 题目问你测试策略怎么答？（搭队伍 — 定时间 — V 模型四大测试跑一遍）", "url": "https://a1npn29y3xu.feishu.cn/wiki/XVJ7wPRKDiGInlkxo1xc6DjPn0c", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::EY6vwLUFqiejCuk7y4ychL0Anzb::1620", "page_id": "docx::EY6vwLUFqiejCuk7y4ychL0Anzb", "title": "哭墙", "course": "大二下：廉颇老矣，尚能饭否", "path": "大二下：廉颇老矣，尚能饭否/哭墙", "section": "哭墙", "url": "https://a1npn29y3xu.feishu.cn/wiki/EY6vwLUFqiejCuk7y4ychL0Anzb", "source_type": "docx", "n_chars": 97, "text": "昔人已乘黄鹤去，此地空余黄鹤楼。\n\n黄鹤一去不复返，白云千载空悠悠。\n\n晴川历历汉阳树，芳草萋萋鹦鹉洲。\n\n日暮乡关何处是？烟波江上使人愁。\n\n**等大家考完，我们一起看美加墨世界杯淘汰赛😭**"}
{"id": "docx::D9hCw9HhvigfxKky77QcZdJCnze::1621", "page_id": "docx::D9hCw9HhvigfxKky77QcZdJCnze", "title": "回归课本", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本", "section": "回归课本", "url": "https://a1npn29y3xu.feishu.cn/wiki/D9hCw9HhvigfxKky77QcZdJCnze", "source_type": "docx", "n_chars": 84, "text": ""}
{"id": "docx::WILPwrUkhiEZRlkY5oLcaVH6n2V::1622", "page_id": "docx::WILPwrUkhiEZRlkY5oLcaVH6n2V", "title": "大二下：廉颇老矣，尚能饭否", "course": "大二下：廉颇老矣，尚能饭否", "path": "大二下：廉颇老矣，尚能饭否", "section": "所有看到这个飞书页面的人都能直接参与讲义编辑！", "url": "https://a1npn29y3xu.feishu.cn/wiki/WILPwrUkhiEZRlkY5oLcaVH6n2V", "source_type": "docx", "n_chars": 671, "text": "1. 把 K 书流散在 C5 C10 的手写笔记找回来，抢救性扫描并让 AI 重新梳理\n2. 未来，如我们所书，另起炉灶，自力更生！\n\n\n\n操作系统这门课复习的时候，书上的代码都要会吗\n\n反而重点是课后习题，比如说经典的 PV 题\n\n那计算机网络呢，重点是啥，感觉老师平时也不布置作业，感觉复习得很茫然\n\n也是课后题哦，因为我当时考试好多题都是课后题改编的\n\n计算机网络的复习反而极其纯朴：背诵现在你能拿到的所有英文版真题\n\n中文版没用\n\n必须是英文版\n\n从头背到尾\n\n那算法分析这门课呢\n\n首先，叠个甲\n\n我 24 年的所有笔记都是手写的\n\n是那种写完一支黑笔的纯手写\n\n这些笔记叠起来百来页一大沓，我全部出掉了\n\n所以你现在问我怎么复习大二下这些哼哈二将，我只能给大家思路，当然，如果大家能把流传的手写稿找回来，那更好\n\n教授我的老师上课质量极高，作业极少，PPT 课后习题质量极高\n\n我当时只做了四件事：全身心投入上课、反复刷作业和 PPT 真题、背诵 PPT、根据老师上课的内容同步刷力扣\n\n最终得分：90+ 班级前十\n\n算法课的思路讲完了，接下来就是 F4 了\n\n有没有uml焚决\n\n记住我的口诀\n\n1. 林老师的作业是高质量的真题素材\n2. 陶老师的复习课是仙人指路\n3. 以“设计 ATM 机“为核心思路，让 gemini 把所有的图都整理一遍，自己亲自上手画图"}
{"id": "docx::WILPwrUkhiEZRlkY5oLcaVH6n2V::1623", "page_id": "docx::WILPwrUkhiEZRlkY5oLcaVH6n2V", "title": "大二下：廉颇老矣，尚能饭否", "course": "大二下：廉颇老矣，尚能饭否", "path": "大二下：廉颇老矣，尚能饭否", "section": "所有看到这个飞书页面的人都能直接参与讲义编辑！", "url": "https://a1npn29y3xu.feishu.cn/wiki/WILPwrUkhiEZRlkY5oLcaVH6n2V", "source_type": "docx", "n_chars": 697, "text": "有uml焚决\n\n记住我的口诀\n\n1. 林老师的作业是高质量的真题素材\n2. 陶老师的复习课是仙人指路\n3. 以“设计 ATM 机“为核心思路，让 gemini 把所有的图都整理一遍，自己亲自上手画图\n4. 每年的名词解释题都不同，自己回归课本看黑色标粗的专有名词\n5. 如果嫌真题不够，请在网上搜索“软件设计师（中级）”职称考试，将所有 uml 的题整理成中文大题库，15 年的真题刷完题感就来了\n\n至于怎么整理，你们自己来，因为我没有上今年陶老师的课，我不知道具体切口\n\n每年的切口都不同\n\n编译技术\n\n应老师教的，质量特别高\n\n全身心投入上课、反复刷作业和期末真题、背诵 PPT\n\n编译原理的主线其实也比较清晰\n\n就是一段 C++ 代码怎么变成中间语言的\n\n用那个啥 cpp 的编译器的网站多敲多看\n\n计算机网络复习最简单\n\n直接逮着英文真题背诵\n\n然后再加上少许的湖科大网课，足量的课后习题以及适量的考研真题\n\ndone\n\n操作系统比计算机网络难的一点在于，不仅要背，而且要深入理解软硬件协同的机理\n\n1. wgh 老师的 ppt 务必拿下，先看复习课，再按照复习课回到 ppt 上背诵\n2. 在此基础上，所有的英文真题还是边刷边背\n3. 在英文真题背熟的基础上，去找考研 10 年真题，我们只刷这些题\n\n- “进程与线程” 尤其是 PV 大题，PV 大题最好提分了\n- “存储管理” 我相信大家计租基础雄厚\n- “文件管理” 这是最莫名其妙的点，反而建议踏踏实实回归 ppt 和课本，别整花活，最多补一点课后英文题\n- “死锁” 套路太固定了，来来回回就是死锁的四个条件 + 那几个算法"}
{"id": "docx::WILPwrUkhiEZRlkY5oLcaVH6n2V::1624", "page_id": "docx::WILPwrUkhiEZRlkY5oLcaVH6n2V", "title": "大二下：廉颇老矣，尚能饭否", "course": "大二下：廉颇老矣，尚能饭否", "path": "大二下：廉颇老矣，尚能饭否", "section": "所有看到这个飞书页面的人都能直接参与讲义编辑！", "url": "https://a1npn29y3xu.feishu.cn/wiki/WILPwrUkhiEZRlkY5oLcaVH6n2V", "source_type": "docx", "n_chars": 156, "text": "大家计租基础雄厚\n- “文件管理” 这是最莫名其妙的点，反而建议踏踏实实回归 ppt 和课本，别整花活，最多补一点课后英文题\n- “死锁” 套路太固定了，来来回回就是死锁的四个条件 + 那几个算法\n\n背诵强度：uml > 计网 > 操作系统 > 编译原理\n\n绝对难度：操作系统 > 编译原理 > 计网 > uml"}
{"id": "docx::BKHfw5sSOitWFtkhSnNcM0ngndh::1625", "page_id": "docx::BKHfw5sSOitWFtkhSnNcM0ngndh", "title": "小题突破：专业术语 Summary", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/小题突破：专业术语 Summary", "section": "Chapter 1", "url": "https://a1npn29y3xu.feishu.cn/wiki/BKHfw5sSOitWFtkhSnNcM0ngndh", "source_type": "docx", "n_chars": 340, "text": "\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::BKHfw5sSOitWFtkhSnNcM0ngndh::1626", "page_id": "docx::BKHfw5sSOitWFtkhSnNcM0ngndh", "title": "小题突破：专业术语 Summary", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/小题突破：专业术语 Summary", "section": "Chapter 2 & 6", "url": "https://a1npn29y3xu.feishu.cn/wiki/BKHfw5sSOitWFtkhSnNcM0ngndh", "source_type": "docx", "n_chars": 340, "text": "\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::BKHfw5sSOitWFtkhSnNcM0ngndh::1627", "page_id": "docx::BKHfw5sSOitWFtkhSnNcM0ngndh", "title": "小题突破：专业术语 Summary", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/小题突破：专业术语 Summary", "section": "Chapter 3 \\~ 5", "url": "https://a1npn29y3xu.feishu.cn/wiki/BKHfw5sSOitWFtkhSnNcM0ngndh", "source_type": "docx", "n_chars": 568, "text": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::BKHfw5sSOitWFtkhSnNcM0ngndh::1628", "page_id": "docx::BKHfw5sSOitWFtkhSnNcM0ngndh", "title": "小题突破：专业术语 Summary", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/小题突破：专业术语 Summary", "section": "Chapter 7", "url": "https://a1npn29y3xu.feishu.cn/wiki/BKHfw5sSOitWFtkhSnNcM0ngndh", "source_type": "docx", "n_chars": 283, "text": "\n\n\n\n\n\n\n\n"}
{"id": "docx::BKHfw5sSOitWFtkhSnNcM0ngndh::1629", "page_id": "docx::BKHfw5sSOitWFtkhSnNcM0ngndh", "title": "小题突破：专业术语 Summary", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/小题突破：专业术语 Summary", "section": "Chapter 8", "url": "https://a1npn29y3xu.feishu.cn/wiki/BKHfw5sSOitWFtkhSnNcM0ngndh", "source_type": "docx", "n_chars": 169, "text": "\n\n\n\n"}
{"id": "docx::BKHfw5sSOitWFtkhSnNcM0ngndh::1630", "page_id": "docx::BKHfw5sSOitWFtkhSnNcM0ngndh", "title": "小题突破：专业术语 Summary", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/小题突破：专业术语 Summary", "section": "Chapter 11 \\~ 13", "url": "https://a1npn29y3xu.feishu.cn/wiki/BKHfw5sSOitWFtkhSnNcM0ngndh", "source_type": "docx", "n_chars": 682, "text": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::BKHfw5sSOitWFtkhSnNcM0ngndh::1631", "page_id": "docx::BKHfw5sSOitWFtkhSnNcM0ngndh", "title": "小题突破：专业术语 Summary", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/小题突破：专业术语 Summary", "section": "Chapter 11 \\~ 13", "url": "https://a1npn29y3xu.feishu.cn/wiki/BKHfw5sSOitWFtkhSnNcM0ngndh", "source_type": "docx", "n_chars": 383, "text": "ishu.cn/file/JcCGbgutKoAqQsxh09bctnkungc)\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::BKHfw5sSOitWFtkhSnNcM0ngndh::1632", "page_id": "docx::BKHfw5sSOitWFtkhSnNcM0ngndh", "title": "小题突破：专业术语 Summary", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/小题突破：专业术语 Summary", "section": "Chapter 14 \\~ 16", "url": "https://a1npn29y3xu.feishu.cn/wiki/BKHfw5sSOitWFtkhSnNcM0ngndh", "source_type": "docx", "n_chars": 682, "text": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::BKHfw5sSOitWFtkhSnNcM0ngndh::1633", "page_id": "docx::BKHfw5sSOitWFtkhSnNcM0ngndh", "title": "小题突破：专业术语 Summary", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/小题突破：专业术语 Summary", "section": "Chapter 14 \\~ 16", "url": "https://a1npn29y3xu.feishu.cn/wiki/BKHfw5sSOitWFtkhSnNcM0ngndh", "source_type": "docx", "n_chars": 668, "text": "ishu.cn/file/ZtEDbgpzboDE1SxqXuRcNvlZnOc)\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::BKHfw5sSOitWFtkhSnNcM0ngndh::1634", "page_id": "docx::BKHfw5sSOitWFtkhSnNcM0ngndh", "title": "小题突破：专业术语 Summary", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/小题突破：专业术语 Summary", "section": "Chapter 14 \\~ 16", "url": "https://a1npn29y3xu.feishu.cn/wiki/BKHfw5sSOitWFtkhSnNcM0ngndh", "source_type": "docx", "n_chars": 212, "text": "ishu.cn/file/DO1rbvGNgohqlPxvjBIccpbXnDb)\n\n\n\n\n\n"}
{"id": "docx::CoA4wXGmMi7LNOkYTlNcrlkdnKd::1635", "page_id": "docx::CoA4wXGmMi7LNOkYTlNcrlkdnKd", "title": "彩蛋：暑期实习总结记", "course": "彩蛋：暑期实习总结记", "path": "彩蛋：暑期实习总结记", "section": "彩蛋：暑期实习总结记/前言：三分天注定，七分靠打拼", "url": "https://a1npn29y3xu.feishu.cn/wiki/CoA4wXGmMi7LNOkYTlNcrlkdnKd", "source_type": "docx", "n_chars": 569, "text": "2025 年 Kevin\n0210 开始针对暑期实习复习\n0416 第一次 HR 面\n0507 最后一场 HR 面\n笼统算起来两个多月了\n\n首先，大家认为，找工作最重要的因素是什么呢？\n\n八股背得6？算法能AK？项目很高级？\n\n不可否认的是，如果你要投递技术岗，那么这三个模块都需要在特定的领域有扎实的基础，都需要能做到和面试官顺利沟通，让面试官觉得你“深不见底”。\n\n但是，如果让Kevin学长来总结的话，Kevin 学长反而会觉得，**运气也是不可被忽略的因素。**“天时 地利 人和”缺一不可。因为求职不是“高考”，不是谁高分谁就一定能赢的。求职是一个**“匹配度校验”**的过程，本质是公司和求职者的**“双向选择”**。\n\n天时：针对你申请的岗位，这一年究竟是“暖季”还是“寒季”？（市场究竟是供过于求，还是供不应求）\n\n地利：你的本科学历是什么样的，研究生学历是什么样的？本科和研究生有没有突出的学术成果或者工程项目成果？\n\n人和：人和得从两个方面去谈\n\n针对求职者来说：求职者的技能水平是否达到了公司对应届毕业生的招聘标准\n\n针对面试官来说：求职者和面试官的沟通是否流畅，求职者是否能“看对眼”\n\n找工作的核心是面试官感觉你靠不靠谱，是否愿意和你做同事\n\n客观因素是无法左右的，Kevin学长只能从主观因素的视角提出一些总结"}
{"id": "docx::CoA4wXGmMi7LNOkYTlNcrlkdnKd::1636", "page_id": "docx::CoA4wXGmMi7LNOkYTlNcrlkdnKd", "title": "彩蛋：暑期实习总结记", "course": "彩蛋：暑期实习总结记", "path": "彩蛋：暑期实习总结记", "section": "彩蛋：暑期实习总结记/一、供需关系：哈耶克还在发力", "url": "https://a1npn29y3xu.feishu.cn/wiki/CoA4wXGmMi7LNOkYTlNcrlkdnKd", "source_type": "docx", "n_chars": 651, "text": "举个例子：\n\n以 Java 后端为代表的岗位是 供过于求\n\n以 Java 安卓客户端为代表的岗位确实 供不应求\n\n**越是供过于求的岗位，考核的苛刻程度就越高，要复习的技术点也越深，难度越大。**\n\n举个例子：某学长在美团招聘的时候填志愿是这样的\n\n第一志愿：Java 后端开发\n\n第二志愿：测试开发\n\n第三志愿：产品经理\n\n**笔试如果过了第二志愿的线，但没过第一志愿的线，那么直接取消第一志愿开第二志愿。因为有上万人投递美团的后端岗位，但是投递前端和算法岗位的人数总和甚至是后端岗位的 1/4 左右！**\n\n如果投递了**供过于求**的岗位，难度直接**翻倍**。\n\n##\n二、简历相关：让面试官觉得“你匹配”\n\n如何写出一份漂亮的简历呢？\n\n[如何写一份优秀的简历_哔哩哔哩_bilibili](https://www.bilibili.com/video/BV17nktYHEHD?spm_id_from=333.788.videopod.sections&vd_source=da1f2d78d73dfaae6ddfbcfe8e4801d8)\n\n[秋招两次被拒后，我学会了简历包装，秋意渐浓，记得加衣_哔哩哔哩_bilibili](https://www.bilibili.com/video/BV12u411g7Xt/?spm_id_from=333.337.search-card.all.click&vd_source=da1f2d78d73dfaae6ddfbcfe8e4801d8)"}
{"id": "docx::CoA4wXGmMi7LNOkYTlNcrlkdnKd::1637", "page_id": "docx::CoA4wXGmMi7LNOkYTlNcrlkdnKd", "title": "彩蛋：暑期实习总结记", "course": "彩蛋：暑期实习总结记", "path": "彩蛋：暑期实习总结记", "section": "彩蛋：暑期实习总结记/一、供需关系：哈耶克还在发力", "url": "https://a1npn29y3xu.feishu.cn/wiki/CoA4wXGmMi7LNOkYTlNcrlkdnKd", "source_type": "docx", "n_chars": 556, "text": "V12u411g7Xt/?spm_id_from=333.337.search-card.all.click&vd_source=da1f2d78d73dfaae6ddfbcfe8e4801d8)\n\n\n\n\n\n##\n三、八股相关：从泛泛而谈到深不见底\n\n[颠覆你认知的八股文回答_哔哩哔哩_bilibili](https://www.bilibili.com/video/BV19hCVY3En6?spm_id_from=333.788.videopod.sections&vd_source=da1f2d78d73dfaae6ddfbcfe8e4801d8)\n\n[背八股的核心原则，八股体系化，构建你的知识网络_哔哩哔哩_bilibili](https://www.bilibili.com/video/BV1YR6tY3E5n?spm_id_from=333.788.videopod.sections&vd_source=da1f2d78d73dfaae6ddfbcfe8e4801d8)"}
{"id": "docx::CoA4wXGmMi7LNOkYTlNcrlkdnKd::1638", "page_id": "docx::CoA4wXGmMi7LNOkYTlNcrlkdnKd", "title": "彩蛋：暑期实习总结记", "course": "彩蛋：暑期实习总结记", "path": "彩蛋：暑期实习总结记", "section": "彩蛋：暑期实习总结记/一、供需关系：哈耶克还在发力", "url": "https://a1npn29y3xu.feishu.cn/wiki/CoA4wXGmMi7LNOkYTlNcrlkdnKd", "source_type": "docx", "n_chars": 445, "text": "deo/BV1YR6tY3E5n?spm_id_from=333.788.videopod.sections&vd_source=da1f2d78d73dfaae6ddfbcfe8e4801d8)\n\n[怎么用最短的时间, 让面试官觉得你的八股深不见底_哔哩哔哩_bilibili](https://www.bilibili.com/video/BV12H6UYWEDF?spm_id_from=333.788.videopod.sections&vd_source=da1f2d78d73dfaae6ddfbcfe8e4801d8)\n\n[面试八股文实际在考察你的什么能力？八股文背的很痛苦？这样背才能对答如流_哔哩哔哩_bilibili](https://www.bilibili.com/video/BV1kEc4ezE8k?spm_id_from=333.788.videopod.sections&vd_source=da1f2d78d73dfaae6ddfbcfe8e4801d8)"}
{"id": "docx::CoA4wXGmMi7LNOkYTlNcrlkdnKd::1639", "page_id": "docx::CoA4wXGmMi7LNOkYTlNcrlkdnKd", "title": "彩蛋：暑期实习总结记", "course": "彩蛋：暑期实习总结记", "path": "彩蛋：暑期实习总结记", "section": "彩蛋：暑期实习总结记/一、供需关系：哈耶克还在发力/第一步：鱼皮面试训练营 HOT90", "url": "https://a1npn29y3xu.feishu.cn/wiki/CoA4wXGmMi7LNOkYTlNcrlkdnKd", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::CoA4wXGmMi7LNOkYTlNcrlkdnKd::1640", "page_id": "docx::CoA4wXGmMi7LNOkYTlNcrlkdnKd", "title": "彩蛋：暑期实习总结记", "course": "彩蛋：暑期实习总结记", "path": "彩蛋：暑期实习总结记", "section": "彩蛋：暑期实习总结记/一、供需关系：哈耶克还在发力/第二步：针对传统 Java 后端岗位，用 xiaolincoding 和黑马程序员进行补充", "url": "https://a1npn29y3xu.feishu.cn/wiki/CoA4wXGmMi7LNOkYTlNcrlkdnKd", "source_type": "docx", "n_chars": 243, "text": "[Java面试题介绍](https://xiaolincoding.com/interview/)\n\n[新版Java面试专题视频教程，java八股文面试全套真题+深度详解（含大厂高频面试真题）\\_哔哩哔哩_bilibili](https://www.bilibili.com/video/BV1yT411H7YK/?spm_id_from=333.337.search-card.all.click&vd_source=da1f2d78d73dfaae6ddfbcfe8e4801d8)"}
{"id": "docx::CoA4wXGmMi7LNOkYTlNcrlkdnKd::1641", "page_id": "docx::CoA4wXGmMi7LNOkYTlNcrlkdnKd", "title": "彩蛋：暑期实习总结记", "course": "彩蛋：暑期实习总结记", "path": "彩蛋：暑期实习总结记", "section": "彩蛋：暑期实习总结记/一、供需关系：哈耶克还在发力/第五步：如果前面的资料在面试中感觉太泛泛而谈了，请和 AI 大量沟通", "url": "https://a1npn29y3xu.feishu.cn/wiki/CoA4wXGmMi7LNOkYTlNcrlkdnKd", "source_type": "docx", "n_chars": 568, "text": "##\n四、项目相关：谁说 RPC 烂大街了？\n\n[实习工作 编程开发 如何准备项目_哔哩哔哩_bilibili](https://www.bilibili.com/video/BV1nBi2YcErN?spm_id_from=333.788.videopod.sections&vd_source=da1f2d78d73dfaae6ddfbcfe8e4801d8)\n\n[不同阶段如何准备项目? 项目烂大街怎么办? 三招教你给烂大街项目换皮_哔哩哔哩_bilibili](https://www.bilibili.com/video/BV1MpqnYuEoy?spm_id_from=333.788.videopod.sections&vd_source=da1f2d78d73dfaae6ddfbcfe8e4801d8)\n\n[外卖商城烂大街? 教你爆改_哔哩哔哩_bilibili](https://www.bilibili.com/video/BV1oPq8YGEem/?spm_id_from=333.337.search-card.all.click)\n\n**核心原则：面试官不是看你的项目是否烂大街，而是看你从这个项目中应用并掌握的技术要点！！！**\n\n##\n五、算法相关：爱拼才会赢\n\n[刷了1000多道算法题，分享我的心得。"}
{"id": "docx::CoA4wXGmMi7LNOkYTlNcrlkdnKd::1642", "page_id": "docx::CoA4wXGmMi7LNOkYTlNcrlkdnKd", "title": "彩蛋：暑期实习总结记", "course": "彩蛋：暑期实习总结记", "path": "彩蛋：暑期实习总结记", "section": "彩蛋：暑期实习总结记/一、供需关系：哈耶克还在发力/第五步：如果前面的资料在面试中感觉太泛泛而谈了，请和 AI 大量沟通", "url": "https://a1npn29y3xu.feishu.cn/wiki/CoA4wXGmMi7LNOkYTlNcrlkdnKd", "source_type": "docx", "n_chars": 648, "text": ".all.click)\n\n**核心原则：面试官不是看你的项目是否烂大街，而是看你从这个项目中应用并掌握的技术要点！！！**\n\n##\n五、算法相关：爱拼才会赢\n\n[刷了1000多道算法题，分享我的心得。希望这个视频能帮助你学习算法、坚持下来_哔哩哔哩_bilibili](https://www.bilibili.com/video/BV1Ku411z7VT?spm_id_from=333.788.recommend_more_video.17&vd_source=da1f2d78d73dfaae6ddfbcfe8e4801d8)\n\n[leetcode就是用来背的！\\_哔哩哔哩_bilibili](https://www.bilibili.com/video/BV1bV411R74j/?spm_id_from=333.337.search-card.all.click&vd_source=da1f2d78d73dfaae6ddfbcfe8e4801d8)\n\n[分享｜如何科学刷题？- 讨论 - 力扣（LeetCode）](http://leetcode.cn/circle/discuss/RvFUtj)\n\n[代码随想录](https://www.programmercarl.com/)\n\n[LeetCode 热题 100 - 学习计划 - 力扣（LeetCode）全球极客挚爱的技术成长平台](https://leetcode.cn/studyplan/top-100-liked/)"}
{"id": "docx::CoA4wXGmMi7LNOkYTlNcrlkdnKd::1643", "page_id": "docx::CoA4wXGmMi7LNOkYTlNcrlkdnKd", "title": "彩蛋：暑期实习总结记", "course": "彩蛋：暑期实习总结记", "path": "彩蛋：暑期实习总结记", "section": "彩蛋：暑期实习总结记/一、供需关系：哈耶克还在发力/第五步：如果前面的资料在面试中感觉太泛泛而谈了，请和 AI 大量沟通", "url": "https://a1npn29y3xu.feishu.cn/wiki/CoA4wXGmMi7LNOkYTlNcrlkdnKd", "source_type": "docx", "n_chars": 562, "text": "[LeetCode 热题 100 - 学习计划 - 力扣（LeetCode）全球极客挚爱的技术成长平台](https://leetcode.cn/studyplan/top-100-liked/)\n\n[面试经典 150 题 - 学习计划 - 力扣（LeetCode）全球极客挚爱的技术成长平台](https://leetcode.cn/studyplan/top-interview-150/)\n\n[剑指 Offer（第二版）](https://github.com/JiashuWu/Books/blob/master/Algorithms%20and%20Data%20Structures/%E5%89%91%E6%8C%87offer_%E7%AC%AC%E4%BA%8C%E7%89%88.pdf)\n\n[剑指offer_在线编程_牛客网](https://www.nowcoder.com/exam/oj/ta?page=1&tpId=13&type=13)\n\n[经典必刷编程题库_在线编译+题解_牛客题霸_牛客网](https://www.nowcoder.com/ta/classic-code)\n\n"}
{"id": "docx::W6cpw2MqViW8Q6kvdOZc95m2nqb::1644", "page_id": "docx::W6cpw2MqViW8Q6kvdOZc95m2nqb", "title": "拓展：各个编程语言是怎么与 SQL 联系起来的？", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（二） Chapter 03 ~ 05 SQL 专题/拓展：各个编程语言是怎么与 SQL 联系起来的？", "section": "拓展：各个编程语言是怎么与 SQL 联系起来的？", "url": "https://a1npn29y3xu.feishu.cn/wiki/W6cpw2MqViW8Q6kvdOZc95m2nqb", "source_type": "docx", "n_chars": 145, "text": "拓展：各个编程语言是怎么与 SQL 联系起来的？\n\n序：笔者在本地的 MySQL 的 springcloud 的 schema 下创建了一张 tb_user 表，存的信息长这样\n\n"}
{"id": "docx::W6cpw2MqViW8Q6kvdOZc95m2nqb::1645", "page_id": "docx::W6cpw2MqViW8Q6kvdOZc95m2nqb", "title": "拓展：各个编程语言是怎么与 SQL 联系起来的？", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（二） Chapter 03 ~ 05 SQL 专题/拓展：各个编程语言是怎么与 SQL 联系起来的？", "section": "Java/Maven 配置", "url": "https://a1npn29y3xu.feishu.cn/wiki/W6cpw2MqViW8Q6kvdOZc95m2nqb", "source_type": "docx", "n_chars": 173, "text": "```XML\n\n 4.0.0\n\n org.example\n dbdemo\n 1.0-SNAPSHOT\n\n mysql\n mysql-connector-java\n 8.0.23\n\n 8\n 8\n UTF-8\n\n```"}
{"id": "docx::W6cpw2MqViW8Q6kvdOZc95m2nqb::1646", "page_id": "docx::W6cpw2MqViW8Q6kvdOZc95m2nqb", "title": "拓展：各个编程语言是怎么与 SQL 联系起来的？", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（二） Chapter 03 ~ 05 SQL 专题/拓展：各个编程语言是怎么与 SQL 联系起来的？", "section": "Java/Java 代码", "url": "https://a1npn29y3xu.feishu.cn/wiki/W6cpw2MqViW8Q6kvdOZc95m2nqb", "source_type": "docx", "n_chars": 619, "text": "```Java\npackage org.example;\n\nimport java.sql.*;\n\npublic class Main {\n\n public static void main(String[] args) {\n // 数据库连接信息\n String schema = \"自己填写对应的schema\";\n String url = \"jdbc:mysql://localhost:3306/\" + schema;\n String username = \"自己填写对应的用户名\";\n String password = \"自己填写对应的密码\";\n\n // SQL 查询语句\n String sql = \"SELECT * FROM tb_user WHERE id = ?\";\n\n // 加载 MySQL JDBC 驱动\n try {\n Class.forName(\"com.mysql.cj.jdbc.Driver\");\n } catch (ClassNotFoundException e) {\n e.printStackTrace();\n return;\n }\n\n // 建立连接"}
{"id": "docx::W6cpw2MqViW8Q6kvdOZc95m2nqb::1647", "page_id": "docx::W6cpw2MqViW8Q6kvdOZc95m2nqb", "title": "拓展：各个编程语言是怎么与 SQL 联系起来的？", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（二） Chapter 03 ~ 05 SQL 专题/拓展：各个编程语言是怎么与 SQL 联系起来的？", "section": "Java/Java 代码", "url": "https://a1npn29y3xu.feishu.cn/wiki/W6cpw2MqViW8Q6kvdOZc95m2nqb", "source_type": "docx", "n_chars": 683, "text": "FoundException e) {\n e.printStackTrace();\n return;\n }\n\n // 建立连接\n try (Connection connection = DriverManager.getConnection(url, username, password);\n PreparedStatement preparedStatement = connection.prepareStatement(sql)) {\n\n // 设置 SQL 查询参数\n preparedStatement.setInt(1, 1);\n\n // 执行查询\n try (ResultSet resultSet = preparedStatement.executeQuery()) {\n while (resultSet.next()) {\n // 假设有一个名为 \"name\" 的列\n String name = resultSet.getString(\"username\");\n // 打印查询结果\n System.out.println(\"Name: \" + name);"}
{"id": "docx::W6cpw2MqViW8Q6kvdOZc95m2nqb::1648", "page_id": "docx::W6cpw2MqViW8Q6kvdOZc95m2nqb", "title": "拓展：各个编程语言是怎么与 SQL 联系起来的？", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（二） Chapter 03 ~ 05 SQL 专题/拓展：各个编程语言是怎么与 SQL 联系起来的？", "section": "Java/Java 代码", "url": "https://a1npn29y3xu.feishu.cn/wiki/W6cpw2MqViW8Q6kvdOZc95m2nqb", "source_type": "docx", "n_chars": 221, "text": "\"username\");\n // 打印查询结果\n System.out.println(\"Name: \" + name);\n }\n }\n } catch (SQLException e) {\n e.printStackTrace();\n }\n }\n}\n```"}
{"id": "docx::W6cpw2MqViW8Q6kvdOZc95m2nqb::1649", "page_id": "docx::W6cpw2MqViW8Q6kvdOZc95m2nqb", "title": "拓展：各个编程语言是怎么与 SQL 联系起来的？", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（二） Chapter 03 ~ 05 SQL 专题/拓展：各个编程语言是怎么与 SQL 联系起来的？", "section": "Python", "url": "https://a1npn29y3xu.feishu.cn/wiki/W6cpw2MqViW8Q6kvdOZc95m2nqb", "source_type": "docx", "n_chars": 666, "text": "```Plain Text\npip install PyMySQL\n```\n\n```Python\nimport pymysql\n\ndef connect_fetch():\n try:\n # 连接数据库\n connection = pymysql.connect(\n host='localhost',\n user='自己填写对应的用户名',\n password='自己填写对应的密码',\n database='自己填写对应的数据库名',\n charset='utf8mb4',\n cursorclass=pymysql.cursors.DictCursor\n )\n\n with connection:\n with connection.cursor() as cursor:\n # 执行查询\n sql = \"SELECT * FROM tb_user WHERE id = %s\"\n cursor.execute(sql, (1,))\n\n # 获取查询结果\n result = cursor.fetchone()\n if result:"}
{"id": "docx::W6cpw2MqViW8Q6kvdOZc95m2nqb::1650", "page_id": "docx::W6cpw2MqViW8Q6kvdOZc95m2nqb", "title": "拓展：各个编程语言是怎么与 SQL 联系起来的？", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（二） Chapter 03 ~ 05 SQL 专题/拓展：各个编程语言是怎么与 SQL 联系起来的？", "section": "Python", "url": "https://a1npn29y3xu.feishu.cn/wiki/W6cpw2MqViW8Q6kvdOZc95m2nqb", "source_type": "docx", "n_chars": 327, "text": ",))\n\n # 获取查询结果\n result = cursor.fetchone()\n if result:\n print(\"查询结果：\", result)\n else:\n print(\"没有找到 id = 1 的数据\")\n\n except pymysql.MySQLError as e:\n print(\"连接或查询失败：\", e)\n\nif __name__ == \"__main__\":\n connect_fetch()\n```"}
{"id": "docx::W6cpw2MqViW8Q6kvdOZc95m2nqb::1651", "page_id": "docx::W6cpw2MqViW8Q6kvdOZc95m2nqb", "title": "拓展：各个编程语言是怎么与 SQL 联系起来的？", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（二） Chapter 03 ~ 05 SQL 专题/拓展：各个编程语言是怎么与 SQL 联系起来的？", "section": "Rust", "url": "https://a1npn29y3xu.feishu.cn/wiki/W6cpw2MqViW8Q6kvdOZc95m2nqb", "source_type": "docx", "n_chars": 577, "text": "\n\n支持驱动 MySQL, PostgreSQL, SQLite\n\n```Rust\n#[derive(Insertable)]\n#[diesel(table_name = users)]\nstruct NewUser {\n name: &'a str,\n hair_color: Option,\n}\nlet new_users = vec![\n NewUser { name: \"Sean\", hair_color: Some(\"Black\") },\n NewUser { name: \"Gordon\", hair_color: None },\n];\ninsert_into(users)\n .values(&new_users)\n .execute(&mut connection);\n```\n\nEqual to\n\n```SQL\nINSERT INTO users (name, hair_color) VALUES\n ('Sean', 'Black'),\n ('Gordon', DEFAULT)\n```"}
{"id": "docx::W6cpw2MqViW8Q6kvdOZc95m2nqb::1652", "page_id": "docx::W6cpw2MqViW8Q6kvdOZc95m2nqb", "title": "拓展：各个编程语言是怎么与 SQL 联系起来的？", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/DB 讲义（二） Chapter 03 ~ 05 SQL 专题/拓展：各个编程语言是怎么与 SQL 联系起来的？", "section": "框架使开发更简易", "url": "https://a1npn29y3xu.feishu.cn/wiki/W6cpw2MqViW8Q6kvdOZc95m2nqb", "source_type": "docx", "n_chars": 102, "text": "在现实生活中，这一些代码被进一步地封装到框架了，开发者可以做到开箱即用✅\n\nJava - Spring - JpaRepository / MyBatis\n\nPython - Flask / Django"}
{"id": "docx::EDJTwsWQ2iFCQrkDfq2cols4n9g::1653", "page_id": "docx::EDJTwsWQ2iFCQrkDfq2cols4n9g", "title": "最后一夜", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/最后一夜", "section": "最后一夜", "url": "https://a1npn29y3xu.feishu.cn/wiki/EDJTwsWQ2iFCQrkDfq2cols4n9g", "source_type": "docx", "n_chars": 687, "text": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n**7 categories of design decisions ?**\n\n**ACDMMBC**\n\nAllocation\n\nCoordinate\n\nData Model\n\nManagement\n\nMapping\n\nBinding"}
{"id": "docx::EDJTwsWQ2iFCQrkDfq2cols4n9g::1654", "page_id": "docx::EDJTwsWQ2iFCQrkDfq2cols4n9g", "title": "最后一夜", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/最后一夜", "section": "最后一夜", "url": "https://a1npn29y3xu.feishu.cn/wiki/EDJTwsWQ2iFCQrkDfq2cols4n9g", "source_type": "docx", "n_chars": 676, "text": "esign decisions ?**\n\n**ACDMMBC**\n\nAllocation\n\nCoordinate\n\nData Model\n\nManagement\n\nMapping\n\nBinding\n\nChoice of Technology\n\n**How to reduce risks ?**\n\n化繁为简\n\nAvailability\n\nSecurity\n\n平衡性能和可拓展性\n\n采用文档跟踪进度并与团队沟通\n\n**可用性**\n\n源：内外的人、软硬件、基础设施、物理环境\n\n激励：错误 —— 忽略、崩溃、错误时间、错误响应\n\n工件：处理器、交流频道、永久存储、进程\n\n响应：发现错误（日志 + 通知），修复错误（禁源、暂停、掩盖、在被损毁模式）\n\n响应度量：可用时间百分比 + 检测错误时间间隔 + 不可用百分比\n\n**策略（软件看病）**\n\n输入：错误，输出：错误被掩盖或修复\n\n主策略：检测错误、修复错误（准备修复、重新引入）、预防错误\n\n**How to detect faults ?**\n\n- Ping / Echo\n- Monitor\n- Heartbeat\n- Timestamp\n- Condition Monitoring\n- Voting\n- Exception Detection\n- Self - Test\n\n**性能**\n\n源：内外部系统\n\n激励：周期性或者 sporadic 或者 stochastic 事件\n\n制品：系统的一个或者多个组成部分\n\n环境：四种操作模式（正常、紧急、峰值、过载）\n\n响应：进程事件、服务层级改变"}
{"id": "docx::EDJTwsWQ2iFCQrkDfq2cols4n9g::1655", "page_id": "docx::EDJTwsWQ2iFCQrkDfq2cols4n9g", "title": "最后一夜", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/最后一夜", "section": "最后一夜", "url": "https://a1npn29y3xu.feishu.cn/wiki/EDJTwsWQ2iFCQrkDfq2cols4n9g", "source_type": "docx", "n_chars": 611, "text": "外部系统\n\n激励：周期性或者 sporadic 或者 stochastic 事件\n\n制品：系统的一个或者多个组成部分\n\n环境：四种操作模式（正常、紧急、峰值、过载）\n\n响应：进程事件、服务层级改变\n\n响应度量：延迟、ddl、throughput、jitter、失误率\n\n**策略（开源节流）**\n\n管理资源（开源）\n\n控制资源需求（节流）\n\n**How Service Discovery works ？**\n\n必要条件\n\n被搜索到的实体希望能被找到\n\n被搜索到的实体必须有辨别标识\n\n- 由寻找者发起\n\n - 泛洪\n - 轮询\n- 由被寻找者发起\n\n - 不断地或者周期性的广告\n - 新的实体主动向已有成员投送广告\n\n - 需要有检测到新的实体的能力\n- 采用注册机制\n\n\n\n**ATAM (Architectural reasons)**\n\n背景：架构者不需要对架构或者商业目标清晰、系统不必完全创建、有大量干系人参与\n\n主要输出：① 一组风险 / 非风险 ② 一组风险主题\n\n其他输出：① 具体的架构表示 ② 商业目标的架构表示 ③ 优先化的 QA 需求 ④ 架构决策到质量需求的映射 ⑤ 一组 identified sensitivity 以及 tradeoff points\n\n执行步骤"}
{"id": "docx::EDJTwsWQ2iFCQrkDfq2cols4n9g::1656", "page_id": "docx::EDJTwsWQ2iFCQrkDfq2cols4n9g", "title": "最后一夜", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/最后一夜", "section": "最后一夜", "url": "https://a1npn29y3xu.feishu.cn/wiki/EDJTwsWQ2iFCQrkDfq2cols4n9g", "source_type": "docx", "n_chars": 666, "text": "的架构表示 ② 商业目标的架构表示 ③ 优先化的 QA 需求 ④ 架构决策到质量需求的映射 ⑤ 一组 identified sensitivity 以及 tradeoff points\n\n执行步骤\n\n介绍 ATAM —— 介绍业务驱动因素 —— 介绍架构 —— 识别架构方法 —— 生成效用树 —— 分析结构方法 —— 头脑风暴（优先排序场景） —— 分析架构方法 —— 呈现结果\n\n**Participant's Roles**\n\n评估团队 3 — 5 人\n\n决策者 PM Architect Customer\n\n架构干系人：\n\n① 开发者、测试人员、集成人员、维护人员、性能工程师、使用者、系统构造者\n\n② 去架构特定的 QA 目标\n\n③ 大公司 12 —— 15 干系人\n\n**the usage of Utility Tree.**\n\n用于识别 ASR 相关内容\n\n根节点（Utility） —— QA 层 —— 属性定义（评价标准） —— ASR\n\n**Definition, concepts, and steps (procedure) of ASRs, ADD**\n\n**ASRs**\n\n1. QAW 表示和介绍\n2. 商业和目标表示\n3. 架构计划表示\n4. 架构驱动定义\n5. 场景头脑风暴\n6. 场景 Consolidation\n7. 场景优先级表示\n8. 场景重定义\n\n**ADD 五步走**\n\n输入：需求 FQC 功能、质量、限制\n\n输出：容器 RIF 职责、交互、信息流\n\n1. 选择系统的某个元素去设计"}
{"id": "docx::EDJTwsWQ2iFCQrkDfq2cols4n9g::1657", "page_id": "docx::EDJTwsWQ2iFCQrkDfq2cols4n9g", "title": "最后一夜", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/最后一夜", "section": "最后一夜", "url": "https://a1npn29y3xu.feishu.cn/wiki/EDJTwsWQ2iFCQrkDfq2cols4n9g", "source_type": "docx", "n_chars": 687, "text": "lidation\n7. 场景优先级表示\n8. 场景重定义\n\n**ADD 五步走**\n\n输入：需求 FQC 功能、质量、限制\n\n输出：容器 RIF 职责、交互、信息流\n\n1. 选择系统的某个元素去设计\n2. 通过 Utility Tree 从被选择的 element 中辨别 ASRs\n3. 生成一个设计解决方案\n4. 为下一个迭代选择输入\n5. 重复 1～4 步\n\n**QAW 的八步走**\n\n1. QAW 展示和介绍\n2. 业务任务介绍\n3. 架构计划介绍\n4. 识别架构驱动因素\n5. 场景头脑风暴\n6. 场景整合\n7. 场景优先级排序\n8. 场景细化\n\n**Software architecture's definition and concept**\n\nSA = Set of software structures\n\nStructure = A set of elements held together by a relation\n\n**Relationships between Pattern and Tactics**\n\nPattern = \"packages\" of tactics → Tradeoff are considered\n\nPermit reuse\n\nContext + Problem + Solution\n\nTactics = design decision, affects a quality attribute response\n\na design decision for a single quality attribute"}
{"id": "docx::EDJTwsWQ2iFCQrkDfq2cols4n9g::1658", "page_id": "docx::EDJTwsWQ2iFCQrkDfq2cols4n9g", "title": "最后一夜", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/最后一夜", "section": "最后一夜", "url": "https://a1npn29y3xu.feishu.cn/wiki/EDJTwsWQ2iFCQrkDfq2cols4n9g", "source_type": "docx", "n_chars": 127, "text": "n decision, affects a quality attribute response\n\na design decision for a single quality attribute\n\ndoes not consider tradeoffs"}
{"id": "docx::DmT3w76jGi27OxkLlfocaT1PnAg::1659", "page_id": "docx::DmT3w76jGi27OxkLlfocaT1PnAg", "title": "最后一夜", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/最后一夜", "section": "手写版", "url": "https://a1npn29y3xu.feishu.cn/wiki/DmT3w76jGi27OxkLlfocaT1PnAg", "source_type": "docx", "n_chars": 511, "text": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::DmT3w76jGi27OxkLlfocaT1PnAg::1660", "page_id": "docx::DmT3w76jGi27OxkLlfocaT1PnAg", "title": "最后一夜", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/最后一夜", "section": "揭榜挂帅，欢迎直接评论", "url": "https://a1npn29y3xu.feishu.cn/wiki/DmT3w76jGi27OxkLlfocaT1PnAg", "source_type": "docx", "n_chars": 674, "text": "概念题考点：\n\n已经考过的\n\nScenario testing\n\nVersion Control\n\n大胆猜测版\n\nBasic Path Coverage\n\n简答题考点：\n\n考过的：\n\n1. Why software testing is not just a technical problem\n2. Test Planning Process\n3. What is Software Testing Automation? Why do we need automated testing?\n4. What is Software Maintenance？List Catagories of software maintenance. List some methods to improve the maintenance of the system?\n5. Bug management process. List the process of Software Configuration Management\n6. Relationship between Software Testing and SQA\n7. How to finish unit testing?\n\n场景题考点：（能不能认为是固定四大问呢）\n\n1. functional testing strategy\n2. system performance testing strategy.\n3. testing process\n4. testing document."}
{"id": "docx::DmT3w76jGi27OxkLlfocaT1PnAg::1661", "page_id": "docx::DmT3w76jGi27OxkLlfocaT1PnAg", "title": "最后一夜", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/最后一夜", "section": "揭榜挂帅，欢迎直接评论", "url": "https://a1npn29y3xu.feishu.cn/wiki/DmT3w76jGi27OxkLlfocaT1PnAg", "source_type": "docx", "n_chars": 203, "text": "l testing strategy\n2. system performance testing strategy.\n3. testing process\n4. testing document.\n\n软件维护类型（改正性/适应性/完善性/预防性维护）\n\n测试流程（单元测试→集成测试→系统测试→验收测试）\n\n验收测试流程（兼容性测试要点、用户参与环节）\n\n维护困难与可维护性提升方法（文档规范、结构化设计）"}
{"id": "docx::DmT3w76jGi27OxkLlfocaT1PnAg::1662", "page_id": "docx::DmT3w76jGi27OxkLlfocaT1PnAg", "title": "最后一夜", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/最后一夜", "section": "揭榜挂帅，欢迎直接评论/DS 速通版/概念题考点（已考过）", "url": "https://a1npn29y3xu.feishu.cn/wiki/DmT3w76jGi27OxkLlfocaT1PnAg", "source_type": "docx", "n_chars": 193, "text": "1. **Scenario Testing（场景测试）**\n 基于真实使用场景设计测试用例，验证系统在复杂业务流程中的表现。例如，模拟用户登录、支付、数据交互等完整流程，检查系统集成性和容错性。\n2. **Version Control（版本控制）**\n 用于管理软件代码和文档的变更历史，确保测试环境与开发版本一致，避免因版本混乱导致缺陷遗漏。常用工具如Git、SVN。\n\n---"}
{"id": "docx::DmT3w76jGi27OxkLlfocaT1PnAg::1663", "page_id": "docx::DmT3w76jGi27OxkLlfocaT1PnAg", "title": "最后一夜", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/最后一夜", "section": "揭榜挂帅，欢迎直接评论/DS 速通版/简答题考点（已考过）", "url": "https://a1npn29y3xu.feishu.cn/wiki/DmT3w76jGi27OxkLlfocaT1PnAg", "source_type": "docx", "n_chars": 691, "text": "1. **Why software testing is not just a technical problem**\n\n - **非技术因素**：测试涉及团队协作、需求沟通、资源管理（如测试环境配置）和风险预估。\n - **用户视角**：需理解用户需求，验证功能是否符合业务目标，而不仅是代码正确性。\n - **经济性**：需权衡测试成本与质量，选择“足够好”（Good Enough）的测试策略。\n2. **Test Planning Process**\n\n - **步骤**：需求分析 → 制定测试范围/策略 → 设计测试用例 → 分配资源（设备、工具、人员） → 执行测试 → 缺陷管理与报告。\n - **核心输出**：测试计划文档、测试用例集、风险评估报告。\n3. **What is Software Testing Automation? Why do we need it?**\n\n - **定义**：通过脚本或工具自动执行测试用例，替代人工重复操作。\n - **必要性**：\n\n - 提高效率，缩短回归测试时间；\n - 增强覆盖率（如边界值、复杂场景）；\n - 支持持续集成/交付（CI/CD）。\n4. **Software Maintenance & Improvement**\n\n - **维护类型**：\n\n - **改正性维护**：修复运行中发现的缺陷；\n - **适应性维护**：适应新环境（如操作系统升级）；\n - **完善性维护**：优化性能或功能；"}
{"id": "docx::DmT3w76jGi27OxkLlfocaT1PnAg::1664", "page_id": "docx::DmT3w76jGi27OxkLlfocaT1PnAg", "title": "最后一夜", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/最后一夜", "section": "揭榜挂帅，欢迎直接评论/DS 速通版/简答题考点（已考过）", "url": "https://a1npn29y3xu.feishu.cn/wiki/DmT3w76jGi27OxkLlfocaT1PnAg", "source_type": "docx", "n_chars": 673, "text": "护类型**：\n\n - **改正性维护**：修复运行中发现的缺陷；\n - **适应性维护**：适应新环境（如操作系统升级）；\n - **完善性维护**：优化性能或功能；\n - **预防性维护**：预防未来潜在问题。\n - **改进方法**：\n\n - 规范文档（需求/设计/测试报告）；\n - 模块化设计降低耦合度；\n - 使用自动化测试工具减少回归成本。\n5. **Bug Management & SCM Process**\n\n - **缺陷管理流程**：提交 → 分配 → 确认 → 修复 → 验证 → 关闭。\n - **软件配置管理（SCM）流程**：\n\n 1. 标识配置项（代码、文档等）；\n 2. 版本控制与变更记录；\n 3. 审计与状态报告；\n 4. 发布管理。\n6. **Relationship between Testing and SQA**\n\n - **测试**：技术活动，聚焦缺陷发现与修复，属于SQA的子集。\n - **SQA（软件质量保证）**：管理活动，覆盖全生命周期（需求评审、过程监控、标准制定），确保质量目标的系统性达成。\n7. **How to finish unit testing?**\n\n - **步骤**：\n\n 1. 确定测试范围（单个函数/类）；\n 2. 设计测试用例（覆盖逻辑分支、异常输入）；\n 3. 使用框架（如JUnit）执行测试；"}
{"id": "docx::DmT3w76jGi27OxkLlfocaT1PnAg::1665", "page_id": "docx::DmT3w76jGi27OxkLlfocaT1PnAg", "title": "最后一夜", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/最后一夜", "section": "揭榜挂帅，欢迎直接评论/DS 速通版/简答题考点（已考过）", "url": "https://a1npn29y3xu.feishu.cn/wiki/DmT3w76jGi27OxkLlfocaT1PnAg", "source_type": "docx", "n_chars": 172, "text": "g?**\n\n - **步骤**：\n\n 1. 确定测试范围（单个函数/类）；\n 2. 设计测试用例（覆盖逻辑分支、异常输入）；\n 3. 使用框架（如JUnit）执行测试；\n 4. 静态分析（代码审查）+动态测试（覆盖率分析）。\n - **工具**：Mock对象模拟依赖项（如Mockito）。\n\n---"}
{"id": "docx::DmT3w76jGi27OxkLlfocaT1PnAg::1666", "page_id": "docx::DmT3w76jGi27OxkLlfocaT1PnAg", "title": "最后一夜", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/最后一夜", "section": "揭榜挂帅，欢迎直接评论/DS 速通版/场景题考点（固定四大问）", "url": "https://a1npn29y3xu.feishu.cn/wiki/DmT3w76jGi27OxkLlfocaT1PnAg", "source_type": "docx", "n_chars": 443, "text": "1. **Functional Testing Strategy**\n\n - **方法**：等价类划分、边界值分析、因果图法；\n - **示例**：登录功能需覆盖有效/无效输入、密码加密显示、多浏览器兼容性。\n2. **System Performance Testing Strategy**\n\n - **指标**：响应时间、吞吐量、并发用户数；\n - **工具**：JMeter模拟负载，LoadRunner分析瓶颈；\n - **场景**：高并发下单、大数据量查询。\n3. **Testing Process**\n\n - **阶段**：单元测试（代码逻辑）→ 集成测试（模块交互）→ 系统测试（全局功能/性能）→ 验收测试（用户验证）。\n4. **Testing Document**\n\n - **关键文档**：测试计划、用例表、缺陷报告、总结报告；\n - **管理工具**：JIRA跟踪缺陷，Confluence归档文档。\n\n---"}
{"id": "docx::DmT3w76jGi27OxkLlfocaT1PnAg::1667", "page_id": "docx::DmT3w76jGi27OxkLlfocaT1PnAg", "title": "最后一夜", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/最后一夜", "section": "揭榜挂帅，欢迎直接评论/DS 速通版/其他高频考点", "url": "https://a1npn29y3xu.feishu.cn/wiki/DmT3w76jGi27OxkLlfocaT1PnAg", "source_type": "docx", "n_chars": 243, "text": "- **软件维护类型**：改正性、适应性、完善性、预防性。\n- **测试流程**：单元→集成→系统→验收测试。\n- **验收测试要点**：\n\n - **兼容性**：跨OS/浏览器/设备验证；\n - **用户参与**：UAT（用户验收测试）环节，确认需求实现。\n- **维护困难与改进**：\n\n - **难点**：文档缺失、代码耦合度高；\n - **改进**：代码重构、自动化回归测试、完善文档体系。\n\n以上内容综合了多个权威来源，建议结合具体案例和实践加深理解。"}
{"id": "docx::HI4ZwZnVEiuazZkU8wEcat8Vn5f::1668", "page_id": "docx::HI4ZwZnVEiuazZkU8wEcat8Vn5f", "title": "未来，如我们所书", "course": "大二下：廉颇老矣，尚能饭否", "path": "大二下：廉颇老矣，尚能饭否/未来，如我们所书", "section": "未来，如我们所书", "url": "https://a1npn29y3xu.feishu.cn/wiki/HI4ZwZnVEiuazZkU8wEcat8Vn5f", "source_type": "docx", "n_chars": 111, "text": "\n\n我这边是没问题的，你这边再看看？"}
{"id": "docx::ODmGwWNAJiltmjkusxKcHsUenid::1669", "page_id": "docx::ODmGwWNAJiltmjkusxKcHsUenid", "title": "本科生涯完结撒花：试卷快速回忆版", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析/本科生涯完结撒花：试卷快速回忆版", "section": "本科生涯完结撒花：试卷快速回忆版", "url": "https://a1npn29y3xu.feishu.cn/wiki/ODmGwWNAJiltmjkusxKcHsUenid", "source_type": "docx", "n_chars": 687, "text": "软件测试 2025 回忆版\n\n名词解析\n1. Fault Error Failure\n2. Test Plan\n3. EP\n4. Branch Testing\n5. Scenario Testing\n简答题\n\n1. 软件测试人员的目标是什么\n2. 请对比 V 模型和 W 模型\n3. 静态测试和动态测试的区别？请举个例子说明区别？\n4. 请你指出软件常见的多个性能问题\n5. Maintainance CAPP\n白盒测试\n\n白盒测试：考的是讲义原题，iR 和 iT 的那个，点就送（注意，第一个if之后加个break）\n\n黑盒测试\n请你阅读材料 回答以下问题\n在京东网购的过程中，总共有以下四种 Cause\n是京东会员\n购买的商品超过 100 块钱\n选择“e 邮”\n在 618 扫货\n以下四种 Effects\n如果你满足以上4个条件 包邮\n如果你不符合最后一个条件，但符合前三个条件，邮费半价\n如果你不是会员，但是符合最后三个条件，邮费半价\n其他情况按原价交邮费\n\n综合题\n你开发了一个会议签到小程序，请阅读材料回答以下问题\n会议签到小程序需要同时支持5万个人的签到以及会议预定，这个小程序 它的签到功能要在两秒之内搞定，这个小程序会议预定之后，必须立即向预订者的邮箱里面发邮件。这个小程序还需要符合以下特点 但我忘了\n请你阅读材料 回答以下问题\n\n第一题：请问你会使用什么类型的系统测试？为什么会选择这一种类型的系统测试\n\n第二题：请你从五个角度来描述你的测试流程，这五个角度分别是：测试流程、测试计划、测试文档、测试工具、测试总结\n\n第三题：请你针对签到功能设计测试用例"}
{"id": "docx::ODmGwWNAJiltmjkusxKcHsUenid::1670", "page_id": "docx::ODmGwWNAJiltmjkusxKcHsUenid", "title": "本科生涯完结撒花：试卷快速回忆版", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/历年真题解析/本科生涯完结撒花：试卷快速回忆版", "section": "本科生涯完结撒花：试卷快速回忆版", "url": "https://a1npn29y3xu.feishu.cn/wiki/ODmGwWNAJiltmjkusxKcHsUenid", "source_type": "docx", "n_chars": 594, "text": "型的系统测试？为什么会选择这一种类型的系统测试\n\n第二题：请你从五个角度来描述你的测试流程，这五个角度分别是：测试流程、测试计划、测试文档、测试工具、测试总结\n\n第三题：请你针对签到功能设计测试用例\n1️⃣ 请你介绍签到功能的具体流程\n2️⃣ 请你设计两个测试用例，用来测试签到功能\n第四题：结合以上分析，请你阐述一下为什么测试用例对于系统级别的测试很重要\n\n彩蛋：宿舍押题\n\n宿舍押题大赛，谁押对的多谁请饭\nS 选手：独立路径、等价类划分✅、系统测试✅、软件维护✅、测试用例\nK 选手：BVA、TDD、Code Review、V model✅、Top-down/Bottom-Up approach\nX 选手： 测试计划✅、PIE Model、负载测试、随机测试、集成测试\n附加赛：简答题\nS 选手：\nFault,Error,Failure的区别✅\n黑白盒的区别\n单元测试的作用\n自动化测试的优缺点\n软件测试的公理（9 选 5）\nK 选手：\n1. Validation & Verification\n2. Fault, Error, Failure ✅\n3. Load Testing, Stress Testing\n4. Maintaincance 的四种方法✅\n5. 软件文档的四种类型\nX 选手：\nα β测试的区别\nW 模型流程✅\n代码评审的元素\n什么是控制流测试\n集成测试的方法"}
{"id": "docx::OgJows7OTilqZBkuZuUck5hznlg::1671", "page_id": "docx::OgJows7OTilqZBkuZuUck5hznlg", "title": "点球大战", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/最后一夜/点球大战", "section": "点球大战", "url": "https://a1npn29y3xu.feishu.cn/wiki/OgJows7OTilqZBkuZuUck5hznlg", "source_type": "docx", "n_chars": 699, "text": "系统方法 = 系统哲学 + 系统分析 + 系统管理\n\n整体、全局、分析✅\n\n职能型组织结构：按照职能分配任务，工作对上负责，职能经理 / 副总裁 向 CEO 负责（学院与大学）\n\n项目型组织结构：按照项目分配任务，工作对上负责，项目经理 向 CEO 负责（曼哈顿计划）\n\n矩阵型组织结构：职能型和项目型的中间形势，个人向职能经理和项目经理负责\n\n项目管理过程组 = 启动 + 计划 + 执行 + 监控 + 收尾\n\n启动：定义和批准项目 / 项目阶段\n\n计划：制定计划，满足要求\n\n执行：协调人力与资源，产生产品等结果\n\n监控（监督和控制）：有规律地测量和监视项目进展，保证项目团队满足项目目标\n\n收尾：项目货项目阶段的正式验收与有效终止\n\nNPV 公式（ cash flow加括号就是负的意思 ）\n\nEV 公式\n\nDiscount Rate：折损率\n\n项目的 NPV 越高越好（早点回本！）\n\nROI = （折算后利润） / （折算后成本）=（折算后收益 - 折算后成本）/ （折算后成本）\n\n**所有的主过程一前一后都是套公式白送 2 分**\n\n**项目范围管理的六个主过程 4 + 2**\n\n**计划（创建范围管理计划、收集需求、定义范围、创建 WBS）**\n\n**监控（验证范围、控制范围）**\n\nWBS 工作分解结构 对项目所涉及工作面向交付成果的分组，定义了项目的全部范围\n\n输入：管理计划，说明书，需求文档，企业环境因素，组织过程资产\n\n输出：范围基线，文档更新\n\nAOA PDM 画图\n\n甘特图\n\n黑色菱形是里程碑\n\n前面加粗是概要任务\n\n浅灰色横条长度是工期\n\n箭头线条表示依赖关系"}
{"id": "docx::OgJows7OTilqZBkuZuUck5hznlg::1672", "page_id": "docx::OgJows7OTilqZBkuZuUck5hznlg", "title": "点球大战", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/最后一夜/点球大战", "section": "点球大战", "url": "https://a1npn29y3xu.feishu.cn/wiki/OgJows7OTilqZBkuZuUck5hznlg", "source_type": "docx", "n_chars": 493, "text": "，说明书，需求文档，企业环境因素，组织过程资产\n\n输出：范围基线，文档更新\n\nAOA PDM 画图\n\n甘特图\n\n黑色菱形是里程碑\n\n前面加粗是概要任务\n\n浅灰色横条长度是工期\n\n箭头线条表示依赖关系\n\nCPM，关键路径要会算\n\n**成本管理的四个主过程 3 + 1**\n\n**计划（计划成本管理、估计成本、决定预算）**\n\n**监控（控制成本）**\n\nEV 的 公式表要会算\n\n**质量管理的三个主过程 1 + 1 + 1**\n\n**计划（计划质量管理）**\n\n**执行（实施质量保证）**\n\n**监控（控制质量）**\n\n因果图 / 鱼骨图 / 石川图 / 五步法：鱼头呈现了问题，鱼骨头呈现了分析过程，鱼边缘呈现了思考视角\n\n6 σ：100w - 3.4 界定-度量-分析-改进-控制 正态分布\n\n测试 = 单元 + 集成 + 系统 + 用户验收\n\n人才三角\n\n马斯洛需求层次理论：生理 — 安全 — 社交 — 尊重 — 自我实现\n\n塔克曼模型：形成 — 震荡 — 规范 — 执行 — 终止\n\n三种对待风险的态度：厌恶 — 中性 — 喜好，低头 — 平视 — 抬头，横为回报，纵为效用"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1673", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/样卷：考生回忆版/选择题 10 题，每题 3 分（ 2024 保持不变，难度适当下调 ）/以下有关 SA 的表述错误的是？", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 116, "text": "A. 拥有 SA 对软件系统的成功开发具有重要作用\n\nB. SA 是一组用来推断（reason）系统的结构\n\nC. SA 特别忽略了某些对推断系统没有用的信息\n\nD. SA 只有被文档记录才存在，没有被文档记录的软件是没有 SA 的"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1674", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/样卷：考生回忆版/选择题 10 题，每题 3 分（ 2024 保持不变，难度适当下调 ）/Which question module structures CANNOT help us answer about the system? ( ).", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 276, "text": "A. What modules are related to other modules by generalization or specialization?\n\nB. What other software elements is a module allowed to use?\n\nC. What is the assignment of each software element to development teams?\n\nD. What other software does it actually use and depend on?"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1675", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/样卷：考生回忆版/选择题 10 题，每题 3 分（ 2024 保持不变，难度适当下调 ）/一个公司即将开发一个网络交易系统，在架构设计环节，公司的架构师发现了一些核心的质量属性场景。有一个质量属性讲的是：“在最高峰负载的时候，这个系统也应当每秒完成 150 个正常的事务/交易。”请问这一个场景与什么质量属性相关？", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 27, "text": "A. 性能 B. 易用性 C. 安全性 D. 可修改性"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1676", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/样卷：考生回忆版/选择题 10 题，每题 3 分（ 2024 保持不变，难度适当下调 ）/针对 QAW（Quality Attribute Workshop）质量属性研讨会 的表述，以下哪一个是错误的？（ ）", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 110, "text": "A. QAW 是一种生成，优先化，并且细化质量属性场景的方法\n\nB. QAW 用来从干系人中收集质量需求\n\nC. QAW 需要在头脑风暴的步骤中测试系统\n\nD. QAW 帮助为为什么架构师顺序的做出某些决策提供理性的理由"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1677", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/样卷：考生回忆版/选择题 10 题，每题 3 分（ 2024 保持不变，难度适当下调 ）/Having () for testing allows to control or capture variable values for acomponent either through a test harness or through normal execution. It is one of the tactics for testability.", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 105, "text": "A. Specialized interfaces\n\nB. Localized state storage\n\nC. Abstract data sources\n\nD. Executable assertions"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1678", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/样卷：考生回忆版/选择题 10 题，每题 3 分（ 2024 保持不变，难度适当下调 ）/一个正在建造的管理系统也许会发出不同形式的警报。在这个系统中，具有生命威胁的警报例如火灾警报的重要度比非官方的警报（例如房间太冷了）要高。这一种对警报的分级体现了以下的哪一种策略？（）", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 46, "text": "A. 限制事件恢复 B. 管理事件采样率 C. 优先化事项 D. 减少事件 overhead"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1679", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/样卷：考生回忆版/选择题 10 题，每题 3 分（ 2024 保持不变，难度适当下调 ）/A () is an example of a quality view. Such a view might show network traffic models, maximum for operations, and so forth.", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 87, "text": "A. Performance view B. Security view C. Communications view D. Reliability vew"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1680", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/样卷：考生回忆版/选择题 10 题，每题 3 分（ 2024 保持不变，难度适当下调 ）/Lightweight Architecture Evaluation takes much less time than ATAM because ()", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 272, "text": "A. The participants are all internal to the organization and fewer in number that for the ATAM\n\nB. No step towards mapping the highly ranked scenarios onto architecture\n\nC. The external evaluation team performs most of the work\n\nD. Only lightweight scenarios are evaluated"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1681", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/样卷：考生回忆版/选择题 10 题，每题 3 分（ 2024 保持不变，难度适当下调 ）/() is an iterative method that allows an architect to choose a part of the system to design, marsha! all architecturally significant requirements for that part and create and test a design for that part.", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 52, "text": "A. ASR B. ADD C. ATAM D. None of the above"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1682", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/样卷：考生回忆版/选择题 10 题，每题 3 分（ 2024 保持不变，难度适当下调 ）/心跳的频率决定了检测错误的时间，更高的频率可以导向提高的可用性。但同时，这也会消耗更多的执行时间以及沟通带宽（从而使得性能下降）。这是什么概念的样例？", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 70, "text": "A. Risk B. Sensitivity point C. Tradeoff D. None of the above"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1683", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/样卷：考生回忆版/简答题 3 题，每题 10 分（ 2024 简答题 4 题，每题 5 分 ）/阅读材料，结合可测试性的知识点进行论述", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 298, "text": "一个可测试的系统是能最简单放弃错误的。换句话说，如果一个系统包含错误，那么（开发者）**不需要花费很长的时间或者很多的努力就可以让错误显现出来**。但从另一个方面来说，错误容忍度指的是**设计出隐藏缺陷的系统（ designing systems that jealously hide their faults ）**。如果从这个视角思考问题，那么（开发者）就应该让这系统难以展示错误。对于你来说，**有可能设计出一个既符合高可测试性，又符合高错误容忍度的系统吗**？或者说，这两种设计目标是不是**本质上不相容 （ inherently incompatible ）的呢**？请发表你的观点。"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1684", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/样卷：考生回忆版/简答题 3 题，每题 10 分（ 2024 简答题 4 题，每题 5 分 ）/阅读材料，结合质量属性场景的知识点回答问题", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 82, "text": "（1）请你为自动取款机（Automatic Teller Machine）写一组具体的安全性场景？\n\n（2）你会如何修改这个机器的软件设计去满足题（1）提及的场景？"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1685", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/样卷：考生回忆版/简答题 3 题，每题 10 分（ 2024 简答题 4 题，每题 5 分 ）/阅读材料，解决现实生活（非软件开发）问题", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 97, "text": "寻找一个现实生活（并不是软件开发）的例子，这个例子**需要应用每一个管理资源的策略**。举个例子，假如你正在管理一个大型超市，请问，你如何**使用这些策略**使得**消费者能更快地通过结账**？"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1686", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/样卷：考生回忆版/综合题 4 题，每题 10 分（ 2024 综合题 4 题，10 + 10 + 15 + 15 ）/材料原文：", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 388, "text": "The convergence and integration of information technology and economic society has led to the rapid growth of data. Data has become the basic strategic resources of the country. Big data is increasingly exerting an important influence onglobal production, circulation, distribution, consumption activities, economic operation mechanism, social life style and national governance capacity."}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1687", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/样卷：考生回忆版/综合题 4 题，每题 10 分（ 2024 综合题 4 题，10 + 10 + 15 + 15 ）/材料原文：", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 694, "text": "tion activities, economic operation mechanism, social life style and national governance capacity.\n\nIn order to implement the decision-making and deployment of the Central Government, comprehensively promote the development and application of big dataof Municipal Government X, and enhance the ability of government service andsupervision, Municipai Government X has conducted a special survey on the software systems.\n\nThe following problems were found in the survey:\n\n(1) The systems of its subordinate organizations are relatively scattered, with more than 300 database systems.\n\n(2) The types of database management system are complex.\n\n(3) Some systems have big data volume close to 1000T."}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1688", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/样卷：考生回忆版/综合题 4 题，每题 10 分（ 2024 综合题 4 题，10 + 10 + 15 + 15 ）/材料原文：", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 690, "text": "of database management system are complex.\n\n(3) Some systems have big data volume close to 1000T.\n\n(4) A large number of citizens refect that their information registration systems arenumerous, and they often need to fill in personal information repeatedly. They have specific needs and must log in to a specific system. They hope to have aunified platform to handle all business, and the piatform can be used on themobile side.\n\n(5) The database system maintainers of government departments also constantlyrefect that there are too many systems related to social security, thephenomenon of data redundancy is serious, and the data interaction betweendatabases is also difficult to achieve."}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1689", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/样卷：考生回忆版/综合题 4 题，每题 10 分（ 2024 综合题 4 题，10 + 10 + 15 + 15 ）/材料原文：", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 378, "text": "ata redundancy is serious, and the data interaction betweendatabases is also difficult to achieve.\n\n(6) Goverment leaders hope that there will be a platform to automatically generaterelevant data reports and data analysis results for their reference, and it is betterto give some intelligent decision-making suggestions.\n\n**Suppose you're an architect to solve these problems.**"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1690", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/样卷：考生回忆版/参考答案/选择题", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 692, "text": "1. D SA 与是否写了文档无关\n2. C **课本原文！**\n\n\n\n1. A 性能\n\n课本原文的场景：\n\nUsers initiate transactions under normal operations. **The system** processes the transactions with an average latency of two seconds.\n\n- Stimulus: Transaction arrivals\n- Source: Users\n- Artifact: The system\n- Response: Process the transactions\n- Response measure: Average latency of two seconds\n- Environment: Under normal operation\n\n1. C 在头脑风暴的时候测试系统感觉莫名其妙的，让我们看原文\n\n\n\n\n\n1. A 记忆题：特殊化的接口允许控制或者捕捉变量\n\n\n\n举个简单的例子\n\n```Java"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1691", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/样卷：考生回忆版/参考答案/选择题", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 646, "text": ". A 记忆题：特殊化的接口允许控制或者捕捉变量\n\n\n\n举个简单的例子\n\n```Java\npublic class SimpleGetterAndSetter {\n private int number;\n public int getNumber() {\n return this.number;\n }\n public void setNumber(int num) {\n this.number = num;\n }\n}\n```\n\n1. C 直接通过阅读理解推断出事情有轻重缓急\n\n\n\n1. GPT 给出的参考答案：The correct answer is **A. Performance view**. This view focuses on aspects like network traffic models, operation capacity, and performance metrics.\n\n\n\n1. A 如果用通俗易懂的方法解释就是：**人少且全部都是组织内的效率相对高**"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1692", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/样卷：考生回忆版/参考答案/选择题", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 586, "text": "\n\n1. A 如果用通俗易懂的方法解释就是：**人少且全部都是组织内的效率相对高**\n\n\n\nB. No step towards mapping the highly ranked scenarios onto architecture ✖ → 步骤还是一样的\n\nC. The external evaluation team performs most of the work ✖ → 压根就没有外部团队负责这件事情\n\nD. Only lightweight scenarios are evaluated ✖ → 看到 Only 心里就要打感叹号，绝对化表述 80% 都可以秒排除\n\n1. B 是不是很多人看到 significant requirements 就急匆匆地选 A 溜了？要审题！题目说的是：**这一个迭代方法，这个迭代方法是设计系统的一部分，MARSHAL 所有 ASR！**\n\n\n\n1. C 福兮祸之所倚 祸兮福之所伏"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1693", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/样卷：考生回忆版/参考答案/简答题（只讲思路）", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 658, "text": "1. **论述辨析题**\n\n题目提出了一个很有意思的话题：错误究竟应该越早发现越好，还是尽量隐藏比较好。\n\n两个论点选其中一个即可：highly testable & highly fault tolerant 可以兼容 / 水火不容\n\n但是无论论点怎么选，论述辨析题答题的总思路都是一样的\n\n第一步：**申明自己的观点**（1 分）\n\n第二步（核心）：对**课本内容进行剖析**（5 分）\n\n这一题需要引用的内容包括了：\n\n① \n\n② \n\n③ \n\n第三步（重要）：结合课本内容对**材料内容进行分析**，并进行适当举例（3 分）\n\n第四步：总结自己的观点，**以架构师的角度为软件开发者提出建议**（1 分）\n\nAI 生成答案仅供参考：\n\n**观点：**"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1694", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/样卷：考生回忆版/参考答案/简答题（只讲思路）", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 680, "text": "要）：结合课本内容对**材料内容进行分析**，并进行适当举例（3 分）\n\n第四步：总结自己的观点，**以架构师的角度为软件开发者提出建议**（1 分）\n\nAI 生成答案仅供参考：\n\n**观点：**\n\n我认为，高可测试性与高错误容忍度可以在某些设计中兼容，但两者的平衡需要谨慎把握，尤其在系统架构设计时，需要根据不同的应用场景和需求做出取舍。\n\n**分析：**\n\n① **高可测试性**：在第十章“Testability”中，Len Bass 等提到，可测试性指的是系统能在开发和维护阶段尽早发现和修复错误。高度可测试的系统通常设计为易于观察和检测其内部状态，并通过自动化测试来快速暴露缺陷。这有助于开发者及时发现和修正问题，降低系统的故障率。\n\n② **高错误容忍度**：第十三章和第十四章强调，高错误容忍度设计旨在确保系统即使发生部分故障，仍能维持部分功能并继续运行，避免系统完全崩溃。通过冗余、回滚机制、容错设计等方式，增强系统在异常情况下的稳定性和可用性（《Availability》，第5章）。\n\n③ **兼容与不兼容**：从理论上讲，错误容忍度和可测试性似乎是两个不同的目标。高可测试性要求系统故障暴露，便于测试和修复。而高错误容忍度则要求系统隐藏错误，通过冗余和恢复措施来维持运行状态，这可能会导致故障暴露的延迟。然而，在实践中，可以通过设计模块化、分层架构来兼顾两者。例如，通过隔离故障组件，使得错误能够局部暴露并被快速修复，同时系统其他部分保持高可用性。\n\n**结论：**\n\n作为架构师，建议在设计系统时根据需求对可测试性与错误容忍度进行权衡。"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1695", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/样卷：考生回忆版/参考答案/简答题（只讲思路）", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 647, "text": "、分层架构来兼顾两者。例如，通过隔离故障组件，使得错误能够局部暴露并被快速修复，同时系统其他部分保持高可用性。\n\n**结论：**\n\n作为架构师，建议在设计系统时根据需求对可测试性与错误容忍度进行权衡。对于关键业务系统，可以选择冗余设计来提高容错能力；而对于迭代频繁、快速交付的系统，则应侧重提高可测试性，以尽早发现潜在缺陷。\n\n1. 场景分析题\n\n笔者希望从“取钱存钱”的用户以及“收钱护钱”的银行两个视角列出不同的场景，再根据实际情况遇到的问题来改。\n\n既然题目已经说明要从具体的安全性视角来写，那么大家先默写，再结合材料凑起来即可，言之有理即可给分。\n\n\n\n需求是什么？引入了什么质量属性？\n\n这个质量属性是什么？具有什么特点？\n\n这个质量属性可以应用于哪些场景？\n\nS — Stimulus — 刺激：① 触发**系统响应的事件** ② 响应的**条件**\n\nS — Source — 源头：引发刺激的 **实体 或者 组件**\n\nE — Environment — 环境：**条件** 或者 **上下文**\n\nA — Artifact — 工件：**系统** / 部分**系统** / 系统集合 / 系统切片\n\nR — Response — 响应：**对刺激的回复**"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1696", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/样卷：考生回忆版/参考答案/简答题（只讲思路）", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 690, "text": "**条件** 或者 **上下文**\n\nA — Artifact — 工件：**系统** / 部分**系统** / 系统集合 / 系统切片\n\nR — Response — 响应：**对刺激的回复**\n\nR — Response Measure — 响应度量：① 评估**效率的准则** / ② **可量化的指标**\n\nAI 生成答案仅供参考，**大家在考试的时候要自行根据 SSEARR 分点列场景。**\n\nATM 系统的安全注意事项\n\n要设计安全的 ATM 系统，我们需要从用户角度（例如取款或存款）和银行角度（例如确保交易和资金的安全）考虑各种场景。以下是具体场景，然后介绍如何修改设计以解决安全问题：\n\n**① 用户视角：存款（3 分）**\n\n- **Source（源）**：用户在 ATM 上进行现金存款操作。\n- **Stimulus（刺激）**：用户通过信封或现金存款功能将现金存入 ATM。\n- **Environment（环境）**：ATM 自身的硬件、软件和用户交互界面，通常位于公共或半公共区域。\n- **Artifact（工件）**：ATM 的现金存款功能、钞票存入口、存款验证界面和收据打印功能。\n- **Response（响应）**：ATM 需要有效地处理存款请求，验证现金的真实性，防止假钞存入，同时确保存款过程安全，避免物理破坏。\n- **Response Measure（响应衡量）**：通过实施钞票认证技术（例如 UV 灯或磁条检测），确保现金的真实性；通过防篡改传感器和报警系统减少物理攻击；提供存款金额确认和数字收据，以确保用户验证存款准确性。"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1697", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/样卷：考生回忆版/参考答案/简答题（只讲思路）", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 669, "text": "Measure（响应衡量）**：通过实施钞票认证技术（例如 UV 灯或磁条检测），确保现金的真实性；通过防篡改传感器和报警系统减少物理攻击；提供存款金额确认和数字收据，以确保用户验证存款准确性。\n\n**② 银行观点：保护 ATM 网络（3 分）**\n\n- **Source（源）**：银行的网络架构和 ATM 系统。\n- **Stimulus（刺激）**：银行希望确保 ATM 与其后台系统之间的通信安全，防止网络攻击或数据泄露。\n- **Environment（环境）**：ATM 与银行核心系统之间的网络连接、数据传输协议、加密技术及安全措施。\n- **Artifact（工件）**：ATM 网络接口、加密通信协议、防火墙和入侵检测系统（IDS）。\n- **Response（响应）**：银行需要加强 ATM 网络的安全性，确保所有数据传输都是加密的，并防止任何未授权的中间人攻击或数据窃取。\n- **Response Measure（响应衡量）**：通过实施端到端加密协议，确保 ATM 与银行系统之间的通信无法被截获；定期进行安全性审查和漏洞测试，确保 ATM 网络不受中间人攻击的影响；使用网络入侵检测系统（IDS）实时监控异常流量和潜在的攻击行为。\n\n**安全增强的措施：**\n\n- 加密：对所有 ATM 通信使用端到端加密，以防止敏感数据被拦截。\n- 防火墙和入侵检测系统：确保所有 ATM 系统都位于强大的防火墙后面，并配备入侵检测系统以识别恶意活动。\n- 定期软件更新：实施定期软件补丁和更新以解决已知漏洞并增强安全性。"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1698", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/样卷：考生回忆版/参考答案/简答题（只讲思路）", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 382, "text": "止敏感数据被拦截。\n- 防火墙和入侵检测系统：确保所有 ATM 系统都位于强大的防火墙后面，并配备入侵检测系统以识别恶意活动。\n- 定期软件更新：实施定期软件补丁和更新以解决已知漏洞并增强安全性。\n\n基于上述情况，以下是安全性方面的潜在设计修改：（3 分）\n\n- 定期审计和实时监控：银行应持续监控 ATM 是否存在异常活动，例如高频交易或未经授权的访问尝试。\n- 用户教育：提供有关如何防止欺诈的明确说明（例如，在输入 PIN 时遮住 PIN 键盘）。\n- 生物识别集成：考虑结合生物识别技术（指纹、面部识别）进行安全的用户身份验证，尤其是对于高价值交易。\n\n总之，安全性对于 ATM 操作中的用户和银行而言都至关重要。设计具有多层安全性的 ATM（从防盗刷设备等物理措施到加密等网络安全措施）可确保用户和金融机构的利益都得到保障。（1 分）\n\n1. 场景分析题"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1699", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/样卷：考生回忆版/参考答案/简答题（只讲思路）", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 684, "text": "安全性对于 ATM 操作中的用户和银行而言都至关重要。设计具有多层安全性的 ATM（从防盗刷设备等物理措施到加密等网络安全措施）可确保用户和金融机构的利益都得到保障。（1 分）\n\n1. 场景分析题\n\nTo manage resources efficiently and improve the customer experience, especially in a busy retail store, we can apply several **manage-resources tactics** (from the realm of software systems) to a real-world scenario like a brick-and-mortar big-box retail store. Below are examples of how to apply these tactics:（以下 10 个选取 3 — 4 个细讲应该就够了，不知道老师怎么给分）\n\n预防：\n\n策略：通过预测问题并提前实施解决方案来预防瓶颈的发生。例如：通过监控商店客流量模式并相应地配备人员，确保在高峰时段（例如周末或节假日）有足够的结账通道开放。在收银台安排更多工作人员或使用自动自助结账系统来处理更高的需求，避免长时间等待。\n\n高效分配：\n\n策略：以优化吞吐量的方式分配资源（人员、设备、空间）。例如：使用动态调度系统根据实时客流量数据将收银员分配到特定通道。如果一条通道比其他通道更繁忙，则可以快速将资源（例如员工）重新分配到该通道。\n\n优先级："}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1700", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/样卷：考生回忆版/参考答案/简答题（只讲思路）", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 697, "text": "化吞吐量的方式分配资源（人员、设备、空间）。例如：使用动态调度系统根据实时客流量数据将收银员分配到特定通道。如果一条通道比其他通道更繁忙，则可以快速将资源（例如员工）重新分配到该通道。\n\n优先级：\n\n策略：根据任务的紧急程度和重要性确定任务的优先级。例如：为购买较少商品的顾客实施“快速通道”。这使那些购买较少商品的顾客可以更快地结账，最大限度地减少其他人的拥堵并加快整个结账流程。\n\n分区：\n\n策略：将资源或任务分解成更小的部分，以便同时处理多个流程。例如：将结账流程分为多个阶段（例如，扫描商品、装袋、付款），并为每个阶段分配不同的工作人员以加快流程。这种分区减少了总体等待时间。\n\n负载平衡：\n\n策略：在可用资源之间均匀分配工作负载，以防止任何一种资源过载。例如：使用队列管理系统，将客户引导到最短或最不繁忙的结账队列。这有助于平衡多个通道上的客户负载，并防止某些通道不堪重负而其他通道未得到充分利用。\n\n动态重新配置：\n\n策略：根据当前情况或需求实时重新配置资源。例如：如果自助结账站的排队太长，则通过临时将客户引导到其他可用收银台来重新配置商店。重新分配资源的灵活性可确保商店的任何区域都不会成为瓶颈。\n\n缓存：\n\n策略：将经常访问的资源存储在更快或更易于访问的位置。例如：设置一个“预扫描”区域，快速扫描商品，然后在顾客完成购物时将其保留。这可以最大限度地减少结账所花费的时间并加快整个流程。\n\n冗余：\n\n策略：实施备份或冗余资源以处理故障或意外的需求激增。例如：在主系统发生故障时，提供备用销售点 (POS) 系统。此外，确保有足够的收银机或移动结账设备来处理意外的客户流量激增。"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1701", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/样卷：考生回忆版/参考答案/简答题（只讲思路）", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 384, "text": "流程。\n\n冗余：\n\n策略：实施备份或冗余资源以处理故障或意外的需求激增。例如：在主系统发生故障时，提供备用销售点 (POS) 系统。此外，确保有足够的收银机或移动结账设备来处理意外的客户流量激增。\n\n反馈循环：\n\n策略：使用来自环境的反馈来实时调整资源分配或流程。例如：使用来自客户流量或结账时间的实时数据来调整人员配备水平。如果反馈循环显示在某些时间排起了长队，管理层可以立即做出反应，开辟更多通道。\n\n分时：\n\n策略：允许多个任务或用户同时共享资源。示例：实施移动结账设备，员工可以在整个商店协助客户结账，而不必让客户排队等候。这有效地在整个商店共享结账流程，减少了等待时间。\n\n结论：\n\n在零售环境中应用这些资源管理策略可以通过减少等待时间和简化结账流程来显著改善客户体验。通过预测需求、使用技术和优化员工分配，商店可以为客户和员工创造一个更高效、更愉快的环境。"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1702", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/样卷：考生回忆版/参考答案/综合题（只讲思路）", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 616, "text": "1. 质量属性 + 通用质量属性场景\n\n笔者相信大家的通用质量属性场景倒背如流，遇到这种题咱们只需要填表格就可以了，既然没有硬性要求，那么大家只需要从以下七个质量属性中选取最擅长的五个，表格只要里面有字就行（不用全写），一列 2 分，封顶 10 分\n\n| | Availability | Interoperability | Modifiability | Performance | Security | Testability | Usability |\n|-|-|-|-|-|-|-|-|\n| Source | | | | | | | |\n| Stimulus | | | | | | | |\n| Environment | | | | | | | |\n| Artifact | | | | | | | |\n| Response | | | | | | | |\n| Response Measure | | | | | | | |\n\n1. 效能树 + 质量属性 + 具体质量属性场景（效能树多少分，就是多少个叶子？）\n\n第十一题是列表，但是到了第十二题，我们使用“思维导图”更方便\n\n第一层节点：七个质量属性选五个\n\n第二层节点：每个质量属性选一到两个定义指标\n\n第三层节点：抄材料（注意更改语法：第一人称 → 第三人称。主动 → 被动）"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1703", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/样卷：考生回忆版/参考答案/综合题（只讲思路）", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 518, "text": "了第十二题，我们使用“思维导图”更方便\n\n第一层节点：七个质量属性选五个\n\n第二层节点：每个质量属性选一到两个定义指标\n\n第三层节点：抄材料（注意更改语法：第一人称 → 第三人称。主动 → 被动）\n\n最后别忘了（M, M）⬅️你不知道如何评估（商业价值，架构影响）就这么写，但不要全部都写（M, M），各位架构师可以根据自己对材料的理解进行调整，这种题没有标准答案，背多分，字多分！\n\n给大家再看一看官方的效能树怎么画\n\n\n\n1. 架构模式 ASR\n\n**说实话，这一题能答的点实在是太多了，反而难以下笔**\n\n1. C & C Architectual View\n\n\n\n题目只要求从 C & C 中选一个架构来画图，言之有理即可给分。\n\n那么，大家在复习的时候选取 2 个 UML 画着简单的图，并且往材料上匹配即可"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1704", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/样卷：考生回忆版/试卷总结/选择题/考点 —— 讲义对照图", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 700, "text": "123456778910"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1706", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/样卷：考生回忆版/试卷总结/选择题/选择题总结", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 280, "text": "① 有一些题目是温柔的送分题，一眼看出来就能出答案，不要想东想西，必须按照常识锁定送分题的分数\n\n② Quality Attributes 每年都会抽取 2 \\~ 3 个重点的考细节，每年的重点都不同，以当年的重点为准\n\n- 记忆背诵型：乖乖把 Tactics Tree 的内容记下来\n- 阅读理解型：根据 General Scenario 以及生活常识就可以很清晰地推导出来\n\n③ 讲义中如果有标荧光笔的地方或者有加红加蓝的地方，那么这些地方就是选择题答案\n\n④ SA 讲义（三）（四）（五）最喜欢看边边角角的习题，要抽出时间把讲义花花绿绿的地方手动整理起来"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1707", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/样卷：考生回忆版/试卷总结/简答题/考点 —— 讲义对照图", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 456, "text": "111213"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1708", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/样卷：考生回忆版/试卷总结/简答题/简答题总结", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 114, "text": "简答题和申论的思路其实是共享的。\n\n申，就是申明课本和材料的文本\n\n论，就是结合课本的理论知识对题目的观点进行论述\n\n"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1709", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/样卷：考生回忆版/试卷总结/简答题/考点 —— 讲义对照图", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 579, "text": "14151617"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1710", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/样卷：考生回忆版/试卷总结/简答题/综合题总结", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 152, "text": "综合题的套路其实很固定：\n\nAttribute General 考一题\n\nUtility Tree + Concrete Scenario 考一题\n\nASRs 或者 ATAM 考一题\n\nModule，C & C，和 Allocation 考一题\n\n**课本背的好，分数低不了。材料读得好，分数少不了。**"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1711", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/选择题样板冲刺卷/Which of the following should be included in the consideration of a Allocation Structure?", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 251, "text": "A. What are the major executing components and how do they interact at runtime\n\nB. what part of the system can run in parallel\n\nC. How software is assigned to hardware processing and communication elements.\n\nD. How does data process through the system"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1712", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/选择题样板冲刺卷/Which one of the following structures pertains to the C&C Structure?", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 93, "text": "A. Service structure\n\nB. Class structure\n\nC. Deployment structure\n\nD. Decomposition structure"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1713", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/选择题样板冲刺卷/Which one of the following tactics is for improving modifiability?", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 103, "text": "A. Removal from Service\n\nB. Detect service attack\n\nC. Increase Semantic Coherence\n\nD. Active redundancy"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1714", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/选择题样板冲刺卷/“A User asks for help, and the system provides help for that context” is a scenario of ( ).", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 58, "text": "A. Security\n\nB. Usability\n\nC. Performance\n\nD. Availability"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1715", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/选择题样板冲刺卷/Which of the following descriptions about the relationships between Architectural Pattern and Architectural tactic is True?", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 235, "text": "A. Patterns have to be augmented with tactics for the design of real systems\n\nB. If a tactic has side effects, it should not be added into the design of a system\n\nC. Tactics are simpler than patterns\n\nD. Tactics are built from Patterns"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1716", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/选择题样板冲刺卷/Boehm and Turner found that projects have a “sweet spot” where up-front architecture planning pays off. For the ( )，the sweet spot is around 40% of the project schedule.", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 120, "text": "A. 10KSLOC project\n\nB. 100KSLOC project\n\nC. 1000KSLOC project\n\nD. extremely large projects with very stable requirements"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1717", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/选择题样板冲刺卷/The ( ) is focused on system-level concerns and specifically the role that software will play in the system and it is keenly dependent on the participation of system stakeholders.", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 117, "text": "A. Utility Tree\n\nB. Quality Attribute Workshop\n\nC. Attribute Driven Design\n\nD. Architecture Trade-off Analysis Method"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1718", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/选择题样板冲刺卷/The testability tactics of “ ( )” refers to isolating an instance of the system from the real world to enable experimentation that is unconstrained by the worry about having to undo the consequences of the experiment.", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 90, "text": "A. Sandbox\n\nB. Executable Assertions\n\nC. Abstract Data Sources\n\nD. Localized State Storage"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1719", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/选择题样板冲刺卷/Availability tactics are designed to enable a system to endure system faults so that a service being delivered by the system remains complaint with its specification. A fault happens when the following stimuli occur EXCEPT FOR ( )", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 261, "text": "A. Omission: A component fails to respond to an input\n\nB. Crash:The component repeatedly suffers omission faults\n\nC. Timing: A component responds but the response is early or late.\n\nD. Event arrivals: The stimuli arrive either from external or internal sources."}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1720", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/选择题样板冲刺卷/Which of the following statements is NOT TRUE about the CAP theorem?", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 536, "text": "A. According to CAP theorem, it is possible to achieve Consistency, Availability and Partition simultaneously (同时地).\n\nB. The CAP theorem is about the three important properties, which are Consistency, Availability and Partition, of a distributed system managing shared data.\n\nC. According to CAP theorem, one of the three important properties, Consistency, Availability and Partition, should be sacrificed.\n\nD. For many applications, it is a choice to sacrifice consistency and provide immediate availability and eventually consistency."}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1721", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/参考答案/Allocation Structure", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 193, "text": "Allocation Structure describes the **mapping from software structures to the system's environments.**\n\nWhat is the system's environment ? → **A file structure, Hardware** and so on...\n\n所以答案选择 C"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1722", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/参考答案/Here are the structures:/Module Structures :", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 68, "text": "- **Decomposition**\n- User -> Layer Pattern\n- **Class**\n- Data model"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1723", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/参考答案/Here are the structures:/Allocation Structures :", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 58, "text": "- **Deployment**\n- Implementation\n- Work Assignment\n\n答案选 A"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1724", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/参考答案/Modifiability", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 248, "text": "- Reduce Size of a Module\n\n - Split Module\n- Increase Cohesion\n\n - Increase Semantic Coherence\n- Reduce Coupling\n\n - Encapsulate\n - Use an Intermediary\n - Restrict Dependencies\n - Refactor\n - Abstract Common Services\n- Defer Binding\n\n选择 C 选项"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1725", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/参考答案/质量属性的概念", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 56, "text": "Availability 强调能不能用（可用性）\n\nUsability 强调好不好用（易用性）\n\n选择 B 选项"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1726", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/参考答案/？Pattern 和 Tactics 的关系", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 185, "text": "\n\n\n\n\n\nA 和 C 似乎都可以？？？"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1727", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/参考答案/Sweet Spot", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 297, "text": "\n\n100KSLOC\n\n记口诀：十百万，二四五\n\n\n\nB\n\n\n\nA\n\nEvent arrivals: The stimuli arrive either from external or internal sources.\n\n事件到达是中性的，和错误检测无关\n\nD"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1728", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "新高考/参考答案/CAP介绍", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 549, "text": "在理论计算机科学中，**CAP定理**（CAP theorem），又被称作**布鲁尔定理**（Brewer's theorem），它指出对于一个分布式计算系统来说，不可能同时满足以下三点：\n\n- 一致性（**C**onsistency） （等同于所有节点访问同一份最新的数据副本）\n- 可用性（**A**vailability）（每次请求都能获取到非错的响应——但是不保证获取的数据为最新数据）\n- 分区容错性（**P**artition tolerance）（以实际效果而言，分区相当于对通信的时限要求。系统如果不能在时限内达成数据一致性，就意味着发生了分区的情况，必须就当前操作在C和A之间做出选择）\n\n根据定理，[分布式系统](https://edu.csdn.net/cloud/sd_summit?utm_source=glcblog&spm=1001.2101.3001.7020)只能满足三项中的两项而不可能满足全部三项。理解CAP理论的最简单方式是想象两个节点分处分区两侧。允许至少一个节点更新状态会导致数据不一致，即丧失了C性质。如果为了保证数据一致性，将分区一侧的节点设置为不可用，那么又丧失了A性质。除非两个节点可以互相通信，才能既保证C又保证A，这又会导致丧失P性质。\n\nA"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1729", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "旧高考/通用模板卷/参考答案/选择题", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 625, "text": "1. C\n\nArchitect 不参与代码的直接编写\n\n1. B\n\n21.2\n\n... Stakeholders include [developers, **testers（A）**, integrators,\n\nmaintainers, performance engineers, users, builders of systems interacting\n\nwith the one under consideration, and others listed in Chapter 3.]\n\n1. C\n\nUtility Tree 将功能不断细化，并且从商业价值和架构影响两个角度提出了优先级\n\n\n\n1. D\n\n只有一个架构师和 warning 没关系吧\n\n1. B\n\nBuildability 和架构构造有关\n\n1. B\n\n- **Ping / Echo**:\n Ping is used to determine the reachability of a network and measure the round-trip delay through the associated network path.\n网络延迟检测：Ping用于确定网络的可达性，并测量通过相关网络路径的往返延迟。\n- **Heartbeat**:"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1730", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "旧高考/通用模板卷/参考答案/选择题", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 670, "text": "delay through the associated network path.\n网络延迟检测：Ping用于确定网络的可达性，并测量通过相关网络路径的往返延迟。\n- **Heartbeat**:\n A periodic message exchange between a system monitor and a process being monitored.\n\n心跳：系统监控器与被监控进程之间的周期性消息交换。\n\n1. 🌟 C\n\n**Allocation structures** show the relationship between the software elements and elements in one or more external environments **in which the software is created and executed**. / **分配结构**显示软件元素与一个或多个外部环境中元素之间的关系，这些环境是软件创建和执行的场所。\n\n1. D\n\nRipple Effect —— 链式反应 / 涟漪效应 / 连锁反应\n\n 根据选项判断， ABC 都可以通过切断或者限制某一个沟通线路来达到削弱连锁反应的效果。\n\n1. A\n\n\n\n1. B"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1731", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "旧高考/通用模板卷/参考答案/选择题", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 283, "text": "fubMiNM1pkUADKcHBIjncg\" file-type=\"wiki\" title=\"Chapter 11 Usability / 第十一章：易用性\" type=\"doc\">\n\n1. B\n\n业务样例 ——> 理解需求 ——> 选择架构 ——> 详细设计 ——> 程序编程 ——> 集成测试\n\nBusiness Case -> Understand Requirement -> Select Software Architecture -> Detail Designing -> Program Coding -> Integration Testing"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1732", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "旧高考/通用模板卷/参考答案/简答题（只讲思路）", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 699, "text": "1. 先默写 Uses Structure 的概念，再默写 Layerd Structure 的概念，最后整合成一张表格或者一段话即可。\n\n*The layered structure is a special kind of uses structure. In uses structure, one unit can use another unit if necessary, no matter what units they are. But in layered structure, the unit from upper layer can only use the unit from lower layer. The detail in the lower layer is invisible to the upper layer.*\n\n1. Data warehouse 和 Blackboard 其实是第 13 章节的一个小点，新高考考的是 Shared-Data Diagram，在此给大家做个拓展吧\n\n数据仓库：面向主题、集成性、稳定性和时变性\n\n黑板：只保存知识源要用的数据\n\n\n\n1. ~~Business Quality 和 Architecture Quality 是 老高考第四章对 Quality 的分类，新高考只需要大家了解即可~~\n2. 模块之间的依赖，以下答案均为 GPT 生成\n\n**Functional Dependencies**:"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1733", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "旧高考/通用模板卷/参考答案/简答题（只讲思路）", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 677, "text": "Quality 是 老高考第四章对 Quality 的分类，新高考只需要大家了解即可~~\n2. 模块之间的依赖，以下答案均为 GPT 生成\n\n**Functional Dependencies**:\n\n- These are direct dependencies where the functionality of one module relies on the functionality of another. For example, a module that calculates taxes might depend on a module that provides current tax rates.\n\n**Data Dependencies**:\n\n- Modules may depend on data provided by other modules. This can be in the form of input parameters, shared databases, or data passed through interfaces.\n\n**Control Dependencies**:\n\n- One module might control the flow of another, such as a controller module that directs the execution of various worker modules based on certain conditions."}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1734", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "旧高考/通用模板卷/参考答案/简答题（只讲思路）", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 693, "text": "ontroller module that directs the execution of various worker modules based on certain conditions.\n\n**Service Dependencies**:\n\n- Modules might depend on services provided by other modules, such as a logging service or a data access service.\n\n**Communication Dependencies**:\n\n- Modules that communicate with each other over a network or through message queues have a communication dependency.\n\n**Resource Dependencies**:\n\n- Modules may depend on shared resources like memory, file systems, or hardware devices.\n\n**Version Dependencies**:\n\n- A module might depend on a specific version of another module or a third-party library, which can lead to issues if the version is updated or deprecated."}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1735", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "旧高考/通用模板卷/参考答案/简答题（只讲思路）", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 698, "text": "module or a third-party library, which can lead to issues if the version is updated or deprecated.\n\n**Runtime Dependencies**:\n\n- At runtime, modules may depend on the presence and availability of other modules to function correctly.\n\n1. ~~Skeletal System：新高考不考~~\n2. Risk points in architectural decision and give an example.\n\n这一题相对比较开放，大家可以从某些质量属性“矫枉过正”的极端例子引出风险，也可以从某些质量属性“忽略处理”的某些例子引出风险，以下思路仅供参考\n\n1. **性能风险**：软件架构可能无法满足性能要求，如响应时间、吞吐量等。例如，如果架构设计没有考虑到高并发用户的需求，可能会导致系统在高负载下性能下降。\n2. **可维护性风险**：架构的复杂性可能导致维护成本增加和维护难度提高。如果架构设计没有考虑到可维护性，未来对系统的修改和扩展可能会非常困难。\n3. **安全性风险**：架构可能存在安全漏洞，导致数据泄露或系统被攻击。例如，如果架构没有适当的安全措施来保护敏感数据，可能会增加数据泄露的风险。\n4. **资源分配风险**：资源分配不当可能导致项目延期或超出预算。例如，如果项目团队没有足够的资源来支持架构的实施，可能会导致项目进度缓慢。"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1736", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "旧高考/通用模板卷/参考答案/简答题（只讲思路）", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 186, "text": "当的安全措施来保护敏感数据，可能会增加数据泄露的风险。\n4. **资源分配风险**：资源分配不当可能导致项目延期或超出预算。例如，如果项目团队没有足够的资源来支持架构的实施，可能会导致项目进度缓慢。\n5. **需求变更风险**：需求的频繁变更可能导致架构需要不断调整，从而影响项目进度和质量。例如，如果业务需求在项目开发过程中不断变化，架构可能需要不断修改以适应这些变化。"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1737", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "旧高考/通用模板卷/参考答案/综合题（只讲思路）", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 418, "text": "1. Quality Attributes，还是老样子，读材料选 Attribute，默写相关概念\n\n| | Availability ✅ | Interoperability ✅ | Modifiability | Performance ✅ | Security ✅ | Testability | Usability ✅ |\n|-|-|-|-|-|-|-|-|\n| Source | | | | | | | |\n| Stimulus | | | | | | | |\n| Environment | | | | | | | |\n| Artifact | | | | | | | |\n| Response | | | | | | | |\n| Response Measure | | | | | | | |\n\n1. ✖\n\n1. ✖\n\n1."}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1738", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "旧高考/通用模板卷/参考答案/综合题（只讲思路）/**Decomposition Structure / 分解结构**", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 659, "text": "The units are modules that are related to each other by the is-a-submodule-of relation. / 这些单元是通过“是一个子模块”关系相互关联的模块。\nIt shows how modules are decomposed into smaller modules recursively until the modules are small enough to be easily understood. / 它展示了模块如何递归地被分解成更小的模块，直到模块足够小，易于理解。\nModules often have products (such as interface specifications, code, test plans, etc.) associated with them. / 模块通常会有一些产品（如接口规范、代码、测试计划等）与之关联。\nThe decomposition structure determines, to a large degree, the system's modifiability, by assuring that likely changes are localized. / 分解结构在很大程度上决定了系统的可修改性，通过确保可能的变更被局部化来实现这一点。\n\n"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1739", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "旧高考/通用模板卷/参考答案/综合题（只讲思路）/Concurrency structure / 并发结构", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 371, "text": "This structure helps determine opportunities for parallelism and the locations where resource contention may occur. / 该结构有助于确定并行性的机会以及可能发生资源争用的位置。\n\nThe units are components. / 单元是组件。\n\nThe connectors are their communication mechanisms. / 连接器是它们的通信机制。\n\nThe components are arranged into logical threads. / 组件被安排为逻辑线程。\n\n"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1740", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "旧高考/通用模板卷/参考答案/综合题（只讲思路）/Deployment Structure / 部署结构", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 699, "text": "The deployment structure shows how software is assigned to hardware processing and communication elements. / 部署结构展示了软件如何分配给硬件处理和通信元素。\n\nThe elements are software elements (usually a process from a C&C view), hardware entities (processors), and communication pathways. / 这些元素包括软件元素（通常是 C&C 视图中的进程）、硬件实体（处理器）和通信通道。\n\nRelations are **allocated-to**, showing on which physical units the software elements reside, and migrates-to if the allocation is dynamic.\n\n关系通过**“分配到”**来表示，展示软件元素所在的物理单元；如果分配是动态的，则通过“迁移到”来表示。\n\nThis structure can be used to reason for performance, data integrity, security, and availability.\n\n该结构可用于推理性能、数据完整性、安全性和可用性。\n\nIt is of particular interest in distributed and parallel systems."}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1741", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "旧高考/通用模板卷/参考答案/综合题（只讲思路）/Deployment Structure / 部署结构", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 178, "text": "lity.\n\n该结构可用于推理性能、数据完整性、安全性和可用性。\n\nIt is of particular interest in distributed and parallel systems.\n\n在分布式和并行系统中，这一结构尤为重要。\n\n"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1742", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "旧高考/小题", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 675, "text": "1. Who are stakeholders ? / 那些角色是干系人？\n2. What are quality attributes ? / 质量属性有哪些？\n3. List 5 architectural patterns / styles ? / 列举五个架构模式 / 风格？\n4. How is an architectural pattern / style determined ? / 架构模式 / 风格是怎么确定的？\n5. What are 3 main categories of architectural structures ? / 三种主要的架构结构是什么？\n6. List 5 architectural structures according to Bass et al.\n7. Discuss the benefits of architectural reviews ?\n8. Explain risk / non-risk / sensitivity / trade-off points in architectural decision.\n9. List ATAM steps.\n10. What is a utility tree ?\n11. What is availability ? What tactics can be taken to use for availability ?\n12. What is ADD? Describe the steps to carry out ADD ?"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1743", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "旧高考/小题", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 668, "text": "ctics can be taken to use for availability ?\n12. What is ADD? Describe the steps to carry out ADD ?\n13. How to create a skeletal system ? 如何创建骨架系统？\n14. Iteroperability / 互操作性\n15. ATAM 考的非常细，比如敏感点的 example，风险主题的 example\n16. 涉及到数据延迟以及交易吞吐量：性能\n17. 可修改性战术有几种 Pattern，Defer Binding Time 属于可修改性战术\n18. 无论是主动冗余还是被动冗余，都属于可用性战术\n19. ATAM 的全拼是什么？ATAM 的小知识点是什么？\n20. 质量属性可以分为（系统、商业、构架），老高考从商业找一个例子，你要分析出来\n21. Finish Design is not a precondition for architectural review.\n22. How is an architectural pattern/style determined?\n23. What is an unplanned architecutral review? Why should the organization have it?\n24. What is brainstorming?\n25. How does the environment influence design?"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1744", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "旧高考/小题", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 166, "text": "the organization have it?\n24. What is brainstorming?\n25. How does the environment influence design?\n26. How does architectural design change the business environment?"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1745", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "旧高考/大题/例题一：RFIDSale 系统（Web 开发）", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 285, "text": "\n\n1. 请根据所提供RFIDSale系统的构架模式和RFIDSale系统的需求规约简表RFIDSaleSRS，进行深入的分析，提出并明确系统的质量属性及其实现战术。\n2. 在全面质量管理的思想指导下，根据系统的质量属性及其实现战术，提出系统的参考模型、参考的构架框架。\n3. 在1,2的基础上，基于ADD方法，提出并详细描述目标系统RFIDSale的软件体系结构；\n4. 基于 ATAM 方法，提出目标系统RFIDSale的软件体系结构的项目组内部评估结果。"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1746", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "旧高考/大题/参考答案/各位**把六个质量属性和它们对应的战术都和这个系统的需求结合起来，扯上去，就可以得分。**", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 220, "text": "例如:\n\n安全性：PDA只能下单。需要保持数据的安全性，机密性。然后结合具体把安全性战术写上去。\n\n例如：\n\n互操作性：PDA如何和系统交互：PDA和系统交互是通过JMS的（涉及到SOA的知识），把互操作性扯上去。\n\n例如\n\n性能：PC是通过Internet来和系统交互的。网络的带宽限制了性能。需要提高性能，这样可以使用.NET的缓冲池策略可以提高性能，（.net的缓冲池策略请参考南哥宝典442页上得PETshop）把想到的战术写上去。"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1747", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "旧高考/大题/参考答案/构架分析", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 96, "text": "这个系统是是一个分布式-分层系统。PDA和服务器之间是采用了C/S的构架。PC和服务器是采用了B/S的构架。所以系统采用了C/S和B/S的混合构架模式。参考的构架框架采用了MVC三层构架框架。"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1748", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "旧高考/大题/参考答案/联系计网的构架回答问题", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 237, "text": "PDA和服务器之间是采用了C/S的构架。PC和服务器是采用了B/S的构架。结合ADD：先描述构架驱动因素，然后描述选择的构架。然后描述选择的构架，各位把上面说到的的C/S和B/S的优缺点，写上去，并且说出C/S和B/S混合后的优点，.NET框架的优缺点。，最后描述下分配的功能。\n\n三层构架优缺点：\n\n三层构架与具体语言没有关系\n\n广义的为数据层逻辑层显示层\n\n优点是代码复用性提高可维护性搞维护起来方便层与层之间分离\n\n缺点是如果你写的项目比较小那代码量可能比不用三层更多"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1749", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "旧高考/大题/例题二：购物中心", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 559, "text": "Suppose the business context of an enterprise with a product center and many stores including the tasks as are shown below: 假设一个企业的业务环境包括一个产品中心和许多商店，包括如下所示的任务：\n\n1. All of the products in each store are supplied by the product center.\n2. A shopping guide help a customer plays order for some products on the scene of a store with portable equipment.\n3. A shopping guide uses a portable equipment to identify each product and look through the product information in detail for helping the sale.\n4. A shopping guide use a portable equipment to take stock ( 盘点 )."}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1750", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "旧高考/大题/例题二：购物中心", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 406, "text": "in detail for helping the sale.\n4. A shopping guide use a portable equipment to take stock ( 盘点 ).\n5. The administrator of the store use personal computer to know something about the sales and the customers involving in the sales periodically.\n\n1、每个商店的产品都由产品中心提供。\n\n2、一个购物指南帮助客户在一家商店的场景中使用便携式设备，对一些产品起着订单的帮助。\n\n3、购物指南使用便携式设备来识别每一个产品，并通过详细的产品信息来帮助销售。\n\n4、物指南使用便携式设备进行盘点（盘点）。\n\n5、本店的管理者使用个人计算机对销售人员和客户定期对销售情况有了解。"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1751", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "旧高考/大题/例题二：购物中心", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 698, "text": "3、购物指南使用便携式设备来识别每一个产品，并通过详细的产品信息来帮助销售。\n\n4、物指南使用便携式设备进行盘点（盘点）。\n\n5、本店的管理者使用个人计算机对销售人员和客户定期对销售情况有了解。\n\nAn IT team are asked to design a software system for the company to help the persona of the context to accomplish the tasks efficiently and effectively based on the RFID identify technology (射频识别). With this technology, the information of a product could be stored in the RFID card (A card works as the meal card does in the canteen) and detected by the portable data detect terminal of PDA with RFID Reader and Writer. The system should include four aspects of the inventory(存货清单), the sales, the stock and the returned goods as well as achieving the goals of portable shopping guide, playing order"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1752", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "旧高考/大题/例题二：购物中心", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 555, "text": "ock and the returned goods as well as achieving the goals of portable shopping guide, playing order rapidly on the scene, taking stock quickly on the spot and CRM (Customer Relationship Management).\n\nIT团队被要求设计一个公司的帮助下有效地完成任务的人的软件系统和基于RFID识别技术有效（射频识别）。利用这种技术，一个产品的信息可以存储在RFID卡（一卡作为餐卡在食堂）和便携式数据检测PDA与RFID读写终端检测。该体系应包括四个方面的库存（存货清单）、销售、库存、退货以及实现便携式购物指南的目标，播放顺序迅速在现场，盘点现场快和CRM（客户关系管理）。\n\nAs a software architect, you are asked to design software architecture to achieve the goals of the system following the steps of ADD. 作为一个软件架构师，你被要求设计软件体系结构，以实现该系统的目标，之后的步骤。"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1753", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "旧高考/大题/例题二：购物中心", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 617, "text": "chieve the goals of the system following the steps of ADD. 作为一个软件架构师，你被要求设计软件体系结构，以实现该系统的目标，之后的步骤。\n\n1. Please separately give 5 quality attribute scenarios to define the security and 5 scenarios to define the modifiability of the system (Score 10). 请分别给 5 个质量属性场景定义安全和 5 个场景，定义系统的可修改性（10分）。\n\n1. Please separately present 5 tactics to achieve the security and 5 tactics to achieve modifiability (Score 10). 请分别提出 5 个策略来实现安全和 5 策略实现可变性（10分）。\n\n1. To trade off the usability and the security, please choose an architecture pattern for the system with detail explanations (Score 10). 为了交易的可用性和安全性，请选择一个系统的架构模式与详细的解释（得分10）。"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1754", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "旧高考/大题/例题二：购物中心", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 320, "text": "pattern for the system with detail explanations (Score 10). 为了交易的可用性和安全性，请选择一个系统的架构模式与详细的解释（得分10）。\n\n1. Please present the *component-and-connector* view of the system design based on the modeling language of UML2.0 and explain the technical rationale of the view (Score 10). 请提供基于UML2.0建模语言设计系统的组件和连接器的看法和解释视图的技术原理（10分）。"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1755", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "旧高考/大题/参考答案/1", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 655, "text": "As to the system described above,\n\nSecurity could be defined by the 5 scenarios as follows:\n\n1. Integrity of data: The system should deny unauthorized visits. The shopping guide cannot use PDA subsystem to revise the order that have been played.\n2. Confidentiality of data: The shopping guide can read the customer information relative to play the order, but cannot read the customer information in more detail.\n3. Resist attacks: The system should authorize the user and has an effective access control system.\n4. Detect attacks: Malicious attacks should be detected by the system.\n5. Recover from the attacks: Should audit and trace the user’s behavior."}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1756", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "旧高考/大题/参考答案/1", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 686, "text": "e detected by the system.\n5. Recover from the attacks: Should audit and trace the user’s behavior.\n\nAnd modifiability could be defined by the 5 scenarios as follows:\n\n1. Support to the modification of the PDA.\n2. Support to the modification of the users and the rights of users.\n3. Support to the modification of the RFID cards and the products.\n4. Support to the modification of the work of flow for the tasks of playing order.\n5. Support for the modification of the Database and web server.\n\n如上所述的系统，\n\n安全可以被定义为如下5种情况：\n\n（1）数据的完整性：系统应拒绝未经授权的访问。导购不能使用PDA系统修改打过的订单。\n\n（2）资料的机密性：购物指南可以读取客户信息，而不可播放该命令，但无法更详细地读取客户信息。\n\n（3）抗攻击：系统应提供授权用户，并具有有效的存取控制系统。\n\n（4）检测攻击：系统中的恶意攻击。\n\n（5）从攻击中恢复：应审核和跟踪用户的行为。"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1757", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "旧高考/大题/参考答案/1", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 211, "text": "而不可播放该命令，但无法更详细地读取客户信息。\n\n（3）抗攻击：系统应提供授权用户，并具有有效的存取控制系统。\n\n（4）检测攻击：系统中的恶意攻击。\n\n（5）从攻击中恢复：应审核和跟踪用户的行为。\n\n和可变性可以由5种情况如下定义：\n\n（1）支持PDA的改性。\n\n（2）支持对用户和用户权利的修改。\n\n（3）支持对射频识别卡及产品的修改。\n\n（4）支持对游戏任务的工作流程的修改。\n\n（5）支持对数据库和网络服务器的修改。"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1758", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "旧高考/大题/参考答案/2", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 418, "text": "Security tacticsModifiability tacticsMaintain the integrity and confidentiality of the data of customer, product or order via an RBAC subsystem;Provide identity authentication mechanism on the PDA; Monitor user’s behavior on the server;Audit the users’ behavior via the system logs；Limit the exposure and access of the data.1）维护客户数据的完整性和保密性，产品或订单通过RBAC系统；2）提供对PDA的身份认证机制；3）监视用户在服务器上的行为；4）通过系统日志审核用户行为；5）限制数据的曝光和访问。"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1759", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "旧高考/大题/参考答案/2", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 601, "text": "the data.1）维护客户数据的完整性和保密性，产品或订单通过RBAC系统；2）提供对PDA的身份认证机制；3）监视用户在服务器上的行为；4）通过系统日志审核用户行为；5）限制数据的曝光和访问。Localize the changes by abstract common services, e.g. provide the unified identity authentication ;Prevent ripple effects via hiding information; Defer the binding time via the configuration document, e.g. configure the data of enumeration；Separate system into 3 parts：the data presentation, the business logic and the data accessing；Use the intermediary to prevent the ripple effects.1）本地化的变化，抽象的共同服务，例如提供统一的身份验证；2）通过隐藏信息来防止纹波效应；通过配置文件推迟绑定时间，例如配置枚举数；3）分系统分为3部分：数据表示、业务逻辑和数据访问；4）利用中介机构，以防涟漪效应。"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1760", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "旧高考/大题/参考答案/3", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 519, "text": "（1）Hierarchy distribution architecture pattern could be adopted.\n\n（2）In detail, C/S and B/S hybrid distribution patterns could be selected to trade off usability and security for the system.\n\n（3）Also, MVC architecture patterns could be utilized to enhance the usability of the system without losing security.\n\n（4）RBAC subsystem could be used to balance usability and security.\n\n（1）可采用分层分布结构模式。\n\n（2）详细说明，可选择以可供选择的方式，以供系统的可用性和安全性，以供选择。\n\n（3）另外，MVC架构模式可以用来提高系统的可用性不失安全。\n\n（4）基于角色的访问控制子系统可以用来平衡安全性和易用性。\n\n 4. 为了平衡易用性、安全性和可修改性。"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1761", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "旧高考/大题/参考答案/4", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 669, "text": "As is shown in the picture, the system is divided into the levels as follows：\n\n1. View level which is composed of the pages of . aspx.\n2. Controller level which is composed of controller components dealing with the business logic.\n3. Model level which is composed of service components dealing with service, model component, and DAO component.\n4. Database level which is composed of SQL Server 2005 to store the data with persistence.\n5. Service level which is also composed of service component for connection and exchanging of the data on the heterogeneous devices or system.\n\n如图所示，系统分为以下等级：\n\n（1）认为一级由网页组成。aspx。\n\n（2）由控制器组件组成的控制器级处理业务逻辑。\n\n（3）由服务组件组成的模型级处理服务、模型组件和道组件。"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1762", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "旧高考/大题/参考答案/4", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 567, "text": "system.\n\n如图所示，系统分为以下等级：\n\n（1）认为一级由网页组成。aspx。\n\n（2）由控制器组件组成的控制器级处理业务逻辑。\n\n（3）由服务组件组成的模型级处理服务、模型组件和道组件。\n\n（4）数据库由SQL Server 2005数据存储的持久性。\n\n（5）服务水平，也由服务组件组成，用于连接和交换异构设备或系统中的数据。\n\nThe technical rationale of the view includes:\n\n1. Reference model: hierarchy model\n2. Architecture pattern: the CS and BS hybrid pattern for distribution system;\n3. Reference framework:\n\n 1. WinForm GUI framework on the PDA part；\n 2. Web service technology is used to exchange the data of PDA and database of SQL Server 2005.\n 3. Asp .NET MVC3 framework on the PC part；\n 4. ORM framework;"}
{"id": "docx::OASaw5mvziULPykvwCRctzLzngb::1763", "page_id": "docx::OASaw5mvziULPykvwCRctzLzngb", "title": "真题解析", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/真题解析", "section": "旧高考/大题/参考答案/4", "url": "https://a1npn29y3xu.feishu.cn/wiki/OASaw5mvziULPykvwCRctzLzngb", "source_type": "docx", "n_chars": 603, "text": "and database of SQL Server 2005.\n 3. Asp .NET MVC3 framework on the PC part；\n 4. ORM framework;\n 5. Spring.Net MVC AOP framework：From the special business logic services, abstract the common services such as access control, system log, concurrency control, transaction processing and so on, as a result, the modifiability of the system is enhanced significantly.\n\n视图的技术原理包括：\n\n（1）参考模型：层次模型\n\n（2）建筑模式：配电系统的政务和混合模式；\n\n（3）参考框架：\n\na）在PDA部分WinForm界面框架；\n\nB）Web服务技术应用到PDA和SQL Server 2005数据库的数据交换。\n\nc）在PC部分ASP。NET MVC3框架；\n\nd）ORM框架；\n\ne）Spring.NET AOP框架：MVC从特定业务逻辑服务，摘要共同服务，如访问控制、系统日志、并发控制、事务处理等，因此，系统的可修改性显著提高。"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1764", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2023 年 I 卷/一、概念题 6 分 \\* 5 题", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 130, "text": "1. system approach\n2. project management plan\n3. critical path method(CPM) or critical path analysis\n4. quality assurance\n5. scrum"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1765", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2023 年 I 卷/二、简答题 15 分 \\* 2 题", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 126, "text": "1. Describe the main processes and outputs of project scope management\n2. list ten knowledge areas，选一个，介绍3个tools and techiques"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1766", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2023 年 I 卷/三、分析题 15 分 3 问", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 43, "text": "1. 画 gantt graph 5分\n2. 算 NPV 6分\n3. 算 PERT4分"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1767", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2023 年 I 卷/四、计算题 25 分/（一）网络图 15 分 2 问", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1768", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2023 年 I 卷/四、计算题 25 分/（二） 挣值管理 10 分 2 问", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 50, "text": "（1）EV，SV，CV，SPI，CPI 6 分\n\n（2）画 earn value chart 4 分"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1769", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2023 年 I 卷/参考答案/概念题/system approach 2.1.1 标题 中-33", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 169, "text": "\n\n\n\n"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1770", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2023 年 I 卷/参考答案/概念题/project management plan 4.3 标题 中-115", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 169, "text": "\n\n\n\n"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1771", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2023 年 I 卷/参考答案/概念题/critical path method (CPM) or critical path analysis 6.7.2 标题 中-174", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 169, "text": "\n\n\n\n"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1772", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2023 年 I 卷/参考答案/概念题/quality assurance 8.4 标题 中-227", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 169, "text": "\n\n\n\n"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1773", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2023 年 I 卷/参考答案/概念题/scrum 2.6.4.2 核心概念 中-52", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 226, "text": "\n\n\n\n\n\n"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1774", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2023 年 I 卷/参考答案/简答题/Describe the main processes and outputs of project scope management 5.1", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1775", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2023 年 I 卷/参考答案/简答题/List ten knowledge areas，选一个，介绍 3 个 tools and techiques", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 357, "text": "\n\n\n\n\n\n**有没有发现 10 个知识领域正好做到了一一对应呢？**\n\n**考场上发现这个规律的同学可以快速地将标题默写完整，并且去寻找自己最熟悉的工具技术拿下 12+！**\n\n这里给出官方的一张表，这张表用来解答刚刚好\n\n"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1776", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2023 年 I 卷/参考答案/分析题/画 gantt graph 5 分", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1777", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2023 年 I 卷/参考答案/分析题/算 NPV 6 分", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1778", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2023 年 I 卷/计算题（兵家必争之地）/已知数据的网络图计算", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1779", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2023 年 I 卷/计算题（兵家必争之地）/已知数据的网络图计算/正向传播，计算 ES 和 EF", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 194, "text": "| | ES | EF |\n|-|-|-|\n| A = 3 | 0 | 0 + 3 = 3 |\n| B = 6 | 8 - 6 = 2 | 3 + 5 = 8 |\n| C = 5 | 6 - 5 = 1 | 2 + 4 = 6 |\n| D = 6 | 3 + 6 = 9 | 9 + 6 = 15 |\n| E = 2 | MAX (6, 15) = 15 | 15 + 2 = 17 |"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1780", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2023 年 I 卷/计算题（兵家必争之地）/已知数据的网络图计算/正向传播，计算 ES 和 EF/反向传播，计算 LS 和 LF", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 211, "text": "| | ES | EF | LS | LF |\n|-|-|-|-|-|\n| A = 3 | 0 | 3 | 0 | 9 - 6 = 3 |\n| B = 6 | 2 | 8 | 15 - 4 = 11 | 11 + 6 = 17 |\n| C = 5 | 1 | 6 | 15 - 5 = 10 | 15 |\n| D = 6 | 9 | 15 | 9 | 15 |\n| E = 2 | 15 | 17 | 15 | 17 |"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1781", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2023 年 I 卷/计算题（兵家必争之地）/已知数据的网络图计算/正向传播，计算 ES 和 EF/最终结果（TF 和 FF 只能针对某个节点进行计算，下面给出公式）", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 409, "text": "| | ES | EF | LS | LF |\n|-|-|-|-|-|\n| A = 3 | 0 | 3 | 0 | 3 |\n| B = 6 | 2 | 8 | 11 | 17 |\n| C = 5 | 1 | 6 | 10 | 15 |\n| D = 6 | 9 | 15 | 9 | 15 |\n| E = 2 | 15 | 17 | 15 | 17 |\n\n**总时差（总浮动时间）= LS - ES = LF - EF**\n\n**（一项工作不影响总工期的前提下所具有的动机时间）**\n\n**自由浮动=min（ 随后活动的ES - 当前活动的EF ）**\n\n**（一项工作不影响后续工作的情况下拥有的动机时间）**\n\n **Free Float 是 min {后继所有节点的ES - 当前活动的 EF }，Total Float 是不是 LS - ES**\n\n**关键活动（关键路径上的活动）的总时差，自由时差都是0**"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1782", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2023 年 I 卷/真题小结", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 240, "text": "1. 概念题要么是课本的**标题**，要么是在课本原文中加粗的（如果是中文版的教材，大家有没有发现**老师考的概念全部都是中文括号加粗后面有英文括号的**呀！）\n2. 简答和分析题今年合并成材料分析大题了，是拉分题。但是有材料的好处是大家可以誊抄\n3. 计算题是兵家必争之地，因为**能考计算的章节只有：4 5 7 （11）！**每年的分值都在 25 — 30 分之间。数据一般不会太难，**公式列对了就有一半分**，要想及格，必须把计算题吃下来！（今年的计算题价值 30 分！）"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1783", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2023 年 I 卷/最后，让我们来看看四份讲义对应的题目和分值吧", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 316, "text": "| 讲义标题 | 对应题号 | 对应分值 |\n|-|-|-|\n| （一） 01 \\~ 03 | 1，5，7 | 6 + 6 + 15 = 22 |\n| （二） 04 \\~ 07 | 2，3，6，8，9，10，11，12 | 12 + 31 + 29 + 10 = 72 |\n| 4 Integration | 2，9 | 6 + 6 = 12 |\n| 5 Scope | 6 | 15 |\n| 6 Time | 3，8，10，11 | 6 + 6 + 4 + 15 = 31 |\n| 7 Cost | 12 | 10 |\n| （三） 08 \\~ 10 | 4 | 6 = 6 |\n| （四） 11 \\~ 13 | —— | 0 |"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1784", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2023 年 II 卷 (只有知识点，没有解析)/题目分配与知识点分布", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 658, "text": "1. 名词解释 x 4\\~5 20\\~25'\n2. 简答题 x3 25\\~30\n3. 计算 x2 30\\~35\n4. 综合分析 给场景 15\\~20\n\n1. 第一章\n\n项目基本概念\n\n\n\n图1-2\n\n\n\n1. 第二章\n\n4个框架\n\n\n\n职能类型\n\n\n\n企业文化\n\n\n\n\n\n高层对项目的支持势\n\n\n\n\n\n敏捷的一些框架/概念\n\n"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1785", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2023 年 II 卷 (只有知识点，没有解析)/题目分配与知识点分布", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 673, "text": "/ZYj9bFwQ9o4BZKx4GoIchJ1ynVh)\n\n敏捷的一些框架/概念\n\n\n\n\n\n\n\n\n\n影响项目的趋势 = 全球化 + 外包 + 虚拟团队 + 敏捷项目管理\n\n\n\n1. 第三章\n\n十大知识领域 过程组\n\n\n\n燃尽图\n\n\n\n1. 第四章\n\n继承管理\n\nSWOT\n\n方法:财务方法->计算 ROI,IRR概念\n\n加权评分模型\n\n\n\n\n\n平衡积分卡"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1786", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2023 年 II 卷 (只有知识点，没有解析)/题目分配与知识点分布", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 661, "text": "/file/ToPrbPnYvoWavcxk0zhcgGUTnpd)\n\n\n\n平衡积分卡\n\n\n\n变更管理：几大体系（流程）\n\n\n\n\n\n\n\n\n\n\n\n1. 第五章\n\n范围，交付物\n\n\n\n\n\n需求->方法\n\n\n\n模型 ?\n\nWBS"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1787", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2023 年 II 卷 (只有知识点，没有解析)/题目分配与知识点分布", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 691, "text": "b9yo0dBqxW3iVcomvDn5c)\n\n需求->方法\n\n\n\n模型 ?\n\nWBS\n\n\n\n\n\n1. 第八章\n\n质量管理基本概念 功能\n\n\n\n性能\n\n\n\n谁为质量负责\n\n\n\n控制方法（7个工具）\n\n因果图/鱼骨图/石川图、控制图、检查表、散点图、直方图、帕累托图、流程图\n\n越大质量越_难_测试\n\n如何提高质量\n\n\n\n不一致成本\n\n\n\n1. 第九章\n\n马斯洛层次需求理论、哪些因素不可少\n\n"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1788", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2023 年 II 卷 (只有知识点，没有解析)/题目分配与知识点分布", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 439, "text": "xZpuNcQtH5n5b)\n\n1. 第九章\n\n马斯洛层次需求理论、哪些因素不可少\n\n\n\n各种理论和各个因素的影响 （P261 -- P267）\n\n柱状图\n\n\n\n资源平衡阶段\n\n\n\nWBII ?\n\n1. 第十章\n\n沟通渠道计算 n \\* (n - 1) / 2\n\n1. 第十一章\n\n三种风险概念(风险规避)\n\n\n\nEMV计算\n\n"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1789", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2023 年 II 卷 (只有知识点，没有解析)/分析题（第 10 章 沟通管理）", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1790", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2022 年 I 卷/一、**概念解释 5 分 \\* 6 题**", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 30, "text": "项目管理\n\nSDLC\n\n成本\n\n质量\n\n定性风险分析\n\n范围"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1791", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2022 年 I 卷/二、**简答题 15 分 \\* 2 题**", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 33, "text": "项目管理计划包含哪些内容？有哪些共同点？\n\n干系人管理的主要过程？"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1792", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2022 年 I 卷/四、**计算题 25 分**", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 87, "text": "画网络图，计算关键路径、**浮动时间**。减少某个活动的时间后，分析对关键路径会产生什么样的影响\n\n画决策树并计算预期货币值EMV\n\n根据题目给出的信息计算挣值管理的所有内容"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1793", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2022 年 I 卷/参考答案/概念题/Project management 1.3 标题 中-7", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1794", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2022 年 I 卷/参考答案/概念题/SDLC 2.4.1 标题 中-44", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1795", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2022 年 I 卷/参考答案/概念题/Cost 7.1.1 标题 中-196", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 86, "text": "成本是为实现一个**特定目标**而**牺牲或放弃**的资源\n\n"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1796", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2022 年 I 卷/参考答案/概念题/Quality 8.2 标题 中-224", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 169, "text": "\n\n\n\n"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1797", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2022 年 I 卷/参考答案/概念题/Performing Qualitive Risk Analysis 11.5 标题 中-329", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1798", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2022 年 I 卷/参考答案/概念题/Scope 5.1 标题 中-134", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1799", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2022 年 I 卷/参考答案/简答题/项目管理计划包含哪些内容？有哪些共同点？", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 169, "text": "\n\n\n\n"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1800", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2022 年 I 卷/参考答案/简答题/干系人管理的主要过程？", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1801", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2022 年 I 卷/最后，让我们来看看四份讲义对应的题目和分值吧", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 305, "text": "| 讲义标题 | 对应题号 | 对应分值 |\n|-|-|-|\n| （一） 01 \\~ 03 | 1,2 | 5 + 5 = 10 |\n| （二） 04 \\~ 07 | 3,4,6,7,8,9,10,12 | 15 + 20 + 10 + 15 = 60 |\n| 4 Integration | 7 | 15 |\n| 5 Scope | 6,9 | 5 + 15 |\n| 6 Time | 10 | 10 |\n| 7 Cost | 3,12 | 5 + 10 |\n| （三） 08 \\~ 10 | 4,8 | 5 + 15 = 20 |\n| （四） 11 \\~ 13 | 5,11 | 5 + 5 = 10 |"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1802", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2022 年 II 卷/一、**概念解释** (6 分 \\* 5 题 = 30 分)", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 66, "text": "1. stakeholder\n2. scope\n3. duration\n4. quality\n5. resource loading"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1803", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2022 年 II 卷/二、**简答题** (15 分 \\* 2 题 = 30)", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 118, "text": "1. Narrate the flow of project cost management\n2. Narrate the basic response strategies for positive and negative risk"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1804", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2022 年 II 卷/三、**分析题**（15 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 85, "text": "\n\n1. 画 WBS(10)\n2. 列出三种可能的风险(5)"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1805", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2022 年 II 卷/四、计算题（ 9 分 + 16 分 ）/**计算题 1**", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 58, "text": "1. 画网络图(5)\n2. 算关键路径(2)\n3. duration of c 改为10之后, 关键路径是多少(2)"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1806", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2022 年 II 卷/参考答案/概念题/stakeholder 1.3.1 标题 中-8", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1807", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2022 年 II 卷/参考答案/概念题/duration 6.6 标题 中-170", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 169, "text": "\n\n**Duration** includes the actual amount of time worked on an activity *plus* elapsed time / 工期包括活动上花费的实际时间和占用时间。"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1808", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2022 年 II 卷/参考答案/概念题/resource loading 9.5.2 标题 中-273", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1809", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2022 年 II 卷/参考答案/简答题/Narrate the flow of project cost management", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1810", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2022 年 II 卷/参考答案/简答题/Narrate the basic response strategies for positive and negative risk", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1811", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2022 年 II 卷/参考答案/分析题", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1812", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2022 年 II 卷/参考答案/分析题/列出三种可能的风险(5) —— 言之有理即可给分", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 169, "text": "范围角度：如果三位员工的工作之间耦合度过高，很有可能同时降低效率\n\n成本角度：给三位员工的成本分配如果出现不匹配的情况，则会及其影响员工的积极性\n\n人力资源角度：员工 3 承担工作过重，一旦员工 3 工作出现问题，则难以开展\n\n"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1813", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2022 年 II 卷/参考答案/计算题/时间管理综合大题/画网络图(5)", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1814", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2022 年 II 卷/最后，让我们来看看四份讲义对应的题目和分值吧", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 317, "text": "| 讲义标题 | 对应题号 | 对应分值 |\n|-|-|-|\n| （一） 01 \\~ 03 | 1 | 6 |\n| （二） 04 \\~ 07 | 2,3,6,8,10,11 | 6 + 6 + 15 + 10 + 9 + 16 = 62 |\n| 4 Integration | —— | 0 |\n| 5 Scope | 2,8 | 6 + 10 = 16 |\n| 6 Time | 3,10 | 6 + 9 = 15 |\n| 7 Cost | 6,11 | 15 + 16 = 31 |\n| （三） 08 \\~ 10 | 4,5 | 6 + 6 = 12 |\n| （四） 11 \\~ 13 | 7,9 | 15 + 5 = 20 |"}
{"id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ::1815", "page_id": "docx::YyAVwRCVwiLDjykWpI3cAQ06npJ", "title": "真题解析", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/真题解析", "section": "新高考真题详解/2020 年 I 卷", "url": "https://a1npn29y3xu.feishu.cn/wiki/YyAVwRCVwiLDjykWpI3cAQ06npJ", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1816", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2013 ✅ Hard/参考答案/填空题（20 空，1 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 661, "text": "1. **data model**\n\n\n\n1. **physical, logial**\n\n\n\n1. **total participation, partial participation**\n\n\n\n1. **view**\n\n\n\n1. **foreign key, check, unique, default**\n\n**这一系列关键词都是 integrity constraints**\n\n\n\n1. **atomicity consistency isolation**\n\n\n\n1. **search-key, pointer**\n\n\n\n1."}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1817", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2013 ✅ Hard/参考答案/填空题（20 空，1 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 544, "text": "cwf5wnNg)\n\n1. **search-key, pointer**\n\n\n\n1.\n\n\n\n1. **selection and projection, restrictive selection and join operation**\n\n**第 13 章 Summary**\n\n\n\n\n\n1. **shared, exclusive**\n\n\n\n1. **immediate database, uncommitted**\n\n"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1818", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2013 ✅ Hard/参考答案/综合题/阅读 ER 图，回答以下问题", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1819", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2013 ✅ Hard/参考答案/综合题/阅读 ER 图，回答以下问题/b) 为以上的 ER 图构建出合理的 relation schema", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 170, "text": "Apply_Form (apply_id, subject, managers)\n\nRepairer (repairer_id, name)\n\nRepair_record (apply_id, repairer_id, record_id, repair_date, fee)\n\nREPAIR(repaired_id, record_id)"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1820", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2013 ✅ Hard/参考答案/综合题/阅读 ER 图，回答以下问题/⚠️ c) 给出一个 SQL 的 DDL 定义，这一些语句需要根据你对 ER 图的理解得出。并且在你的 DDL 语句中定义 reference-integrity constraints。/表一：仅创建实体，忽略了关系", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 643, "text": "```SQL\nCREATE TABLE apply_form (\n apply_id BIGINT UNSIGNED PRIMARY KEY NOT NULL AUTO_INCREMENT,\n subject VARCHAR(50) NOT NULL,\n managers VARCHAR(50) NOT NULL\n);\n\nCREATE TABLE repairer (\n repairer_id BIGINT UNSIGNED PRIMARY KEY NOT NULL AUTO_INCREMENT,\n name VARCHAR(50) NOT NULL\n);\n\nCREATE TABLE repair_record (\n record_id BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,\n apply_id BIGINT UNSIGNED,\n repairer_id BIGINT UNSIGNED,\n repair_date DATE NOT NULL DEFAULT CURRENT_DATE,\n fee BIGINT UNSIGNED DEFAULT 0,\n PRIMARY KEY (apply_id, repairer_id, record_id),\n FOREIGN KEY (apply_id) REFERENCES apply_form(apply_id),"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1821", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2013 ✅ Hard/参考答案/综合题/阅读 ER 图，回答以下问题/⚠️ c) 给出一个 SQL 的 DDL 定义，这一些语句需要根据你对 ER 图的理解得出。并且在你的 DDL 语句中定义 reference-integrity constraints。/表一：仅创建实体，忽略了关系", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 169, "text": "KEY (apply_id, repairer_id, record_id),\n FOREIGN KEY (apply_id) REFERENCES apply_form(apply_id),\n FOREIGN KEY (repairer_id) REFERENCES repairer(repairer_id)\n);\n```"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1822", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2013 ✅ Hard/参考答案/综合题/阅读 ER 图，回答以下问题/⚠️ c) 给出一个 SQL 的 DDL 定义，这一些语句需要根据你对 ER 图的理解得出。并且在你的 DDL 语句中定义 reference-integrity constraints。/表二：多对多关系单独列表", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 650, "text": "```SQL\nCREATE TABLE apply_form (\n apply_id CHAR(11) NOT NULL,\n subject VARCHAR(11) NOT NULL,\n CONSTRAINT A_id PRIMARY KEY (apply_id)\n);\n\nCREATE TABLE repairer (\n repairer_id CHAR(11) NOT NULL,\n name VARCHAR(11) NOT NULL,\n r_id CHAR(11) NOT NULL,\n CONSTRAINT P_id PRIMARY KEY (repairer_id),\n CONSTRAINT FK_A FOREIGN KEY (r_id) REFERENCES repair_record(record_id)\n);\n\nCREATE TABLE repair_record (\n record_id CHAR(11) NOT NULL,\n fee FLOAT(5, 2) NOT NULL,\n repair_date DATE NOT NULL,\n CONSTRAINT R_id PRIMARY KEY (record_id)\n);\n\nCREATE TABLE repair (\n record_id CHAR(11) NOT NULL,\n repairer_id CHAR(11) NOT NULL,"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1823", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2013 ✅ Hard/参考答案/综合题/阅读 ER 图，回答以下问题/⚠️ c) 给出一个 SQL 的 DDL 定义，这一些语句需要根据你对 ER 图的理解得出。并且在你的 DDL 语句中定义 reference-integrity constraints。/表二：多对多关系单独列表", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 336, "text": "d_id)\n);\n\nCREATE TABLE repair (\n record_id CHAR(11) NOT NULL,\n repairer_id CHAR(11) NOT NULL,\n CONSTRAINT FK_R FOREIGN KEY (record_id) REFERENCES repair_record(record_id),\n CONSTRAINT FK_P FOREIGN KEY (repairer_id) REFERENCES repairer(repairer_id),\n CONSTRAINT RP_id PRIMARY KEY (record_id, repairer_id) -- 添加复合主键\n);\n```"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1824", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2013 ✅ Hard/参考答案/综合题/范式计算分析", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1825", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2013 ✅ Hard/参考答案/综合题/范式计算分析/a) 求解（BD）+", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 38, "text": "B 和 D 都能推出 AC，A 和 C 可以相互推导，但是没看到 E 的影子"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1826", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2013 ✅ Hard/参考答案/综合题/范式计算分析/b) 求解 R 的候选码", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 244, "text": "什么是候选码？\n\n\n\n\n\n根据题目我们可以得到，E 一定得在候选码的行列里面，因为 ABCD 没有任何一个属性能推导出 E\n\n至于 ABCD 嘛，根据题意，选 B 或者选 D 都可以把 AC 推出来，但是 B 和 D 无法互相推出来\n\n所以 R 的候选码应该是 BDE"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1827", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2013 ✅ Hard/参考答案/综合题/范式计算分析/⚠️ c) 将分解变成 BCNF", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 174, "text": "\n\n我们应该消除 B -> A -> C 的传递依赖\n\nR1 （B, A）\n\nR2 （D, C）\n\nR3 （B, D, E）\n\n"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1828", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2013 ✅ Hard/参考答案/综合题/前五问 SQL，后两问 关系代数", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1829", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2013 ✅ Hard/参考答案/综合题/前五问 SQL，后两问 关系代数/a) 从 PART 表中寻找到最轻零件的 PNO", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 87, "text": "```SQL\n-- 使用 min\nselect pno\nfrom PART\nwhere weight = (select min(weight) from PART)\n```"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1830", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2013 ✅ Hard/参考答案/综合题/前五问 SQL，后两问 关系代数/⚠️ b) 从 SUPPLIER 表中寻找供应商的 sname 和 scity，这个供应商可以供应项目 J1的所有零件", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 552, "text": "```SQL\n-- 母题来源：求使用了S1 提供的所有零件的工程号码。\nselect distinct spj.JNO\n from spj, j\n where NOT EXISTS (\n SELECT 1\n FROM spj\n WHERE spj.JNO = j.JNO AND spj.SNO != 'S1'\n )\n AND EXISTS (\n SELECT 1\n FROM spj\n WHERE spj.JNO = j.JNO AND spj.SNO = 'S1'\n );\n\n -- 参考答案？求供应项目 J1 的所有零件的供应商的 sname 和 scity\nSELECT s.sname, s.scity\nFROM SUPPLIER s\nWHERE NOT EXISTS (\n SELECT p.pno\n FROM PART p\n WHERE NOT EXISTS (\n SELECT spj.pno\n FROM SPJ spj\n WHERE spj.sno = s.sno AND spj.pno = p.pno AND spj.jno = 'J1'\n )\n);\n\n```\n\n参考思路解析："}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1831", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2013 ✅ Hard/参考答案/综合题/前五问 SQL，后两问 关系代数/⚠️ b) 从 SUPPLIER 表中寻找供应商的 sname 和 scity，这个供应商可以供应项目 J1的所有零件/**1. 找出项目 `J1` 需要的所有零件**", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 85, "text": "从 `SPJ` 表中查询出所有与项目 `J1` 相关的零件：\n\n```SQL\nSELECT pno\nFROM SPJ\nWHERE jno = 'J1';\n```\n\n---"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1832", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2013 ✅ Hard/参考答案/综合题/前五问 SQL，后两问 关系代数/⚠️ b) 从 SUPPLIER 表中寻找供应商的 sname 和 scity，这个供应商可以供应项目 J1的所有零件/**2. 确定某个供应商是否能提供一个具体零件**", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 223, "text": "我们需要检查某个供应商 `sno` 是否能提供一个零件 `pno`：\n\n```SQL\nSELECT spj.pno\nFROM SPJ spj\nWHERE spj.sno = s.sno AND spj.pno = p.pno AND spj.jno = 'J1';\n```\n\n- 这个子查询检查是否存在一个记录，表明供应商 `sno` 提供了零件 `pno` 且零件属于项目 `J1`。\n- 如果这个记录存在，那么该供应商能提供该零件。\n\n---"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1833", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2013 ✅ Hard/参考答案/综合题/前五问 SQL，后两问 关系代数/⚠️ b) 从 SUPPLIER 表中寻找供应商的 sname 和 scity，这个供应商可以供应项目 J1的所有零件/**3. 确保没有零件是供应商无法提供的**", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 330, "text": "- 如果供应商不能提供项目 `J1` 所需的某个零件，那么他就不符合条件。\n- 我们可以用一个双层嵌套的 `NOT EXISTS` 来表示：\n\n - 外层子查询列出项目 `J1` 所需的所有零件。\n - 内层子查询检查供应商是否提供了这些零件。\n\n```SQL\nSELECT p.pno\nFROM PART p\nWHERE NOT EXISTS (\n SELECT spj.pno\n FROM SPJ spj\n WHERE spj.sno = s.sno AND spj.pno = p.pno AND spj.jno = 'J1'\n);\n```\n\n如果 `NOT EXISTS` 返回 `TRUE`，说明供应商没有提供该零件。\n\n---"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1834", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2013 ✅ Hard/参考答案/综合题/前五问 SQL，后两问 关系代数/⚠️ b) 从 SUPPLIER 表中寻找供应商的 sname 和 scity，这个供应商可以供应项目 J1的所有零件/**4. 把条件套用到所有供应商**", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 82, "text": "- 外层查询从 `SUPPLIER` 表中遍历每个供应商。\n- 对于每个供应商，检查是否存在任何他们无法提供的零件（即是否满足 `NOT EXISTS` 的条件）。"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1835", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2013 ✅ Hard/参考答案/综合题/前五问 SQL，后两问 关系代数/⚠️ c) 按照升序排序将每一个项目的零件总数进行排序", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 149, "text": "```SQL\nSELECT j.JNO, j.JNAME, SUM(spj.QTY) AS TOTAL_PARTS\nFROM SPJ spj\nJOIN PROJECT j ON spj.JNO = j.JNO\nGROUP BY j.JNO\nORDER BY TOTAL_PARTS ASC;\n```"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1836", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2013 ✅ Hard/参考答案/综合题/前五问 SQL，后两问 关系代数/d) 将 姓名为 ITM 的供应商的信息进行全部删除（假设没有外键约束）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 138, "text": "```SQL\ndelete from supplier where s.name = 'ITM';\ndelete from spj where spj.sno = (select s.sno from supplier s where s.name = 'ITM');\n```"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1837", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2013 ✅ Hard/参考答案/综合题/前五问 SQL，后两问 关系代数/e) 新增一个在 'Shanghai'，名称是 'Sys' 的项目到 PROJECT 表上", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 71, "text": "```SQL\ninsert into project(jname, jcity) values ('Sys','Shanghai');\n```"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1838", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2013 ✅ Hard/参考答案/综合题/前五问 SQL，后两问 关系代数/欢迎大家积极讨论关系代数相关方案", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1839", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2013 ✅ Hard/参考答案/综合题/Query Processing，继续使用第三问的表格", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 632, "text": "**供应商表 SUPPLIER (SNO,SNAME,STATUS,CITY)**\n\n**零件表 PART (PNO,PNAME,COLOR,WEIGHT)**\n\n**工程项目表 PROJECT (JNO,JNAME,CITY)**\n\n**供应情况表 SPJ (SNO,PNO,JNO,QTY)**\n\n\n\n什么是 expression tree？\n\n\n\n\n\n\n\n这一题考的是 nature-join 和 merge-join 的公式，大家直接把 bp 和 bspj 的公式套进去即可\n\n\n\n\n\n"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1840", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2014 ✅ Medium/参考答案（逐题转写版）/填空题 （20 空，一空 1 分，共 20 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 647, "text": "1. Let R be a relation schema, R1 and R2 form a decomposition of R. Decomposition is a \\_\\_ if for all legal databases instances r of R,\n\n\n\n**lossless**\n\n\n\n1. For evaluating an entire expression tree, \\_\\_ passes on tuples to parent operations even as an operation is being executed.\n\n**UPD:producer-driven(push/eager)**\n\n1. The time it takes for a disk I/O includes block-transfer time and \\_\\_ time. The latter consists of \\_\\_ time and rotational latency.\n\n**disk seeks, MTTF**\n\n"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1841", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2014 ✅ Medium/参考答案（逐题转写版）/填空题 （20 空，一空 1 分，共 20 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 618, "text": "rotational latency.\n\n**disk seeks, MTTF**\n\n\n\n\n\n1. A sequence of primitive operations that can be used to evaluate a query is a \\_\\_ plan.\n\n\n\nhttps://www.sanfoundry.com/rdbms-multiple-choice-questions-answers/#google_vignette\n\n1. In query processing, the query-execution engine takes the \\_\\_ plan which contains detailed information on how a particular query or a set of queries will be executed.\n\n"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1842", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2014 ✅ Medium/参考答案（逐题转写版）/填空题 （20 空，一空 1 分，共 20 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 682, "text": "ery or a set of queries will be executed.\n\n\n\n1. In deferred database modification scheme, \\_\\_ operation is the only operation used in the recovery procedure.\n\n**~~commit~~**\n\n**UPD:应为Redo**\n\n1. Cascading rollbacks can be avoided by applying \\_\\_ two phase locking protocol to transactions in concurrency protocols.\n\n**strict/Rigorous**\n\n\n\n1. \\_\\_ is the most widely used structure for recording the modification of database. Since a failure may occur while an update is taking place, it must be written out to \\_\\_ storage before the actual update to database to be done."}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1843", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2014 ✅ Medium/参考答案（逐题转写版）/填空题 （20 空，一空 1 分，共 20 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 335, "text": "ing place, it must be written out to \\_\\_ storage before the actual update to database to be done.\n\n**Log,** **permanent**\n\n\n\n1. A (possibly concurrent) schedule is serializable if it is \\_\\_ to a serial schedule.\n\n**冲突等价**\n\n"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1844", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2014 ✅ Medium/参考答案（逐题转写版）/综合题 （6 题大题，共 80 分）/范式计算与分析", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 489, "text": "\n\n**a)** ABC → D, (ABC)+ = (ABCD)，D → E, (ABC)+ = (ABCDE)\n\n 又因为 E → A，所以候选码也可以是（EBC），又因为 D → E，所以候选码还可以是（DBC）\n\n候选码：ABC，EBC，DBC\n\nb) 让我们回顾一下范式的要求\n\n\n\n**候选码中的属性是主属性**，ABCDE 全部都是主属性\n\n所以既没有非主属性对码的部分函数依赖，也没有非主属性对码的传递函数依赖\n\n所以 R (A, B, C, D, E) 就是 3NF\n\nc) 我们需要消除 A -> D -> E -> A 的传递依赖\n\nR1（A, B, C, D）\n\nUPD:在$F^+$位于R1-schema的投影中，有$D\\to A $依赖，需要继续分解为R(A,D) R(A,B,D)\n\nR2（D, E）\n\nR3（E, A）"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1845", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2014 ✅ Medium/参考答案（逐题转写版）/综合题 （6 题大题，共 80 分）/Query Processing", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 502, "text": "\n\n看到这一种题，我们先列出一张表格\n\n| | R | S |\n|-|-|-|\n| 元组总数 | 10,000 | 2,000 |\n| 每页有多少个元组 | 10 | 10 |\n| 总共多少页 | 1000 | 200 |\n\nSort-merge join 的公式？\n\n针对已经排序好的：（1000 + 200） + 向上取整（ 1000 / 15 ）+ 向上取整（ 200 / 15 ）\n\n\n\n针对没有排序好的，还需要额外加上排序的损失：\n\n\n\n\n\n"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1846", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2014 ✅ Medium/参考答案（逐题转写版）/综合题 （6 题大题，共 80 分）/概念简答题", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 166, "text": "**Describe the process of cost-based optimization.**\n\n\n\n"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1847", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2014 ✅ Medium/参考答案（逐题转写版）/综合题 （6 题大题，共 80 分）/Serializable Schedules", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 674, "text": "\n\n回顾**可串行化**的定义：\n\n\n\n\n\n但是我们真正做题的时候，如果我们还采用这种所谓的“非冲突指令”进行求解，那太繁琐了，我们有必要引入我们在数据库学过的一个概念：**有向无环图**。\n\n\n\n\n\n针对这一道题，我们可以画一个图，去判定两个调度是否成环。\n\n在画这一道题的图之前，让我们来看看老师举的画图案例\n\n\n\n再来看看这一道题的解决方案\n\n\n\n\n\n"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1848", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/参考答案/填空题（20 空，一空 1 分，共 20 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 696, "text": "1. **instance（实例） schema**\n\n\n\n1. **3, trivial functional dependency（平凡函数依赖）**\n\n\n\n1. **lossless decomposition（2014 真题复现）**\n\n\n\n1. **attributes, relationship**\n\n\n\n1. **br + bs**\n\n\n\n1. **uniform, random**\n\n\n\n1. **equivalence rules**\n\n\n\n1. [log[n/2]K] （年真题复现）\n\n"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1849", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/参考答案/填空题（20 空，一空 1 分，共 20 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 656, "text": "g6zxvzSMcm2BDnnh)\n\n1. [log[n/2]K] （年真题复现）\n\n\n\n1. **atomicity consistency （2013 年真题复现，填空题英文拿不准宁可写中文保正确性）**\n\n\n\n1. **partically, aborted**\n\n\n\n\n\n1. **recoverable**\n\n\n\n1. **Composite, multivated**\n\n\n\n\n\n1. **foreign key**\n\n"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1850", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/参考答案/综合题（5 道大题，共 80 分）/ER 图设计（16 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 511, "text": "[16 points] Database designⅠ: Consider the following conditions\n\n1. The STUDENT may be taught by one and only one teacher . The TEACHER may be instructor of one or more STUDENT .\n2. The TEACHER may be responsible for one and only one CLASS . The CLASS may be the responsibility of one and only one TEACHER .\n3. The CLASS may be made of one of one or more STUDENT . The STUDENT must be a member of one and only one CLASS .\n4. The CLASS must have one and only are ROOM . The ROOM may belong to one or more CLASS ."}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1851", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/参考答案/综合题（5 道大题，共 80 分）/ER 图设计（16 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 669, "text": "CLASS .\n4. The CLASS must have one and only are ROOM . The ROOM may belong to one or more CLASS .\n\n Notes : Assume entity CLASS has the following attributes : CID and CNAME , entity ROOM has the following attributes : RID and LOCATION , entity STUDENT has the following attributes : SID , LASTNAME , and FIRSTNAME , entity TEACHER has following attributes : TID ,TEACHERNAME , and TITLE .\n\n1. [8 points] Construct an E-R diagram showing these relationships .\n\n\n\n1. [4 points] Construct appropriate relation schemas for the above E-R diagrams .\n\n```SQL\nstudent(sid, lastname, firstname, tid)\ninstrcution(sid, tid)"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1852", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/参考答案/综合题（5 道大题，共 80 分）/ER 图设计（16 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 474, "text": "s for the above E-R diagrams .\n\n```SQL\nstudent(sid, lastname, firstname, tid)\ninstrcution(sid, tid)\nteacher(tid, teachername, title, cid)\nclass(cid, cname, rid)\nroom(rid, location)\nmake(sid, cid)\n```\n\n1. ⚠️ [4 points] Create an index *std_index* on the **student** relation with **SID** as the *search_key* .\n\n\n\n\n\n```SQL\ncreate index std_index on student(SID);\n```"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1853", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/参考答案/综合题（5 道大题，共 80 分）/概念简答题（6 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 692, "text": "[6 points] In database design , how to represent relationship set as relational schema ?\n\n\n\n\n\n\n\n参考论述：\n\nIn database design, representing a relationship set as a relational schema involves creating a table structure that captures the entities and their relationships in a way that adheres to the principles of relational database design. Here's a step-by-step guide on how to represent a relationship set as a relational schema:\n\n1. **Identify Entities and Attributes:**\n\n - Determine the entities involved in the relationship."}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1854", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/参考答案/综合题（5 道大题，共 80 分）/概念简答题（6 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 641, "text": "1. **Identify Entities and Attributes:**\n\n - Determine the entities involved in the relationship.\n - Identify the attributes (columns) that describe each entity.\n\n1. **Determine the Relationship Type:**\n\n - Understand the nature of the relationship (one-to-one, one-to-many, many-to-many).\n - This will help in deciding the structure of the relational schema.\n\n1. **Create Primary Keys:**\n\n - Assign a unique identifier (primary key) to each entity to ensure that each record can be uniquely identified.\n\n1. **Define Foreign Keys:**\n\n - For relationships, use foreign keys in the related tables to maintain referential integrity."}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1855", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/参考答案/综合题（5 道大题，共 80 分）/概念简答题（6 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 664, "text": "- For relationships, use foreign keys in the related tables to maintain referential integrity.\n - A foreign key in one table points to the primary key of another table.\n\n1. **Normalize the Database:**\n\n - Apply normalization rules to eliminate redundancy and ensure data integrity.\n - The goal is to reduce data anomalies and improve the integrity of the database.\n\n1. **Create the Tables:**\n\n - Based on the entities and their relationships, create tables for each entity.\n - Include the primary keys and foreign keys as needed.\n\n1. **Implement the Relationship:**\n\n - For one-to-many relationships, the foreign key is placed in the \"many\" side table."}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1856", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/参考答案/综合题（5 道大题，共 80 分）/概念简答题（6 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 232, "text": "ionship:**\n\n - For one-to-many relationships, the foreign key is placed in the \"many\" side table.\n - For many-to-many relationships, create an associative (junction) table that contains the primary keys of both related entities."}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1857", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/参考答案/综合题（5 道大题，共 80 分）/范式计算题（14 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 662, "text": "\n\na) 因为 D 无法被任何属性推导出来，所以 D 一定是候选码中的一个属性\n\nA -> CB （AD） = (ABCD)\n\nE -> FA （AED） = (ABCDEF)\n\n又因为 E 能推导出 A，所以候选码是（DE）\n\nLet us compute E+ E+={FACBE}\n\nLet us compute ED+ E+={ABCDEF}\n\nThus ED→R ED is a superkey.\n\nIt is easy to see that E →/（不可推导）→ R, D →/→ R\n\nThus, ED is a candidate key.\n\nNote that ED is not implied by any other attributes. Thus, any candidate key of R must contain ED. Further, ED is the unique candidate key of R\n\nb) 存在非主属性 A 对码 BC 的部分函数依赖，所以并不是 3NF\n\nR1（A, B, C）\n\nR2（A, E, F）\n\n以上的拆解并没有包含候选码 DE\n\n最终拆解方案还要再加上 R3（D, E）\n\nNot. In A→CB, A is not a superkey and is not contained in the candidate key."}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1858", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/参考答案/综合题（5 道大题，共 80 分）/范式计算题（14 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 683, "text": "最终拆解方案还要再加上 R3（D, E）\n\nNot. In A→CB, A is not a superkey and is not contained in the candidate key.\n\nCompute the canonical cover, we have Fi=F\n\nAccording to Fi, we get R1=(A,B,C), R2=(A,E,F)\n\nNote none of schemas contains ED, we generate R3=(D,E)\n\nThus, decomposition of R\n\nR1=(A,B,C), R2=(A,E,F), R3=(D,E)\n\nc) 存在非主属性 A 对码 BC 的部分函数依赖，所以并不是 BCNF\n\n我们先将关系模式拆解为\n\nR1（A, B, C） R2（A, D, E, F）\n\n此时，E -> FA 是主属性对码 FA 的部分函数依赖，所以还要继续拆解\n\nR3（A, E, F） R4（D, E）\n\n最终的拆解方案：R1（A, B, C）R3（A, E, F） R4（D, E）\n\nNot. A→CB disobeys the definition of BCNF.\n\nR1=(A,B,C), R2=(A,D,E,F)\n\nIn R2, E→FA disobey the definition of BCNF.\n\nR3=(A,E,F), R4=(D,E)\n\nThus, decomposition of R\n\nR1=(A,B,C), R3=(A,E,F), R4=(D,E)"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1859", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/参考答案/综合题（5 道大题，共 80 分）/SQL 与 关系代数（22 + 6 = 28 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 637, "text": "[28 points]\n\nBOOK ( Bookid , Title , Publishername )\n\nBOOK_AUTHORS ( Bookid , Authorname )\n\nPUBLISHER ( Publishername , Address , Phone )\n\nBOOK_COPIES ( Bookid , Branchid , No_Of_Copies )\n\nLIBRARY_BRANCH ( Branchid , Branchname , Address )\n\nBOOK_LOANS ( Bookid , Branchid , Cardno , **DateOut , Duedate** )\n\nBORROWER ( Cardno , Name , Address , Phone )\n\n1. [3 points]Write appropriate SQL DDL statements for declaring the BOOK_AUTHORS relation.\n\n```SQL\nCREATE TABLE book_authors (\n bookid BIGINT UNSIGNED NOT NULL,\n authorname VARCHAR(200) NOT NULL,\n PRIMARY KEY (bookid),\n FOREIGN KEY (bookid) REFERENCES book(Bookid)\n);\n```"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1860", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/参考答案/综合题（5 道大题，共 80 分）/SQL 与 关系代数（22 + 6 = 28 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 629, "text": "R(200) NOT NULL,\n PRIMARY KEY (bookid),\n FOREIGN KEY (bookid) REFERENCES book(Bookid)\n);\n```\n\n1. [6 points]Give an expression in **relational algebra** to express the following queries.\n\nQ1: Retrieve the names of all borrowers who do not have any books checked out.\n\n\n\nQ2: for each book that is loaned out from the “Sharpstown” branch and whose DueDate is today, retrieve the book title, the borrow’s name, and the borrower’s address.\n\n\n\n1. [16 points] Give an expression in SQL to express the following queries :"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1861", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/参考答案/综合题（5 道大题，共 80 分）/SQL 与 关系代数（22 + 6 = 28 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 677, "text": "JTod9JRxpGDpc2zEZnAe)\n\n1. [16 points] Give an expression in SQL to express the following queries :\n\n - How many copies of the book titled *The Lost Tribe* are owned by the library branch whose name is “sharpstown” ?\n\n ```SQL\n select no_of_copies\n from book_copies, book, library_branch\n where bookcopies.bookid = book.bookid\n and book_copies.branchid = library_branch.branchid\n and book.title = 'The Lost Tribe'\n and library_branch.branchname = 'sharpstown';\n ```\n\n - For each library branch , retrieve the branch name and that the total number of books loaned out from that branch . 对于每个图书馆分馆，检索分馆名称以及从该分馆借出的图书总数。\n\n ```SQL\n SELECT\n LB.Branchname,"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1862", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/参考答案/综合题（5 道大题，共 80 分）/SQL 与 关系代数（22 + 6 = 28 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 666, "text": "ed out from that branch . 对于每个图书馆分馆，检索分馆名称以及从该分馆借出的图书总数。\n\n ```SQL\n SELECT\n LB.Branchname,\n COUNT(BL.Bookid) AS Total_Books_Loaned\n FROM\n LIBRARY_BRANCH LB\n JOIN\n BOOK_LOANS BL ON LB.Branchid = BL.Branchid\n GROUP BY\n LB.Branchname;\n ```\n\n - Retrieve the name , address , and number of books checked out for all borrowers who have more than five books checked out .\n\n ```SQL\n SELECT borrower.name, borrower.address, COUNT(book_loans.bookid) AS number_of_books\n FROM borrower\n JOIN book_loans ON borrower.cardno = book_loans.cardno\n GROUP BY borrower.cardno\n HAVING COUNT(book_loans.bookid) > 5;\n ```\n\n ```SQL"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1863", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/参考答案/综合题（5 道大题，共 80 分）/SQL 与 关系代数（22 + 6 = 28 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 698, "text": "_loans.cardno\n GROUP BY borrower.cardno\n HAVING COUNT(book_loans.bookid) > 5;\n ```\n\n ```SQL\n SELECT borrower.name, borrower.address, COUNT(book_loans.bookid) AS number_of_books\n FROM borrower\n JOIN book_loans ON borrower.cardno = book_loans.cardno\n GROUP BY borrower.name, borrower.address\n HAVING COUNT(book_loans.bookid) > 5;\n ```\n\n - For each book authored ( or co-authored ) by “ Stephen King “ , retrieve the title and the number of copies owned by the library branch whose name is “ central ” .\n\n ```SQL\n -- 方法一\n select title, no_of_copies\n from book b, book_authors ba, book_copies bc, library_branch lb\n where b.bookid = ba.bookid\n and b.bookid = bc.bookid"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1864", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/参考答案/综合题（5 道大题，共 80 分）/SQL 与 关系代数（22 + 6 = 28 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 698, "text": "ors ba, book_copies bc, library_branch lb\n where b.bookid = ba.bookid\n and b.bookid = bc.bookid\n and bc.branchid = lb.branchid\n and ba.authorname = 'Stephen King'\n and lb.branchname = 'central';\n\n -- 方法二\n SELECT b.Title, bc.No_Of_Copies\n FROM BOOK b\n JOIN BOOK_AUTHORS ba ON b.Bookid = ba.Bookid\n JOIN BOOK_COPIES bc ON b.Bookid = bc.Bookid\n JOIN LIBRARY_BRANCH lb ON bc.Branchid = lb.Branchid\n WHERE ba.Authorname = 'Stephen King'\n AND lb.Branchname = 'central';\n ```\n2. [3 points] Record the fact that the manager didn’t maintain information about the book named “ T&G ” ,i.e. remove information about “ T&G ” .\n\n```SQL\n-- 请注意，期末考的表格如果没有说外键，就说明你要全部写\n-- 此时，写删除语句的顺序很重要！"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1865", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/参考答案/综合题（5 道大题，共 80 分）/SQL 与 关系代数（22 + 6 = 28 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 629, "text": ",i.e. remove information about “ T&G ” .\n\n```SQL\n-- 请注意，期末考的表格如果没有说外键，就说明你要全部写\n-- 此时，写删除语句的顺序很重要！\n\n-- Delete from BOOK_AUTHORS for all authors of 'T&G'\nDELETE FROM BOOK_AUTHORS\nWHERE Bookid IN (\n SELECT Bookid FROM BOOK WHERE Title = 'T&G'\n);\n\n-- Delete from BOOK_COPIES for all copies of 'T&G'\nDELETE FROM BOOK_COPIES\nWHERE Bookid IN (\n SELECT Bookid FROM BOOK WHERE Title = 'T&G'\n);\n\n-- Delete from BOOK_LOANS for all loans of 'T&G'\nDELETE FROM BOOK_LOANS\nWHERE Bookid IN (\n SELECT Bookid FROM BOOK WHERE Title = 'T&G'\n);\n\n-- Finally, delete the book 'T&G' from the BOOK table\nDELETE FROM BOOK\nWHERE Title = 'T&G';\n```"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1866", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/参考答案/综合题（5 道大题，共 80 分）/查询处理，优化与事务（16 分）/⚠️ 5.1 描述选择的原理以及损失", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 203, "text": "\n\n最好的情况 h + n\n\n\n\n5（树高） + 1（访问文件） = 6\n\n"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1867", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/参考答案/综合题（5 道大题，共 80 分）/查询处理，优化与事务（16 分）/⚠️ 5.2 概念简答题：描述 Indexed Nested-Loop Join 的全流程", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 232, "text": "[4 points] Describe the process of Indexed nested-loop join .\n\n\n\n\n\n"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1868", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/参考答案/综合题（5 道大题，共 80 分）/查询处理，优化与事务（16 分）/⚠️ 5.3 概念简答题：两阶段锁是什么？", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 371, "text": "[4 points] Please describe the two-phase looking protocol and prove that it ensures conflict-serializable schedules and does not ensure freedom from deadlocks . / 请描述两阶段锁，并证明两阶段锁保证了冲突可串行化但是不保证死锁的自由度。\n\n\n\n\n\n"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1869", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/参考答案/综合题（5 道大题，共 80 分）/查询处理，优化与事务（16 分）/5.4 阅读日志，分析 redo 和 undo", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 357, "text": "\n\n没有出现 commit 和 abort，undo，回到此前状态\n\n如果出现 commit 和 abort，redo，什么都不用写\n\n（a）选项，T0 和 T1 都是正常处理的，redo\n\nA := 950, B := 2050, C := 600\n\n（b）选项，T0 是正常处理的，用 redo；T1 并不是正常处理，用 undo\n\nA := 950, B := 2050，C := 700\n\n（c）选项，T0 并不是正常处理的，用 undo\n\nA := 1000, B := 2000\n\n"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1870", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/B 卷 ✅ Easy/参考答案/填空题（20 空，一空 1 分，共 20 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 678, "text": "1. **physical, logical, view（2013 真题复现）**\n\n\n\n1. **1**\n\n\n\n\n\n1. **α -> βγ**\n\n\n\n\n\n1. **2 1**\n\n\n\n1. **relational execution**\n\n\n\n\n\n\n\n"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1871", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/B 卷 ✅ Easy/参考答案/填空题（20 空，一空 1 分，共 20 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 673, "text": "ishu.cn/file/LiwrbI0KCoMYcKxf4YVcIWWnnMe)\n\n\n\n\n\n1. **dense**\n\n\n\n\n\n1. **closed**\n\n\n\n\n\n1. **8**\n\n5 + [10 / 4]（向上取整） = 8\n\n\n\n1. **isolation, durability（2013 真题复现）**\n\n\n\n1. **active**\n\n"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1872", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/B 卷 ✅ Easy/参考答案/填空题（20 空，一空 1 分，共 20 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 440, "text": "8lbryQTocqPUx8Pm0cBLxAnAf)\n\n1. **active**\n\n\n\n\n\n\n\n1. **stable**\n\n\n\n1. **growing, shrinking**\n\n\n\n1. **before**\n\n"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1873", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/B 卷 ✅ Easy/参考答案/综合题（4 道大题，共 80 分）/ER 图分析（20 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1874", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/B 卷 ✅ Easy/参考答案/综合题（4 道大题，共 80 分）/ER 图分析（20 分）/列出实体集以及他们的主键（3 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1875", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/B 卷 ✅ Easy/参考答案/综合题（4 道大题，共 80 分）/ER 图分析（20 分）/Give appropriate relation schemas for the entity sets.（3 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1876", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/B 卷 ✅ Easy/参考答案/综合题（4 道大题，共 80 分）/ER 图分析（20 分）/列出关系集合以及他们的主键（4 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1877", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/B 卷 ✅ Easy/参考答案/综合题（4 道大题，共 80 分）/ER 图分析（20 分）/Give appropriate relation schemas for the relationship sets.（4 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1878", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/B 卷 ✅ Easy/参考答案/综合题（4 道大题，共 80 分）/ER 图分析（20 分）/在前一题的基础上优化 relation schemas（4 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1879", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/B 卷 ✅ Easy/参考答案/综合题（4 道大题，共 80 分）/ER 图分析（20 分）/为 instructor, teaches, department, course 写 SQL 的 DDL （4 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 382, "text": "要求：with appropriate data-type defined in standard SQL. ldentify referential-integrity constrains that should hold, and include them in the DDL definition.\n\n\n\n\n\n\n\n"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1880", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/B 卷 ✅ Easy/参考答案/综合题（4 道大题，共 80 分）/ER 图分析（20 分）/备注：课本的设计", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 283, "text": "\n\n\n\n\n\n\n\n"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1881", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/B 卷 ✅ Easy/参考答案/综合题（4 道大题，共 80 分）/范式分析（20 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1882", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/B 卷 ✅ Easy/参考答案/综合题（4 道大题，共 80 分）/范式分析（20 分）/为什么我们需要 3NF？（课本原题）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 169, "text": "\n\n\n\n"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1883", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/B 卷 ✅ Easy/参考答案/综合题（4 道大题，共 80 分）/范式分析（20 分）/请你将这个模式拆分为 3NF。", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 144, "text": "A -> BC\n\nB -> C\n\nA -> B\n\nAB -> C\n\n主属性：A\n\n我们应当消除非主属性对码的部分函数依赖和传递函数依赖\n\nR1(A, B)\n\nR2(B, C)\n\n"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1884", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/B 卷 ✅ Easy/参考答案/综合题（4 道大题，共 80 分）/SQL 与 关系代数 （ 16 分 + 8 分 = 24 分 ）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1885", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/B 卷 ✅ Easy/参考答案/综合题（4 道大题，共 80 分）/SQL 与 关系代数 （ 16 分 + 8 分 = 24 分 ）/关系代数 Find the names of all employees who live in Beijing", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1886", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/B 卷 ✅ Easy/参考答案/综合题（4 道大题，共 80 分）/SQL 与 关系代数 （ 16 分 + 8 分 = 24 分 ）/关系代数 Find the names and cities of residence of all employees who work for XYZ Bank and have more than \\$8,000 salary.", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1887", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/B 卷 ✅ Easy/参考答案/综合题（4 道大题，共 80 分）/SQL 与 关系代数 （ 16 分 + 8 分 = 24 分 ）/⚠️ Find the name of company that has the most employees", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 524, "text": "```SQL\nSELECT c.company_name\nFROM company c\nJOIN works w ON c.company_name = w.company_name\nGROUP BY c.company_name\nHAVING COUNT(w.employee_name) = (\n SELECT MAX(employee_count)\n FROM (\n SELECT COUNT(w2.employee_name) AS employee_count\n FROM works w2\n GROUP BY w2.company_name\n ) AS subquery\n)\n```\n\n```SQL\nselect company_name\nfrom works\ngroup by company_name\nhaving count (distinct employee_name) >= all (\n select count (distinct employee_name)\n from works\n group by company_name\n)\n```"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1888", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/B 卷 ✅ Easy/参考答案/综合题（4 道大题，共 80 分）/SQL 与 关系代数 （ 16 分 + 8 分 = 24 分 ）/Find the names of all employees in this database who live in the same city as the company for which they work", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 165, "text": "```SQL\nselect e.employee_name\nfrom employee e, works w, company c\nwhere e.employee_name = w.employee_name\nand w.company_name = c.company_name\nand e.city = c.city\n```"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1889", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/B 卷 ✅ Easy/参考答案/综合题（4 道大题，共 80 分）/SQL 与 关系代数 （ 16 分 + 8 分 = 24 分 ）/Find the names, street addresses, and cities of residence of all employees whose manager lives in Shanghai.", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 241, "text": "```SQL\nselect *\nfrom employee e, manages m\nwhere e.employee_name = m.employee_name\nand m.manager_name in (\n select employee_name\n from employee\n where city = 'Shanghai'\n);\n```\n\n"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1890", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/B 卷 ✅ Easy/参考答案/综合题（4 道大题，共 80 分）/SQL 与 关系代数 （ 16 分 + 8 分 = 24 分 ）/为所有的经理涨薪 12%", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 119, "text": "```SQL\nupdate works\nset salary = salary * 1.12\nwhere employee_name in (\n select manager_name\n from manages\n);\n```"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1891", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/B 卷 ✅ Easy/参考答案/综合题（4 道大题，共 80 分）/查询处理，优化与事务（16 分）/⚠️ 4.1 B+ 树的查询处理（ 4 分 ）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 238, "text": "\n\n\n\n这题是 **辅助索引** **非码** **等值 （hi + n）\\* (tT + tS)**\n\n hi = 4，n = 3，代入求解\n\n"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1892", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/B 卷 ✅ Easy/参考答案/综合题（4 道大题，共 80 分）/查询处理，优化与事务（16 分）/⚠️ 4.2 概念简答题：描述 Merge-join 的全流程", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1893", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/B 卷 ✅ Easy/参考答案/综合题（4 道大题，共 80 分）/查询处理，优化与事务（16 分）/⚠️ 4.3 概念简答题：两阶段锁是什么？", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 371, "text": "[4 points] Please describe the two-phase looking protocol and prove that it ensures conflict-serializable schedules and does not ensure freedom from deadlocks . / 请描述两阶段锁，并证明两阶段锁保证了冲突可串行化但是不保证死锁的自由度。\n\n\n\n\n\n"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1894", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2015 质量最好，考前必刷 A + B/B 卷 ✅ Easy/参考答案/综合题（4 道大题，共 80 分）/查询处理，优化与事务（16 分）/⚠️ 4.4 阅读日志，分析 redo 和 undo", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 357, "text": "\n\n没有出现 commit 和 abort，undo，回到此前状态\n\n如果出现 commit 和 abort，redo，什么都不用写\n\n（a）选项，T0 和 T1 都是正常处理的，redo\n\nA := 950, B := 2050, C := 600\n\n（b）选项，T0 是正常处理的，用 redo；T1 并不是正常处理，用 undo\n\nA := 950, B := 2050，C := 700\n\n（c）选项，T0 并不是正常处理的，用 undo\n\nA := 1000, B := 2000\n\n"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1895", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2017 ✅ Medium/参考答案/填空题（11 空，1 空 1 分，共 11 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 673, "text": "1. **candidate key**\n\n\n\n1. ALTER TABLE ... **DROP** COLUMN ... , **DELETE** FROM ...\n\n第一个空是修改表格的列\n\n\n\n第二个空是修改表格的行\n\n\n\n1. **unknown**\n\n\n\n| P | Q | P && Q | P \\|\\| Q |\n|-|-|-|-|\n| 1 | 1 | 1 | 1 |\n| 1 | 0 | 0 | 1 |\n| 1 | ? | ? | 1 |\n| 0 | 1 | 0 | 1 |\n| 0 | 0 | 0 | 0 |\n| 0 | ? | 0 | ? |\n| ? | 1 | ? | 1 |\n| ? | 0 | 0 | ? |\n| ? | ? | ? | ? |\n\n1. **partial participation（2013 真题复现）**\n\n\n\n1. **multivalued**"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1896", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2017 ✅ Medium/参考答案/填空题（11 空，1 空 1 分，共 11 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 666, "text": "cipation（2013 真题复现）**\n\n\n\n1. **multivalued**\n\n\n\n\n\n1. **dependency-preserving（2015 年 范式计算题 真题复现）**\n\n\n\n提问，既然 BCNF 已经对数据库提出了高范式的要求，但为什么还需要 3NF？\n\nBCNF decomposition can only guarantee it is lossless, while 3NF decomposition can guarantee that it is both lossless and **dependency-preserving**\n\n1. [(n-1)/2]\n\n\n\n1. index scan\n\n\n\n1. **aborted**"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1897", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2017 ✅ Medium/参考答案/填空题（11 空，1 空 1 分，共 11 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 236, "text": "BcAC5tnNg)\n\n1. index scan\n\n\n\n1. **aborted**\n\n\n\n1. **deadlocks**（真题复现）\n\n"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1898", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2017 ✅ Medium/参考答案/术语解释与简答（4 题，每题 6 分，共 24 分）/SQL 术语/(a) 请解释什么是 view materialization", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 689, "text": "A materialization view is nothing but, it is a query that fetches the data from one or more tables in the database. The query can involve operations such as joins, filtering, and aggregations. It is a database object that stores the results of the query table. Materialized views in the [Database Management System (DBMS)](https://www.geeksforgeeks.org/introduction-of-dbms-database-management-system-set-1/) work as the existing snapshots of the data, reducing the computational overhead. Unlike standard views, which are data that is virtually dynamically generated when the materialization view contains original data that exists in the database until the data is modified or truncated."}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1899", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2017 ✅ Medium/参考答案/术语解释与简答（4 题，每题 6 分，共 24 分）/SQL 术语/(b) 请你用 SQL 定义一个名为 num_employee(company_name, num) 的视图", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 377, "text": "```SQL\nemployee(employee_name, street, city)\nworks(employee_name, company_name, salary)\ncompany(company_name, city)\n```\n\n```SQL\nCREATE VIEW num_employee AS (\n SELECT c.company_name, COUNT(e.employee_name) AS num\n FROM employee e\n JOIN works w ON e.employee_name = w.employee_name\n JOIN company c ON w.company_name = c.company_name\n GROUP BY c.company_name\n);\n```"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1900", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2017 ✅ Medium/参考答案/术语解释与简答（4 题，每题 6 分，共 24 分）/索引术语/(a) 解释什么是 sequential index", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 294, "text": "顺序索引，也称为单列索引，是一种数据库索引类型，它基于数据表中单个列的值来创建。顺序索引通常按照数据值的顺序存储索引项，类似于书籍的目录，其中每个条目都指向数据表中具有特定值的行。顺序索引适用于等值查询和范围查询，因为它们可以高效地扫描和排序数据。\n\n**顺序索引的特点：**\n\n1. **顺序存储**：索引项按顺序排列，类似于数据表中的物理存储顺序。\n2. **适用于等值和范围查询**：顺序索引适合执行等值查询（查找特定值）和范围查询（查找一定范围内的值）。\n3. **全表扫描替代**：在没有索引的情况下，数据库可能需要执行全表扫描来找到所需的数据，顺序索引可以减少这种情况的发生。"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1901", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2017 ✅ Medium/参考答案/术语解释与简答（4 题，每题 6 分，共 24 分）/索引术语/(b) 对比 sequential index 和 hash index，解释 sequential index 的优缺点", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 700, "text": "**顺序索引的优点：**\n\n1. **范围查询效率**：顺序索引非常适合执行范围查询，因为它可以快速定位到一个范围内的所有数据。\n2. **顺序访问**：顺序索引允许数据库系统以顺序方式访问数据，这对于某些操作（如排序）非常有用。\n3. **稳定性**：顺序索引不会因为数据的插入和删除而频繁变动，这使得索引结构相对稳定。\n\n**顺序索引的缺点：**\n\n1. **空间消耗**：顺序索引可能会占用较多的磁盘空间，尤其是当索引的列包含大量数据时。\n2. **写操作开销**：对于频繁更新的表，顺序索引可能需要更多的维护工作，因为插入和删除操作可能需要移动大量的索引项。\n3. **不适合随机访问**：虽然顺序索引适合顺序访问，但对于随机访问（如等值查询）可能不如哈希索引高效。\n\n**哈希索引的优点：**\n\n1. **快速随机访问**：哈希索引非常适合快速随机访问，因为它们可以通过哈希函数直接定位到数据的位置。\n2. **空间效率**：哈希索引通常比顺序索引更节省空间，因为它们不需要存储完整的键值。\n3. **写操作优化**：哈希索引对于插入和删除操作通常更高效，因为它们不需要重新排序或移动大量的索引项。\n\n**哈希索引的缺点：**\n\n1. **不适合范围查询**：哈希索引不适合执行范围查询，因为它们不保留键值的顺序。\n2. **哈希冲突**：在高负载因子下，哈希冲突可能会增加，这会影响查询性能。\n3. **数据分布依赖**：哈希索引的性能高度依赖于哈希函数的选择和数据的分布。\n\n"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1902", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2017 ✅ Medium/参考答案/术语解释与简答（4 题，每题 6 分，共 24 分）/查询优化：Join/(a) Nested block loop join algorithm is one effective algorithm to implement JOIN operation in database processing. Please explain the main steps. （真题复现）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1903", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2017 ✅ Medium/参考答案/术语解释与简答（4 题，每题 6 分，共 24 分）/查询优化：Join/(b) 使用(a)的算法预估连接成本。instructor 表有 1000 个块，teaches 有 500 个块，主存有 5 个数据块。cost = number of block transfer + disk seeks", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 351, "text": "\n\n\n\n在这一题中 br = 500, bs = 1000\n\nIO cost 500 / 4 \\* 1000 + 500\n\n\n\nSeek 500 / (5 - 2) 向上取整为 167\n\n\n\n如果是 PPT 的方案 500 / (5 - 1) 向上取整为 125"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1904", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2017 ✅ Medium/参考答案/术语解释与简答（4 题，每题 6 分，共 24 分）/可序列化 schedule （2014 真题复现）/(b) 请检测以下两个事务是否是可序列化的并确认你的答案", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 657, "text": "| T1 | T2 |\n|-|-|\n| R(A) | |\n| R(B) | |\n| IF A = 0 THEN B = 1 | |\n| | R(B) |\n| | R(A) |\n| W(B) | |\n| | IF B = 0 THEN A = A + 1 |\n| | W(A) |\n\n回顾**可串行化**的定义：\n\n\n\n\n\n但是我们真正做题的时候，如果我们还采用这种所谓的“非冲突指令”进行求解，那太繁琐了，我们有必要引入我们在数据库学过的一个概念：**有向无环图**。\n\n\n\n\n\n针对这一道题，我们可以画一个图，去判定两个调度是否成环。\n\n在画这一道题的图之前，让我们来看看老师举的画图案例\n\n\n\n再来看看这一道题，出现环路，不满足\n\n"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1905", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2017 ✅ Medium/参考答案/计算与长问答题（65 分）/SQL 与 关系代数（12 + 8 = 20 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 122, "text": "请阅读《数据库系统概念 第五版》 图片 3.1，回答以下问题，画横线的表示主键\n\n**前三题写 SQL 语句，后两题写关系代数**\n\n"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1906", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2017 ✅ Medium/参考答案/计算与长问答题（65 分）/SQL 与 关系代数（12 + 8 = 20 分）/Find the customers who have accounts at the branch \"ICBC-001\"", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 185, "text": "```SQL\nselect c.customer_name\nfrom customer c, depositor d, account a\nwhere c.customer_name = d.customer_name\nand d.account_number = a.account_number\nand a.branch_name = 'ICBC-001';\n```"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1907", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2017 ✅ Medium/参考答案/计算与长问答题（65 分）/SQL 与 关系代数（12 + 8 = 20 分）/Find customers who have accounts in the same city where they live.", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 220, "text": "```SQL\nselect *\nfrom customer c, depositor d, account a, branch b\nwhere c.customer_name = d.customer_name\nand d.account_number = a.account_number\nand a.branch_name = b.branch_name\nand c.customer_city = b.branch_city;\n```"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1908", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2017 ✅ Medium/参考答案/计算与长问答题（65 分）/SQL 与 关系代数（12 + 8 = 20 分）/Find all the customers who have accounts at both the branches located in \"Guangzhou\" and \"Shenzhen\"", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 471, "text": "```SQL\nselect c.*\nfrom customer c\nwhere c.customer_name in (\n select d.customer_name\n from depositor d, account a, branch b\n where d.account_number = a.account_number\n and a.branch_name = b.branch_name\n and b.branch_city = 'Guangzhou'\n)\nand c.customer_name in (\n select d.customer_name\n from depositor d, account a, branch b\n where d.account_number = a.account_number\n and a.branch_name = b.branch_name\n and b.branch_city = 'Shenzhen'\n);\n```"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1909", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2017 ✅ Medium/参考答案/计算与长问答题（65 分）/SQL 与 关系代数（12 + 8 = 20 分）/Find out the branches which provide loans to the customer \"Zhanshan\".", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1910", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2017 ✅ Medium/参考答案/计算与长问答题（65 分）/SQL 与 关系代数（12 + 8 = 20 分）/Suppose each customer can borrow multiple loans from a branch. Find the names of customers who borrow more than 30,000 loans in total at the branch \"ICBC-001\"", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1911", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2017 ✅ Medium/参考答案/计算与长问答题（65 分）/范式分析（3 题 × 5 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 523, "text": "\n\n\n\n(a) A -> BC A+ = ABC\n\n A -> D A+ = ABCD\n\nBCD -> E A+ = ABCDE\n\n(b) 根据定义，候选码应该是最小的可以表示所有属性的码\n\n\n\n根据（a），A 一定是 候选码\n\n又因为 E -> A，所以 E 也是 候选码\n\nB -> D, BC -> E，所以 BC 也是 候选码\n\n最终结果：A, E, BC\n\n(c) 3NF 消除了非主属性对码的传递函数依赖\n\nBCNF 在 3NF 的基础上，还消除了主属性对码的传递函数依赖\n\n因为 B -> D，所以 BC -> E\n\n又因为 E -> A 且 A -> BC\n\n所以存在非主属性 BC 对码 E 的传递函数依赖 BC -> E -> A -> BC\n\n所以这个范式是 3NF，不是 BCNF"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1912", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2017 ✅ Medium/参考答案/计算与长问答题（65 分）/范式分析（4 题，共 15 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 671, "text": "\n\n（a) 要证明无损分解，则需要证明两个关系经过自然连接之后能不能变成原来的函数\n\n要证明函数依赖，则需要证明这种分解是否能保持 F 的两个函数关系式\n\n这两个证明是相互独立的\n\n我们可以看出，R1 和 R2 经过自然连接之后无法恢复到 R，理由是\n\n\n\nR1 相交 R2 = B，R1 - R2 等于 A, C, D, E\n\n非常遗憾的是，B 无法独立推导任何一个 attribute\n\n\n\n\n\n所以这是无损连接\n\n（2） BCNF 需要消除主属性对码的传递函数依赖关系\n\n主属性：A B C E\n\nR1(A, B, E)，主键为 A, E\n\nR2(B, C, D)，主键为 B, C\n\n（3）在（2）问的 BCNF 拆解中，R1 保持了 A → B，R2 保持了 BC → D，且消除了 B 的传递函数依赖，符合条件\n\n（4）3NF 需要消除非主属性对码的传递函数依赖关系，只要符合 BCNF，就符合第三范式\n\nR1(A, B, E)，主键为 A, E\n\nR2(B, C, D)，主键为 B, C"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1913", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2017 ✅ Medium/参考答案/计算与长问答题（65 分）/范式分析（4 题，共 15 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 155, "text": "数依赖，符合条件\n\n（4）3NF 需要消除非主属性对码的传递函数依赖关系，只要符合 BCNF，就符合第三范式\n\nR1(A, B, E)，主键为 A, E\n\nR2(B, C, D)，主键为 B, C\n\n"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1914", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2017 ✅ Medium/参考答案/计算与长问答题（65 分）/ER 图分析（5 题 × 3 分 = 15 分）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1915", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2017 ✅ Medium/参考答案/计算与长问答题（65 分）/ER 图分析（5 题 × 3 分 = 15 分）/(a) Give the schemas of the entity sets, and underline the primary key.", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 170, "text": "author(name, address, URL)\n\nbook(ISBN, title, year, price)\n\nshopping_basket(basket_id, number)\n\ncustomer(c_id, name, address, phone)\n\npublisher(p_id, address, phone, URL)"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1916", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2017 ✅ Medium/参考答案/计算与长问答题（65 分）/ER 图分析（5 题 × 3 分 = 15 分）/(b) Give the schemas of the relationship sets, and underline the primary key.", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 111, "text": "written_by(name, ISBN)\n\npublished_by(ISBN, p_id)\n\ncontains(ISBN, number, basket_id)\n\nbasket_of(basket_id, c_id)"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1917", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2017 ✅ Medium/参考答案/计算与长问答题（65 分）/ER 图分析（5 题 × 3 分 = 15 分）/(c) Remove the redundancy of the above schemas, i.e., to incorporate some schemas if necessary.", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 242, "text": "author(name, address, URL)\n\nwritten_by(name, ISBN)\n\nbook(ISBN, title, year, price, publisher_id)\n\npublisher(p_id, address, phone, URL)\n\nshopping_basket(basket_id, number, ISBN)\n\nbasket_of(basket_id, c_id)\n\ncustomer(c_id, name, address, phone)"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1918", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2020（回忆版）✅", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1919", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2021（回忆版）✅", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1920", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2022（小题）✅ Easy", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 74, "text": "5 题选择题，每题 2 分，共 10 分\n\n7 题判断题，每题 2 分，共 14 分\n\n1 题数据库设计题，共 27 分\n\n4 题大题，共 49 分"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1921", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2022（小题）✅ Easy/Part I 选择题（2 分 × 5 题）/SQL 的分类", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 107, "text": "We specify a database schema by a set of definitions by a special language called ?\n\nA. DDL\n\nB. UML\n\nC. DML"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1922", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2022（小题）✅ Easy/Part I 选择题（2 分 × 5 题）/Armstrong 公理", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 59, "text": "如果 A->BC 且 C -> D，那个推论是错的？\n\nA. A -> C\n\nB. A -> D\n\nC. B -> D"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1923", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2022（小题）✅ Easy/Part I 选择题（2 分 × 5 题）/关系代数推论", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 68, "text": "请问哪一句推论是错的？\n\n"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1924", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2022（小题）✅ Easy/Part I 选择题（2 分 × 5 题）/事务的 ACID（本题两个空对应两个不同选项）", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1925", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2022（小题）✅ Easy/Part II 判断题 （2 分 × 7 题）/查询过程", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 40, "text": "在查询过程中，heuristic optimizers 的动机是降低优化成本吗？"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1926", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2022（小题）✅ Easy/Part II 判断题 （2 分 × 7 题）/ER 设计", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 35, "text": "有时候我们不必为 many-to-many 的关系构建一张表格，对吗？"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1927", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "2022（小题）✅ Easy/参考答案，欢迎直接在评论区勘误", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 30, "text": "选择题：A,C,B,DC\n\n判断题：1和 3 和 7 是对的"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1928", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "简答题/**两阶段封锁协议为什么能保证冲突可串行化？**", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 659, "text": "**Answer:** Suppose two-phase locking does not ensure serializability. Then\n\nthere exists a set of transactions *T*0, *T*1 ... *Tn*−1 which obey 2PL and which\n\nproduce a nonserializable schedule.A non-serializable schedule implies a\n\ncycle in the precedence graph, andwe shall showthat 2PL cannot produce\n\nsuch cycles. Without loss of generality, assume the following cycle exists\n\nin the precedence graph: *T*0 → *T*1 → *T*2 → ... → *Tn*−1 → *T*0. Let a*i* be\n\nthe time at which *Ti* obtains its last lock (i.e. *Ti* ’s lock point). Then for all\n\ntransactions such that *Ti* → *Tj* , a*i* < a*j* . Then for the cycle we have\n\na0 < a1 < a2 < ... < a*n*−1 < a0"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1929", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "简答题/**两阶段封锁协议为什么能保证冲突可串行化？**", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 476, "text": "such that *Ti* → *Tj* , a*i* < a*j* . Then for the cycle we have\n\na0 < a1 < a2 < ... < a*n*−1 < a0\n\nSince a0 < a0 is a contradiction, no such cycle can exist. Hence 2PL\n\ncannot produce non-serializable schedules. Because of the property that\n\nfor all transactions such that *Ti* → *Tj* , a*i* < a*j* , the lock point ordering\n\nof the transactions is also a topological sort ordering of the precedence\n\ngraph. Thus transactions can be serialized according to their lock points."}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1930", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "简答题/比较顺序索引和Hash索引，以及他们的优点缺点", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 311, "text": "Cost of periodic re-organization//定期重新组织的开销\n\nRelative frequency of insertions and deletions//相对频繁的更新\n\nExpected type of queries:\n\nHashing is generally better at retrieving records having a specified value of the key.\n\n//Hashing：检索特定值\n\nIf range queries are common, ordered indices are to be preferred\n\n//顺序索引：范围查询"}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1931", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "简答题/描述块嵌套连接", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 75, "text": "every block of inner relation is paired with every block of outer relation."}
{"id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc::1932", "page_id": "docx::NP0XwmkHbileBPkQPMOcGxdonVc", "title": "真题解析✅", "course": "3.5➡️3.0 数据库系统 / DataBase System", "path": "3.5➡️3.0 数据库系统 / DataBase System/真题解析✅", "section": "简答题/证明是否为无损分解", "url": "https://a1npn29y3xu.feishu.cn/wiki/NP0XwmkHbileBPkQPMOcGxdonVc", "source_type": "docx", "n_chars": 63, "text": "若 A∩B 是 A或B的超码，则R分解成AB是无损分解\n\n- 证明是否为保持依赖[dependency preserving]"}
{"id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd::1933", "page_id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd", "title": "课后习题（DS 版）", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课后习题（DS 版）", "section": "一、黑盒：集装箱", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7CEwNJJMiEkoJkdyDLctP3fnyd", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd::1934", "page_id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd", "title": "课后习题（DS 版）", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课后习题（DS 版）", "section": "一、黑盒：集装箱/DS 参考/基于等价类划分（Equivalence Partitioning）的测试用例设计/**假设条件**：", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7CEwNJJMiEkoJkdyDLctP3fnyd", "source_type": "docx", "n_chars": 164, "text": "1. `containerSize` 参数仅接受合法枚举值（Small/Medium/Large），不会传入 `null` 或其他非法值。\n2. `weight` 和 `volume` 必须为正整数（≥1），否则视为无效输入。\n3. **有效等价类**需同时满足重量和体积的约束，任一条件不满足即返回 `false`。\n\n---"}
{"id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd::1935", "page_id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd", "title": "课后习题（DS 版）", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课后习题（DS 版）", "section": "一、黑盒：集装箱/DS 参考/基于等价类划分（Equivalence Partitioning）的测试用例设计/**等价类划分**：", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7CEwNJJMiEkoJkdyDLctP3fnyd", "source_type": "docx", "n_chars": 264, "text": "| 参数 | 有效等价类 | 无效等价类 |\n|-|-|-|\n| **Small容器** | 1 ≤ weight ≤1000, 1 ≤ volume ≤1 | weight 1000; volume 1 |\n| **Medium容器** | 1 ≤ weight ≤5000, 1 ≤ volume ≤10 | weight 5000; volume 10 |\n| **Large容器** | 1 ≤ weight ≤10000, 1 ≤ volume ≤20 | weight 10000; volume 20 |\n\n---"}
{"id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd::1936", "page_id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd", "title": "课后习题（DS 版）", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课后习题（DS 版）", "section": "一、黑盒：集装箱/DS 参考/基于等价类划分（Equivalence Partitioning）的测试用例设计/**测试用例设计**：", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7CEwNJJMiEkoJkdyDLctP3fnyd", "source_type": "docx", "n_chars": 565, "text": "**正常测试（Valid Cases）**：\n\n1. **Small容器**：`size=Small, weight=1000, volume=1` → `true`*（有效等价类上限）*\n2. **Medium容器**：`size=Medium, weight=5000, volume=10` → `true`*（有效等价类上限）*\n3. **Large容器**：`size=Large, weight=10000, volume=20` → `true`*（有效等价类上限）*\n\n**错误测试（Invalid Cases）**：\n\n1. **重量超限**：`size=Small, weight=1001, volume=1` → `false`*（重量超出Small上限）*\n2. **体积超限**：`size=Large, weight=5000, volume=21` → `false`*（体积超出Large上限）*\n3. **负值输入**：`size=Medium, weight=-500, volume=5` → `false`*（无效等价类：负重量）*\n4. **双参数超限**：`size=Medium, weight=5001, volume=11` → `false`*（重量和体积均超限）*\n\n---"}
{"id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd::1937", "page_id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd", "title": "课后习题（DS 版）", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课后习题（DS 版）", "section": "一、黑盒：集装箱/DS 参考/基于边界值分析（Boundary Value Analysis）的测试用例设计/**边界值定义**：", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7CEwNJJMiEkoJkdyDLctP3fnyd", "source_type": "docx", "n_chars": 175, "text": "| 容器类型 | 重量边界值（kg） | 体积边界值（m³） |\n|-|-|-|\n| Small | 0, 1, 1000, 1001 | 0, 1, 2 |\n| Medium | 0, 1, 5000, 5001 | 0, 1, 10, 11 |\n| Large | 0, 1, 10000, 10001 | 0, 1, 20, 21 |\n\n---"}
{"id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd::1938", "page_id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd", "title": "课后习题（DS 版）", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课后习题（DS 版）", "section": "一、黑盒：集装箱/DS 参考/基于边界值分析（Boundary Value Analysis）的测试用例设计/**测试用例设计**：", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7CEwNJJMiEkoJkdyDLctP3fnyd", "source_type": "docx", "n_chars": 590, "text": "**正常边界测试**：\n\n1. **Small下限**：`size=Small, weight=1, volume=1` → `true`*（重量和体积的最小有效值）*\n2. **Large上限**：`size=Large, weight=10000, volume=20` → `true`*（重量和体积的最大有效值）*\n\n**边界附近错误测试**：\n\n1. **Small重量边界超限**：`size=Small, weight=1001, volume=1` → `false`*（重量超过Small上限）*\n2. **Medium体积边界超限**：`size=Medium, weight=5000, volume=11` → `false`*（体积超过Medium上限）*\n3. **Large负值输入**：`size=Large, weight=0, volume=20` → `false`*（重量为0，无效输入）*\n\n**混合边界条件**：\n\n1. **重量在边界而体积超限**：`size=Medium, weight=5000, volume=11` → `false`*（重量有效，体积无效）*\n2. **体积在边界而重量超限**：`size=Small, weight=1001, volume=1` → `false`*（体积有效，重量无效）*\n\n---"}
{"id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd::1939", "page_id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd", "title": "课后习题（DS 版）", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课后习题（DS 版）", "section": "一、黑盒：集装箱/DS 参考/**总结**", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7CEwNJJMiEkoJkdyDLctP3fnyd", "source_type": "docx", "n_chars": 457, "text": "通过等价类划分和边界值分析，可以覆盖以下场景：\n\n1. **正常路径**：所有参数在有效范围内。\n2. **错误路径**：参数超限、负值输入、组合超限。\n3. **边界条件**：最小值、最大值及其邻近值的验证。\n\n实际编码时，需结合单元测试框架（如JUnit）编写断言，并确保测试独立性和可重复性。例如，使用参数化测试减少重复代码：\n\n```Java\n@ParameterizedTest\n@CsvSource({\n \"Small, 1000, 1, true\",\n \"Small, 1001, 1, false\",\n \"Large, 10000, 21, false\"\n})\nvoid testCheckContainer(containerSize size, int weight, int volume, boolean expected) {\n assertEquals(expected, checkContainer(size, weight, volume));\n}\n```"}
{"id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd::1940", "page_id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd", "title": "课后习题（DS 版）", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课后习题（DS 版）", "section": "二、白盒：集装箱", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7CEwNJJMiEkoJkdyDLctP3fnyd", "source_type": "docx", "n_chars": 298, "text": "\n\n语句覆盖、边覆盖、end-to-end 的路径覆盖，竟然都可以用同一套测试用例解决诶？\n\n这一题如果出什么条件覆盖，条件组合覆盖，那就很有生活了\n\n| size | weight | volume | ok |\n|-|-|-|-|\n| \\* | -1 | -1 | F |\n| Small | 1001 | 2 | F |\n| Medium | 5001 | 11 | F |\n| Large | 10001 | 21 | F |\n| Small | 999 | 0.5 | T |"}
{"id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd::1941", "page_id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd", "title": "课后习题（DS 版）", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课后习题（DS 版）", "section": "⚠️ 三、完成真值表", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7CEwNJJMiEkoJkdyDLctP3fnyd", "source_type": "docx", "n_chars": 309, "text": "\n\nCAUSES 理论上应该有 64 种 TF 的组合，但是穷举之后发现：\n\n自相矛盾的组合可以删除\n\n效果相同的组合可以合并\n\n所以最终就浓缩成八种了\n\n不知道除了穷举算法以外，大家还有没有好的办法呢？\n\n毕竟考试真的 64 种穷举的话，算到猴年马月才能算完\n\nRULESCAUSES12345678重量 <= 1T1*1重量 > 10T000体积 == 1 立方米1*0体积 > 20 立方米00*Small101Large010EFFECTS成功通过110物品太大001物品太重000"}
{"id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd::1942", "page_id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd", "title": "课后习题（DS 版）", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课后习题（DS 版）", "section": "⚠️ 三、完成真值表/DS Solution/Combinational Test Cases for Rules 4-8/Rule 4: Small Container, Valid Volume, Weight Exceeds Limit", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7CEwNJJMiEkoJkdyDLctP3fnyd", "source_type": "docx", "n_chars": 276, "text": "- **Test Data**: `size = Small`, `weight = 1001 kg`, `volume = 1 m³`\n- **Expected Outputs**: `check()` → `false` (fails), `tooLarge()` → `false`, `tooHeavy()` → `true`\n- **Explanation**: Weight exceeds Small's limit (1000 kg), but volume is valid. Too heavy, not too large."}
{"id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd::1943", "page_id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd", "title": "课后习题（DS 版）", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课后习题（DS 版）", "section": "⚠️ 三、完成真值表/DS Solution/Combinational Test Cases for Rules 4-8/Rule 5: Small Container, Valid Weight, Volume Exceeds Limit", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7CEwNJJMiEkoJkdyDLctP3fnyd", "source_type": "docx", "n_chars": 264, "text": "- **Test Data**: `size = Small`, `weight = 500 kg`, `volume = 2 m³`\n- **Expected Outputs**: `check()` → `false`, `tooLarge()` → `true`, `tooHeavy()` → `false`\n- **Explanation**: Volume exceeds Small's limit (1 m³), but weight is valid. Too large, not too heavy."}
{"id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd::1944", "page_id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd", "title": "课后习题（DS 版）", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课后习题（DS 版）", "section": "⚠️ 三、完成真值表/DS Solution/Combinational Test Cases for Rules 4-8/Rule 6: Large Container, Valid Weight, Volume Exceeds Limit", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7CEwNJJMiEkoJkdyDLctP3fnyd", "source_type": "docx", "n_chars": 267, "text": "- **Test Data**: `size = Large`, `weight = 5000 kg`, `volume = 21 m³`\n- **Expected Outputs**: `check()` → `false`, `tooLarge()` → `true`, `tooHeavy()` → `false`\n- **Explanation**: Volume exceeds Large's limit (20 m³), but weight is valid. Too large, not too heavy."}
{"id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd::1945", "page_id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd", "title": "课后习题（DS 版）", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课后习题（DS 版）", "section": "⚠️ 三、完成真值表/DS Solution/Combinational Test Cases for Rules 4-8/Rule 7: Large Container, Valid Volume, Weight Exceeds Limit", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7CEwNJJMiEkoJkdyDLctP3fnyd", "source_type": "docx", "n_chars": 271, "text": "- **Test Data**: `size = Large`, `weight = 10001 kg`, `volume = 10 m³`\n- **Expected Outputs**: `check()` → `false`, `tooLarge()` → `false`, `tooHeavy()` → `true`\n- **Explanation**: Weight exceeds Large's limit (10000 kg), but volume is valid. Too heavy, not too large."}
{"id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd::1946", "page_id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd", "title": "课后习题（DS 版）", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课后习题（DS 版）", "section": "⚠️ 三、完成真值表/DS Solution/Combinational Test Cases for Rules 4-8/Rule 8: Large Container, Both Weight and Volume Exceed Limits", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7CEwNJJMiEkoJkdyDLctP3fnyd", "source_type": "docx", "n_chars": 263, "text": "- **Test Data**: `size = Large`, `weight = 15000 kg`, `volume = 25 m³`\n- **Expected Outputs**: `check()` → `false`, `tooLarge()` → `true`, `tooHeavy()` → `true`\n- **Explanation**: Both weight and volume exceed Large's limits. Both too large and too heavy.\n\n---"}
{"id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd::1947", "page_id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd", "title": "课后习题（DS 版）", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课后习题（DS 版）", "section": "⚠️ 三、完成真值表/DS Solution/Key Assumptions", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7CEwNJJMiEkoJkdyDLctP3fnyd", "source_type": "docx", "n_chars": 501, "text": "1. **Volume Constraints**:\n\n - Small container: Volume must be **≤1 m³** (invalid if >1).\n - Large container: Volume must be **≤20 m³** (invalid if >20).\n2. **Weight Constraints**:\n\n - Small container: Weight must be **≤1000 kg** (invalid if >1000).\n - Large container: Weight must be **≤10000 kg** (invalid if >10000).\n3. **Input Validity**: Weight and volume are assumed to be **positive integers** (≥1). Invalid inputs (e.g., negative values) are not explicitly covered in this table.\n\n---"}
{"id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd::1948", "page_id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd", "title": "课后习题（DS 版）", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课后习题（DS 版）", "section": "⚠️ 三、完成真值表/DS Solution/Implementation Notes", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7CEwNJJMiEkoJkdyDLctP3fnyd", "source_type": "docx", "n_chars": 294, "text": "- Use parameterized testing to reduce redundancy (e.g., JUnit 5’s `@ParameterizedTest`).\n- Test edge cases explicitly (e.g., `weight = 1000` for Small, `volume = 20` for Large).\n- Ensure mutual exclusivity between `check()`, `tooLarge()`, and `tooHeavy()` based on the problem’s specifications."}
{"id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd::1949", "page_id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd", "title": "课后习题（DS 版）", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课后习题（DS 版）", "section": "四、EP（等价类划分） + BVA（边界值分析）+ TT（真值表）", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7CEwNJJMiEkoJkdyDLctP3fnyd", "source_type": "docx", "n_chars": 688, "text": "\n\n```Java\npublic enum Usage {\n NONE, LOW, HIGH\n}\n\npublic class WindPowerSystem {\n\n public Usage useWindPower(int windSpeed, int hydro, int load) {\n if (windSpeed 120) {\n return Usage.NONE;\n }\n if (hydro >= 100 && load <= 1000) {\n return Usage.LOW;\n } else {\n return Usage.HIGH;\n }\n }\n\n private boolean isValid(int windSpeed, int hydro, int load) {\n // Assuming valid ranges for hydro and load need to be defined\n // For now, let's assume they are non-negative integers\n return windSpeed >= 0 && hydro >= 0 && load >= 0;\n }\n}\n```"}
{"id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd::1950", "page_id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd", "title": "课后习题（DS 版）", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课后习题（DS 版）", "section": "四、EP（等价类划分） + BVA（边界值分析）+ TT（真值表）/Equivalence Partitions", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7CEwNJJMiEkoJkdyDLctP3fnyd", "source_type": "docx", "n_chars": 179, "text": "1. **Invalid Inputs**:\n\n - `windSpeed 120`\n2. **Valid Inputs**:\n\n - `20 1000`: Should return `Usage.HIGH`\n - `hydro >= 100` and `load <= 1000`: Should return `Usage.LOW`"}
{"id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd::1951", "page_id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd", "title": "课后习题（DS 版）", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课后习题（DS 版）", "section": "四、EP（等价类划分） + BVA（边界值分析）+ TT（真值表）/Equivalence Partitions/Boundary Values", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7CEwNJJMiEkoJkdyDLctP3fnyd", "source_type": "docx", "n_chars": 240, "text": "For boundary value analysis, we consider the boundaries of each partition:\n\n- `windSpeed = 19`, `windSpeed = 20`, `windSpeed = 120`, `windSpeed = 121`\n- `hydro = 99`, `hydro = 100`, `hydro = 101`\n- `load = 999`, `load = 1000`, `load = 1001`"}
{"id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd::1952", "page_id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd", "title": "课后习题（DS 版）", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课后习题（DS 版）", "section": "四、EP（等价类划分） + BVA（边界值分析）+ TT（真值表）/Equivalence Partitions/Truth Table", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7CEwNJJMiEkoJkdyDLctP3fnyd", "source_type": "docx", "n_chars": 82, "text": "We can also create a truth table to cover all possible combinations of conditions."}
{"id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd::1953", "page_id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd", "title": "课后习题（DS 版）", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课后习题（DS 版）", "section": "五、白盒", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7CEwNJJMiEkoJkdyDLctP3fnyd", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd::1954", "page_id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd", "title": "课后习题（DS 版）", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课后习题（DS 版）", "section": "六、EP + BVA", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7CEwNJJMiEkoJkdyDLctP3fnyd", "source_type": "docx", "n_chars": 694, "text": "\n\n```Java\nclass DataInput {\n private int value;\n\n // If s represents a valid Java int, which is >= min and <= max,\n // then convert sets \"value\" to the value represented by s and\n // returns true.\n // Otherwise, value is undefined, and convert() returns false.\n public boolean convert(String s, int min, int max) {\n try {\n int intValue = Integer.parseInt(s);\n if (intValue >= min && intValue <= max) {\n value = intValue;\n return true;\n }\n } catch (NumberFormatException e) {\n // The string could not be parsed as an integer\n }"}
{"id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd::1955", "page_id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd", "title": "课后习题（DS 版）", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课后习题（DS 版）", "section": "六、EP + BVA", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7CEwNJJMiEkoJkdyDLctP3fnyd", "source_type": "docx", "n_chars": 190, "text": "h (NumberFormatException e) {\n // The string could not be parsed as an integer\n }\n return false;\n }\n\n public int getValue() {\n return value;\n }\n}\n```"}
{"id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd::1956", "page_id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd", "title": "课后习题（DS 版）", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课后习题（DS 版）", "section": "六、EP + BVA/Unit Tests Using Equivalence Partitioning and Boundary Value Analysis/Equivalence Partitions", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7CEwNJJMiEkoJkdyDLctP3fnyd", "source_type": "docx", "n_chars": 307, "text": "1. **Valid Inputs**:\n\n - A string that can be parsed to an integer within the range `[min, max]`.\n2. **Invalid Inputs**:\n\n - A string that cannot be parsed to an integer (e.g., \"abc\").\n - A string that represents an integer less than `min`.\n - A string that represents an integer greater than `max`."}
{"id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd::1957", "page_id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd", "title": "课后习题（DS 版）", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课后习题（DS 版）", "section": "六、EP + BVA/Unit Tests Using Equivalence Partitioning and Boundary Value Analysis/Equivalence Partitions/Boundary Values", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7CEwNJJMiEkoJkdyDLctP3fnyd", "source_type": "docx", "n_chars": 451, "text": "- For a given range `[min, max]`, test the following values:\n\n - `min - 1`\n - `min`\n - `min + 1`\n - `max - 1`\n - `max`\n - `max + 1`\n\nNow, let's write the unit tests in Java using JUnit.\n\nThis artifact contains the implementation of the `convert` method and its corresponding unit tests covering equivalence partitions and boundary values. You can run these tests using a JUnit testing framework to ensure the correctness of the `convert` method."}
{"id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd::1958", "page_id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd", "title": "课后习题（DS 版）", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课后习题（DS 版）", "section": "七、语句 + 分支覆盖", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7CEwNJJMiEkoJkdyDLctP3fnyd", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd::1959", "page_id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd", "title": "课后习题（DS 版）", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课后习题（DS 版）", "section": "七、语句 + 分支覆盖/基于代码逻辑分析（Java方法`check()`）", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7CEwNJJMiEkoJkdyDLctP3fnyd", "source_type": "docx", "n_chars": 102, "text": "方法目标：验证字符串 `s` 中的所有字符是否为有效数字字符（0-9）。\n\n代码逻辑缺陷：\n\n- **第10行** （字符的ASCII值不可能小于0，应修正为 `s.charAt(i)'9'`）\n\n---"}
{"id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd::1960", "page_id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd", "title": "课后习题（DS 版）", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课后习题（DS 版）", "section": "七、语句 + 分支覆盖/基于代码逻辑分析（Java方法`check()`）/（a）语句覆盖测试设计", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7CEwNJJMiEkoJkdyDLctP3fnyd", "source_type": "docx", "n_chars": 249, "text": "**目标**：执行每一行代码至少一次\n\n**测试用例**：\n\n1. **有效字符串**\n\n - 输入：`s = \"5\"`\n - 执行路径：\n\n - `s.length() >=1` → 跳过第7行\n - 循环遍历字符 `'5'` → 跳过第10、12行\n - `return true`\n - **覆盖代码行**：6,7,9,10,12,14,15\n2. **无效字符串**\n\n - s = \"\"\n - s = \"!\"\n - s = \"A\"\n\n---"}
{"id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd::1961", "page_id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd", "title": "课后习题（DS 版）", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课后习题（DS 版）", "section": "七、语句 + 分支覆盖/基于代码逻辑分析（Java方法`check()`）/（b）分支覆盖测试设计", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7CEwNJJMiEkoJkdyDLctP3fnyd", "source_type": "docx", "n_chars": 66, "text": "**目标**：覆盖所有判断条件的 **真/假** 结果\n\n**关键分支**：\n\n1. **`if (s.length() 9)`**"}
{"id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd::1962", "page_id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd", "title": "课后习题（DS 版）", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课后习题（DS 版）", "section": "七、语句 + 分支覆盖/基于代码逻辑分析（Java方法`check()`）/（b）分支覆盖测试设计/测试用例：", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7CEwNJJMiEkoJkdyDLctP3fnyd", "source_type": "docx", "n_chars": 247, "text": "| 用例编号 | 输入 | 预期输出 | 覆盖的分支条件 |\n|-|-|-|-|\n| 1 | `s = \"\"` | `false` | 分支1为真（空字符串） |\n| 2 | `s = \"a\"` | `false` | 分支3为真（字符 `'a'` ASCII > '9'） |\n| 3 | `s = \"5\"` | `true` | 分支1、2、3均为假（所有条件不触发） |\n| 4 | `s = \"√\"` | `false` | 分支2为真（假设 `√` 的ASCII <0） |\n\n---"}
{"id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd::1963", "page_id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd", "title": "课后习题（DS 版）", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课后习题（DS 版）", "section": "七、语句 + 分支覆盖/基于代码逻辑分析（Java方法`check()`）/测试代码示例（JUnit）", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7CEwNJJMiEkoJkdyDLctP3fnyd", "source_type": "docx", "n_chars": 539, "text": "```Java\nimport static org.junit.Assert.*;\nimport org.junit.Test;\n\npublic class CheckTest {\n @Test\n public void testEmptyString() {\n assertFalse(check(\"\")); // 用例1：分支1为真\n }\n\n @Test\n public void testNonNumericChar() {\n assertFalse(check(\"a\")); // 用例2：分支3为真\n }\n\n @Test\n public void testValidString() {\n assertTrue(check(\"5\")); // 用例3：所有分支为假\n }\n\n @Test\n public void testInvalidLowChar() {\n assertFalse(check(\"√\")); // 用例4：分支2为真（假设存在ASCII<0的字符）\n }\n}\n```\n\n---"}
{"id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd::1964", "page_id": "docx::E7CEwNJJMiEkoJkdyDLctP3fnyd", "title": "课后习题（DS 版）", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课后习题（DS 版）", "section": "七、语句 + 分支覆盖/基于代码逻辑分析（Java方法`check()`）/潜在问题与改进建议", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7CEwNJJMiEkoJkdyDLctP3fnyd", "source_type": "docx", "n_chars": 154, "text": "1. **逻辑错误修复**：\n\n - 将第10行改为 `s.charAt(i) '9'`\n2. **边界条件补充**：\n\n - 测试 `s = \"0\"`（最小值）和 `s = \"9\"`（最大值）\n3. **性能优化**：\n\n - 循环中一旦 `ok = false` 可提前终止（避免冗余判断）"}
{"id": "docx::Qi2dwZhlGiCaylkjVVgcVK1hnRb::1965", "page_id": "docx::Qi2dwZhlGiCaylkjVVgcVK1hnRb", "title": "课后复习题（选择题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后复习题（选择题题库）", "section": "课后复习题（选择题题库）", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qi2dwZhlGiCaylkjVVgcVK1hnRb", "source_type": "docx", "n_chars": 325, "text": "课后复习题（选择题题库）\n\n\n\n答案选 B\n\nATAM 提到过，Reviewer可以是同行审核，也可以是完全无关者审核\n\n21.2\n\n... Stakeholders include [developers, testers, integrators,\n\nmaintainers, performance engineers, users, builders of systems interacting\n\nwith the one under consideration, and others listed in Chapter 3.]"}
{"id": "docx::Qi2dwZhlGiCaylkjVVgcVK1hnRb::1966", "page_id": "docx::Qi2dwZhlGiCaylkjVVgcVK1hnRb", "title": "课后复习题（选择题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后复习题（选择题题库）", "section": "Chapter 04", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qi2dwZhlGiCaylkjVVgcVK1hnRb", "source_type": "docx", "n_chars": 226, "text": "\n\n\n\n\n\n"}
{"id": "docx::Qi2dwZhlGiCaylkjVVgcVK1hnRb::1967", "page_id": "docx::Qi2dwZhlGiCaylkjVVgcVK1hnRb", "title": "课后复习题（选择题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后复习题（选择题题库）", "section": "Chapter 15", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qi2dwZhlGiCaylkjVVgcVK1hnRb", "source_type": "docx", "n_chars": 681, "text": "1. Which one of the following tactics is for improving availability?\n\n 1. Resource management and scheduling\n 2. Increase module cohesion\n 3. Passive redundancy\n 4. Discover services\n\n\n\n1. Modifiablility is about the change and our interest in it is the cost and risk of making the change. Which of the following statements is **NOT** true about modifiablility?\n\n 1. Using an intermediary can help improve modifiability\n 2. The change can be made during the implementation or execution\n 3. Making modules bigger can help increase modifiablility\n 4. Publish/Subscribe tactic is used for improving modifiablility"}
{"id": "docx::Qi2dwZhlGiCaylkjVVgcVK1hnRb::1968", "page_id": "docx::Qi2dwZhlGiCaylkjVVgcVK1hnRb", "title": "课后复习题（选择题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后复习题（选择题题库）", "section": "Chapter 15", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qi2dwZhlGiCaylkjVVgcVK1hnRb", "source_type": "docx", "n_chars": 674, "text": "n help increase modifiablility\n 4. Publish/Subscribe tactic is used for improving modifiablility\n\n\n\n1. About Agile architecture, which of the following statements is **NOT** true?\n\n 1. Large-scale successful projects need a blend of agile and architecture\n 2. For small projects with uncertain requirements, spending too much time on architecture design is not a good choice\n 3. For large projects with unstable requirements, it is not needed to design architecture at the early phase of project.\n 4. For a large and complex system with stable requirements, it is good to devote much time on the architecture."}
{"id": "docx::Qi2dwZhlGiCaylkjVVgcVK1hnRb::1969", "page_id": "docx::Qi2dwZhlGiCaylkjVVgcVK1hnRb", "title": "课后复习题（选择题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后复习题（选择题题库）", "section": "Chapter 15", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qi2dwZhlGiCaylkjVVgcVK1hnRb", "source_type": "docx", "n_chars": 155, "text": "e and complex system with stable requirements, it is good to devote much time on the architecture.\n\n"}
{"id": "docx::Qi2dwZhlGiCaylkjVVgcVK1hnRb::1970", "page_id": "docx::Qi2dwZhlGiCaylkjVVgcVK1hnRb", "title": "课后复习题（选择题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后复习题（选择题题库）", "section": "参考答案/Chapter 04", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qi2dwZhlGiCaylkjVVgcVK1hnRb", "source_type": "docx", "n_chars": 648, "text": "1. 选择 B，因为在 run time 阶段表现的结构是 C&C Structure\n\n原文：\n\nOther structures focus on the way the elements interact with each other **at runtime** to carry out the system's functions. / 其他结构关注于元素在运行时如何相互交互以实现系统的功能。\n\nWe call runtime structures component-and-connector (C&C) structures. / 我们称这种运行时结构为组件与连接器（C&C）结构。\n\n1. 选择 D\n\n原文：\n\n\n\n1. 选择 C\n\nSome structures partition systems into implementation units, which we call modules. / 一些结构将系统划分为实现单元，我们称之为模块。\nModules are assigned specific computational responsibilities, and are the basis of work assignments for programming teams. / 模块被分配了特定的计算责任，并成为编程团队工作分配的基础。"}
{"id": "docx::Qi2dwZhlGiCaylkjVVgcVK1hnRb::1971", "page_id": "docx::Qi2dwZhlGiCaylkjVVgcVK1hnRb", "title": "课后复习题（选择题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后复习题（选择题题库）", "section": "参考答案/Chapter 04", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qi2dwZhlGiCaylkjVVgcVK1hnRb", "source_type": "docx", "n_chars": 667, "text": "ities, and are the basis of work assignments for programming teams. / 模块被分配了特定的计算责任，并成为编程团队工作分配的基础。\nIn large projects, these elements (modules) are subdivided for assignment to subteams. / 在大型项目中，这些元素（模块）会进一步细分，以便分配给子团队。\n\nModule structures embody decisions as to how the system is to be structured as a set of code or data units. / 模块结构体现了关于系统如何作为一组代码或数据单元进行组织的决策。\n\nIn any module structure, the elements are modules of some kind (perhaps classes, or layers, or merely divisions of functionality all of which are units of implementation). / 在任何模块结构中，元素都是某种类型的模块（可能是类，层，或者仅仅是功能的划分，这些都属于实现单元）。\n\nModules are assigned areas of functional responsibility. / 模块被分配了特定的功能责任区域。"}
{"id": "docx::Qi2dwZhlGiCaylkjVVgcVK1hnRb::1972", "page_id": "docx::Qi2dwZhlGiCaylkjVVgcVK1hnRb", "title": "课后复习题（选择题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后复习题（选择题题库）", "section": "参考答案/Chapter 04", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qi2dwZhlGiCaylkjVVgcVK1hnRb", "source_type": "docx", "n_chars": 221, "text": "者仅仅是功能的划分，这些都属于实现单元）。\n\nModules are assigned areas of functional responsibility. / 模块被分配了特定的功能责任区域。\n\n\n\n1. 选择 D\n\n"}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::1973", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 01", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::1974", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 01/参考答案", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 384, "text": "**Software architecture and building architecture analogy**\n**Strong points of the analogy:**\n\n- **Foundational importance**: Both software architecture and building architecture are foundational to their respective systems. A good architectural design establishes a robust structure for the entire system, providing a framework within which all other components function effectively."}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::1975", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 01/参考答案", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 449, "text": "or the entire system, providing a framework within which all other components function effectively.\n- **Guiding development**: Both kinds of architecture serve as the blueprint or guiding plan for the development of the system. In buildings, the architectural plans dictate the layout, flow, and integration of spaces, and in software, the architecture defines the structure of software components, their interactions, and how they evolve over time."}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::1976", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 01/参考答案", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 678, "text": "re defines the structure of software components, their interactions, and how they evolve over time.\n- **Reusability and patterns**: Both software and building architecture utilize established patterns or designs. In buildings, these may include structural patterns like domes, arches, or beams, while in software, patterns such as layered, client-server, or microservices architectures guide the design of scalable, efficient systems.\n- **Views**: Just as a building can be viewed from multiple perspectives (e.g., floor plans, elevations, sections), software architecture is often represented using different views, such as module, deployment, or component-and-connector views."}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::1977", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 01/参考答案", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 422, "text": "n represented using different views, such as module, deployment, or component-and-connector views.\n\n**Correspondence in buildings to software architecture structures and views:**\n\n- **Structures**: In buildings, the structures can be likened to the software components (e.g., walls, beams, and floors in a building) and the connections between them (e.g., load-bearing connections in buildings and data flows in software)."}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::1978", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 01/参考答案", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 629, "text": "connections between them (e.g., load-bearing connections in buildings and data flows in software).\n- **Views**: In buildings, views are created to represent the architecture from different perspectives—e.g., the façade view or cross-sectional view—which is similar to how different views in software (e.g., component view, deployment view) provide different perspectives on the system’s architecture.\n- **Patterns**: Building architectural patterns (e.g., residential, commercial, gothic, modern) are similar to software patterns like layered architecture, client-server, and event-driven designs.\n\n**Weaknesses of the analogy:**"}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::1979", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 01/参考答案", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 579, "text": "ike layered architecture, client-server, and event-driven designs.\n\n**Weaknesses of the analogy:**\n\n- **Dynamic vs static**: Building architecture is largely static, whereas software systems are dynamic and evolve continuously, which makes architectural decisions for software more complex in terms of scalability, maintenance, and adaptability.\n- **Physical vs logical constraints**: Buildings have physical constraints (e.g., weight, materials, space), while software architecture primarily deals with logical constraints (e.g., data flow, processing power, user requirements)."}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::1980", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 01/参考答案", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 650, "text": "re primarily deals with logical constraints (e.g., data flow, processing power, user requirements).\n- **Human interaction**: The interaction between people and a building is generally direct (e.g., physical movement through spaces), whereas the interaction between users and software can be more abstract and mediated by interfaces and software logic.\n- **Breakdown of analogy**: The analogy breaks down when considering software's need for flexibility, changes in functionality over time, or the ability to quickly integrate new technologies. This is unlike buildings, where once constructed, significant changes are often costly and difficult.\n\n---"}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::1981", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 01/参考答案", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 667, "text": "unlike buildings, where once constructed, significant changes are often costly and difficult.\n\n---\n\n**Documented structures and relations in architectures**\n In architectures I have been exposed to, there are often multiple structures and relations documented. For instance, typical software architectures document the **modular structure**, **component interactions**, and **data flow**, similar to the descriptions in this chapter. However, some architectures might lack certain views like **allocation structures** or **deployment structures** due to the project's scope or the focus on specific aspects like performance optimization or user interface design.\n\n---"}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::1982", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 01/参考答案", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 649, "text": "cope or the focus on specific aspects like performance optimization or user interface design.\n\n---\n\n1. **Alternative definitions of software architecture**\n Another common definition of software architecture includes **rationale**—that is, the reasoning behind design decisions. For example, it explains why certain patterns or technologies were chosen, or why specific trade-offs were made (e.g., between performance and scalability). In comparison to the definition in this chapter, this adds a layer of **justification** to the architecture, which could be valuable for future decision-making or for stakeholders to understand the design choices."}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::1983", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 01/参考答案", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 445, "text": "could be valuable for future decision-making or for stakeholders to understand the design choices.\n\nI agree that considerations like **rationale** and **evolution** should be part of the definition because they provide insight into the **why** behind architecture, enabling future developers or teams to understand its evolution and be better equipped to modify or extend it.\n\n---\n\n1. **Architecture as a basis for analysis and decision-making**"}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::1984", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 01/参考答案", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 432, "text": "ipped to modify or extend it.\n\n---\n\n1. **Architecture as a basis for analysis and decision-making**\n Architecture serves as the basis for **system analysis** by providing a framework through which quality attributes like performance, modifiability, and security can be assessed. For instance, a **concurrency structure** can reveal potential bottlenecks, and a **deployment structure** can help assess the system’s ability to scale."}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::1985", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 01/参考答案", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 674, "text": "tential bottlenecks, and a **deployment structure** can help assess the system’s ability to scale.\n\nIn decision-making, architecture empowers decisions related to **cost**, **schedule**, **resource allocation**, and **risk management**. For example, the choice of a **layered architecture** may lead to easier modifiability, influencing decisions about long-term maintenance costs.\n\n---\n\n1. **Architecture's role in project risk reduction**\n Architecture helps in **reducing project risks** by:\n\n- **Providing clarity**: It clarifies the overall structure of the system, ensuring all stakeholders have a shared understanding of the system’s components and how they interact."}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::1986", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 01/参考答案", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 570, "text": "ring all stakeholders have a shared understanding of the system’s components and how they interact.\n- **Early identification of bottlenecks**: Through architectural analysis, performance and scalability issues can be identified early, allowing time for adjustments.\n- **Guiding incremental development**: A well-defined architecture allows for an incremental, modular development approach, where parts of the system can be tested and deployed gradually, reducing the risk of failure.\n\n---\n\n1. **System architecture vs. Software architecture vs. Enterprise architecture**"}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::1987", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 01/参考答案", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 534, "text": "of failure.\n\n---\n\n1. **System architecture vs. Software architecture vs. Enterprise architecture**\n\n- **System Architecture**: This typically refers to the overall structure of a system, which can include hardware and software elements. It outlines how different subsystems interact, such as in embedded systems where software and hardware must work together.\n- **Software Architecture**: As defined in the chapter, software architecture focuses primarily on the software components and their relationships within the software system."}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::1988", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 01/参考答案", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 628, "text": "re focuses primarily on the software components and their relationships within the software system.\n- **Enterprise Architecture**: This encompasses the structure and design of the entire organization’s IT infrastructure, including systems, applications, data, and technologies. It provides a high-level view to align IT strategy with business goals. All three share a focus on **structural decisions**, but **enterprise architecture** extends beyond software and includes business processes and IT systems alignment.\n\n---\n\n1. **Example of architecture**\n Consider an example architecture for a **web-based e-commerce platform**:"}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::1989", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 01/参考答案", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 621, "text": "ample of architecture**\n Consider an example architecture for a **web-based e-commerce platform**:\n\n- **Structures shown**: Typically, a web application architecture would show a **client-server structure**, **component-and-connector structure** (e.g., front-end, back-end services), and **deployment structure** (e.g., cloud-based servers, databases).\n- **Missing structures**: If not included, the **work assignment structure** (who does what, which teams work on which parts) and **performance-related structures** (such as caching layers) should be included for better analysis of performance and team responsibility."}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::1990", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 01/参考答案", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 616, "text": "h as caching layers) should be included for better analysis of performance and team responsibility.\n- **Analysis supported**: The architecture supports **performance**, **scalability**, and **availability analysis**, but it may not provide enough detail on **security** or **data privacy**, which could be crucial for an e-commerce platform.\n\n---\n\n1. **Sailing ships' architecture**\n When thinking about sailing ships, we can propose the following **structures** for distinguishing and reasoning about ship architecture:\n\n- **Hull structure**: Defines the ship's shape and how it impacts **stability** and **speed**."}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::1991", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 01/参考答案", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 680, "text": "re:\n\n- **Hull structure**: Defines the ship's shape and how it impacts **stability** and **speed**.\n- **Rigging structure**: Includes the types of sails and masts, which determine the **sailing capabilities** and **wind resistance**.\n- **Control structure**: Refers to the steering mechanisms (rudder, wheel) and how they affect **maneuverability**.\n- **Cargo structure**: Outlines how the ship’s internal space is organized for cargo, affecting **capacity** and **balance**.\n\nThese structures would allow us to reason about the ship’s **performance**, **speed**, **sailing ability**, and **load distribution**—similar to how software architecture reasons about system attributes."}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::1992", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 02", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::1993", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 02/参考答案/Q1: Contrarian Position for Each of the Thirteen Reasons", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 478, "text": "1. **Architecture will inhibit or enable a system's driving quality attributes.**\n\n - **Contrarian View**: In small projects or prototyping, direct code changes and iterative testing may be more effective in driving quality attributes than relying on architecture. Developers may make quick decisions based on immediate needs without formal architectural constraints.\n2. **The decisions made in architecture allow you to reason about and manage change as the system evolves.**"}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::1994", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 02/参考答案/Q1: Contrarian Position for Each of the Thirteen Reasons", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 473, "text": "ecisions made in architecture allow you to reason about and manage change as the system evolves.**\n\n - **Contrarian View**: In fast-moving, agile environments or short-term projects, where the system evolves rapidly, architecture decisions may become outdated quickly, and continuous refactoring might be a better way to manage change than relying on long-term architectural decisions.\n3. **The analysis of architecture enables early prediction of a system's qualities.**"}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::1995", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 02/参考答案/Q1: Contrarian Position for Each of the Thirteen Reasons", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 456, "text": "l decisions.\n3. **The analysis of architecture enables early prediction of a system's qualities.**\n\n - **Contrarian View**: In small, tightly scoped projects or experiments, early architecture analysis may not provide significant benefits. Developers might just build quickly, and qualities may be determined through direct testing rather than predictions based on architecture.\n4. **A documented architecture enhances communication among stakeholders.**"}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::1996", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 02/参考答案/Q1: Contrarian Position for Each of the Thirteen Reasons", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 457, "text": "based on architecture.\n4. **A documented architecture enhances communication among stakeholders.**\n\n - **Contrarian View**: In highly collaborative, small teams, verbal communication or informal meetings may suffice for sharing ideas and solving problems. Documenting architecture could be time-consuming and unnecessary in such environments.\n5. **Architecture is a carrier of the earliest and hence most fundamental, hardest-to-change design decisions.**"}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::1997", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 02/参考答案/Q1: Contrarian Position for Each of the Thirteen Reasons", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 677, "text": "ure is a carrier of the earliest and hence most fundamental, hardest-to-change design decisions.**\n\n - **Contrarian View**: In projects where requirements are unclear or likely to change frequently, architecture might actually constrain flexibility. For these projects, it might be better to defer architectural decisions and evolve the system as needed.\n6. **An architecture defines a set of constraints on subsequent implementation.**\n\n - **Contrarian View**: For rapid development or innovation, minimal architectural constraints may be advantageous, as they allow the team to explore different solutions freely and experiment without being confined by rigid guidelines."}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::1998", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 02/参考答案/Q1: Contrarian Position for Each of the Thirteen Reasons", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 519, "text": "am to explore different solutions freely and experiment without being confined by rigid guidelines.\n7. **The architecture dictates the structure of an organization, or vice versa.**\n\n - **Contrarian View**: In small or decentralized organizations, the architecture may not significantly impact organizational structure. Teams may self-organize, and flexible workflows may be more effective than relying on an overarching architectural vision.\n8. **An architecture can provide the basis for evolutionary prototyping.**"}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::1999", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 02/参考答案/Q1: Contrarian Position for Each of the Thirteen Reasons", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 487, "text": "g architectural vision.\n8. **An architecture can provide the basis for evolutionary prototyping.**\n\n - **Contrarian View**: In highly exploratory projects, a predefined architecture might limit the potential to explore innovative solutions. Evolutionary prototyping can occur without a structured architecture, with the focus being on rapid iteration and feedback.\n9. **Architecture is the key artifact that allows the architect and project manager to reason about cost and schedule.**"}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::2000", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 02/参考答案/Q1: Contrarian Position for Each of the Thirteen Reasons", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 478, "text": "he key artifact that allows the architect and project manager to reason about cost and schedule.**\n\n - **Contrarian View**: In small projects or where deadlines are short, cost and schedule can be managed more effectively through simple task lists and timeboxing techniques. Detailed architectural planning might not be necessary for managing smaller-scale projects.\n10. **Architecture can be created as a transferable, reusable model that forms the heart of a product line.**"}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::2001", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 02/参考答案/Q1: Contrarian Position for Each of the Thirteen Reasons", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 493, "text": "tecture can be created as a transferable, reusable model that forms the heart of a product line.**\n\n - **Contrarian View**: In highly customized or niche products, the cost of creating reusable models might not justify the benefits. A one-off architecture tailored specifically to the product may be more cost-effective than trying to create reusable architecture.\n11. **Architecture-based development focuses attention on the assembly of components, rather than simply on their creation.**"}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::2002", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 02/参考答案/Q1: Contrarian Position for Each of the Thirteen Reasons", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 510, "text": "velopment focuses attention on the assembly of components, rather than simply on their creation.**\n\n - **Contrarian View**: In smaller, monolithic applications or prototyping efforts, the focus may be on getting a working prototype rather than assembling independent components. The complexity of managing multiple components can be avoided in favor of direct development.\n12. **By restricting design alternatives, architecture channels the creativity of developers, reducing design and system complexity.**"}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::2003", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 02/参考答案/Q1: Contrarian Position for Each of the Thirteen Reasons", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 690, "text": "ives, architecture channels the creativity of developers, reducing design and system complexity.**\n\n - **Contrarian View**: In highly creative or exploratory environments (e.g., startups), limiting design alternatives through architectural constraints might stifle innovation. In such cases, it may be better to keep options open and experiment freely.\n13. **Architecture can be the foundation for training a new team member.**\n\n - **Contrarian View**: In fast-paced, fluid teams, especially in smaller companies or projects with short timelines, direct mentoring and on-the-job learning may be more effective than relying on architecture documentation to train new team members.\n\n---"}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::2004", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 02/参考答案/Q2: Measuring the Benefits of Architecture in a Project", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 534, "text": "To measure the benefits of each of the thirteen points, consider the following metrics or evaluation methods:\n\n1. **Inhibiting or Enabling Quality Attributes**: Measure performance, scalability, and security after implementing architecture. Track improvements in key quality metrics (e.g., response time, uptime, throughput).\n2. **Reasoning About and Managing Change**: Track the time and effort spent on refactoring over time. Fewer changes and less refactoring in an architecture-driven project suggest successful change management."}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::2005", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 02/参考答案/Q2: Measuring the Benefits of Architecture in a Project", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 556, "text": "hanges and less refactoring in an architecture-driven project suggest successful change management.\n3. **Early Prediction of System Qualities**: Use early testing or simulation results to predict system performance. Measure how accurate early architectural predictions were when compared to post-implementation results.\n4. **Enhancing Communication Among Stakeholders**: Conduct surveys to measure stakeholder satisfaction and alignment before and after documentation of the architecture. Track issues or misunderstandings that arise without documentation."}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::2006", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 02/参考答案/Q2: Measuring the Benefits of Architecture in a Project", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 509, "text": "umentation of the architecture. Track issues or misunderstandings that arise without documentation.\n5. **Carrier of Early Design Decisions**: Evaluate the frequency of changes to the design and compare with the cost of those changes. More stable decisions early on reduce the cost and disruption of future changes.\n6. **Defining Constraints on Implementation**: Measure the speed and flexibility of implementation. Too many constraints might slow development; too few might lead to misalignment of components."}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::2007", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 02/参考答案/Q2: Measuring the Benefits of Architecture in a Project", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 551, "text": "ion. Too many constraints might slow development; too few might lead to misalignment of components.\n7. **Architecture Dictating Organizational Structure**: Measure the efficiency and clarity of communication and decision-making in teams structured around the architecture. Track performance or productivity of teams organized according to the architecture.\n8. **Basis for Evolutionary Prototyping**: Track how fast prototypes can be built and how frequently the system changes. Evolutionary prototyping can reduce risk if the system can adapt quickly."}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::2008", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 02/参考答案/Q2: Measuring the Benefits of Architecture in a Project", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 697, "text": "ently the system changes. Evolutionary prototyping can reduce risk if the system can adapt quickly.\n9. **Key Artifact for Cost and Schedule**: Compare initial estimates to actual costs and schedules. A more accurate forecast after architecture planning would demonstrate its effectiveness.\n10. **Transferable, Reusable Model for Product Lines**: Evaluate the cost and time saved when reusing the architecture across different products. Reusability metrics include reduced development time for new products.\n11. **Assembly of Components vs. Creation of Components**: Track the time spent assembling existing components versus creating new ones. Focusing on assembly could reduce the time to market."}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::2009", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 02/参考答案/Q2: Measuring the Benefits of Architecture in a Project", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 620, "text": "existing components versus creating new ones. Focusing on assembly could reduce the time to market.\n12. **Restricting Design Alternatives to Reduce Complexity**: Track the complexity of the system. Fewer design alternatives might lead to a simpler, more maintainable system, which can be measured by metrics like code churn, bug reports, and maintenance costs.\n13. **Architecture as a Foundation for Training**: Measure how quickly new team members become productive. Faster onboarding and fewer questions related to system understanding could indicate the effectiveness of architectural documentation for training.\n\n---"}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::2010", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 02/参考答案/Q3: ROI for Architecture-Centric Practices", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 490, "text": "When introducing architecture-centric practices, the **ROI** could be argued as follows:\n\n- **Reduced rework and errors**: By establishing clear architectural guidelines upfront, teams are less likely to make design mistakes that require costly rework.\n- **Faster scaling and better quality**: Architecture enables better decision-making around scalability, performance, and maintainability. This leads to a system that is easier to extend, potentially reducing long-term development costs."}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::2011", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 02/参考答案/Q3: ROI for Architecture-Centric Practices", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 512, "text": "This leads to a system that is easier to extend, potentially reducing long-term development costs.\n- **Improved communication**: A well-documented architecture ensures that all stakeholders have a clear understanding of the system, reducing miscommunication and ambiguity. This can prevent costly mistakes and improve project coordination.\n- **Faster onboarding**: New team members can get up to speed faster when there is a documented architecture, leading to reduced training time and quicker project delivery."}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::2012", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 02/参考答案/Q3: ROI for Architecture-Centric Practices", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 368, "text": "there is a documented architecture, leading to reduced training time and quicker project delivery.\n- **Long-term cost savings**: Reusing architectural models or components across projects reduces future development time and cost. The reusability aspect of architecture-centric practices contributes to a lower total cost of ownership over multiple product cycles.\n\n---"}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::2013", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 02/参考答案/Q4: Prioritizing the Thirteen Points", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 626, "text": "Here’s a prioritized list based on my judgment of which aspects are most critical for long-term success:\n\n- **Architecture will inhibit or enable a system's driving quality attributes.** Because quality attributes (performance, security, modifiability) directly impact the system’s success.\n- **The analysis of architecture enables early prediction of a system's qualities.** Early predictions prevent costly changes later.\n- **Architecture is a carrier of the earliest and hence most fundamental, hardest-to-change design decisions.** These decisions influence the system's long-term direction and are costly to change later."}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::2014", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 02/参考答案/Q4: Prioritizing the Thirteen Points", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 583, "text": "sions.** These decisions influence the system's long-term direction and are costly to change later.\n- **An architecture defines a set of constraints on subsequent implementation.** Constraints ensure consistency and direction during implementation.\n- **Architecture is the key artifact that allows the architect and project manager to reason about cost and schedule. Cost** and schedule management are crucial for project success.\n- **A documented architecture enhances communication among stakeholders.** Clear communication is essential for project alignment and avoiding mistakes."}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::2015", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 02/参考答案/Q4: Prioritizing the Thirteen Points", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 614, "text": "among stakeholders.** Clear communication is essential for project alignment and avoiding mistakes.\n- **Architecture can be created as a transferable, reusable model that forms the heart of a product.** Reusability lowers future costs and speeds up product development.\n- **Architecture-based development focuses attention on the assembly of components, rather than simply on their creation.** Assembling pre-existing components speeds development and ensures scalability.\n- **Architecture can provide the basis for evolutionary prototyping.** Prototypes based on solid architecture are easier to evolve and adapt."}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::2016", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 02/参考答案/Q4: Prioritizing the Thirteen Points", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 587, "text": "evolutionary prototyping.** Prototypes based on solid architecture are easier to evolve and adapt.\n- **By restricting design alternatives, architecture channels the creativity of developers, reducing design and system complexity.** Simpler systems are easier to maintain and scale.\n- **The architecture dictates the structure of an organization, or vice versa.** Organizational alignment with architecture ensures smooth project execution.\n- **Architecture can be the foundation for training a new team member.** A clear architectural foundation helps new members get up to speed faster."}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::2017", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 02/参考答案/Q4: Prioritizing the Thirteen Points", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 223, "text": "ing a new team member.** A clear architectural foundation helps new members get up to speed faster.\n- **An architecture can provide the basis for evolutionary prototyping.** Prototypes can be iterated based on architecture,"}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::2018", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 04", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::2019", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 05", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::2020", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 06", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::2021", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 07", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::2022", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 08", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::2023", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 09", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::2024", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 10", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::2025", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 11", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::2026", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 12", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::2027", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 13", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::2028", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 14", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::2029", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 15", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::2030", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 16", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::2031", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 17", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::2032", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 19", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae::2033", "page_id": "docx::JUfUw2mTHiahSbkQXAAcw6PDnae", "title": "课后讨论题（简答题题库）", "course": "2.5➡️3.0 软件体系结构 / Software Architecture", "path": "2.5➡️3.0 软件体系结构 / Software Architecture/课后讨论题（简答题题库）", "section": "Chapter 21", "url": "https://a1npn29y3xu.feishu.cn/wiki/JUfUw2mTHiahSbkQXAAcw6PDnae", "source_type": "docx", "n_chars": 55, "text": ""}
{"id": "docx::PWocwsbMoiRSeokDnQRchFT6nAb::2034", "page_id": "docx::PWocwsbMoiRSeokDnQRchFT6nAb", "title": "课本例题", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课本例题", "section": "课本例题", "url": "https://a1npn29y3xu.feishu.cn/wiki/PWocwsbMoiRSeokDnQRchFT6nAb", "source_type": "docx", "n_chars": 61, "text": "课本例题\n\n"}
{"id": "docx::PWocwsbMoiRSeokDnQRchFT6nAb::2035", "page_id": "docx::PWocwsbMoiRSeokDnQRchFT6nAb", "title": "课本例题", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课本例题", "section": "订座系统", "url": "https://a1npn29y3xu.feishu.cn/wiki/PWocwsbMoiRSeokDnQRchFT6nAb", "source_type": "docx", "n_chars": 69, "text": "Page 60 - 75\n\n"}
{"id": "docx::PWocwsbMoiRSeokDnQRchFT6nAb::2036", "page_id": "docx::PWocwsbMoiRSeokDnQRchFT6nAb", "title": "课本例题", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课本例题", "section": "订座系统/黑盒测试/等价类划分", "url": "https://a1npn29y3xu.feishu.cn/wiki/PWocwsbMoiRSeokDnQRchFT6nAb", "source_type": "docx", "n_chars": 452, "text": "有效等价类\n\nfreeSeats 在区间内\n\nseatRequired 在区间内\n\nfreeSeats >= seatsRequired\n\n无效等价类\n\nfreeSeats 不在区间内\n\nseatRequired 不在区间内\n\nfreeSeats < seatsRequired\n\n\n\n\n\n补充说明：打 \\* 号的表示无效等价类，每一个写一条。没有打 \\* 号的表示有效等价类，使用尽量少的测试用例覆盖尽量多的有效等价类\n\n\n\n用例 ID被覆盖的用例输入预期输出freeSeatsseatsRequired返回值有效等价类12,7,1023,6,9无效等价类31445568"}
{"id": "docx::PWocwsbMoiRSeokDnQRchFT6nAb::2037", "page_id": "docx::PWocwsbMoiRSeokDnQRchFT6nAb", "title": "课本例题", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课本例题", "section": "订座系统/黑盒测试/边界值分析", "url": "https://a1npn29y3xu.feishu.cn/wiki/PWocwsbMoiRSeokDnQRchFT6nAb", "source_type": "docx", "n_chars": 112, "text": "\n\n"}
{"id": "docx::PWocwsbMoiRSeokDnQRchFT6nAb::2038", "page_id": "docx::PWocwsbMoiRSeokDnQRchFT6nAb", "title": "课本例题", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课本例题", "section": "订座系统/黑盒测试/组合测试（真值表）", "url": "https://a1npn29y3xu.feishu.cn/wiki/PWocwsbMoiRSeokDnQRchFT6nAb", "source_type": "docx", "n_chars": 89, "text": "Rules1234Causes0 <= f <= tFTT1 <= r <= tFTTr <= fFTEffectsreturn valueFFFT"}
{"id": "docx::PWocwsbMoiRSeokDnQRchFT6nAb::2039", "page_id": "docx::PWocwsbMoiRSeokDnQRchFT6nAb", "title": "课本例题", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课本例题", "section": "`🌟 premium()`", "url": "https://a1npn29y3xu.feishu.cn/wiki/PWocwsbMoiRSeokDnQRchFT6nAb", "source_type": "docx", "n_chars": 631, "text": "Page 79 - 101\n\n\n\n```Java\npublic int premium(int age, char gender, boolean married) {\n int premium;\n if ((age 65) || (gender != 'M' && gender != 'F')) {\n premium = 0;\n } else {\n premium = 500;\n if ((age < 25) && (gender == 'M') && (!married)) {\n premium += 1500;\n } else {\n if (married || gender == 'F')\n premium -= 200;\n if ((age >= 45) && (age <= 65))\n premium -= 100;\n }\n }\n return premium;\n }\n```"}
{"id": "docx::PWocwsbMoiRSeokDnQRchFT6nAb::2040", "page_id": "docx::PWocwsbMoiRSeokDnQRchFT6nAb", "title": "课本例题", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课本例题", "section": "`🌟 class CarTax`", "url": "https://a1npn29y3xu.feishu.cn/wiki/PWocwsbMoiRSeokDnQRchFT6nAb", "source_type": "docx", "n_chars": 699, "text": "Page 113 - 127\n\n```Java\nclass CarTax {\n\n private boolean valid;\n private int yearOfManufacture;\n private int co2Pollution;\n private int tax;\n\n CarTax(int year) {\n if (year>=1900) {\n valid = true;\n yearOfManufacture = year;\n } else\n valid = false;\n co2Pollution = -1000;\n tax = -1;\n }\n\n public void setCO2(int rating) {\n if (valid)\n co2Pollution = rating * 1000;\n }\n\n public int getCO2() {\n return co2Pollution / 1000;\n }\n\n public int getManufactureYear() {\n if (valid)\n return yearOfManufacture;\n else\n return -1;\n }\n\n public int readAndZeroTax() {\n int temp = tax;\n tax = 0;"}
{"id": "docx::PWocwsbMoiRSeokDnQRchFT6nAb::2041", "page_id": "docx::PWocwsbMoiRSeokDnQRchFT6nAb", "title": "课本例题", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课本例题", "section": "`🌟 class CarTax`", "url": "https://a1npn29y3xu.feishu.cn/wiki/PWocwsbMoiRSeokDnQRchFT6nAb", "source_type": "docx", "n_chars": 393, "text": "lse\n return -1;\n }\n\n public int readAndZeroTax() {\n int temp = tax;\n tax = 0;\n return temp;\n }\n\n public int calculateTax(boolean newSystem) {\n if (valid)\n if ( (yearOfManufacture2010) && (newSystem) ) )\n if (newSystem)\n tax = 10 * (co2Pollution/1000);\n else\n tax = 3000;\n return tax;\n }\n}\n```"}
{"id": "docx::IutWwAKNSiiHobkZeSocluujnph::2042", "page_id": "docx::IutWwAKNSiiHobkZeSocluujnph", "title": "课本原文 Chapter 11 ~ 13", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/课本原文 Chapter 11 ~ 13", "section": "课本原文 Chapter 11 \\~ 13", "url": "https://a1npn29y3xu.feishu.cn/wiki/IutWwAKNSiiHobkZeSocluujnph", "source_type": "docx", "n_chars": 682, "text": "\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::IutWwAKNSiiHobkZeSocluujnph::2043", "page_id": "docx::IutWwAKNSiiHobkZeSocluujnph", "title": "课本原文 Chapter 11 ~ 13", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/课本原文 Chapter 11 ~ 13", "section": "课本原文 Chapter 11 \\~ 13", "url": "https://a1npn29y3xu.feishu.cn/wiki/IutWwAKNSiiHobkZeSocluujnph", "source_type": "docx", "n_chars": 668, "text": "ishu.cn/file/ULTybTFgCoCSGQxky6dcaXj5nDe)\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::IutWwAKNSiiHobkZeSocluujnph::2044", "page_id": "docx::IutWwAKNSiiHobkZeSocluujnph", "title": "课本原文 Chapter 11 ~ 13", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/课本原文 Chapter 11 ~ 13", "section": "课本原文 Chapter 11 \\~ 13", "url": "https://a1npn29y3xu.feishu.cn/wiki/IutWwAKNSiiHobkZeSocluujnph", "source_type": "docx", "n_chars": 668, "text": "ishu.cn/file/ZBZPbxHHcoBiW7xtyDec2EKLnkd)\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::IutWwAKNSiiHobkZeSocluujnph::2045", "page_id": "docx::IutWwAKNSiiHobkZeSocluujnph", "title": "课本原文 Chapter 11 ~ 13", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/课本原文 Chapter 11 ~ 13", "section": "课本原文 Chapter 11 \\~ 13", "url": "https://a1npn29y3xu.feishu.cn/wiki/IutWwAKNSiiHobkZeSocluujnph", "source_type": "docx", "n_chars": 668, "text": "ishu.cn/file/CFWYbnx1fojbl7xQW4Cco3fcnme)\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::IutWwAKNSiiHobkZeSocluujnph::2046", "page_id": "docx::IutWwAKNSiiHobkZeSocluujnph", "title": "课本原文 Chapter 11 ~ 13", "course": "3.5➡️3.0 软件项目管理 / IT Project Management", "path": "3.5➡️3.0 软件项目管理 / IT Project Management/课本原文 Chapter 11 ~ 13", "section": "课本原文 Chapter 11 \\~ 13", "url": "https://a1npn29y3xu.feishu.cn/wiki/IutWwAKNSiiHobkZeSocluujnph", "source_type": "docx", "n_chars": 155, "text": "ishu.cn/file/VzFbbSgEso9dhdxeZbDcSNDInWb)\n\n\n\n"}
{"id": "docx::AGDJwuvwjilvq0kNuyqcyvUXnne::2047", "page_id": "docx::AGDJwuvwjilvq0kNuyqcyvUXnne", "title": "课本拾遗", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课本拾遗", "section": "课本拾遗", "url": "https://a1npn29y3xu.feishu.cn/wiki/AGDJwuvwjilvq0kNuyqcyvUXnne", "source_type": "docx", "n_chars": 677, "text": "\n\nA study by Hewlett Packard on the frequency of occurrence of various fault types, found that 50% of the faults were either Algorithmic or Computation and Precision.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::AGDJwuvwjilvq0kNuyqcyvUXnne::2048", "page_id": "docx::AGDJwuvwjilvq0kNuyqcyvUXnne", "title": "课本拾遗", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课本拾遗", "section": "课本拾遗", "url": "https://a1npn29y3xu.feishu.cn/wiki/AGDJwuvwjilvq0kNuyqcyvUXnne", "source_type": "docx", "n_chars": 668, "text": "ishu.cn/file/DhgXb60LPocKgTxNQbLc6Rv3nof)\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n"}
{"id": "docx::AGDJwuvwjilvq0kNuyqcyvUXnne::2049", "page_id": "docx::AGDJwuvwjilvq0kNuyqcyvUXnne", "title": "课本拾遗", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/回归课本/课本拾遗", "section": "课本拾遗", "url": "https://a1npn29y3xu.feishu.cn/wiki/AGDJwuvwjilvq0kNuyqcyvUXnne", "source_type": "docx", "n_chars": 539, "text": "ishu.cn/file/A2KJbxNXOoGjSmx5yFjcmXtLnfh)\n\n\n\n\n\n\n\n\n\n\n\n**IEEE** Testing is “The activity in which a system or component is executed under specified conditions, the results are observed or recorded, and an evaluation is made of some aspect of the system or component."}
{"id": "pdf::Ch0 Course_Overview::2050", "page_id": "pdf::Ch0 Course_Overview", "title": "Ch0 Course_Overview.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch0 Course_Overview.pdf", "section": "Ch0 Course_Overview.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/AaUlw3ntgi5qCPkN0mecdUtbnHH", "source_type": "pdf", "n_chars": 652, "text": "Software Testing and Maintenance\nYanxia Liu cslyx@scut.edu.cn\nSpring, 2025\n1\n\nINTRODUCTION\nØSoftware Testing is a critical element of developing quality software systems \nØIt is a systematic approach to judge quality and discover bugs\nØThis course presents the theory and practice of software testing and \nMaintenance\nØTopics covered include:\n§ Black-box and white-box testing, and related test case generation\n§ Testing team and testing documentation\n§ Testing in the Software Process\n§ Performance testing basics\n§ Tools for software testing\n2\n\nCOURSE OBJECTIVES\nØUnderstand the concepts and theory related to software testing and quality \nassurance"}
{"id": "pdf::Ch0 Course_Overview::2051", "page_id": "pdf::Ch0 Course_Overview", "title": "Ch0 Course_Overview.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch0 Course_Overview.pdf", "section": "Ch0 Course_Overview.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/AaUlw3ntgi5qCPkN0mecdUtbnHH", "source_type": "pdf", "n_chars": 692, "text": "OBJECTIVES\nØUnderstand the concepts and theory related to software testing and quality \nassurance\nØUnderstand the relationship between black-box and white-box testing, and \nknow how to apply as appropriate\nØUnderstand different testing techniques and process used for developingtest \ncases and evaluating test adequacy\nØLearn to use automated testing tools efficiently and effectively\nØUnderstand current state of software testing and maintenance\n3\n\nGRADING\nØDaily performance (40%)\nØClass attendance (10%)\nØQuiz & Assignments (10%)\nØExperiments（20%）\n§ Black Box -test case design\n§ White Box -test case design\n§ Automated functional testing\n§ Automated Performance testing\nØFinal Exam (60%)"}
{"id": "pdf::Ch0 Course_Overview::2052", "page_id": "pdf::Ch0 Course_Overview", "title": "Ch0 Course_Overview.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch0 Course_Overview.pdf", "section": "Ch0 Course_Overview.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/AaUlw3ntgi5qCPkN0mecdUtbnHH", "source_type": "pdf", "n_chars": 693, "text": "-test case design\n§ Automated functional testing\n§ Automated Performance testing\nØFinal Exam (60%)\nPenalties for Cheating\nIf you cheat in this class, you will fail the class.\n4\n\nTEXTBOOK\nØSoftware Testing Principles and Practice\n Second Edition, English language\n S. Brown, J. Timoney, T. Lysaght and D. Ye\n China Machine Press, 2019\n§ The book is developed over ten years and reflects the \nexperience in industry and lecturing from authors;\n§ The book is the results of extracting and interpreting \ntest techniques from a wide classic books and standards.\n§ By providing extensive worked examples, the book \naims to provide a solid basis for both understanding and"}
{"id": "pdf::Ch0 Course_Overview::2053", "page_id": "pdf::Ch0 Course_Overview", "title": "Ch0 Course_Overview.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch0 Course_Overview.pdf", "section": "Ch0 Course_Overview.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/AaUlw3ntgi5qCPkN0mecdUtbnHH", "source_type": "pdf", "n_chars": 691, "text": "ding extensive worked examples, the book \naims to provide a solid basis for both understanding and \napplying various test techniques\n5\n\nCONTENTS\nØSoftware Testing Principles and Practice\n1.Introduction to Software Testing (Chapter 1)\n2.Testing in the software Process (Chapter 9)\n3.Black-Box Testing (Chapter 2&3)\n4.White-Box Testing (Chapter 2&3)\n5.Test Team & Test Documentation \n6.Unit Testing (Chapter 3,4&5)\n7.Integration Testing (Chapter 6)\n8.System Testing (Chapter 7)\n9.Software Test Automation (Chapter 8)\n10.Software Maintenance \n6\n\nREFERENCES"}
{"id": "pdf::Ch0 Course_Overview::2054", "page_id": "pdf::Ch0 Course_Overview", "title": "Ch0 Course_Overview.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch0 Course_Overview.pdf", "section": "Ch0 Course_Overview.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/AaUlw3ntgi5qCPkN0mecdUtbnHH", "source_type": "pdf", "n_chars": 539, "text": "(Chapter 7)\n9.Software Test Automation (Chapter 8)\n10.Software Maintenance \n6\n\nREFERENCES\nØMOOC Course- Software Testing\n NanjingUniversity , Zhenyu Chen （https://www.mooctest.net/）\n7\n\nREFERENCES\nSoftware Testing \nSecond Edition, Ron Patton\nChina Machine Press, 2006\nIntroduction to Software Testing \nSecond Edition, Paul Ammann&Jeff Offutt\nCambridge University Press, 2018\nHowGoogleTestSoftware \n James,Whittaker Jason,Arbon Jeff,Carollo\n Postsand Telecommunications Press, 2016\nhttp://www.cs.gmu.edu/~offutt/softwaretest/ 8"}
{"id": "pdf::Ch1-1 Introduction::2055", "page_id": "pdf::Ch1-1 Introduction", "title": "Ch1-1 Introduction.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch1-1 Introduction.pdf", "section": "Ch1-1 Introduction.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Rf2HwlwE8iBmMOkWf2ycOn3snze", "source_type": "pdf", "n_chars": 690, "text": "Introduction to Software Testing\nYanxia Liu cslyx@scut.edu.cn\nSpring, 2025\n1\n\nContents\nØWhy do we test software? \n§1.1 What is software?\n§1.2 What is bug?\n§1.3 Fault, Error and Failure\n§1.4Adverse Effects of Faulty Software\nØThe theory of Testing \n§2.1 Verification and Validation\n§2.2 Goals of Testing Software\n2\n\nContents\nØWhy do we test software? \n§1.1 What is software?\n§1.2 What is bug?\n§1.3 Fault, Error and Failure\n§1.4Adverse Effects of Faulty Software\n3\n\n1.1 What is Software ?\nØA software system usually consists of a number of : \n§Instructions within separate programs that when executed some desired \nfunction\n§Data structures that enable the programs to adequately manipulate"}
{"id": "pdf::Ch1-1 Introduction::2056", "page_id": "pdf::Ch1-1 Introduction", "title": "Ch1-1 Introduction.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch1-1 Introduction.pdf", "section": "Ch1-1 Introduction.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Rf2HwlwE8iBmMOkWf2ycOn3snze", "source_type": "pdf", "n_chars": 693, "text": "executed some desired \nfunction\n§Data structures that enable the programs to adequately manipulate \ninformation\n§Configuration files which are used to set up these programs\n§System documentation which describes the structure of the system\n§User documentation which explains how to use the system and web sites \nfor users to download recent product information\n4\n\nEarly Days of Software\nØComputer-basedsystems were developed usinghardware-oriented \nmanagement\n§Project managers focused on hardware\n§Project managers applied the controls,methods, and tools that we \nrecognize ashardware engineering\nØProgramming was viewed as an art form\n§The programmer often learned his craft bytrial and error"}
{"id": "pdf::Ch1-1 Introduction::2057", "page_id": "pdf::Ch1-1 Introduction", "title": "Ch1-1 Introduction.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch1-1 Introduction.pdf", "section": "Ch1-1 Introduction.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Rf2HwlwE8iBmMOkWf2ycOn3snze", "source_type": "pdf", "n_chars": 668, "text": "ng\nØProgramming was viewed as an art form\n§The programmer often learned his craft bytrial and error\n§The software world was undisciplined\n5\n\nSoftwarein the 21st Century\nØSoftware defines behavior\n§Servers, Storage, Network routers, Switching networks, other Infrastructure\nØToday’s software market :\n§much bigger\n§more competitive\n§more users\nØEmbedded Control Applications\n§Airplanes, air traffic control\n§Spaceships\n§Watches\n§Ovens\n§Remote Controllers\nØAgile processes put increased pressure on testers to assure the software quality\n6\nIndustry is going through a \nrevolution in what testing means to \nthe success of software products\n\n7\nQuote due to Dr. Mark Harman"}
{"id": "pdf::Ch1-1 Introduction::2058", "page_id": "pdf::Ch1-1 Introduction", "title": "Ch1-1 Introduction.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch1-1 Introduction.pdf", "section": "Ch1-1 Introduction.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Rf2HwlwE8iBmMOkWf2ycOn3snze", "source_type": "pdf", "n_chars": 644, "text": "volution in what testing means to \nthe success of software products\n\n7\nQuote due to Dr. Mark Harman\nSoftware is a Skin that Surrounds Our Civilization\n\nØThere are risks associated with Software Development\n§Modern programs are complex and have tenthousands of lines of code\n§The customer’s requirements can be vague, lacking in exactness\n§Deadlines and budgets put pressure on the development team\nØThe combination of these factors can lead to a lack emphasis being placed on \nthe final quality of the software product\n§Poor quality can result in software failure resulting in high maintenance costs and long \ndelays before the final deployment"}
{"id": "pdf::Ch1-1 Introduction::2059", "page_id": "pdf::Ch1-1 Introduction", "title": "Ch1-1 Introduction.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch1-1 Introduction.pdf", "section": "Ch1-1 Introduction.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Rf2HwlwE8iBmMOkWf2ycOn3snze", "source_type": "pdf", "n_chars": 677, "text": "n software failure resulting in high maintenance costs and long \ndelays before the final deployment\n§The impact on the business can be loss of reputation, legal claims, decrease in market \nshare\nQuality and Software\n8\n\nØThe International Standard can provide \n§support for setting quality goals \n§support for design review, verification and validation.\nØThe International Standard \n1) A quality in use model composed of five characteristics\n2) A product quality model composed of eight characteristics (which are further subdivided into \nsubcharacteristics) \nØBe applicable to all software products and computer systems\nISO/IEC 25010:2011 System and software quality models\n9"}
{"id": "pdf::Ch1-1 Introduction::2060", "page_id": "pdf::Ch1-1 Introduction", "title": "Ch1-1 Introduction.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch1-1 Introduction.pdf", "section": "Ch1-1 Introduction.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Rf2HwlwE8iBmMOkWf2ycOn3snze", "source_type": "pdf", "n_chars": 663, "text": "l software products and computer systems\nISO/IEC 25010:2011 System and software quality models\n9\n\n1) Quality in use 2）Product Quality\n10\n\n\nContents\nØWhy do we test software? \n§1.1 What is software?\n§1.2 What is bug?\n§1.3 Fault, Error and Failure\n§1.4Adverse Effects of Faulty Software\n11\n\n1.2 What is Bug ?\nØWhat is your understanding for Bug?\nØBugs a.k.a. … §Defect\n§Fault\n§Problem\n§Error\n§Incident\n§Anomaly\n§Variance\n§Failure\n§Inconsistency\n§Product \nAnomaly\n§Product \nIncidence\n§Feature :-)\nThe term Bug is used informally \n12\n\nWhere is Bug from ?\nØBug story (03:35 min)\nØIn 1947 Grace Hopper was operating a room-sized computer"}
{"id": "pdf::Ch1-1 Introduction::2061", "page_id": "pdf::Ch1-1 Introduction", "title": "Ch1-1 Introduction.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch1-1 Introduction.pdf", "section": "Ch1-1 Introduction.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Rf2HwlwE8iBmMOkWf2ycOn3snze", "source_type": "pdf", "n_chars": 690, "text": "tory (03:35 min)\nØIn 1947 Grace Hopper was operating a room-sized computer \ncalled the Mark II in Harvard University .\n§mechanical relays \n§glowing vacuum tubes\n§technicians program the computer by reconfiguring it \n§Technicians had to change the occasional vacuum tube.\nØA moth flew into the computer and was zapped by the high \nvoltage when it landed on a relay.\nHence, the first computer bug!\n13\n\nWhere is Bug from ?\nØGrace Hopper (01:15min)\n§Distinguished Mathematician and computer scientist \n§Rear Admiral in the U.S. Navy\n§”Thefirst Lady of Software ”\nDec.9,1906 ~ Jan.1,1992\nGrace Hopper and the Invention \nof the Information Age\nØPrograming Accomplishments"}
{"id": "pdf::Ch1-1 Introduction::2062", "page_id": "pdf::Ch1-1 Introduction", "title": "Ch1-1 Introduction.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch1-1 Introduction.pdf", "section": "Ch1-1 Introduction.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Rf2HwlwE8iBmMOkWf2ycOn3snze", "source_type": "pdf", "n_chars": 624, "text": "06 ~ Jan.1,1992\nGrace Hopper and the Invention \nof the Information Age\nØPrograming Accomplishments \n§Discovered the first Bug\n§Created the biggest Bug - Y2K\n§Created the first Compiler A-0for computer languages\n§Developed the first commercial programming language\n COBOL(Common Business-Oriented Language) \n§Defined the model for high-level programming languages\n \n14\n\nØGrace Hopper\n§ Encouraging young people to learn how to program\nØ The Grace Hopper Celebration (GHC )\n§The world’slargestconferenceofwomenin technology\nWhere is Bug from ?\nØQuotes\n“People have an enormous tendency to resist change. They love to say,"}
{"id": "pdf::Ch1-1 Introduction::2063", "page_id": "pdf::Ch1-1 Introduction", "title": "Ch1-1 Introduction.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch1-1 Introduction.pdf", "section": "Ch1-1 Introduction.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Rf2HwlwE8iBmMOkWf2ycOn3snze", "source_type": "pdf", "n_chars": 666, "text": "Where is Bug from ?\nØQuotes\n“People have an enormous tendency to resist change. They love to say, \n'We've always done it this way.' I try to fight that.” —Grace Hopper\n“Compiling in '51, nobody believed that. I had a running compiler and \nnobody would touch it, because, they carefully told me, computers \ncould only do arithmetic, they could not write programs. It was a \nselling job to get people to try it.” —Grace Hopper\n“I tell everybody, 'Go ahead and do it. You can always apologize later.’” —Grace Hopper\n15\n\nContents\nØWhy do we test software? \n§1.1 What is software?\n§1.2 What is bug?\n§1.3 Fault, Error and Failure"}
{"id": "pdf::Ch1-1 Introduction::2064", "page_id": "pdf::Ch1-1 Introduction", "title": "Ch1-1 Introduction.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch1-1 Introduction.pdf", "section": "Ch1-1 Introduction.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Rf2HwlwE8iBmMOkWf2ycOn3snze", "source_type": "pdf", "n_chars": 657, "text": "s\nØWhy do we test software? \n§1.1 What is software?\n§1.2 What is bug?\n§1.3 Fault, Error and Failure\n§1.4Adverse Effects of Faulty Software\n16\n\nSoftware Fault : A static defect in the software\nSoftware Failure : External, incorrect behavior with respect to the requirements \nor other description of the expected behavior\nSoftware Error : An incorrect internal state that is the manifestation of some fault\n1.3 Fault, Error and Failure\nØ Use Terms that have precise, defined, and unambiguous meanings\nSometimes bug mean fault, sometimes error, sometimes failure \n… often the speaker doesn’t know what it means !\n17\n\nA patient gives a doctor a list of symptom"}
{"id": "pdf::Ch1-1 Introduction::2065", "page_id": "pdf::Ch1-1 Introduction", "title": "Ch1-1 Introduction.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch1-1 Introduction.pdf", "section": "Ch1-1 Introduction.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Rf2HwlwE8iBmMOkWf2ycOn3snze", "source_type": "pdf", "n_chars": 695, "text": "ow what it means !\n17\n\nA patient gives a doctor a list of symptom \nThe doctor tries to diagnose the root cause, the ailment \nThe doctor may look for anomalous internal conditions\n (high blood pressure, irregular heartbeat, bacteria in the blood stream)\nFaults, Errors and Failures Example\nDifference : \nMost medical problems result from external attacks (bacteria, viruses) or physical degradation as we age.\nSoftware faults were there at the beginning and do not “appear” when a part wears out.\nFailure\nFault\nErrors\nFaults in software are equivalent to design mistakes in hardware\n.\n18\n\nA Concrete Example\n19\npublic static int numZero (int [ ] arr)"}
{"id": "pdf::Ch1-1 Introduction::2066", "page_id": "pdf::Ch1-1 Introduction", "title": "Ch1-1 Introduction.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch1-1 Introduction.pdf", "section": "Ch1-1 Introduction.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Rf2HwlwE8iBmMOkWf2ycOn3snze", "source_type": "pdf", "n_chars": 679, "text": "to design mistakes in hardware\n.\n18\n\nA Concrete Example\n19\npublic static int numZero (int [ ] arr)\n{ // Effects: If arr is null throw NullPointerException\n // else return the number of occurrences of 0 in arr\n int count = 0;\n for (int i = 1; i < arr.length; i++)\n {\n if (arr [ i ] == 0)\n {\n count++;\n }\n }\n return count;\n}\nFault: Should start \nsearching at 0, not 1\nTe s t 1\n[ 2, 7, 0 ]\nExpected: 1\nActual: 1\nTe s t 2\n[ 0, 2, 7 ]\nExpected: 1\nActual: 0\nError: i is 1, not 0, on \nthe first iteration\nFailure: none\nError: i is 1, not 0\nError propagates to the variable count\nFailure: count is 0 at the return statement\n\nExecution/Reachability:"}
{"id": "pdf::Ch1-1 Introduction::2067", "page_id": "pdf::Ch1-1 Introduction", "title": "Ch1-1 Introduction.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch1-1 Introduction.pdf", "section": "Ch1-1 Introduction.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Rf2HwlwE8iBmMOkWf2ycOn3snze", "source_type": "pdf", "n_chars": 629, "text": "pagates to the variable count\nFailure: count is 0 at the return statement\n\nExecution/Reachability: \nThe location or locations in the program that contain the faults must be reached\nInfection: \nThe state of the program must be incorrect\nPropagation : \nThe infected state must propagate to cause some output of the program to be \nincorrect .\nPIE Model\nA test may not execute the location of the fault !\nA test executing the fault may not produce an error!\nAn error may not be propagate to the output !\n20\n\nPIE Model\n§Execution \n§Infection \n§Propagation \nDiscussion:"}
{"id": "pdf::Ch1-1 Introduction::2068", "page_id": "pdf::Ch1-1 Introduction", "title": "Ch1-1 Introduction.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch1-1 Introduction.pdf", "section": "Ch1-1 Introduction.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Rf2HwlwE8iBmMOkWf2ycOn3snze", "source_type": "pdf", "n_chars": 668, "text": "§Infection \n§Propagation \nDiscussion: \nCould you construct a simple program P (with a fault) and 3 tests , s.t.\n1)T1 executes the fault , but no error;\n2)T2 executes the fault and produces an error, but no failure;\n3)T3 produces a failure.\n§Fault\n§Error\n§Failure\n21\n\nAnother Concrete Example\n22\npublic static double computeMean (int [ ] arr)\n{ // Effects: If arr is null throw NullPointerException\n // else return the mean of arr\n int length = arr. length -1 ;\n double mean,sum;\n sum = 0.0;\n for (int i = 0; i < length; i++)\n {\n sum += numbers [i]\n }\n mean = sum/(double)length\n return mean;\n}"}
{"id": "pdf::Ch1-1 Introduction::2069", "page_id": "pdf::Ch1-1 Introduction", "title": "Ch1-1 Introduction.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch1-1 Introduction.pdf", "section": "Ch1-1 Introduction.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Rf2HwlwE8iBmMOkWf2ycOn3snze", "source_type": "pdf", "n_chars": 683, "text": "length; i++)\n {\n sum += numbers [i]\n }\n mean = sum/(double)length\n return mean;\n}\nFault: Should be set \n“arr.length”\nTe s t 3\n[ 3, 4, 5 ]\nExpected: 4\nActual: 3.5\nTe s t 1\n[ 3, -3, 0 ]\nExpected: 0 \nActual: 0\nError: sum is 7, not 12\nError propagates to mean\nFailure: wrong mean 3.5\nNO Error: sum is 0\nNO Failure \nTe s t 2\n[ 3, 5, 4 ]\nExpected: 4 \nActual: 4\nError: sum is 8. not 12\nNO Failure \n\nContents\nØWhy do we test software? \n§1.1 What is software?\n§1.2 What is bug?\n§1.3 Fault, Error and Failure\n§1.4Adverse Effects of Faulty Software\n23\n\n1.4Software Faults -Categories\nAlgorithmicfaults\nAlgorithmicfaultsaretheonesthatoccurswhenaunitofthesoftwaredoes"}
{"id": "pdf::Ch1-1 Introduction::2070", "page_id": "pdf::Ch1-1 Introduction", "title": "Ch1-1 Introduction.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch1-1 Introduction.pdf", "section": "Ch1-1 Introduction.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Rf2HwlwE8iBmMOkWf2ycOn3snze", "source_type": "pdf", "n_chars": 639, "text": "aults -Categories\nAlgorithmicfaults\nAlgorithmicfaultsaretheonesthatoccurswhenaunitofthesoftwaredoes\nnotproduceacorrect outputcorrespondingtothegiveninputunderthe\ndesignatedalgorithm\nSyntaxFaults\nTheseoccurwhencodeisnotinconformancetotheprogramminglanguage\nspecification,(i.e.sourcecodecompiledafewyearsbackwitholder\nversionsofcompilersmayhavesyntaxthatdoesnotconformtopresent\nsyntaxcheckingbycompilers(becauseofstandardsconformity).\n24\n\nSoftware Faults -Categories\nDocumentationfaults\n IncompleteorincorrectdocumentationwillleadtoDocumentationfaults\nStressoroverloadfaults\n StressorOverloadfaultshappenswhendatastructuresarefilledpasttheir"}
{"id": "pdf::Ch1-1 Introduction::2071", "page_id": "pdf::Ch1-1 Introduction", "title": "Ch1-1 Introduction.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch1-1 Introduction.pdf", "section": "Ch1-1 Introduction.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Rf2HwlwE8iBmMOkWf2ycOn3snze", "source_type": "pdf", "n_chars": 695, "text": "ionfaults\nStressoroverloadfaults\n StressorOverloadfaultshappenswhendatastructuresarefilledpasttheir\nspecificcapacitywhereasthesystemcharacteristicsaredesignedtohandleno\nmorethanamaximumloadplannedundertherequirements\nCapacityandboundaryfaults\n CapacityorBoundaryfaultsoccurwhenthesystemproducesanunacceptable\nperformancebecausethesystemactivitymayreachitsspecifiedlimitdueto\noverload\nComputationandprecisionfaults\n ComputationandPrecisionfaultsoccurwhenthecalculatedresultusingthe\nchosenformuladoesnotconfirmtotheexpectedaccuracyorprecision 25\n\nSoftware Faults -Categories\nThroughputorperformancefaults\nThisiswhenthedevelopedsystemdoesnotperformatthespeedspecified\nunderthestipulatedrequirements"}
{"id": "pdf::Ch1-1 Introduction::2072", "page_id": "pdf::Ch1-1 Introduction", "title": "Ch1-1 Introduction.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch1-1 Introduction.pdf", "section": "Ch1-1 Introduction.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Rf2HwlwE8iBmMOkWf2ycOn3snze", "source_type": "pdf", "n_chars": 681, "text": "faults\nThisiswhenthedevelopedsystemdoesnotperformatthespeedspecified\nunderthestipulatedrequirements\nRecoveryfaults\nThishappenswhenthesystemdoesnotrecovertotheexpectedperformance\nevenafterafaultisdetectedandcorrected\nTimingorcoordinationfaults\nThesearetypicalofrealtimesystemswhentheprogrammingandcodingare\nnotcommensuratetomeettheco-ordinationofseveralconcurrentprocesses\norwhentheprocesseshavetobeexecutedinacarefullydefinedsequence\n26\n\nSoftware Faults -Categories\nStandardsandProcedureFaults\nStandardsandProcedurefaultsoccurwhenateammemberdoesnotfollow\nthestandardsdeployedbytheorganizationwhichwillleadtotheproblemof\nothermembershavingtounderstandthelogicemployedortofindthedata"}
{"id": "pdf::Ch1-1 Introduction::2073", "page_id": "pdf::Ch1-1 Introduction", "title": "Ch1-1 Introduction.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch1-1 Introduction.pdf", "section": "Ch1-1 Introduction.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Rf2HwlwE8iBmMOkWf2ycOn3snze", "source_type": "pdf", "n_chars": 651, "text": "ganizationwhichwillleadtotheproblemof\nothermembershavingtounderstandthelogicemployedortofindthedata\ndescriptionneededforsolvingaproblem.\n27\n\nSoftware Faults \nØA study by HewlettPackard on thefrequency ofoccurrence of various\nfault types, found that50% of the faultswere eitherAlgorithmic or\nComputation andPrecision\n28\n\nSoftware Failures\nØFailures can be classified by their severity\nLevel 1. Failure causes a system crash and the recovery time is extensive; or \nfailure causes a loss of function and data and there is no workaround\nLevel 2. Failure causes a loss of function or data but there is manual workaround \nto temporarily accomplish the tasks"}
{"id": "pdf::Ch1-1 Introduction::2074", "page_id": "pdf::Ch1-1 Introduction", "title": "Ch1-1 Introduction.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch1-1 Introduction.pdf", "section": "Ch1-1 Introduction.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Rf2HwlwE8iBmMOkWf2ycOn3snze", "source_type": "pdf", "n_chars": 698, "text": "uses a loss of function or data but there is manual workaround \nto temporarily accomplish the tasks\nLevel 3. Failure causes a partial loss of function or data where user can \naccomplish most of the tasks with a small amount of workaround\nLevel 4. Failure causes cosmetic and minor inconveniences where all the user \ntasks can still be accomplished\n29\n\nAdverse Effects of Faulty Software\nØCommunications: Loss or corruption of communication media, non delivery of data.\nØSpace Applications: Lost lives, launch delays.\nØDefense and Warfare: Misidentification of friend or foe.\nØTransportation: Deaths, delays, sudden acceleration, inability to brake.\nØSafety-critical Applications: Death, injuries."}
{"id": "pdf::Ch1-1 Introduction::2075", "page_id": "pdf::Ch1-1 Introduction", "title": "Ch1-1 Introduction.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch1-1 Introduction.pdf", "section": "Ch1-1 Introduction.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Rf2HwlwE8iBmMOkWf2ycOn3snze", "source_type": "pdf", "n_chars": 696, "text": "s, delays, sudden acceleration, inability to brake.\nØSafety-critical Applications: Death, injuries.\nØElectric Power: Death, injuries, power outages, long-term health hazards (radiation).\nØMoney Management: Fraud, violation of privacy, shutdown of stock exchanges and banks, \n negative interest rates.\nØControl of Jails: Technology-aided escape attempts and successes, accidental release of \n inmates, failures in software controlled locks.\nØ……. 30\n\nSpectacular Software Failures\n31\nIntel’s Pentium FDIV fault : Public relations \nnightmare\nTHERAC-25 radiation machine : 2000, Poor \ntesting of safety-critical software can cost lives : \n3 patients were killed\nMars Polar\nLander crash\nsite?"}
{"id": "pdf::Ch1-1 Introduction::2076", "page_id": "pdf::Ch1-1 Introduction", "title": "Ch1-1 Introduction.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch1-1 Introduction.pdf", "section": "Ch1-1 Introduction.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Rf2HwlwE8iBmMOkWf2ycOn3snze", "source_type": "pdf", "n_chars": 672, "text": "of safety-critical software can cost lives : \n3 patients were killed\nMars Polar\nLander crash\nsite?\nTHERAC-25 design\nAriane 5:\nexception-handling\nbug : forced self\ndestruct on maiden\nflight (64-bit to 16-bit\nconversion: about\n370 million $ lost)\nWe need our software to be\n \ndependable\nTe s t i n g i s \none\n \nway to assess dependability\nNASA’s Mars lander: September 1999, crashed \ndue to a units integration fault\nAriane 5 explosion : Millions of $$\n\nSpectacular software Failures\n32\nØHealthcare website : Crashed repeatedly \non launch—never load tested\nSoftware testers try to find faults before the faults find users\nØBoeing A220 : Engines failed after software"}
{"id": "pdf::Ch1-1 Introduction::2077", "page_id": "pdf::Ch1-1 Introduction", "title": "Ch1-1 Introduction.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch1-1 Introduction.pdf", "section": "Ch1-1 Introduction.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Rf2HwlwE8iBmMOkWf2ycOn3snze", "source_type": "pdf", "n_chars": 588, "text": "ters try to find faults before the faults find users\nØBoeing A220 : Engines failed after software \nupdate allowed excessive vibrations\nØToyota brakes : Dozens dead, thousands of crashes\nØNortheast blackout : 50 million people, $6 \nbillion USD lost … alarm system failed\nØBoeing 737 Max : Crashed due to overly \naggressive software flight overrides (MCAS)\n\n\nWhat Does This Mean?\n34\nSoftware testing is getting more important\nWhat are we trying to do when we test ?\nWhat are our goals ?\n\nDiscussion\nØHave you heard of other faulty software ?\n \n§In the media?\n§From personal experience?\n35"}
{"id": "pdf::Ch1-2 Introduction::2078", "page_id": "pdf::Ch1-2 Introduction", "title": "Ch1-2 Introduction.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch1-2 Introduction.pdf", "section": "Ch1-2 Introduction.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/H7Xtwgn6BiqoS4kZM5ycjjQEnah", "source_type": "pdf", "n_chars": 672, "text": "Introduction to Software Testing\nYanxia Liu cslyx@scut.edu.cn\nSpring, 2025\n1\n\nContents\n Why do we test software? \n 1.1 What is software?\n 1.2 What is bug?\n 1.3 Fault, Error and Failure\n 1.4 Adverse Effects of Faulty Software\n The theory of Testing \n 2.1 Verification and Validation\n 2.2 Software Testing Axioms\n 2.3 Goals of a Software Tester\n2\n\nContents\n The theory of Testing \n 2.1 Verification and Validation\n 2.2 Software Testing Axioms\n 2.3 Goals of a Software Tester\n3\n\n Verification : The process of determining whether the products of a given \nphase of the software development process fulfill the requirements \nestablished during the previous phase"}
{"id": "pdf::Ch1-2 Introduction::2079", "page_id": "pdf::Ch1-2 Introduction", "title": "Ch1-2 Introduction.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch1-2 Introduction.pdf", "section": "Ch1-2 Introduction.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/H7Xtwgn6BiqoS4kZM5ycjjQEnah", "source_type": "pdf", "n_chars": 668, "text": "of the software development process fulfill the requirements \nestablished during the previous phase\n Validation : The process of evaluating software at the end of software \ndevelopment to ensure compliance with intended usage\n• IV&V stands for “independent verification and validation”\n2.1 Validation & Verification (IEEE)\n\n5\nValidation & Verification (IEEE)\n\n6\n Specifications play a key role. \n Detailed specifications provide the correct behavior of the software.\n They must describe normal and error behavior.\nSpecifications\n\n7\nValidation & Verification (IEEE)\n\nContents\n The theory of Testing \n 2.1 Verification and Validation\n 2.2 Software Testing Axioms"}
{"id": "pdf::Ch1-2 Introduction::2080", "page_id": "pdf::Ch1-2 Introduction", "title": "Ch1-2 Introduction.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch1-2 Introduction.pdf", "section": "Ch1-2 Introduction.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/H7Xtwgn6BiqoS4kZM5ycjjQEnah", "source_type": "pdf", "n_chars": 669, "text": "Contents\n The theory of Testing \n 2.1 Verification and Validation\n 2.2 Software Testing Axioms\n 2.3 Goals of a Software Tester\n8\n\n9\n2.2 Software Testing Axioms\n1. It is impossible to test a program completely.\n2. Software testing is a risk-based exercise.\n3. Testing cannot show the absence of bugs.\n4. The more bugs you find, the more bugs there are.\n5. Not all bugs found will be fixed.\n6. It is difficult to say when a bug is indeed a bug.\n7. Specifications are never final.\n8. Software testers are not the most popular members of a project.\n9. Software testing is a disciplined and technical profession.\n\n10\nAxiom 1 It is impossible to test a program completely"}
{"id": "pdf::Ch1-2 Introduction::2081", "page_id": "pdf::Ch1-2 Introduction", "title": "Ch1-2 Introduction.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch1-2 Introduction.pdf", "section": "Ch1-2 Introduction.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/H7Xtwgn6BiqoS4kZM5ycjjQEnah", "source_type": "pdf", "n_chars": 674, "text": "s a disciplined and technical profession.\n\n10\nAxiom 1 It is impossible to test a program completely\n How many test cases do you need to exhaustively test:\n Powerpoint\n A calculator\n MS Word\n Any interesting software!\n The only way to be absolutely sure software works is to run it against all possible \ninputs and observe all of its outputs …\n Oh, and the specification must be correct and complete\n\n11\nAxiom 1 It is impossible to test a program completely\n The number of possible inputs is very large.\n The number of possible outputs is very large.\n The number of paths through the software is very large.\n The software specification open to interpretation.\n\n\n12"}
{"id": "pdf::Ch1-2 Introduction::2082", "page_id": "pdf::Ch1-2 Introduction", "title": "Ch1-2 Introduction.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch1-2 Introduction.pdf", "section": "Ch1-2 Introduction.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/H7Xtwgn6BiqoS4kZM5ycjjQEnah", "source_type": "pdf", "n_chars": 654, "text": "paths through the software is very large.\n The software specification open to interpretation.\n\n\n12\nAxiom 2 Software testing is a risk-based exercise\nIf you do not test the software for all inputs (a wise choice) \nyou take a risk. Hopefully you will skip a lot of inputs that \nwork correctly.\nWhat if you skip inputs that cause a fault?\n Risk: financial loss, security, loss of money, loss of life!\n That is a lot of pressure for a tester!\nThis course is all about techniques and practices to help \nreduce the risk without breaking the bank.\n\n\n13\nAxiom 3 Testing cannot show the absence of bugs\n“ Program testing can be used to show the presence of"}
{"id": "pdf::Ch1-2 Introduction::2083", "page_id": "pdf::Ch1-2 Introduction", "title": "Ch1-2 Introduction.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch1-2 Introduction.pdf", "section": "Ch1-2 Introduction.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/H7Xtwgn6BiqoS4kZM5ycjjQEnah", "source_type": "pdf", "n_chars": 644, "text": "m 3 Testing cannot show the absence of bugs\n“ Program testing can be used to show the presence of \nbugs, but never to show their absence! ” \n--------Edsger Wybe Dijkstra\nDijkstra received the 1972 ACM Turing Awardfor \nfundamental contributions in the area of programming \nlanguages\n\n\n14\nAxiom 4 The more bugs you find, the more bugs there are\n Bugs appear in groups, where you see one you will likely \nfind more … Why?\n• Programmers can have bad days\n• Programmers tend to make the same mistakes\n• Some bugs are just the tip of the iceberg.\n• Boris Beizer coined the term pesticide paradox to describe"}
{"id": "pdf::Ch1-2 Introduction::2084", "page_id": "pdf::Ch1-2 Introduction", "title": "Ch1-2 Introduction.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch1-2 Introduction.pdf", "section": "Ch1-2 Introduction.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/H7Xtwgn6BiqoS4kZM5ycjjQEnah", "source_type": "pdf", "n_chars": 637, "text": "bugs are just the tip of the iceberg.\n• Boris Beizer coined the term pesticide paradox to describe \nthe phenomenon that the more you test software the more \nimmune it becomes to your test cases.\n• Remedy: continually write new and different tests to exercise \ndifferent parts of the software.\n\n\n15\nAxiom 5 Not all bugs found will be fixed\nWhy wouldn’t you fix a bug you knew about?\n There’s not enough time\no Some deadlines cannot be extended (e.g., Y2K)\n It’s not really a bug\no Specifications can be wrong\n It’s too risky to fix\no “I’m not touching Murphy’s code!”\n It’s just not worth it\no Bugs in fringe features may have to wait"}
{"id": "pdf::Ch1-2 Introduction::2085", "page_id": "pdf::Ch1-2 Introduction", "title": "Ch1-2 Introduction.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch1-2 Introduction.pdf", "section": "Ch1-2 Introduction.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/H7Xtwgn6BiqoS4kZM5ycjjQEnah", "source_type": "pdf", "n_chars": 681, "text": "’m not touching Murphy’s code!”\n It’s just not worth it\no Bugs in fringe features may have to wait\no Why not charge the customer for bug fixes in the next release (sound familiar?) :-)\n\n16\nAxiom 6 It is difficult to say when a bug is indeed a bug\n If there is a problem in the software but no one ever discovers it … is it a bug?\n not programmers, not testers, and not even a single customer\n What is your opinion?\nDoes a bug have to be observable in order for it to me a bug?\n Bugs that are undiscovered are called latent bugs.\n\n17\nAxiom 7 Specifications are never final\n Building a product based on a “moving target” specification is fairly unique \nto software development."}
{"id": "pdf::Ch1-2 Introduction::2086", "page_id": "pdf::Ch1-2 Introduction", "title": "Ch1-2 Introduction.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch1-2 Introduction.pdf", "section": "Ch1-2 Introduction.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/H7Xtwgn6BiqoS4kZM5ycjjQEnah", "source_type": "pdf", "n_chars": 646, "text": "lding a product based on a “moving target” specification is fairly unique \nto software development.\n Competition is fierce\n Very rapid release cycles\n Software is “easy” to change\n Not true in other engineering domains\n E.g., the Brooklyn Bridge could not be adjusted to allow train traffic to cross it once its \nconstruction started.\n\n\n18\nAxiom 8 Software testers are not the most popular members of a project\n Goal of a software tester\n Find bugs\n Find bugs early\n Make sure bugs get fixed\n Tips to avoid becoming unpopular\n Find bugs early\n Temper your enthusiasm … act in a professional manner\n Don’t report just the bad news\n\n19"}
{"id": "pdf::Ch1-2 Introduction::2087", "page_id": "pdf::Ch1-2 Introduction", "title": "Ch1-2 Introduction.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch1-2 Introduction.pdf", "section": "Ch1-2 Introduction.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/H7Xtwgn6BiqoS4kZM5ycjjQEnah", "source_type": "pdf", "n_chars": 694, "text": "early\n Temper your enthusiasm … act in a professional manner\n Don’t report just the bad news\n\n19\nAxiom 9 Software testing is a disciplined and technical profession\n When software was simpler and more manageable software testers \nwere often untrained and testing was not done methodically.\n It is now too costly to build buggy software. As a result testing has \nmatured as a discipline.\n Sophisticated techniques\n Tool support\n Rewarding careers\n\n\nContents\n The theory of Testing \n 2.1 Verification and Validation\n 2.2 Software Testing Axioms\n 2.3 Goals of a Software Tester\n20\n\n21\n2.3 Goals of a Software Tester\nTo identify the ideal test – that is, the minimum test data required to"}
{"id": "pdf::Ch1-2 Introduction::2088", "page_id": "pdf::Ch1-2 Introduction", "title": "Ch1-2 Introduction.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch1-2 Introduction.pdf", "section": "Ch1-2 Introduction.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/H7Xtwgn6BiqoS4kZM5ycjjQEnah", "source_type": "pdf", "n_chars": 145, "text": "Goals of a Software Tester\nTo identify the ideal test – that is, the minimum test data required to\nensure that the software works for all inputs."}
{"id": "pdf::Ch10 StaticTesting::2089", "page_id": "pdf::Ch10 StaticTesting", "title": "Ch10 StaticTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch10 StaticTesting.pdf", "section": "Ch10 StaticTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/LBqWwBf4AiMLsjkjjK4cHKhLnec", "source_type": "pdf", "n_chars": 687, "text": "StaticTesting\nYanxia Liu cslyx@scut.edu.cn\nSpring, 2025\n\nContents\nØStaticTesting\n§Code Review\n§Static ProgramAnalysis\n\n1. Static Testing\nØStatic testing is the process of carefully and methodically reviewing and \nanalyzing the software for bugs without executing it.\n§Code Review\n§Static ProgramAnalysis\nØThis form of testing is very valuable and has advantages over execution-based \ntesting. Reported experience shows that a large number of faults can be found \nusing static testing.\nØThis has benefits in terms of cost and productivity because faults are found \n(and corrected) early on and less time is required for execution-based tests.\n\nExperience of Static Testing\n\n2. Code Review"}
{"id": "pdf::Ch10 StaticTesting::2090", "page_id": "pdf::Ch10 StaticTesting", "title": "Ch10 StaticTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch10 StaticTesting.pdf", "section": "Ch10 StaticTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/LBqWwBf4AiMLsjkjjK4cHKhLnec", "source_type": "pdf", "n_chars": 687, "text": "and less time is required for execution-based tests.\n\nExperience of Static Testing\n\n2. Code Review\nEssential elements of code review\nØIdentify problems:\n§Find problems with the software such as missing items, mistakes, etc.\nØFollow rules:\n§Amount of code to be reviewed, how much time will be spent, etc.\nØPrepare:\n§Each participant should prepare in order to contribute to the review.\nØWrite a report:\n§Summarize the results of the review, make report available to the \ndevelopment team.\n\nInformalCode Review\nØPeer reviews\n§An informal small group of programmers and/or testers act as reviewers.\n§Participants should follow the 4 essential elements even through the review is \ninformal."}
{"id": "pdf::Ch10 StaticTesting::2091", "page_id": "pdf::Ch10 StaticTesting", "title": "Ch10 StaticTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch10 StaticTesting.pdf", "section": "Ch10 StaticTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/LBqWwBf4AiMLsjkjjK4cHKhLnec", "source_type": "pdf", "n_chars": 664, "text": "viewers.\n§Participants should follow the 4 essential elements even through the review is \ninformal.\nØWalkthroughs\n§A more formal process in which the author of the code formally presents the code \nto a small group of programmers and/or testers.\n§The author reads the code line by line explaining what it does, reviewers listen \nand ask questions.\n§Participants should follow the 4 essential elements.\n\nFormalCode Inspections\nØAn inspection is more comprehensive than awalk-through.\n§Code presenter is not the author of the code.\n§The other participants are the inspectors.\n§There is a moderator to assure that the rules are followed and the meeting \nruns smoothly."}
{"id": "pdf::Ch10 StaticTesting::2092", "page_id": "pdf::Ch10 StaticTesting", "title": "Ch10 StaticTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch10 StaticTesting.pdf", "section": "Ch10 StaticTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/LBqWwBf4AiMLsjkjjK4cHKhLnec", "source_type": "pdf", "n_chars": 626, "text": "ctors.\n§There is a moderator to assure that the rules are followed and the meeting \nruns smoothly. \nØAfter the inspection a report is composed. The programmer then makes \nchanges and a re-inspection occurs, if necessary.\nØFormal code inspections are effective at finding bugs in code and designs and \nare gaining in popularity.\n\nCode review checklist: Data reference errors\nØIs an un-initialized variable referenced?\nØAre array subscripts integer values and are they within the array’s bounds?\nØAre there off-by-one errors in indexing operations or references to arrays?\nØIs a variable used where a constant would work better?"}
{"id": "pdf::Ch10 StaticTesting::2093", "page_id": "pdf::Ch10 StaticTesting", "title": "Ch10 StaticTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch10 StaticTesting.pdf", "section": "Ch10 StaticTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/LBqWwBf4AiMLsjkjjK4cHKhLnec", "source_type": "pdf", "n_chars": 656, "text": "ndexing operations or references to arrays?\nØIs a variable used where a constant would work better?\nØIs a variable assigned a value that’s of a different type than the variable?\nØIs memory allocated for referenced pointers?\nØAre data structures that are referenced in different functions defined \nidentically?\n\nCode review checklist: Data declaration errors\nØAre the variables assigned correct length, type, storage class? \n§E.g. should a variable be declared a string instead of an array of \ncharacters?\nØIf a variable is initialized at its declaration, is it properly initialized and \nconsistent with its type?\nØAre there any variable with similar names?"}
{"id": "pdf::Ch10 StaticTesting::2094", "page_id": "pdf::Ch10 StaticTesting", "title": "Ch10 StaticTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch10 StaticTesting.pdf", "section": "Ch10 StaticTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/LBqWwBf4AiMLsjkjjK4cHKhLnec", "source_type": "pdf", "n_chars": 658, "text": "it properly initialized and \nconsistent with its type?\nØAre there any variable with similar names?\nØAre there any variables declared that are never referenced or just referenced \nonce (should be a constant)?\nØAre all variables explicitly declared within a specific module?\n\nCode review checklist: Computation errors\nØDo any calculations that use variables have different data types?\n§E.g., add a floating-point number to an integer\nØDo any calculations that use variables have the same data type but are different \nsize?\n§E.g., add a long integer to a short integer\nØAre the compiler’s conversion rules for variables of inconsistent type or size \nunderstood?"}
{"id": "pdf::Ch10 StaticTesting::2095", "page_id": "pdf::Ch10 StaticTesting", "title": "Ch10 StaticTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch10 StaticTesting.pdf", "section": "Ch10 StaticTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/LBqWwBf4AiMLsjkjjK4cHKhLnec", "source_type": "pdf", "n_chars": 663, "text": "nteger\nØAre the compiler’s conversion rules for variables of inconsistent type or size \nunderstood?\nØIs overflow or underflow in the middle of a numeric calculation possible?\nØIs it ever possible for a divisor/modulus to be 0?\nØCan a variable’s value go outside its meaningful range?\n§E.g., can a probability be less than 0% or greater than 100%?\nØAre parentheses needed to clarify operator presence rules?\n\nCode review checklist: Comparison errors\nØAre the comparisons correct?\n§E.g., < instead of <=\nØAre there comparisons between floating-point values?\n§E.g., is 1.0000001 close enough to 1.0000002 to be equal?\nØAre the operands of a Boolean operator Boolean?"}
{"id": "pdf::Ch10 StaticTesting::2096", "page_id": "pdf::Ch10 StaticTesting", "title": "Ch10 StaticTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch10 StaticTesting.pdf", "section": "Ch10 StaticTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/LBqWwBf4AiMLsjkjjK4cHKhLnec", "source_type": "pdf", "n_chars": 686, "text": "s 1.0000001 close enough to 1.0000002 to be equal?\nØAre the operands of a Boolean operator Boolean?\n§E.g., in C 0 is false and non-0 is true\n\nCode review checklist: Control flow errors\nØDo the loops terminate? If not, is that by design?\nØDoes every switch statement have a default clause?\nØAre there switch statements nested in loops?\nØE.g., careful because break statements in switch statements will not \nexit the loop … but break statements not in switch statements will \nexit the loop.\nØIs it possible that a loop never executes? If it acceptable if it doesn’t?\nØDoes the compiler support short-circuiting in expression evaluation?\n\nCode review checklist: Subroutine parameter errors"}
{"id": "pdf::Ch10 StaticTesting::2097", "page_id": "pdf::Ch10 StaticTesting", "title": "Ch10 StaticTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch10 StaticTesting.pdf", "section": "Ch10 StaticTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/LBqWwBf4AiMLsjkjjK4cHKhLnec", "source_type": "pdf", "n_chars": 672, "text": "port short-circuiting in expression evaluation?\n\nCode review checklist: Subroutine parameter errors\nØIf constants are passed to the subroutine as arguments are they accidentally \nchanged in the subroutine?\nØDo the units of each parameter match the units of each corresponding \nargument?\n§E.g., English versus metric\n§This is especially pertinent for SOA components\nØDo the types and sizes of the parameters received by a subroutine match \nthose sent by the calling code?\n\nCode review checklist: Input/Output errors\nØIf the file or peripheral is not ready, is that error condition handled?\nØDoes the software handle the situation of the external device being \ndisconnected?"}
{"id": "pdf::Ch10 StaticTesting::2098", "page_id": "pdf::Ch10 StaticTesting", "title": "Ch10 StaticTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch10 StaticTesting.pdf", "section": "Ch10 StaticTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/LBqWwBf4AiMLsjkjjK4cHKhLnec", "source_type": "pdf", "n_chars": 644, "text": "dition handled?\nØDoes the software handle the situation of the external device being \ndisconnected?\nØHave all error messages been checked for correctness, appropriateness, \ngrammar, and spelling?\nØAre all exceptions handled by some part of the code?\nØDoes the software adhere to the specified format of the date being read from \nor written to the external device?\n\nCode review checklist: Other checks\nØDoes your code pass the lint test?\n§E.g., How about gcc compiler warnings?\nØIs your code portable to other OS platforms?\nØDoes the code handle ASCII and Unicode?\nØHow about internationalization issues?\nØDoes your code rely on deprecated APIs?"}
{"id": "pdf::Ch10 StaticTesting::2099", "page_id": "pdf::Ch10 StaticTesting", "title": "Ch10 StaticTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch10 StaticTesting.pdf", "section": "Ch10 StaticTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/LBqWwBf4AiMLsjkjjK4cHKhLnec", "source_type": "pdf", "n_chars": 646, "text": "ASCII and Unicode?\nØHow about internationalization issues?\nØDoes your code rely on deprecated APIs?\nØWill your code port to architectures with different byte orderings?\n§E.g., little (increasing numeric significance with increasing memory \naddresses) versus big (the opposite of little) endian?\n\n3. Static ProgramAnalysis\nØTry to discover issues by analyzing source code. No need to run.\n§Defects of interest may be on uncommon or difficult-to-force execution paths \nfor testing.\n§What we really want to do is check the entire possible state space of the \nprogram for particular properties (e.g., race condition, buffer overflow, use \nafter free)"}
{"id": "pdf::Ch10 StaticTesting::2100", "page_id": "pdf::Ch10 StaticTesting", "title": "Ch10 StaticTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch10 StaticTesting.pdf", "section": "Ch10 StaticTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/LBqWwBf4AiMLsjkjjK4cHKhLnec", "source_type": "pdf", "n_chars": 677, "text": "of the \nprogram for particular properties (e.g., race condition, buffer overflow, use \nafter free)\n§Static code analysis tools: Lint/ FindBugs/Coverity/Facebook Infer…\n.\nDynamic:\n§Testing: Direct execution of code on test data in a controlled environment.\nStatic:\n§Inspection: Human evaluation of code, design documents (specs and models), \nmodifications.\n§ Program Analysis: Tools reasoning about the program without executing it.\n\nThe most common defect in open-source software\nCoverity Scan Program (Stanford, 2006)\n§Launched under a contract with the Department of Homeland Security to \nharden open source software which provides critical infrastructure for the \nInternet."}
{"id": "pdf::Ch10 StaticTesting::2101", "page_id": "pdf::Ch10 StaticTesting", "title": "Ch10 StaticTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch10 StaticTesting.pdf", "section": "Ch10 StaticTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/LBqWwBf4AiMLsjkjjK4cHKhLnec", "source_type": "pdf", "n_chars": 683, "text": "Security to \nharden open source software which provides critical infrastructure for the \nInternet.\n§Analyzed more than 290 open source projects, including Linux, Apache, \nPHP, and Android.\nDefects Frequency Risk\nNull pointer dereferences 27.60% Medium\nResource leaks 23.19% High\nIncorrect expression 9.76% Medium\nUninitialized variables 8.41% High\nUse after free 5.91% High\nBuffer overflows 5.52% High\n\nprogram Crash, exit, restart, execution of unauthorized code or command\nChecker：\nFORWARD_NULL\n\nChecker: \nRESOURCE_LEAKDoS attacks, sensitive data leaks, resource consumption\n\nChecker:\nCOPY_PASTE_ERROR\nUnexpected output values, program logic errors, runtime errors\n\nChecker:\nUNINIT"}
{"id": "pdf::Ch10 StaticTesting::2102", "page_id": "pdf::Ch10 StaticTesting", "title": "Ch10 StaticTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch10 StaticTesting.pdf", "section": "Ch10 StaticTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/LBqWwBf4AiMLsjkjjK4cHKhLnec", "source_type": "pdf", "n_chars": 689, "text": "r:\nCOPY_PASTE_ERROR\nUnexpected output values, program logic errors, runtime errors\n\nChecker:\nUNINIT\nResultin incorrect program logic, incorrect data, program crash\n\nMemory - illegal accesses, Program Crash, exit, restart, resource consumption\nChecker: \nUSE_AFTER_FREE\n\nChecker:\n OVERRUN\nMemory - illegal accesses, Program Crash, exit, restart, resource consumption\n\nProgram Analyzer\nCode Report Type Line\n1 mem leak 324\n2 buffer oflow 4,353,245\n3 sql injection 23,212\n4 stack oflow 86,923\n5 dang ptr 8,491\n… … …\n10,502 info leak 10,921\nProgram \nAnalyzer\nSpec\nSound: may \nreport many\nwarnings\nMay emit \nfalse alarms\nAnalyze large \ncode bases\nfalse alarm\nfalse alarm\n\nNull pointer analysis"}
{"id": "pdf::Ch10 StaticTesting::2103", "page_id": "pdf::Ch10 StaticTesting", "title": "Ch10 StaticTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch10 StaticTesting.pdf", "section": "Ch10 StaticTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/LBqWwBf4AiMLsjkjjK4cHKhLnec", "source_type": "pdf", "n_chars": 692, "text": "ngs\nMay emit \nfalse alarms\nAnalyze large \ncode bases\nfalse alarm\nfalse alarm\n\nNull pointer analysis\nØTrack each variable in the program at all program points. \nØAbstraction:\n§Program counter\n§3 states for each variable: null, not-null, and maybe-null.\nØThen check if, at each dereference, the analysis has identified whether the \ndereferenced variable is or might be null.\n\nIn graph form…\n1.int foo() {\n2. Integer x = new Integer(6);\n3. Integer y = bar();\n4. int z;\n5. if (y != null)\n6. z = x.intVal() + y.intVal();\n7. } else {\n8. z = x.intVal();\n9. y = x;\n10. x = null;\n11. }\n12. return z + x.intVal();\n13.}\nInteger x = new Integer(6);\nint z; \nif (y != null)"}
{"id": "pdf::Ch10 StaticTesting::2104", "page_id": "pdf::Ch10 StaticTesting", "title": "Ch10 StaticTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch10 StaticTesting.pdf", "section": "Ch10 StaticTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/LBqWwBf4AiMLsjkjjK4cHKhLnec", "source_type": "pdf", "n_chars": 678, "text": "null;\n11. }\n12. return z + x.intVal();\n13.}\nInteger x = new Integer(6);\nint z; \nif (y != null) \nz = x.intVal() + \ny.intVal();\nz = x.intVal();\n y = x;\n x = null;\nreturn z + x.intVal();\nInteger y = bar();\nx à not-null\nx à not-null, y à maybe-null\nx à not-null, y à not-null x à not-null, y ànull\nx à not-null, y à not-null x à null, y à not-null\nx à maybe-null, y à not-nullError: may have null pointer on line 12, \nbecause x may be null!\n\nQuality assurance at Microsoft\nØOriginal process: manual code inspection \n•Effective when system and team are small \n•Too many paths to consider as system grew \nØEarly 1990s: add massive system and unit testing \n•Tests took weeks to run"}
{"id": "pdf::Ch10 StaticTesting::2105", "page_id": "pdf::Ch10 StaticTesting", "title": "Ch10 StaticTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch10 StaticTesting.pdf", "section": "Ch10 StaticTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/LBqWwBf4AiMLsjkjjK4cHKhLnec", "source_type": "pdf", "n_chars": 646, "text": "nsider as system grew \nØEarly 1990s: add massive system and unit testing \n•Tests took weeks to run \n•Diversity of platforms and configurations \n•Sheer volume of tests \n•Inefficient detection of common patterns, security holes \nØNon-local, intermittent, uncommon path bugs was treading water in Windows \nVista development \nØEarly 2000s: add static analysis\nResults indicate static analysis tools are complementary to other fault-detection \ntechniques for the economic production of a high-quality software product.\n\nStatic Analysis vs. Testing\nWhich one to use when?\nØPoints in favor of Static Analysis\n○ Don’t need to set up run environment, etc."}
{"id": "pdf::Ch10 StaticTesting::2106", "page_id": "pdf::Ch10 StaticTesting", "title": "Ch10 StaticTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch10 StaticTesting.pdf", "section": "Ch10 StaticTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/LBqWwBf4AiMLsjkjjK4cHKhLnec", "source_type": "pdf", "n_chars": 459, "text": "h one to use when?\nØPoints in favor of Static Analysis\n○ Don’t need to set up run environment, etc.\n○ Can analyze functions/modules independently and in parallel\n○ Don’t need to think of (or try to generate) program inputs\nØPoints in favor of Testing / Dynamic Analysis\n○ Not deterred by complex program features\n○ Can easily handle external libraries, platform-specific config, etc.\n○ Ideally no false positives\n○ Easier to debug when a failure is identified"}
{"id": "pdf::Ch11 AcceptanceTesting::2107", "page_id": "pdf::Ch11 AcceptanceTesting", "title": "Ch11 AcceptanceTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch11 AcceptanceTesting.pdf", "section": "Ch11 AcceptanceTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/QFjiwrCvFiVOVdkU4UKcLnUgnEc", "source_type": "pdf", "n_chars": 668, "text": "Acceptance Testing\nYanxia Liu cslyx@scut.edu.cn\nSpring, 2025\n1\n\nContents\nØWhat is Acceptance Testing\nØContents of Acceptance Testing\nØInstallationTesting&CompatibilityTesting\nØAlpha Testing & Beta Testing\nØBrief comparison of four phases of software testing\n2\n\n3\nØAcceptance testing is the final level of software testing where the system is \ntested for compliance to its business requirements. \nØIt is performed by the client or the end users with the intent to see if the product \nis fit for delivery.\nØIt is carried out after system testing and before the final delivery to the client.\nØIt works under theBlack Box Testing Method. \n1. What is Acceptance Testing\n\n4"}
{"id": "pdf::Ch11 AcceptanceTesting::2108", "page_id": "pdf::Ch11 AcceptanceTesting", "title": "Ch11 AcceptanceTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch11 AcceptanceTesting.pdf", "section": "Ch11 AcceptanceTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/QFjiwrCvFiVOVdkU4UKcLnUgnEc", "source_type": "pdf", "n_chars": 678, "text": "ivery to the client.\nØIt works under theBlack Box Testing Method. \n1. What is Acceptance Testing\n\n4\n2.Contents of Acceptance Testing\nTwo parts: Software Configuration Review and Software Validity Testing.\n1.Software configuration review\nCommon software configuration items include ：\n(1)Main software program configuration, generally including source \nprogram, executable program, software installation and configuration \nscript, key test script or test program\n(2) Main technical documents\n(3) Main development management documents\n\n5\nØComplete the following checksforthesoftware configuration :\n(1) Source code check\n§Normative check\n§Data type check\n§Check external interfaces"}
{"id": "pdf::Ch11 AcceptanceTesting::2109", "page_id": "pdf::Ch11 AcceptanceTesting", "title": "Ch11 AcceptanceTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch11 AcceptanceTesting.pdf", "section": "Ch11 AcceptanceTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/QFjiwrCvFiVOVdkU4UKcLnUgnEc", "source_type": "pdf", "n_chars": 636, "text": "configuration :\n(1) Source code check\n§Normative check\n§Data type check\n§Check external interfaces\n(2) Software consistency check\n§Compile check\n§Install and uninstall tests\n§Run the module consistency check\nØCheck the following items for documents :\n§Completeness\n§Normative\n§Targeted\n§Complete independence\n§Flexibility\n§Traceability\nContents of Acceptance Testing\n\n6\nContents of Acceptance Testing\n2.Software validity test\n§Software interface testing\n§Usability testing\n§Functional testing（including normal business process testing and error \nhandling capability testing）\n§Performance test（ including load, volume and stress testing）"}
{"id": "pdf::Ch11 AcceptanceTesting::2110", "page_id": "pdf::Ch11 AcceptanceTesting", "title": "Ch11 AcceptanceTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch11 AcceptanceTesting.pdf", "section": "Ch11 AcceptanceTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/QFjiwrCvFiVOVdkU4UKcLnUgnEc", "source_type": "pdf", "n_chars": 689, "text": "d error \nhandling capability testing）\n§Performance test（ including load, volume and stress testing）\n§Software executing environment and system platform configuration testing\n§Robustness testing( including recovery tests under various hardware and \nsoftware failures)\n§Reliability testing\n§Compatibility testing\n§Data backup testing\n§Security testing\n\n7\nContents of Acceptance Testing\n\n8\nAcceptance TestingConsideration\n(1)Before the acceptance test, a formal acceptance test plan shall be prepared to clarify the criteria \nfor passing the acceptance test, which shall be confirmed by users.\n(2)The acceptance test must be carried out in the actual use environment of end users, or simulate"}
{"id": "pdf::Ch11 AcceptanceTesting::2111", "page_id": "pdf::Ch11 AcceptanceTesting", "title": "Ch11 AcceptanceTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch11 AcceptanceTesting.pdf", "section": "Ch11 AcceptanceTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/QFjiwrCvFiVOVdkU4UKcLnUgnEc", "source_type": "pdf", "n_chars": 627, "text": "(2)The acceptance test must be carried out in the actual use environment of end users, or simulate \nthe actual operation environment of users, so as to avoid some potential problems of software \nthat cannot be found due to environmental differences.\n(3)Acceptance tests should cover coarse-grained, business-level functions of the software. There \nis traceability between acceptance test cases and software project contracts and software \nrequirements specifications. \nIt is not possible or necessary for acceptance test cases to re-run all test cases conducted during the \ndevelopment phase.\n\n9\nAcceptance TestingConsideration"}
{"id": "pdf::Ch11 AcceptanceTesting::2112", "page_id": "pdf::Ch11 AcceptanceTesting", "title": "Ch11 AcceptanceTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch11 AcceptanceTesting.pdf", "section": "Ch11 AcceptanceTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/QFjiwrCvFiVOVdkU4UKcLnUgnEc", "source_type": "pdf", "n_chars": 683, "text": "o re-run all test cases conducted during the \ndevelopment phase.\n\n9\nAcceptance TestingConsideration\n(4) The acceptance test must be user-oriented and conducted in a way that users can intuitively \nperceive from the perspective of the actual business scenarios used by end users. \n(5) The design of acceptance test cases must fully consider the user‘s way of thinking, usage habits, \nbusiness language, etc., and organize test cases and test procedures according to the main business \nscenarios.Itfocuses on the function points and performance points that customers care most about.\n(6) Acceptance testing of project-type software is generally completed jointly by the tester and user"}
{"id": "pdf::Ch11 AcceptanceTesting::2113", "page_id": "pdf::Ch11 AcceptanceTesting", "title": "Ch11 AcceptanceTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch11 AcceptanceTesting.pdf", "section": "Ch11 AcceptanceTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/QFjiwrCvFiVOVdkU4UKcLnUgnEc", "source_type": "pdf", "n_chars": 687, "text": "Acceptance testing of project-type software is generally completed jointly by the tester and user \n; Product software for the public and shall be conducted jointly by the tester, design, marketing and \nafter-sales service department.\n\n10\n3. InstallationTesting\nØInstallation testing is a type of software testing that verifies the software’s \ninstallation process and ensures that the software is installed correctly on \nvarious systems and configurations.\nØIt is a critical aspect of the software testing process and helps ensure that the \nsoftware can be easily installed, configured, and uninstalled without any issues.\n•System software installation\n•Application software installation"}
{"id": "pdf::Ch11 AcceptanceTesting::2114", "page_id": "pdf::Ch11 AcceptanceTesting", "title": "Ch11 AcceptanceTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch11 AcceptanceTesting.pdf", "section": "Ch11 AcceptanceTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/QFjiwrCvFiVOVdkU4UKcLnUgnEc", "source_type": "pdf", "n_chars": 665, "text": "nd uninstalled without any issues.\n•System software installation\n•Application software installation\n•Server installation\n•Client installation\n•Product upgrade installation\n\n11\n3. InstallationTesting\nPrecautions for installation testing:\nØWhether professional installation is required.\nØDoes the installation manual have any restrictions or requirements on the installation \nenvironment?\nØWhether the process is simple and easy to master.\nØCheck whether there are obvious and reasonable prompts during the process.\nØWhether there will be unforeseeable or irreparable errors.\nØWhether the installation program occupies system resources and conflicts with the original"}
{"id": "pdf::Ch11 AcceptanceTesting::2115", "page_id": "pdf::Ch11 AcceptanceTesting", "title": "Ch11 AcceptanceTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch11 AcceptanceTesting.pdf", "section": "Ch11 AcceptanceTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/QFjiwrCvFiVOVdkU4UKcLnUgnEc", "source_type": "pdf", "n_chars": 629, "text": "rrors.\nØWhether the installation program occupies system resources and conflicts with the original \nsystem, which affects the security of the original system.\nØIntegrity and flexibility of software installation.\nØVerification of license and registration number.\nØCheck whether the original program can run properly after the upgrade.\nØUninstall testing\n\n12\n3. Compatibility Testing\nØCompatibility testing aims to check the developed software application \nfunctionality on various software, hardware platforms, network and browser etc.\nØThis testing is done only when the application becomes stable.\nØSoftwareCompatibility Testing"}
{"id": "pdf::Ch11 AcceptanceTesting::2116", "page_id": "pdf::Ch11 AcceptanceTesting", "title": "Ch11 AcceptanceTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch11 AcceptanceTesting.pdf", "section": "Ch11 AcceptanceTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/QFjiwrCvFiVOVdkU4UKcLnUgnEc", "source_type": "pdf", "n_chars": 687, "text": "etc.\nØThis testing is done only when the application becomes stable.\nØSoftwareCompatibility Testing\n•Testing the compatibility of an application with an Operating System like \nLinux, Mac, Windows\n•Testing compatibility on Database like Oracle SQL server, MongoDB server.\n•Testingbrowser compatibility with different browsers like Google Chrome, \nInternet Explorer etc. \n\n13\nPC Unix/Mac\nWinxpWin7Win10Win11SolarisHP-UXMacOSAIX\nIE11 √ √\nIE edge √ √ √\nFirefox √ √ √\nChrome √ √ √ √\n360 √ √\n…\nWeb applications must be compatible with different versions of browsers running \ndifferent OS.\nDesign test matrix table\n\n14\n3. Compatibility Testing\nØHardwareCompatibilityTesting–ConfigurationTesting"}
{"id": "pdf::Ch11 AcceptanceTesting::2117", "page_id": "pdf::Ch11 AcceptanceTesting", "title": "Ch11 AcceptanceTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch11 AcceptanceTesting.pdf", "section": "Ch11 AcceptanceTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/QFjiwrCvFiVOVdkU4UKcLnUgnEc", "source_type": "pdf", "n_chars": 677, "text": "n test matrix table\n\n14\n3. Compatibility Testing\nØHardwareCompatibilityTesting–ConfigurationTesting\nØTesting compatibility on different devices like in mobile phones, computers\nØChecking compatibility with a particular size of \n•RAM\n•ROM\n•Hard Disk\n•Memory Cards\n•Processor\n•Graphics Card……\n\n16\n4. Alpha Testing & Beta Testing\nØAlpha and Beta testingare Acceptance Testing types(Customer \nValidation methodologies ) that help in building confidence to launch the \nproduct, and thereby result in the success of the product in the market.\nØAlpha and Beta Testing phases mainly focus on discovering the bugs \nfrom an already tested product and they give a clear picture of how the"}
{"id": "pdf::Ch11 AcceptanceTesting::2118", "page_id": "pdf::Ch11 AcceptanceTesting", "title": "Ch11 AcceptanceTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch11 AcceptanceTesting.pdf", "section": "Ch11 AcceptanceTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/QFjiwrCvFiVOVdkU4UKcLnUgnEc", "source_type": "pdf", "n_chars": 650, "text": "s on discovering the bugs \nfrom an already tested product and they give a clear picture of how the \nproduct is used by the real-time users. \n\n\n17\nAlpha Testing\nØAlpha testingis the form of acceptance testing that takes place at \nthe developer’s site.\nØIt can be carried out by both in-house developers and QAs as well \nas potential end-users as well.\nØAlpha testing is not open to the world.\n\n18\nBeta Testing\nØBeta Testing (Field Testing)is the form of acceptance testing that takes place \nat the customer’s or the end user’s site.\nØIt is performed after alpha testing and in the real-world environment without \nthe presence or control of developers."}
{"id": "pdf::Ch11 AcceptanceTesting::2119", "page_id": "pdf::Ch11 AcceptanceTesting", "title": "Ch11 AcceptanceTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch11 AcceptanceTesting.pdf", "section": "Ch11 AcceptanceTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/QFjiwrCvFiVOVdkU4UKcLnUgnEc", "source_type": "pdf", "n_chars": 695, "text": "ter alpha testing and in the real-world environment without \nthe presence or control of developers.\nØBeta tests or the beta version of the application are normally open to the \nwhole world (or client).\nFor example,recently Microsoft corporation released Windows 10 beta and based \non the feedback from thousands of users they managed to release a stable OS \nversion. In the past, Apple also released OS X beta in public and fixed many minor \nissues and improved the OS based on user feedback.\n\n19\nAlpha Testing & Beta Testing\n\n20\nAlpha Testing & Beta Testing\n\n21\n5.Brief comparison of software testing phases\nItems Unit Testing Integration Testing System Testing Acceptance Testing\nTest \nobject"}
{"id": "pdf::Ch11 AcceptanceTesting::2120", "page_id": "pdf::Ch11 AcceptanceTesting", "title": "Ch11 AcceptanceTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch11 AcceptanceTesting.pdf", "section": "Ch11 AcceptanceTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/QFjiwrCvFiVOVdkU4UKcLnUgnEc", "source_type": "pdf", "n_chars": 682, "text": "esting phases\nItems Unit Testing Integration Testing System Testing Acceptance Testing\nTest \nobject\nSoftware units, such \nas functions, classes, \ncomponents, modules\nInterfaces between \nmodules, such as parameter \npassing\nThe entire system, \nincluding hardware \nand software\nThe entire system, \nincluding hardware and \nsoftware\nTestbasis Detailed software design Software architecture design Software requirements specification Requirements specification, contract, acceptance criteria\nTester Developer or white box test engineer Developers and testers work together primarily the responsibility of professional testers User-dominant, developer and tester work together\nTest\nmethods"}
{"id": "pdf::Ch11 AcceptanceTesting::2121", "page_id": "pdf::Ch11 AcceptanceTesting", "title": "Ch11 AcceptanceTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch11 AcceptanceTesting.pdf", "section": "Ch11 AcceptanceTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/QFjiwrCvFiVOVdkU4UKcLnUgnEc", "source_type": "pdf", "n_chars": 434, "text": "sponsibility of professional testers User-dominant, developer and tester work together\nTest\nmethods\nWhite box test is \nmainly used\nBlack box testing is \nmainly used while white \nbox testing is the secondary\nFully black-box \ntesting Fully black-box testing\nTest dataReal data is generally not used Real data is generally not used Use or simulate real business data whenever possible Use or simulate real business data whenever possible"}
{"id": "pdf::Ch12 SoftwareMaintenance::2122", "page_id": "pdf::Ch12 SoftwareMaintenance", "title": "Ch12 SoftwareMaintenance.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch12 SoftwareMaintenance.pdf", "section": "Ch12 SoftwareMaintenance.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/X1flwzVN1i2qEIkTXJLcnDQlnCd", "source_type": "pdf", "n_chars": 699, "text": "SoftwareMaintenance\nYanxia Liu cslyx@scut.edu.cn\nSpring, 2025\n1\n\nContents\nØWhatis Software Maintenance \nØTypes of Maintenance\nØSoftware Maintenance Life Cycle\nØSoftware Maintainability\n2\n\n4\n1.WhatisSoftware maintenance \n“When the transition from development to evolution is \nnot seamless, the process of changing the software \nafter delivery is often called software maintenance”\nØIEEE: Maintenance is the process of modifying a software system or component \nafter delivery to correct faults, improve performance or other attributes, or adapt to \na changed environment.\nØMaintenance does not normally involve major changes to the system’s architecture\nØMaintenance requires program understanding\n\n6"}
{"id": "pdf::Ch12 SoftwareMaintenance::2123", "page_id": "pdf::Ch12 SoftwareMaintenance", "title": "Ch12 SoftwareMaintenance.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch12 SoftwareMaintenance.pdf", "section": "Ch12 SoftwareMaintenance.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/X1flwzVN1i2qEIkTXJLcnDQlnCd", "source_type": "pdf", "n_chars": 685, "text": "y involve major changes to the system’s architecture\nØMaintenance requires program understanding\n\n6\nMaintenance vs. Evolution\nØSoftware Maintenance\n§ Activities required to keep a software system operational after it \nis deployed\nØSoftware Evolution\n§ Continuous changes from a lesser, simpler, or worse system to a \nhigher or better system\n\n7\nSoftware Evolution\nØThe system changes relate to changing needs—business and user\nØThe system evolves continuously throughout its lifetime\nØModern agile processes emphasize getting a few functionalities \nrunning, then adding new behaviors over time\n“Software development does not stop when a \nsystem is delivered but continues throughout the"}
{"id": "pdf::Ch12 SoftwareMaintenance::2124", "page_id": "pdf::Ch12 SoftwareMaintenance", "title": "Ch12 SoftwareMaintenance.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch12 SoftwareMaintenance.pdf", "section": "Ch12 SoftwareMaintenance.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/X1flwzVN1i2qEIkTXJLcnDQlnCd", "source_type": "pdf", "n_chars": 670, "text": "time\n“Software development does not stop when a \nsystem is delivered but continues throughout the \nlifetime of the system”\n\n16\n2.Types of Maintenance\n\n\n17\nØY2K\nomany, many systems had to be updated\nolanguage analyzers (find where changes need to be made)\nØAnti-Virus Software\nodon't usually have to update software, but must send virus definitions\nØOperating System Patching\noMicrosoft, Apple, Linux/Unix\noOS is core to use of computer, so it must be constantly maintained\nØCommercial Software in General\nocustomers need to be informed of updates\nMaintenance Examples\n\n21\nØMaintenance programmers generally lack detailed knowledge about the system or \napplication domain"}
{"id": "pdf::Ch12 SoftwareMaintenance::2125", "page_id": "pdf::Ch12 SoftwareMaintenance", "title": "Ch12 SoftwareMaintenance.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch12 SoftwareMaintenance.pdf", "section": "Ch12 SoftwareMaintenance.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/X1flwzVN1i2qEIkTXJLcnDQlnCd", "source_type": "pdf", "n_chars": 693, "text": "ØMaintenance programmers generally lack detailed knowledge about the system or \napplication domain\noOften scarce sources available to reference\noUsually requires going to the source code to figure out how the system works\noExperienced programmers have learned to distrust documentation, usually \ninsufficient and out of date\noWhen a quick-fix is done, the documentation is often not updated to reflect \nchanges\nØ47% of software maintenance effort devoted to understanding the software\no E.g. if there are n modules and we change k of them, for each changed module we need to \nknow possible interactions with the other n-1 modules\nØ>50% of effort can be attributed to lack of user understanding"}
{"id": "pdf::Ch12 SoftwareMaintenance::2126", "page_id": "pdf::Ch12 SoftwareMaintenance", "title": "Ch12 SoftwareMaintenance.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch12 SoftwareMaintenance.pdf", "section": "Ch12 SoftwareMaintenance.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/X1flwzVN1i2qEIkTXJLcnDQlnCd", "source_type": "pdf", "n_chars": 680, "text": "ractions with the other n-1 modules\nØ>50% of effort can be attributed to lack of user understanding\no Incomplete or mistaken reports of errors and enhancements\nØLow Morale -Maintenance sometimes considered second-rate job\nProblems facing maintainers\n\n22\n3.Software Maintenance Life Cycle\nØ Changes are implemented in \nthe software system by \nfollowing a software \nmaintenance process \nØIEEE 1219: \nØProcess for controlling \nmaintenance changes\nØKnown as Software \nMaintenance Life Cycle \n(SMLC).\n\n\n34\n4. Additional maintenance terms\nØMaintainability : The ease with which software can be modified\nØ\nRipple effect \n: Changes in one software location can impact other \n components"}
{"id": "pdf::Ch12 SoftwareMaintenance::2127", "page_id": "pdf::Ch12 SoftwareMaintenance", "title": "Ch12 SoftwareMaintenance.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch12 SoftwareMaintenance.pdf", "section": "Ch12 SoftwareMaintenance.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/X1flwzVN1i2qEIkTXJLcnDQlnCd", "source_type": "pdf", "n_chars": 695, "text": "can be modified\nØ\nRipple effect \n: Changes in one software location can impact other \n components\nØImpact analysis : Process of identifying how a change in terms of \n how a change will affect the rest of the system \nØTraceability : The degree to which a relationship can be established \n between two or more software artifacts\nØLegacy systems : A software system that is still in use, but the \n development team is no longer active\n\n36\nMajor maintenance activities\nØIdentify the change\n§What to change, why to change it there\nØManage the process … what resources are needed?\nØUnderstand the program\n§How to make the change, determining the ripple effect\nØMake the change\nØTest the change"}
{"id": "pdf::Ch12 SoftwareMaintenance::2128", "page_id": "pdf::Ch12 SoftwareMaintenance", "title": "Ch12 SoftwareMaintenance.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch12 SoftwareMaintenance.pdf", "section": "Ch12 SoftwareMaintenance.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/X1flwzVN1i2qEIkTXJLcnDQlnCd", "source_type": "pdf", "n_chars": 678, "text": "he program\n§How to make the change, determining the ripple effect\nØMake the change\nØTest the change\nØDocument and record the change\nWe must understand an existing system before changing it\n§ How to make the change ?\n§ What are the potential ripple effects ?\n§ What skills and knowledge are required ?\n\n37\nComprehension process\nRead \ndocumentation\nRun the program\nRead the \nsource code Static analysis\nDynamic analysis\n\n38\nØProgram comprehension\noProgram slicers\noStatic analyzers\noDynamic analyzers\noData flow analyzers\noCross-references\noDependency analyzers\nØReverse engineering tools\nØSoftware test tools\nØSoftware configuration management tools\nØSoftware documentation tools"}
{"id": "pdf::Ch12 SoftwareMaintenance::2129", "page_id": "pdf::Ch12 SoftwareMaintenance", "title": "Ch12 SoftwareMaintenance.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch12 SoftwareMaintenance.pdf", "section": "Ch12 SoftwareMaintenance.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/X1flwzVN1i2qEIkTXJLcnDQlnCd", "source_type": "pdf", "n_chars": 666, "text": "g tools\nØSoftware test tools\nØSoftware configuration management tools\nØSoftware documentation tools\nØSoftware measurement tools\nSoftware maintenance tools\n\n39\nWhat influences understanding?\nØExpertise : Domain knowledge, programming skills\nØProgram structure : Modularity, level of nesting\nØDocumentation : Readability, accuracy, up-to-date\nØCoding conventions : Naming style, small design patterns\nØComments : Accuracy, clarity, and usefulness\nØProgram presentation : Good use of indentation and spacing\nSloppy programming creates\nmaintenance debt\n\n53\nSummary\nØProgramming habits have a major impact on readability\nØReadability has a major impact on maintainability"}
{"id": "pdf::Ch12 SoftwareMaintenance::2130", "page_id": "pdf::Ch12 SoftwareMaintenance", "title": "Ch12 SoftwareMaintenance.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch12 SoftwareMaintenance.pdf", "section": "Ch12 SoftwareMaintenance.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/X1flwzVN1i2qEIkTXJLcnDQlnCd", "source_type": "pdf", "n_chars": 260, "text": "amming habits have a major impact on readability\nØReadability has a major impact on maintainability\nØMaintainability determines long-term costs\nThe minor decisions that engineers make determine how \nmuch money the company makes\nThat is what engineering means !"}
{"id": "pdf::Ch2 TestProcess::2131", "page_id": "pdf::Ch2 TestProcess", "title": "Ch2 TestProcess.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch2 TestProcess.pdf", "section": "Ch2 TestProcess.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/T1YQwI0Gvi1Qi5kwEO6czKSGnFf", "source_type": "pdf", "n_chars": 640, "text": "Testing in the Software Process\nYanxia Liu cslyx@scut.edu.cn\nSpring, 2025\n1\n\nContents\n Waterfall Model\n Spiral Model\n V Model\n W Model\n Agile Model – XP\n DevOps \n2\n\n3\n1. Waterfall Model\n All the planning is done at the beginning,\nand once created it is not to be changed.\n There is no overlap between any of the\nsubsequent phases.\n Often anyone’s first chance to “see” the\nprogram is at the very end once the \ntesting is complete.\n\n\n4\nWaterfall Model – Strength& Weakness\n Strength: \n1) If time is spent early on making sure that the requirements and design \nare absolutely correct, then this will save much time and effort later."}
{"id": "pdf::Ch2 TestProcess::2132", "page_id": "pdf::Ch2 TestProcess", "title": "Ch2 TestProcess.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch2 TestProcess.pdf", "section": "Ch2 TestProcess.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/T1YQwI0Gvi1Qi5kwEO6czKSGnFf", "source_type": "pdf", "n_chars": 683, "text": "he requirements and design \nare absolutely correct, then this will save much time and effort later.\n2) There is an emphasis on documentation which keeps all knowledge in a \ncentral repository and can be referenced easily by new members joining \nthe team.\n\n5\n Weakness: \n1) Few visible signs of progress until the end of the project\n2) It is not flexible to changes\n3) Time-consuming to produce all the documentation\n4) Tests are only carried out at the end – this could mean a compromise if \ntime or budgetary constraints exist\n5) Having to test the program as a whole could result in incomplete testing\n6) If testing does identify a fault that suggests a redesign it may be ignored"}
{"id": "pdf::Ch2 TestProcess::2133", "page_id": "pdf::Ch2 TestProcess", "title": "Ch2 TestProcess.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch2 TestProcess.pdf", "section": "Ch2 TestProcess.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/T1YQwI0Gvi1Qi5kwEO6czKSGnFf", "source_type": "pdf", "n_chars": 672, "text": "incomplete testing\n6) If testing does identify a fault that suggests a redesign it may be ignored \nbecause of the trouble involved\n7) If the customer is unhappy it may incur a long maintenancephase \nresolving their issues\nWaterfall Model – Strength& Weakness\n\n6\n2. Spiral Model\n Risk-driven development \nprocess\n Combination of waterfall \nmodel and Rapid Prototype \nIteration model\n Begins with a design goal \nand ends with the client \nreviewing the progress.\n\n7\nSpiral Model – Strength& Weakness\nStrength Weakness\nAdditional functionality or changes can be done \nat a later stage\nRisk of not meeting the schedule or budget\nCost estimation becomes easy as the prototype"}
{"id": "pdf::Ch2 TestProcess::2134", "page_id": "pdf::Ch2 TestProcess", "title": "Ch2 TestProcess.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch2 TestProcess.pdf", "section": "Ch2 TestProcess.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/T1YQwI0Gvi1Qi5kwEO6czKSGnFf", "source_type": "pdf", "n_chars": 693, "text": "ter stage\nRisk of not meeting the schedule or budget\nCost estimation becomes easy as the prototype \nbuilding is done in small fragments\nSpiral development works best for large projects only \nalso demands risk assessment expertise\nContinuous or repeated development helps in risk \nmanagement\nFor its smooth operation spiral model protocol needs to \nbe followed strictly\nDevelopment is fast and features are added in a \nsystematic way in Spiral development\nDocumentation is more as it has intermediate phases\nThere is always a space for customer feedback Spiral software development is not advisable for smaller \nproject, it might cost them a lot\n\n8\n3. V Model\n Extension of the Waterfall model"}
{"id": "pdf::Ch2 TestProcess::2135", "page_id": "pdf::Ch2 TestProcess", "title": "Ch2 TestProcess.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch2 TestProcess.pdf", "section": "Ch2 TestProcess.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/T1YQwI0Gvi1Qi5kwEO6czKSGnFf", "source_type": "pdf", "n_chars": 699, "text": "ble for smaller \nproject, it might cost them a lot\n\n8\n3. V Model\n Extension of the Waterfall model\n emphasizes Verification & Validation by marking the relationships between each phase of the \nlife cycle and testing activities\n Once the code implementation is finished the testing begins.\n Starts with unit testing, and moves up one test level at a time until the acceptance testing \nphase is completed\n\n\n9\nV Model\n Each document produced is associated with pairs of phases in the model.\n– (a) the User Requirements Specification. URS\n– (b) the System Requirements Specification, SRS\n– (c) the System Design Specifications, SDS\n– (d) Detailed Design Specifications, DDS"}
{"id": "pdf::Ch2 TestProcess::2136", "page_id": "pdf::Ch2 TestProcess", "title": "Ch2 TestProcess.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch2 TestProcess.pdf", "section": "Ch2 TestProcess.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/T1YQwI0Gvi1Qi5kwEO6czKSGnFf", "source_type": "pdf", "n_chars": 692, "text": "e System Design Specifications, SDS\n– (d) Detailed Design Specifications, DDS\n\n\n10\nV Model – Strength& Weakness\nStrength Weakness\nIt is simple and easy to manage due to the \nrigidity of the model\nLike the Waterfall model , there is no working \nsoftware produced until late during the life cycle\nIt encourages Verification and Validation at all \nphases\nIt is unsuitable where the requirements are at a\nmoderate to high risk of changing.\nEach phase has specific deliverables and a \nreview process.\nThe tight link between test, debug and change\ntasks during the test phase is not clear \nIt gives equal weight to testing alongside \ndevelopment rather than treating it as an"}
{"id": "pdf::Ch2 TestProcess::2137", "page_id": "pdf::Ch2 TestProcess", "title": "Ch2 TestProcess.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch2 TestProcess.pdf", "section": "Ch2 TestProcess.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/T1YQwI0Gvi1Qi5kwEO6czKSGnFf", "source_type": "pdf", "n_chars": 639, "text": "s not clear \nIt gives equal weight to testing alongside \ndevelopment rather than treating it as an \nafterthought at the end.\n\n11\n4. W Model\n Extension of V Model/Both V\n Testing is not after the code \nimplementation .\n Parallel to the development \nprocess, the test process is \ncarried out. \n Co-operation between \ndevelopment and testing \n Testing is more than just \nconstruction, execution and \nevaluation of test cases. \n\n\n12\n5. Agile Model\n Iterative and Incremental Development\n Break large projects into short cycles , each delivering a functional increment to iteratively refine \nfeatures.\n Customer-Centric Value Delivery"}
{"id": "pdf::Ch2 TestProcess::2138", "page_id": "pdf::Ch2 TestProcess", "title": "Ch2 TestProcess.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch2 TestProcess.pdf", "section": "Ch2 TestProcess.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/T1YQwI0Gvi1Qi5kwEO6czKSGnFf", "source_type": "pdf", "n_chars": 662, "text": "elivering a functional increment to iteratively refine \nfeatures.\n Customer-Centric Value Delivery\n Deliver working software frequently to adapt to changing requirements.\n Embracing Change\n Treat requirement changes as opportunities for improvement, adjusting priorities via continuous \nfeedback rather than adhering strictly to initial plans.\n Self-Organizing Teams and Collaboration\n Empower cross-functional teams to self-manage, emphasizing face-to-face communication\n\n13\nExtreme Programming -Value\nCommunication: \n XP programmers communicate with\ntheir customers and fellow \nprogrammers\nSimplicity\n they keep their design simple and \nclean\nFeedback:"}
{"id": "pdf::Ch2 TestProcess::2139", "page_id": "pdf::Ch2 TestProcess", "title": "Ch2 TestProcess.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch2 TestProcess.pdf", "section": "Ch2 TestProcess.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/T1YQwI0Gvi1Qi5kwEO6czKSGnFf", "source_type": "pdf", "n_chars": 642, "text": "customers and fellow \nprogrammers\nSimplicity\n they keep their design simple and \nclean\nFeedback: \n Get feedback by software testing from\nthe start\nCourage:\n Deliver the system to customers as \nearly as possible \n Implement changes as suggested,\nresponding with courage to changing \nrequirements\n\n\n14\nExtreme Programming - Process\n\n\n15\nExtreme Programming - Process\n\n\n16\n Testing Throughout the Lifecycle\n Shift-Left Testing: Start testing during the requirements phase, parallel to \ndevelopment\n Continuous Testing: Integrate testing into every iteration to ensure quality for \neach incremental release.\n Test-Driven Development (TDD)"}
{"id": "pdf::Ch2 TestProcess::2140", "page_id": "pdf::Ch2 TestProcess", "title": "Ch2 TestProcess.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch2 TestProcess.pdf", "section": "Ch2 TestProcess.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/T1YQwI0Gvi1Qi5kwEO6czKSGnFf", "source_type": "pdf", "n_chars": 667, "text": "to every iteration to ensure quality for \neach incremental release.\n Test-Driven Development (TDD)\n Write unit tests first → Develop code to pass tests → Refactor code.\n Define requirements through tests to ensure code meets expectations and \nremains maintainable.\nTesting in Agile Model\n\n17\nTDD - Test-Driven Development\nWrite a test for \nnew capability\nStart\nCompile\nFix compile \nerrors\nRun the test\nAnd see it fail\nWrite the code\nRun the test\nAnd see it pass\nRefactor as needed\n\n\n18\n Acceptance Testing Aligned with User Stories\n Define acceptance criteria for each user story, with tests designed around these \ncriteria.\n Continuous Feedback and Improvement"}
{"id": "pdf::Ch2 TestProcess::2141", "page_id": "pdf::Ch2 TestProcess", "title": "Ch2 TestProcess.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch2 TestProcess.pdf", "section": "Ch2 TestProcess.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/T1YQwI0Gvi1Qi5kwEO6czKSGnFf", "source_type": "pdf", "n_chars": 657, "text": "each user story, with tests designed around these \ncriteria.\n Continuous Feedback and Improvement\n Use daily builds and continuous integration (CI) to automate tests\n Automation as the Backbone\n Test Pyramid:\n High volume of unit tests (fast, low-cost, code-level coverage).\n Middle: Integration/API tests (validate module interactions).\n Top: Fewer end-to-end (UI) tests (simulate user workflows, costly but critical for \nkey paths).\nTesting in Agile Model\n\n19\nTest Pyramid\n\n20\n DevOps is a development methodology \n bridging the gap between Development and Operations\n emphasizing communication and collaboration, continuous integration, quality"}
{"id": "pdf::Ch2 TestProcess::2142", "page_id": "pdf::Ch2 TestProcess", "title": "Ch2 TestProcess.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch2 TestProcess.pdf", "section": "Ch2 TestProcess.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/T1YQwI0Gvi1Qi5kwEO6czKSGnFf", "source_type": "pdf", "n_chars": 699, "text": "ment and Operations\n emphasizing communication and collaboration, continuous integration, quality \nassurance and delivery with automated deployment utilizing a set of development \npractices.\n DevOps extends Agile by emphasizing deep integration of development and operations, \nusing automation tools and continuous delivery (CI/CD) to streamline the entire \nworkflow from code to production.\n Agile Development emphasizes iterative processes and collaboration in \ndevelopment, enabling rapid response to requirements through short cycles, \ncustomer feedback, and cross-functional teamwork.\n6. DevOps\nImprove software delivery efficiency and quality\n\n21\nWhy DEVOPS?\nCustomer\nCustomer \nRequirements"}
{"id": "pdf::Ch2 TestProcess::2143", "page_id": "pdf::Ch2 TestProcess", "title": "Ch2 TestProcess.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch2 TestProcess.pdf", "section": "Ch2 TestProcess.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/T1YQwI0Gvi1Qi5kwEO6czKSGnFf", "source_type": "pdf", "n_chars": 687, "text": "ps\nImprove software delivery efficiency and quality\n\n21\nWhy DEVOPS?\nCustomer\nCustomer \nRequirements\nDevelopment\n& Testing Operations Team\nGAP\nFocuses on speed and innovation Prioritizes stability and reliability\nWorks in iterative cycles with frequent code changes Manages infrastructure, deployments, and incident response, often favoring cautious, infrequent changes\nblame Ops for deployment bottlenecks blame Dev for unstable code\nversion control and testing frameworks Monitoring systems , configuration management\n\n22\nWhy DEVOPS?\nCustomer\nCustomer \nRequirements\nDeployment \nServers\nContinuous Integration \n&\nContinuous Deployment\n● Pipeline : Set of automated processes and tools"}
{"id": "pdf::Ch2 TestProcess::2144", "page_id": "pdf::Ch2 TestProcess", "title": "Ch2 TestProcess.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch2 TestProcess.pdf", "section": "Ch2 TestProcess.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/T1YQwI0Gvi1Qi5kwEO6czKSGnFf", "source_type": "pdf", "n_chars": 326, "text": "s\nContinuous Integration \n&\nContinuous Deployment\n● Pipeline : Set of automated processes and tools\n● Code analysis, testing and maintenance\n● Integrate code changes by each developer to keep \nmain branch up to date.\n● Continuous deployment after each commit.\n● Automatic rollbacks if the deployment fails\n\n23\nTools for DevOps"}
{"id": "pdf::Ch3 TestPrinciple::2145", "page_id": "pdf::Ch3 TestPrinciple", "title": "Ch3 TestPrinciple.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch3 TestPrinciple.pdf", "section": "Ch3 TestPrinciple.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/KeBjwYxVVicQpxkAJvDcC7THnob", "source_type": "pdf", "n_chars": 684, "text": "Principles of Software Testing\nYanxia Liu cslyx@scut.edu.cn\nSpring, 2025\n1\n\nContents\nØStatic and Dynamic Verification\nØBlack and White Box Testing\nØTest Artefacts\n2\n\n3\n1.Static and Dynamic Verification\nØStatic Verification does not require the execution of the software code, while \nDynamic Verification does.\nØStatic Verification can be as straightforward as having someone of training \nand experience reading through the code to search for faults.\nØDynamic Verification confirms the operation of a program by executing it.\n\n4\nStatic Verification\nØStatic verification may include static analysis, code reviews, checks against coding \nstandards and guidelines, and other techniques."}
{"id": "pdf::Ch3 TestPrinciple::2146", "page_id": "pdf::Ch3 TestPrinciple", "title": "Ch3 TestPrinciple.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch3 TestPrinciple.pdf", "section": "Ch3 TestPrinciple.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/KeBjwYxVVicQpxkAJvDcC7THnob", "source_type": "pdf", "n_chars": 677, "text": "atic analysis, code reviews, checks against coding \nstandards and guidelines, and other techniques.\nØIt could be a formal approach consisting of symbolic verification of the translation \nbetween the specification and the source code\n\n5\nDynamic Verification\nØThe Input values are provided as inputs to the \nprogram during execution\nØThe Actual Outputs are collected from the \nprogram, and then they are compared with the \nExpected Outputs.\nØTest Cases are created that guide the selection of suitable Test Data (consisting \nof Input values and Expected Output values\n\n6\n2. Black and White Box Testing\nØBlack Box testing is based entirely on the program specification and aims to"}
{"id": "pdf::Ch3 TestPrinciple::2147", "page_id": "pdf::Ch3 TestPrinciple", "title": "Ch3 TestPrinciple.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch3 TestPrinciple.pdf", "section": "Ch3 TestPrinciple.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/KeBjwYxVVicQpxkAJvDcC7THnob", "source_type": "pdf", "n_chars": 657, "text": "nd White Box Testing\nØBlack Box testing is based entirely on the program specification and aims to \nverify that the program meets the specified requirements\nØWhite box testing uses the implementation of the software to derive the tests. \nThe tests are designed to exercise some aspect of the program code\n\n7\nCompare Black and White Box Testing\nØWhite box testing does not find faultsrelated to missing functionality. These areerrors of omission.\nØBlack box testing does not find faultsrelated to extra functionality. These areerrors of commission.\n\n8\nCoverage Interpretation\nBlack-Box testing provides for coverage of thespecification, but not full coverage"}
{"id": "pdf::Ch3 TestPrinciple::2148", "page_id": "pdf::Ch3 TestPrinciple", "title": "Ch3 TestPrinciple.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch3 TestPrinciple.pdf", "section": "Ch3 TestPrinciple.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/KeBjwYxVVicQpxkAJvDcC7THnob", "source_type": "pdf", "n_chars": 678, "text": "Interpretation\nBlack-Box testing provides for coverage of thespecification, but not full coverage \nof theimplementation. That is, there may be code inthe implementation that \nproduces results notstated in the specification.\nWhite-Box testing provides for coverage of theimplementation, but not of the \nspecification. Thatis there may be behaviour stated in thespecification for which \nthere is no code in theimplementation.\n\n9\nBlack-BoxTesting\nThe basic principle of Black-Box Testingcan be expressed in a number of\ndifferent ways:\n1. Test against the specification.\n2. Use test coverage criteria based on the\nspecification.\n3. Develop test cases derived from the\nspecification."}
{"id": "pdf::Ch3 TestPrinciple::2149", "page_id": "pdf::Ch3 TestPrinciple", "title": "Ch3 TestPrinciple.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch3 TestPrinciple.pdf", "section": "Ch3 TestPrinciple.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/KeBjwYxVVicQpxkAJvDcC7THnob", "source_type": "pdf", "n_chars": 688, "text": "coverage criteria based on the\nspecification.\n3. Develop test cases derived from the\nspecification.\n4. “Exercise” the specification.\n\n\n10\nWhite-BoxTesting\nThe basic principle of White-Box Testing canbe expressed:\n1. Test against the implementation\n2. Use test coverage criteria based on the\nimplementation\n3. Develop test cases derived from the\nimplementation\n4. “Exercise” implementation\n\n\n11\nFault Insertion\nØThe most common technique is referred to as Mutation Testing where faults (or\n“mutations”) are inserted into the source code, and the code checked to see if the\nmutant produces a different output.\nØIn Strong Mutation Testing this check is carried out by executing the code.\n\n12"}
{"id": "pdf::Ch3 TestPrinciple::2150", "page_id": "pdf::Ch3 TestPrinciple", "title": "Ch3 TestPrinciple.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch3 TestPrinciple.pdf", "section": "Ch3 TestPrinciple.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/KeBjwYxVVicQpxkAJvDcC7THnob", "source_type": "pdf", "n_chars": 677, "text": "different output.\nØIn Strong Mutation Testing this check is carried out by executing the code.\n\n12\nOffut’s 5 sufficient mutations\nØABS: -ABS(), ABS(), 0\nØAOR: + - * / %\nØLCR: (a && b) or (a || b) ->\n (a other-op b), (a), (b)\n(a op true), (a op false), (true op b), (false op b)\nØROR: (a cmp b) ->\n a [< <= > >= != ==] b, true, false\nØUOI: insert “! - ++ --” before expression\n• AOR (arithmetic operator replacement)\nReplace one of the arithmetic operators by one \nof the others\n• LCR (logical connector replacement)\nReplace one of the logical operators by one of \nthe others\n• ROR (Relational operator replacement) \nReplace one of the relational operators by one \nof the others"}
{"id": "pdf::Ch3 TestPrinciple::2151", "page_id": "pdf::Ch3 TestPrinciple", "title": "Ch3 TestPrinciple.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch3 TestPrinciple.pdf", "section": "Ch3 TestPrinciple.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/KeBjwYxVVicQpxkAJvDcC7THnob", "source_type": "pdf", "n_chars": 201, "text": "OR (Relational operator replacement) \nReplace one of the relational operators by one \nof the others\n• UOI (unary operator insertion) Insert a unary \noperator before the expression\n\n13\n3. Test Artifacts"}
{"id": "pdf::Ch4 BlackBox::2152", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 689, "text": "Black-Box Testing\nYanxia Liu cslyx@scut.edu.cn\nSpring, 2025\n1\n\nContents\nØEquivalence Partitioning\nØBoundary Value Analysis\nØCombinational Testing\nØSequence and Value\nØRandom Testing and Error Guessing\nØScenarioTesting\n2\n\n3\n1.Equivalence Partitioning\nØExample\n Consider a method,\n – boolean isNegative(int x),\n This accepts a single Java \nint as its input parameter. The \nmethod returns true if x is \nnegative, otherwise false.\nTwo equivalence partitions for the parameter x can be identified:\n– 1. Integer.MIN VA L U E . .-1\n– 2. 0..Integer.MAX V ALUE\nØAn Equivalence Partition (EP) is a range of values for a parameter for which \nthe specification states equivalent processing.\n\n4"}
{"id": "pdf::Ch4 BlackBox::2153", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 614, "text": "is a range of values for a parameter for which \nthe specification states equivalent processing.\n\n4\nØThese specification-based ranges are called Equivalence Partitions – according \nto the specification, any value in the partition is processed equivalently to any \nother value\nEquivalence Partitioning\nØEvery value for every parameter must be in one equivalence partition.\n§– There are no values between partitions.\n§– The natural range of the parameter provides the upper and lower limits for partitions \nwhere not specified otherwise.\nØEquivalence Partitions are useful for testing the fundamental operation of the"}
{"id": "pdf::Ch4 BlackBox::2154", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 691, "text": "ecified otherwise.\nØEquivalence Partitions are useful for testing the fundamental operation of the \nsoftware: if the software fails using EP values, then it is not worth testing with \nmore sophisticated techniques until the faults have been fixed.\n\n5\nEquivalence Partitioning\nSystem\nOutputs\nInvalid inputs Valid inputs\nØEquivalence partitioning is the process \nof methodically reducing the huge (or \ninfinite) set of possible test cases into a \nsmall, but equally effective, set of test \ncases.\nA\nB\nA1,A2…,An\nA2 \nrepresents \nA\n\n6\nØValidequivalenceClass\n§ A meaningful set of data in an input field. \n§ Used to verify whether the system function and performance can be correctly implemented."}
{"id": "pdf::Ch4 BlackBox::2155", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 624, "text": "field. \n§ Used to verify whether the system function and performance can be correctly implemented.\nØInvalid equivalence class\n§ A meaningless set of data in an input field. \n§Used to test the fault tolerance of the system.\nEquivalence Class\nEquivalence classes form a partition of a set.\nPartition: collection of mutually disjoint subsets whose union is the entire set.\n\n7\nSteps to identify the test cases\n1.Identify the inputs/outputs from the specification\neg. input fields in a form, inputs to command line programs, outputs-messages, calculations etc.\n2.Identify the equivalence classes for the inputs/outputs identified"}
{"id": "pdf::Ch4 BlackBox::2156", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 683, "text": "ts-messages, calculations etc.\n2.Identify the equivalence classes for the inputs/outputs identified\n§For arange, 1 validclass(within the range) and two invalidclass (one outside each end of the \nrange)\n§If the input is aset of validvalues, 1 validclass(from within the set) and 1 invalidclass \n(outside the set)\n§Ifthe input is a set of values and the program treats input values differently, 1 valid class for \neach allowed input and 1 invalid class (the set of all disallowed inputs).\n\n\n8\n§For aBoolean, 1 validclass (true) and 1 invalidclass (false)\n§For amandatoryinput, empty(invalid) and valid inputs.\n§If the input must follow rules, 1 valid class (conforming to the rule) and"}
{"id": "pdf::Ch4 BlackBox::2157", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 685, "text": "lid) and valid inputs.\n§If the input must follow rules, 1 valid class (conforming to the rule) and \nseveral invalid classes (violating the rule from different ways)\n3. Divide each input into equivalence classesand form equivalence class \ntable, specifying a unique ID for each equivalence class.\nSteps to identify the test cases\n\n9\n(1) Equivalence classes table examples\nInput value : Score of students , range from 0~100 \nInput value : Required Courses , {Database, Network, OS }\nParametersValid Equivalence ClassInvalid Equivalence Class\nScore 0<=X<= 100 (1) X < 0 (2)X > 100 (3)\nParametersValid Equivalence ClassInvalid Equivalence Class\nCourse"}
{"id": "pdf::Ch4 BlackBox::2158", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 684, "text": "(2)X > 100 (3)\nParametersValid Equivalence ClassInvalid Equivalence Class\nCourse \nDatabase (1)\nOthers (4)Network (2)\nOS (3)\n\n10\n(1) Equivalence classes table examples\nInput value : ExternalDial PhoneNumber, “9 - eight digits”\nParametersValid Equivalence ClassInvalid Equivalence Class\nPhone \nnumber \n9 \ndigits string \nbeginning with “9”. \n(1)\nNot beginning with “9”. (2)\nNot digits string (3)\nNot 9 (4)\n\n11\n(2) Design Test cases covering equivalence classes\nInput value : ExternalDial, “9 - eight digits”\nParametersValid Equivalence ClassInvalid Equivalence Class\nPhone \nnumber \n9"}
{"id": "pdf::Ch4 BlackBox::2159", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 672, "text": "al, “9 - eight digits”\nParametersValid Equivalence ClassInvalid Equivalence Class\nPhone \nnumber \n9 \ndigits string \nbeginning with “9”. \n(1)\nNot beginning with “9”. (2)\nNot digits string (3)\nNot 9 (4)\nTestcaseIDPhoneNumberExpected\nOutput\nActual\nOutput\nEquivalenceClasses\nCoverage\n1 912345678 OK （1）\n2 812349878 Error (2)\n3 9abcdefgh Error (3)\n4 93465 Error (4)\n\n12\n4. Write test cases for the valid class followed by invalid class. There could be \nan overlap sometimes.\nØTest cases for valid classes\n§Each cover as many valid classes as possible, and repeat until all valid classes are \ncovered by thetest cases set."}
{"id": "pdf::Ch4 BlackBox::2160", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 675, "text": "y valid classes as possible, and repeat until all valid classes are \ncovered by thetest cases set.\nØTest cases for invalid classes\n§Each only cover one invalid class (include one invalid value and the remaining \nvalues will all be valid).\nSteps to identify the test cases\n\n13\nProgram: \n F (a,b,c) with input domains A, B, and C.\nElements of partition denoted as : \nEquivalence Class Testing\nEquivalence testing: use one element from each equivalence class.\n\n14\nWeak Equivalence Class Testing\nØUse one variable from each equivalence class in a test case.\nØ#test cases = #classes in the partition with the largest numbering of subsets.\n\n15\nStrong Equivalence Class Testing"}
{"id": "pdf::Ch4 BlackBox::2161", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 661, "text": "asses in the partition with the largest numbering of subsets.\n\n15\nStrong Equivalence Class Testing\nØBased on Cartesian product of the partition subsets.\nØGeneralization: equivalence classes on outputs\nØWe cover all the equivalence classes, and we have one of each possible \ncombination of inputs.\n\n16\nThe Nextdate Program\nIt is a function that returns the date of the day after the input date.\n The month, day and year values in the input date have numerical values with the following \nconstraints.\n\n\n17\nTraditional Equivalence Class Testing\nBetter Equivalence relation?\nLook at the functionality of the program, that is,what must be done to input date?\nNote:"}
{"id": "pdf::Ch4 BlackBox::2162", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 695, "text": "relation?\nLook at the functionality of the program, that is,what must be done to input date?\nNote: \n§A year is a leap year if it is divisible by 4, unless it is a century year.\n§Century years are leap years only if they are multiples of 400. So 2000 is a leap year while \nthe year 1900 is not a leap year.\n\n18\nPostulate the following equivalence classes:\nInput\nClasses\nOutput\nClasses\n(m1,m2,m3) X (d1,d2,d3,d4) X (y1,y2)\n3 x 4 x 2 = 24 test cases\nStrong Equivalence Class Test Cases\n\n19\nExamplesfrom Book (p.60)\nDescription\n A program for airline seat \nreservation takes two inputs. \nThe first is the number of free seats \n The second is the number of seats \nrequired. Both numbers are integers."}
{"id": "pdf::Ch4 BlackBox::2163", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 657, "text": "he number of free seats \n The second is the number of seats \nrequired. Both numbers are integers.\n\n\n20\n\n\n21\n\n\n22\nCommentonEquivalence Partitioning\nØEquivalence Partitions provide a minimum level of blackboxtesting. At least one \nvalue has been tested fromevery input and output partition, using a minimum\nnumber of tests.\nØThese tests are likely to ensure that the basic dataprocessing aspects of the code \nare correct. But they donot exercise the different decisions made in the code.\nØThis is important, as decisions are a frequent source ofmistakes in the code. These \ndecisions generally reflectthe boundaries of input partitions, or the identification"}
{"id": "pdf::Ch4 BlackBox::2164", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 632, "text": "code. These \ndecisions generally reflectthe boundaries of input partitions, or the identification \nofcombinations of inputs requiring particular processing.\n\n23\nStrengths&Weakness\nØProvides a good basic level of testing.\nØWell suited to data processing applicationswhere input variables may be \neasilyidentified and take on distinct valuesallowing easy partitioning.\nØProvides a structured means for identifyingbasic Test Cases.\nØCorrect processing at the edges ofpartitions is not tested.\nØCombinations of inputs are not tested.\nØThe technique does not provide analgorithm for finding the partitions or\nselecting the test data.\n\n24"}
{"id": "pdf::Ch4 BlackBox::2165", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 685, "text": "e technique does not provide analgorithm for finding the partitions or\nselecting the test data.\n\n24\nØBoundary conditions are situations at the edge of the planned operational \nlimits of the software.\nE.g., negative to zero to positive numbers, exceeding the input field length of a form, \netc.\nØChoose input data that lie on the boundary when formulating equivalence \npartitions.\nTest the valid data just inside the boundary\nTest the last possible valid data\nTest the invalid data just outside the boundary\nØSecurity flaws such as buffer overflow attacks exploit boundaries of array \nbuffers.\n2.BoundaryValueAnalysis\nEquivalence \nclass\nOuterpoint\nInnerpoint\n\n25\nPicking Boundary Values"}
{"id": "pdf::Ch4 BlackBox::2166", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 692, "text": "ffers.\n2.BoundaryValueAnalysis\nEquivalence \nclass\nOuterpoint\nInnerpoint\n\n25\nPicking Boundary Values\n1.Every parameter has a boundary value at thetop and bottom of \nevery equivalence partition.\n2.For a contiguous data type, the successor tothe value at the top \nof one partition must bethe value at the bottom of the next.\n3.The natural range of the parameter providesthe ultimate \nmaximum and minimum values.\n\n\n26\nØThe 0, 1 and last loops in the Loop structure\nØThe first and last elements of the array\nØMaximum and minimum values allowed for a variable type\nØThe first and last nodes of a linked list\nØThe maximum and minimum number of acceptable characters, such asin \nusername and password"}
{"id": "pdf::Ch4 BlackBox::2167", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 675, "text": "ked list\nØThe maximum and minimum number of acceptable characters, such asin \nusername and password\nØThe first row, first column, last row and last column of the table/report\nCommon Boundary Values\nØTypically, software testing involves several types of boundary checks: numbers, \ncharacters, position, weight, size, speed, orientation, dimension, space, and so on.\nØAccordingly, the boundary values of the above types should be in: Max/min, \nfirst/last, up/down, fastest/slowest, highest/lowest, shortest/longest, empty/full, etc.\n\n27\nExamplesfrom Book (p.64)\n\n\n28\nØTest Data values are provided by thetechnique.\nØTests focus on areas where faults aremore likely to be found."}
{"id": "pdf::Ch4 BlackBox::2168", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 647, "text": "values are provided by thetechnique.\nØTests focus on areas where faults aremore likely to be found.\nØCombinations of inputs are not tested.\nStrengths&Weakness\n§For each variable, select five values\n1)Min The minimum\n2)Min+ Slightly above the minimum\n3)Nor Normal\n4)Max– Slightly below the maximum\n5)Max Maximum\n\n29\n3.Combinational Testing\nØThere are a number of different techniques for identifying relevant \ncombinations, such as Cause-Effect Graphs, Decision Tables and Truth Tables.\nØThe analysis of combinations involves identifying all the different combinations \nof input causes to the software and their associated output effects."}
{"id": "pdf::Ch4 BlackBox::2169", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 636, "text": "ll the different combinations \nof input causes to the software and their associated output effects.\nØThe causes and effects are described as logical statements (or predicates), based \non the specification of the software. These expressions specify the conditions \nrequired for a particular variable to cause a particular effect.\n\n30\nTruth Table\nØTo test all the different behaviors of the program, a Truth Table is created. The \ninputs (“Causes”) and outputs (“Effects”) are specified as Boolean expressions \n(using predicate logic).\nØCombinations of the causes are the inputs that will generate a particular response \nfrom the program."}
{"id": "pdf::Ch4 BlackBox::2170", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 666, "text": "mbinations of the causes are the inputs that will generate a particular response \nfrom the program.\nØTest Cases are then constructed that will cover all possible combinations of \nCause and Effect. For N independent causes, there will therefore be a total of 2N \ndifferent combinations. The Truth Table specifies how the software should \nbehave for each combination.\n\n31\nExample A – isNegative()\n§Rule 1 states that if x<0, then the return value is true.\n§Rule 2 states that if !(x<0), then the return value is false.\nEach column is referred to as a Rule in the Truth Table – Each Rule is a different test case.\n\n32\nExample B – largest()\n\n\n33\n“Don’t Care” Conditions"}
{"id": "pdf::Ch4 BlackBox::2171", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 685, "text": "Table – Each Rule is a different test case.\n\n32\nExample B – largest()\n\n\n33\n“Don’t Care” Conditions\nØ“Don’t care” conditions exist where the value of a cause has no impact on the \neffect.\nØThese “Don’t care” conditions are used to reduce the number of rules where the \nsame output will be generated irrespective of whether the Cause is true or false. \nØIn the worst case, if there are no “Don’t care” conditions, N Causes will create 2N \nRules. \nØ“Don’t care” conditions are represented by a “*” for the causes in a Truth Table.\n\n34\nExample C – condIsNegt()\nThe number of tests is reduced using ‘don’t-care” conditions where the value of\na particular cause has no effect on the output."}
{"id": "pdf::Ch4 BlackBox::2172", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 684, "text": "ed using ‘don’t-care” conditions where the value of\na particular cause has no effect on the output.\nCombinational Testing\ndoes not test all the combinations of causes\n\n35\nStrengths&Weakness\nØExercises combinations of test data\nØThe truth tables can sometime be very large. The solution is to identify \nsubproblems and develop separate tables for each. \nØVery dependent on the quality of the specification - more detail means more \ncauses and effects, which takes more time to test; less detail means less \ncauses and effects, but less effective testing.\n\n36\nDecision Tables - Wikipedia\nØprecise yet compact way to model complicated logic \nØAssociate conditions with actions to perform"}
{"id": "pdf::Ch4 BlackBox::2173", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 655, "text": "Øprecise yet compact way to model complicated logic \nØAssociate conditions with actions to perform\nØCan associate many independent conditions with several actions in an elegant way\n\n37\nDecision Tables - Terminology\n\n\n38\nDecision Tables - Printer Troubleshooting DT\n\n\n39\nDecision Tables – NextDate DT\nØThe NextDate problem illustrates the correspondence between equivalence classes \nand decision table structure\nØThe NextDate problem illustrates the problem of dependencies in the input \ndomain\nØDecision tables can highlight such dependencies\nØImpossible dates can be clearly marked as a separate action\n\n40\nNextDate Equivalence Classes – for 1st try\n\n\n41"}
{"id": "pdf::Ch4 BlackBox::2174", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 668, "text": "ates can be clearly marked as a separate action\n\n40\nNextDate Equivalence Classes – for 1st try\n\n\n41\nNextDate Decision Table – mutually exclusive conditions\n\n\n42\nNextDate Decision Table – (1st try - partial)\n\n\n43\nNextDate Decision Table – (2st try - partial)\n\n44\nNew Equivalence Classes – for 2rd try\n\n\n45\nNextDate DT (3rd try - part 1)\n\n\n46\nNextDate DT (3rd try - part 2)\n\n\n47\nReduced NextDate DT (3rd try - part 1)\n\n48\nNextDate Test Cases\n\n49\nØDecision Table testing is most appropriate for programswhere\n§ There is a lot of decision making\n§ There are important logical relationships among inputvariables\n§ There are calculations involving subsets of input variables"}
{"id": "pdf::Ch4 BlackBox::2175", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 693, "text": "al relationships among inputvariables\n§ There are calculations involving subsets of input variables\n§ There is complex computation logic (high cyclomaticcomplexity)\nØIt has been shown that equivalence classes and decisiontables can \nbe closely related.\nComment\n\n50\nØSequences of values are important where the software preserves state.\nØThe response to a particular input value can vary depending on the state, and \nthe state depends on the previous sequence of values.\nØThe normal approach for analyzing sequences is by using a State Diagram to \nidentify the states the software can be in, and the response (“Action”) to \neach input (“Event”) in each state.\n4. Sequence and Value testing \n\n51"}
{"id": "pdf::Ch4 BlackBox::2176", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 686, "text": "the response (“Action”) to \neach input (“Event”) in each state.\n4. Sequence and Value testing \n\n51\nState Diagram\n\n\n52\nØState\n An abstract situation in the life cycle of a system entity\n(for instance, the contents of an object)\nØTransition\n An allowable two-state sequence. Caused by an event\nØEvent\n An input or a time interval\nØGuard\n Predicate expression associated with an event, stating a Boolean \nrestriction for a transition to fire\nØAction\n The output that follows an event\nBuilding blocks of a state diagram\n\n\n53\n\n\n54\nImportance of State-based testing\nØState-based testing is important for object-oriented software\n In particular for real-time/control systems and communications"}
{"id": "pdf::Ch4 BlackBox::2177", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 657, "text": "ortant for object-oriented software\n In particular for real-time/control systems and communications\n§Classes, clusters, subsystem or system\n§Behavior bugs due to complex and implicit structure\nØWe are interested in testing the behavior of many different types of systems, \nincluding event-driven software systems.\nØStatechart can model event-driven behavior. If we can express the system under test \nas a statechart, we can generate test cases for its behavior.\n\n55\n\n\n56\n\n\n57\nState Diagram Analysis\n Test case = sequence of input events\nØAll-events coverage: each event of the state machine is included in the test suite \n(is part of at least one test case)"}
{"id": "pdf::Ch4 BlackBox::2178", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 671, "text": "each event of the state machine is included in the test suite \n(is part of at least one test case)\nØAll-states coverage: each state of the state machine is exercised at least once \nduring testing, by some test case in the test suite\nØAll–transitions coverage. each transition is exercised at least once\n– implies (subsumes) all-events coverage, all-states coverage\n– ”minimum acceptable strategy for responsible testing of a state machine”\nØAll –paths coverage from entry to exit. In the diagram there is no exit state so all \npaths from entry to every state need to be identified.\nØAll –circuits coverage in the diagram that start and end in the same state\n\n58\n\n\n59\n\n\n60"}
{"id": "pdf::Ch4 BlackBox::2179", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 653, "text": "entified.\nØAll –circuits coverage in the diagram that start and end in the same state\n\n58\n\n\n59\n\n\n60\nØTest data is generated using random number generators. The distribution \nmay be uniform, or chosen to mimic, in a statistical sense, the type of inputs \nthat the program will receive in real use.\nØIf the specification is clearly written and thorough, then it should be possible \nto find the set(s) of possible input values.\nØThe goal is to achieve a “reasonable” coverage of the possible values for \neach input parameter, based on its distribution. This can be determined \nheuristically (using, for example, 10 random values), or based on a statistical"}
{"id": "pdf::Ch4 BlackBox::2180", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 698, "text": "can be determined \nheuristically (using, for example, 10 random values), or based on a statistical \nsample size determined from the required confidence in the coverage.\n5. Random Testing and Error Guessing\nRandom Testing \n\n61\nØEach Test Case is represented by a set of(random) input values, one for each \nparameter.\nØIf the test is fully automated, then each TestCase is represented by a \ndistribution of valuesfor a particular parameter.\nØThis will normally include the upper and lowerlimits, and the distribution to \nbe used betweenthese limits to select a random value.\nRandom Testing\n\n62\nØRandom Test Data generation is straightforward toimplement and leads to a \nfast generation of Test Cases."}
{"id": "pdf::Ch4 BlackBox::2181", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 655, "text": "Test Data generation is straightforward toimplement and leads to a \nfast generation of Test Cases.\nØIf the distribution/histogram of the real-world input data isknown, then this \nprovides a mathematical basis forselecting a set of input test case values.\nØThe measured test failure rate then provides anindication of the expected \nfailure rate in use.\nØRandom data selection is sometimes used for stability testing,to ensure that \nno input data value causes the software tocrash or raise unexpected \nexceptions. This technique is easyto implement in an automated manner, \nbut is unlikely to findfaults except in low-quality code.\nRandom TestingComment\n\n63"}
{"id": "pdf::Ch4 BlackBox::2182", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 633, "text": "omated manner, \nbut is unlikely to findfaults except in low-quality code.\nRandom TestingComment\n\n63\nØThis is an ad-hoc approach, based on intuition andexperience. \nØTest data is selected that is likely to expose faultsin the code. Some typical \nexamples of inputs likely to causeproblems are:\n– Empty or null strings, arrays, lists, and class references. These may find code that \ndoes not check for empty or non-null values before using them.\n– Zero as a value, or as a count of instances or occurrences. These may find divide-by-\nzero faults.\n– Spaces or null characters in strings. This may find code that does not process strings"}
{"id": "pdf::Ch4 BlackBox::2183", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 668, "text": "o faults.\n– Spaces or null characters in strings. This may find code that does not process strings \ncorrectly or does not trim whitespace before trying to extract data from the string.\n– Negative numbers. These may find faults in code that only expects to receive \npositive numbers.\nØThe goal is to cover as many values as possible which in the experience of \nthe tester are likely to expose faults in the code\nError Guessing\n\n64\nError Guessing\nA program that sorts a List(such as an array) can presumably has the \nfollowing cases that require special testing:\n1) The input Listis empty\n2) The List contains only one element\n3) All elements in the Listhave been sorted"}
{"id": "pdf::Ch4 BlackBox::2184", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 643, "text": "nput Listis empty\n2) The List contains only one element\n3) All elements in the Listhave been sorted\n4) Listhas been arranged in reverse order\n5) Some or all elements in the Listare the same\n\n65\nØThe tester selects values which are likely to produce errors. Each value is a \nTest Case.\nØThis technique can produce both normal and error Test Cases. The values \nselected are those that are likely to expose faults in the code, they are not \nnecessarily illegal values.\nØInput Test Data is selected, based on Test Cases which are not yet covered. \nAs with the other test techniques, error cases should be executed \nindividually.\nError Guessing\n\n66"}
{"id": "pdf::Ch4 BlackBox::2185", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 697, "text": "As with the other test techniques, error cases should be executed \nindividually.\nError Guessing\n\n66\nØWith experienced testers, this can be a very effective complement to other \ntesting techniques.\nØIt depends on how well the testers know the types of mistakes that the \ndevelopers are likely to make, or mistakes that have a high impact on the \nfinal product.\nError Guessing Comment\n\n67\nØScenario Testingis aSoftware Testing Techniquethat uses scenarios i.e. \nspeculative stories to help the tester work through a complicated problem or test \nsystem. \nØScenario testing is performed to ensure that the end-to-end function of software \nand all the process flow of the software are working properly."}
{"id": "pdf::Ch4 BlackBox::2186", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 665, "text": "he end-to-end function of software \nand all the process flow of the software are working properly. \nØIn scenario testing, the testers assume themselves to be the end users and find the \nreal-world scenarios or use cases which can be carried out on the software by the \nend user. \n6. Scenario Testing\n\n68\nUse case Scenario\nØActor \n§something with behavior, such as a person \n§(identified by role), computer system, or organization; e.g. \na cashier, a player.\nØScenario (aka a use case instance) \n§a specific sequence of actions and interactions between \nactors and the system \n§it is one particular story of using a system, or one path \nthrough a use case.\nØUse case"}
{"id": "pdf::Ch4 BlackBox::2187", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 688, "text": "system \n§it is one particular story of using a system, or one path \nthrough a use case.\nØUse case \n§a collection of related success and failure scenarios that \ndescribe an actor using a system to support a goal. \n\n\n69\nBasic flow and Alternative flow\nØBasic Flow\n§The simplest path through the use case, that is, without any error, \nthe program directly from the beginning to the end of the process.\n§The most used operation process by most users, reflecting the \nmain functions and processes of the software. \n§There is only one base flow for a business, and the base flow has \nonly one start and one end.\nØAlternative Flow\n§Start with a base flow, perform under a specific condition, and"}
{"id": "pdf::Ch4 BlackBox::2188", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 665, "text": "rt and one end.\nØAlternative Flow\n§Start with a base flow, perform under a specific condition, and \nthen rejoin the base flow (such as alternative flows 1 and 3); \n§Or originate from another alternative flow (such as alternative \nflow 2); \n§Use cases can also be terminated without being added to the base \nflow (such as alternative flows 2 and 4)\n§reflecting various exception and error conditions.\nUseCase Start\nAlternative \nFlow 3\nAlternative \nFlow 4\nAlternative \nFlow 1\nAlternative \nFlow 2\nUseCase End\n\n70\nUse case Scenario\n1.Scenario 1: Basic flow\n2.Scenario 2: Basic flow → Alternative flow 1\n3.Scenario 3: Basic flow → Alternative flow 1 → Alternative flow 2"}
{"id": "pdf::Ch4 BlackBox::2189", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 649, "text": "Basic flow → Alternative flow 1\n3.Scenario 3: Basic flow → Alternative flow 1 → Alternative flow 2\n4.Scenario 4: Basic flow → Alternative flow 3\n5.Scenario 5: Basic flow → Alternative flow 3→ Alternative flow 1\n6.Scenario 6: Basic Flow → Alternative flow 3→ Alternative flow 1→ Alternative flow 2\n7.Scenario 7: Basic flow → Alternate flow 4\n8.Scenario 8: Basic flow → Alternative flow 3→ Alternative flow 4\nIn order to simplify the analysis of the problem, only oneloop executionof the alternative \nflow 3 is considered\n\n71\nScenarioTestingSteps\nScenario Testing Goal\nØSimulate the user to complete the operation of normal functions and core business"}
{"id": "pdf::Ch4 BlackBox::2190", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 660, "text": "io Testing Goal\nØSimulate the user to complete the operation of normal functions and core business \nlogic to verify the correctness of software functions;\nØSimulate the main errors in user operation to verify the abnormal error handling \nability of software.\nAlternative flows, like the program execution paths, will cause the scenario explosion.\nTypical scenarios need to be selected for testing. \n(1) One and only one scenario contains the basic flow;\n(2) The minimum number of scenarios: the total of basic flows and alternative flows;\n(3) For an alternative flow: at least one scenario covering it, which try to avoid \ncovering other alternative flows\n\n72"}
{"id": "pdf::Ch4 BlackBox::2191", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 622, "text": "flow: at least one scenario covering it, which try to avoid \ncovering other alternative flows\n\n72\n(1)According to the specification, describe the basic flow and alternative flow of \nthe software under test.\n(2) Construct different scenarios to meet the requirements of test completeness and \nno redundancy.\n(3) Design corresponding test cases for each scenario.\n(4) Re-examine all generated test cases and remove redundant test cases. After the \ntest cases are determined, the test data values are determined for each test case.\nScenarioTestingSteps\n\n73\nScenarioTestingExample\nA hotel system supports online reservations."}
{"id": "pdf::Ch4 BlackBox::2192", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 677, "text": "case.\nScenarioTestingSteps\n\n73\nScenarioTestingExample\nA hotel system supports online reservations. \nCustomers visit the website for room reservation operation, select a reservation \ndate, suitable room, online reservation.\n In this case, you need to login to the system using your personal account.\n After the login succeeds, you can make the deposit payment. \nAfter the deposit is paid successfully, the room reservation form will be \ngenerated to complete the whole room reservation process. \nThe system allows a reservation period of 30 days and a deposit of 400 dollars.\n\n74\n(1) Determine the basic flow and alternative flow\ntype description type description\nThe basic flow"}
{"id": "pdf::Ch4 BlackBox::2193", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 695, "text": "(1) Determine the basic flow and alternative flow\ntype description type description\nThe basic flow\nSelect booking date Alternative flow 1 The reservation date is overdue\nChoose the room Alternative flow 2 No spare room\nLogintotheaccount Alternative flow 3 Account does not exist\nPaythedeposit Alternative flow 4 Password iswrong\nGenerate reservation order Alternative flow 5 The account balance is insufficient\nScenarioTestingExample\n\n75\n(2) Generate different scenarios based on the base flow and alternative flow\nScenario 1 (Successful reservation) : Basic flow.\nScenario 2 (Reservation date overdue) : Basic flow, alternate flow 1.\nScenario 3 (no spare room) : Basic flow, alternative flow 2."}
{"id": "pdf::Ch4 BlackBox::2194", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 630, "text": "erdue) : Basic flow, alternate flow 1.\nScenario 3 (no spare room) : Basic flow, alternative flow 2.\nScenario 4 (account does not exist) : Basic flow, alternate flow 3.\nScenario 5 (password error) : Basic flow, alternate flow 4.\nScenario 6 (Insufficient account balance) : Basic flow, alternate flow 5.\nScenarioTestingExample\n\n76\n(3) Test case design\n “V” ：condition must be Valid for the base flow to be executed\n “ I” ：the desired alternative flow will be activated if the condition is Invalid\n “N /a” (not applicable) ：the condition does not apply to the test case.\nTCScenario/Condition DateRoomAccount PWBalance Expected Output"}
{"id": "pdf::Ch4 BlackBox::2195", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 680, "text": "ion does not apply to the test case.\nTCScenario/Condition DateRoomAccount PWBalance Expected Output\n1 Scenario 1 (Successful reservation) V V V V V \"reservation succeeded\" the account balance is decreased\n2 Scenario 2 (Reservation date overdue) I n/a n/a n/a n/a \"Invalid reservation date”Reselect the date\n3 Scenario 3 (no spare room) V I n/a n/a n/a “Reservation room is full”Reselect the date\n4 Scenario 4 (account does not exist) V V I n/a n/a “Account does not exist”Enter the account again\n5 Scenario 5 (password error) V V V I n/a “Password error”Enter the password again\n6 Scenario 6 (Insufficient account balance) V V V V I “Insufficient account balance， please recharge”"}
{"id": "pdf::Ch4 BlackBox::2196", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 696, "text": "Scenario 6 (Insufficient account balance) V V V V I “Insufficient account balance， please recharge”\nScenarioTestingExample\n\n77\n(4) Determine the test case data values\nAssume that User1 is a registered user and the password is MyPass. User2 is an unregistered user.\nTC Scenario/Condition Date Room Account PW Balance Expected Output\n1 Scenario1 A valid Date Not full User1 MyPass 800 Successful \n2 Scenario2 An overdue Date n/a n/a n/a n/a Overdue\n3 Scenario3 A valid Date Full n/a n/a n/a No Room\n4 Scenario4 A valid Date Not full User2 n/a n/a Account Error\n5 Scenario5 A valid Date Not full User1 NoPass n/a Password Error\n6 Scenario6 A valid Date Not full User1 MyPass 200 Insufficient Balance"}
{"id": "pdf::Ch4 BlackBox::2197", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 642, "text": "1 NoPass n/a Password Error\n6 Scenario6 A valid Date Not full User1 MyPass 200 Insufficient Balance\nScenarioTestingExample\n\n78\n7.Summary：Strategies on BlackBox Testing\n1.For the specific input field in the specific function page, the refined test is carried \nout, using equivalence class and boundary value; Use static testing to check \nbuttons, links, content, images, etc;\n2.If the function description contains a combination of input conditions, and the \nbusiness logic is complex, decision table can be used.\n3.Boundary value analysis should be considered in any case, as it is one of the \nmost effective methods to find software defects."}
{"id": "pdf::Ch4 BlackBox::2198", "page_id": "pdf::Ch4 BlackBox", "title": "Ch4 BlackBox.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch4 BlackBox.pdf", "section": "Ch4 BlackBox.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/Qv71w6Ig1iOBu3k6HuKcJwRtnUt", "source_type": "pdf", "n_chars": 333, "text": "ld be considered in any case, as it is one of the \nmost effective methods to find software defects.\n4.Test cases can be expanded by error guessing method, and the valuable \nexperience of test engineers is emphasized.\n5.For the system with clear business process, the scenario testing can be used \nthroughout the whole testing process"}
{"id": "pdf::Ch5-1 WhiteBox-LogicCoverage::2199", "page_id": "pdf::Ch5-1 WhiteBox-LogicCoverage", "title": "Ch5-1 WhiteBox-LogicCoverage.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch5-1 WhiteBox-LogicCoverage.pdf", "section": "Ch5-1 WhiteBox-LogicCoverage.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7Wvwq6U5ioyelkR4O2cmnP9nwh", "source_type": "pdf", "n_chars": 690, "text": "White-Box Testing\nYanxia Liu cslyx@scut.edu.cn\nSpring, 2025\n1\n\nContents\nØControlFlowTesting\n§Statement Coverage\n§Decision Coverage\n§Condition Coverage\n§Decision Condition Coverage\n§Condition Combination Coverage\n§PathCoverage\n§Basis Path Testing\n2\n\n3\nControlFlowTesting\nØControl-flow testing is a structural testing strategy that uses the program’s \ncontrol flow as a model.\nØRequires the tester to have a clear understanding of the logical structure of the \nprogram, and even to be able to master all the details of the source program.\nØMost applicable tonew software for unit testing.\n\n4\n1.StatementCoverage\nØDesign test cases andworkout input values required to ensure that every source"}
{"id": "pdf::Ch5-1 WhiteBox-LogicCoverage::2200", "page_id": "pdf::Ch5-1 WhiteBox-LogicCoverage", "title": "Ch5-1 WhiteBox-LogicCoverage.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch5-1 WhiteBox-LogicCoverage.pdf", "section": "Ch5-1 WhiteBox-LogicCoverage.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7Wvwq6U5ioyelkR4O2cmnP9nwh", "source_type": "pdf", "n_chars": 694, "text": ".StatementCoverage\nØDesign test cases andworkout input values required to ensure that every source \ncodestatement is executed.\nØAlso known as point coverage\nØThe weakest logical coverage, beused interoperatively with other testingmethods.\n\n5\n(A>1) and (B=0)\n(A=2) or (X>1)\nX = X / A\nX=X+1\nT\nT\nF\nF\nb\nc\ne\na\n1\ns\nd\n2\n3\n4\n5\n6\n7\npublic static float Example(float A,B,X){\n \n if ( A>1 && B==0 ) \n X= X / A;\n if (A==2 || X>1) \n X=X+1;\n return X;\n}\nI. A=2, B= 0, X=4 ---- sacbed\nProgramFlowGraph Source Code\nTestCase Input (A，B，X) Path Output ( X )\n1 2,0,4 sacbed 3\n\n6\nIf there is a problem with the logical operation of the two decisions, like:\nØAND à OR \nØOR à AND"}
{"id": "pdf::Ch5-1 WhiteBox-LogicCoverage::2201", "page_id": "pdf::Ch5-1 WhiteBox-LogicCoverage", "title": "Ch5-1 WhiteBox-LogicCoverage.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch5-1 WhiteBox-LogicCoverage.pdf", "section": "Ch5-1 WhiteBox-LogicCoverage.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7Wvwq6U5ioyelkR4O2cmnP9nwh", "source_type": "pdf", "n_chars": 680, "text": "ere is a problem with the logical operation of the two decisions, like:\nØAND à OR \nØOR à AND\nØX>1 à X>0\n……\nthe above test case cannot detect it.\nThe statement coverage seem like it validates every statement comprehensively, \nbut it's quite weak. Why?\nStatementCoverage\n\n7\n2.DecisionCoverage (Branch Coverage)\nØDesign test cases andworkout input values required to ensure that every source \ncode branch is taken.\nØEach true and false branch of the program is executed at least once\nØAlso known as edge coverage\n\n8\nØEach true and false branch is executed at least once\n(A>1) and (B=0)\n(A=2) or (X>1)\nX = X / A\nX=X+1\nT\nT\nF\nF\nb\nc\ne\na\n1\ns\nd\n2\n3\n4\n5\n6\n7\nI: A=3, B=0,X=1: sacbd"}
{"id": "pdf::Ch5-1 WhiteBox-LogicCoverage::2202", "page_id": "pdf::Ch5-1 WhiteBox-LogicCoverage", "title": "Ch5-1 WhiteBox-LogicCoverage.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch5-1 WhiteBox-LogicCoverage.pdf", "section": "Ch5-1 WhiteBox-LogicCoverage.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7Wvwq6U5ioyelkR4O2cmnP9nwh", "source_type": "pdf", "n_chars": 699, "text": ") and (B=0)\n(A=2) or (X>1)\nX = X / A\nX=X+1\nT\nT\nF\nF\nb\nc\ne\na\n1\ns\nd\n2\n3\n4\n5\n6\n7\nI: A=3, B=0,X=1: sacbd\nII: A=2, B=1,X=1: sabed\nIs there other test cases combination satisfying \nbranch coverage?\nDoes it cover all the statement?\n\n9\nDecisionCoverage (Branch Coverage)\nØTest cases that satisfy decision coverage definitely satisfy statement coverage.\nØDecision Coverage is better than statement coverage, but it's still weak logical \ncoverage.\nØX>1 à X<1\nthe above test cases cannot detect it.\nØDecision coverage does not guarantee that errors in decision conditions can be \ndetected. Therefore, stronger logical coverage criteria are needed to test the \ninternal conditions.\n\n10\n3. Condition Coverage"}
{"id": "pdf::Ch5-1 WhiteBox-LogicCoverage::2203", "page_id": "pdf::Ch5-1 WhiteBox-LogicCoverage", "title": "Ch5-1 WhiteBox-LogicCoverage.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch5-1 WhiteBox-LogicCoverage.pdf", "section": "Ch5-1 WhiteBox-LogicCoverage.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7Wvwq6U5ioyelkR4O2cmnP9nwh", "source_type": "pdf", "n_chars": 684, "text": "er logical coverage criteria are needed to test the \ninternal conditions.\n\n10\n3. Condition Coverage\nØA complex decision is formed from multiple (Boolean) conditions.\nØCondition Coverage extends Branch Coverage by ensuring that, for complex \ndecisions, each condition within the decision is tested for its true and false values.\nØ There is a caveat: it is not necessary that the decision itself take on true and false \nvalues!\nØTest data is selected to ensure that every condition in every decision takes on the \nvalue true and false.\n\n11\nDecision Expression #1\nIf A>1 True T1 \n FalseT1\nIf B==0 True T2 \n FalseT2\nDecision Expression #2"}
{"id": "pdf::Ch5-1 WhiteBox-LogicCoverage::2204", "page_id": "pdf::Ch5-1 WhiteBox-LogicCoverage", "title": "Ch5-1 WhiteBox-LogicCoverage.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch5-1 WhiteBox-LogicCoverage.pdf", "section": "Ch5-1 WhiteBox-LogicCoverage.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7Wvwq6U5ioyelkR4O2cmnP9nwh", "source_type": "pdf", "n_chars": 671, "text": "FalseT1\nIf B==0 True T2 \n FalseT2\nDecision Expression #2\nIf A==2 True T3 \n FalseT3\nIf X>1 True T4 \n FalseT4\n(A>1) and (B=0)\n(A=2) or (X>1)\nX = X / A\nX=X+1\nT\nT\nF\nF\nb\nc\ne\na\n1\ns\nd\n2\n3\n4\n5\n6\n7\nØEach true and false condition in each \ndecision is executed at least once\n\n12\n(A>1) and (B=0)\n(A=2) or (X>1)\nX = X / A\nX=X+1\nT\nT\nF\nF\nb\nc\ne\na\n1\ns\nd\n2\n3\n4\n5\n6\n7\n(A>1) (A≤1)\n(B=0) (B≠0)\n(A=2)(A≠2)\n(X>1)(X≤1)\nTestCasePath Condition Output\nXABX\nTrue False\nT1\nT2\nT3\nT4\nT1\nT2\nT3\nT4\n\n13\n(A>1) and (B=0)\n(A=2) or (X>1)\nX = X / A\nX=X+1\nT\nT\nF\nF\nb\nc\ne\na\n1\ns\nd\n2\n3\n4\n5\n6\n7\n(A>1) (A≤1)\n(B=0) (B≠0)\n(A=2)(A≠2)"}
{"id": "pdf::Ch5-1 WhiteBox-LogicCoverage::2205", "page_id": "pdf::Ch5-1 WhiteBox-LogicCoverage", "title": "Ch5-1 WhiteBox-LogicCoverage.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch5-1 WhiteBox-LogicCoverage.pdf", "section": "Ch5-1 WhiteBox-LogicCoverage.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7Wvwq6U5ioyelkR4O2cmnP9nwh", "source_type": "pdf", "n_chars": 693, "text": "(A=2) or (X>1)\nX = X / A\nX=X+1\nT\nT\nF\nF\nb\nc\ne\na\n1\ns\nd\n2\n3\n4\n5\n6\n7\n(A>1) (A≤1)\n(B=0) (B≠0)\n(A=2)(A≠2)\n(X>1)(X≤1)\nⅡ: A=1, B=1,X=1: sabd\nⅠ: A=2, B=0,X=4: sacbed\nTestCase Path Condition X\nABX\n204 sacbed T1,T2,T3,T4 3\n111 sabd T1,T2,T3,T4 1Decision coverage is satisfiedWhether decision coverage is satisfied\nSituation #1\n\n14\n(A>1) and (B=0)\n(A=2) or (X>1)\nX = X / A\nX=X+1\nT\nT\nF\nF\nb\nc\ne\na\n1\ns\nd\n2\n3\n4\n5\n6\n7\n(A>1) (A≤1)\n(B=0) (B≠0)\n(A=2)(A≠2)\n(X>1)(X≤1)\nⅣ: A=1, B=1,X=2: sabed\nⅢ: A=2, B=0,X=1: sacbed\nTestCase Path Condition X\nABX\n201 sacbed T1,T2,T3,T4 1.5\n112 sabed T1,T2,T3,T4 3Decision coverage isn’t satisfied\nSituation #2\n\n15\n(A>1) (A≤1)\n(B=0) (B≠0)\n(A=2)(A≠2)\n(X>1)(X≤1)\nⅥ: A=2, B=1,X=1: sabed"}
{"id": "pdf::Ch5-1 WhiteBox-LogicCoverage::2206", "page_id": "pdf::Ch5-1 WhiteBox-LogicCoverage", "title": "Ch5-1 WhiteBox-LogicCoverage.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch5-1 WhiteBox-LogicCoverage.pdf", "section": "Ch5-1 WhiteBox-LogicCoverage.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7Wvwq6U5ioyelkR4O2cmnP9nwh", "source_type": "pdf", "n_chars": 652, "text": "n’t satisfied\nSituation #2\n\n15\n(A>1) (A≤1)\n(B=0) (B≠0)\n(A=2)(A≠2)\n(X>1)(X≤1)\nⅥ: A=2, B=1,X=1: sabed\nTestCase\nPath Conditions X\nABX\n103 sabed T1,T2,T3,T4 4\n211 sabed T1,T2,T3,T4 2\nⅤ: A=1, B=0,X=3: sabed\n(A>1) and (B=0)\n(A=2) or (X>1)\nX = X / A\nX=X+1\nT\nT\nF\nF\nb\nc\ne\na\n1\ns\nd\n2\n3\n4\n5\n6\n7\nNeither decision coverage \nnor statement coverage is satisfied\nSituation #3\n\n16\nCondition Coverage\nØStrength: focuses on condition outcomesand thus extends Branch coverage\nØWeakness: may fail to achieve branchcoverage as it is not necessary for the\ndecision itself to take on true and falseoutcomes.\nconsider thetest cases\n(1) a=true and b= false\n(2) a=false and b=true"}
{"id": "pdf::Ch5-1 WhiteBox-LogicCoverage::2207", "page_id": "pdf::Ch5-1 WhiteBox-LogicCoverage", "title": "Ch5-1 WhiteBox-LogicCoverage.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch5-1 WhiteBox-LogicCoverage.pdf", "section": "Ch5-1 WhiteBox-LogicCoverage.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7Wvwq6U5ioyelkR4O2cmnP9nwh", "source_type": "pdf", "n_chars": 681, "text": "ke on true and falseoutcomes.\nconsider thetest cases\n(1) a=true and b= false\n(2) a=false and b=true\nEach condition (a and b) have taken on thevalues of true and false but the \ndecision itselfalways evaluates to false. \nThus, BranchCoverage has not been achieved\n\n17\n4. Decision/Condition Coverage\nØGenerate test data such that all conditions in adecision take on both outcomes (if \npossible) atleast once and exercise the true and falseoutcomes of every decision.\n§Each decision has True and False test cases\n§In addition, each condition in a decision has True and False test cases (if possible)\nØ It is a combination of Condition Coverage and Branch Testing. It uses the same test"}
{"id": "pdf::Ch5-1 WhiteBox-LogicCoverage::2208", "page_id": "pdf::Ch5-1 WhiteBox-LogicCoverage", "title": "Ch5-1 WhiteBox-LogicCoverage.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch5-1 WhiteBox-LogicCoverage.pdf", "section": "Ch5-1 WhiteBox-LogicCoverage.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7Wvwq6U5ioyelkR4O2cmnP9nwh", "source_type": "pdf", "n_chars": 666, "text": "if possible)\nØ It is a combination of Condition Coverage and Branch Testing. It uses the same test \ndata as for Condition Coverage but must additionally ensure that each branch or \ndecision takes a true or false outcome.\n§Single condition decision: 2 test cases\n§2-condition decisions: 2+ test cases\n\n18\n(A>1) and (B=0)\n(A=2) or (X>1)\nX = X / A\nX=X+1\nT\nT\nF\nF\nb\nc\ne\na\n1\ns\nd\n2\n3\n4\n5\n6\n7\nTestCase\nPath Condition Decision#1,#2 XABX\n204sacbed T1,T2,T3,T4 T, T 3\n111 sabd T1 ,T2, T3, T4 F,F 1\nSituation #1\n\n19\nAirline Seat reservation Example\n\n\n20\nEach Boolean value for each decision\nIn addition, each Boolean value for each condition\nAirline Seat reservation Example\n\n21"}
{"id": "pdf::Ch5-1 WhiteBox-LogicCoverage::2209", "page_id": "pdf::Ch5-1 WhiteBox-LogicCoverage", "title": "Ch5-1 WhiteBox-LogicCoverage.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch5-1 WhiteBox-LogicCoverage.pdf", "section": "Ch5-1 WhiteBox-LogicCoverage.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7Wvwq6U5ioyelkR4O2cmnP9nwh", "source_type": "pdf", "n_chars": 691, "text": "ch decision\nIn addition, each Boolean value for each condition\nAirline Seat reservation Example\n\n21\nAirline Seat reservation ----Test Cases\n\n22\nDecision/Condition Coverage Comments\nØSteps\n§Identify all the decisions in the program\n§List all the conditions\n§Generate the test data to cover the above decisions and conditions\nØAddresses one of deficiencies of condition coverage by forcing each branch to \nbe exercised .\n§Conditions can be masked due to the potential lazy evaluation of compound conditions, \ne.g.\n while(!(found) && (i<=x))\n§For the decision to be true, both conditions must evaluate to true. \n§For the decision to be false, only the first condition need to evaluate to false."}
{"id": "pdf::Ch5-1 WhiteBox-LogicCoverage::2210", "page_id": "pdf::Ch5-1 WhiteBox-LogicCoverage", "title": "Ch5-1 WhiteBox-LogicCoverage.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch5-1 WhiteBox-LogicCoverage.pdf", "section": "Ch5-1 WhiteBox-LogicCoverage.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7Wvwq6U5ioyelkR4O2cmnP9nwh", "source_type": "pdf", "n_chars": 688, "text": "uate to true. \n§For the decision to be false, only the first condition need to evaluate to false.\n \nØThus, the consequence of the second condition evaluating to false might be \ninsufficiently considered.\n\n23\nDecision/Condition Coverage Strengths & Weaknesses\nØThe true and false outcomes of every decision and every condition are covered\nØThis gives stronger coverage than just Condition Coverage or Decision \nCoverage\nØEven though every decision is tested, and every condition is tested, not every \npossible combination of conditions is tested.\n\n24\n5. Condition Combination Coverage\nØTests are generated to cause every possible combination of conditions for every \ndecision to be tested."}
{"id": "pdf::Ch5-1 WhiteBox-LogicCoverage::2211", "page_id": "pdf::Ch5-1 WhiteBox-LogicCoverage", "title": "Ch5-1 WhiteBox-LogicCoverage.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch5-1 WhiteBox-LogicCoverage.pdf", "section": "Ch5-1 WhiteBox-LogicCoverage.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7Wvwq6U5ioyelkR4O2cmnP9nwh", "source_type": "pdf", "n_chars": 698, "text": "s are generated to cause every possible combination of conditions for every \ndecision to be tested.\nØThe goal is to achieve 100% coverage of every decision and 100% coverage of \nevery condition.\nØA Truth-Table is the best way to identify all the possible combinations of values.\n\n25\nEvery combination of conditions for every \ndecision be taken at least once\n(A>1) and (B=0)\n(A=2) or (X>1)\nX = X / A\nX=X+1\nT\nT\nF\nF\nb\nc\ne\na\n1\ns\nd\n2\n3\n4\n5\n6\n7\n①A＞1, B＝0， TT\n②A＞1, B≠0， TF\n③A≯1, B＝0， FT\n④A≯1, B≠0， FF\n⑤A＝2, X＞1， TT\n⑥A＝2, X≯1， TF\n⑦A≠2, X＞1， FT\n⑧A≠2, X≯1， FF\n\n26\n(A>1) and (B=0)\n(A=2) or (X>1)\nX = X / A\nX=X+1\nT\nT\nF\nF\nb\nc\ne\na\n1\ns\nd\n2\n3\n4\n5\n6\n7\nI. A=2,B=0,X=4\nII. A=2,B=1,X=1"}
{"id": "pdf::Ch5-1 WhiteBox-LogicCoverage::2212", "page_id": "pdf::Ch5-1 WhiteBox-LogicCoverage", "title": "Ch5-1 WhiteBox-LogicCoverage.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch5-1 WhiteBox-LogicCoverage.pdf", "section": "Ch5-1 WhiteBox-LogicCoverage.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7Wvwq6U5ioyelkR4O2cmnP9nwh", "source_type": "pdf", "n_chars": 662, "text": "=0)\n(A=2) or (X>1)\nX = X / A\nX=X+1\nT\nT\nF\nF\nb\nc\ne\na\n1\ns\nd\n2\n3\n4\n5\n6\n7\nI. A=2,B=0,X=4\nII. A=2,B=1,X=1\nIII. A=1,B=0,X=2\nIV . A=1,B=1,X=1\nI: sacbed\nII: sabed\nIII: sabed\nIV: sabd\nPath\nMeeting the criteria of conditional combination coverage means meeting the criteria of \ndecision coverage, conditional coverage and decision/conditional coverage.\n1. A＞1, B＝0\n2. A＞1, B≠0\n3. A≯1, B＝0\n4. A≯1, B≠0\n5. A＝2, X＞1\n6. A＝2, X≯1\n7. A≠2, X＞1\n8. A≠2, X≯1\n\n27\nTestCase\nPath Conditions ConditionCombination Decisions Expected OutputAB X\n20 4 sacbedT1,T2,T3,T4 1, 5 TT 3\n21 1 sabedT1,T2,T3,T4 2, 6 FT 2\n10 2 sabedT1,T2,T3,T4 3, 7 FT 3\n11 1 sabd T1,T2,T3,T4 4, 8 FF 1"}
{"id": "pdf::Ch5-1 WhiteBox-LogicCoverage::2213", "page_id": "pdf::Ch5-1 WhiteBox-LogicCoverage", "title": "Ch5-1 WhiteBox-LogicCoverage.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch5-1 WhiteBox-LogicCoverage.pdf", "section": "Ch5-1 WhiteBox-LogicCoverage.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7Wvwq6U5ioyelkR4O2cmnP9nwh", "source_type": "pdf", "n_chars": 685, "text": "T 3\n21 1 sabedT1,T2,T3,T4 2, 6 FT 2\n10 2 sabedT1,T2,T3,T4 3, 7 FT 3\n11 1 sabd T1,T2,T3,T4 4, 8 FF 1\nFour testcases allow each of the eight condition combinations \nto occur at least once: \n\n28\n(A>1) and (B=0)\n(A=2) or (X>1)\nX = X / A\nX=X+1\nT\nT\nF\nF\nb\nc\ne\na\n1\ns\nd\n2\n3\n4\n5\n6\n7\nI. A=2,B=0,X=4\nII. A=2,B=1,X=1\nIII. A=1,B=0,X=2\nIV . A=1,B=1,X=1\nI: sacbed\nII: sabed\nIII: sabed\nIV: sabd\nPath\nNot every path in the program can be executed , for example, sacbd.\n1. A＞1, B＝0\n2. A＞1, B≠0\n3. A≯1, B＝0\n4. A≯1, B≠0\n5. A＝2, X＞1\n6. A＝2, X≯1\n7. A≠2, X＞1\n8. A≠2, X≯1\n\n29\nAirline Seat reservation Example\n\n\n30\nAirline Seat reservation Example\n\n31\nAirline Seat reservation ----Test Cases\n\n32"}
{"id": "pdf::Ch5-1 WhiteBox-LogicCoverage::2214", "page_id": "pdf::Ch5-1 WhiteBox-LogicCoverage", "title": "Ch5-1 WhiteBox-LogicCoverage.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch5-1 WhiteBox-LogicCoverage.pdf", "section": "Ch5-1 WhiteBox-LogicCoverage.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7Wvwq6U5ioyelkR4O2cmnP9nwh", "source_type": "pdf", "n_chars": 644, "text": "ation Example\n\n\n30\nAirline Seat reservation Example\n\n31\nAirline Seat reservation ----Test Cases\n\n32\nCondition Combination Coverage Strengths & Weaknesses\nØTests all possible combinations of conditions in every decision\nØCan be expensive: n conditions in a decision give 2n test cases\nØCan be difficult to determine the required input parameter values\nØEven though multiple condition testing covers every possible combination of \nconditions in a decision, it does not cause every possible execution path to be taken\n\n33\nThe program Grade combines an exam and coursework mark into a single \ngrade. The values for exam and coursework are integers."}
{"id": "pdf::Ch5-1 WhiteBox-LogicCoverage::2215", "page_id": "pdf::Ch5-1 WhiteBox-LogicCoverage", "title": "Ch5-1 WhiteBox-LogicCoverage.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch5-1 WhiteBox-LogicCoverage.pdf", "section": "Ch5-1 WhiteBox-LogicCoverage.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7Wvwq6U5ioyelkR4O2cmnP9nwh", "source_type": "pdf", "n_chars": 677, "text": "an exam and coursework mark into a single \ngrade. The values for exam and coursework are integers. \nIf the exam or coursework mark is less than 50 then the grade returned is a ‘Fail’. \nTo pass the course with a ‘Pass, C’, the student must score between 50 and 60 in the \nexam, and at least 50 in the coursework. \nThey will pass the course with ‘Pass, B’, if they score over 60 in the exam and 50 in \nthe coursework. \nIn addition to this, if the average of the exam and the coursework is at least 70, then \nthey are awarded a ‘Pass, A’. Input values that are less than 0 or greater than 100 for \neither the exam or coursework are invalid and the program will return a message to"}
{"id": "pdf::Ch5-1 WhiteBox-LogicCoverage::2216", "page_id": "pdf::Ch5-1 WhiteBox-LogicCoverage", "title": "Ch5-1 WhiteBox-LogicCoverage.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch5-1 WhiteBox-LogicCoverage.pdf", "section": "Ch5-1 WhiteBox-LogicCoverage.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/E7Wvwq6U5ioyelkR4O2cmnP9nwh", "source_type": "pdf", "n_chars": 529, "text": "r than 100 for \neither the exam or coursework are invalid and the program will return a message to \nsay ‘Marks out of range’.\nEX. Grade Specification\n\n34\n1)Please draw the program flow chart \nof the above code \n2)Please list all the decisions and their \nconditions of the above program. \n3) Please use the Condition \nCombination coverage testing \nmethod to design the testcases for \nthe above code \n\n35\n\n\n36\n\n\n37\n\n\n38\nTest Cases and Test Data\n\n39\nTest Cases and Test Data\n\n40\nTest Cases and Test Data\n\n41\nTest Cases and Test Data"}
{"id": "pdf::Ch5-2 WhiteBox-PathCoverage::2217", "page_id": "pdf::Ch5-2 WhiteBox-PathCoverage", "title": "Ch5-2 WhiteBox-PathCoverage.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch5-2 WhiteBox-PathCoverage.pdf", "section": "Ch5-2 WhiteBox-PathCoverage.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/UVqYwkTjqiVJeLkBDbncdDJTnjg", "source_type": "pdf", "n_chars": 674, "text": "White-Box Testing\nYanxia Liu cslyx@scut.edu.cn\nSpring, 2025\n1\n\nContents\nØControlFlowTesting\n§Statement Coverage\n§Decision Coverage\n§Condition Coverage\n§Decision Condition Coverage\n§Condition Combination Coverage\n§PathCoverage\n§Basis Path Testing\n2\n\n3\n1. Control Flow Graphs (CFGs)\nBeing able to create a Control Flow Graphs is essential for path testing \ntechniques.\nØDirected graph G(V , E)\n§V is set of vertices\n§E is set of edges, E = V*V\nØRepresent the flow of control\n§Each node represents one or more statements\n§Each edge represents a ‘jump’ or ‘branch’\n§Two exits=a decision (True or False)\n\n\n4\nControl Flow Graphs for Sequence \n\n\n5\nCFG for Selection (if-then)\n\n\n6"}
{"id": "pdf::Ch5-2 WhiteBox-PathCoverage::2218", "page_id": "pdf::Ch5-2 WhiteBox-PathCoverage", "title": "Ch5-2 WhiteBox-PathCoverage.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch5-2 WhiteBox-PathCoverage.pdf", "section": "Ch5-2 WhiteBox-PathCoverage.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/UVqYwkTjqiVJeLkBDbncdDJTnjg", "source_type": "pdf", "n_chars": 694, "text": "decision (True or False)\n\n\n4\nControl Flow Graphs for Sequence \n\n\n5\nCFG for Selection (if-then)\n\n\n6\nCFG for Selection (if-then-else)\n\n\n7\nCFG for Selection (switch)\n\n\n8\nCFG for Iteration (while)\n\n\n9\nCFG for Iteration (do-while)\n\n\n10\nCFG for Iteration (for)\n\n\n11\nCFG Tips\nØIdentify all the “jump” points (decisions):\n§if, while, switch/case, for\nØStart at the top of the code\nØWork your way down to the next jump point\nØCreate a new node\nØFor each decision identify the destination node if (a) True and (b) \nfalse\nØConnect the nodes\n\n12\nExample Code\n\n\n13\nProgram Flow Graph vs. Control Flow Graph\nØControl flow Graph \nis a simplified \nprogram flow graph\nØOnly describes the \ncontrol flow of the"}
{"id": "pdf::Ch5-2 WhiteBox-PathCoverage::2219", "page_id": "pdf::Ch5-2 WhiteBox-PathCoverage", "title": "Ch5-2 WhiteBox-PathCoverage.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch5-2 WhiteBox-PathCoverage.pdf", "section": "Ch5-2 WhiteBox-PathCoverage.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/UVqYwkTjqiVJeLkBDbncdDJTnjg", "source_type": "pdf", "n_chars": 620, "text": "ØControl flow Graph \nis a simplified \nprogram flow graph\nØOnly describes the \ncontrol flow of the \nprogram\nØDoes not show the \nspecific operation \nof data and the \nspecific conditions \nof branch or loop\n(A>1) and (B=0)\n(A=2) or (X>1)\nX = X / A\nX=X+1\nT\nT\nF\nF\nb\nc\ne\na\n1\ns\nd\n2\n3\n4\n5\n6\n7\n2\n4\n1\n3\n5\n6\ns,a\nb\nd\nc\ne\n\n14\n2. Path Coverage\nØGenerate test data to exercise all the distinct paths in aprogram. This is called \n“path coverage”\nØPath coverage causes every possible path from entry toexit of the program to be \ntaken during test execution. \nØThe goal is to achieve 100% coverage of every start-to-finishpath in the code."}
{"id": "pdf::Ch5-2 WhiteBox-PathCoverage::2220", "page_id": "pdf::Ch5-2 WhiteBox-PathCoverage", "title": "Ch5-2 WhiteBox-PathCoverage.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch5-2 WhiteBox-PathCoverage.pdf", "section": "Ch5-2 WhiteBox-PathCoverage.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/UVqYwkTjqiVJeLkBDbncdDJTnjg", "source_type": "pdf", "n_chars": 654, "text": "ng test execution. \nØThe goal is to achieve 100% coverage of every start-to-finishpath in the code.\nØA path that makes i iterations through aloop is distinct from a path that makes \ni+1iterationsthrough a loop, even if the samenodes are visited in both iterations\nThus, there can be an infinite number ofpaths in some programs!\n\n15\nØNeed to limit the number of paths: choose equivalence classes of paths\nØTwo paths are considered equivalent if they differ only in the number of \nloop iterations, giving two classes of loops:\n§ one with 0 iterations\n§ one with n iterations (n > 0)\nØOther equivalence paths can also be chosen if required\nPath Coverage\n\n16"}
{"id": "pdf::Ch5-2 WhiteBox-PathCoverage::2221", "page_id": "pdf::Ch5-2 WhiteBox-PathCoverage", "title": "Ch5-2 WhiteBox-PathCoverage.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch5-2 WhiteBox-PathCoverage.pdf", "section": "Ch5-2 WhiteBox-PathCoverage.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/UVqYwkTjqiVJeLkBDbncdDJTnjg", "source_type": "pdf", "n_chars": 691, "text": "with n iterations (n > 0)\nØOther equivalence paths can also be chosen if required\nPath Coverage\n\n16\nThe CFG of a program can be described by a regular expression that \nuses the following operations:\n . is the concatenation of a sequence of nodes\n + is a decision in the graph (i.e. an if statement)\n * is iteration (0 or more times, e.g. a while statement)\nPath Expression\n\n17\nPath Expression - Example\nThe CFG can be \nrepresented by\n1) i=0;\n2) while (i1 && B==0 ) \n X= X / A;\n if (A==2 || X>1) \n X=X+1;\n return X;\n}\nPath Expression: \nPaths: abd\nabed\nacbd\nacbed\na.(0+c).b.(0+e).d\n\n30\nPath Coverage – EX.\nTest Cases Paths OutputA B X X\n1 1 1 abd 1\n1 1 2 abed 2\n3 0 1 acbd 1/3\n2 0 4 acbed 4/3\nTestCase\nPath Conditions ConditionCombination Decisions Expected OutputAB X\n20 4 acbed T1,T2,T3,T4 1, 5 TT 3\n21 1 abed T1,T2,T3,T4 2, 6 FT 2\n10 2 abed T1,T2,T3,T4 3, 7 FT 3\n11 1 abd T1,T2,T3,T4 4, 8 FF 1\nCompared with Condition"}
{"id": "pdf::Ch5-2 WhiteBox-PathCoverage::2226", "page_id": "pdf::Ch5-2 WhiteBox-PathCoverage", "title": "Ch5-2 WhiteBox-PathCoverage.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch5-2 WhiteBox-PathCoverage.pdf", "section": "Ch5-2 WhiteBox-PathCoverage.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/UVqYwkTjqiVJeLkBDbncdDJTnjg", "source_type": "pdf", "n_chars": 676, "text": "4 2, 6 FT 2\n10 2 abed T1,T2,T3,T4 3, 7 FT 3\n11 1 abd T1,T2,T3,T4 4, 8 FF 1\nCompared with Condition \nCombination coverage:\n\n31\nPath Coverage – Strengths/Weaknesses\nØIt does create combinations of paths not exercised by other methods\n§Creating and executing tests for all possible paths results in 100% \nstatement coverage and 100% branch coverage.\nØHowever, it can be computationally intensive if the program is complex \nand many paths are found.\nØAlso, it does not explicitly evaluate the conditions in each decision.\nØIf path coverage and condition combination coverage are combined, test \ncases with stronger fault detection ability can be designed\n\n32\n3. Basis Path Testing"}
{"id": "pdf::Ch5-2 WhiteBox-PathCoverage::2227", "page_id": "pdf::Ch5-2 WhiteBox-PathCoverage", "title": "Ch5-2 WhiteBox-PathCoverage.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch5-2 WhiteBox-PathCoverage.pdf", "section": "Ch5-2 WhiteBox-PathCoverage.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/UVqYwkTjqiVJeLkBDbncdDJTnjg", "source_type": "pdf", "n_chars": 679, "text": "mbined, test \ncases with stronger fault detection ability can be designed\n\n32\n3. Basis Path Testing\nØBasis Path Testing is aWhite Box Testingmethod in which test cases are \ndefined based on flows or logical paths that can be taken through the program.\nØThe objective of basis path testing is to define the number of independent paths, \nso the number of test cases needed can be defined explicitly to maximize test \ncoverage.\nØBasis path testing involves execution of all possible blocks in a program and \nachieves maximum path coverage with the least number of test cases. \n\n33\nIndependent paths\nIndependent path is defined as a path from entry to exit that has at least one edge"}
{"id": "pdf::Ch5-2 WhiteBox-PathCoverage::2228", "page_id": "pdf::Ch5-2 WhiteBox-PathCoverage", "title": "Ch5-2 WhiteBox-PathCoverage.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch5-2 WhiteBox-PathCoverage.pdf", "section": "Ch5-2 WhiteBox-PathCoverage.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/UVqYwkTjqiVJeLkBDbncdDJTnjg", "source_type": "pdf", "n_chars": 692, "text": "ependent paths\nIndependent path is defined as a path from entry to exit that has at least one edge \nwhich has not been traversed before in any other paths.\n2\n4\n1\n3\n5\n6\na\nb\nd\nc\ne\nNumber of the independent paths: 3 \nPath Expression: \nPaths: abd\nabed\nacbd\nacbed\na.(0+c).b.(0+e).d\n✓\n✓\n✓\n✗\n\n34\nSteps for Basis Path testing\n（1）Draw a control flowgraph (to determine different program paths)\n（2）CalculateCyclomatic complexity\n (metrics to determine the number of independent paths)\n（3）Find a basis set of paths \n（4）Generate test cases to exercise each path\n\n35\nvoid \nFunc\n(int \nnPosX\n, int \nnPosY\n)\n{\n \nwhile (\nnPosX\n \n> 0) \n \n{\n \n \n int \nnSum\n \n= \nnPosX\n \n+ \nnPosY\n;\n \n \n if (\nnSum\n \n> 1) \n \n \n {"}
{"id": "pdf::Ch5-2 WhiteBox-PathCoverage::2229", "page_id": "pdf::Ch5-2 WhiteBox-PathCoverage", "title": "Ch5-2 WhiteBox-PathCoverage.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch5-2 WhiteBox-PathCoverage.pdf", "section": "Ch5-2 WhiteBox-PathCoverage.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/UVqYwkTjqiVJeLkBDbncdDJTnjg", "source_type": "pdf", "n_chars": 652, "text": "while (\nnPosX\n \n> 0) \n \n{\n \n \n int \nnSum\n \n= \nnPosX\n \n+ \nnPosY\n;\n \n \n if (\nnSum\n \n> 1) \n \n \n {\n \n \n \nnPosX\n--\n;\n \nnPosY\n--\n;\n \n \n }\n \n \n else \n \n \n {\n \n \n \nif (\nnSum\n \n< \n-\n1) \nnPosX\n \n-\n= 2; \n \n \n \nelse \nnPosX\n \n-\n= 4; \n \n \n } // end of if\n \n} // end of while\n}\n7\n6\n2\n3\n1\n8\n4\n5\n11\n9\n10\nStep1：Drawa controlflowgraph\nProgram Flow Graph\n\n36\nProgram Flow Graph\n1\n7\n6\n2,3\n8\n9\n10\n11\n4,5\nNodes\nEdges\nRegions\nA region enclosed by edges and \nnodes(including outer region)\nControl Flow Graph\n7\n6\n2\n3\n1\n8\n4\n5\n11\n9\n10\nNode9 is the end of Node6, \nNode10 /Node3, Node 11/ Node 1\n3 Decision \nNodes\n1,3,6\nStep1：Drawa controlflowgraph\n\n37"}
{"id": "pdf::Ch5-2 WhiteBox-PathCoverage::2230", "page_id": "pdf::Ch5-2 WhiteBox-PathCoverage", "title": "Ch5-2 WhiteBox-PathCoverage.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch5-2 WhiteBox-PathCoverage.pdf", "section": "Ch5-2 WhiteBox-PathCoverage.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/UVqYwkTjqiVJeLkBDbncdDJTnjg", "source_type": "pdf", "n_chars": 625, "text": "of Node6, \nNode10 /Node3, Node 11/ Node 1\n3 Decision \nNodes\n1,3,6\nStep1：Drawa controlflowgraph\n\n37\nStep2: CalculateMcCabe’s Cyclomatic complexity\nØCyclomatic Complexity is a testing metric developed by Thomas J. McCabe and \nused for measuring the complexity of a software program. \n§It is a quantitative measure of independent paths in the source code of a software program.\nBasis Path Testing checks each linearly independent path through the program, whichmeans \nnumber of test cases, will be equivalent to the cyclomatic complexity of the program.\nØQuestion: \nHow many paths should be found to cover the basis path set?"}
{"id": "pdf::Ch5-2 WhiteBox-PathCoverage::2231", "page_id": "pdf::Ch5-2 WhiteBox-PathCoverage", "title": "Ch5-2 WhiteBox-PathCoverage.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch5-2 WhiteBox-PathCoverage.pdf", "section": "Ch5-2 WhiteBox-PathCoverage.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/UVqYwkTjqiVJeLkBDbncdDJTnjg", "source_type": "pdf", "n_chars": 685, "text": "omplexity of the program.\nØQuestion: \nHow many paths should be found to cover the basis path set?\nØCyclomatic Complexity provides a basis for determining the upper bound of \nthe basis path set. \nØCyclomatic Complexity is the maximum number of independent paths\n§Note: The basis path set is not unique.\n\n38\nStep2: CalculateMcCabe’s Cyclomatic complexity\nØThree methods to compute Cyclomatic Complexity V(G)\nV(G) = E - N + 2 E = Number of edges, N =Number of Nodes \nV (G) = P + 1 P = Number of decision nodes (node that contains condition)\nV(G) = R R= Number of regions\n\n39\n1\n7\n6\n2,3\n8\n9\n10\n11\n4,5\nStep2: CalculateMcCabe’s Cyclomatic complexity\n(1)V(G) =R= 4\n(2) V(G) =E-N+2 = 11-9+2=4"}
{"id": "pdf::Ch5-2 WhiteBox-PathCoverage::2232", "page_id": "pdf::Ch5-2 WhiteBox-PathCoverage", "title": "Ch5-2 WhiteBox-PathCoverage.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch5-2 WhiteBox-PathCoverage.pdf", "section": "Ch5-2 WhiteBox-PathCoverage.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/UVqYwkTjqiVJeLkBDbncdDJTnjg", "source_type": "pdf", "n_chars": 681, "text": "9\n10\n11\n4,5\nStep2: CalculateMcCabe’s Cyclomatic complexity\n(1)V(G) =R= 4\n(2) V(G) =E-N+2 = 11-9+2=4\n(3) V(G) =P+1 = 3+1=4\n\n40\nStep3: FindBasisPathSet\nIndependent path: \nA path that moves along at least one new edge from the beginning to the end\nPath 1：1-11\nPath 2：1-2-3-4-5-10-1-11\nPath 3：1-2-3-6-8-9-10-1-11\nPath 4：1-2-3-6-7-9-10-1-11\n1\n7\n6\n2,3\n8\n9\n10\n11\n4,5\nTo traverse the above path is to \nexecute all statements and all the \nbranches in the program at least once. \n\n41\nStep4: Design Test Cases\nDesign test cases to ensure the execution of each path in the basis path set.\nInput Paths Output\nnPosX nPosY nPosX nPosY\n-1 1 1 – 11 -1 1\n1 1 1 – 2 – 3 – 4 – 5 – 10 – 1 – 11 0 0\n1 -3"}
{"id": "pdf::Ch5-2 WhiteBox-PathCoverage::2233", "page_id": "pdf::Ch5-2 WhiteBox-PathCoverage", "title": "Ch5-2 WhiteBox-PathCoverage.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch5-2 WhiteBox-PathCoverage.pdf", "section": "Ch5-2 WhiteBox-PathCoverage.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/UVqYwkTjqiVJeLkBDbncdDJTnjg", "source_type": "pdf", "n_chars": 694, "text": "Paths Output\nnPosX nPosY nPosX nPosY\n-1 1 1 – 11 -1 1\n1 1 1 – 2 – 3 – 4 – 5 – 10 – 1 – 11 0 0\n1 -3\n1 – 2 – 3 – 6 – 8 \n– 9 – 10 – 1 – \n11\n-1 -3\n1 -1\n1 – 2 – 3 – 6 – 7 \n– 9 – 10 – 1 – \n11\n-3 -1\n\n46\nDiscussion :Compound condition decomposition \nØIf the compound condition is included, the compound condition should be \ndecomposed into several simple conditions.\nØEach simple condition corresponds to a node in the flow diagram. \na and b a or b\n\n(A>1) and (B=0)\n(A=2) or (X>1)\nX = X / A\nX=X+1\nT\nT\nF\nF\nb\nc\ne\na\n1\ns\nd\n2\n3\n4\n5\n6\n7\nDiscussion :Compound condition decomposition \nA>1\nX = X / A\nX=X+1\nT\nT\nF\nF\ns\ng\nB=0\nT\nA=2\nX>1\n T\nF\nF\na b\nc\nd\ne\nf\n\nDiscussion :Compound condition decomposition \nA>1\nX = X / A"}
{"id": "pdf::Ch5-2 WhiteBox-PathCoverage::2234", "page_id": "pdf::Ch5-2 WhiteBox-PathCoverage", "title": "Ch5-2 WhiteBox-PathCoverage.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch5-2 WhiteBox-PathCoverage.pdf", "section": "Ch5-2 WhiteBox-PathCoverage.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/UVqYwkTjqiVJeLkBDbncdDJTnjg", "source_type": "pdf", "n_chars": 458, "text": "F\ns\ng\nB=0\nT\nA=2\nX>1\n T\nF\nF\na b\nc\nd\ne\nf\n\nDiscussion :Compound condition decomposition \nA>1\nX = X / A\nX=X+1\nT\nT\nF\nF\ns\ng\nB=0\nT\nA=2\nX>1\n T\nF\nF\na b\nc\nd\ne\nf\na\nd\ne\nb\nf\ng\nc\nDecision Coverage = Condition Coverage\n\n49\na\nd\ne\nb\nf\ng\nc\nDiscussion :Compound condition decomposition \nPath Expression:a.(b.(c+0)+0).d.(e.(f+0)+f).g\nNo. of Paths: 9\n(ad + abd + abcd) (efg + eg + fg)\nNo. of Independent Paths:V(G) = 5\nIndependent Paths:\n1)adeg\n2)abdeg\n3)abcdeg\n4)adfg\n5)adefg"}
{"id": "pdf::Ch6 Test Documentation::2235", "page_id": "pdf::Ch6 Test Documentation", "title": "Ch6 Test Documentation.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch6 Test Documentation.pdf", "section": "Ch6 Test Documentation.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/YFodwcsJoiOtrBknZjLcPvcinbe", "source_type": "pdf", "n_chars": 657, "text": "Software Testing Documentation\nYanxia Liu cslyx@scut.edu.cn\nSpring, 2025\n1\n\n3\nSoftware Testing Documents\nList some software testing documents that we need to use/maintain regularly:\n1)Test Plan\n2)Test Design andTest Case Specification\n3)Bug Reports\n4)Test Summary Reports\n …….\nProjects that have documents have a high level of maturity.\nLack of documentation is becoming a problem for acceptance.\n\nØ Test Plan\n§Process for planning\n§Test plan components\nØ Test Case\n4\nTest Plan and Test Case\n\n5\n1. Test Plan\nØATEST PLANis a document describing software testing scope and activities. \nIt is the basis for formally testing any software / product in a project."}
{"id": "pdf::Ch6 Test Documentation::2236", "page_id": "pdf::Ch6 Test Documentation", "title": "Ch6 Test Documentation.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch6 Test Documentation.pdf", "section": "Ch6 Test Documentation.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/YFodwcsJoiOtrBknZjLcPvcinbe", "source_type": "pdf", "n_chars": 673, "text": "ng scope and activities. \nIt is the basis for formally testing any software / product in a project.\n§the scope, approach, resources and schedule of intended test activities.\nØMaster Test Plan:A single high-level test plan for a project / product that \nunifies all other test plans.\nØTesting Level Specific:Test plans for each level of testing:\n§Unit TestPlan\n§Integration TestPlan\n§System TestPlan\n§Acceptance TestPlan\nØTesting Type Specific:Test plans for specific types of testing likePerformance \nTestPlan andSecurity TestPlan.\n\n6\nTest Planning Process\n1)Define test strategy\n2)Define test system\n3)Estimate test effort\n4)Prepare and review test plan\n\n7\n1) Test Strategy"}
{"id": "pdf::Ch6 Test Documentation::2237", "page_id": "pdf::Ch6 Test Documentation", "title": "Ch6 Test Documentation.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch6 Test Documentation.pdf", "section": "Ch6 Test Documentation.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/YFodwcsJoiOtrBknZjLcPvcinbe", "source_type": "pdf", "n_chars": 663, "text": "tegy\n2)Define test system\n3)Estimate test effort\n4)Prepare and review test plan\n\n7\n1) Test Strategy\n•Approach: how to do different tasks\n•Entry/exit criteria\n•When can you start?\n•When can you stop?\n•When can you restart?\n•Automation\n•Which tools?\n•When? (e.g., only regression testing)\n•Scope\n•You cannot test everything.\n•What are the priorities?\n•most important features\n•new code\n•most difficult areas\n•most often used features\n\n8\n2) Test Systems\n•Architecture\n•Test suite: collection of tests for a related group of \nrequirements\n•Test case: smallest unit\n•Environment: physical facilities，platforms \n\n9\n3) Estimating Test Effort\n•Tasks: list of things to do"}
{"id": "pdf::Ch6 Test Documentation::2238", "page_id": "pdf::Ch6 Test Documentation", "title": "Ch6 Test Documentation.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch6 Test Documentation.pdf", "section": "Ch6 Test Documentation.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/YFodwcsJoiOtrBknZjLcPvcinbe", "source_type": "pdf", "n_chars": 696, "text": "vironment: physical facilities，platforms \n\n9\n3) Estimating Test Effort\n•Tasks: list of things to do\n•Effort estimation: previous experience, expert judgment, \ndecomposition\n•Schedule: show relationships between tasks\n•Risks: estimate likelihood and impact\n\n10\nTest Plan Components (1)\n1.Test plan identifier: unique\n2.Introduction: objectives of document/Specify constraints\n3.Test items: high-level description of inputs to testing\n (software / products and their versions)\n4.Features to be tested: list of features or requirements\n5.Features not to be tested: features you cannot test yet\nThe format and content of a software test plan vary depending on the processes, standards, and test"}
{"id": "pdf::Ch6 Test Documentation::2239", "page_id": "pdf::Ch6 Test Documentation", "title": "Ch6 Test Documentation.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch6 Test Documentation.pdf", "section": "Ch6 Test Documentation.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/YFodwcsJoiOtrBknZjLcPvcinbe", "source_type": "pdf", "n_chars": 681, "text": "he format and content of a software test plan vary depending on the processes, standards, and test \nmanagement tools being implemented. \nThe following format, which is based on IEEE standard for software test documentation, provides a \nsummary of what a test plan can / should contain.\n\n11\nTest Plan Components (2)\n6.Approach\nnhow you will test\nnmay include: phases of testing (unit, system, acceptance), \nstatic vs. dynamic methods, performance testing, \nregression testing, use of problem tracking system\n7.Item pass/fail criteria\nnWhen does a test pass?\nnWhen does the product pass?\n\n1212\nTest Plan Components (3)\n8.Suspension criteria and resumption requirements: what to do if"}
{"id": "pdf::Ch6 Test Documentation::2240", "page_id": "pdf::Ch6 Test Documentation", "title": "Ch6 Test Documentation.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch6 Test Documentation.pdf", "section": "Ch6 Test Documentation.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/YFodwcsJoiOtrBknZjLcPvcinbe", "source_type": "pdf", "n_chars": 653, "text": "s?\n\n1212\nTest Plan Components (3)\n8.Suspension criteria and resumption requirements: what to do if \nbugs prevent progress\n9.Test deliverables: all outputs of testing\n Test Case/Defects Report/ Test Report…\n9.Environmental needs: hardware and software/network\n any testing or related tools.\n10.Responsibilities: who does what/each team / role / individual.\n\n13\nTest Plan Components (4)\n13.Staffing and training needs: list people or types of people\n14.Schedule: milestones\n15.Risks and contingencies: matrix here\n•the risks that have been identified.\n•the mitigation plan and the contingency plan for each risk.\n16.Approvals: signatures\n\n14\n2. TestCase"}
{"id": "pdf::Ch6 Test Documentation::2241", "page_id": "pdf::Ch6 Test Documentation", "title": "Ch6 Test Documentation.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch6 Test Documentation.pdf", "section": "Ch6 Test Documentation.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/YFodwcsJoiOtrBknZjLcPvcinbe", "source_type": "pdf", "n_chars": 686, "text": "he mitigation plan and the contingency plan for each risk.\n16.Approvals: signatures\n\n14\n2. TestCase\nØATEST CASEis a documented set of preconditions (prerequisites), procedures \n(inputs / actions) and postconditions (expected results) which a tester uses to \ndetermine whether a system under test satisfies requirements or works \ncorrectly. \nØA test case can have one or multipletest scripts. \n§A sequence of instructions for the execution of a test\nØA collection of test cases is called atest suite.\n\n15\n\n\nØBug Report\nØTest Summary Report\n16\nBug Report & Test Summary Report\n\n17\n3. Bug Report\nØA bug report isa document that outlines information about what’s \nwrong with the software."}
{"id": "pdf::Ch6 Test Documentation::2242", "page_id": "pdf::Ch6 Test Documentation", "title": "Ch6 Test Documentation.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch6 Test Documentation.pdf", "section": "Ch6 Test Documentation.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/YFodwcsJoiOtrBknZjLcPvcinbe", "source_type": "pdf", "n_chars": 619, "text": "Report\nØA bug report isa document that outlines information about what’s \nwrong with the software. \nØIt lists the reasons or seen errors to point out what exactly is viewed as \nwrong, and also includes a request and/or details for how to address it.\nØA bug report needs to be clear, actionable and simple to complete.\nØThe point of writing a defect report (bug report) is to get bugs fixed.\n“This is what we have, this is what \nwe should have instead, so fix it.”\n\n19\nImportant Features in Bug Report\n1) Bug Number/id\nA Bug number or an identification number The developer can easily check if a particular bug has been"}
{"id": "pdf::Ch6 Test Documentation::2243", "page_id": "pdf::Ch6 Test Documentation", "title": "Ch6 Test Documentation.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch6 Test Documentation.pdf", "section": "Ch6 Test Documentation.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/YFodwcsJoiOtrBknZjLcPvcinbe", "source_type": "pdf", "n_chars": 689, "text": "Bug number or an identification number The developer can easily check if a particular bug has been \nfixed or not. It makes the whole testing and retesting process smoother and easier.\n2) Bug Title\nThe Bug title should be suggestive enough that the reader can understand it. A clear bug title makes it \neasy to understand and the reader can know if the bug has been reported earlier or has been fixed.\n3) Report Type\n One or more field which will describe the bug type, including:\n§ Coding error\n§ Design error\n§ New Suggestion\n§ Documentation issue\n§ Hardware problem\n\n20\n4) Severity:This describes the impact of the bug.\nTypes of Severity:\n§Blocker:No further testing work can be done."}
{"id": "pdf::Ch6 Test Documentation::2244", "page_id": "pdf::Ch6 Test Documentation", "title": "Ch6 Test Documentation.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch6 Test Documentation.pdf", "section": "Ch6 Test Documentation.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/YFodwcsJoiOtrBknZjLcPvcinbe", "source_type": "pdf", "n_chars": 661, "text": "s describes the impact of the bug.\nTypes of Severity:\n§Blocker:No further testing work can be done.\n§Critical:Application crash, Loss of data.\n§Major:Major loss of function.\n§Minor:Minor loss of function.\n§Trivial:Some UI enhancements.\n§Enhancement:Request for a new feature or some enhancement in the existing one.\n5) Priority:When should a bug be fixed? Priority is generally set from P1 to P5. P1 as \n“fix the bug with the highest priority” and P5 as ” Fix when time permits”.\nImportant Features in Bug Report\n\n21\n6) Status:By default the bug status will be ‘New’. Later on, the bug goes through \nvarious stages like Fixed, Verified, Reopen, Won’t Fix, etc."}
{"id": "pdf::Ch6 Test Documentation::2245", "page_id": "pdf::Ch6 Test Documentation", "title": "Ch6 Test Documentation.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch6 Test Documentation.pdf", "section": "Ch6 Test Documentation.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/YFodwcsJoiOtrBknZjLcPvcinbe", "source_type": "pdf", "n_chars": 625, "text": "‘New’. Later on, the bug goes through \nvarious stages like Fixed, Verified, Reopen, Won’t Fix, etc.\n7) Assign To:If you know which developer is responsible for that particular module \nin which the bug occurred, then you can specify the email address of that developer. Else \nkeep it blank as this will assign the bug to the module owner, if not the Manager will \nassign the bug to the developer. \nImportant Features in Bug Report\n\n22\nImportant Features in Bug Report\n8) Platform/Environment\n§OS and browser configuration is necessary for a clear bug report. It is the best way to \ncommunicate how the bug can be reproduced."}
{"id": "pdf::Ch6 Test Documentation::2246", "page_id": "pdf::Ch6 Test Documentation", "title": "Ch6 Test Documentation.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch6 Test Documentation.pdf", "section": "Ch6 Test Documentation.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/YFodwcsJoiOtrBknZjLcPvcinbe", "source_type": "pdf", "n_chars": 660, "text": "necessary for a clear bug report. It is the best way to \ncommunicate how the bug can be reproduced.\n§Without the exact platform or environment, the application may behave differently and the \nbug at the tester’s end may not replicate on the developer’s end. \n9) Description\n§Bug description helps the developer to understand the bug. It describes the problem \nencountered. \n§It is a good practice to describe each problem separately instead of crumbling them \naltogether. Don’t use terms like “I think” or “I believe”.\n\n23\nImportant Features in Bug Report\nØSteps to Reproduce\nA good Bug report should clearly mention the steps to reproduce. These steps should"}
{"id": "pdf::Ch6 Test Documentation::2247", "page_id": "pdf::Ch6 Test Documentation", "title": "Ch6 Test Documentation.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch6 Test Documentation.pdf", "section": "Ch6 Test Documentation.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/YFodwcsJoiOtrBknZjLcPvcinbe", "source_type": "pdf", "n_chars": 671, "text": "s to Reproduce\nA good Bug report should clearly mention the steps to reproduce. These steps should \ninclude actions that may cause the bug. Don’t make generic statements. Be specific on \nthe steps to follow.\nA good example of a well-written procedure is given below Steps:\n§Select product Abc01.\n§Click on Add to cart.\n§Click Remove to remove the product from the cart.\n\n24\nØExpected and Actual Result\n§A Bug description is incomplete without the Expected and Actual results.\n§ It is necessary to outline what the outcome of the test is and what the user should \nexpect. \nØScreenshot\n§A picture is worth a thousand words. Take a Screenshot of the instance of failure with"}
{"id": "pdf::Ch6 Test Documentation::2248", "page_id": "pdf::Ch6 Test Documentation", "title": "Ch6 Test Documentation.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch6 Test Documentation.pdf", "section": "Ch6 Test Documentation.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/YFodwcsJoiOtrBknZjLcPvcinbe", "source_type": "pdf", "n_chars": 696, "text": "Screenshot\n§A picture is worth a thousand words. Take a Screenshot of the instance of failure with \nproper captioning to highlight the defect. \n§Highlight unexpected error messages with light red color. This draws attention to the \nrequired area.\nImportant Features in Bug Report\n\n25\nBug life cycle covers all possible status\n\n26\nWhat is a bug reporting system?\nØBug Reporting System\nØBug Tracking Software\nØIssue Tracking Software\nØIssue Management Software\nØDefect Tracking System\nA bug reporting system is an application “that keeps track of reported software bugs”.\nTherefore, a bug reporting software allows you to report, document, store, manage, assign, \nclose & archive the reports.\n\n\n27"}
{"id": "pdf::Ch6 Test Documentation::2249", "page_id": "pdf::Ch6 Test Documentation", "title": "Ch6 Test Documentation.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch6 Test Documentation.pdf", "section": "Ch6 Test Documentation.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/YFodwcsJoiOtrBknZjLcPvcinbe", "source_type": "pdf", "n_chars": 680, "text": "software allows you to report, document, store, manage, assign, \nclose & archive the reports.\n\n\n27\nBug reporting system\nSuch as: QC(Quality center)、禅道、Mantis、JIRA、TestLink、Bugzilla\n\n\n28\nBug reporting system\n\n\n29\nBug reporting system\n\n\n30\n4. Test Summary Report\nØTest Summary Report is an important deliverable which is prepared at the \nend of a Testing project, or rather after Testing is completed. \nØThe prime objective of this document is to explain various details and \nactivities about the Testing performed for the Project, to the respective \nstakeholders like Senior Management, Client, etc.\nØAfter performing exhaustive testing, publishing the test results, metrics, best"}
{"id": "pdf::Ch6 Test Documentation::2250", "page_id": "pdf::Ch6 Test Documentation", "title": "Ch6 Test Documentation.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch6 Test Documentation.pdf", "section": "Ch6 Test Documentation.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/YFodwcsJoiOtrBknZjLcPvcinbe", "source_type": "pdf", "n_chars": 607, "text": "ent, Client, etc.\nØAfter performing exhaustive testing, publishing the test results, metrics, best \npractices, lessons learned, conclusions on ‘Go Live’ etc. are extremely \nimportant to produce that as evidence for the Testing performed and the \nTesting conclusion.\n\n31\nWhat Test Summary Report Contains?\nØApplication Overview\n< Brief description of the application tested>\nØTypes of testing performed\n\nØTest Environment & Tools"}
{"id": "pdf::Ch6 Test Documentation::2251", "page_id": "pdf::Ch6 Test Documentation", "title": "Ch6 Test Documentation.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch6 Test Documentation.pdf", "section": "Ch6 Test Documentation.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/YFodwcsJoiOtrBknZjLcPvcinbe", "source_type": "pdf", "n_chars": 692, "text": "being tested properly through testing types agreed as per Test Strategy.>\nØTest Environment & Tools\n\n\n32\nWhat Test Summary Report Contains?\nØTesting Scope\n1.In Scope\n2.Out of Scope\n3.Items not tested\n•In-Scope:Functional Testing for the following modules are in Scope of Testing\n•Registration\n•Booking\n•Payment\n•Out of Scope:Performance Testing was not done for this application.\n•Items not tested:Verification of connectivity with the third party system ‘Central repository system’ \nwas not tested, as the connectivity could not be established due to some technical limitations."}
{"id": "pdf::Ch6 Test Documentation::2252", "page_id": "pdf::Ch6 Test Documentation", "title": "Ch6 Test Documentation.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch6 Test Documentation.pdf", "section": "Ch6 Test Documentation.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/YFodwcsJoiOtrBknZjLcPvcinbe", "source_type": "pdf", "n_chars": 671, "text": "’ \nwas not tested, as the connectivity could not be established due to some technical limitations. \n\n\n33\nWhat Test Summary Report Contains?\nØMetrics \n\n\n34\nWhat Test Summary Report Contains?\n\n\n35"}
{"id": "pdf::Ch6 Test Documentation::2253", "page_id": "pdf::Ch6 Test Documentation", "title": "Ch6 Test Documentation.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch6 Test Documentation.pdf", "section": "Ch6 Test Documentation.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/YFodwcsJoiOtrBknZjLcPvcinbe", "source_type": "pdf", "n_chars": 299, "text": "aphs can be attached for better visual representation>\n\n\n34\nWhat Test Summary Report Contains?\n\n\n35\nTesting management tools禅道（www.zentao.net ）\n \n\n\n36\nTesting management tools禅道（www.zentao.net ）\n \n\n\n37\nTesting management toolsTAPD（www.tapd.cn ）\n \n\n\n39\nTesting management toolsTest Link（testlink.org）"}
{"id": "pdf::Ch7 UnitTesting::2254", "page_id": "pdf::Ch7 UnitTesting", "title": "Ch7 UnitTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch7 UnitTesting.pdf", "section": "Ch7 UnitTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/AfK1wcMh5i61GXkOvfkc5dbNnjb", "source_type": "pdf", "n_chars": 671, "text": "Unit Testing\nYanxia Liu cslyx@scut.edu.cn\nSpring, 2025\n1\n\nContents\nØ Whatdo we test?\nØ Unit Testing\nØTest-Driven Development (TDD)\nØAutomated Unit Testing\n2\n\n3\n1. What do we test? - – the Focus of Concern\n\n\n4\nWhat do we test? - – the Focus of Concern\n\n6\nWhat do we test? - – the Focus of Concern\n\n7\nWhat do we test? - – the Focus of Concern\n\n8\nWhat do we test? - – the Focus of Concern\n\n9\n2.Unit Testing\nØ Unit tests are mainly whitebox tests written by developers, and designed \nto verify small units of program functionality.\n• Key Metaphor: I.C. Testing\n Integrated Circuits are tested individually for functionality before the whole circuit is \ntested.\n• Definitions"}
{"id": "pdf::Ch7 UnitTesting::2255", "page_id": "pdf::Ch7 UnitTesting", "title": "Ch7 UnitTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch7 UnitTesting.pdf", "section": "Ch7 UnitTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/AfK1wcMh5i61GXkOvfkc5dbNnjb", "source_type": "pdf", "n_chars": 676, "text": "rcuits are tested individually for functionality before the whole circuit is \ntested.\n• Definitions\nWhitebox – Unit tests are written with full knowledge of implementation details.\nDevelopers – Unit tests are written by you, the developer, concurrently with \nimplementation.\nSmall Units – Unit tests should isolate one piece of software at a time.\n• Individual methods and classes\nVerify – Make sure you built ‘the software right.’ Testing against the contract.\n• Contrast this with validation\n\n10\nTask of Unit Testing\nØ All independently path tests in the unit\nØCalculation errors, incorrect comparisons, inappropriate control flows\nØ Local data structure testing in the unit"}
{"id": "pdf::Ch7 UnitTesting::2256", "page_id": "pdf::Ch7 UnitTesting", "title": "Ch7 UnitTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch7 UnitTesting.pdf", "section": "Ch7 UnitTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/AfK1wcMh5i61GXkOvfkc5dbNnjb", "source_type": "pdf", "n_chars": 665, "text": "rors, incorrect comparisons, inappropriate control flows\nØ Local data structure testing in the unit\nØVariable initialization, datatypes, buffer overflow, memory address exception\nØ Unit interface test \nØmethod parameters, I/O access , file or network etc.\nØ Unit boundary value test\nØ Every error handling path test in the unit\nØ Memory analysis\nØMemory allocation , memory leak\n…….. \n\n11\nRole of Unit Testing\nØHelps localize errors\n§ Failure indicates problem in the unit under test\nØFind errors early\n§ Unit tests are written during development, usually by developer\n§ More expensive to fix defects found later by another team\nØAvoid unnecessary functionality"}
{"id": "pdf::Ch7 UnitTesting::2257", "page_id": "pdf::Ch7 UnitTesting", "title": "Ch7 UnitTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch7 UnitTesting.pdf", "section": "Ch7 UnitTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/AfK1wcMh5i61GXkOvfkc5dbNnjb", "source_type": "pdf", "n_chars": 635, "text": "loper\n§ More expensive to fix defects found later by another team\nØAvoid unnecessary functionality\n§Write test first, only write enough code to get it working\nØImprove code quality \n§Helps developer deliver working code\n§Assure minimum quality of units before integration into system\n\n12\nUnit Test\n\n\n13\nUnit Test and Scaffolding\n\n\n14\nUnit Test\n\n\n15\nTechniques for Unit Testing : Scaffolding\n\n16\nTechniques for Unit Testing : Scaffolding\n\n17\n3.Test-Driven Development\nØWrite the tests before the code\n§Helps you think about corner cases when writing\n§Helps you think about interface design\nØWrite code only when an automated test fails"}
{"id": "pdf::Ch7 UnitTesting::2258", "page_id": "pdf::Ch7 UnitTesting", "title": "Ch7 UnitTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch7 UnitTesting.pdf", "section": "Ch7 UnitTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/AfK1wcMh5i61GXkOvfkc5dbNnjb", "source_type": "pdf", "n_chars": 651, "text": "when writing\n§Helps you think about interface design\nØWrite code only when an automated test fails\nØIf you find a bug through other means, first write a test thatfails, then fix \nthe bug\n§Bug won’t resurface later\nØRun tests as often as possible, ideally every time the code ischanged\n§Having comprehensive unit tests allows you to refactor codewith \nconfidence\n§Without unit tests, code is fragile – changes might break clients!\n\n18\nTDD - Test-Driven Development\nWrite a test for \nnew capability\nStart\nCompile\nFix compile \nerrors\nRun the test\nAnd see it fail\nWrite the code\nRun the test\nAnd see it pass\nRefactor as needed\n\n\n19\nTest-Driven Development"}
{"id": "pdf::Ch7 UnitTesting::2259", "page_id": "pdf::Ch7 UnitTesting", "title": "Ch7 UnitTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch7 UnitTesting.pdf", "section": "Ch7 UnitTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/AfK1wcMh5i61GXkOvfkc5dbNnjb", "source_type": "pdf", "n_chars": 664, "text": "it fail\nWrite the code\nRun the test\nAnd see it pass\nRefactor as needed\n\n\n19\nTest-Driven Development\nØAn excellent practice promoted by the iterative and agile XP method , also \nknown as test-first development\nØAdvantages\n§The unit tests actually get written\n§Programmer satisfaction leading to more consistent test writing\n§Clarification of detailed interface and behavior\n§Provable, repeatable, automated verification\n§The confidence to change things\n\n20\n4.Automated Unit Test\nØTesting Framework are tools that help manage and run yourunit tests.\nØxUnitFramework：JUnit(java),CppUnit(c++),NUnit(.Net)\nØHelp achieve three properties of good unit tests:\n • Automatic"}
{"id": "pdf::Ch7 UnitTesting::2260", "page_id": "pdf::Ch7 UnitTesting", "title": "Ch7 UnitTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch7 UnitTesting.pdf", "section": "Ch7 UnitTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/AfK1wcMh5i61GXkOvfkc5dbNnjb", "source_type": "pdf", "n_chars": 690, "text": "Unit(java),CppUnit(c++),NUnit(.Net)\nØHelp achieve three properties of good unit tests:\n • Automatic\nTests should be easy to run and check for correct completion.\nØThis allows developers to quickly confirm their code is workingafter a \nchange.\n • Repeatable\n Any developer can run the tests and they will work right away.\n • Independent\nTests can be run in any order and they will still work.\n\n21\n\n22\n\n23\n\n24\n\n25\nJUnit: A Java Unit Testing Framework\nhttp://www.junit.org/\n\n26\nA JUnit Test Case\n\n27\nHelpful JUnit Assert Statements\n\n\n〉\n28\n\n29\nOther Helpful JUnit Features\n@BeforeClass –> \n @Before –> @Test –> @After \n–> @AfterClass\n\n30\n\n31\n\nJunit Suite Testing\n32\n\n33\nJunit Suite Testing"}
{"id": "pdf::Ch7 UnitTesting::2261", "page_id": "pdf::Ch7 UnitTesting", "title": "Ch7 UnitTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch7 UnitTesting.pdf", "section": "Ch7 UnitTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/AfK1wcMh5i61GXkOvfkc5dbNnjb", "source_type": "pdf", "n_chars": 200, "text": "@Before –> @Test –> @After \n–> @AfterClass\n\n30\n\n31\n\nJunit Suite Testing\n32\n\n33\nJunit Suite Testing\n\nØ@ Suite.SuiteClasses\nØRun As -> JUnit Test\n34\nJunit Suite Testing\n\n35\nJunit \nParameterized \nTesting"}
{"id": "pdf::Ch8 IntegrationTesting::2262", "page_id": "pdf::Ch8 IntegrationTesting", "title": "Ch8 IntegrationTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch8 IntegrationTesting.pdf", "section": "Ch8 IntegrationTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FjhowzZixiJLOakNqjjcOGZFnRj", "source_type": "pdf", "n_chars": 693, "text": "Integration Testing\nYanxia Liu cslyx@scut.edu.cn\nSpring, 2025\n1\n\nContents\nØWhat is Integration Testing\nØ Approaches to Integration Testing\nØDecomposition-based Integration\nØCall-Graph based Integration\nØMM Path based Integration\n2\n\n3\n1. Lifecycle Testing Relationships\n\n\n4\nTesting Level Assumptions and Objectives\n\n\n5\nDefinitions – Integration Tests\nØIntegration test data is selected to ensure that the components or \nsub-systems of a system are working correctly together.\nØTest cases will explore different interactions between the \ncomponents, and make sure the correct results are produced.\n\n8\nIntegration Testing – Drivers and Stubs\nØDrivers and Stubs are temporary \nsoftware components"}
{"id": "pdf::Ch8 IntegrationTesting::2263", "page_id": "pdf::Ch8 IntegrationTesting", "title": "Ch8 IntegrationTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch8 IntegrationTesting.pdf", "section": "Ch8 IntegrationTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FjhowzZixiJLOakNqjjcOGZFnRj", "source_type": "pdf", "n_chars": 631, "text": "d.\n\n8\nIntegration Testing – Drivers and Stubs\nØDrivers and Stubs are temporary \nsoftware components\n§A test driver calls the software under test, \npassing the test data as inputs.\n§In manual testing, where the system \ninterface has not been completed, a test \ndriver is used in its place to provide the \ninterface between the test user and the \nsoftware under test.\n\n\n9\nØDrivers\n§Drivers can have varying levels of sophistication.\n§It could be hard-coded to run through a fixed series of input values, read \ndata from a prepared file, contain a suitable random number generator \netc..\nIntegration Testing – Drivers and Stubs\nØStubs"}
{"id": "pdf::Ch8 IntegrationTesting::2264", "page_id": "pdf::Ch8 IntegrationTesting", "title": "Ch8 IntegrationTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch8 IntegrationTesting.pdf", "section": "Ch8 IntegrationTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FjhowzZixiJLOakNqjjcOGZFnRj", "source_type": "pdf", "n_chars": 676, "text": "e, contain a suitable random number generator \netc..\nIntegration Testing – Drivers and Stubs\nØStubs\n§A stub is a temporary or dummy software that is required by the software \nunder test to operate properly. \n§This is a throw-away version to allow testing to take place.\n§It will provide a fixed or limited set of values to be passed to the software \nunder test.\n\n10\n2. Approaches to Integration Testing ( “source” of test cases)\nØDecomposition-basedIntegration\n§“Big bang”integration\n§Top-downintegration\n§Bottom-upintegration\n§Sandwichintegration\nØCall graph-basedIntegration\n§Pairwise integration\n§Neighborhood integration\nØPath-basedIntegration\n§MM-PathbasedIntegration\n\n11"}
{"id": "pdf::Ch8 IntegrationTesting::2265", "page_id": "pdf::Ch8 IntegrationTesting", "title": "Ch8 IntegrationTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch8 IntegrationTesting.pdf", "section": "Ch8 IntegrationTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FjhowzZixiJLOakNqjjcOGZFnRj", "source_type": "pdf", "n_chars": 681, "text": "§Pairwise integration\n§Neighborhood integration\nØPath-basedIntegration\n§MM-PathbasedIntegration\n\n11\n2.1 Decomposition-based Integration\nØInthisstrategy, do the decomposition based on the functional characteristics of the system.\n§A functional characteristic is defined by what the module does, that is, actions or \nactivities performed by the module.\nBig bang integration\n§big-bang groups the whole system and test it in a single test phase.\nTop-down integration\n§Top-down starts at the root of the tree and slowly work to lower level of the tree\nBottom-up integration\n§Bottom-up mirrors top-down, it starts at the lower level implementation of\nthe system and work towards the main"}
{"id": "pdf::Ch8 IntegrationTesting::2266", "page_id": "pdf::Ch8 IntegrationTesting", "title": "Ch8 IntegrationTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch8 IntegrationTesting.pdf", "section": "Ch8 IntegrationTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FjhowzZixiJLOakNqjjcOGZFnRj", "source_type": "pdf", "n_chars": 662, "text": "rrors top-down, it starts at the lower level implementation of\nthe system and work towards the main\nSandwich integration\n§ Sandwich is an approach that combines both top-down and bottom-up.\n\n12\nBig bang Integration\nØConsiders the whole system as a subsystem\nØTests all the modules in a single test session\nØOnly one integration testing session\nNo...\n– stubs\n– drivers\n– strategy\nØVery difficult fault isolation\n\n\n13\nØBreadth-first traversal of the functional decomposition tree.\n• First step: Check main program logic, with all called units replaced by stubs that always return correct values.\n• Move down one level\n– replace one stub at a time with actual code."}
{"id": "pdf::Ch8 IntegrationTesting::2267", "page_id": "pdf::Ch8 IntegrationTesting", "title": "Ch8 IntegrationTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch8 IntegrationTesting.pdf", "section": "Ch8 IntegrationTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FjhowzZixiJLOakNqjjcOGZFnRj", "source_type": "pdf", "n_chars": 673, "text": "always return correct values.\n• Move down one level\n– replace one stub at a time with actual code.\n– any fault must be in the newly integrated unit\nØDepth-firsttraversal\nTop-Down Integration\nØEarly SUT prototype\nØThrow-away code programming\n\n14\nBottom-Up Integration\nØReverse of top-down integration\n§Start at leaves of the functional decomposition tree.\n§Driver units...\n– call next level unit\n– “drive” the unit with inputs\nØAs with top-down integration, one driver unit at a time is replaced with actual code.\nØAny fault is (most likely) in the newly integrated code.\nØLess throw-away code programming\nØNo prototype and Main program tested last\n\n\n15\nSandwich integration"}
{"id": "pdf::Ch8 IntegrationTesting::2268", "page_id": "pdf::Ch8 IntegrationTesting", "title": "Ch8 IntegrationTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch8 IntegrationTesting.pdf", "section": "Ch8 IntegrationTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FjhowzZixiJLOakNqjjcOGZFnRj", "source_type": "pdf", "n_chars": 659, "text": "ss throw-away code programming\nØNo prototype and Main program tested last\n\n\n15\nSandwich integration\nØCombines top-down approach and bottom-up approach\n§Generally, higher level modules use a top-down approach (stub)\n§Normally, lower-level modules use a bottom-up approach (driver)\nØTesting converges to the middle\nØNumber of integration sessions can vary\nØTop and bottom layers can be done in parallel\nØLess stubs and drivers needed\nØHard to isolate problems\n\n\n16\nCaseStudy---The NextDate Program\nØThis program uses three variables: month, date and year.\nØWith the input, it returns the next date of the inputted date.\nIt has the following characteristics:\n\n17"}
{"id": "pdf::Ch8 IntegrationTesting::2269", "page_id": "pdf::Ch8 IntegrationTesting", "title": "Ch8 IntegrationTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch8 IntegrationTesting.pdf", "section": "Ch8 IntegrationTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FjhowzZixiJLOakNqjjcOGZFnRj", "source_type": "pdf", "n_chars": 652, "text": "the input, it returns the next date of the inputted date.\nIt has the following characteristics:\n\n17\nPseudo-code of the NextDate program implementation-Main()\n\n\n18\nPseudo-code of the NextDate program implementation – isLeap()\n\n19\nPseudo-code of the NextDate program implementation – lastDayOfMonth()\n\n\n20\nPseudo-code of the NextDate program implementation – validDate()\n\n\n21\nPseudo-code of the NextDate program implementation –getDate()\n\n22\nPseudo-code of the NextDate program implementation – incrementDate()\n\n\n23\nPseudo-code of the NextDate program implementation – printDate()\n\n\n24\nDecomposition-based Integration --- the NextDate program ( Big Bang)"}
{"id": "pdf::Ch8 IntegrationTesting::2270", "page_id": "pdf::Ch8 IntegrationTesting", "title": "Ch8 IntegrationTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch8 IntegrationTesting.pdf", "section": "Ch8 IntegrationTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FjhowzZixiJLOakNqjjcOGZFnRj", "source_type": "pdf", "n_chars": 684, "text": "lementation – printDate()\n\n\n24\nDecomposition-based Integration --- the NextDate program ( Big Bang)\nCompile all the modules in the functional decomposition tree and test the whole system in a single session\n\n25\nDecomposition-based Integration --- the NextDate program ( Top-down)\nØStart with Main as a target node and replace the children nodes one by one with stubs (only one stub in each test session).\nØWe must build the stub such that it returns correct values to the real module and compatible to the test cases.\nA possible stub \nfor incrementDate:\nThe test cases will be limited by how \nand what we code in the stub\nNot be able to isolate them withstubs with a top-down approach"}
{"id": "pdf::Ch8 IntegrationTesting::2271", "page_id": "pdf::Ch8 IntegrationTesting", "title": "Ch8 IntegrationTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch8 IntegrationTesting.pdf", "section": "Ch8 IntegrationTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FjhowzZixiJLOakNqjjcOGZFnRj", "source_type": "pdf", "n_chars": 639, "text": "by how \nand what we code in the stub\nNot be able to isolate them withstubs with a top-down approach\nNever called by Main directly\n\n26\nDecomposition-based Integration --- the NextDate program ( Bottom-up)\nBegins with the leaves of the decomposition tree, and use a driver version \nof the unit that would normally call it to provide it with test cases.\nØNo need to substitute as many modules with temporary throw-away modules\nA possible driver\n for isLeap: \nisLeap_driver()\nisLeap_driver)\n\n27\nDecomposition-based Integration --- the NextDate program ( Sandwich)\nSandwich integration combines top-down integration and bottom-up integration."}
{"id": "pdf::Ch8 IntegrationTesting::2272", "page_id": "pdf::Ch8 IntegrationTesting", "title": "Ch8 IntegrationTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch8 IntegrationTesting.pdf", "section": "Ch8 IntegrationTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FjhowzZixiJLOakNqjjcOGZFnRj", "source_type": "pdf", "n_chars": 676, "text": "e program ( Sandwich)\nSandwich integration combines top-down integration and bottom-up integration.\n§ In top-down by starting at the root of the functional decomposition tree, which \ncan test the main program at early stage. \n§In bottom-up, we will have coverage that is easy to create test cases.\nThere are no strict guidelines in modules grouping\n\n\n28\nPros and Cons of Decomposition-Based Integration\nØPros\n– intuitively clear\n– “build” with proven components\n– fault isolation varies with the number of units being Integrated\nØCons\n– some branches in a functional decomposition may not correspond \nwith actual interfaces.\n– stub and driver development can be extensive\n\n29"}
{"id": "pdf::Ch8 IntegrationTesting::2273", "page_id": "pdf::Ch8 IntegrationTesting", "title": "Ch8 IntegrationTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch8 IntegrationTesting.pdf", "section": "Ch8 IntegrationTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FjhowzZixiJLOakNqjjcOGZFnRj", "source_type": "pdf", "n_chars": 679, "text": "tion may not correspond \nwith actual interfaces.\n– stub and driver development can be extensive\n\n29\n2.2 Call Graph-based Integration\nØDefinition: The Call Graph of a program is a directed graph in which\n– nodes are unit\n– edges correspond to actual program calls (or messages)\nØCall Graph Integration avoids the possibility of impossible edges in decomposition-based \nintegration.\nØCan still use the notions of stubs and drivers.\nØCan still traverse the Call Graph in a top-down or bottom-up strategy.\nTwo strategies\n– Pair-wise integration\n– Neighborhood integration\nDegrees of nodes in the Call Graph indicate integration sessions\n– test high indegree nodes first, or at least,"}
{"id": "pdf::Ch8 IntegrationTesting::2274", "page_id": "pdf::Ch8 IntegrationTesting", "title": "Ch8 IntegrationTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch8 IntegrationTesting.pdf", "section": "Ch8 IntegrationTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FjhowzZixiJLOakNqjjcOGZFnRj", "source_type": "pdf", "n_chars": 690, "text": "odes in the Call Graph indicate integration sessions\n– test high indegree nodes first, or at least,\n– pay special attention to “popular” nodes\n\n30\nPair-Wise Integration\nØBy definition, and edge in the Call Graph refers to an interface between the \nunits that are the endpoints of the edge.\nØEvery edge represents a pair of units to test.\nØFault isolation is localized to the pair being Integrated\nØThe number of integration testing sessions is the number of edges\n\n\n31\nNeighborhood Integration\nØThe neighborhood (or radius 1) of a node in a graph is the set of nodes that are one \nedge away from the given node.\nØThis can be extended to larger sets by choosing larger values for the radius."}
{"id": "pdf::Ch8 IntegrationTesting::2275", "page_id": "pdf::Ch8 IntegrationTesting", "title": "Ch8 IntegrationTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch8 IntegrationTesting.pdf", "section": "Ch8 IntegrationTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FjhowzZixiJLOakNqjjcOGZFnRj", "source_type": "pdf", "n_chars": 691, "text": "from the given node.\nØThis can be extended to larger sets by choosing larger values for the radius.\nØStub and driver effort is reduced.\n\n\n32\n2.3 Path-Based Integration\nØMotivation : an integration testing level construct similar to Paths Coverage for unit \ntesting\n– extend the symbiosis of spec-based and code-based testing to the integration level\n– greater emphasis on behavioral threads\n– shift emphasis from interface testing to interactions (cofunctions) among units\nØNeed some new definitions\n– source and sink nodes in a program graph\n– module (unit ) execution path\n– generalized message\n– MM-Path\n\n33\nNew and Extended Definitions\nØA source node in a program is a statement fragment"}
{"id": "pdf::Ch8 IntegrationTesting::2276", "page_id": "pdf::Ch8 IntegrationTesting", "title": "Ch8 IntegrationTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch8 IntegrationTesting.pdf", "section": "Ch8 IntegrationTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FjhowzZixiJLOakNqjjcOGZFnRj", "source_type": "pdf", "n_chars": 648, "text": "age\n– MM-Path\n\n33\nNew and Extended Definitions\nØA source node in a program is a statement fragment \nat which program execution begins or resumes.\nØA sink node in a unit is a statement fragment at \nwhich program execution terminates.\nØA module execution path is a sequence of \nstatements that begins with a source node and ends \nwith a sink node, with no intervening sink nodes.\nØA message is a programming language mechanism \nby which one unit transfers control to another unit, \nand acquires a response from the other unit.\nØModule/Message-Path – an interleaved sequence of \nmodule execution paths and messages.\n\n\n34\nMM-Path Definition and Example"}
{"id": "pdf::Ch8 IntegrationTesting::2277", "page_id": "pdf::Ch8 IntegrationTesting", "title": "Ch8 IntegrationTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch8 IntegrationTesting.pdf", "section": "Ch8 IntegrationTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FjhowzZixiJLOakNqjjcOGZFnRj", "source_type": "pdf", "n_chars": 695, "text": "n interleaved sequence of \nmodule execution paths and messages.\n\n\n34\nMM-Path Definition and Example\nAn MM-Path is an interleaved sequence of module execution paths and messages.\nAn MM-Path \nacross three units\nThe node sequence \n\n35\nMM-Path based Integration --- the NextDate program\nThe MM-Paths begin in and return to the main program.\nThe following fragment represent the first MM-Path for “5/27/2002”\nMain problem is knowing how many MM-Paths are required to complete the integration\ntest. The set of MM-Paths should traverse all source-to-sink paths.\n\n36\nPros and Cons of Path-Based Integration\nØPros\n§Hybrid of functional and structural testing\n§Closely coupled with actual system behaviour"}
{"id": "pdf::Ch8 IntegrationTesting::2278", "page_id": "pdf::Ch8 IntegrationTesting", "title": "Ch8 IntegrationTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch8 IntegrationTesting.pdf", "section": "Ch8 IntegrationTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FjhowzZixiJLOakNqjjcOGZFnRj", "source_type": "pdf", "n_chars": 235, "text": "on\nØPros\n§Hybrid of functional and structural testing\n§Closely coupled with actual system behaviour\n§Does not require stub or driver\nØCons\n§Extra effort required to identify the MM-Paths\n\n37\nComparison of Integration Testing Strategies"}
{"id": "pdf::Ch9 SystemTesting::2279", "page_id": "pdf::Ch9 SystemTesting", "title": "Ch9 SystemTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch9 SystemTesting.pdf", "section": "Ch9 SystemTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/WmjXwHonTiWeR2kqIPAcn0ymnIr", "source_type": "pdf", "n_chars": 630, "text": "System Testing\nYanxia Liu cslyx@scut.edu.cn\nSpring, 2025\n1\n\nContents\nØ What is System Testing\nØ System Test Types\n§Functional Testing\n§Non-Functional Testing\n§Regression Testing\n2\n\n3\n1. What is System Testing\nØTests the behavior of a system as a whole, with respect to scenarios and \nrequirements.\n§ Assumes all components already work well\n§ Integration testing finish( checking software quality by testing two or more dependent software \nmodules as a group or a (sub)system.)\n \nØBlack-box testing techniques are used.\n§ Reconciles software against top-level requirements\n§ Tests stem from concrete use cases in the requirements"}
{"id": "pdf::Ch9 SystemTesting::2280", "page_id": "pdf::Ch9 SystemTesting", "title": "Ch9 SystemTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch9 SystemTesting.pdf", "section": "Ch9 SystemTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/WmjXwHonTiWeR2kqIPAcn0ymnIr", "source_type": "pdf", "n_chars": 661, "text": "es software against top-level requirements\n§ Tests stem from concrete use cases in the requirements\nØVerifies that the new SW system integrates with the existing environment. \nThis may include other systems, hardware, people and databases.\n\n4\n2. System Testing Types\nØTest “types” classify the purpose of the test, rather than its scope or \nmechanism.\n§Functional testing\n§Ensure compliance with functional requirements\n§Non-functional testing\n§Ensure compliance with non-functional requirements\n§Regression testing\n\n5\n2.1 System Testing ( Functional)\nThe default assumption in testing\nØFunctional testing verifies the software’s behavior matches expectations."}
{"id": "pdf::Ch9 SystemTesting::2281", "page_id": "pdf::Ch9 SystemTesting", "title": "Ch9 SystemTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch9 SystemTesting.pdf", "section": "Ch9 SystemTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/WmjXwHonTiWeR2kqIPAcn0ymnIr", "source_type": "pdf", "n_chars": 676, "text": "lt assumption in testing\nØFunctional testing verifies the software’s behavior matches expectations.\nØAlso includes testing bad inputs, to check implicit assumptions\n§i.e., given nonsense input, the program should do “something reasonable”\nØCuts across all levels of testing, but heavy on unit testing\n§Theinterface used for testing is the System Interface : the user interface, thenetwork \ninterface, dedicated hardware interfaces, etc.\n\n8\nØThe selection of Test Cases is based on Black-Box Testing.\nØApplication of Scenario Testing, Equivalence Partitions, Boundary Value \nAnalysis, Error Guessing, Decision-Table Testing, Random Testing etc. is \nrelatively straightforward."}
{"id": "pdf::Ch9 SystemTesting::2282", "page_id": "pdf::Ch9 SystemTesting", "title": "Ch9 SystemTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch9 SystemTesting.pdf", "section": "Ch9 SystemTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/WmjXwHonTiWeR2kqIPAcn0ymnIr", "source_type": "pdf", "n_chars": 650, "text": "ysis, Error Guessing, Decision-Table Testing, Random Testing etc. is \nrelatively straightforward. \n§Like Unit Testing, test casesand test data are selected using the technique being used.\n§The only difference is that instead of calling a method with the specifiedparameters, the \ndata must be entered into the interface as appropriate, and then the results collected from \ntheinterface.\nFunctional Testing Strategy\n\n9\n2.2 System Testing ( Non - Functional)\nØRoughly, testing things that are not “functionality”\nØGenerally, tests quality of the software, also called the “-ilities”\n§Usability\n§Reliability\n§Maintainability\n§Security\n§Performance\n§……"}
{"id": "pdf::Ch9 SystemTesting::2283", "page_id": "pdf::Ch9 SystemTesting", "title": "Ch9 SystemTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch9 SystemTesting.pdf", "section": "Ch9 SystemTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/WmjXwHonTiWeR2kqIPAcn0ymnIr", "source_type": "pdf", "n_chars": 692, "text": "are, also called the “-ilities”\n§Usability\n§Reliability\n§Maintainability\n§Security\n§Performance\n§……\nØNonfunctional testing is an umbrella term for many test types.\n§Note these aren’t all mutually exclusive!\n§Not all of these may be carried out on the product or be applicable to it.\n\n\n10\nSystem Testing ( Non - Functional)\nConformance Testing \n§Used to verify that the system conforms to a set of published standards. Many \nstandards will have a published suite of conformance tests or have a selected authority \nto run these tests. \n§This is particularly important for communications software, as software system must \ncorrectly interoperate with other implementations.\nDocumentation Testing"}
{"id": "pdf::Ch9 SystemTesting::2284", "page_id": "pdf::Ch9 SystemTesting", "title": "Ch9 SystemTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch9 SystemTesting.pdf", "section": "Ch9 SystemTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/WmjXwHonTiWeR2kqIPAcn0ymnIr", "source_type": "pdf", "n_chars": 626, "text": ", as software system must \ncorrectly interoperate with other implementations.\nDocumentation Testing\n§Used to verify that the documentation (in printed form, online, help, or prompts) is \nsufficient for the software to be installed and operated efficiently. \n§Typically, a full installation is performed, and then the different system functions are \nexecuted, exactly as documented. Responses are checked against the documented \nresponses.\n\n11\nSystem Testing ( Non - Functional)\nUsability Testing\n§ Used to verify the ease-of-use of the system. \n§This can be either automated (verifying font sizes, information placement on the"}
{"id": "pdf::Ch9 SystemTesting::2285", "page_id": "pdf::Ch9 SystemTesting", "title": "Ch9 SystemTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch9 SystemTesting.pdf", "section": "Ch9 SystemTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/WmjXwHonTiWeR2kqIPAcn0ymnIr", "source_type": "pdf", "n_chars": 636, "text": "of the system. \n§This can be either automated (verifying font sizes, information placement on the \nscreen, use of colors, or the speed of progress by users of different experience \nlevels), or manual (based on feedback forms completed by users).\nInteroperability Testing \n§ Used to verify that the software can exchange and share information with other \nrequired software products. \n§Typically, tests are run on all pairs of products to see that all the information that \nneeds to be shared is transferred correctly. This is particularly important for \ncommunications software.\n\n12\nSystem Testing ( Non - Functional)\nPerformance Testing"}
{"id": "pdf::Ch9 SystemTesting::2286", "page_id": "pdf::Ch9 SystemTesting", "title": "Ch9 SystemTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch9 SystemTesting.pdf", "section": "Ch9 SystemTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/WmjXwHonTiWeR2kqIPAcn0ymnIr", "source_type": "pdf", "n_chars": 649, "text": "important for \ncommunications software.\n\n12\nSystem Testing ( Non - Functional)\nPerformance Testing \n§Used to verify that the performance targets for the software have been met. \n§These tests verify that metrics such as the configuration limits (static), response latency \nor maximum number of simultaneous users (dynamic) are measured and compared to \nthe specified requirements. \nPortability Testing \n§Used to verify that the software is portable to another operating environment. \n§A selection of tests from the original platform are run in each new environment. \n§The new platforms may be software platforms (such as 32-bit and 64-bit versions of"}
{"id": "pdf::Ch9 SystemTesting::2287", "page_id": "pdf::Ch9 SystemTesting", "title": "Ch9 SystemTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch9 SystemTesting.pdf", "section": "Ch9 SystemTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/WmjXwHonTiWeR2kqIPAcn0ymnIr", "source_type": "pdf", "n_chars": 684, "text": "environment. \n§The new platforms may be software platforms (such as 32-bit and 64-bit versions of \nthe same operating system, or implementations by different vendors), or hardware \nplatforms (such as mobile phones, tablets, laptops, workstations, and servers), or \ndifferent environments (databases, networks, etc.).\n\n13\nSystem Testing ( Non - Functional)\nSecurity Testing \n§Used to verify that the system security features are not vulnerable to attack.\n§ The tests will deliberately attempt to break security measures. \n§Examples would include impersonating another user, accessing protected files, \naccessing network ports, breaking encrypted storage or communications, or inserting"}
{"id": "pdf::Ch9 SystemTesting::2288", "page_id": "pdf::Ch9 SystemTesting", "title": "Ch9 SystemTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch9 SystemTesting.pdf", "section": "Ch9 SystemTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/WmjXwHonTiWeR2kqIPAcn0ymnIr", "source_type": "pdf", "n_chars": 664, "text": "tected files, \naccessing network ports, breaking encrypted storage or communications, or inserting \nunauthorized software.\nSoftware reliability \n§Used to verify the probability of failure-free operation of an application in a specified \noperating environment and time period. \n§Failure Intensity: The number of failures occurring in a given time period.\n§MTBF: The average value of the next failure interval\n\n14\n2.3Regression Testing\nØMaking sure that code changes haven’t broken existingfunctionality, \nperformance, security, etc.\nØIn practice, this means re-running tests after a code change\nØWith good test automation and goodunit/integration/system/etc. tests,"}
{"id": "pdf::Ch9 SystemTesting::2289", "page_id": "pdf::Ch9 SystemTesting", "title": "Ch9 SystemTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch9 SystemTesting.pdf", "section": "Ch9 SystemTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/WmjXwHonTiWeR2kqIPAcn0ymnIr", "source_type": "pdf", "n_chars": 684, "text": "g tests after a code change\nØWith good test automation and goodunit/integration/system/etc. tests, \nthis is literally runningtests again after a change.\n\n\n15\n1)Manual software testing is slow, error-prone, and hard to repeat \naccurately:\n§Testing All workflows/all fields/all negative scenarios is time consuming\n§Become boring and hence error prone as human testers lose concentration.\n§The testing finishes for the day when the testers go home\n2) Yet software testing needs to be fast, accurate, and repeatable:\n§Performed frequently without a time penalty.\n§Test results can be relied on as a quality indicator.\n§Be repeatable to allow for regression testing.\n2.4TestAutomation\n\n16"}
{"id": "pdf::Ch9 SystemTesting::2290", "page_id": "pdf::Ch9 SystemTesting", "title": "Ch9 SystemTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch9 SystemTesting.pdf", "section": "Ch9 SystemTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/WmjXwHonTiWeR2kqIPAcn0ymnIr", "source_type": "pdf", "n_chars": 694, "text": "ed on as a quality indicator.\n§Be repeatable to allow for regression testing.\n2.4TestAutomation\n\n16\nWhat is Automated Testing?\nIt’s a software testing method that compares expected and actual \nresults of test cases with the help of special automation testing tools\n§Automated execution of tests, or collections of tests\n§Automated collection of results\n§Automated evaluation of results\n§Automated reports\n§Automated measurement of test coverage\n\n17\nThe Key Differences Between Manual and Automated Testing\nBenefits and drawbacks automated testing has：\nPros:（High ROI&Faster GoTo market）\n§Supports execution of repeated Test Cases\n§Aids in testing a large Test Matrix\n§Enables parallel execution"}
{"id": "pdf::Ch9 SystemTesting::2291", "page_id": "pdf::Ch9 SystemTesting", "title": "Ch9 SystemTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch9 SystemTesting.pdf", "section": "Ch9 SystemTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/WmjXwHonTiWeR2kqIPAcn0ymnIr", "source_type": "pdf", "n_chars": 681, "text": "s execution of repeated Test Cases\n§Aids in testing a large Test Matrix\n§Enables parallel execution\n§Encourages unattended execution\n§Improves accuracy thereby reducing human-generated errors\n§Saves time and money\nCons:\n§Automation instruments are usually expensive;\n§It is ineffective in testing user experience in applications;\n§Coding knowledge and experience are a must.\n\n18\nSelenium\nØSelenium is one of the most popular Automated Testing suites. \nØSelenium is designed to support and encourage Automation Testing of functional \naspects of web-based applications and a wide range of browsers and platforms.\n§It’s an open-source\n§It has a large user base and helping communities"}
{"id": "pdf::Ch9 SystemTesting::2292", "page_id": "pdf::Ch9 SystemTesting", "title": "Ch9 SystemTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch9 SystemTesting.pdf", "section": "Ch9 SystemTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/WmjXwHonTiWeR2kqIPAcn0ymnIr", "source_type": "pdf", "n_chars": 681, "text": "e of browsers and platforms.\n§It’s an open-source\n§It has a large user base and helping communities\n§It has multi-browser and platform compatibility\n§It has active repository developments\n§It supports multiple language implementations\n\n19\nSelenium\nSelenium automates browsers.\nPrimarily it is for automating web applications for testing \npurposes, but is certainly not limited to just that.\nhttps://www.selenium.dev\n\n20\n3. PerformanceTesting\nØknows as ‘Perf Testing’, is a type of testing performed to check how \napplication or software performs under workload in terms of responsiveness \nand stability. \nØThe Performance Test goal is to identify and remove performance bottlenecks"}
{"id": "pdf::Ch9 SystemTesting::2293", "page_id": "pdf::Ch9 SystemTesting", "title": "Ch9 SystemTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch9 SystemTesting.pdf", "section": "Ch9 SystemTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/WmjXwHonTiWeR2kqIPAcn0ymnIr", "source_type": "pdf", "n_chars": 688, "text": "ness \nand stability. \nØThe Performance Test goal is to identify and remove performance bottlenecks \nfrom an application. It is a subset of performance engineering.\nØ This test is mainly performed to check whether the software meets the \nexpected requirements for application speed, scalability, and stability.\nSpeed – Determines whether the application responds quickly\nScalability – Determines maximum user load the software application can handle.\nStability – Determines if the application is stable under varying loads\n\n22\nCommon Performance Problems\nØLong Load time –Load time is normally the initial time it takes an application to start. This \nshould generally be kept to a minimum."}
{"id": "pdf::Ch9 SystemTesting::2294", "page_id": "pdf::Ch9 SystemTesting", "title": "Ch9 SystemTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch9 SystemTesting.pdf", "section": "Ch9 SystemTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/WmjXwHonTiWeR2kqIPAcn0ymnIr", "source_type": "pdf", "n_chars": 625, "text": "ly the initial time it takes an application to start. This \nshould generally be kept to a minimum. \nØPoor response time –Response time is the time it takes from when a user inputs data into \nthe application until the application outputs a response to that input. \nØPoor scalability –A software product suffers from poor scalability when it cannot handle \nthe expected number of users or when it does not accommodate a wide enough range of \nusers.\nØBottlenecking –Bottlenecks are obstructions in a system which degrade overall system \nperformance. Bottlenecking is when either coding errors or hardware issues cause a decrease"}
{"id": "pdf::Ch9 SystemTesting::2295", "page_id": "pdf::Ch9 SystemTesting", "title": "Ch9 SystemTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch9 SystemTesting.pdf", "section": "Ch9 SystemTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/WmjXwHonTiWeR2kqIPAcn0ymnIr", "source_type": "pdf", "n_chars": 635, "text": "ystem \nperformance. Bottlenecking is when either coding errors or hardware issues cause a decrease \nof throughput under certain loads. Bottlenecking is generally fixed by either fixing poor \nrunning processes or adding additional Hardware.\nØSomecommon performance bottlenecksare\n§CPU utilization\n§Memory utilization\n§Network utilization\n§Disk usage\n\n25\nPerformance Testing Metrics: Parameters Monitored\n§Processor Usage –an amount of time processor spends executing non-idle threads.\n§Memory use –amount of physical memory available to processes on a computer.\n§Disk time –amount of time disk is busy executing a read or write request."}
{"id": "pdf::Ch9 SystemTesting::2296", "page_id": "pdf::Ch9 SystemTesting", "title": "Ch9 SystemTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch9 SystemTesting.pdf", "section": "Ch9 SystemTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/WmjXwHonTiWeR2kqIPAcn0ymnIr", "source_type": "pdf", "n_chars": 653, "text": "processes on a computer.\n§Disk time –amount of time disk is busy executing a read or write request.\n§Bandwidth –shows the bits per second used by a network interface.\n§Response time –time from when a user enters a request until the first character of the response is \nreceived.\n§Throughput –rate a computer or network receives requests per second.\n§Hits per second –the no. of hits on a web server during each second of a load test.\n§……\n\n26\nExample Performance Test Cases\nØBaseline Test:To run each scenario with 1 Vuser and multiple iterations in order to identify \nwhether the application performance meets the business Service Level Agreement or not."}
{"id": "pdf::Ch9 SystemTesting::2297", "page_id": "pdf::Ch9 SystemTesting", "title": "Ch9 SystemTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch9 SystemTesting.pdf", "section": "Ch9 SystemTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/WmjXwHonTiWeR2kqIPAcn0ymnIr", "source_type": "pdf", "n_chars": 680, "text": "to identify \nwhether the application performance meets the business Service Level Agreement or not.\nØVerify response time is not more than 4 secs when 1000 users access the website simultaneously.\nØVerify response time of the Application Under Load is within an acceptable range when the \nnetwork connectivity is slow\nØVerify response time of the application under low, moderate and heavy load conditions.\nØCheck the maximum number of users that the application can handle before it crashes.\nØCheck database execution time when 500 records are read/written simultaneously.\nØCheck CPU and memory usage of the application and the database server under peak load \nconditions\n\n27\n\n\n28"}
{"id": "pdf::Ch9 SystemTesting::2298", "page_id": "pdf::Ch9 SystemTesting", "title": "Ch9 SystemTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch9 SystemTesting.pdf", "section": "Ch9 SystemTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/WmjXwHonTiWeR2kqIPAcn0ymnIr", "source_type": "pdf", "n_chars": 624, "text": "PU and memory usage of the application and the database server under peak load \nconditions\n\n27\n\n\n28\nTypes of Performance Testing\nØLoad testing –checks the application’s ability to perform under anticipated user loads. \nThe objective is to identify performance bottlenecks before the software application \ngoes live.\nØStress testing –involves testing an application under extreme workloads to see how it \nhandles high traffic or data processing. The objective is to identify the breaking point of \nan application.\nØEndurance testing –is done to make sure the software can handle the expected load over \na long period of time."}
{"id": "pdf::Ch9 SystemTesting::2299", "page_id": "pdf::Ch9 SystemTesting", "title": "Ch9 SystemTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch9 SystemTesting.pdf", "section": "Ch9 SystemTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/WmjXwHonTiWeR2kqIPAcn0ymnIr", "source_type": "pdf", "n_chars": 677, "text": "esting –is done to make sure the software can handle the expected load over \na long period of time.\nØSpike testing –tests the software’s reaction to sudden large spikes in the load generated \nby users.\nØVo l u m e t e s t i n g– Under V olume Testing large no. of. Data is populated in a database and \nthe overall software system’s behavior is monitored. The objective is to check software \napplication’s performance under varying database volumes.\n\n29\nPerformance Testing Vs Load Testing Vs Stress Testing\nPerformance Testing is the superset for both load & stress testing.\nØThe primary goal of performance testing includes establishing the \nbenchmark behavior of the system."}
{"id": "pdf::Ch9 SystemTesting::2300", "page_id": "pdf::Ch9 SystemTesting", "title": "Ch9 SystemTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch9 SystemTesting.pdf", "section": "Ch9 SystemTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/WmjXwHonTiWeR2kqIPAcn0ymnIr", "source_type": "pdf", "n_chars": 636, "text": "e primary goal of performance testing includes establishing the \nbenchmark behavior of the system. \nØThe benchmark and standard of the application should be set in terms \nof attributes like speed, response time, throughput, resource usage, \nand stability. All these attributes are tested in a performance test.\nØExposing defects in an application related to buffer overflow, memory \nleaks and mismanagement of memoryetc.\n\n30\n\n\n31\n\n\n32\nLoad Vs Stress Vs Volume Testing\nIn volume testing, it is checked as for how the system behaves against a \ncertain volume of data. \nThus, the databases are stuffed with their maximum capacity and their"}
{"id": "pdf::Ch9 SystemTesting::2301", "page_id": "pdf::Ch9 SystemTesting", "title": "Ch9 SystemTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch9 SystemTesting.pdf", "section": "Ch9 SystemTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/WmjXwHonTiWeR2kqIPAcn0ymnIr", "source_type": "pdf", "n_chars": 654, "text": "a \ncertain volume of data. \nThus, the databases are stuffed with their maximum capacity and their \nperformance levels like response time and server throughput are monitored.\n\n33\nPerformance Testing Process\n1.Identify your testing environment –Know your physical test environment, production \nenvironment and what testing tools are available. Understand details of the hardware, \nsoftware and network configurations\n2.Identify the performance acceptance criteria –This includes goals and constraints for \nthroughput, response times and resource allocation. It is also necessary to identify project \nsuccess criteria outside of these goals and constraints."}
{"id": "pdf::Ch9 SystemTesting::2302", "page_id": "pdf::Ch9 SystemTesting", "title": "Ch9 SystemTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch9 SystemTesting.pdf", "section": "Ch9 SystemTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/WmjXwHonTiWeR2kqIPAcn0ymnIr", "source_type": "pdf", "n_chars": 675, "text": "It is also necessary to identify project \nsuccess criteria outside of these goals and constraints. \nTesters should be empowered to set performance criteria and goals because often the \nproject specifications will not include a wide enough variety of performance benchmarks.\n\n34\nPerformance Testing Process\n3.Plan & design performance tests –Determine how usage is likely to vary amongst end users \nand identify key scenarios to test for all possible use cases. It is necessary to simulate a variety \nof end users, plan performance test data and outline what metrics will be gathered.\n4.Configuring the test environment –Prepare the testing environment before execution. Also,"}
{"id": "pdf::Ch9 SystemTesting::2303", "page_id": "pdf::Ch9 SystemTesting", "title": "Ch9 SystemTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch9 SystemTesting.pdf", "section": "Ch9 SystemTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/WmjXwHonTiWeR2kqIPAcn0ymnIr", "source_type": "pdf", "n_chars": 695, "text": "hered.\n4.Configuring the test environment –Prepare the testing environment before execution. Also, \narrange tools and other resources.\n5.Implement test design –Create the performance tests according to your test design.\n6.Run the tests –Execute and monitor the tests.\n7.Analyze, tune and retest– Consolidate, analyze and share test results. Then fine tune and test \nagain to see if there is an improvement or decrease in performance. Since improvements \ngenerally grow smaller with each retest, stop when bottlenecking is caused by the CPU. Then \nyou may have the consider option of increasing CPU power.\n\n35\nPerformanceTuning\n\n36\nPerformance Testing Automation\nadvantages of Automation Testing:"}
{"id": "pdf::Ch9 SystemTesting::2304", "page_id": "pdf::Ch9 SystemTesting", "title": "Ch9 SystemTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch9 SystemTesting.pdf", "section": "Ch9 SystemTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/WmjXwHonTiWeR2kqIPAcn0ymnIr", "source_type": "pdf", "n_chars": 653, "text": "U power.\n\n35\nPerformanceTuning\n\n36\nPerformance Testing Automation\nadvantages of Automation Testing:\n§The same test script can be used for every execution by just \nmaking changes in test data (wherever required)\n§Execution time is much less compared to manual execution\n§Consistent results\n\n37\nPerformance Test Tools\n1.HP LoadRunner–is the most popular performance testing tools on the market today. This tool is \ncapable of simulating hundreds of thousands of users, putting applications under real-life loads to \ndetermine their behavior under expected loads.Loadrunnerfeatures a virtual user generator which \nsimulates the actions of live human users."}
{"id": "pdf::Ch9 SystemTesting::2305", "page_id": "pdf::Ch9 SystemTesting", "title": "Ch9 SystemTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch9 SystemTesting.pdf", "section": "Ch9 SystemTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/WmjXwHonTiWeR2kqIPAcn0ymnIr", "source_type": "pdf", "n_chars": 696, "text": "loads.Loadrunnerfeatures a virtual user generator which \nsimulates the actions of live human users.\n2.ApacheJmeter–one of the leading tools used for load testing of web and application servers\nLoadRunner Architecture Diagram\n\n38\n1.Surfing the Products Page of Amazon.com\n2.Checkout\n3.Payment Processing\n4.Checking MyAccount Page\nSuppose you are assigned to check the performance of Amazon.com for 5000 users\n1.Virtual User Generator (VUGen) ------- Create VUGen Scripts\nØA rich coding editor and used to replicate System Under Load (SUL) behavior.\nØProvides a “recording” feature which records communication to and from client \nand Server in form of a coded script – also called VUser script."}
{"id": "pdf::Ch9 SystemTesting::2306", "page_id": "pdf::Ch9 SystemTesting", "title": "Ch9 SystemTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch9 SystemTesting.pdf", "section": "Ch9 SystemTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/WmjXwHonTiWeR2kqIPAcn0ymnIr", "source_type": "pdf", "n_chars": 654, "text": "communication to and from client \nand Server in form of a coded script – also called VUser script.\nVUGen can record to simulate following business processes:\n\n39\n2.Controller-------- Scenario Creation /Scenario Execution\nControls the Load simulation by managing, for example:\n§How many VUsers to simulate against each business process or VUser Group\n§Behavior of VUsers (ramp up, ramp down, simultaneous or concurrent nature etc.)\n§Nature of Load scenario e.g. Real Life or Goal Oriented or verifying SLA\nSuppose you are assigned to check the performance of Amazon.com for 5000 users\n\n40\nController will add the following parameter to the VUGen Script"}
{"id": "pdf::Ch9 SystemTesting::2307", "page_id": "pdf::Ch9 SystemTesting", "title": "Ch9 SystemTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch9 SystemTesting.pdf", "section": "Ch9 SystemTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/WmjXwHonTiWeR2kqIPAcn0ymnIr", "source_type": "pdf", "n_chars": 692, "text": "ce of Amazon.com for 5000 users\n\n40\nController will add the following parameter to the VUGen Script\n1)3500 Users areSurfing the Products Page of Amazon.com\n2)750 Users are inCheckout\n3)500 Users areperforming Payment Processing\n4)250 Users areChecking MyAccount Page ONLY after 500 \nusers have done Payment Processing\n1)Initiate 5 VUsers every 2 seconds till a load of 3500 \nVUsers (surfing Amazon product page) is achieved.\n2)Iterate for 30 minutes\n3)Suspend iteration for 25 VUsers\n4)Re-start 20 VUSers\n5)Initiate 2 users (in Checkout, Payment Processing, \nMyAccounts Page) every second.\n6)2500 VUsers will be generated at Machine A\n7)2500 VUsers will be generated at Machine B\nmore complex"}
{"id": "pdf::Ch9 SystemTesting::2308", "page_id": "pdf::Ch9 SystemTesting", "title": "Ch9 SystemTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch9 SystemTesting.pdf", "section": "Ch9 SystemTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/WmjXwHonTiWeR2kqIPAcn0ymnIr", "source_type": "pdf", "n_chars": 648, "text": "00 VUsers will be generated at Machine A\n7)2500 VUsers will be generated at Machine B\nmore complex \nscenarios are possible\nSuppose you are assigned to check the performance of Amazon.com for 5000 users\n\n41\n3.Analysis ------- (Results Analysis)\n§During the execution, Controller creates a dump of results in raw form\n•The “Analysis” component reads this file to perform various types of analysis \nand generates graphs\n•These graphs show various trends to understand the reasoning behind errors and failure \nunder load; thus help to figure whether optimization is required in Server or infrastructure.\nBandwidth could be \ncreating a bottleneck"}
{"id": "pdf::Ch9 SystemTesting::2309", "page_id": "pdf::Ch9 SystemTesting", "title": "Ch9 SystemTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch9 SystemTesting.pdf", "section": "Ch9 SystemTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/WmjXwHonTiWeR2kqIPAcn0ymnIr", "source_type": "pdf", "n_chars": 659, "text": "her optimization is required in Server or infrastructure.\nBandwidth could be \ncreating a bottleneck\nSuppose you are assigned to check the performance of Amazon.com for 5000 users\n\n42\nJmeter\nØ‘Apache JMeter’ is an open source, 100% java-based application with a graphical \ninterface,whichcananalyze and measure the performance of web application or a \nvariety of services. \nØDeveloped byStefano Mazzocchiof the Apache Software Foundation. \nØPrimarily written to test the performance of Apache JServ(currently known as Apache Tomcat project).\nhttps://jmeter.apache.org\n\n43\nJMeter Features\nØOpen source application\nØUser-friendly GUI： simple and interactive GUI."}
{"id": "pdf::Ch9 SystemTesting::2310", "page_id": "pdf::Ch9 SystemTesting", "title": "Ch9 SystemTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch9 SystemTesting.pdf", "section": "Ch9 SystemTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/WmjXwHonTiWeR2kqIPAcn0ymnIr", "source_type": "pdf", "n_chars": 655, "text": "he.org\n\n43\nJMeter Features\nØOpen source application\nØUser-friendly GUI： simple and interactive GUI.\nØSupport various testing approach:like Load Testing, Distributed Testing, and Functional Testing, etc.\nØPlatform independent:run on any environment /workstation that accepts a Java virtual machine\nØSupport various server types:highly extensible for different server : Web, Database, Mail...\nØSupport multi-protocol:protocols such as HTTP , JDBC, LDAP , SOAP , JMS, and FTP…\nØSimulation:using virtual users to generate heavy load against web application under test.\nØFramework: multi-threading framework which allows concurrent and simultaneous sampling of"}
{"id": "pdf::Ch9 SystemTesting::2311", "page_id": "pdf::Ch9 SystemTesting", "title": "Ch9 SystemTesting.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/Ch9 SystemTesting.pdf", "section": "Ch9 SystemTesting.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/WmjXwHonTiWeR2kqIPAcn0ymnIr", "source_type": "pdf", "n_chars": 429, "text": "r test.\nØFramework: multi-threading framework which allows concurrent and simultaneous sampling of \ndifferent functions by many or separate thread groups.\nØRemote distributed testing:Master-Slave concept for distributed testing where master will distribute \ntests among all slaves and slaves will execute scripts against your server.\nØTest result visualization:viewed in different formats like graph, table, tree, and report etc."}
{"id": "pdf::REVIEW::2312", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 667, "text": "Software Testing & Maintenance\nReview\nYanxia Liu cslyx@scut.edu.cn\nSpring, 2025\n1\n\nContents\n PART 1: Main Contents of Course\n PART 2: Exam Issue\n2\n\n3\nPART 1: Main Contents of Course\nStatic Program Analysis not included\nKey Topic\nCall-Graph & MM based Integration not included\n\n\nChapter 1 Introduction\n Why do we test software? \n 1.1 What is software?\n 1.2 What is bug?\n 1.3 Fault, Error and Failure\n The theory of Testing \n 2.1 Verification and Validation\n 2.2 Goals of Testing Software\n4\n\n1.1 What is Software ?\n A software system usually consists of a number of : \n Instructions within separate programs that when executed give some \ndesired function"}
{"id": "pdf::REVIEW::2313", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 687, "text": "number of : \n Instructions within separate programs that when executed give some \ndesired function\n Data structures that enable the programs to adequately manipulate \ninformation\n Configuration files which are used to set up these programs\n System documentation which describes the structure of the system\n User documentation which explains how to use the system and web sites \nfor users to download recent product information\n5\n\n1.2 What is Bug ?\n What is your understanding for Bug?\n Bugs a.k.a. … Defect\n Fault\n Problem\n Error\n Incident\n Anomaly\n Variance\n Failure\n Inconsistency\n Product \nAnomaly\n Product \nIncidence\n Feature :-)\nThe term Bug is used informally\n6"}
{"id": "pdf::REVIEW::2314", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 685, "text": "onsistency\n Product \nAnomaly\n Product \nIncidence\n Feature :-)\nThe term Bug is used informally\n6\n\nSoftware Fault : A static defect in the software\nSoftware Failure : External, incorrect behavior with respect to the requirements \nor other description of the expected behavior\nSoftware Error : An incorrect internal state that is the manifestation of some fault\n1.3 Fault, Error and Failure\n Use Terms that have precise, defined, and unambiguous meanings\nSometimes bug mean fault, sometimes error, sometimes failure\n… often the speaker doesn’t know what it means !\n7\n\nExecution/Reachability: \nThe location or locations in the program that contain the faults must be reached\nInfection:"}
{"id": "pdf::REVIEW::2315", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 666, "text": "lity: \nThe location or locations in the program that contain the faults must be reached\nInfection: \nThe state of the program must be incorrect\nPropagation : \nThe infected state must propagate to cause some output of the program to be \nincorrect .\nPIE Model\nA test may not execute the location of the fault !\nA test executing the fault may not produce an error!\nAn error may not be propagate to the output !\n8\n\n Verification : The process of determining whether the products of a given \nphase of the software development process fulfill the requirements \nestablished during the previous phase\n Validation : The process of evaluating software at the end of software"}
{"id": "pdf::REVIEW::2316", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 637, "text": "during the previous phase\n Validation : The process of evaluating software at the end of software \ndevelopment to ensure compliance with intended usage\n• IV&V stands for “independent verification and validation”\n2.1 Validation & Verification (IEEE)\n\n10\nValidation & Verification (IEEE)\n\n11\n2.2 Software Testing Axioms\n1. It is impossible to test a program completely.\n2. Software testing is a risk-based exercise.\n3. Testing cannot show the absence of bugs.\n4. The more bugs you find, the more bugs there are.\n5. Not all bugs found will be fixed.\n6. It is difficult to say when a bug is indeed a bug.\n7. Specifications are never final."}
{"id": "pdf::REVIEW::2317", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 670, "text": "be fixed.\n6. It is difficult to say when a bug is indeed a bug.\n7. Specifications are never final.\n8. Software testers are not the most popular members of a project.\n9. Software testing is a disciplined and technical profession.\n\n12\n2.3 Goals of a Software Tester\nTo identify the ideal test – that is, the minimum test data required to\nensure that the software works for all inputs.\n\nChapter 2 Testing in the Software Process\n Waterfall Model\n Spiral Model\n V Model\n W Model\n Agile Model - XP\n13\n\n14\n1. Waterfall Model\n All the planning is done at the beginning,\nand once created it is not to be changed.\n There is no overlap between any of the\nsubsequent phases."}
{"id": "pdf::REVIEW::2318", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 648, "text": "d once created it is not to be changed.\n There is no overlap between any of the\nsubsequent phases.\n Often anyone’s first chance to “see” the\nprogram is at the very end once the \ntesting is complete.\n\n\n15\n2. Spiral Model\n Risk-driven development \nprocess\n Combination of waterfall \nmodel and Rapid Prototype \nIteration model\n Begins with a design goal \nand ends with the client \nreviewing the progress.\n\n16\n3. V Model\n Extension of the Waterfall model\n emphasizes Verification & Validation by marking the relationships between each phase of the \nlife cycle and testing activities\n Once the code implementation is finished the testing begins."}
{"id": "pdf::REVIEW::2319", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 680, "text": "e \nlife cycle and testing activities\n Once the code implementation is finished the testing begins.\n Starts with unit testing, and moves up one test level at a time until the acceptance testing \nphase is completed\n\n\n17\nV Model\n Each document produced is associated with pairs of phases in the model.\n– (a) the User Requirements Specification. URS\n– (b) the System Requirements Specification, SRS\n– (c) the System Design Specifications, SDS\n– (d) Detailed Design Specifications, DDS\n\n\n18\n4. W Model\n Extension of V Model/Both V\n Testing is not after the code \nimplementation .\n Parallel to the development \nprocess, the test process is \ncarried out."}
{"id": "pdf::REVIEW::2320", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 694, "text": "code \nimplementation .\n Parallel to the development \nprocess, the test process is \ncarried out. \n Co-operation between \ndevelopment and testing \n Testing is more than just \nconstruction, execution and \nevaluation of test cases. \n\n\n19\n5. Agile Model\n Testing Throughout the Lifecycle\n Shift-Left Testing: Start testing during the requirements phase, parallel to \ndevelopment\n Continuous Testing: Integrate testing into every iteration to ensure quality for \neach incremental release.\n Test-Driven Development (TDD)\n Write unit tests first → Develop code to pass tests → Refactor code.\n Define requirements through tests to ensure code meets expectations and \nremains maintainable.\n\n20"}
{"id": "pdf::REVIEW::2321", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 674, "text": "Define requirements through tests to ensure code meets expectations and \nremains maintainable.\n\n20\nAgile Model\n Acceptance Testing Aligned with User Stories\n Define acceptance criteria for each user story, with tests designed around these \ncriteria.\n Continuous Feedback and Improvement\n Use daily builds and continuous integration (CI) to automate tests\n Automation as the Backbone\n Test Pyramid:\n High volume of unit tests (fast, low-cost, code-level coverage).\n Middle: Integration/API tests (validate module interactions).\n Top: Fewer end-to-end (UI) tests (simulate user workflows, costly but critical for \nkey paths).\n\nChapter 3 Principles of Software Testing"}
{"id": "pdf::REVIEW::2322", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 690, "text": "late user workflows, costly but critical for \nkey paths).\n\nChapter 3 Principles of Software Testing\n Static and Dynamic Verification\n Black and White Box Testing\n21\n\n22\n1. Static and Dynamic Verification\n Static Verification does not require the execution of the software code, while \nDynamic Verification does.\n Static Verification (or Static Analysis) can be as straightforward as having \nsomeone of training and experience reading through the code to search for \nfaults.\n Dynamic Verification (or Software Testing) confirms the operation of a \nprogram by executing it.\n\n23\n2. Black and White Box Testing\n Black Box testing is based entirely on the program specification and aims to"}
{"id": "pdf::REVIEW::2323", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 675, "text": "d White Box Testing\n Black Box testing is based entirely on the program specification and aims to \nverify that the program meets the specified requirements\n White box testing uses the implementation of the software to derive the tests. \nThe tests are designed to exercise some aspect of the program code\n\nChapter 4 BlackBox Testing\n Equivalence Partitioning\n Boundary Value Analysis\n Combinational Testing\n Random Testing and Error Guessing\n Scenario Testing\n24\n\n25\n1. Equivalence Partitioning\n Example\nConsider a method,\n– boolean isNegative(int x),\nThis accepts a single Java \nint as its input parameter. The \nmethod returns true if x is \nnegative, otherwise false."}
{"id": "pdf::REVIEW::2324", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 660, "text": "ngle Java \nint as its input parameter. The \nmethod returns true if x is \nnegative, otherwise false.\nTwo equivalence partitions for the parameter x can be identified:\n– 1. Integer.MIN V ALUE..-1\n– 2. 0..Integer.MAX V ALUE\n An Equivalence Partition (EP) is a range of values for a parameter for which \nthe specification states equivalent processing.\n\n26\n Valid equivalence Class\n A meaningful set of data in an input field. \n Used to verify whether the system function and performance can be correctly implemented.\n Invalid equivalence class\n A meaningless set of data in an input field. \n Used to test the fault tolerance of the system.\nEquivalence Class"}
{"id": "pdf::REVIEW::2325", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 683, "text": "set of data in an input field. \n Used to test the fault tolerance of the system.\nEquivalence Class\nEquivalence classes form a partition of a set.\nPartition: collection of mutually disjoint subsets whose union is the entire set.\n\n27\nSteps to identify the test cases\n1. Identify the inputs/outputs from the specification\neg. input fields in a form, inputs to command line programs, outputs-messages, calculations etc.\n2. Identify the equivalence classes for the inputs/outputs identified\n For arange, 1 validclass(within the range) and two invalid class (one outside each end of the\nrange)\n If the input isa set of valid values, 1 valid class(from within the set) and1 invalid class"}
{"id": "pdf::REVIEW::2326", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 680, "text": "ange)\n If the input isa set of valid values, 1 valid class(from within the set) and1 invalid class\n(outside the set)\n If the input isa set of valuesand the program treatsinput values differently, 1 valid class for\neach allowed input and 1 invalid class (the set of all disallowed inputs).\n\n\n28\n For aBoolean, 1 validclass (true) and1 invalidclass (false)\n For amandatory input, empty(invalid) and valid inputs.\n If the input mustfollow rules, 1 valid class (conforming to the rule) and\nseveral invalid classes (violating the rule from different ways)\nDivide each input into equivalence classes and formequivalence class table,\nspecifying aunique IDfor each equivalence class."}
{"id": "pdf::REVIEW::2327", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 690, "text": "uivalence classes and formequivalence class table,\nspecifying aunique IDfor each equivalence class.\nSteps to identify the test cases\n\n29\n Boundary conditions are situations at the edge of the planned operational \nlimits of the software.\nE.g., negative to zero to positive numbers, exceeding the input field length of a form, \netc.\n Choose input data that lie on the boundary when formulating equivalence \npartitions.\nTest the valid data just inside the boundary\nTest the last possible valid data\nTest the invalid data just outside the boundary\n Security flaws such as buffer overflow attacks exploit boundaries of array \nbuffers.\n2. Boundary Value Analysis\nEquivalence \nclass\nOuter point"}
{"id": "pdf::REVIEW::2328", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 675, "text": "cks exploit boundaries of array \nbuffers.\n2. Boundary Value Analysis\nEquivalence \nclass\nOuter point\nInner point\n\n30\n3. Combinational Testing\n There are a number of different techniques for identifying relevant \ncombinations, such as Cause-Effect Graphs, Decision Tables and Truth Tables.\n The analysis of combinations involves identifying all the different combinations \nof input causes to the software and their associated output effects.\n The causes and effects are described as logical statements (or predicates), based \non the specification of the software. These expressions specify the conditions \nrequired for a particular variable to cause a particular effect.\n\n31"}
{"id": "pdf::REVIEW::2329", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 677, "text": "ssions specify the conditions \nrequired for a particular variable to cause a particular effect.\n\n31\nDecision Tables - Wikipedia\n precise yet compact way to model complicated logic \n Associate conditions with actions to perform\n Can associate many independent conditions with several actions in an elegant way\n\n32\nDecision Tables - Terminology\n\n\n33\n Test data is generated using random number generators. The distribution \nmay be uniform, or chosen to mimic, in a statistical sense, the type of inputs \nthat the program will receive in real use.\n If the specification is clearly written and thorough, then it should be possible \nto find the set(s) of possible input values."}
{"id": "pdf::REVIEW::2330", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 654, "text": "arly written and thorough, then it should be possible \nto find the set(s) of possible input values.\n The goal is to achieve a “reasonable” coverage of the possible values for \neach input parameter, based on its distribution. This can be determined \nheuristically (using, for example, 10 random values), or based on a statistical \nsample size determined from the required confidence in the coverage.\n4. Random Testing and Error Guessing\nRandom Testing \n\n34\n This is an ad-hoc approach, based on intuition and experience. \n Test data is selected that is likely to expose faults in the code. Some typical \nexamples of inputs likely to cause problems are:"}
{"id": "pdf::REVIEW::2331", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 624, "text": "likely to expose faults in the code. Some typical \nexamples of inputs likely to cause problems are:\n– Empty or null strings, arrays, lists, and class references. These may find code that \ndoes not check for empty or non-null values before using them.\n– Zero as a value, or as a count of instances or occurrences. These may find divide-by-\nzero faults.\n– Spaces or null characters in strings. This may find code that does not process strings \ncorrectly or does not trim whitespace before trying to extract data from the string.\n– Negative numbers. These may find faults in code that only expects to receive \npositive numbers."}
{"id": "pdf::REVIEW::2332", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 650, "text": ".\n– Negative numbers. These may find faults in code that only expects to receive \npositive numbers.\n The goal is to cover as many values as possible which in the experience of \nthe tester are likely to expose faults in the code\nError Guessing\n\n35\n Scenario Testing is a Software Testing Technique that uses scenarios i.e. \nspeculative stories to help the tester work through a complicated problem or test \nsystem. \n Scenario testing is performed to ensure that the end-to-end function of software \nand all the process flow of the software are working properly. \n In scenario testing, the testers assume themselves to be the end users and find the"}
{"id": "pdf::REVIEW::2333", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 694, "text": "g properly. \n In scenario testing, the testers assume themselves to be the end users and find the \nreal-world scenarios or use cases which can be carried out on the software by the \nend user. \n5. Scenario Testing\n\n36\nBasic flow and Alternative flow\n Basic Flow\n The simplest path through the use case, that is, without any error, \nthe program directly from the beginning to the end of the process.\n The most used operation process by most users, reflecting the \nmain functions and processes of the software. \n There is only one base flow for a business, and the base flow has \nonly one start and one end.\n Alternative Flow\n Start with a base flow, perform under a specific condition, and"}
{"id": "pdf::REVIEW::2334", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 696, "text": "and one end.\n Alternative Flow\n Start with a base flow, perform under a specific condition, and \nthen rejoin the base flow (such as alternative flows 1 and 3); \n Or originate from another alternative flow (such as alternative \nflow 2); \n Use cases can also be terminated without being added to the base \nflow (such as alternative flows 2 and 4)\n reflecting various exception and error conditions.\nUseCase Start\nAlternative \nFlow 3\nAlternative \nFlow 4\nAlternative \nFlow 1\nAlternative \nFlow 2\nUseCase End\n\n37\nScenario Testing Steps\nScenario Testing Goal\n Simulate the user to complete the operation of normal functions and core business \nlogic to verify the correctness of software functions;"}
{"id": "pdf::REVIEW::2335", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 690, "text": "ation of normal functions and core business \nlogic to verify the correctness of software functions;\n Simulate the main errors in user operation to verify the abnormal error handling \nability of software.\nAlternative flows, like the program execution paths, will cause the scenario explosion.\nTypical scenarios need to be selected for testing. \n(1) One and only one scenario contains the basic flow;\n(2) The minimum number of scenarios: the total of basic flows and alternative flows;\n(3) For an alternative flow: at least one scenario covering it, which try to avoid \ncovering other alternative flows\n\n38\n(1) According to the specification, describe the basic flow and alternative flow of"}
{"id": "pdf::REVIEW::2336", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 685, "text": "tive flows\n\n38\n(1) According to the specification, describe the basic flow and alternative flow of \nthe software under test.\n(2) Construct different scenarios to meet the requirements of test completeness and \nno redundancy.\n(3) Design corresponding test cases for each scenario.\n(4) Re-examine all generated test cases and remove redundant test cases. After the \ntest cases are determined, the test data values are determined for each test case.\nScenario Testing Steps\n\n39\n6. Summary： Strategies on BlackBox Testing\n1. For the specific input field in the specific function page, the refined test is carried \nout, using equivalence class and boundary value; Use static testing to check"}
{"id": "pdf::REVIEW::2337", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 696, "text": "ined test is carried \nout, using equivalence class and boundary value; Use static testing to check \nbuttons, links, content, images, etc;\n2. If the function description contains a combination of input conditions, and the \nbusiness logic is complex, decision table can be used.\n3. Boundary value analysis should be considered in any case, as it is one of the \nmost effective methods to find software defects.\n4. Test cases can be expanded by error guessing method, and the valuable \nexperience of test engineers is emphasized.\n5. For the system with clear business process, the scenario testing can be used \nthroughout the whole testing process\n\nChapter 5: White-Box Testing\n Control Flow Testing"}
{"id": "pdf::REVIEW::2338", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 636, "text": "be used \nthroughout the whole testing process\n\nChapter 5: White-Box Testing\n Control Flow Testing\n Statement Coverage\n Decision Coverage\n Condition Coverage\n Decision Condition Coverage\n Condition Combination Coverage\n Path Coverage\n Basis Path Testing\n40\n\n41\nControl Flow Testing\n Control-flow testing is a structural testing strategy that uses the program’s \ncontrol flow as a model.\n Requires the tester to have a clear understanding of the logical structure of the \nprogram, and even to be able to master all the details of the source program.\n Most applicable to new software for unit testing.\n\n42\n1. Statement Coverage"}
{"id": "pdf::REVIEW::2339", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 669, "text": "f the source program.\n Most applicable to new software for unit testing.\n\n42\n1. Statement Coverage\n Design test cases and work out input values required to ensure that every source \ncode statement is executed.\n Also known as point coverage\n The weakest logical coverage, be used interoperatively with other testing methods.\n\n43\n2. Decision Coverage (Branch Coverage)\n Design test cases and work out input values required to ensure that every source \ncode branch is taken.\n Each true and false branch of the program is executed at least once\n Also known as edge coverage\n\n44\n3. Condition Coverage\n A complex decision is formed from multiple (Boolean) conditions."}
{"id": "pdf::REVIEW::2340", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 675, "text": "verage\n\n44\n3. Condition Coverage\n A complex decision is formed from multiple (Boolean) conditions.\n Condition Coverage extends Branch Coverage by ensuring that, for complex \ndecisions, each condition within the decision is tested for its true and false values.\n There is a caveat: it is not necessary that the decision itself take on true and false \nvalues!\n Test data is selected to ensure that every condition in every decision takes on the \nvalue true and false.\n\n45\n4. Decision/Condition Coverage\n Generate test data such that all conditions in a decision take on both outcomes (if \npossible) at least once and exercise the true and false outcomes of every decision."}
{"id": "pdf::REVIEW::2341", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 666, "text": "h outcomes (if \npossible) at least once and exercise the true and false outcomes of every decision.\n Each decision has True and False test cases\n In addition, each condition in a decision has True and False test cases (if possible)\n It is a combination of Condition Coverage and Branch Testing. It uses the same test \ndata as for Condition Coverage but must additionally ensure that each branch or \ndecision takes a true or false outcome.\n Single condition decision: 2 test cases\n 2-condition decisions: 2+ test cases\n\n46\n5. Condition Combination Coverage\n Tests are generated to cause every possible combination of conditions for every \ndecision to be tested."}
{"id": "pdf::REVIEW::2342", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 662, "text": "s are generated to cause every possible combination of conditions for every \ndecision to be tested.\n The goal is to achieve 100% coverage of every decision and 100% coverage of \nevery condition.\n A Truth-Table is the best way to identify all the possible combinations of values.\n\n47\n6. Control Flow Graphs (CFGs)\nBeing able to create a Control Flow Graphs is essential for path testing \ntechniques.\n Directed graph G(V , E)\n V is set of vertices\n E is set of edges, E = V*V\n Represent the flow of control\n Each node represents one or more statements\n Each edge represents a ‘jump’ or ‘branch’\n Two exits=a decision (True or False)\n\n\n48\n7. Path Coverage"}
{"id": "pdf::REVIEW::2343", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 635, "text": "h edge represents a ‘jump’ or ‘branch’\n Two exits=a decision (True or False)\n\n\n48\n7. Path Coverage\n Generate test data to exercise all the distinct paths in a program. This is called \n“path coverage”\n Path coverage causes every possible path from entry to exit of the program to be \ntaken during test execution. \n The goal is to achieve 100% coverage of every start-to-finish path in the code.\n A path that makes i iterations through a loop is distinct from a path that makes \ni+1 iterations through a loop, even if the same nodes are visited in both iterations\nThus, there can be an infinite number of paths is some programs!\n\n49"}
{"id": "pdf::REVIEW::2344", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 696, "text": "are visited in both iterations\nThus, there can be an infinite number of paths is some programs!\n\n49\n Need to limit the number of paths: choose equivalence classes of paths\n Two paths are considered equivalent if they differ only in the number of \nloop iterations, giving two classes of loops:\n one with 0 iterations\n one with n iterations (n > 0)\n Other equivalence paths can also be chosen if required\nPath Coverage\n\n50\nThe CFG of a program can be described by a regular expression that \nuses the following operations:\n. is the concatenation of a sequence of nodes\n+ is a decision in the graph (i.e. an if statement)\n* is iteration (0 or more times, e.g. a while statement)\nPath Expression"}
{"id": "pdf::REVIEW::2345", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 636, "text": "h (i.e. an if statement)\n* is iteration (0 or more times, e.g. a while statement)\nPath Expression\n\n51\n8. Basis Path Testing\n Basis Path Testing is a White Box Testing method in which test cases are \ndefined based on flows or logical paths that can be taken through the program.\n The objective of basis path testing is to define the number of independent paths, \nso the number of test cases needed can be defined explicitly to maximize test \ncoverage.\n Basis path testing involves execution of all possible blocks in a program and \nachieves maximum path coverage with the least number of test cases. \n\n52\nSteps for Basis Path testing"}
{"id": "pdf::REVIEW::2346", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 698, "text": "hieves maximum path coverage with the least number of test cases. \n\n52\nSteps for Basis Path testing\n（1） Draw a control flow graph (to determine different program paths)\n（2） Calculate Cyclomatic complexity\n(metrics to determine the number of independent paths)\n（3） Find a basis set of paths \n（4） Generate test cases to exercise each path\n\n53\nStep2: Calculate McCabe’s Cyclomatic complexity\n Three methods to compute Cyclomatic Complexity V(G)\nV(G) = E - N + 2 E = Number of edges, N =Number of Nodes \nV (G) = P + 1 P = Number of decision nodes (node that contains condition)\nV(G) = R R= Number of regions\n\nChapter 6: Test documentation\n Test Plan\nTest Case\nBug Report\nTest Summary Report\n54\n\n55"}
{"id": "pdf::REVIEW::2347", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 679, "text": "gions\n\nChapter 6: Test documentation\n Test Plan\nTest Case\nBug Report\nTest Summary Report\n54\n\n55\n1. Test Plan\n A TEST PLAN is a document describing software testing scope and activities. \nIt is the basis for formally testing any software / product in a project.\n the scope, approach, resources and schedule of intended test activities.\n Master Test Plan: A single high-level test plan for a project / product that \nunifies all other test plans.\n Testing Level Specific: Test plans for each level of testing:\n Unit Test Plan\n Integration Test Plan\n System Test Plan\n Acceptance Test Plan\n Testing Type Specific:Test plans for specific types of testing like Performance"}
{"id": "pdf::REVIEW::2348", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 691, "text": "ptance Test Plan\n Testing Type Specific:Test plans for specific types of testing like Performance \nTest Plan and Security Test Plan.\n\n56\nTest Planning Process\n1) Define test strategy\n2) Define test system\n3) Estimate test effort\n4) Prepare and review test plan\n\n57\n2. Test Case\n A TEST CASE is a documented set of preconditions (prerequisites), procedures \n(inputs / actions) and postconditions (expected results) which a tester uses to \ndetermine whether a system under test satisfies requirements or works \ncorrectly. \n A test case can have one or multiple test scripts . \n A sequence of instructions for the execution of a test\n A collection of test cases is called a test suite.\n\n58"}
{"id": "pdf::REVIEW::2349", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 662, "text": "f instructions for the execution of a test\n A collection of test cases is called a test suite.\n\n58\n3. Bug Report\n A bug report is a document that outlines information about what’s \nwrong with the software. \n It lists the reasons or seen errors to point out what exactly is viewed as \nwrong, and also includes a request and/or details for how to address it.\n A bug report needs to be clear, actionable and simple to complete.\n The point of writing a defect report (bug report) is to get bugs fixed.\n“This is what we have, this is what \nwe should have instead, so fix it.”\n\n59\nA good bug report:\n Contains the information needed to reproduce and fix problems"}
{"id": "pdf::REVIEW::2350", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 660, "text": "so fix it.”\n\n59\nA good bug report:\n Contains the information needed to reproduce and fix problems\n Is an efficient form of communication for both bug reporter and \nbug receiver\n Can be and is resolved as fast as possible\n Is sent to the person in charge\n Is filed in a defined way\n Establishes a common ground for collaboration\nBug Report\n\n60\n4. Test Summary Report\n Test Summary Report is an important deliverable which is prepared at the \nend of a Testing project, or rather after Testing is completed. \n The prime objective of this document is to explain various details and \nactivities about the Testing performed for the Project, to the respective"}
{"id": "pdf::REVIEW::2351", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 689, "text": "ain various details and \nactivities about the Testing performed for the Project, to the respective \nstakeholders like Senior Management, Client, etc.\n After performing exhaustive testing, publishing the test results, metrics, best \npractices, lessons learned, conclusions on ‘Go Live’ etc. are extremely \nimportant to produce that as evidence for the Testing performed and the \nTesting conclusion.\n\nChapter 7: Unit Testing\n What do we test?\n Unit Testing\nTest-Driven Development (TDD)\nAutomated Unit Testing\n61\n\n62\n2. Unit Testing\n Unit tests are mainly whitebox tests written by developers, and designed \nto verify small units of program functionality.\n• Key Metaphor: I.C. Testing"}
{"id": "pdf::REVIEW::2352", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 664, "text": "elopers, and designed \nto verify small units of program functionality.\n• Key Metaphor: I.C. Testing\n Integrated Circuits are tested individually for functionality before the whole circuit is \ntested.\n• Definitions\n Whitebox – Unit tests are written with full knowledge of implementation details.\n Developers – Unit tests are written by you, the developer, concurrently with \nimplementation.\n Small Units – Unit tests should isolate one piece of software at a time.\n• Individual methods and classes\n Verify – Make sure you built ‘the software right.’ Testing against the contract.\n• Contrast this with validation\n\n63\nRole of Unit Testing\nHelps localize errors"}
{"id": "pdf::REVIEW::2353", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 680, "text": "ainst the contract.\n• Contrast this with validation\n\n63\nRole of Unit Testing\nHelps localize errors\n Failure indicates problem in the unit under test\n Find errors early\n Unit tests are written during development, usually by developer\n More expensive to fix defects found later by another team\n Avoid unnecessary functionality\n Write test first, only write enough code to get it working\nImprove code quality code\n Helps developer deliver working code\n Assure minimum quality of units before integration into system\n\n64\n3. Test-Driven Development\nAn excellent practice promoted by the iterative and agile XP method , also \nknown as test-first development\nAdvantages"}
{"id": "pdf::REVIEW::2354", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 692, "text": "e promoted by the iterative and agile XP method , also \nknown as test-first development\nAdvantages\n The unit tests actually get written\n Programmer satisfaction leading to more consistent test writing\n Clarification of detailed interface and behavior\n Provable, repeatable, automated verification\n The confidence to change things\n\n65\n4. Automated Unit Test\nTesting Framework are tools that help manage and run your unit tests.\nxUnit Framework： JUnit(java), CppUnit(c++), NUnit(.Net)\n Help achieve three properties of good unit tests:\n• Automatic\n Tests should be easy to run and check for correct completion.\n This allows developers to quickly confirm their code is working after a"}
{"id": "pdf::REVIEW::2355", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 682, "text": "for correct completion.\n This allows developers to quickly confirm their code is working after a \nchange.\n• Repeatable\n Any developer can run the tests and they will work right away.\n• Independent\n Tests can be run in any order and they will still work.\n\nChapter 8: Integration Testing\n What is Integration Testing\n Approaches to Integration Testing\n Decomposition-based Integration\n66\n\n67\n1. Definitions – Integration Tests\n Integration test data is selected to ensure that the components or \nsub-systems of a system are working correctly together.\n Test cases will explore different interactions between the \ncomponents, and make sure the correct results are produced.\n\n68"}
{"id": "pdf::REVIEW::2356", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 663, "text": "different interactions between the \ncomponents, and make sure the correct results are produced.\n\n68\nDrivers and Stubs\n Drivers and Stubs are temporary \nsoftware components\n A test driver calls the software under test, \npassing the test data as inputs.\n In manual testing, where the system \ninterface has not been completed, a test \ndriver is used in its place to provide the \ninterface between the test user and the \nsoftware under test.\n\n\n69\n Drivers\n Drivers can have varying levels of sophistication.\n It could be hard-coded to run through a fixed series of input values, read \ndata from a prepared file, contain a suitable random number generator \netc.."}
{"id": "pdf::REVIEW::2357", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 691, "text": "of input values, read \ndata from a prepared file, contain a suitable random number generator \netc..\nIntegration Testing – Drivers and Stubs\n Stubs\n A stub is a temporary or dummy software that is required by the software \nunder test to operate properly. \n This is a throw-away version to allow testing to take place.\n It will provide a fixed or limited set of values to be passed to the software \nunder test.\n\n70\n2 Decomposition-based Integration\n In this strategy, do the decomposition based on the functional characteristics of the system.\n A functional characteristic is defined by what the module does, that is, actions or \nactivities performed by the module.\nBig bang integration"}
{"id": "pdf::REVIEW::2358", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 694, "text": "what the module does, that is, actions or \nactivities performed by the module.\nBig bang integration\n big-bang groups the whole system and test it in a single test phase.\nTop-down integration\n Top-down starts at the root of the tree and slowly work to lower level of the tree\nBottom-up integration\n Bottom-up mirrors top-down, it starts at the lower level implementation of\nthe system and work towards the main\nSandwich integration\n Sandwich is an approach that combines both top-down and bottom-up.\n\n71\nBig bang Integration\n Considers the whole system as a subsystem\n Tests all the modules in a single test session\n Only one integration testing session\nNo...\n– stubs\n– drivers\n– strategy"}
{"id": "pdf::REVIEW::2359", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 694, "text": "in a single test session\n Only one integration testing session\nNo...\n– stubs\n– drivers\n– strategy\n Very difficult fault isolation\n\n\n72\n Breadth-first traversal of the functional decomposition tree.\n• First step: Check main program logic, with all called units replaced by stubs that always return correct values.\n• Move down one level\n– replace one stub at a time with actual code.\n– any fault must be in the newly integrated unit\nTop-Down Integration\n Early SUT prototype\n Throw-away code programming\n\n73\nBottom-Up Integration\n Reverse of top-down integration\n Start at leaves of the functional decomposition tree.\n Driver units...\n– call next level unit\n– “drive” the unit with inputs"}
{"id": "pdf::REVIEW::2360", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 690, "text": "ctional decomposition tree.\n Driver units...\n– call next level unit\n– “drive” the unit with inputs\n As with top-down integration, one driver unit at a time is replaced with actual code.\n Any fault is (most likely) in the newly integrated code.\n Less throw-away code programming\n No prototype and Main program tested last\n\n\n74\nSandwich integration\n Combines top-down approach and bottom-up approach\n Generally, higher level modules use a top-down approach (stub)\n Normally, lower-level modules use a bottom-up approach (driver)\n Testing converges to the middle\n Number of integration sessions can vary\n Top and bottom layers can be done in parallel\n Less stubs and drivers needed"}
{"id": "pdf::REVIEW::2361", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 665, "text": "n sessions can vary\n Top and bottom layers can be done in parallel\n Less stubs and drivers needed\n Hard to isolate problems\n\n\nChapter 10: System Testing\n What is System Testing\n System Test Types\n Functional Testing\n Non-Functional Testing\n Regression Testing\n75\n\n76\n1. What is System Testing\n Tests the behavior of a system as a whole, with respect to scenarios and \nrequirements.\n Assumes all components already work well\n Integration testing finish( checking software quality by testing two or more dependent software \nmodules as a group or a (sub)system.)\n Black-box testing techniques are used.\n Reconciles software against top-level requirements"}
{"id": "pdf::REVIEW::2362", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 652, "text": "tem.)\n Black-box testing techniques are used.\n Reconciles software against top-level requirements\n Tests stem from concrete use cases in the requirements\n Verifies that the new SW system integrates with the existing environment. \nThis may include other systems, hardware, people and databases.\n\n77\n2. System Testing Types\n Test “types” classify the purpose of the test, rather than its scope or \nmechanism.\n Functional testing\n Ensure compliance with functional requirements\n Non-functional testing\n Ensure compliance with non-functional requirements\n Regression testing\n\n78\n2.1 System Testing ( Functional)\nThe default assumption in testing"}
{"id": "pdf::REVIEW::2363", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 657, "text": "ements\n Regression testing\n\n78\n2.1 System Testing ( Functional)\nThe default assumption in testing\n Functional testing verifies the software’s behavior matches expectations.\n Also includes testing bad inputs, to check implicit assumptions\n i.e., given nonsense input, the program should do “something reasonable”\n Cuts across all levels of testing, but heavy on unit testing\n The interface used for testing is the System Interface : the user interface, the network \ninterface, dedicated hardware interfaces, etc.\n\n79\n The selection of Test Cases is based on Black-Box Testing.\n Application of Scenario Testing, Equivalence Partitions, Boundary Value"}
{"id": "pdf::REVIEW::2364", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 694, "text": "ed on Black-Box Testing.\n Application of Scenario Testing, Equivalence Partitions, Boundary Value \nAnalysis, Error Guessing, Decision-Table Testing, Random Testing etc. is \nrelatively straightforward. \n Like Unit Testing, test cases and test data are selected using the technique being used.\n The only difference is that instead of calling a method with the specified parameters, the \ndata must be entered into the interface as appropriate, and then the results collected from \nthe interface.\nFunctional Testing Strategy\n\n80\n2.2 System Testing ( Non - Functional)\n Roughly, testing things that are not “functionality”\n Generally, tests quality of the software, also called the “-ilities”"}
{"id": "pdf::REVIEW::2365", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 661, "text": "that are not “functionality”\n Generally, tests quality of the software, also called the “-ilities”\n Usability\n Reliability\n Maintainability\n Security\n Performance\n Portability\n Recovery\n Robustness\n ……\n Nonfunctional testing is an umbrella term for many test types.\n Note these aren’t all mutually exclusive!\n Not all of these may be carried out on the product or be applicable to it.\n\n\n81\n2.3 Regression Testing\n Making sure that code changes haven’t broken existing functionality, \nperformance, security, etc.\n In practice, this means re-running tests after a code change\n With good test automation and good unit/integration/system/etc. tests,"}
{"id": "pdf::REVIEW::2366", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 694, "text": "tests after a code change\n With good test automation and good unit/integration/system/etc. tests, \nthis is literally running tests again after a change.\n\n\n82\n3. Performance Testing\n knows as ‘Perf Testing’, is a type of testing performed to check how \napplication or software performs under workload in terms of responsiveness \nand stability. \n The Performance Test goal is to identify and remove performance bottlenecks \nfrom an application. It is a subset of performance engineering.\n This test is mainly performed to check whether the software meets the \nexpected requirements for application speed, scalability, and stability.\nSpeed – Determines whether the application responds quickly"}
{"id": "pdf::REVIEW::2367", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 679, "text": "tion speed, scalability, and stability.\nSpeed – Determines whether the application responds quickly\nScalability – Determines maximum user load the software application can handle.\nStability – Determines if the application is stable under varying loads\n\n83\nCommon Performance Problems\n Long Load time – Load time is normally the initial time it takes an application to start. This \nshould generally be kept to a minimum. \n Poor response time – Response time is the time it takes from when a user inputs data into \nthe application until the application outputs a response to that input. \n Poor scalability – A software product suffers from poor scalability when it cannot handle"}
{"id": "pdf::REVIEW::2368", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 662, "text": "nput. \n Poor scalability – A software product suffers from poor scalability when it cannot handle \nthe expected number of users or when it does not accommodate a wide enough range of \nusers.\n Bottlenecking – Bottlenecks are obstructions in a system which degrade overall system \nperformance. Bottlenecking is when either coding errors or hardware issues cause a decrease \nof throughput under certain loads. Bottlenecking is generally fixed by either fixing poor \nrunning processes or adding additional Hardware.\n Some common performance bottlenecks are\n CPU utilization\n Memory utilization\n Network utilization\n Disk usage\n\n84\nTypes of Performance Testing"}
{"id": "pdf::REVIEW::2369", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 694, "text": "tilization\n Memory utilization\n Network utilization\n Disk usage\n\n84\nTypes of Performance Testing\n Load testing – checks the application’s ability to perform under anticipated user loads. \nThe objective is to identify performance bottlenecks before the software application \ngoes live.\n Stress testing – involves testing an application under extreme workloads to see how it \nhandles high traffic or data processing. The objective is to identify the breaking point of \nan application.\n Endurance testing – is done to make sure the software can handle the expected load over \na long period of time.\n Spike testing – tests the software’s reaction to sudden large spikes in the load generated"}
{"id": "pdf::REVIEW::2370", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 649, "text": "time.\n Spike testing – tests the software’s reaction to sudden large spikes in the load generated \nby users.\n V olume testing– Under V olume Testing large no. of. Data is populated in a database and \nthe overall software system’s behavior is monitored. The objective is to check software \napplication’s performance under varying database volumes.\n\n85\nPerformance Testing Vs Load Testing Vs Stress Testing\nPerformance Testing is the superset for both load & stress testing.\n The primary goal of performance testing includes establishing the \nbenchmark behavior of the system. \n The benchmark and standard of the application should be set in terms"}
{"id": "pdf::REVIEW::2371", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 670, "text": "rk behavior of the system. \n The benchmark and standard of the application should be set in terms \nof attributes like speed, response time, throughput, resource usage, \nand stability. All these attributes are tested in a performance test.\n Exposing defects in an application related to buffer overflow, memory \nleaks and mismanagement of memory etc.\n\n86\n\n\n87\n\n\n88\nLoad Vs Stress Vs Volume Testing\nIn volume testing, it is checked as for how the system behaves against a \ncertain volume of data. \nThus, the databases are stuffed with their maximum capacity and their \nperformance levels like response time and server throughput are monitored.\n\n89\nPerformance Test Tools"}
{"id": "pdf::REVIEW::2372", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 680, "text": "rformance levels like response time and server throughput are monitored.\n\n89\nPerformance Test Tools\n1. HP LoadRunner – is the most popular performance testing tools on the market today. This tool is \ncapable of simulating hundreds of thousands of users, putting applications under real-life loads to \ndetermine their behavior under expected loads. Loadrunner features a virtual user generator which \nsimulates the actions of live human users.\n2. Apache Jmeter– one of the leading tools used for load testing of web and application servers\nLoadRunner Architecture Diagram\n\nChapter 10: Static Testing\n Static Testing\n Code Review\n Static Program Analysis\n90\n\n91\n1. Static Testing"}
{"id": "pdf::REVIEW::2373", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 684, "text": "0: Static Testing\n Static Testing\n Code Review\n Static Program Analysis\n90\n\n91\n1. Static Testing\n Static testing is the process of carefully and methodically reviewing and \nanalyzing the software for bugs without executing it.\n Code Review\n Static Program Analysis\n This form of testing is very valuable and has advantages over execution-based \ntesting. Reported experience shows that a large number of faults can be found \nusing static testing.\n This has benefits in terms of cost and productivity because faults are found \n(and corrected) early on and less time is required for execution-based tests.\n\n92\n2. Code Review\nEssential elements of code review\n Identify problems:"}
{"id": "pdf::REVIEW::2374", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 663, "text": "or execution-based tests.\n\n92\n2. Code Review\nEssential elements of code review\n Identify problems:\n Find problems with the software such as missing items, mistakes, etc.\n Follow rules:\n Amount of code to be reviewed, how much time will be spent, etc.\n Prepare:\n Each participant should prepare in order to contribute to the review.\n Write a report:\n Summarize the results of the review, make report available to the \ndevelopment team.\n\n93\nInformal Code Review\n Peer reviews\n An informal small group of programmers and/or testers act as reviewers.\n Participants should follow the 4 essential elements even through the review is \ninformal.\n Walkthroughs"}
{"id": "pdf::REVIEW::2375", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 662, "text": "cipants should follow the 4 essential elements even through the review is \ninformal.\n Walkthroughs\n A more formal process in which the author of the code formally presents the code \nto a small group of programmers and/or testers.\n The author reads the code line by line explaining what it does, reviewers listen \nand ask questions.\n Participants should follow the 4 essential elements.\n\n94\nFormal Code Inspections\n An inspection is more comprehensive than a walk-through.\n Code presenter is not the author of the code.\n The other participants are the inspectors.\n There is a moderator to assure that the rules are followed and the meeting \nruns smoothly."}
{"id": "pdf::REVIEW::2376", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 632, "text": "tors.\n There is a moderator to assure that the rules are followed and the meeting \nruns smoothly. \n After the inspection a report is composed. The programmer then makes \nchanges and a re-inspection occurs, if necessary.\n Formal code inspections are effective at finding bugs in code and designs and \nare gaining in popularity.\n\nCode review checklist: Data reference errors\n Is an un-initialized variable referenced?\n Are array subscripts integer values and are they within the array’s bounds?\n Are there off-by-one errors in indexing operations or references to arrays?\n Is a variable used where a constant would work better?"}
{"id": "pdf::REVIEW::2377", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 631, "text": "dexing operations or references to arrays?\n Is a variable used where a constant would work better?\n Is a variable assigned a value that’s of a different type than the variable?\n Is memory allocated for referenced pointers?\n Are data structures that are referenced in different functions defined \nidentically?\n\nChapter 11: Acceptance Testing\n What is Acceptance Testing\n Contents of Acceptance Testing\n Alpha Testing & Beta Testing\n Brief comparison of four phases of software testing\n96\n\n97\nAcceptance testing is the final level of software testing where the system is \ntested for compliance to its business requirements."}
{"id": "pdf::REVIEW::2378", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 653, "text": "level of software testing where the system is \ntested for compliance to its business requirements. \nIt is performed by the client or the end users with the intent to see if the product \nis fit for delivery.\nIt is carried out after system testing and before the final delivery to the client.\nIt works under the Black Box Testing Method.\n1. What is Acceptance Testing\n\n98\n2.Contents of Acceptance Testing\n\n99\n3. Alpha Testing & Beta Testing\n Alpha and Beta testing are Acceptance Testing types(Customer \nValidation methodologies ) that help in building confidence to launch the \nproduct, and thereby result in the success of the product in the market."}
{"id": "pdf::REVIEW::2379", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 680, "text": "confidence to launch the \nproduct, and thereby result in the success of the product in the market.\n Alpha and Beta Testing phases mainly focus on discovering the bugs \nfrom an already tested product and they give a clear picture of how the \nproduct is used by the real-time users. \n\n100\nAlpha Testing\n Alpha testing is the form of acceptance testing that takes place at \nthe developer’s site.\n It can be carried out by both in-house developers and QAs as well \nas potential end-users as well.\n Alpha testing is not open to the world.\n\n101\nBeta Testing\n Beta Testing (Field Testing) is the form of acceptance testing that takes place \nat the customer’s or the end user’s site."}
{"id": "pdf::REVIEW::2380", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 687, "text": "ting) is the form of acceptance testing that takes place \nat the customer’s or the end user’s site.\n It is performed after alpha testing and in the real-world environment without \nthe presence or control of developers.\n Beta tests or the beta version of the application are normally open to the \nwhole world (or client).\nFor example, recently Microsoft corporation released Windows 10 beta and based \non the feedback from thousands of users they managed to release a stable OS \nversion. In the past, Apple also released OS X beta in public and fixed many minor \nissues and improved the OS based on user feedback.\n\n102\nAlpha Testing & Beta Testing\n\n103\nAlpha Testing & Beta Testing\n\n104"}
{"id": "pdf::REVIEW::2381", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 620, "text": "OS based on user feedback.\n\n102\nAlpha Testing & Beta Testing\n\n103\nAlpha Testing & Beta Testing\n\n104\n4. Brief comparison of software testing phases\nItems Unit Testing Integration Testing System Testing Acceptance Testing\nTest \nobject\nSoftware units, such \nas functions, classes, \ncomponents, modules\nInterfaces between \nmodules, such as parameter \npassing\nThe entire system, \nincluding hardware \nand software\nThe entire system, \nincluding hardware and \nsoftware\nTest basis Detailed software design Software architecture design Software requirements specification Requirements specification, contract, acceptance criteria"}
{"id": "pdf::REVIEW::2382", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 688, "text": "esign Software requirements specification Requirements specification, contract, acceptance criteria\nTester Developer or white box test engineer Developers and testers work together primarily the responsibility of professional testers User-dominant, developer and tester work together\nTest\nmethods\nWhite box test is \nmainly used\nBlack box testing is \nmainly used while white \nbox testing is the secondary\nFully black-box \ntesting Fully black-box testing\nTest data Real data is generally not used Real data is generally not used Use or simulate real business data whenever possible Use or simulate real business data whenever possible\n\n What is Software Maintenance \n Types of Maintenance"}
{"id": "pdf::REVIEW::2383", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 670, "text": "mulate real business data whenever possible\n\n What is Software Maintenance \n Types of Maintenance\n Software Maintenance Life Cycle\n Software Maintainability\n105\nChapter 12: Software Maintenance\n\n106\n1. What is Software maintenance \n“When the transition from development to evolution is \nnot seamless, the process of changing the software \nafter delivery is often called software maintenance”\n IEEE: Maintenance is the process of modifying a software system or component \nafter delivery to correct faults, improve performance or other attributes, or adapt to \na changed environment.\n Maintenance does not normally involve major changes to the system’s architecture"}
{"id": "pdf::REVIEW::2384", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 697, "text": "ged environment.\n Maintenance does not normally involve major changes to the system’s architecture\n Maintenance requires program understanding\n\n107\n2. Types of Maintenance\n\n\n108\n3. Software Maintenance Life Cycle\n Changes are implemented in \nthe software system by \nfollowing a software \nmaintenance process \nIEEE 1219: \nProcess for controlling \nmaintenance changes\nKnown as Software \nMaintenance Life Cycle \n(SMLC).\n\n\n109\n4. Software maintainability\n1. Understanding the Program\n2. Programming for Change\n3. Coding Style\n Maintainability : The ease with which software can be modified\n\n110\nPART 2: Exam Issue\nQuestion Type:\n 1. Explain the following concept in your own words (25 points)"}
{"id": "pdf::REVIEW::2385", "page_id": "pdf::REVIEW", "title": "REVIEW.pdf", "course": "2.5➡️4.0 软件测试 / Software Testing", "path": "2.5➡️4.0 软件测试 / Software Testing/ST PPT 2025/REVIEW.pdf", "section": "REVIEW.pdf", "url": "https://a1npn29y3xu.feishu.cn/wiki/FWS8wYFnoiDT74kplwccITqxn3c", "source_type": "pdf", "n_chars": 548, "text": "PART 2: Exam Issue\nQuestion Type:\n 1. Explain the following concept in your own words (25 points)\n 2. Answer the following question briefly in your own words (25 points)\n 3. Please analyse the following questions . (30 points)\n 1) Please complete the white box test cases for the following program. \n 2) Please design black box test cases according to the following problem \ndescription.\n 4. Application question: about testing a software project. (20 points)\nExam Time: \nMonday , Week 10 , April 28th 8:50-10:50\n有课程冲突的同学记得提前请假，参加考试（必修）！！！"}