Issue 10601: refactoring of the ExecutionContext model element (rtc-ftf) Source: Real-Time Innovations (Mr. Rick Warren, rwarren@rti.com rick.warren@rti.com rick@rti.com) Nature: Uncategorized Issue Severity: Summary: The model element ExecutionContext, which is currently an interface, has association ends and a state machine. Therefor, it would be more correct to model it as a Class instead. Its operations can be moved to a new Interface "ExecutionContextOperations" that will be implemented by the Class ExecutionContext." Resolution: ExecutionContext should be a Class so that it can have a state machine and association ends. However, a separation between Class and Interface is felt to be a good design. Therefore, the operations of ExecutionContext shall be moved to a new Interface ExecutionContextOperations, and ExecutionContext itself shall become a Class. Revised Text: · At the beginning of section 7.2.2, Components, in the figure 7.2, Lightweight RTC Package, ExecutionContextOperations should be depicted, and ExecutionContext should not be depicted with the <<interface>> keyword. All operations of ExecutionContext should move to ExecutionContextOperations. (The Associations remain attached to ExecutionContext.) · In section 7.2.2.6, Execution Context, the following new unnumbered subsection should be inserted after the existing "Description" section: Interface Realizations· ExecutionContextOperations · In section 7.2.2.6, ExecutionContext, the "Operations" section should be moved into a new numbered section, "7.2.2.7 ExecutionContextOperations" · Subsequent sections should be renumbered accordingly. · The title of the table should be changed to "ExecutionContextOperations" accordingly. · The new section "ExecutionContextOperations" should begin with the following unnumbered subsection: DescriptionThe ExecutionContextOperations interface defines the operations that all instances of ExecutionContext must provide. · In section 7.4.2, Stereotypes and Interfaces, in figure 7.16, Introspection interfaces, the depiction of ExecutionContext should be replaced with one of ExecutionContextOperations. · In section 7.4.2.4, ExecutionContextAdmin, the bullet "ExecutionContext" under the heading Generalizations should be removed. A new unnumbered subsection "Interface Realizations" should be added with a single bullet: "ExecutionContextOperations". · The ExecutionContext arguments to ModeCapable::get_current_mode_in_context and get_pending_mode_in_context should be changed to ExecutionContextOperations so that the methods can be used when the context is an instance of ExecutionContextAdmin. · Make the change in figure 7.12, Modes of operation, at the beginning of section 7.3.3, Modes of Operation. · Make the change in the operations table in section 7.3.3.3, ModeCapable. · Make the change in the IDL definitions of ModeCapable in Annex A of the specification and in RTC.idl. · A new subsection should be added to the section 8.2, IDL Definitions, before the existing subsection 8.2.1, Stereotypes: 8.2.1 Classes and InterfacesBecause UML classes and interfaces are both represented by IDL interfaces (see section 8.1.2), the types ExecutionContext and ExecutionContextOperations are essentially identical. Therefore, in the PSMs, they have been collapsed to a single IDL interface "ExecutionContext." Actions taken: January 22, 2007: receiuved issue January 15, 2008: closed issue Discussion: End of Annotations:===== te: Mon, 22 Jan 2007 11:03:08 -0800 From: Rick Warren Organization: RTI User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) To: Juergen Boldt CC: issues@omg.org, rtc-ftf@omg.org Subject: Re: issue 10477 -- RTC FTF issue Hi Juergen, We have been discussing the proposed reorganization of the diagrams under this issue (10477), but also a refactoring of the ExecutionContext model element. I think these two discussions should properly be under two separate issues. I propose that the existing issue, 10477, refer only to the diagrams. Juergen, could you please provide a new issue number for its model refactoring aspect? I suggest titling the new issue "Refactor ExecutionContext into an Interface and a Class". You can leave Takeshi Sakamoto of Technologic Arts as the Source, since he suggested the refactoring. The summary of the new issue should be: "The model element ExecutionContext, which is currently an interface, has association ends and a state machine. Therefor, it would be more correct to model it as a Class instead. Its operations can be moved to a new Interface "ExecutionContextOperations" that will be implemented by the Class ExecutionContext." Thanks, - Rick Juergen Boldt wrote: *OMG issue 10477: Lightweight RTC package diagram* *Source:* Technologic Arts (Takeshi Sakamoto, ) *Severity:* Minor *Disposition:* Resolution Proposed *Summary* At the Figure 7.2 Lightweight RTC package, it explains about Lightweight RTC but followings are mixed in the diagram. * Meta model: o Describes how each model element relates to other elements. Since it is a model that focused on the static relationship among elements, it does not describe operation usually. * Stereotype description o Describes what the base elements such as Component, elements already described for the elements described newly in the specification, are and what additive attributes are . * Interface description o Describes what sort of operation each element has. In the OMG specification, it seems that the elements are categorized and described in separate diagrams mostly. Therefore, I think it would be better if the diagram should be divided as follows. (I think it would be better that Interface description should be described at the beginning of explanation about individual element.) *Proposed Resolution* The element of ExecutionContextEntity is added. This is because ExecutionContext is defined as interface. I think it would be better that the element that realized ExecutionContext was necessary and added it. -- Rick Warren Lead Software Engineer Real-Time Innovations (RTI) 3975 Freedom Circle Santa Clara, CA 95054 +1 (408) 200-4755 rick.warren@rti.com www.rti.com RTI - The Real-Time Middleware Company X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0 Date: Mon, 22 Jan 2007 15:13:02 -0500 To: issues@omg.org, rtc-ftf@omg.org From: Juergen Boldt Subject: issue 10601 -- RTC FTF issue This is issue # 10601 refactoring of the ExecutionContext model element The model element ExecutionContext, which is currently an interface, has association ends and a state machine. Therefor, it would be more correct to model it as a Class instead. Its operations can be moved to a new Interface "ExecutionContextOperations" that will be implemented by the Class ExecutionContext." Juergen Boldt Director, Member Services Object Management Group 140 Kendrick St Building A Suite 300 Needham, MA 02494 USA tel: +1 781 444 0404 x 132 fax: +1 781 444 0320 email: juergen@omg.org www.omg.org