On Nov 29, 2007, at 7:00 AM, Walt Farrell wrote:
On Thu, 29 Nov 2007 00:45:09 -0600, Ed Gould
<[EMAIL PROTECTED]> wrote:
Thanks, that is what I thought. Then it is still needed to copyright
requirements before submitting them to SHARE.
I don't understand what you think that would accomplish? Copyright
protects
the expression of an idea.
A requirement should, primarily, provide a description of a problem
you're
having for which you want a solution. I don't see what benefit a
copyright
on your description of a problem would have for you or anyone else.
Assuming you went further, and suggested an implementation, would
you really
want a copyright that might restrict IBM (or anyone else) from
implementing
your proposal? If so, why ask for a solution in the first place? Any
restriction on implementation would seem to destroy all the benefit of
having a requirements process.
Walt,
There of course is a simple solution and that is to let anyone that
is a member of SHARE have read access to the database. The reasons
are simple and yet it would benefit IBM and SHARE members alike. The
first is that so duplicate requirements might not be submitted(or at
least minimized), this would reduce IBM's man power spent working on
responding and implementing and planning of requirements. The third
or so is that people could see if their requirement has been
submitted already so duplicates should be cut down. The fourth is
that Users can see and request (through SHARE) that IBM to re-
prioritize any outstanding requirements.
The myth (as I call it) IBM responds to requirements in their own
timely manor, in reality they respond only if it fits IBM's needs.
The requirement (good ones) have a business case which should have
included cost justification. The cost (over years) might increase
significantly, so if a resubmission is needed because of costs
increase the user should be able to resubmit with different numbers
to reflect the change and this would help IBM prioritize
implementation. Although in all honesty (at least what I have seen)
if a requirement doesn't get implemented in say 5 years there is
almost no chance it will ever occur.
There are other benefits as well but the above is a start for an
impromtu response. There is also probably a revue that should be done
every few years to see if requirements are not needed or need to be
revised. This could be done by a committee (project?) at SHARE (and
with input from IBM).
Ed
----------------------------------------------------------------------
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
