Presentation is loading. Please wait.

Presentation is loading. Please wait.

Legacy Systems - Page P3-L11-1 MEF-TRANSITION-P3-L11-1 Dr. M.E. Fayad Lesson 11: Dealing With Legacy Systems SoftwareEngineeringII.

Similar presentations


Presentation on theme: "Legacy Systems - Page P3-L11-1 MEF-TRANSITION-P3-L11-1 Dr. M.E. Fayad Lesson 11: Dealing With Legacy Systems SoftwareEngineeringII."— Presentation transcript:

1 Legacy Systems - Page P3-L11-1 MEF-TRANSITION-P3-L11-1 Dr. M.E. Fayad Lesson 11: Dealing With Legacy Systems SoftwareEngineeringII

2 Legacy Systems - Page P3-L11-2 MEF-TRANSITION-P3-L11-2 Dr. M.E. Fayad Lesson Objectives oUnderstand how to reuse non-OO software oLearn how to encapsulate non-OO code oRecognize required language features oLearn how to develop object-oriented encapsulations of non-OO code oLearn how to manage dual documentation

3 Legacy Systems - Page P3-L11-3 MEF-TRANSITION-P3-L11-3 Dr. M.E. Fayad OO S OFTWARE C OMMUNICATES V IA W ELL D EFINED I NTERFACES

4 Legacy Systems - Page P3-L11-4 MEF-TRANSITION-P3-L11-4 Dr. M.E. Fayad N ON -OO S OFTWARE M UST B E C OMPLETELY E NCAPSULATED

5 Legacy Systems - Page P3-L11-5 MEF-TRANSITION-P3-L11-5 Dr. M.E. Fayad L ANGUAGE I NTERFACING R ULES 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 Legacy Systems - Page P3-L11-6 MEF-TRANSITION-P3-L11-6 Dr. M.E. Fayad R ULES T O E NCAPSULATE H ERITAGE C ODE I NTO O BJECTS Look for clean interfaces If necessary, create “messages” to pass data - no data coupling allowed Look for clean interfaces If necessary, create “messages” to pass data - no data coupling allowed

7 Legacy Systems - Page P3-L11-7 MEF-TRANSITION-P3-L11-7 Dr. M.E. Fayad M ANAGING OO/N ON -OO D OCUMENTATION (D O D-STD-2167A E XAMPLE )

8 Legacy Systems - Page P3-L11-8 MEF-TRANSITION-P3-L11-8 Dr. M.E. Fayad R EUSING N ON -OO S OFTWARE S UMMARY 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


Download ppt "Legacy Systems - Page P3-L11-1 MEF-TRANSITION-P3-L11-1 Dr. M.E. Fayad Lesson 11: Dealing With Legacy Systems SoftwareEngineeringII."

Similar presentations


Ads by Google