1 / 8

Best Practices for Integrating Legacy Systems into Object-Oriented Software

In this lesson, we explore techniques for effectively dealing with legacy non-object-oriented software within modern object-oriented systems. Key objectives include understanding how to reuse and encapsulate non-OO code, recognizing necessary language features, and developing object-oriented encodings of existing systems. Emphasis is placed on maintaining well-defined interfaces, information hiding, and ensuring that non-OO software is completely encapsulated to facilitate integration. By adopting these strategies, developers can maximize maintainability and extensibility while effectively managing dual documentation for OO and non-OO software.

albany
Télécharger la présentation

Best Practices for Integrating Legacy Systems into Object-Oriented Software

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Lesson 11:Dealing With Legacy Systems Software Engineering II

  2. Lesson Objectives • Understand how to reuse non-OO software • Learn how to encapsulate non-OO code • Recognize required language features • Learn how to develop object-oriented encapsulations of non-OO code • Learn how to manage dual documentation

  3. OO SOFTWARE COMMUNICATES VIA WELL DEFINED INTERFACES

  4. NON-OO SOFTWARE MUST BE COMPLETELY ENCAPSULATED

  5. LANGUAGE INTERFACING RULES • Language interface must maintain OO structure • No data coupling • Well defined interfaces • Information Hiding • Object-Oriented language should be main part of program • Helps keep as many OO features as possible • Maximum benefit of maintainability and extensibility

  6. RULES TO ENCAPSULATE HERITAGE CODE INTO OBJECTS • Look for clean interfaces • If necessary, create “messages” to pass data - no data coupling allowed

  7. MANAGING OO/NON-OO DOCUMENTATION(DOD-STD-2167A EXAMPLE)

  8. REUSING NON-OO SOFTWARE SUMMARY • Non-OO software can be reused within OO systems • Non-OO software must be completely encapsulated • OO notation can be developed for encapsulated heritage software • OO documentation can be developed using the encapsulation

More Related