软件测试与评估：01-Software Engineering Practices.pptVIP

Principles of Software Testing for Testers Instructor Notes Module 1 - Software Engineering Practices Objectives Identify some common software development problems. Identify six software engineering practices for addressing common software development problems. Discuss how a software engineering process provides supporting context for software engineering practices. Module 1 - Content Outline (Agenda) Software development problems Six software engineering practices Supporting software engineering practices with process Symptoms of Software Development Problems User or business needs not met Requirements churn Modules don’t integrate Hard to maintain Late discovery of flaws Poor quality or poor user experience Poor performance under load No coordinated team effort Build-and-release issues Trace Symptoms to Root Causes Module 1 - Content Outline (Agenda) Software development problems Six software engineering practices Supporting software engineering practices with process Six software engineering practices Practice 1: Develop Iteratively Waterfall Development Characteristics Delays confirmation of critical risk resolution Measures progress by assessing work-products that are poor predictors of time-to-completion Delays and aggregates integration and testing Precludes early deployment Frequently results in major unplanned project extensions Iterative Development Produces an Executable Risk Profiles Practice 2: Manage Requirements Manage Requirements - Map of the Territory Manage Requirements - Use-Case Concepts An actor represents a person or another system that interacts with the system. A use case defines a sequence of actions a system performs that yields a result of observable value to an actor. Practice 3: Use Component Architectures Resilient Component-Based Architectures Resilient Meets current and future requirements Improves extensibility Enables reuse Encapsulates system dependencies Component-based Reuse or customize components Select from commercia