Conference turris::languages

279.0. "DECtrace V2.0 requirements requested" by OOTOOL::OCONNELL (Mike) Tue Jun 19 1990 23:14

          <<< DBTOOL::$255$DUA25:[NOTES$LIBRARY]DECTRACE_V10.NOTE;1 >>>
                     -< DECtrace for VMS V1.0 conference >-
================================================================================
Note 13.0             DECtrace V2.0 Requirements requested            No replies
OOTOOL::OCONNELL "Mike"                             148 lines  19-JUN-1990 22:09
--------------------------------------------------------------------------------
+-------------+
| | | | | | | |
|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:	DECtrace Interest List		Date:  June 16, 1990
					From:  Mike O'Connell
					Dept:  DBS Product Management
					Ext:   264-6103
					Loc/Mail Stop:  NUO1-1/C11
					Email: OOTOOL::OCONNELL


Subject:  DECtrace V2.0 Requirements Requested

DECtrace is a VMS layered product used to collect and log event and performance
information from layered applications and products.  This information can be
used for purposes such as: 

	o application benchmarking
	o database tuning
	o ACMS application tuning
	o capacity planning
	o error logging
	o and more . . .

    We are currently gathering requirements for DECtrace V2.0.  Below are
    outlined some of the defined requirements for V2.0 for your
    convenience.  Please use the form at the end of this memo to submit
    your new requirements to Mike O'Connell on OOTOOL::OCONNELL.  If
    you have questions please call me at 264-6103 (603) 884-6103.


DECtrace V2.0
-------------

DECtrace V2.0 is targeted for FRS in Q2FY92.  The theme for DECtrace V2.0 is
support for distributed databases and applications.  Goals identified to date
are: 

Gets:

	o Support for DECdtm event collection.  This will provide the ability
	  to relate events collected from database products which are
	  implemented with 2-phase commit support, back to the related global
	  transaction events contained within the DECdtm software.

	o Support for distributed tracing (debugging) support, which allows 
	  tracing of events across multiple nodes in a network.
	  
	o Distributed control of collections across multiple nodes in a
	  network.

	o Transparent support for CMA or PPL multi-thread server environments.

	o EMA compliance

	o Formatting data into a distributed database.

	o OSF Ultrix and Ultrix advanced development.

	o Make DECtrace event data available for use by on-line performance
	  monitors built by customers or other groups.

Might Gets:

	o Produce DDIF files for reports

	o Provide C2 level security

Our Phase 0 schedule is:

	January 30, 1990	Open Phase 0
	March 30th, 1990	Close requirements gathering
	April 13th, 1990	Publish V1.1 Phase 0 documents
	June 18th, 1990		Close Phase 0 V1.1 
	July			Publish V2.0 Phase 0 documents
	July			Close Phase 0 V2.0	


	    		DECtrace V2.0


		Product Requirements Input Form

1.   Submitter:
	DTN:
	Node:
	Loc/MS:
	Position:

2.   Group supporting requirements request:

     Include group and project (if applicable) name and brief description of 
     project

3.   Abstract:

     Which DECtrace version:  V1.1  or   V2.0

     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.

8.   Justification:

     Include any other reasons for including this request.

9.   Rating:

     Rate the importance of including the requirement using the
     following scale.  A rating of 1 - ESSENTIAL means that the
     the product should not ship without it so be sure to provide
     adequate justification.

	1 - ESSENTIAL    2 - IMPORTANT    3 - 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.