ANKITHA CHOWDARY GARAPATI

Slides:



Advertisements
Similar presentations
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
Advertisements

© 2005 by Prentice Hall Appendix 2 Automated Tools for Systems Development Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
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.
Object-Oriented Analysis and Design
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.
1 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall James A. Senn’s Information Technology, 3 rd Edition Chapter 11 Creating Enterprise.
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.
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.
Supplement 02CASE Tools1 Supplement 02 - Case Tools And Franchise Colleges By MANSHA NAWAZ.
Software Engineering CSE470: Systems Engineering 35 Computer System Engineering Computer System Engineering is a problem-solving activity. Itemize desired.
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
Software Configuration Management
Database Administration Chapter 16. Need for Databases  Data is used by different people, in different departments, for different reasons  Interpretation.
© 2005 by Prentice Hall Appendix 2 Automated Tools for Systems Development Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
Architecture, Implementation, and Testing Architecture and Implementation Prescriptive architecture vs. descriptive architecture Prescriptive architecture:
Appendix 2 Automated Tools for Systems Development © 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 2 Slide 1.
Chapter 2 The process Process, Methods, and Tools
Engineering, Operations & Technology | Information TechnologyAPEX | 1 Copyright © 2009 Boeing. All rights reserved. Architecture Concept UG D- DOC UG D-
Thirteenth Lecture Hour 8:30 – 9:20 am, Sunday, September 16 Software Management Disciplines Process Automation (from Part III, Chapter 12 of Royce’ book)
Software System Engineering: A tutorial
Information System Design IT60105 Lecture 21 Staff Organization, Risk Management and Software Configuration Management.
Introduction to MDA (Model Driven Architecture) CYT.
Capability Maturity Models Software Engineering Institute (supported by DoD) The problems of software development are mainly caused by poor process management.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
1 10/14/2015ã 2007, Spencer Rugaber The Waterfall Process Software plans and requirements Validation System feasibility Validation Product design Verification.
Enterprise Architecture Enterprise Architecture = a framework or ‘blueprint’ for how the organization achieves the business objectives at hand and in future.
Content The system development life cycle
KS3 Phase4 Client Server Monitoring System October 1, 2008 by Stephen, Seema, Kam, Shpetim.
I am an IT Software Engineer. Hello !!. L1 : INTRODUCTION  Goals of Software Engineering:  What IT Demands Today ?  IT Products Design Methodologies.
Enterprise Systems Architectures EGN 5621 Enterprise Systems Collaboration (Professional MSEM) Fall, 2012.
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 05. Review Software design methods Design Paradigms Typical Design Trade-offs.
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
Database Administration
PRJ566 Project Planning & Management Software Architecture.
UNIT-1 SOFTWARE PRODUCT AND PROCESS: Introduction – S/W Engineering paradigm – Verification – Validation – Life cycle models – System engineering –
CASE (Computer-Aided Software Engineering) Tools Software that is used to support software process activities. Provides software process support by:- –
CISB113 Fundamentals of Information Systems IS Development.
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.
Chapter 4 Automated Tools for Systems Development Modern Systems Analysis and Design Third Edition 4.1.
Process Asad Ur Rehman Chief Technology Officer Feditec Enterprise.
Software Engineering Introduction.
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.
Software Production ( ) Lecture 3: Dr. Samer Odeh Hanna (PhD) office: 318.
T EST T OOLS U NIT VI This unit contains the overview of the test tools. Also prerequisites for applying these tools, tools selection and implementation.
CASE Tools and their Effect on Software Quality
1 CASE Computer Aided Software Engineering. 2 What is CASE ? A good workshop for any craftsperson has three primary characteristics 1.A collection of.
CIS 375 Bruce R. Maxim UM-Dearborn
Software Engineering – A layered Technology
Appendix 2 Automated Tools for Systems Development
Software Project Configuration Management
Definition CASE tools are software systems that are intended to provide automated support for routine activities in the software process such as editing.
Modern Systems Analysis and Design Third Edition
CS4311 Spring 2011 Process Improvement Dr
Modern Systems Analysis and Design Third Edition
The Systems Engineering Context
IEEE Std 1074: Standard for Software Lifecycle
Business System Development
Tools of Software Development
Chapter 1 (pages 4-9); Overview of SDLC
Modern Systems Analysis and Design Third Edition
Modern Systems Analysis and Design Third Edition
Software Engineering I
Modern Systems Analysis and Design Third Edition
Presentation transcript:

