Issue 7588: Start/stop behavior (swradio-ftf) Source: PrismTech (Mr. Gerald Lee Bickle, jerry.bickle@prismtechusa.com) Nature: Uncategorized Issue Severity: Summary: What is the association or behavior in regards to resource operations and provides and uses ports? Proposed Solution: Association is for the uses and provides ports and no effect on resource operations. Rationale: Consistent behavior of resource components. Resolution: Revised Text: Resolution: Association is for the uses and provides ports and no effect on resource operations. Add a semantics section to the Resource (Section 8.1.5.7) to explain this. Revised Text: This resolution assumes starting point from Issue 7904 Resolution. Added semantic paragraph to 8.1.5.7 Resource section as follows: The Resource Port Supplier and Port Connector implementation is not inhibited nor impacted by the stop operation, all methods of these two interfaces are supported, behavior unchanged. However, the behavior of the provided ports themselves is impacted. The impact of the stop is port implementation specific. The usual case is that port behavior is halted upon being stopped (started attribute is false). Resource component usage of connected port capabilities will cease and any access to provided port capabilities would result in error notification. An example would be an IO port that, upon being stopped, prevents further data from being pushed out and allows no further data to be pushed in. A notable exception would include status providing ports that would remain active even while stopped to maintain good standing with observing components. Actions taken: July 14, 2004: received issue August 2, 2005: closed issue Discussion: End of Annotations:===== ssue 11: Start/stop behavior: What is the association or behavior in regards to resource operations and provides and uses ports? Proposed Solution: Association is for the uses and provides ports and no effect on resource operations. Rationale: Consistent behavior of resource components. Jerry Bickle Engineering Fellow Network Centric Systems 1010 Production Rd Fort Wayne, IN 46808-4711 260-429-6280 Subject: SWRADIO FTF - Issue 7588 Clarification Date: Sat, 16 Oct 2004 11:43:09 -0700 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: SWRADIO FTF - Issue 7588 Clarification Thread-Index: AcSzr/5PzIPvfeASQ5WXQA9aEQhVFg== From: "Hayes, Persnaz N" To: Cc: X-OriginalArrivalTime: 16 Oct 2004 18:43:10.0013 (UTC) FILETIME=[FBE7AED0:01C4B3AF] Jerry, From the issue title and description I don.t understand what is required to be done as a resolution for this issue. Could you please clarify/explain so that I can proceed with fixing the problem(s) and recommending a resolution? Issue Title: Start/stop behavior Short Description: What is the association or behavior in regards to resource operations and provides and uses ports? Proposed Resolution/Comments Distributed with Issue Text: Association is for the uses and provides ports and no effect on resource operations. Rationale: Consistent behavior of resource components. Thank you. Neli Hayes The Boeing Company Integrated Defense Systems, Network Communication Systems Software Technical Director and Principal Software Architect (714) 762-8768 persnaz.n.hayes@boeing.com Subject: RE: issue 7904 and 7588 resolutions Date: Tue, 22 Feb 2005 10:35:28 -0500 Thread-Topic: issue 7904 and 7588 resolutions Thread-Index: AcUYdYOyOXm9nOEKQ/aLp26TL65JgAAfmTGw From: "Demirbilek, Tansu" To: "Browne, Mike \(Space Technology\)" Cc: "Hayes, Persnaz N" , X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id j1MFkO14031887 Hi Mike, I'll make those changes in the next rev of the convenience document and add the state diagram in the Rose model. I believe this would be a common resolution for both 7904 and 7588, is that right? Thanks, Tansu -----Original Message----- From: Browne, Mike (Space Technology) [mailto:mike.browne@ngc.com] Sent: Monday, February 21, 2005 7:29 PM To: Demirbilek, Tansu Subject: issue 7904 and 7588 resolutions Tansu, I do not have framemaker, etc. to formally make changes. I believe we discussed my providing you with a word doc and the associated power point for the figure, and you could cut them in. Well here they are. I hope they are to the team's liking. <> <> Please call me if you have any difficulties or if I can help further. Subject: RE: issue 7904 and 7588 resolutions To: "Hayes, Persnaz N" Cc: swradio-ftf@omg.org X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 From: Gerald_L_Bickle@raytheon.com Date: Tue, 22 Feb 2005 10:08:45 -0500 X-MIMETrack: Serialize by Router on NotesServer3/HDC(Release 6.5.2|June 01, 2004) at 02/22/2005 10:08:47 AM X-SPAM: 0.00 Comments on proposed resolution 1. I thought we were totally removing the portExists operation from the DomainManager and DeviceManger. Also, According to the issues list, the group decided not to add the port exists operation at all to the spec but remove it from spec. 2. The UnknownPorts exception should return a string sequence not a PortSequence. Jerry Bickle Engineering Fellow Network Centric Systems 1010 Production Rd Fort Wayne, IN 46808-4711 260-429-6280 Subject: RE: issue 7904 and 7588 resolutions Date: Tue, 22 Feb 2005 09:01:41 -0800 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: issue 7904 and 7588 resolutions Thread-Index: AcUY8aE15rCmMrjlTMi7X8i2miWRNQADHdeg From: "Browne, Mike \(Space Technology\)" To: "Tony Martin" Cc: X-OriginalArrivalTime: 22 Feb 2005 17:01:41.0992 (UTC) FILETIME=[2E732680:01C51900] X-MIME-Autoconverted: from quoted-printable to 8bit by amethyst.omg.org id j1MHCq14001327 Tony, The idea of the initialize is indeed to re-establish a known initial state. This distinction is made to allow a stop to be called and followed by a start to resume from the previous point. A stop/initialize/start would be a start over, cold start. The initialize is purposly prohibited from being called in the start state (see constraints associated with Resource). This was done in recognition that the initialize intended to re-initialize back to a known setting, which assumed nothing is started. Performing this action while currently started just seemed out of order and lead to possible confusing transitions. The releaseObject operation was allowed while started with this worry as the resulting state is a terminal state. That at least was the rationale. mike -----Original Message----- From: Tony Martin [mailto:tony.martin@scatechnica.com] Sent: Tuesday, February 22, 2005 7:18 AM To: Browne, Mike (Space Technology) Subject: Re: issue 7904 and 7588 resolutions Hello Mike, The resolutions look good and Tansu should be able to get these into the spec but I am curious about one thing.. In the drawing you show that a stopped process can be initialize(). I find this interesting as I would have assumed that this would have been reserved for creation only. If the purpose was to be able to reset a resource to a known state, then why would the resource have to be in the stopped state? Could one not also "initialize()" a started process? Thank You Antonio Martin Consulting Software Architect SCA Technica 603-321-5220 ----- Original Message ----- From: "Browne, Mike (Space Technology)" To: Sent: Monday, February 21, 2005 7:33 PM Subject: FW: issue 7904 and 7588 resolutions This is what I sent to Tansu for my issue resolutions. The resolution to 7904 is mostly as presented in Burlingame. The 7588 paragraph is new. > -----Original Message----- > From: Browne, Mike (Space Technology) > Sent: Monday, February 21, 2005 4:29 PM > To: 'Demirbilek, Tansu' > Subject: issue 7904 and 7588 resolutions > > Tansu, > > I do not have framemaker, etc. to formally make changes. I believe we discussed my providing you with a word doc and the associated power point for the figure, and you could cut them in. Well here they are. I hope they are to the team's liking. > > > <> > > <> > > Please call me if you have any difficulties or if I can help further. > 260-429-5060 Fax