Reflections on the course material

I have to admit I am in love with UML. No wait, perhaps deeply, deeply in 'Like' with UML (there are some bits that I find tedious) and when working on the restaurant case study I developed real interest in knowing what it is like working with these methodologies with a team of people on a common project. How fascinating to witness, first hand,  how the pieces fit together, supporting the other processes, etc. Perhaps I shall get the chance someday. 

I read Al's comments about her reflections to the effect each model is part form, part individual creative process and this strange alchemy is part of the attraction for me, as is, in the end, making something that works! I do believe that UML, properly applied, can and does aid the development of systems/software and reduces the risk of a project's failure (or ensures it's abandonment if that is what comes to light). 

It is interesting to reflect on this : all the cases we've been given for tutorials could become, in fact are real-time computer systems. I just passed the Lion's Yard Car Park today on my way to catch a bus, and saw cars approaching barriers, tickets being inserted, barriers lifting... it can be done, created, actualized in the world. All that we've looked at can be modeled, designed implemented.  I quite fancied the idea of finding commercial vendors of restaurant computer systems and contacting them, asking if I could see some marketing material just to get an idea how close or how far off I was in my very basic design work. It has been done! Just look over the counter next time you're at Burger King or watch the waiter tally up your bill at Revolutions.

As for object oriented design, its inherent principles and its application, this class and Java programming, helped me ' get it '  - and I was really struggling the first few weeks. I came from old school SSAD design and programming techniques... it is all in a line, just follow the line and you'll get to the end.  UML and Java have helped me see the amazing flexibility offered to both system designer and programmer by virtue of OOB's 'many facets' nature. One may follow a line for a wee bit, but bounce way over 'there', as it were, with an operation then bounce back. Models reflect other models and no one model can show you all. It is 'way cool'.

Regarding Blogging:

As a medium of communication and interaction I see now that there is a lot of potential in 'collective blogging' for want of a better way to describe it and perhaps we'll all get a chance to use it again next semester in one way or another. I hope so, I would do a few things differently and take more advantage of the potential for interactivity.

Lastly - thanks to everyone for making this class happen. I really am grateful to gain the exposure to this material. 

If anyone is interested in UML certification, ask me! I plan to pursue it. :D 

Edit to Add:

Just to be explicit, I have completed a full series of diagrams on the Green St. Car Park for the marking requirements of this blog.