OMG Process Help PageThe intent of this page is to provide links to some useful resources that help OMG members conduct OMG business. The information pertains to subgroup chair responsibilities, the technology adoption process, chartering subgroups, documents and communication. Some of the specific topics covered include:
The Ultimate SourcesThe ultimate sources are, of course, OMG's web site and the Policies and Procedures of the OMG Technical Process (affectionately known as P&P). Chair ResponsibilitiesA "few nuggets of hard-won wisdom", authored by OMG VP and Technical Director Andrew Watson, are available in presentation format as OMG document omg/2000-01-04. An additional resource for FTF and RTF chairs can be found in presentation format as OMG document omg/2007-12-01. A quick reference to chairing meetings is the vade mecum (produced by our resident Latin scholar). For those so inclined, there is a publicly-available electronic copy of Robert's Rules of Order. (The 11th edition of Robert's is available in your favorite bookstore.) Meeting PlanningChairs are requested to provide the OMG with meeting room requirements for each meeting. A form requesting such is available. Chairs must also provide a meeting agenda to the OMG no later than two weeks before the start of a TC Meeting. Agendas should be posted to agendas@omg.org, which ensures that they will be posted on the OMG Technical Meeting Agendas Page. ProxiesConfused about proxies? Click here to learn more. Reporting Meeting ActivityIt is the responsibility of a chair to report his or her group's activity during the week of an OMG Technical Meeting at the appropriate plenary meeting on Friday. A form is available for reporting group activity. This reporting form can be accessed with explanations or without explanations. OMG Technology Adoption ProcessThe OMG Hitchhiker's Guide serves an aid to navigating through and complying with the OMG technology adoption process. While the guide was written with those responsible for shepherding the process in mind, it provides a useful interpretive tool for anyone wishing to understand the process better. Architecture Board HelpEvery year after the main AB elections AB members are allocated to liaison roles with the active Task Forces, SIGs and Subcommittees. This is an informal relationship to ensure that there's an AB member to whom members of the group can turn for AB-related advice. If there's a bye-election during the year, the new holder of the seat takes on the previous occupant's liaison duties. New groups are allocated liaisons (also known as "buddies") after the next AB election. These liaison assignments can be found here TC Meeting and Work in Progress InformationA reference page is available for information on future and past Technology Committee meetings and Technology Committee work in progress. RFPs and RFP SubmissionsA template for RFPs is available on the OMG document server. An abbreviated version is available for distribution for AB and Task Force review only. Draft RFPs should be sent electronically to omg-documents@omg.org. RFP submissions must be mailed to the OMG. The correct mailing address must be specified in the RFP. A checklist of guidelines to help navigation through the RFP process can be found here. Several years ago, OMG decided to submit the majority of its specifications to ISO to become ISO standards using either ISO JTC1’s PAS process or ISO’s Fast-Track. For a specification from OMG to become an ISO standard, it is highly desirable that it be in a format closely approximating the ISO format. (If it is not in an ISO-like format when the standard comes up for its five year review in ISO, it will be withdrawn). Two templates in regular FrameMaker format and FrameMaker MIF format are available for formatting submissions in the ISO PAS format. RFIs and RFI ResponsesA template for RFIs is available on the OMG document server. Draft RFIs should be sent electronically to omg-documents@omg.org. RFI responses must be mailed to the OMG. The correct mailing address must be specified in the RFI. Business Committee Requirements and QuestionnaireAlthough not the responsibility of the issuing Task Force, submitters often inquire about two OMG Business Committee (BC) documents related to RFP submissions. The first is the Business Committee RFP Attachment, which identifies the criteria the BC uses when evaluating submissions. This document is included in the RFP template (see above). The second is the Business Committee Questionnaire, which accompanies a RFP submission and is a statement by a submitter of their intention to provide a commercially-available implementation of the adopted specification. Evaluating RFP SubmissionsGuidelines are available to assist Task Forces in forming the work groups (called evaluation teams) that are tasked with evaluating RFP submissions issued by the Task Force and to assist these teams in performing those evaluations. Vote-to-VoteBy policy, neither a Task Force nor Technology Committee can vote to recommend a Revised Submission until at least the second OMG meeting following the due date of the final Revised Submission. However, a vote to recommend at the meeting immediately following this due date may occur provided that the following conditions are met:
Normally, a Task Force will wait a meeting cycle before engaging in the vote to recommend in order to adequately digest the submission(s). The intent of the Vote-to-Vote, which is the exception, is to accelerate the adoption process when “time to market” for the specification is a critical factor. The Task Force must weigh this criticality against the quality of the proposed specification. FTF and RTF Final ReportsClick here for a template for FTF and RTF final reports. Other Forms and TemplatesA useful resource for acquiring templates and forms used in various technology adoption processes can be found on the Template Downloads page. Chartering SubgroupsIt is the responsibility of a nominated chair organizing a Task Force, Special Interest Group, Subcommittee, Finalization Task Force (FTF) or Revision Task Force (RTF) to make a motion to charter the subgroup at the appropriate plenary meeting on the Friday of a OMG Technical Meeting. Forms are available to assist in making such a motion:
CommunicationsThe two major means of communications among OMG members and with industry at large are:
Mail ListsSome of the more widely used mail lists and their intent include:
Mail list subscription / un-subscription is handled by sending email to request@omg.org. Individual EmailOMG members and staff with electronic mail access may be reached by sending email to FIRSTNAME_LASTNAME@omg.org. Subgroup Chairs may be contacted by appending "-chair" to the subgroup's email list name. Email requests to OMG staff is an effective (and, in some cases, required) means of conducting business. Some of the more widely used addresses and their intent include:
OMG DocumentsA few, quick notes about accessing OMG documents. OMG documents are identified by a document number, which takes the form prefix/yyyy-mm-nn, where:
For example, the Business Rules in Models RFI is assigned document number ad/2002-09-13. This means that the issuing group was the Analysis and Design PTF ("ad"); the document was issued September ("09"), 2002; and it was the thirteenth document that A&D PTF issued that month. For a complete listing of subgroup prefixes, consult the OMG TC White Pages. Search engines are available to locate OMG documents, providing access either to all documents available on the document server (Members only) or to those which are publicly-available. A complete list of all available OMG documents, updated daily, can be obtained as a text list (WARNING: extremely lengthy.) Finally, OMG documents may be accessed via URL. To form the correct URL, append the document prefix and number to "http://doc.omg.org/" For example, http://doc.omg.org/ad/2002-09-13 for the example above. This will direct you to a page with links to a choice of formats for the document (e.g. PDF, Word, Zip, etc). Remember that some documents may be not be accessible to non-members. OMG SpecificationsA Catalog of OMG Specifications exists on the OMG web site for accessing recently adopted and formal (publicly available) specifications. The OMG Technical Editor, in collaboration with the Specification Management Subcommittee, determines a release schedule for new specifications. Last updated on
April 27, 2009 by Fred |
||||||||||||||||||||||
|
Copyright © 1997-2010 Object Management Group, Inc. All Rights
Reserved. For questions about the WEBSITE , please contact webmaster@omg.org. For TECHNICAL questions, please contact webtech@omg.org. This site is best viewed with Netscape Navigator, Mozilla Firefox or Internet Explorer versions 6.0 or later or any browser capable of viewing JavaScript and CSS 2.0. The site is using DHTML JavaScript Menu By Milonic.com. |