场景:有四个上图情况不使用策略模式的时候的代码是这样的
public double getPrice(String type, double price) {
if (type.equals("普通客户小批量")) {
System.out.println("不打折,原价");
return price;
} else if (type.equals("普通客户大批量")) {
System.out.println("打九折");
return price * 0.9;
} else if (type.equals("老客户小批量")) {
System.out.println("打八五折");
return price * 0.85;
} else if (type.equals("老客户大批量")) {
System.out.println("打八折");
return price * 0.8;
}
return price;
}
首先呢,这个不符合开闭原则,且后期添加新的情况过于复杂且不变.这里呢,策略模式是这样的,首先定义四个策略方式,每个方式都实现与同一个接口获得数据,再次就是定义一个类去隔离客户端和具体的算法
策略接口
public interface Strategy {
double getPrice(double standardPrice);
}
普通客户小批量(不打折,原价)
public class NewCustomerFewStrategy implements Strategy {
@Override
public double getPrice(double standardPrice) {
System.out.println("不打折,原价");
return standardPrice;
}
}
普通客户大批量(打九折)
public class NewCustomerManyStrategy implements Strategy {
@Override
public double getPrice(double standardPrice) {
System.out.println("打九折");
return standardPrice*0.9;
}
}
老客户小批量(打八五折)
public class OldCustomerFewStrategy implements Strategy {
@Override
public double getPrice(double standardPrice) {
System.out.println("打八五折");
return standardPrice*0.85;
}
}
老客户大批量(打八折)
public class OldCustomerManyStrategy implements Strategy {
@Override
public double getPrice(double standardPrice) {
System.out.println("打八折");
return standardPrice*0.8;
}
}
负责和具体的策略类交互
/**
* 负责和具体的策略类交互
* 这样的话,具体的算法和直接的客户端调用分离了,使得算法可以独立于客户端独立的变化。
*/
public class Context {
Strategy strategy;
public Context(Strategy strategy) {
this.strategy = strategy;
}
public Strategy getStrategy() {
return strategy;
}
public void setStrategy(Strategy strategy) {
this.strategy = strategy;
}
public void pringPrice(double s) {
System.out.println("您该报价:" + strategy.getPrice(s));
}
}
测试
OldCustomerManyStrategy strategy = new OldCustomerManyStrategy();
Context context = new Context(strategy);
context.pringPrice(998);