Issue 7584: Specify which interfaces are mandatory (swradio-ftf) Source: PrismTech (Mr. Gerald Lee Bickle, jerry.bickle@prismtechusa.com) Nature: Uncategorized Issue Severity: Summary: Specify which interfaces are mandatory, and which ports are required for components Rationale: Consistency and standardization of components, improves waveform portability of code and XML descriptors. Resolution: Revised Text: Actions taken: July 13, 2004: received issue April 19, 2007: closed no change Discussion: Discussion: October 7, 2004 FTF Telecon: Jerry's suggestion for how to tackle the solution for this issue: Treat it as a base component definition. E.g. for an audio component, at a minimum, it should have these types of features. If audio or serial should have a required control or data port, we should specify that in the constraint section Tansu Demirbilek provided the resolution included below, and this issue was included in the 1st ballot. However, there was some discussion on the scope of the provided resolution and the issue was pulled from the 1st ballot. March 10, 2005 Telecon: Jerry: Not sure if there is any more to be done here. Perhaps Tansu's already submitted resolution is fine. Tansu will touch base with Jerry during 2nd FTF. Revised Text: In Section 9.3.1.2.1, (ConnectionlessLink Component), pg 211, replace the following sentence in the Constraints section: "ConnectionlessLinkComponent shall provide at least one bi-directional DataControl port." with "ConnectionlessLinkComponent shall provide one ControlPort, at least one input DataControl port and at least one output DataControl port." In Section 9.3.1.3.1, (AckConnectionlessLink Component), pg 214, replace the following sentence in the Constraints section: "AckConnectionlessLinkComponent shall provide at least one bi-directional DataControl port." with "AckConnectionlessLinkComponent shall provide one ControlPort, at least one input DataControl port and at least one output DataControl port." In Section 9.3.1.4.2, (ConnectionLinkComponent), pg 220, replace the following sentence in the Constraints section: "ConnectionLinkComponent shall provide at least one bi-directional DataControl port." with "ConnectionLinkComponent shall provide one ControlPort and at least one StreamPort." In Section 9.3.2.3, (MediumAccessController Component), pg 226, replace the following sentence in the Constraints section: "The MediumAccessController Component shall provide at least one DataControl port." with "MediumAccessController component shall provide one ControlPort, at least one input DataControl port and at least one output DataControl port." In Section 9.5.2.1.1, (ModemComponent), pg 236, create a Constrains section and add this statement: "ModemComponent shall provide one ControlPort and at least one DataControlPort or DataPort. All of the device definitions shown in Figure 9-74 that specialize ModemComponent shall provide these ports at a minimum." In Section 9.5.2.2.1, (ModemComponent), pg 242, create a Constrains section and add this statement: "RFIFComponent shall provide one ControlPort and at least one DataControlPort or DataPort. All of the device definitions shown in Figure 9-77 that specialize RFIFComponent shall provide these ports at a minimum." Disposition: Deferred Discussion: Not sure if there is any more to be done here. Perhaps Tansu's already submitted resolution is fine. Tansu will touch base with Jerry during 2nd FTF. 2nd FTF will include the changes included with this issue and the disposition. Disposition: Deferred Discussion: No longer an issue. What is imporptant are the interfaces, and the components are there for references. We are only interested in platform service components being standardized and not the WFs. This issue has been overcome by events, In the Data Link Layer Facilities volume spec, DLL component definitions have constraints for the types of ports that needs to be supported. End of Annotations:===== ssue 7: Specify which interfaces are mandatory, and which ports are required for components Rationale: Consistency and standardization of components, improves waveform portability of code and XML descriptors. Jerry Bickle Engineering Fellow Network Centric Systems 1010 Production Rd Fort Wayne, IN 46808-4711 260-429-6280 Subject: Issues 7661 and 7584 Date: Fri, 8 Oct 2004 14:41:53 -0400 Thread-Topic: Issues 7661 and 7584 Thread-Index: AcStZnpJgdz+VN3sST+00n9nhFZ6qQ== From: "Demirbilek, Tansu" To: Cc: X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id i98J0j1U011818 This is a comment on issues 7661 and 7584. Issue 7584: Specify which interfaces are mandatory, and which ports are required for components Issue 7661: : The specification lacks consistent use of the SWRadio stereotypes for the interface definitions in the Facilities. Even though the deadline for Issue 7584 is earlier than that for 7661, I propose to resolve 7661 first, and define the interfaces according to section 8.3.1. After doing this, we can easily specify which ports are needed for each component. (Idata interface requires DataPort, etc.) Subject: Question about ports Date: Mon, 18 Oct 2004 15:37:26 -0400 Thread-Topic: Question about ports Thread-Index: AcS1SeW7F9DEYSL3QSyVd+l33+HhQQ== From: "Demirbilek, Tansu" To: Do we currently specify the direction of data in port definition, and if not, do you guys think it might be necessary? I'm in the process of providing a resolution for 7584 (required ports for components) and I was wondering if it is required to mention the direction of the ports. Thanks, Tansu A. Tansu Demirbilek Systems Engineer Mercury Computer Systems, Inc. 199 Riverneck Road Chelmsford, MA 01824 Office: +1-978-967-1129 Fax: +1-978-256-8596 Subject: Re: Question about ports To: "Demirbilek, Tansu" Cc: X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 From: Gerald_L_Bickle@raytheon.com Date: Mon, 18 Oct 2004 15:00:04 -0500 X-MIMETrack: Serialize by Router on NotesServer3/HDC(Release 5.0.13a |April 8, 2004) at 10/18/2004 03:00:09 PM X-SPAM: 0.00 I was going to generate an issue that the SWRadioPort should have a property that indicates the type of port (required = in, provided = out, or both = in out) Jerry Bickle Engineering Fellow Network Centric Systems 1010 Production Rd Fort Wayne, IN 46808-4711 260-429-6280 260-429-5060 Fax "Demirbilek, Tansu" To: cc: Subject: Question about ports 10/18/2004 02:37 PM Do we currently specify the direction of data in port definition, and if not, do you guys think it might be necessary? I'm in the process of providing a resolution for 7584 (required ports for components) and I was wondering if it is required to mention the direction of the ports. Thanks, Tansu A. Tansu Demirbilek Systems Engineer Mercury Computer Systems, Inc. 199 Riverneck Road Chelmsford, MA 01824 Office: +1-978-967-1129 Subject: Re: Question about ports To: "Demirbilek, Tansu" Cc: X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 From: Gerald_L_Bickle@raytheon.com Date: Mon, 18 Oct 2004 15:00:04 -0500 X-MIMETrack: Serialize by Router on NotesServer3/HDC(Release 5.0.13a |April 8, 2004) at 10/18/2004 03:00:09 PM X-SPAM: 0.00 I was going to generate an issue that the SWRadioPort should have a property that indicates the type of port (required = in, provided = out, or both = in out) Jerry Bickle Engineering Fellow Network Centric Systems 1010 Production Rd Fort Wayne, IN 46808-4711 260-429-6280 260-429-5060 Fax "Demirbilek, Tansu" To: cc: Subject: Question about ports 10/18/2004 02:37 PM Do we currently specify the direction of data in port definition, and if not, do you guys think it might be necessary? I'm in the process of providing a resolution for 7584 (required ports for components) and I was wondering if it is required to mention the direction of the ports. Thanks, Tansu A. Tansu Demirbilek Systems Engineer Mercury Computer Systems, Inc. 199 Riverneck Road Chelmsford, MA 01824 Office: +1-978-967-1129 260-429-5060 Fax