naml Forum Rss Feed

NEW POST: nAML and UML

OlivierCueilliez — Wed, 17 Sep 2008 18:57:35 GMT

Hi,

The name, nAML, confused me as it suggests is it .NET oriented.

I guess what stands for Microsoft stands for you: If you feel that the current UML notation is not sufficient for all design problems (I have this feeling myself, time to time), why don't you join the OMG as an individual contributor? There is still room for UML improvement, as it is still not possible to develop software just by designing it with UML, which I believe is one of the goal of the OMG (along with the even-more abstract concepts behind MOF and MDA).

There are some interesting ideas in your proposals and I am going to give them a try. I would like to see what kind of design problems could be solved using your new types of diagram.

Olivier

NEW POST: nAML and UML

joycsc — Mon, 15 Sep 2008 09:28:53 GMT

Hi,

Sorry this is NOT from Microsoft, but a personal effort.

In last couple of years in my software development career, I have worked several mid and large scale projects, from system analysis, designing architecture, implementation to tester level. To express both requirements and technical concepts, visual modeling became a vital need for me, especially for very complex level problems and corresponding candidate solutions. I became (and still) a big fan of UML, which has very powerful notations and semantics to describe a system visually from different point of view. This smart visual modeling language made my software development life much easier, even while I was reviewing the requirement and technical models after a long interval.

In many cases, on my recent software projects, I have been feeling need of a simpler semantic notation, where I can model an existing and proposed system in a single diagram, both from structural (static) and behavioral (dynamic) point of view, from physical to logical point of view and moreover which will be easy enough to be implemented quickly with a small set of notations. Having both structural and behavioral components along with low level view in a single diagram, may require a considerable big space. However for a complex system and/or concept this can be considerable to have the whole model illustrated in a wide big whiteboard or wall enabling the system stakeholders and architect to view the system from deeper view.

After establishing the notations and semantics for nAML and its successful implementation, I just wanted to share the idea with others, so that others can be benefitted. Using nAML doesn’t mean that you have to leave your existing modeling practices, but if the new concept really adds some benefit on your developer life, don’t forget to have your own feedback to make nAML better.

OlivierCueilliez wrote:
Hi,

I am a UML user; and I would like to know why Microsoft created a new modeling language instead of putting its strengths in the improvement of the existing unified standard?

By the way, I would appreciate a sort of comparison table between both modeling languages, with forces and weaknesses.

It seems to me that UML would be sufficient to design .Net applications. What design problem could be solved with nAML that could not be solved with UML?

Thanks,
Olivier

NEW POST: nAML and UML

djwa — Fri, 12 Sep 2008 22:11:15 GMT

I don't think this is MS created - check out the article on code project from the link on the front and it seems to be coming from a developer.

NEW POST: ever hear of UML 2.0?

uml_modeler — Fri, 12 Sep 2008 19:20:34 GMT

How would you compare & contrast?

I would say without exaggeration that 1000s of man years of collective effort have gone into the standardization of the Unified Modeling Language by the OMG.

NEW POST: nAML and UML

OlivierCueilliez — Fri, 12 Sep 2008 19:19:23 GMT

Hi,

I am a UML user; and I would like to know why Microsoft created a new modeling language instead of putting its strengths in the improvement of the existing unified standard?

By the way, I would appreciate a sort of comparison table between both modeling languages, with forces and weaknesses.

It seems to me that UML would be sufficient to design .Net applications. What design problem could be solved with nAML that could not be solved with UML?

Thanks,
Olivier