Issue 9231: Inconsistent use of the term "Facility or Facilities" (swradio-rtf) Source: L-3 Communications, Communication Systems - West (Mr. Mark Scoville, mark.scoville@L-3com.com) Nature: Uncategorized Issue Severity: Summary: Problem: In chapter 4, Facility is defined to be, "An environment providing a realization of certain functionality through set of well defined interfaces." Subsequently, in chapter 9, the SWRADIO PIM components (5 Facilities) are defined not referring to "environments", but refer to "set of interfaces", "set of services", and for the last three, functional definitions. These "facility" definitions are confusing, and need to be worded to reflect consistent ideas. Proposed Solution: The ultimate solution would be to refactor the specification to reflect the standard definitions provided in the OMAG (http://www.omg.org/docs/ab/97-05-05.pdf <http://www.omg.org/oma/>) - upon which the MDA (<http://www.omg.org/docs/omg/03-06-01.pdf> and its current terminologies) was guided. Shy of that, redo the definitions of "facility" in chapter 4, and change the facilities as defined in chapter 9 to consistently reflect the following definitions. In summary there are four classifications of object interfaces: * Object Services are interfaces for general services that are likely to be used in any program based on distributed objects. * Common Facilities are interfaces for horizontal end-user-oriented facilities applicable to most application domains. * Domain Interfaces are application domain-specific interfaces. * Application Interfaces are non-standardized application-specific interfaces. Rationale: This change will clarify the intent of a facility in the SWRadio specification, and make it consistent with standard OMG-speak. Resolution: Revised Text: In: · section 4 sbc/06-04-08 (Common and Data Link Layer Facilities Specification) · section 4 sbc/06-04-05 (Communications Channel and Equipment Specification), · section 4 sbc/06-04-04 (Component Framework Specification) · section 9.0 sbc/06-04-17 (PIM and PSM for Software Radio Components Specification Version 1.0) change the definition of Facility from: An environment providing a realization of certain functionality through set of well defined interfaces. to: The realization of certain functionality through a set of well defined interfaces. In sbc/06-04-08 (Common and Datalink Layer Facilities Specification) section 7.0 change the following text from: · Common Platform Facilities - This facility defines the set of services that all components within a platform can be used. Examples of these types of services are log, naming, and event service. · Common Layer Facilities - This facility defines the set of interfaces that all components (regardless of any layering) within a platform can realize. Examples of these types of interfaces are flow control, packet, and stream interfaces. · Data Link Layer Facilities - These facilities define Link Layer Control (LLC) and Medium Access Control (MAC) layer functionality for communication needs. to: · Common Platform Facilities - The set of interfaces that all components within a platform can be used. Examples of these types of services are log, naming, and event service. · Common Layer Facilities - The set of interfaces that all components (regardless of any layering) within the radio can realize. Examples of these types of interfaces are flow control, packet, and stream interfaces. · Data Link Layer Facilities - The set of interfaces that define Link Layer Control (LLC) and Media Access Control (MAC) layer functionality for communication needs. In sbc/06-04-08 (Common and Datalink Layer Facilities Specification) section 7.2, change the following text from: · Quality of Service Facilities - defines the quality of service related facilities. · Flow Control Facilities - provides means to control communication flow so that a sender does not transmit more packets than a receiver can process. · Measurement Facilities - specifies facilities to set up waveform related measurement parameters and schedule the measurement. · Error Control Facilities -- allows the Receiver to tell the Sender about frames damaged or lost during transmission, and coordinates the re-transmission of those frames by the Sender. · PDU Facilities - defines the Protocol Data Unit (PDU) building block concept that can be used in connectionless communication among radio sets as well as inter-component communication within a radio. · Stream Facilities - defines the stream building block concept that can be used in connection-oriented communication among radio sets as well as inter-component communication within a radio. to: · Quality of Service Facilities - The set of interfaces that define the quality of service related functionality. · Flow Control Facilities - The set of interfaces that control communication flow between senders and receivers. · Measurement Facilities - The set of interfaces that provide measurement parameters and intervals. · Error Control Facilities - The set of interfaces that allow the Receiver to tell the Sender about frames damaged or lost during transmission, and coordinates the re-transmission of those frames by the Sender. · PDU Facilities - The set of interfaces that define the Protocol Data Unit (PDU) used in communication among radio sets as well as inter-component communication within a radio. · Stream Facilities - The set of interfaces that define the stream concept used in communication among radio sets as well as inter-component communication within a radio. In sbc/06-04-05 (Communications Channel and Equipment Specification) section 8, change the following text from: · Physical Layer Facilities - These facilities define the functionality to convert the digitized signal into a propagating RF wave, and conversely, to convert a propagating RF wave into a digitized signal for processing. The facilities also include frequency tuning, filters, interface cancellation, analog digital conversion, up/down conversion, gain control, synthesizer, etc., functionality. Lastly, the Facilities have Input and Output (I/O) Facilities for serial and audio layer functionality. · Radio Control Facilities consist of facilities that are used to manage the control of a RadioSet such as audio alarms, Radio Set configuration, and Radio Set channel management. To: · Physical Layer Facilities - The set of interfaces that define the functionality to convert the digitized signal into a propagating RF wave, and conversely, to convert a propagating RF wave into a digitized signal for processing. The facilities also include frequency tuning, filters, interface cancellation, analog digital conversion, up/down conversion, gain control, synthesizer etc., functionality. Physical layer facilities also include functionality for baseband I/O such as serial and audio devices. · Radio Control Facilities - The set of interfaces that define the functionality to manage the radio domain and channels within the radio. In sbc/06-04-17 (PIM and PSM for Software Radio Components Specification Version 1.0) section 9.0, change the following text from: · Common Layer Facilities - This facility defines the set of interfaces that all components (regardless of any layering) within the radio can realize as described in reference 3.1.5.2. Examples of these types of interfaces are flow control, packet, and stream interfaces.\ · Common Radio Facilities - This facility defines the set of services that all components within the radio can be used. Examples of these types of services are log, naming, and event service as described in reference 3.1.3. · Data Link Layer Facilities - These facilities define Link Layer Control (LLC) and Media Access Control (MAC) layer functionality for communication needs as described in reference 3.1.5.2. · Physical Layer Facilities - These facilities define the functionality to convert the digitized signal into a propagating RF wave, and conversely, to convert a propagating RF wave into a digitized signal for processing as described in reference 3.1.5.2. The facilities also include frequency tuning, filters, interface cancellation, analog digital conversion, up/down conversion, gain control, synthesizer, etc., functionality. Physical layer facilities also include functionality for baseband I/O such as serial and audio devices. · Radio Control Facilities - These facilities define the functionality to configure, get status, and control the radio domain and channels within the radio as described in reference 3.1.5. To: · Component Framework Facilities - The set of interfaces that all components (regardless of any layering) within the radio can realize as described in reference 3.2.5. Examples of these types of interfaces are waveform, device, and platform management interfaces. · Common Layer Facilities - The set of interfaces that all components (regardless of any layering) within the radio can realize as described in reference 3.2.1. Examples of these types of interfaces are flow control, packet, and stream interfaces. · Common Radio Facilities - The set of interfaces that all components within the radio can use. Examples of these types of facilities are log, naming, and event service as described in reference 3.2.1. · Data Link Layer Facilities - The set of interfaces that compose the Link Layer Control (LLC) and Media Access Control (MAC) layer functionality for communication needs as described in reference 3.2.1. · Physical Layer Facilities - The set of interfaces that define the functionality to convert the digitized signal into a propagating RF wave, and conversely, to convert a propagating RF wave into a digitized signal for processing as described in reference 3.2.4. The facilities also include frequency tuning, filters, interface cancellation, analog digital conversion, up/down conversion, gain control, synthesizer etc., functionality. Physical layer facilities also include functionality for baseband I/O such as serial and audio devices. · Radio Control Facilities - The set of interfaces that define the functionality to manage the radio domain and channels within the radio as described in reference 3.2.4. Actions taken: December 8, 2005: received issue April 19, 2007: closed issue Discussion: Resolution: 1. Remove the word "environment" from the definition of facility 2. Refine the definitions of the five facilities to be more consistent in their use of terms like "interfaces", "services", and "defines <…> functionality". End of Annotations:===== m: mark.scoville@L-3com.com To: issues@omg.org, swradio-rtf@omg.org Subject: SWRADIO RTF Issue - Inconsistent use of the term "Facility or Fac ilities" Date: Thu, 8 Dec 2005 10:01:08 -0700 X-Mailer: Internet Mail Service (5.5.2653.19) Title: Inconsistent use of the term "Facility or Facilities" Problem: In chapter 4, Facility is defined to be, "An environment providing a realization of certain functionality through set of well defined interfaces." Subsequently, in chapter 9, the SWRADIO PIM components (5 Facilities) are defined not referring to "environments", but refer to "set of interfaces", "set of services", and for the last three, functional definitions. These "facility" definitions are confusing, and need to be worded to reflect consistent ideas. Proposed Solution: The ultimate solution would be to refactor the specification to reflect the standard definitions provided in the OMAG (http://www.omg.org/docs/ab/97-05-05.pdf ) - upon which the MDA ( and its current terminologies) was guided. Shy of that, redo the definitions of "facility" in chapter 4, and change the facilities as defined in chapter 9 to consistently reflect the following definitions. In summary there are four classifications of object interfaces: * Object Services are interfaces for general services that are likely to be used in any program based on distributed objects. * Common Facilities are interfaces for horizontal end-user-oriented facilities applicable to most application domains. * Domain Interfaces are application domain-specific interfaces. * Application Interfaces are non-standardized application-specific interfaces. Rationale: This change will clarify the intent of a facility in the SWRadio specification, and make it consistent with standard OMG-speak.