李彤《软件工程》教学课件ch4.pptVIP

Testing phases Requirements R equir ements specifica tion S ystem specifica tion S ystem design Detailed design Module and unit code and test Sub-system integ r a tion test plan S ystem Integ r a tion test plan Acceptance test plan Service Acceptance test S ystem integ r a tion test Sub-system integ r a tion test 4.3.4 Software evolution Software is inherently flexible and can change. As requirements change through changing business circumstances, the software that supports the business must also evolve and change. Although there has been a demarcation (划分) between development and evolution (maintenance) this is increasingly irrelevant as fewer and fewer systems are completely new. System evolution 4.4 The Rational Unified Process A modern process model derived from the work on the UML and associated process. Normally described from 3 perspectives A dynamic perspective that shows phases over time; A static perspective that shows process activities; A practive perspective that suggests good practice. RUP phase model Establish the business case for the system. Develop an understanding of the problem domain and the system architecture. System design, programming and testing. Deploy the system in its operating environment. RUP good practice Develop software iteratively Manage requirements Use component-based architectures Visually model software Verify software quality Control changes to software 4.5 Computer-aided software engineering Computer-aided software engineering (CASE) is software to support software development and evolution processes. Activity automation Graphical editors for system model development; Data dictionary to manage design entities; Graphical UI builder for user interface construction; Debuggers to support program fault finding; Automated translators to generate new versions of a program. CASE technology CASE technology has led to significant improvements in the software process. However, these are not the order of magnitude(重大) improvements