Jump to content

Modeling the Checkout Process


TomTees

Recommended Posts

I could use some suggestion on how to model the Checkout Process for my e-commerce site.

 

As I see it, when a person "checks out" there are 5 steps...

 

1.) Create an Account/Log-In

2.) Enter Addresses

3.) Choose Shipping Options

4.) Enter Payment Details

5.) Review & Place Order

 

I'm trying to avoid having gigantic "God classes" and struggling to figure out how to abstract things in good OOP terms.

 

My Head First: Design Patterns book talked about the "State Pattern" and I'm wondering if that might be a good approach?  :shrug:

 

Maybe each of the 5 steps above could be a "state" in the Checkout Process?

 

What do you think?

 

 

TomTees

 

 

Link to comment
Share on other sites

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.