软件体系结构ATAM.pptVIP

* Sensitivities and Tradeoffs Example Sensitivity Changing the timing scheme from a harmonic framework to a non-harmonic framework would be easy, but due to implied timing dependencies, there would impact far reaching impacts to other modules.把定时方法从一个精确的框架移植到一个不精确的框架可能很容易，但是因为各个模块对定时的依赖，可能会极大地影响它们的正常工作 Example Tradeoffs In order to achieve the required level of performance in the discrete event generation component, assembly language had to be used thereby reducing the portability of this component.为了达到性能要求，不得不在离散的事件产生组件中使用汇编语言。此组件不再有移植性 * Example Approach Elicitation Scenario: Detect and recover from HW failure of main switch场景：检测主交换机的硬件故障，并恢复 Stimulus: CPU failure Response: 0.999999 availability of switch Architectural Approaches: R S T * Example Approach Elicitation Scenario: Detect and recover from HW failure of main switch场景：检测主交换机的硬件故障，并恢复 Stimulus: CPU failure Response: 0.999999 availability of switch Architectural Approaches: R S T Backup CPU(s) Backup Data Channel Watchdog Heartbeat Failover Rerouting * Example Approach Elicitation Scenario: Detect and recover from HW failure of main switch场景：检测主交换机的硬件故障，并恢复 Stimulus: CPU failure Response: 0.999999 availability of switch Architectural Approaches: R S T Backup CPU(s) X X Backup Data Channel X X X Watchdog X Heartbeat X Failover Rerouting X X * Example Approach Elicitation Analysis: ensures no common mode failure by using different HW and OS通过使用不同的硬件和操作系统确保不会有一样的错误发生 worst-case rollover is accomplished in 3 seconds在最坏的情况下，只要3秒钟内回卷成功就可以 guaranteed to detect failure with 1 second保证错误在1秒钟内被检测到 watchdog is simple and proven reliable看门狗很简单，而且被证明可信赖 * 7a. Brainstorm Scenarios Scenarios are example stimuli used to Represent stakeholders’ interests说明角色关心的内容 Understand quality attribute requirements Scenarios are specific场景是对系统的 anticipated uses of (use case scenarios),预期使用(用例场景)， anticipated changes to (growth scenarios), or预期改变(演化场景)，或者 unanticipated stresses to (exploratory scenarios) 非预期的重压(试探场景)