Conference csc32::consolemanager

234.0. "V1.2 requirements/request form" by ZENDIA::DBIGELOW (Innovate, Integrate, Evaporate) Sun Apr 03 1994 23:29

    *********************
    * * D I G I T A L * *			INTEROFFICE MEMORANDUM
    *********************
   
    To: VMS Interest List			Date:	1-April-1994
        UNIX Interest List     			From:   Ann Dinneen
						Dept:	DSM
						DTN :	227-3736
						LOC/MS:	TAY2-2/B04
						Enet:	TOOK::DINNEEN


    Subject:  POLYCENTER Console Manager V1.2 - Phase 0 Opening


    I am pleased to announce the opening of Phase 0 for POLYCENTER 
    Console Manager V1.2.

    POLYCENTER Console Manager V1.1, soon to ship from the ESSB, is 
    a layered product that centralizes communication and control of
    globally distributed multivendor environments.  This product expands
    the concepts of a network data center, which may span a floor,
    a building, a city, a country, or even a continent.  It is available 
    on RISC ULTRIX, DEC OSF/1 AXP, OpenVMS VAX, and OpenVMS AXP platforms,
    and can manage any system or device that can send ASCII data over
    an RS232C line, has an EIA console port, and supports XON/XOFF 
    and I/O buffering.

    PRODUCT GOALS
    -------------

    The goal of POLYCENTER Console Manager V1.2 is to expand upon the 
    existing capability of V1.1.  The V1.2 product is intended to:

    - enhance existing features and functionality of V1.1

    - extend the product offerings by providing the ability to manage
      additional software platforms such as Windows/NT.

    - integrate with platforms such as POLYCENTER Manager on NetView.

    - and of course, include bug fixes. 


     A Product Requirements Input Form is attached to this memo for your 
     use in submitting requirements.   Please return your completed 
     form to:   TOOK::DINNEEN 
		no later than April 30, 1994.
     
     Please be as specific as possible in defining your requirements, and 
     when appropriate, provide as much justification as you can for their 
     inclusion in POLYCENTER Console Manager.  

     Although all requirements are welcome, time and resource constraints
     will force us to prioritize each requirement.  All outstanding 
     requirements will be reviewed for inclusion in the next release.  
     Additionally, I welcome your nominations for both internal and external 
     field test candidates.
  





                       POLYCENTER Console Manager V1.2

                       Product Requirements Input Form


    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

    Directions:
    ----------

    Please complete this form by providing all requested information.
    Submit the completed form to TOOK::DINNEEN no later than April 30, 
    1994 to ensure consideration of your requirements during 
    POLYCENTER Console Manager V1.2 Phase 0.

    =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=


    1.  Submittor:

        DTN:
        Node:
        Loc/MS:
        Position:

    2.  Customer, Engineering or Support Group issuing request:

        Include name and brief description of group.

    3.  Abstract:

        Include brief, single-paragraph description of requirement.

    4.  Description:

        Include detailed description of requirement and an indication of
        expected result if requirement is included.

    5.  Schedule:

        Note any schedule concerns caused by products on which this
        requirement would be dependent.  Include availability dates for
        specifications, prototypes, field tests, and FRS when appropriate.

    6.  Benefit:

        Description of benefit, including substantiating data.

    7.  Impact of not meeting request:

        Describe impact to Digital if request is turned down.  Please
        explain this in terms of lost opportunities and markets.



                                                                   Page 2 

    8.  Justification:

        Include here any other reasons for including this request.

    9.  Rating:

        Rate the importance of including the requirement using the
        following scale:

        1 - ESSENTIAL        3 - IMPORTANT        5 - DESIRABLE

    10. Known issues:

        Include statement of risks to either schedule or content.

    11. Support documents:

        Identify any documents that add detail to the request.