asp.net-mvc – DesignPatterns：哪个最适合用于向导式用户界面

To put it another way: Where/How do you abstract/encapsulate the logic of determining what is the next step in the wizard based on what the user has chosen on a particular step of the wizard?

一种方法是建模Wizard,Step和Product类.也许是这样的？

public class Wizard
{
  public Step forward() {//...}

  public Step backward() {//...}

  public Step current() {//...}

  public Product getProduct() {//...}
}

public class Step
{
  public String name() {//...}

  public void commit(Product product) {//...}

  public void rollback(Product product) {//...}
}

public class Product
{
  //...
}

向导的目的是构建产品(汽车,计算机,假期等).

在这种情况下,它的向导决定下一步 – 可能基于向导正在构建的产品的状态.向导将在UI的控制下表现得像Builder,这将是Director并告诉向导何时以及在何种方向进行转换.由Wizard决定下一步实际是什么.可以支持多个分支点,但该实现将隐藏在向导内部.

步骤将是具有撤消/重做功能的Command Pattern的实例.