软件工程第3章设计方案.pptVIP

* NOTES TO THE INSTRUCTOR Review description of modifiable. Bullet 1. Very difficult to maintain compound requirements, particularly when one part of the requirement changes. Example: “The system shall produce an accounting report……AND process biweekly timesheets. “ Bullet 2. Establishing requirements categories enhances modifiability – what are some examples? Financials? Eligibility? Interfaces? CPS? Bullets 3-5. Capability to add, change, and delete requirements from the set is a must. It can be done either manually or via a tool. This will happen a lot – so make sure there is a good way to do this which is not too onerous. Your requirements WILL change – its government – new laws, policies, leadership, practices, technology … * * * * * * 产品缺陷包括：与上游工作产品之间偏差；与标准之间存在的偏差 * * * * * * 产品缺陷包括：与上游工作产品之间偏差；与标准之间存在的偏差 * * * * * * * * * * * * 非常简单而又直接的方式 * 非常简单而又直接的方式 * * * * * * * * * * 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