comment on this article

A graphical approach

What does UML 2.0 bring to the graphical modelling landscape? By Vanessa Knivett.

With system complexity on the increase and time to market pressures tightening, system designers have to work harder and smarter than ever. And, in their efforts to find solutions to increasingly difficult design problems, they find themselves struggling to find terms to describe them.

As problems and solutions become more complex, not only is it harder for authors to describe them, but it is harder for reviewers and other users to understand the descriptions. This is driving the adoption of graphical modelling languages, as exemplified in the Unified Modelling Language, or UML.

For the Object Management Group (OMG), UML is a key step in a much grander plan to encourage industry adoption of a model driven development architecture – a means of reducing the importance of code and focusing on what matters: how the final application is supposed to work. Telelogic's senior methods engineer Morgan Björkander, says: "Model driven development turns systems and software development into more of a systems and software engineering discipline."

Click here to request this article by email

Author
Graham Pitcher

Comment on this article


This material is protected by MA Business copyright See Terms and Conditions. One-off usage is permitted but bulk copying is not. For multiple copies contact the sales team.

What you think about this article:


Add your comments

Name
 
Email
 
Comments
 

Your comments/feedback may be edited prior to publishing. Not all entries will be published.
Please view our Terms and Conditions before leaving a comment.

Related Articles