GeekArticles 
Testing Software Development
Testing Software DevelopmentImplementing Reusable Object-Oriented Components
Object-oriented (OO) classes are generally not reusable because they are not meaningful in isolation; most classes only have meaning as members of cooperating suites of classes (e.g., design patterns). These suites usually arise in designs, but rarely exist as encapsulated entities in OO implementations. In this paper the authors present a method for directly mapping cooperating suites of classes into encapsulated C++ implementations. Their method is an improvement over the VanHilst and Notkin approach for implementing collaboration-based designs and constitutes a step towards more reusable (object-oriented) components. Author(s) : Yannis Smaragdakis and Don Batory
Sponsored Links
Read Next: The Reusable Asset Specification [HTML]
Related Topics
Subscribe via RSS
Software Development
- Article :: Pat O'Toole's Dos and Don'ts of Process Improvement: DON’T Expect a Miracle
- Article :: Pat O'Toole's Dos and Don'ts of Process Improvement: DON’T: Attend Industry Conferences
- Article :: How to Monitor Software Process Improvement
- Article :: Pat O'Toole's Dos and Don'ts of Process Improvement: Do Exit Staged, Right?
- Article :: Pat O'Toole's Dos and Don'ts of Process Improvement: Do Set the Stage for Continuous Improvement
- Article :: Management Role: Ensuring That Software Process Improvement Sticks
- Article :: Pat O'Toole's Dos and Don'ts of Process Improvement: Don’t Maintain a Low Profile
- Article :: Pat O'Toole's Dos and Don'ts of Process Improvement: Don't Carry Old Baggage on a New Journey
- Article :: Real Process Improvement: Getting What You Need
- Article :: Pat O'Toole's Dos and Don'ts of Process Improvement: DO Your Level Best To Stay Under the Threshold
Sponsored Links
About |
Privacy Policy |
Submit Resource |
Submit Article |
Contact |
Site Map
Copyright © 2009 GeekArticles.com. All Rights Reserved.
