Art of Software Reuse

Ctrlk

Design

Wrap Legacy APIs Think Products, Not Applications Identify Common Needs Create Common Connectivity Components Consistent APIs Manage Domain Variations Evolve Functionality Iteratively Offer Reusable Assets with Multiple Interfaces Leverage Services Across Functional Flows Mediate Service Requests & Responses Refactoring Abstract Utility Functions Reduce Technical Debt Facilitate Extensibility Encapsulate Variations Using Patterns Understand Adoption Barriers Ease Testability Supportability

PreviousUnderstand Lack of Reuse NextWrap Legacy APIs

Last updated 5 years ago

Was this helpful?