ANKITHA CHOWDARY GARAPATI CASE FOR SOFTWARE PROCESS AUTOMATION TAXONOMY BY ANKITHA CHOWDARY GARAPATI

WHAT IS CASE ? Computer Aided Software Engineering is a technique to help with one or more phases of the software development cycle which involves analysis, design, implementation and maintenance of software . CASE provides the engineer with the ability to automate the manual activities

Integration Framework Environment Architecture CASE BUILDING BLOCKS Integration Framework Portability Services CASE Tools Operating System Hardware Environment Architecture

TAXONOMY OF CASE Tools that are interactive in nature [CASE tools] and those that are not [Development tools]. Tools that support activities early in the life cycle of a soft ware project [front-end CASE tools] and those that are used later in the life cycle [back-end CASE tools]. Tools that are specific to a particular life-cycle step or domain [vertical CASE tools] and those that are common across a number of life-cycle steps or domains [horizontal CASE tools].

Classification by function Their role as instruments for managers or technical people Their use in various steps of the software development process The environment architecture i.e. hardware and software that supports the CASE tools Origin Cost

Information Engineering Tools Process Modeling And Management Tools Project Planning Tools Risk Analysis Tools: Project Management Tools

Requirements Tracing Tools Metrics And Management Tools Documentation Tools Quality Assurance Tools Database Management Tools Software Configuration Management Tools

Analysis and Design tools PRO/SIM tools Interface Design and development Tools Programming Tools Integration and Testing tools Reengineering Tools

CASE ENVIRONMENT A CASE environment is a collection of CASE tools and other components together with an integration approach that supports most or all of the interactions that occur among the environment components, and between the users of the environment and the environment itself. The CASE tools provide an environment that will help automate the software process.

INTEGRATED ENVIRONMENT I-CASE INTEGRATED ENVIRONMENT Benefits can be derived from individual CASE tools that address specific software engineering activities, but the real power of CASE can be achieved only through integration. Integration demands standardized interfaces between tools, consistent representation of information, homogeneous mechanism for communication, and an effective approach to enable the I-CASE to move along various hardware platforms and operating systems.

ELEMENTS OF I-CASE Integration Framework Foundation blocks CASE Tools Portability services Integration Framework CASE Tools ELEMENTS OF I-CASE

Architectural Model for the integration Framework USER INTERFACE LAYER Interface Toolkit and Presentation Protocol Tools Management Services CASE TOOL TOOLS LAYER OBJECT MANAGEMENT LAYER Integration and configuration management services SHARED REPOSITORY LAYER CASE Database and access control functions

The integrated CASE environment ( I-CASE) enables Smooth transfer of information from one tool to another and from one software engineering step to the next. Allow direct access to any tool contained in the environment. A change to one item of information to be tracked to other related information items.

Collect both management and technical metrics to improve the process and the product. Reduction in the effort required to perform umbrella activities Increase in project control through better planning, monitoring and communication. Improved coordination and support effective communication.

CASE REPOSITORY Two types of mechanisms have been used in CASE software to store design information: A dictionary, which contains names and descriptions of data items, processes, etc. A repository, which contains this dictionary information and a complete coded representation of plans, models and designs, with tools for cross-checking, correlation analysis and validation.

Role of Repository in I-CASE The repository is the heart of CASE system It performs the following functions : Data integrity Information Sharing Data-Tool Integration Data-Date Integration Document standardization