These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.

Slides:



Advertisements
Similar presentations
© 2005 by Prentice Hall Appendix 2 Automated Tools for Systems Development Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
Advertisements

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.
Computer-Aided Software Engineering
Lecture 12 Reengineering Computer-aided Software Engineering Cleanroom Software Engineering.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
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.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
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.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
CASE Tools CIS 376 Bruce R. Maxim UM-Dearborn. Prerequisites to Software Tool Use Collection of useful tools that help in every step of building a product.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Supplement 02CASE Tools1 Supplement 02 - Case Tools And Franchise Colleges By MANSHA NAWAZ.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Chapter 1 The Systems Development Environment Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
CIS 375 Bruce R. Maxim UM-Dearborn
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 Tools of Software Development l 2 types of tools used by software engineers:
CIS 376 Bruce R. Maxim UM-Dearborn
© 2005 by Prentice Hall Appendix 2 Automated Tools for Systems Development Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Appendix 2 Automated Tools for Systems Development © 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 2 Slide 1.
Chapter 6 System Engineering - Computer-based system - System engineering process - “Business process” engineering - Product engineering (Source: Pressman,
These slides are designed to accompany Web Engineering: A Practitioner’s Approach (The McGraw-Hill Companies, Inc.) by Roger Pressman and David Lowe, copyright.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
ANKITHA CHOWDARY GARAPATI
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
1 Software Engineering: A Practitioner’s Approach, 7/e Chapter 2 Process: A Generic View Software Engineering: A Practitioner’s Approach, 7/e Chapter 2.
CASE (Computer-Aided Software Engineering) Tools Software that is used to support software process activities. Provides software process support by:- –
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 15a: Product Metrics for Software Software Engineering: A Practitioner’s Approach, 6/e Chapter.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission 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.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Chapter 4 Automated Tools for Systems Development Modern Systems Analysis and Design Third Edition 4.1.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
1 Software Engineering: A Practitioner’s Approach, 6/e Chapter 9: Design Engineering Software Engineering: A Practitioner’s Approach, 6/e Chapter.
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.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
1 CASE Computer Aided Software Engineering. 2 What is CASE ? A good workshop for any craftsperson has three primary characteristics 1.A collection of.
1 These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 5/e and are provided with permission by.
CIS 375 Bruce R. Maxim UM-Dearborn
Appendix 2 Automated Tools for Systems Development
Modern Systems Analysis and Design Third Edition
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
Modern Systems Analysis and Design Third Edition
Modern Systems Analysis and Design Third Edition
McCall’s Triangle of Quality
Modern Systems Analysis and Design Third Edition
Presentation transcript:

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, SIM3302 Software Design & Testing Software Engineering: A Practitioner’s Approach, 5/e Chapter 31 Computer-Aided Software Engineering

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, CASE... in its idealized form, CASE combines a set of software development tools that are integrated with a data base to form an environment the tools address each important step in the software engineering process the tools increase insight thereby improving quality; reduce drudgery thereby improving productivity; and enhance control, thereby leading to on-time projects...

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Learning Objectives At the end of this chapter, students should be able to Explain the purpose of CASE tool. Explain the purpose of CASE tool. Explain the CASE building blocks. Explain the CASE building blocks. Explain the taxonomy of CASE tools. Explain the taxonomy of CASE tools. Explain is I-CASE Explain what is I-CASE Explain the benefits and challenges of I-CASE Explain the benefits and challenges of I-CASE List and draw the integration architecture List and draw the integration architecture Explain what is CASE repository Explain what is CASE repository

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Introduction What is CASE? · CASE is the use of IT in SW development activities, techniques and methodology CASE tools are programs that automate or support one or more phases in a SW development life cycle Purpose of CASE tools : · increase the speed of SW development activities increase the SW productivity improve the quality of the SW developed

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, CASE building blocks Found in most application support models CASE environment model CASE Tools Integration framework Portability services Operating system HW platform Environment architecture Important to I- CASE

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, CASE building blocks…cont. portability services = as a bridge between CASE tools + integration framework + environment architecture portability services = as a bridge between CASE tools + integration framework + environment architecture integration framework = collection of specialized programs that enables individual CASE tools to : integration framework = collection of specialized programs that enables individual CASE tools to : communicate with one another communicate with one another create a project data base create a project data base exhibit the same look and feel to the SW engineer exhibit the same look and feel to the SW engineer integrated tools help project team develop, organize and control work products integrated tools help project team develop, organize and control work products

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, CASE building blocks…cont. Integration options are shown below : Integration options are shown below : Individual tool (point solution)  Used to assist in a particular SE activity (ex : analysis modeling)  Does not directly communicate with other tools  Not part of I-CASE environment

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Integration options…cont Data exchange Tool bridges & partnerships  Facilities for data exchange  Produce output in std format that compatible with other tools  Or form a bridge between tools

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Integration options…cont Single source integration  When a single CASE tools vendor integrates a number of different tools  Sells as a package  Addition of tools from other vendors is not easy

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Integration options…cont Integrated Project Support Environment  Each building blocks have been created  Use IPSE standards to build tools that’ll be compatible with IPSE

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Taxonomy of CASE tools CASE tools do not have to be part of an integrated environment to be useful to SW engineers but the impact on product quality will be greater if they are [pressman] CASE tools do not have to be part of an integrated environment to be useful to SW engineers but the impact on product quality will be greater if they are [pressman] CASE tools can be classified by function, role, use in SE process, environment architecture, etc. CASE tools can be classified by function, role, use in SE process, environment architecture, etc.

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, A Taxonomy of CASE Tools business systems planning project management support analysis and design integration &testing re–engineering prototyping/simulation tools CASE Database programming framework

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Integrated CASE (I-CASE) environments Integration = combination and closure Integration = combination and closure Combines a variety of different tools and a spectrum of information  enables closure of communication among tools, between people and across the SW process Combines a variety of different tools and a spectrum of information  enables closure of communication among tools, between people and across the SW process Tools are integrated  SE information is available to each tool that needs it Tools are integrated  SE information is available to each tool that needs it Usage is integrated  common look and feel is provided for all tools Usage is integrated  common look and feel is provided for all tools Development philosophy is integrated  standards SE approach Development philosophy is integrated  standards SE approach

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Benefits of I-CASE Smooth transfer of information from one tool to another and one SE step to the the next Reduction in the effort required to perform umbrella activities Increase in project control Improve staff coordinatio n

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Challenges of I-CASE Consistent representations of SE information Standardized interfaces between tools Homogeneous mechanism for communication between SW engineer and each tool An effective approach that will enable I-CASE to move among various HW platforms and OS.

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, Integration Architecture Architectural model for the integration framework[pressman] User interface layer Interface tool kit Presentation protocol Tools mgt services CASE tool Tools layer Object mgt layer Integration services Configuration mgt services Shared repository layer CASE database Access control functions

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, CASE repository REPOSITORY = a centralized database that contains all diagrams, forms & report definitions, data structure, data definitions, process flows & logic, and definitions of other organizational and system components REPOSITORY = a centralized database that contains all diagrams, forms & report definitions, data structure, data definitions, process flows & logic, and definitions of other organizational and system components it provides a set of mechanisms and data structures that achieve data/tool and data/data integration it provides a set of mechanisms and data structures that achieve data/tool and data/data integration

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, CASE repository functions Data integrity Data/tool integration Information sharing Data/data integration Methodology enforcement Document standardization CASE repository Function CASE repository Function

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, CASE repository Function…cont Data Integrity include functions to validate entries to the repository ensure consistency among related objects automatically perform ‘cascading’ modifications when a change to one object demands some change to objects that are related to it

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, CASE repository Function…cont Information sharing provides a mechanism for sharing information among multiple developers and between multiple tools, managers and controls multi-user access to data and locks/unlocks objects so that changes are not overlaid on one another.

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, CASE repository Function…cont Data-tool integration establish a data models that can be accessed by all tools in the I-Case environment, control access to that data, and perform appropriate configuration management functions.

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, CASE repository Function…cont Data Integration the database management system relates data objects so that other function can be achieved.

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, CASE repository Function…cont Methodology enforcement the ERD model of data stored in the repository can imply a specific paradigm for SE at a minimum, the relationships and objects define a set of steps that must be conducted to build the contents of the repository.

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, CASE repository Function…cont Document standardization the definition of objects in the database leads directly to a standard approach for the creation of SE documents.

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, References Pressman, R. (2003). Software Engineering: A Practitioner's Approach. 6th & 5th edition. New York: McGraw-Hill. Pressman, R. (2003). Software Engineering: A Practitioner's Approach. 6th & 5th edition. New York: McGraw-Hill. Somerville I. (2001). Software Engineering. 6th edition. Addison Wesley Somerville I. (2001). Software Engineering. 6th edition. Addison Wesley ~The End ~