Thanks Rob. And the shotgun method never hurt either. Good advice.
Michael Crump
Manager, Computing Services
Saint-Gobain Containers, Inc.
1509 S. Macedonia Ave.
Muncie, IN 47302
765.741.7696
765.741.7012 f
This email and its attachments may be confidential and are intended
solely for the use of the individual to whom it is addressed. Any views
or opinions expressed are solely those of the author and do not
necessarily represent those of Saint-Gobain. <redaction>. If you are
not the intended recipient of this email and its attachments, you must
take no action based upon them, nor must you copy or show them to
anyone. Please contact the sender if you believe you have received this
email in error.
Tradition
Just because you've always done it that way doesn't mean it's not
incredibly stupid.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, May 07, 2008 9:52 AM
To: Midrange Systems Technical Discussion
Subject: RE: IBM investment in i
The Request for Design Change (or DCR) process at
https://www-912.ibm.com/r_dir/ReqDesChange.nsf/Request_for_Design_Change
?OpenForm
is a good method. If you want to put "weight" behind it, then have
multiple people submit the same request.
COMMON is good. And they've done a fine effort lately of stressing
requirements. They did fall by the wayside for awhile but COMMON is
definitely putting shove back into it. My only problem with doing it
that
way is once I had a requirements coordinator totally reword my request
into something else. Granted, that was a decade or so ago. I submit
DCR's online for the same reasons that I submit PMR's online - so that I
get my wording in and not just what an operator or someone else hears
and
types in.
Hey, do both. Peace - through superior firepower.
Rob Berendt
midrange.com
