Conference ulysse::rdb_vms_competition

1167.0. "SQL/Services Extended Kit - Phase 0 Open" by WILBRY::WASSERMAN (Deb Wasserman, DTN 264-1863) Thu Jun 25 1992 16:19

+---------------------------+ TM
|   |   |   |   |   |   |   |
| d | i | g | i | t | a | l |
|   |   |   |   |   |   |   |
+---------------------------+


To: DISTRIBUTION		      DATE: 18 June 1992
    				      FROM: Deb Wasserman
				      DEPT: Database Product Management
 				      LOC:  NUO1-1/C11
    				      DTN:  264-1863
    			      	      ENET: WILBRY::WASSERMAN


Subject:  SQL/Services Extended Kit V1.0 - Opening of Phase 0


The purpose of this memo is to announce the opening of Phase 0 for the
SQL/Services Extended Kit V1.0.  As implied by the name, this product
extends the functionality offered by the SQL/Services base kit in 
terms of additional client and network transport support.

Our current goal is to close Phase 0 on August 18th, 1992.  Please submit
your requirements on the attached Product Requirements Input Form, and
send it to me at WILBRY::WASSERMAN no later than August 4, 1992.


PRODUCT DESCRIPTION

SQL/Services provides remote access to Rdb/VMS and RdbAccess databases
from various desktop client platforms over DECnet and TCP/IP network 
transports.  SQL/Services base functionality is a component of Rdb/VMS.  
It is shipped and documented as part of the Rdb/VMS development kit.  

The purpose of the SQL/Services Extended Kit is to build upon the
base product by offering similar functionality from such possible
platforms as Visual Basic, Borland C++, WATCOM C, SCO Unix, HP,
Windows NT, and over networks such as Multinet and Novell.


SCHEDULE

Our preliminary schedule is:

	June 18, 1992	Open Phase 0
	August 18, 1992	Close Phase 0
	10/92		Close Phase 1
	11/92		Close Phase 2
	 1/93		Close Phase 3
	 1/93		Submit to SSB
	 2/93		FRS

If you would like to discuss the requirements, please feel free to 
call me at 264-1863.  If you would like to be removed from this
distribution list, or know someone who would like to be added, let
me know.


                        SQL/Services Extended Kit V1.0

                       Product Requirements Input Form

       (Send Input to WILBRY::WASSERMAN no later than August 4, 1992)
                


1.  Submittor:

    DTN:
    Node:
    Loc/MS:
    Position:

2.  Engineering or Support Group issuing requirements 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, protos, 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.

8.  Justification:

    Include here any other reasons for including this request.

                                                                Page 2


9.  Rating:

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

        1 - ESSENTIAL        2 - IMPORTANT        3 - DESIRABLE

     o  ESSENTIAL = This product should not be shipped without this feature.   
	It is a critical feature that, if it were missing, would cause 
	most customers not to purchase the product and would cause major 
	damage to customers' perception of Digital's database strategies.

     o  IMPORTANT = This product should include this feature unless its   
	inclusion would jeopardize the time-to-market goals.  The lack  
	of this feature may cause certain customers not to purchase the
	product, either because it is a feature that is available and 
	used often in current products or it is a feature they have 
	requested for a long time.  This feature should be included  
	no later than Version 1.1.

     o  DESIRABLE = Desirable features will be considered for this product.


10.  Known issues:

    Include statement of risks to either schedule or content.

11.  Support documents:

    Identify any documents that add detail to the request.