>If it hasn't already been posted, here is the summary information from the >>current SHARE requirement process that I think is relevant:
>"Welcome to the SHARE Requirements system. >Policy 15: SHARE is not meant to be a vehicle whereby providers of >>information technology strategies, architectures, products or services >>obtain information about the activities of competitors. Using such >>information obtained through participation in SHARE Activities is contrary >>to the purposes of SHARE and is not permitted. >Use of this system implies an assertion that you and your Installation have >>no conflict of interest with the products for which improvements and >>enhancements are being requested. " >This summary (and policy 15 itself) haven't changed in years as far as I >know. This is out of date. Policy IND-1 is current. REF # IND-001; 08/12/2006 POLICY IND-1 SHARE REQUIREMENTS POLICY: It is the policy of SHARE that Requirements are the joint property of SHARE and the provider of information technology strategies, architectures, products or services to whom they are directed. They are only to be used for SHARE purposes, as authorized by the Board of Directors. Specifically authorized uses include use within SHARE Activities, use within the provider as required for generating and monitoring responses, and as a key element of the SHARE/provider dialogue. To protect this dialogue, unauthorized dissemination of Requirements is not permitted. PURPOSE: The SHARE Requirements process is a vehicle through which SHARE Members can provide statements to providers describing a business need related to the provider's product(s) or service(s) that is not currently met. This policy is intended to establish the ownership of SHARE Requirements, the authority of SHARE with regard to these requirements and expectations of participants in the SHARE Requirements process. PROCEDURE: 1.1 Definition The requirements process consists of all SHARE Activities, including, but not limited to, meetings, electronic conferences, newsletters and databases, in which requirements for information technology strategies, architectures, products or services are discussed, formulated, voted upon, or addressed in any manner, in written, oral or electronic form. 1.2 Participation in the requirements process 1. SHARE is not meant to be a vehicle whereby providers of information technology strategies, architectures, products or services obtain information about the activities of competitors. 2. Using such information obtained through participation in SHARE Activities is contrary to the purposes of SHARE and is not permitted. 3. Upon mutual agreement between SHARE and a particular provider, one or more activities of the requirements process for that provider may be closed to other providers. 1.3 Compliance It is the responsibility of each individual participating in a SHARE requirements process to determine whether participation in any particular requirements process would violate this policy and, if so, to not participate. Any individual involved in a requirements process should immediately notify the initiator of that process upon becoming aware of an apparent violation of this policy. The initiator of that process shall take whatever steps are necessary to ensure compliance and shall notify the Secretary of any violation of this policy. Finally, IMO this discussion is idiotic. One person doesn't like the process. I agree with Patrick O'Keefe: if it doesn't work for you start your own process. Bob Shannon Rocket Software ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
