1. Business System Development
CSC581

2. Lecture 25 Automated Tools for Systems Development

3. 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.

4. 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.

5. 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

6. Purpose of CASE is to facilitate a single design philosophy within an organization.

7. 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

8. 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

9. The Outlook for CASE Functionality is increasing Cost is decreasing
Reverse Engineering Tools
Automated tools that read program source code as input and create graphical and textual representations of program design-level information
Reengineering Tools
Automated software that reads program source code, analyzes it and automatically or interactively alters an existing system to improve quality and/or performance

11. Impact of CASE on Individuals
Systems analysts: automate routine tasks
Programmers: piece together objects created by code generators
Users: increased participation via upper CASE tools
Top managers: CASE-based planning assists with strategy development
Functional managers: CASE helps reengineer business processes
IS managers: CASE gives better control over IS development processes

12. Forces For and Against CASE Adoption
Driving forces:
Short development time
Improved productivity
Improved system quality
Improved worker skills
Improved portability
Improved management
Resisting forces:
High purchase cost
High training cost
Low organizational confidence
Lack of standards
Perceived threat to job security

13. Categories of CASE
Upper CASE: support information planning, project identification and selection, project initiation and planning, analysis and design
Lower CASE: support the implementation and maintenance phases of the systems development life cycle
Cross life-cycle CASE: support activities that occur across multiple phases of the systems development life cycle

14. Types of CASE Tools Diagramming tools
Computer display and report generators
Analysis tools used to check for incomplete, inconsistent or incorrect specifications
A central repository
Documentation generators
Code generators

16. CASE versus Traditional Systems Development
Traditional approach does not offer support for integration of specification documents.
Often, documentation is done after coding is completed in traditional systems development.
Traditional approach often leads to out- of-date documentation.

17. CASE versus Traditional Systems Development (cont.)
Emphasis on coding and testing
Paper-based specifications
Manual coding of programs
Manual documenting
Intensive software testing
Maintain code and documentation
CASE-Based Systems Development:
Emphasis on analysis and design
Rapid interactive prototyping
Automated code generation
Automated documentation generation
Automated design checking
Maintain design specifications

18. CASE Diagramming Tools
Enable representation of a system and components visually
Effective for representing process flows, data structures and program structures
Several types of diagrams, including:
Data Flow Diagrams (DFD)
Class Diagrams
Entity-Relationship Diagrams

20. CASE Form and Report Generator Tools
CASE tools that support the creation of system forms and reports in order to prototype how systems will look and feel to users
Two Purposes:
Create, modify, and test prototypes of computer display forms and reports
Identify data items to display or collect for each form or report

22. CASE Analysis Tools
Enable automatic checking for incomplete, inconsistent, or incorrect specifications in diagrams, forms and reports.
Types of analyses vary depending on the organization’s development methodology and features of CASE environment.

23. The CASE repository contains complete information needed to create, modify and evolve a software system from project initiation and planning to code generation and maintenance.

24. Information Repository: Combines information about an organization’s business information and its application portfolio
Data Dictionary: Contains data definitions for all organizational applications

25. Summary of today’s lecture
In this lecture we talked about :
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.

26. Overview of the next lecture
In next lecture, we will:
Describe the organizational roles involved in information systems development.
Discuss analytical skills required for success as a systems analyst.
Discuss technical skills required for success as a systems analyst.

27. The End