| The process for submitting Phase 0 requirements is described below. Note
that Cathy Foley is no longer the product management contact for VMS
DECwindows: you should contact Paul (STAR::) Steeves instead. Also, Peter
George is no longer the project leader contact: you should contact Vince
(STAR::) Orgovan instead.
+-------------+
| | | | | | | |
|d|i|g|i|t|a|l| I N T E R O F F I C E M E M O R A N D U M
| | | | | | | |
+-------------+
TO: DECwindows Interest List DATE: November 21, 1988
FROM: Cathy Foley
DEPT: VMS Product Management
LOC/MAIL STOP: ZKO3-4/T61
CC: Peter George DTN: 381-1536
Paul Steeves NET ADDRESS: STAR::
Steve Marchesano
Vivek Marya
SUBJECT: VMS DECwindows Post V1.0 Input Requested
VMS Product Management is requesting your input on product and market
requirements for subsequent releases of VMS DECwindows software. To ensure
that your requirements are considered in the review process, your input
must be received no later than Friday, December 2, 1988. Please use the
attached form to submit your product requirement input and send it to
STAR::FOLEY
Your input is requested on all software and applications that are bundled
with the VMS DECwindows offering. This includes the Out of the Box
applications.
If you have questions, please send mail to STAR::FOLEY and STAR::GEORGE.
VMS DECwindows (Version 1.n) Platform Requirements Input Form
1. Submittor:
2. Designated Responsible Individual:
DTN:
Node:
Loc/Mail Stop:
Position:
3. Engineering or Marketing Group Supporting Requirements Request:
Include name and brief description of group.
4. Abstract:
Include brief, single-paragraph, description of each requirement.
5. Description:
Include detailed description of each requirement and an indication
of what you hope to achieve.
6. Schedule:
Note any schedule concerns for dependent products. You should
also note whether you believe that the noted feature/function
should be provided in the next release or in a release that would
follow that.
7. Benefit:
Description of benefit, including substantiating data.
8. Impact of Not Meeting Request:
Describe impact to DEC if request is turned down. Please explain
this in terms of lost opportunities and markets.
9. Justification:
Include here any other reasons for doing.
10. Rating:
To be provided by Designated Responsible Individual.
Ratings can be numerical ranking (1, 2, 3, and so on) or evenly
spread across total list (as top 25%, middle 50%, and low 25%).
Please indicate indicate whether requirement is desirable,
required, or critical. If more than one requirement is given,
please state the relative priority of each.
11. Known Issues:
Include statement of risks to either schedule or content.
12. Support Documents:
Identify any documents that add detail to the request.
|