Chapter 4 Automated Tools for Systems Development Modern Systems Analysis and Design Third Edition 4.1.

Slides:



Advertisements
Similar presentations
Ch 3 System Development Environment
Advertisements

© 2005 by Prentice Hall Appendix 2 Automated Tools for Systems Development Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix.
Case Tools Trisha Cummings. Our Definition of CASE  CASE is the use of computer-based support in the software development process.  A CASE tool is a.
Chapter 7 CASE Tools and Joint and Rapid Application Development.
11.1 Lecture 11 CASE tools IMS Systems Design and Implementation.
Copyright 2002 Prentice-Hall, Inc. Chapter 4 Automated Tools for Systems Development 4.1 Modern Systems Analysis and Design Third Edition.
© Prentice Hall CHAPTER 9 Application Development by Information Systems Professionals.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
ISMT221 Information Systems Analysis and Design Project Management Tools Lab 1 Tony Tam.
Requirements Analysis 5. 1 CASE b505.ppt © Copyright De Montfort University 2000 All Rights Reserved INFO2005 Requirements Analysis CASE Computer.
Copyright 2002 Prentice-Hall, Inc. Chapter 4 Automated Tools for Systems Development 4.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Systems Analysis & Design Sixth Edition Systems Analysis & Design Sixth Edition Toolkit Part 2.
IMS Information Systems Development Practices
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 15 Finalizing.
9.1 Quality and productivity issues in information systems development: CASE tools and prototyping IMS Information Systems Development Practices.
Fundamentals of Information Systems, Second Edition
CHAPTER 3: Managing the Information Systems Project
Supplement 02CASE Tools1 Supplement 02 - Case Tools And Franchise Colleges By MANSHA NAWAZ.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 Tools of Software Development l 2 types of tools used by software engineers:
Chapter 1 The Systems Development Environment
© 2005 by Prentice Hall Appendix 2 Automated Tools for Systems Development Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
Chapter 1 The Systems Development Environment
Chapter 1 Database Systems. Good decisions require good information derived from raw facts Data is managed most efficiently when stored in a database.
The Systems Development Environment. Learning Objectives Define information systems analysis and design. Describe the different types of information systems.
Appendix 2 Automated Tools for Systems Development © 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 2 Slide 1.
Systems Analysis – Analyzing Requirements.  Analyzing requirement stage identifies user information needs and new systems requirements  IS dev team.
Chapter 1 The Systems Development Environment
Describing Methodologies PART II Rapid Application Development*
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design.
Copyright 2002 Prentice-Hall, Inc. Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
The Systems Development Methodologies. Objectives  Describe the information Systems Development Life Cycle (SDLC)  Explain prototyping  Explain Rapid.
Architecture for a Database System
McGraw-Hill/Irwin Copyright © 2006 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 7 CASE Tools and Joint and Rapid Application Development.
Approaches to Systems Development Week 2 CMIS570.
1 Chapter 13 Understanding Computers, 11 th Edition 13 Program Development and Programming Languages TODAY AND TOMORROW 11 th Edition CHAPTER.
CASE Form and Report Generator Tools Done by Hessa AlSubaie Aisha AlOmani.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix B Rapid Application.
1 Systems Analysis and Design in a Changing World, Thursday, January 18, 2007.
Content The system development life cycle
Systems Analysis and Design in a Changing World, Fourth Edition
ANKITHA CHOWDARY GARAPATI
Chapter 6 CASE Tools Software Engineering Chapter 6-- CASE TOOLS
CASE (Computer-Aided Software Engineering) Tools Software that is used to support software process activities. Provides software process support by:- –
Copyright 2002 Prentice-Hall, Inc. Chapter 4 Automated Tools for Systems Development 4.1 Modern Systems Analysis and Design.
Software Engineering Chapter: Computer Aided Software Engineering 1 Chapter : Computer Aided Software Engineering.
Toolkit 2.
The Systems Development Environment Systems Analysis and Design II.
NURHALIMA 1. Identify the trade-offs when using CASE Describe organizational forces for and against adoption of CASE tools Describe the role of CASE tools.
CASE Tools and their Effect on Software Quality
CASE (Computer-Aided Software Engineering) Tools
1 CASE Computer Aided Software Engineering. 2 What is CASE ? A good workshop for any craftsperson has three primary characteristics 1.A collection of.
Appendix 2 Automated Tools for Systems Development
Modern Systems Analysis and Design Third Edition
CASE Tools and Joint and Rapid Application Development
Computer Aided Software Engineering (CASE)
Modern Systems Analysis and Design Third Edition
Business System Development
Tools of Software Development
Chapter 4 Automated Tools for Systems Development
Chapter 1 Database Systems
Modern Systems Analysis and Design Third Edition
ابزارهاي خودكار توليد سيستم‌هاي نرم‌افزاري (CASE Systems)
Modern Systems Analysis and Design Third Edition
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 Tools of Software Development l 2 types of tools used by software engineers:
Modern Systems Analysis and Design Third Edition
Presentation transcript:

