IMHO inheritance is often overused by people new to OO design. In this sort of situation delegation is often better.
I would have a separate PaymentPolicy class that the Project class can have as an attribute. This would then be subclassed into FixedPricePolicy and PayAsYouGoPolicy (and maybe others in the future). This class heirarchy would handle anything to do with payment....
Thread: OO Design Question  |
|||||||||||||
|
Started 1 month, 1 week ago by JulianRead101
The Application
I have built a web application that allows a company to manage its clients and the projects they are doing for those clients. The app is built using PHP5 + Zend Framework.
I currently have a project class that is populated from the database on creation and has a number of different methods.
The Problem
I must now change the system so that clients can ...
|
|
||||||||||||
|
|||||||||||||
Other posts in this thread:
JulianRead101 replied 1 month, 1 week ago
Thanks for the reply, that makes a lot of sense. I will look into implementing it now.
Size: 142 bytes
Customize: 
|
Top contributing authorsRelated threads on "Dev Shed Forums - Open Source web development":Related threads on other sites: |
||||||||||||
Thread profile page for "OO Design Question" on http://www.devshed.com.
This report page is a snippet summary view from a single thread "OO Design Question", located on the Message Board at http://www.devshed.com.
This thread profile page shows the thread statistics for: Total Authors, Total Thread Posts, and Thread Activity
Home |
About Us |
Submit Your Site |
Update Your Site |
Get Search For Your Site |
Partners |
Contact |
Search Plugin |
Blog |
 |
Last Searches | Top Searches |
Designated brands and trademarks are property of their respective owners.
Use of this website constitutes acceptance of BoardReader's User Agreement and Privacy Policy.