[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

1452.0. "Call for V3 Phase 0 requirements " by STAR::STEEVES (Go Mondo Balto!) Fri Sep 15 1989 18:34

+---------------+
! 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:  List                               Date:       Sept 15
                                        From:       Paul Steeves
                                        Dept:       VMS Product Mgmt
                                        Ext :       381-1621
                                        Mail Stop:  ZK3-4/T61
                                        DECnet:     STAR::STEEVES
Subject: Call for Phase 0 requirements  

This is the official call for:

            VMS DECwindows Version 3
             Phase 0 requirements

Please use the following form to make requests.
Send mail to STAR::STEEVES --- Do NOT reply to this note.
The deadline for submitting requests is Oct 1.

Once the requirements are compiled, we will
make them public and announce the Phase 0
review date and location.
*************************************************


Phase 0 Requirement Template

1) Submitor (person/group making the request)

2) Abstract (short description of request)

3) Description (detailed description of request)

4) Schedule
        Specification available (as much detail as is appropiate)
        Proto Available 
        Test schedule
        Planned FCS

5) Benefit (short statement of benefit with substantiating data)

6) Impact of not meeting request (impact to DEC if request is turned down)

7) Justification (any other reason for doing)

8) Submittor's rating (desirable, required, or critical)

9) Known issues (statement of risk either to schedule or content)

10) Support documents (any documents that add detail to the request)



An example VMS Phase 0 requirement:


                  (Fictitious example)

                VMS Phase 0 Requirement


Submittor:  Ray Riddick
            Product Manager CDrom

Abstract:   VMS Support of the CDROM controller and laser disk as a
            bootable device and a supported software distribution media
            on all VAX Processors

Description: VMS should support the laser disk controller as a bootable
            MSCP device on all unibus, q-Bus, and BI VAXen. In addition VMS
            should support this technology as a distribution media for
            VMS and layered product software and documentation. All data
            distributed on laser disks will be encrypted.  A key will be
            provided by SPS to those under contract for specific products.
            Distribution of the laser disk will be quarterly and will
            require a "remastering" of VMS for each distribution.

Schedule:   Controller specification available      15-SEP-84
            Controller proto available to VMS       30-DEC-84
            First Customer test of media            20-APR-85
            FCS                                     30-JUN-85

Benefit:    There is a great finacial savings to DEC by manufacturing and
            distributing software in this manner. A summary of the financial
            impact follows (a detailed analysis is attached as addendum 1).

                                     FY86            FY87            FY88
            No CDrom                2000K           4000K           8000K

            With CDrom               600K            700K            800K

            Savings to DEC          1400K           3300K           7200K


Impact of not doing: The impact is twofold. First is the cost in equipment,
            floor space, etc as outlined in the attached financial statement.
            Second is the customer perception that DEC is insistant on arcane
            means of distribution and is not committed to improved technology
            for software distribution.

Justification:  Financial benefit as described.
                Market perception as described
                Customer ease of use    

Rating: Required (high priority for software engineering.)





Issues:     A means for coordinating layered software and VMS distribution
            must be found. A person has been chartered to work cooperatively
            with the VMS system Manager to develop a plan by 1-MAR-85 for
            software distribution.

            There is also an issue surrounding encryption to non US customers.
            This is to be resolved by the Product Manager. 

            The risk to the program for each of these items is low to moderate.

Supporting Documents:
            Project plan, buisness plan, and specification may be found in
            ajax::wrkd$:[riddick.cdrom]*.*;*



T.RTitleUserPersonal
Name
DateLines