Which pattern should i follow? Whether Strategy pattern or normal Abstract methods

Question

4.00/5 (1 vote)

See more:

I have a requirement and i am addled to which pattern i must go for.

Requirement : I have 3 methods namely PopulateAccountBalance(), PopulatePayeeAccount() and PopulateDistributionDate(). Here the two methods PopulateAccountBalance() and PopulatePayeeAccount() implementation is going to vary based on 3 GroupTypes namely Group1 , Group2 and Group 3.

I know i can go either for Strategy Pattern OR a normal abstract classes with Parent-child relationship where base class acts as parent and 3 separate child classes for each Group.

In the second choice the base class will be an abstract class and will hold common method PopulateDistributionDate() being implemented and the other two methods which gonna vary based on child class will be abstract methods. It is the duty of the child classes to implement abstract methods on their way.

Now which way should i follow. Whether shall i go for Strategy pattern or Abstract class way.

Posted 9-Jan-11 23:13pm

sri_3464

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Venkatesh Mookkan · Accepted Answer · 2011-01-09T23:18:00

Solution 1

I would go for Abstract class way (Second Method).

Update:

It is difficult to justify. It is definitely upto your business need.

One clear advantage is you can have partial or full implementation of the methods in the base class itself.

You can read the following articles to get more information:

Abstract Class versus Interface[^]

MSDN Reference[^]

Mark it as answer if it is helpful

Posted 9-Jan-11 23:18pm

Venkatesh Mookkan

Updated 9-Jan-11 23:35pm

v3

Comments

sri_3464 10-Jan-11 5:22am

can you please justify.. i tried googling to know about it.. not getting the satisfying reason

Venkatesh Mookkan 10-Jan-11 5:34am

I have updated the answer.