Re- engineeniering.

Slides:



Advertisements
Similar presentations
Software Re-engineering
Advertisements

Software Re-engineering
Chapter 27 Software Change.
CIS 376 Bruce R. Maxim UM-Dearborn
Chapter 11 Software Evolution
SWE 316: Software Design and Architecture Objectives Lecture # 23 Software Reengineering SWE 316: Software Design and Architecture  To describe the activities.
CMMI – Continuous as well as staged model CMMI capability levels – Incomplete, performed, managed, defined, quantitatively managed, optimized Example.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Reverse Engineering When is it the most cost effective? Raymond Utz.
1 / 24 CS 425/625 Software Engineering Software Evolution Based on Chapter 21 of the textbook [SE-8] Ian Sommerville, Software Engineering, 8 th Ed., Addison-Wesley,
Lesson-12 Information System Development-2
Reverse Engineering: Legacy Systems Alexander Endert.
Software Evolution Managing the processes of software system change
Dr Kettani, Spring 2002 Software Engineering IIFrom Sommerville, 6th edition Software change l Managing the processes of software system change.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 21 Slide 1 Software evolution.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 21 Slide 1 Software evolution.
Software evolution.
Software evolution.
Driss Kettani Sommerville, 6th edition Software Engineering II Software re-engineering l Reorganising and modifying existing software systems to make them.
Software Reengineering 2003 년 12 월 2 일 최창익, 고광 원.
Software Re-engineering
Chapter 9 – Software Evolution and Maintenance
SEG Software Maintenance1 Software Maintenance “The modification of a software product after delivery to correct faults, to improve performance or.
Software evolution. Objectives l To explain why change is inevitable if software systems are to remain useful l To discuss software maintenance and maintenance.
CS 425/625 Software Engineering Legacy Systems
The Program Development Cycle
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 27Slide 1 Software change l Managing the processes of software system change.
 CS 5380 Software Engineering Chapter 9 Software Evolution.
Program Development Cycle Modern software developers base many of their techniques on traditional approaches to mathematical problem solving. One such.
CS Data Structures I Chapter 2 Principles of Programming & Software Engineering.
Lecture 14 Maintaining the System and Managing Software Change SFDV Principles of Information Systems.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 28Slide 1 CO7206 System Reengineering 4.2 Software Reengineering Most slides are Slides.
Chapter 5: Software Re-Engineering Omar Meqdadi SE 3860 Lecture 5 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
HNDIT23082 Lecture 06:Software Maintenance. Reasons for changes Errors in the existing system Changes in requirements Technological advances Legislation.
Chapter 2: Software Maintenance Omar Meqdadi SE 3860 Lecture 2 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
1 Software Maintenance The process of changing the system after it has been delivered and in operation Software change is inevitable –New requirements.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 21 Slide 1 Software evolution 2.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 21 Slide 1 Software evolution.
Chapter 9 – Software Evolution 1Chapter 9 Software evolution.
Design and implementation Chapter 7 – Lecture 1. Design and implementation Software design and implementation is the stage in the software engineering.
Reverse Engineering Dept. of I&CT, MIT, Manipal. Aspects To Be Covered Introduction to reverse engineering. Comparison between reverse and forward engineering.
Software change Software change is inevitable –New requirements emerge when the software is used –The business environment changes –Errors must be repaired.
Friday, 23 August 2013 Session Work out Presented By: Abhijit Pal.
© SERG Reverse Engineering (Software Maintenance & Reengineering) Software Maintenance Managing the processes of system change.
CS223: Software Engineering Lecture 33: Software Maintenance.
CS223: Software Engineering Lecture 34: Software Maintenance.
Laurea Triennale in Informatica – Corso di Ingegneria del Software I – A.A. 2006/2007 Andrea Polini XVI. Software Evolution.
Tutorial 4 IT323.  Q1. As a software project manager in a company that specializes in the development of software for the offshore oil industry, you.
Environment Assessment
Chapter 18 Maintaining Information Systems
1.Introduction to Software Engineering
Introduction to Software Evolution and Maintenance
Software Maintenance.
Chapter 9 – Software Evolution
Introduction to Computers
Software Maintenance PPT By :Dr. R. Mall.
Chapter 9 – Software Evolution
CS 425/625 Software Engineering Software Evolution
CSSSPEC6 SOFTWARE DEVELOPMENT WITH QUALITY ASSURANCE
Chapter 9 – Software Evolution and Maintenance
Chapter 9 Software Maintenance
IS301 – Software Engineering V:
Software Re-Engineering
Chapter 27 Software Change.
Chapter 8 Software Evolution.
Lecture 06:Software Maintenance
Software Engineering Practices
Introduction Software maintenance:
Software Re-engineering and Reverse Engineering
Presentation transcript:

Re- engineeniering

Forward engineering: Re-engineering: Starts with system specifications and evolves the design & implementation of a new system Re-engineering: Starts with an existing system & the development process for the replacement is based on understanding and transforming the original system.

Re-engineering Legacy program Structured modularized version of the program

Activities performed during Re-engineering Source code translation: Old language  Modern version language Reverse engineering: Documentation. (After analyzing the program) Program structure improvement: Control structure analyzed and modified to make it easier to read and understand

Program modularization: Related parts of the program are grouped together and where appropriate, redundancy is removed. In some cases, this stage may involve architectural transformation where a centralised system extended for a single computer is modified to run on a distributed platform. Data re-engineering: The data processed by the program is changed to reflect program changes

Re-engineering Process Program Documentation Original program Reverse engineering Program Modularization Source code translation Modularized Program Original data Program structure improvement Data Re-engineering Structured Program Re-engineered Data

Factors affects Re-engineering cost The quality of the software The tool support available The extent of data conversion required The availability of expert staff

Other Approaches for software development Personal Software Process (PSP) Team Software Process (TSP)