Case Study

We received many requests from golfers that they would like the ability to save an image of their score card. This would allow them to immortalize that once-in-a-lifetime hole in one, that pro-am game with one of the golfing greats, or that holiday playing The Old Course at St Andrews Links. To satisfy this request, we will add the ability to save an image of their score card to our application. Golfers will then be able to scan an image of their score card, or take a picture of it with their smart phones, and save it in our database.

There are at least two ways to satisfy this requirement. The first might be to simply add a BLOB attribute to our existing Scoring Record entity type. And while someone could probably make a strong argument that this is where it goes, placing it there would have repercussions through much of our completed work. Therefore, for this exercise we will instead add another entity type to our data model containing the BLOB attribute. Ultimately we will end up making just about the same amount of changes or additions to our model, but by implementing it this way we will be able to better isolate and focus on those changes from the work we have already accomplished.