软件工程第3章案例分析.ppt

* * * * * 产品缺陷包括：与上游工作产品之间偏差；与标准之间存在的偏差 * * * * * * 产品缺陷包括：与上游工作产品之间偏差；与标准之间存在的偏差 * * * * * * * * * 非常简单而又直接的方式 * 非常简单而又直接的方式 * * * * * * * * * * So you all are involved in coding and supporting the SACWIS application – have you ever received a requirement that was not really a requirement? Examples of high level requirements? You say yes/no about whether it is a sufficient requirement? The system needs to report case related information at the worker and manager level. The system needs to track the services a child is receiving. The system shall determine if the foster care child meets the Age/School requirement to be IV-E eligible. The system shall determine if the foster care child does not meet the Period of Ineligibility criteria to be IV-E eligible. * * * * * * * * * * * * * * 在多处包含相同的需求可以使文档更易于阅读，但也会给文档的维护增加困难 * * 1 The RS and the project requirements have entirely different lifespan 2 to help partition the documentation, different audiences, and potential lack of sound design principles * NOTES TO THE INSTRUCTOR Here are some terms to avoid when defining clear requirements. Many of these terms are subjective. They could mean different things to different people. Select a few of the terms and describe why they’re unclear. May--violates standard construct (shall/will). May or may not? And/or. Function 1 and Function 2 vs. Function 1 or Function 2. And-shall do both 1 and 2. Or-shall do 1 or 2. Other terms that we should avoid? This list is just a start. If students ask for more that aren’t on this list, you can also mention the following: flexibly to the extent specified modular to the extent required efficient adequate where possible usually/often/sometimes [Other grammatical constructs to avoid] Passive voice. “The counter is set.” By whom? By what? Comparatives (words ending in “er” and “est”). Better/faster. Best/fastest. Implied certainty. “All” “Every” “Never” Which terms do your customers use most frequently? * NOTES TO TH