Forever Odd

SOS UML diagram

I completed my UML diagram a couple days ago, but due to my busy weekend I am just getting around to making the post now.  I worked on the diagram periodically for about a week and a half.   I added the notes sections in order to give me a reminder as to how I am thinking everything will work in harmony.  I do apologize if all the syntax is not correct, namely the links between classes.

I chose to not specify return types, variable types, and parameters for constructors/functions in order to preserve some generality and flexibility.   This allows me to figure out exactly what type of variable everything needs to be and exactly what parameters are necessary as I progress through the coding phase.  The layout of my program, as described by the UML, is by no means set in stone.  This is my first time designing a more robust system from start to finish, without just diving straight in to the coding, and actually doing some planning.  I felt this was important because for larger applications it is more important to have a general overview of how you are going to go about achieving your goal.

To view a larger image of my SOS UML Diagram just click on the image, then use your back button to get back to my blog.