tailieunhanh - Lecture Business system development - Lecture 25: Automated tools for systems development

In this chapter students will be able to: Identify the tradeoffs when using CASE to support system development activities, describe organizational forces for and against CASE, describe the role of CASE tools in SDLC, list and describe CASE components. | Business System Development CSC581 Lecture 25 Automated Tools for Systems Development 2 Summary of the previous lecture In previous lecture, we : Be familiar with the system installation process. Understand different types of conversion strategies and when to use them. Understand several techniques for managing change. Be familiar with post-installation processes. Outlines We today’s lecture we will: Identify the tradeoffs when using CASE to support system development activities. Describe organizational forces for and against CASE. Describe the role of CASE tools in SDLC. List and describe CASE components. Describe upper CASE, lower CASE, cross-life-cycle CASE, and CASE repository. What is CASE? Computer-aided Software Engineering Software tools that provide automated support for some portions of the system development process Used to support or automate activities throughout the systems development life cycle (SDLC) Increase productivity Improve overall quality of systems 5 . | Business System Development CSC581 Lecture 25 Automated Tools for Systems Development 2 Summary of the previous lecture In previous lecture, we : Be familiar with the system installation process. Understand different types of conversion strategies and when to use them. Understand several techniques for managing change. Be familiar with post-installation processes. Outlines We today’s lecture we will: Identify the tradeoffs when using CASE to support system development activities. Describe organizational forces for and against CASE. Describe the role of CASE tools in SDLC. List and describe CASE components. Describe upper CASE, lower CASE, cross-life-cycle CASE, and CASE repository. What is CASE? Computer-aided Software Engineering Software tools that provide automated support for some portions of the system development process Used to support or automate activities throughout the systems development life cycle (SDLC) Increase productivity Improve overall quality of systems 5 Purpose of CASE is to facilitate a single design philosophy within an organization. Organizational Objectives of CASE Improve quality of systems developed Increase speed of development and design Ease and improve testing process through automated checking Improve integration of development activities via common methodologies Improve quality and completeness of documentation Help standardize the development process Improve project management Simplify program maintenance Promote reusability Improve software portability 7 Obstacles to Widespread CASE Deployment Cost Between $5,000 and $15,000 per year to provide CASE tools to one systems analyst Return on Investment Biggest benefits of CASE come in late stages of SDLC Productivity Bottlenecks Inability of some tools to share information Difficulty in providing tools for all stages of SDLC 8 The Outlook for CASE Functionality is increasing Cost is decreasing Reverse Engineering Tools Automated tools that read program source code as input and .