I'm coming at UML from a conceptual angle.
I'm looking for a way to communicate with both the developers and the business users about the process at hand. UML looks like (if my developers understand it, which I doubt) I can use it to lay out pre-development application architecture/requirements for my myriad required documents.
So if we all agreed on it, I'd be fine using it for high level sequence diagrams, for instance. And use case diagramming.
Thing is, we're pretty much a waterfall development environment, and this teacher is tying UML pretty tightly to very iterative development. I dont think it's as causal as he says, though.
I'm not sure it'd help me write code if I were doing the analysis myself. I may try and write up the Phoenix and see what happens.
Still, it's helping regularise my self-taught OOP stuff, and can go on my resumé.
What is UML? Some type of markup language, I'm guessing.
UML is a detailed form of diagramming used mostly in software development.
See, I think UML makes more sense for waterfall. You can do the diagrams once and then execute on them. Maybe you change them a little bit as you go along, but not much.
In iterative, you'd have to change them over and over again. I doubt most people would, and you'd end up with the diagrams not matching the sytem.
Current instructor sees iterative as repeteadly modifying the diagrams to look progressively less and less like the "problem domain" and more like the solution architecture. Also, to pick the high profile use cases and start from there.
Perkins,
you need to set up the Tivo to check the mothership periodically or the clock starts drifting and the taping won't begin and end at the correct time.
Thanks LN-- I will keep that in mind.
Ooooh. iPod mixing board for DJs [link]
Jilli, my buddy Rivethead_242 is making his club DJ debut (he's DJ'd between sets at a few local concerts) this weekend, and he's DJing by iPod. Actually, I think it's 1 iPod, 1 iBook, and his iButt.
