系统分析与设计Chap20.ppt

Chapter 20 – Systems Operations and Support * Teaching Notes Note how many maintenance problems relate back to getting the requirements wrong way back in the requirements analysis phase. It is important to do a good analysis if you want a good system. Chapter 20 – Systems Operations and Support * No additional notes. Chapter 20 – Systems Operations and Support * Teaching Notes The tasks shown in this figure, unlike the previous figures, are logically sequential tasks required to solve a single problem (although these tasks can overlap and be consolidated in many projects). Chapter 20 – Systems Operations and Support * Teaching Notes We often discuss personal experiences with debugging old code as a way to help students understand how code degrades over time. Chapter 20 – Systems Operations and Support * Teaching Notes Find a demonstration version of a testing program (frequently available on the Web) and show it to the class. Find a demonstration version of a configuration management program (frequently available on the Web) and show its version control features to the class. Or use a programming environment the students have used in programming classes (such as Visual Studio) and show its versioning features. Chapter 20 – Systems Operations and Support * No additional notes. Chapter 20 – Systems Operations and Support * No additional notes. Chapter 20 – Systems Operations and Support * No additional notes. Chapter 20 – Systems Operations and Support * Teaching Notes In this figure, we are showing logically sequential tasks required to solve a single problem (although these tasks can overlap and be consolidated in many projects). Chapter 20 – Systems Operations and Support * No additional notes. Chapter 20 – Systems Operations and Support * Teaching Notes Control flow knows are the number of times logic paths cross one another. Ideally, it should be zero. Cycle complexity is the number of unique paths through a program. The fewer, the better. Chapter 20 – Systems Op