In my mainframe world I always cautioned my users to avoid coupling new technology with a new application -- calling it a "formula for disaster".
And that's kind of what this is as I am new to both Java and Patterns. (Run for the hills!). For Java I'm using Oracle's online Java Tutorial and for Patterns I'm using Head First Design Patterns put out by O'Reilly. I'm reasonably familiar with OOP.
For educational purposes, I'm taking an application I built for my wife in PHP to see if I can re-tool it (in Java using Patterns). Though the strategy pattern seems to fit the bill, I'd like your thoughts.
This application consists of 4 data-stores: The Student, The Horse, The Tack and The (Lesson) Recap. All four of these require C.R.U.D. (Create, Retrieve, Update, Delete) capabilities. The Horse and The Tack data-stores consist of merely a key and a name. The Student only a key, a name and an enum lesson day (Sunday ... Saturday) The recap, however, contains not only the key, but the data from a unique combination of these tables along with the instructor name, the date, a session identifier, a lesson identifier and a text recap of the lesson.
What pattern would you use for this and what would you set as your interfaces?