Issue 5725: Section 5, Page 5-2: Tag definitions (uml-scheduling-ftf)
Source: The MathWorks (Mr. Alan Moore, alan.moore(at)mathworks.co.uk)
Nature: Uncategorized Issue
Severity: 
Summary: Tag definitions. The domain attribute name of RTduration is wrong.
 

Resolution: See issue 5039 for disposition
Revised Text: 
Actions taken:
October 25, 2002: received issue
June 30, 2003: closed issue
Discussion: 

End of Annotations:=====
From: "Moore, Alan" <AlanM@artisansw.com> 
To: "'Juergen Boldt'" <juergen@omg.org> 
Subject: RE: issues 5710 - 5714 -- UML Profile for Scheduling FTF
issues 
Date: Fri, 25 Oct 2002 09:54:05 +0100 
X-Mailer: Internet Mail Service (5.5.2653.19) 


Hi Juergen,


You missed:


Section 5, Page 5-21
Tag definitions. The domain attribute name of RTduration is wrong.
Miguel de Miguel 


Thanks again,
Alan.
> -----Original Message-----
> From: Juergen Boldt [mailto:juergen@omg.org]
> Sent: 24 October 2002 18:43
> To: issues@omg.org; uml-scheduling-ftf@omg.org
> Subject: issues 5710 - 5714 -- UML Profile for Scheduling FTF issues
> 
> 
> All issues submitted by Alan Moore   "Moore, Alan" 
> <AlanM@artisansw.com>
> 
> 
> 
> This is issue # 5710
> 
> Section 4, Page 4-38,
> 
> GRMrelase stereotype there is a spelling error.
> 
> ==================
> 
> This is issue # 5711
> 
> Section 5, figure 5-5.
> 
> Some scheduling analysis techniques use more than one 
> duration time in the 
> description of actions (one action, specially SAction that inherits 
> TimedAction, can have associated more than one duration and this can 
> provide different scheduling analysis results).
> 
> =================
> 
> This is issue # 5712
> 
> Section 5, Page 5-13 first lines.
> 
> The definition of duration looks like an "execution time" 
> definition, not 
> like a "computation time" definition, that is the role of 
> this attribute in 
> analysis metamodels. Suggest the following definition: "the 
> time interval 
> of execution capacity used by the action"
> 
> ==================
> 
> This is issue # 5713
> 
> Section 7, Figure 7-1
> 
> We suggest changing some multiplicities to avoid some problems. The 
> association ExecutionEngine-SchedulingJob imposes a single 
> ExecutionEngine 
> to SchedulingJob. In distributed systems an schedulingjob 
> will execute in 
> mode than one execution engine (the modification of page 118 
> description of 
> Scheduling Jobs is because of this). Some scheduling analysis 
> techniques 
> support alternative of responses (more than one response for each 
> scheduling job), and more than one trigger event can generate 
> the execution 
> of the scheduling job.
> 
> ===================
> 
> This is issue # 5714
> 
> Section 7,Page 7-8
> 
> Suggest the following definition Execution Engine: "An 
> execution engine is 
> an active, protected, executing-type resource that is 
> allocated to the 
> execution of schedulable resources, and hence any actions 
> that use those 
> schedulable resources to execute. In general, they are 
> processor, network 
> or device."  See issue with page 30 in section 4. This 
> modification takes 
> in to account the scheduling policies in networks and devices 
> (not only 
> processors)
> 
> ==================
> 
> =================================
> Juergen Boldt
> Director, Member Services
> 
> Object Management Group
> 250 First Avenue, Suite 100
> Needham, MA 02494
> 
> Tel.          +1 781 444 0404 ext. 132
> Fax:          +1 781 444 0320
> email:                juergen@omg.org
> www           www.omg.org
> 
> ================================
>