License

I agree with the author that UML’s lack of integration into automated lifecycle process at both the domain end and the technology end tends to make the documentation a one time island of work. However, I do not agree that domain specific products have to be developed. We do not understand sytems well enough yet to make such a conclusion.

The criticism of UML’s lack of ability to generate code is one of the reasons I am in favor of the Associative Model of Data and the Sentences ADBMS at LazySoft. The schema, form design, query design and results are all built into a single user interface that can be updated in real time and issues such as normalization and denormalization that plagues relational database integrity and performance do not exist.

This is a topic I have thought about quite a bit. I find that I am a focused person and upon achieving flow either at work or in my own study I will not allow that state to be interrupted until the product of my flow is completed. This does not correspond to the work habits of the status quo. It is not nine to five behavior. Consequently, my employers are continually at odds with performance and attendance. My experience of flow is generally not a team experience and I will not interrupt it to accommodate a team experience of flow. I will simply produce my deliverable and go and get some sleep.