Iteration 1 : Responsibilities : Skin Spider : Kinky Solutions : A Student's Perspective by Ben Nadel

Overview Project Updates What Is Skin Spider? Iteration 1 I1 : Responsibilities I1 : Design I1 : Data Persistance I1 : No Framework I1 : The Code Iteration 2 I2 : The Code

Who Are The Players In This Game?

Now that we have a basic of what we want the application to be doing, we can start to break down our problem domain into different players and responsibilities. Let's just quickly brainstorm the sort of things we will need including object as well as responsibilities. Once we have this list, we will go back and organize it.

Spidering

For starters, we are going to need an object that can crawl over pages and collect links. That's really the basis of the application. And, let thing about it, there are different type of crawling:

1. Searching for links to thumbnail sites.
2. Searching for links to video files.
3. Downloading video files.

Data Storage

We need to be storing data. Not only that, since we are not using a database, we need to be able to store data to flat files and then read data from the files. What I am thinking is that we can probably store things in light weight XML files but then convert that to ColdFusion query objects and store them in the application scope (or other persistent memory object).

Data Retrieval And Manipulation

In addition to storing data, we need to be able to search, view, edit, and delete it. Here are some data retrieval actions that will need to occur:

1. Search the videos.
2. View a detail page about a video.
3. Update video information including name, description, tags, starring.
4. Delete a video.

Security

For this phase, we are not going to worry about security. This is going to be a single-user, non-protected application. We can always come back and factor in security in a different round. And honestly, you probably shouldn't have this application on your computer if security is an issue ;)

Those are all main responsibilities that pop into my mind. Remember, this is an initial responsibilities list. This IS GOING TO CHANGE. That's part of the iterative approach to this demonstration. That's part of the journey. Yahoo for learning!

Now that we have our initial responsibilities laid out, let's work on some prototype designs. Seeing a design will often help codify what the system's real responsibilities are.