乔伊·F·乔治-现代系统分析与设计（第6版）hoffer_msad6e_ch14.pptVIP

* * * * * ? 2011 Pearson Education, Inc. Publishing as Prentice Hall Role of CASE and Automated Development Tools in Maintenance Traditional systems development Emphasis is on coding and testing. Changes are implemented by coding and testing first. Documentation is done after maintenance is performed. Keeping documentation current is often neglected due to time-consuming nature of task. * Chapter 14 ? 2011 Pearson Education, Inc. Publishing as Prentice Hall Role of CASE and Automated Development Tools in Maintenance (Cont.) Development with CASE Emphasis is on design documents. Changes are implemented in design documents. Code is regenerated using code generators. Documentation is updated during maintenance. * Chapter 14 ? 2011 Pearson Education, Inc. Publishing as Prentice Hall Role of CASE and Automated Development Tools in Maintenance (Cont.) Reverse engineering: automated tools that read program source code as input and create graphical and textual representations of design-level information such as program control structures, data structures, logical flow, and data flow * Chapter 14 ? 2011 Pearson Education, Inc. Publishing as Prentice Hall Role of CASE and Automated Development Tools in Maintenance (Cont.) Reengineering: automated tools that read program source code as input; perform an analysis of the program’s data and logic; and then automatically, or interactively with a systems analyst, alter an existing system in an effort to improve its quality or performance * Chapter 14 ? 2011 Pearson Education, Inc. Publishing as Prentice Hall Role of CASE and Automated Development Tools in Maintenance (Cont.) * Chapter 14 Figure 14-10 Visual Studio .NET engineer applications into Visio UML diagrams ? 2011 Pearson Education, Inc. Publishing as Prentice Hall * Chapter 14 Website Maintenance Special considerations: 24 X 7 X 365 Nature of continuous availability makes maintenance challenging. Pages under maintenance can be locked. Consider using date and time stamps to