From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 115aec,ce9ca111bc951193,start X-Google-Attributes: gid115aec,public X-Google-Thread: 103376,ce9ca111bc951193,start X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-10-12 07:57:07 PST Path: archiver1.google.com!postnews1.google.com!not-for-mail From: prenom_nomus@yahoo.com (Mark) Newsgroups: comp.realtime,comp.lang.ada Subject: Tasking diagram for SW Architecture document Date: 12 Oct 2001 07:57:06 -0700 Organization: http://groups.google.com/ Message-ID: NNTP-Posting-Host: 199.46.200.230 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: posting.google.com 1002898627 21370 127.0.0.1 (12 Oct 2001 14:57:07 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: 12 Oct 2001 14:57:07 GMT Xref: archiver1.google.com comp.realtime:4021 comp.lang.ada:14417 Date: 2001-10-12T14:57:07+00:00 List-Id: I'm soliciting opinions (hopefully with some practical experience behind them) on the notational presentation of a concurrency/tasking diagram which would be used in a software architecture document for real-time systems. It should be able to represent both OO and non-OO (modular, Ada-based, etc) designs. I've noticed that a variant of the UML collaboration diagram seems to be popular in current publications. Although the folks at Artisan feel that a DARTS type diagram is more expressive. We have already decided to use UML static structure diagrams (OMG calls them "class diagrams") showing UML packages for the logical view and deployment diagrams for the deployment view. I am particularly not concerned about CASE tool support for this diagram since it will NOT be used for any code generation etc. Visio or similar drawing tools would be fine for this. It is an informational diagram for engineers. thanks Mark