The First Four Use Cases are Complete

After three months, countless questioning and a conviction that I was an idiot for overdesigning this, the first four Use Cases are complete! That's right, a user can NOW enter in data to either determine their pace, run time OR distance ran!

Like I said earlier, it is THREE months past due. What should have been completed over a weekend took this long to complete. I over designed EVERYTHING. From the actual design to the data entry views to the modeling concepts. This whole thing could actually be done in Microsoft Excel with no problem! But I decided to be stuborn and make it more than I probably should. But, in the end, I did learn a lot! To me, as stated earlier in this blog, that was the most important part of the whole thing. That, and the fact that I wanted to blog my development process, if for no ther reason than for archiving a design. I think I will publish this design for myself. I found websites that will aid me in that effort.

Now, it is time to finish the application and complete the Use Cases by developing the last Use Case: the "Save RunData" use case. I fear that use case will be the hardest to develop. I need to learn/refamiliarize myself with Serialization. I also need to determine if I am going to go ahead and set up a database to save the data--or just put the data in a format that can be used by Microsoft Excel (or some other spreadsheet). Also, I do need to go ahead and start the work in the ACTUAL class that I am taking: A Visual Basic Class. So, I will try to split my time more evenly between this project and my class.