Issue 5990: PAstep needs tags for message size (uml-scheduling-rtf)
Source: Carleton University (Dr. Murray Woodside, cmw(at)sce.carleton.ca)
Nature: Uncategorized Issue
Severity: 
Summary: There are no tags for message size, which is really important when the
messages are 
transmitted over a communication network. For a synchronous message, there
are in 
fact two message sizes: one for the request and the other for the reply. 


       - As the UML messages are stereotyped as PAStep, an easy fix would be
to add 
two tags to a step, PAinSize and PAoutSize of type Integer, to describe the
size of 
the data needed as input for the step, and the size of the results produced
by the 
step. Most steps would not need these tags. 

Resolution: 
Revised Text: 
Actions taken:
July 3, 2003: received issue
Discussion: 
This seems to require a new feature, hence a new RFP
End of Annotations:=====
From: "Moore, Alan" <AlanM@artisansw.com> 
To: "Juergen Boldt (E-mail)" <juergen@omg.org> 
Subject: Issues with SPT 
Date: Thu, 3 Jul 2003 09:30:24 +0100 
X-Mailer: Internet Mail Service (5.5.2653.19) 


Hi Juergen,



Can you raise the following four issues against the Profile for
Schedulability, Performance and Time.



4. Title: PAstep needs tags for message size


Source: Murray Woodside and Dorina Petriu


There are no tags for message size, which is really important when the
messages are 
transmitted over a communication network. For a synchronous message, there
are in 
fact two message sizes: one for the request and the other for the reply. 


       - As the UML messages are stereotyped as PAStep, an easy fix would be
to add 
two tags to a step, PAinSize and PAoutSize of type Integer, to describe the
size of 
the data needed as input for the step, and the size of the results produced
by the 
step. Most steps would not need these tags. 
Thanks,
Alan