Date: 8/29/2000 Requirement #: WAVV200013
Title : Elimination of POWER Queue
Reformat During Release Upgrades
(Short description of what you want the
product changed to - include keywords like function, short product name)
Statement of
the Problem : (What? Detailed description of what you want
changed, 400 char.limit)
End the requirement that
POWER queues be reformatted every time a new release
of VSE is made available.
Benefit : (Why? Non-technical business
case description, i.e a business case. Do not reword problem statement
above. How do you to justify the needed
change? Wwill itrequest
benefit the submitter’s your company, and the vendor
and others? Business case
and benefits to users and vendor which can to justify
the needed change?. Quantify: run time, dollars, manpower, etc. Also, wWhy
should is it important
for vendor to want to do this for their
customer?s)
VSE sites with robust printing requirements
(500 pages/min or more, 3+ volumes of 3390-3) face horrendous scheduling and
capacity problems every time a POWER queue reformat is required. Many hours of DEDICATED system time could be
saved, both in the actual reformatting of the data file as well as in the
backup of the queue file from the previous release and its restoration to the
new release.
Date : (When? ASAP, 6 months, one year from now, etc)
ASAP
Impact : (How? How will your company’s business be
affected if a solution is not
delivered.)
In worst case,
foregoing needed upgrade for up to 6 months
(until busy season ends).
Solution : (optional desired / undesired elements Note: suggest can limit vendor ability to deliver a solution)
Classification : (Suggestion=Nice Idea, Long
Range=Future, Tactical=ASAP, or Acceptability=I won’t buy the product
or will drop the product if solution not provided)
tactical
Company Name: Dickinson
Direct
Author Name: Lance
H. Vaughan Author Title: Senior Systems Programmer
Author
Address: 120 Campanelli Drive
Braintree MA 02184
Author E-mail: lance@dickinson.com
Telephone: (781) 849-3700
X674
·
Please
be precise and short.
·
The
Benefit section is extremely important – please make a business case.
·
Proofread
- recheck accuracy of contact information before saving.
·
File
as unique name-WRvviinn, where vv=vendor initials, ii=your initial, ‘nn’ to number each requirement.
Ex.: Wribwm01 ib=IBM, wm=wayne mery
·
Submit
your labeled diskette (with your full name) to the requirements coordinator, a
black shirt WAVV manager, the registration desk or copy it to the root drive of
a registration or workroom PC.
* [IR1]