INSTRUMENTATION DESIGN FOR AN AMMONIA PLANT: CAD MODEL CAPTURE Ana Carolina Olivera 1, Gustavo E. Vazquez 1, Nélida B. Brignole 1,2 1 Laboratorio de Investigación.

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.
CMMI – Continuous as well as staged model CMMI capability levels – Incomplete, performed, managed, defined, quantitatively managed, optimized Example.
Real-Time Server Oriented Operating System for Embedded Applications David Donari, Leo Ordinez, Rodrigo Santos and J. Orozco Instituto de Investigaciones.
Unified theory of software evolution Reengineering – Business process reengineering and software reengineering BPR model – Business definition, process.
ITEC200 Week01 Introduction to Software Design.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 System models.
Copyright 2002 Prentice-Hall, Inc. Chapter 4 Automated Tools for Systems Development 4.1 Modern Systems Analysis and Design Third Edition.
The Unified Software Development Process - Workflows Ivar Jacobson, Grady Booch, James Rumbaugh Addison Wesley, 1999.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Fall 2007CS 225 Introduction to Software Design Chapter 1.
Software Evolution Managing the processes of software system change
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.
Software Reengineering
Introduction to Software Design Chapter 1. Chapter 1: Introduction to Software Design2 Chapter Objectives To become familiar with the software challenge.
CS 501: Software Engineering
1 Info 1409 Systems Analysis & Design Module Lecture 8 – Modelling tools and techniques HND Year /9 De Montfort University.
© Copyright Eliyahu Brutman Programming Techniques Course.
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.
Spring 2009CS 225 Introduction to Software Design Chapter 1.
Software Engineering Tools and Methods Presented by: Mohammad Enamur Rashid( ) Mohammad Rashim Uddin( ) Masud Ur Rahman( )
Introduction to Software Design Chapter 1. Chapter 1: Introduction to Software Design2 Chapter Objectives To become familiar with the software challenge.
© 2005 by Prentice Hall Appendix 2 Automated Tools for Systems Development Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
Software Reengineering 2003 년 12 월 2 일 최창익, 고광 원.
The Re-engineering and Reuse of Software
Software Re-engineering
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
Appendix 2 Automated Tools for Systems Development © 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 2 Slide 1.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.
Chapter 4 System Models A description of the various models that can be used to specify software systems.
Class Specification Implementation Graph By: Njume Njinimbam Chi-Chang Sun.
System models Abstract descriptions of systems whose requirements are being analysed Abstract descriptions of systems whose requirements are being analysed.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 A Discipline of Software Design.
©Ian Sommerville 2000, Mejia-Alvarez 2009 Slide 1 Software Processes l Coherent sets of activities for specifying, designing, implementing and testing.
1 SYS366 Lecture Visual Modeling and Business Use Case Diagrams.
Introduction to Software Design Chapter 1. Chapter Objectives  To become familiar with the software challenge and the software life cycle  To understand.
HCI in Software Process Material from Authors of Human Computer Interaction Alan Dix, et al.
Odyssey A Reuse Environment based on Domain Models Prepared By: Mahmud Gabareen Eliad Cohen.
Object Management Group (OMG) Specifies open standards for every aspect of distributed computing Multiplatform Model Driven Architecture (MDA)
Chapter 7 System models.
System models l Abstract descriptions of systems whose requirements are being analysed.
Modified by Juan M. Gomez Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
1 Introduction to Software Engineering Lecture 1.
1 Software Development Software Engineering is the study of the techniques and theory that support the development of high-quality software The focus is.
©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.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Copyright 2002 Prentice-Hall, Inc. Chapter 4 Automated Tools for Systems Development 4.1 Modern Systems Analysis and Design.
Chapter 4 Automated Tools for Systems Development Modern Systems Analysis and Design Third Edition 4.1.
CS451 Software Maintenance Yugi Lee STB #555 (816) Note: This lecture was designed based on Stephen Schach’s.
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
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 SYS366 Week 2 - Lecture Visual Modeling and Process.
Appendix 2 Automated Tools for Systems Development
Modern Systems Analysis and Design Third Edition
Software Maintenance.
Business System Development
Designing Software for Ease of Extension and Contraction
Reverse Engineering: A Roadmap
Chapter 4 Automated Tools for Systems Development
Need for the subject.
Introduction To software engineering
UML profiles.
Software Design Lecture : 14.
System Reengineering Restructuring or rewriting part or all of a system without changing its functionality Applicable when some (but not all) subsystems.
SECURITY AS NON-FUNCTIONAL REQUIREMENT IN SOFTWARE ENGINEERING
Introduction Software maintenance:
Modern Systems Analysis and Design Third Edition
For University Use Only
Presentation transcript:

