By S.Luann
It is a good idea to have some kind of notation language specific for .Net application. This language can be easily understand by business analyst and members of a development team. nAML is that kind of language.
Unfortunately I am not excited after I read the artical[1] in WiKi. there is a lot of confusion between operation boxes and element boxes.
From the example, I bet nAML is expecting to show two aspect of a system: structural and behavioral. the former mainly by "belongs to" and the latter by action verbs. In behavioral respect, it also demonstrates the squence attributes of actions. this is done by life line.
I don't think use a box to describe operation is a good idea. In fact there are a few mistake drawings of actions even in the example. The action note in classical sequence diagram is good enough to be used here as well.
Here is my drawing for the example.
[1] An example of using nAML
http://wiki.asp.net/page.aspx/481/net-application-modeling-language
[2]nAML specification
http://code.msdn.microsoft.com/Project/Download/FileDownload.aspx?ProjectName=naml&DownloadId=3083
[3] Visio 2003 stencil for nAML
http://code.msdn.microsoft.com/Project/Download/FileDownload.aspx?ProjectName=naml&DownloadId=3084
2 comments:
I don't know why you are thinking having an action box will create any problem or confusion...the directed action arrow is fine for simple atomic actions, but to show more complex and compound action (which consistns of several action) an action box really helps to visualyze the overall flow along with having a way to isolate the actions from external nAML components.
Thanks for pointing the mistake in 'Hello World' sample. Corrected the sample in wiki and original specification document. :)
Post a Comment