1 / 13

SWRadio FTF & SBC DTF Joint Meeting

SWRadio FTF & SBC DTF Joint Meeting. June 23 rd 2004. Agenda Items. FTF Overview Deadlines, Requirements, Process Issues D&C Alignment Implementation Discussion. FTF Overview.

kylee-vang
Download Presentation

SWRadio FTF & SBC DTF Joint Meeting

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SWRadio FTF & SBC DTFJoint Meeting June 23rd 2004

  2. Agenda Items • FTF Overview • Deadlines, Requirements, Process • Issues • D&C Alignment • Implementation Discussion

  3. FTF Overview • An F/RTF is chartered by the appropriate TC to gather comments on a particular specification from OMG Members and others, and to decide whether changes are necessary in response to those comments. An F/RTF may recommend changes that provide clarification of the wording without changing its intent, or minor revisions that correct the detail of the specification without adding or removing significant functionality. Enhancements to the specification are outside the scope of the F/RTF, and must be deferred to a later RFP process (see section 4.2). P&P 2.2 § 4.4.1.1

  4. FTF Overview • FTF handles first post-adoption revision • Includes clean-up for publication • Turns “Adopted” submission into “available” specification • FTFs and RTFs respond to “Issues” submitted to OMG • Can come from anyone (including FTF/RTF members) • FTF/RTF members should file issues in the same way as non-members, so resolutions can be tracked

  5. Raising Issues • Via the OMG web page (preferred) or email to issues@omg.org • http://www.omg.org/technology/agreement.htm • Juergen will manually assign the incoming issue to RTF/FTF, file it on issues page and email it to your RTF/FTF mailing list • When you discuss the issue, please preserve the issue number in the email subject • This helps Juergen when he copies the email thread back on to the Issues web page

  6. Voting • Votes Taken by email • Meetings, email discussions and teleconferences are open to all OMG representatives (just like any OMG subgroup) • Simple Majority Voting

  7. Delinquent Members • Non-participants are automatically ejected • A Representative on the F/RTF who fails to vote in a contiguous sequence of at least two polls that complete during a period of at least two weeks is automatically removed from the F/RTF. A proxy vote or a vote of abstain is considered a vote for this purpose. P&P 2.2 § 4.4.1.3

  8. Members: Tansu Demirbilek (Chair), Mercury David Fitkin, Rockwell Collins Dominick Paniscotti, BAE Systems Jerry Bickle, Raytheon Kevin Richardson, Mitre Manfred Koethe, 88solutions Francis Bordeleau, Zeligsoft Mark Scoville, L-3 Communications, CSW Phil Eyermann, ITT Aerospace/Communications Camille Bell, Blue Collar Neli Hayes (Chair), Boeing Francois-Xavier Lebas, Thales France Jean Belzile, ETS (to be removed) Mike Gudaitis, L-3 Communications, GSI David K. Murotake, SCA Technica Victor Giddings, Objective Interface Systems Geoff Holt, Spectrum Signal (to be added) SWRadio FTF Members

  9. Final Adopted Specification: dtc-04-05-04 (also available at ftp://ftp.omg.org/pub/swradio) Deadlines: Final Adopted Specification Publication: July 1 2004 Comments Due: 1 Feb 2005 Recommendations and Report Deadline: 22 April 2005 (One week after the OMG meeting) SWRadio FTF Deadline

  10. Issues • Specify which interfaces are mandatory, and which ports are required for components • Comm channel data descriptors need to be defined in the annex (currently TBD) • Physical layer TBD needs to be fixed in the annex • A provided port can have multiple interfaces -> an additional parameter needs to be added to the getPort operation? • Is there a need to have a getPorts operation? • disconnectPort operation at the resource level port does not have a requiredPort attribute. • Abstract data types for interface attributes and refer to those in the facility descriptions.

  11. Issues • Start/stop behavior: what is the association? • Check “shall” & “may” statements • Mapping of UML Profile Infrastructure elements to M1 level. Better mapping needed. • OCL Statements for constraints needed • IDL Namespace issue (circular dependency) • Break the spec into multiple volumes

  12. Action Items • Jerry: • Generate a document for node manager requirements, for D&C alignment • Group: • Raise issues!! • Database/White Paper on differences between SCA and SWRadio, and possible migration paths

  13. Implementation Discussion • What’s the implementation requirement for APIs? • Which parties are interested in implementation?

More Related