Chapter 4 Automated Tools for Systems Development Modern Systems Analysis and Design Third Edition 4.1

Introduction Lack of consistency in technique and methodology made development of systems difficult – error-ridden, over budget, late Goal – To develop common techniques, standard methodologies, automated tools Computer-Aided Software Engineering (CASE) Automated software tools used by systems analysts to develop information systems Used to support or automate activities throughout the systems development life cycle (SDLC) Increase productivity Improve overall quality of systems 4.2

The Use of CASE in Organizations Purpose of CASE is to facilitate a single design philosophy within an organization with many projects, systems, people. CASE tools runs on variety of mini and mainframe systems. Objectives of CASE Improve quality of systems developed Increase speed of development and design Ease and improve testing process through automated checking Improve quality and completeness of documentation Help standardize the development process Improve project management Simplify program maintenance Promote reusability of modules and documentation 4.3

CASE and System Quality Majority of organizations adopt CASE to improve speed and quality of systems development projects Several factors that inhibit widespread 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 – testing, implementation and maintenance Long duration for early stages – planning, analysis, design – leads to frustration by managers and users Productivity Bottlenecks Inability of some tools to share information Difficulty in providing tools for all stages of SDLC 4.4

The Outlook for CASE Functionality is increasing Cost is decreasing Expose CASE technology earlier in education and career 4.5

Components of CASE Upper CASE CASE tools designed to support the information planning and the project identification and selection, project initiation and planning, analysis and design phases of the systems development life cycle Lower CASE CASE tools designed to support the implementation and maintenance phases of the systems development life cycle Cross life-cycle CASE CASE tools designed to support activities that occur across multiple phases of the systems development life cycle Most CASE tools utilize a repository to store all diagrams, forms, models and report definitions 4.6

Components of CASE 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 CASE tools also provides Security Features Version Control Import/Export Backup and Recovery 4.7

CASE versus Traditional Systems Development Traditional Systems Development 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 Automated code generation Automated documentation generation Automated design checking Maintain design specifications 4.8

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 Data Flow Diagrams (DFD) Functional Hierarchy Diagrams Entity-Relationship Diagrams 4.9

Data Flow Diagrams (DFD)

Entity-Relationship Diagrams

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 which data items to display or collect for each form or report 4.12 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

CASE Repository Integrated CASE (I-CASE) Integration of various CASE tools and their data I-CASE tools use common terminology, notations and methods for system development across all tools All I-CASE tools have a common user interface Automated systems development environment that provides numerous tools to create diagrams, forms and reports Provides analysis, reporting and code generation facilities Seamlessly shares and integrates data across and between tools Repository is centralized database containing all diagrams, forms and report definitions, data structure, data definitions, process flow and logic Holds complete information needed to create, modify and evolve a software system from project initiation and planning to code generation and maintenance 4.13

CASE Repository Two Primary Segments Information Repository Data Dictionary Information Repository Combines information about an organization’s business information and its application portfolio Provides automated tools to manage and control access to repository Business Information Data stored in corporate databases Application Portfolio Application programs used to manage business 4.14

CASE Repository Data Dictionary Computer software tool used to manage and control access to the information repository Contains all data definitions for all organizational applications Cross referencing Enables one description of a data item to be stored and accessed by all individuals Single definition for a data item is established and used Entries have a standard definition Element name and alias Textual description of the element List of related elements Element type and format Range of acceptable values Other information unique to the proper processing of this element 4.15

CASE Repository CASE Repository and the SDLC During project initiation and planning phase, all information related to the problem being solved is stored in the repository Problem domain, project resources, history and organizational context During analysis and design phases, store graphical diagrams and prototype forms and reports Data stored in repository are used for basis to generate code and documentation Additional Advantages Assistance with project management tasks Aids in software reusability The ability to design software modules in a manner so that they can be used again and again in different systems without significant modification 4.16

CASE Documentation Generator Tools Enable the easy production of both technical and user documentation Allow creation of master templates used to verify that documentation conforms to all stages of SDLC 4.17 CASE Code Generation Tools Enable the automatic generation of program and database definition code directly from the design documents, diagrams, forms and reports stored in the repository

Visual and Emerging Development Tools Object-Oriented Development Tools Object A chunk of program and data that is built to perform common functions within a system Easily reused Encapsulation Process of grouping data and instructions together Development environment includes pre-defined objects and facilitates reuse of code 4.18

Visual and Emerging Development Tools Visual Development Tools Enable developers to quickly create user interfaces Popular tools include: Microsoft Visual Studio Delphi Powerbuilder ColdFusion 4.19