When I started this module, I have to admit I was thinking that UML is all well and good but isn't my cup of tea. I just wanted to be a developer who grinds out code all day.
But, more recently, as the problems I want to solve get more complicated, I can see why UML is needed. Even for our Least Squares Regression assignment for Software Engineering, I voluntarily drew a rough class diagram to help me plan my classes. UML can seem a little abstract when you have little or no industry experience. However, through my own experience, I am at least starting to understand why UML is necessary.
Subscribe to:
Post Comments (Atom)
1 comment:
Having worked on a major implementation for a business not using any formal modeling whatsoever (save awkwardly drawn flow charts on dry-wipe boards) I, too, 'have seen the UML light'.
It is in essence a powerful diagrammatic language that has the breadth and scope, from big picture to little picture, to fashion, conceptually, what a system needs must do.
And then supports the creation of it.
Post a Comment