Leaderboard

Well, I don't know how seriously this is intended, but I think it questions the point of doing software modeling at all. At the risk of derailing my own thread, here are a few thoughts on why modeling is advantageous and, I think, essential for effective programming: 1) We want to be able to propose, analyze, and modify design approaches prior to implementing them. (The underlying argument is that, apart from trivial or by-rote implementations, if we just start implementing code we will not likely achieve an optimal implementation immediately; on the other hand, careful analysis can result in better-designed applications.) a) It is much faster and easier to do this in UML than in the development environment. b) UML expresses relationships more effectively than the LabVIEW IDE can. (LabVIEW's class view, for instance, does indicate inheritance relationships but it does not indicate in any fashion relationships between methods, nor other essential types of relationships, e.g., composition.) 2) Within a UML/SysML tool we can also model behaviors (e.g., state behaviors), and link all of these to other essential elements of software engineering (e.g., requirements, tests). 3) Of course, it is even better to be able to be able to create code from the model, but that is something I don't presently do (but would very much like to be able to do--without losing the other capabilities). Paul