INSTRUMENTATION DESIGN FOR AN AMMONIA PLANT: CAD MODEL CAPTURE Ana Carolina Olivera 1, Gustavo E. Vazquez 1, Nélida B. Brignole 1,2 1 Laboratorio de Investigación y Desarrollo en Computación Científica (LIDeCC) Departamento de Ciencias e Ingeniería de la Computación Universidad Nacional del Sur Av. Alem 1253 – Bahía Blanca Argentina 2 Planta Piloto de Ingeniería Química (PLAPIQUI) Universidad Nacional del Sur - CONICET Complejo CRIBABB – Camino La Carrindanga km. 7 – CC Bahía Blanca Argentina

INSTRUMENTATION DESIGN FOR AN AMMONIA PLANT: CAD MODEL CAPTURE Introduction Instrumentation Design Automatization Decision Support System (DSS) Software Reengineering Concept Stages Requirement Analysis Model Capture Re-design of the DSS Conclusions

Introduction Instrument Design ? ? ?

Instrumentation Design Model Variables Unmeasured Variables Observable Variables Unobservable Variables Measured Variables Redundant Variables Non- Redundant Variables ObservabilityRedundancy

Decision Support System (DSS) Ponzoni I. & others et. al., 2004 Vazquez G. E & others et. al., 2001 Ferraro S. J. & others, 2002

Software Reengineering Forward engineering is the traditional process of moving from high-level abstractions and logical, implementation-independent designs to the physical implementation of the system. Reverse engineering is the process of analyzing a subject system to: Identify the system’s components and their interrelationships and create representations of the system in another form or at a higher level of abstraction

Software Reengineering Software Reengineering is the examination and alteration of a subject system to reconstitute it in a new form and the subsequent implementation of the new form. Forward engineeringReverse engineering Software Reengineering

Software Reengineering - Stages

Requirement Analysis During its application for the analysis of industrial plants, the tool (GM) suffered several anarchical changes that mainly had to do with the addition of new items of equipment and measurements. Those changes had been made without following a specific method and also without documenting the modifications. The problem was partly caused by the programming language whose features made the maintenance difficult. The upkeeping was unrelated to faults, but had mainly to do with the addition of new unforeseen functionalities.

Requirement Analysis The existing software was integrated to the tools for observability analysis, redundancy identification and the other modules that constituted the DSS. Since these modules were all developed in an independent way, the interfaces did not offer the users distinctive advantages when a complex design has to be carried out.

Requirement Analysis Their integration demanded global restructuring.

Requirement Analysis Another important aspect is friendliness, which can be achieved by a graphical interface with facilities to visualize the flowsheet that is being created. This facility should be available at any point during the definition allowing the addition or remotion of an instrument wherever needed.

Model Capture

the original design and architecture of the software was recuperated to create a representation with a higher level of abstraction.

Model Capture In this stage both the study of the existing documentation and the interviews with the developer of the original software are mandatory.

Firstly, all the code was scanned to find weaknesses in the implementation and in the programming language. At this point an intensive analysis on the data structures, functionalities and software architecture is carried out to achieve the DSS original design. The earliest implementation considered the plant topology, but it was not directly shown to the user. Achieving the visibility of the input data was an essential goal of this reengineering. Model Capture

Re-design The re-design may be carried out after having settled the requirements of the DSS and captured the original design. Bearing in mind the advantages of the object-oriented paradigm and making use of the Unified Modelling Language (UML) (Fowler et al., 1998), this activity was successfully performance.

Re-design

The topology of a chemical plant must be straightforwardly available to the engineer. Its representation is natural because it may be captured as a directed graph. Topologically speaking, a chemical plant may be represented by a graph, its nodes being the items of equipment and its edges being the process streams. As to the modules for observability and redundancy, they have been developed and tested carefully. Therefore, they should remain untouched. The only modification was to establish an interface and hide their implementation totally.

ModGen vs. DSS Prototype ModGenDSS Prototype

DSS Prototype – NH3 Plant

DSS Prototype

Conclusions In this work we only discussed the first two stages in the re-engineering procedure. In this paper reverse engineering has been addressed since we have explained how to deal with complex software resulting from a chaotic generation by the constant incorporation of new tools. It was discussed how to re-adapt it by means of the software reengineering approach, so that it fulfils a standard programming and becomes transparent and reusable.