Information Technology Reference
In-Depth Information
Dynamic Modeling
One effective feature of UML was visual modeling. Clearly, graph-
ical representations are superior to text for complex and abstract
concepts such as major software applications. In my view, UML
could be extended in today's world to include dynamic 3D models
in full color that can show two forms of change that are not in-
cluded in today's UML.
One form would represent and model the application when it is
executing and show the dynamics of inputs, outputs, and process-
ing in visual form. Relative speeds would be realistic but, of course,
slowed down for the benefit of human observers. Dynamic models
would help to eliminate performance bottlenecks and also reveal
security flaws.
A second form of dynamism would show the continuous growth
of requirements during development and after release. Develop-
ment requirements change on average about 2% per calendar
month and tend to be messy. Once software is delivered, it still
changes so long as there are active users. Postrelease changes av-
erage between 8% and 14% per year after release, sometimes for
more than 20 years.
Requirements changes are usually not well defined and tend
to degrade the structure of software architecture as they accumu-
late. The industry needs better and more dynamic visual represent-
ations of software in motion. Software applications are obviously
the most fast-moving products ever built, and they also evolve con-
tinuously over many years.
Another use of dynamic models would be to simulate various
kinds of virus attacks and other cyberthreats which, of course, only
occur when the software runs. Back doors might also be identified.
As Rational grew and evolved, it acquired several companies that added to
the Rational technology stack. However, the most important change occurred in
February 2003, when Rational was acquired by IBM and became known as IBM
Rational.
Search WWH ::
Custom Search