Is Papyrus Ready?

Late last year, Michael Jastram stated that he was disappointed in Eclipse Papyrus, which I will admit was probably a valid concern in the past.

This prompted me to comment on it on the PapyrusUML blog, first in my secret identity as one of the bloggers on that site and then as myself in the comment (thus revealing said secret identity).

As a result of this, Jaxenter invited be to provide a longer response to address various aspects of Papyrus. And I agreed to answer their questions as this type of conversation can only ensure that we have an active, constructive discussion to improve our mutual understanding and Papyrus.

You can see my response in their “Eclipse Papyrus — Ready for the big stage?” article.

In short, it all depends on your expectations. Are you a UML expert or a toolsmith? Then you may very well find what you need in Papyrus. Are you a beginner with UML? Then you may very well be overwhelm by the tool. It’s all a matter of perspective, expectations, and needs!

The one thing I am certain of is that, with the Papyrus Industry Consortium, Papyrus’ future is brighter than a year ago!

Your Business May Depend on Your CMO and CIO Working Together

This is a great article that brings up some issues that can prevent the CMO and CIO from working effectively together and aligning their decisions with the enterprise’s business objectives, instead of their own departments.

Your Business May Depend on Your CMO and CIO Working Together.

This is also an area where IBM Rational can help, in facilitating  collaboration between these two, sometimes silo’ed, entities, especially where software and system intensive solutions are at play.

IBM Rational’s tools for product portfolio management can help manage the input from both the CMO and CIO teams to the definition of the products provided by the enterprise. Each division provides its needs, its objectives, and its desired outcomes, and IBM Rational Focal Point can help blend all of this and keep it aligned with the overall division and enterprise business objectives. Each product (or project) can then be evaluated against these business objectives and scheduled accordingly.

Further integration between the product portfolio tools and IBM Rational’s collaborative lifecycle management platform then ensures that the software and system requirements can be traced to the implementation and deployment of the software/systems products.

Yes, this is a simplified view of the whole thing, but it can and has been done in the past!

RSD and UPDM: Enterprise Architecture for Systems

Steve Hovater has just published to developerWorks a great article on using the new UPDM functionality in RSD 7.0.5. The article takes you through a short introduction to UPDM, followed by the creation of a small model, and concluding with the use of Eclipse BIRT to create the associated DoDAF views.

If you are into systems development or enterprise architecture, I would recommend you take a look!