Issue 5076: RT CORBA models do not identifies network resources (uml-scheduling-ftf) Source: Universidad Politecnica de Madrid (Prof. Miguel de Miguel, mmiguel(at)dit.upm.es) Nature: Uncategorized Issue Severity: Summary: 10. RT CORBA models do not identifies network resources. RT CORBA standard does not pay special attention to communication transport times (like operating system support), but an scheduling analysis that does not take into account network resources (e.g. ATM, CAN networks, or RSVP protocols) provide scheduling analysis non realistic. The profile includes comments about the operating systems dependencies but not communication transport. Resolution: see above Revised Text: Change Fig 9-1 Add new section to 9.1.1: "9.1.1.1 RTCchannel This is an instance of a communication channel between RT CORBA ORBs. It represents the transport over which tow ORBs communicate. Attributes averageLatency the one-way latency (delay) for the communication channel. This is a time value expression, so it may be an integer, a distribution function, or a histogram. Associations schedulingPolicy (inherited from ExecutionEngine) is the scheduling policy for this communication channel. The usual policies are FixedPriority or FIFO. rTCconnection the set of RT CORBA connections that are deployed on this channel. In effect, this is an instance of a deploys relationship. However, for convenience, it is rendered in the domain model as a stereotyped association." Add new section to 9.1.1 "9.1.1.6 RTCscheduler This is an instance of an RT CORBA scheduler (see Section 7.1.3.7, "Scheduler," on page 7-10). It becomes the scheduling policy for the RT CORBA POA with which it is associated. As an infrastructure element, it is the platform for execution of the scheduler interface and serves as a resource broker for execution engines. The RT CORBA 2.0 specification defines four modules for four types of schedulers (fixed priority, earliest deadline first, least laxity first, and maximum utility (see "Scheduling Policy" on page 7-10)). Associations response the set of responses scheduled by this scheduler" Add a new association to domain definition of RTCconnection: "host the communication channel that implements this connection" Add new stereotype to section 9. Stereotype: "RSAchannel" Base Class: Classifier ClassifierRole Instance Object Node Parents: "SAengine" Tags: RSAschedulingPolicy RSAaverageLatency Tag Descriptions: Tag Name Tag Type Multiplicity Domain Attribute Name RSAschedulingPolicy Enumeration:{'FIFO','RateMonotonic','DeadlineMonotonic','HKL','FixedPriority','MinimumLaxityFirst','MaximizeAccruedUtility','MinimumSlackTime'} [0..1] RTCchannel::schedulingPolicy RSAaverageLatency RTtimeValue [0..1] RTCchannel::averagelatency Add new tag to RSAhost to RSAconnection to reference a Channel: Tag Name Tag Type Multiplicity Domain Attribute Name RSAhost Reference to an element stereotyped as "RSAchannel" [0..1] RTCconnection::host Actions taken: March 20, 2002: received issue June 30, 2003: closed issue Discussion: I will look into this (Bran) The behavior of the communication transport probably belongs in the "engineering" layer along with processors and RTOSs. One approach is to define a specialization of execution engine to define the transport characteristics. Then transport would be either an association class for the association between execution engines, or an engineering layer class that realizes the association between execution engines We've added a new Channel class to represent some kinds of communication End of Annotations:===== This is issue # 5076 RT CORBA models do not identifies network resources 10. RT CORBA models do not identifies network resources. RT CORBA standard does not pay special attention to communication transport times (like operating system support), but an scheduling analysis that does not take into account network resources (e.g. ATM, CAN networks, or RSVP protocols) provide scheduling analysis non realistic. The profile includes comments about the operating systems dependencies but not communication transport.