I'm quite new to OOP & am doing my first major project in this area. I've been reading quite a bit & watching loads of tutorials. However I cannot find a "best-pratice" or design pattern for a fairly common scenario. This may be a newbie question, but I hope some of you may have practical experience with this.
The use cases are complted and I have identified the various actors of the system. The website will have the following actors:
- Anonymous visitor (can make a payment or donation without becoming a member)
- EventMember (can create & modify events)
- StandardMember (can sign up for events)
Further there will be some external system "actors" like an analytics system.
Let's say I created a Person superclass and then 4 subclasses for the types of user. There would hardly be anything in common. For the administrator only the name may be stored. The member will need to set all the mandatory fields. The anonymous visitor could be a person or a bot. A visitor may become a member. The various users may share some common methods like search.
Should I create seperate classes for let's say visitor, member (with 2 member sub-types) and administrator. Also would it make sense to create separate classes for the external systems?
What is Waterfall Model?
Waterfall model is the classic Software Development Life Cycle method practiced in software development process. As the name "waterfall" describes, this development is flowing downwards steadily like waterfall, i.e., procee…
The Fluent Interface Design Pattern
You can use the Fluent Interface (http://en.wikipedia.org/wiki/Fluent_interface) design pattern to make your PHP code easier to read and maintain. "Fluent Interface" is an object-oriented design pattern that r…
This video teaches viewers how to create their own website using cPanel and Wordpress. Tutorial walks users through how to set up their own domain name from tools like Domain Registrar, Hosting Account, and Wordpress. More specifically, the order in…