Conference heron::euro_swas_ai

349.0. "DEC OPS5 V4.0 Phase 0 Announcmement." by ULYSSE::ROACH (TANSTAAFL !) Wed Jul 17 1991 10:45

 

                  I N T E R O F F I C E   M E M O R A N D U M

                                        Date:     10-Jul-1991 08:54pm CET
                                        From:     OPERATOR
                                                  OPERATOR@AIADM@SELECT@HERON@ULYSSE@MRGATE@VALMTS@VBO
                                        Dept:      
                                        Tel No:    

TO:  PATRICK ROACH@VBE


Subject: DEC OPS5 V4.0 Phase 0 Announcmement.

From:	38745::OSTROM "Knowlege Based Systems Prod. Mgmt. - 296-5150  10-Jul-1991 1258" 10-JUL-1991 12:57:22.04
To:	AIPERS::OPERATOR
CC:	
Subj:	DEC OPS5 V4.0 Phase 0 Announcmement.  Please forward to AITC.


    ----------------------------- TM
    |   |   |   |   |   |   |   |
    | d | i | g | i | t | a | l |               INTEROFFICE MEMORANDUM      
    |   |   |   |   |   |   |   |
    -----------------------------               
     


TO: OPS5 INTEREST LIST                          DATE: July 1, 1991
    VMS INTEREST LIST                           FROM: Andrew Ostrom
    ULTRIX INTEREST LIST                        DEPT: Knowledge Based Systems
                                                        Product Management
    AITC Distribution                           EXT:  296-5150
                                                LOC:  LMO2/L11
CC:                                             ENET: ANDREW::OSTROM


SUBJECT: DEC OPS5 V4.0 PHASE ZERO ANNOUNCEMENT

This  memo  announces the opening of the collection of  requirements  for
Phase Zero of DEC OPS5 V4.0.  

A preliminary copy of the Product Requirements Document will be available
on July 8, 1991 in the public directory GUESS::OPS$V40:[PHASE0].


PRODUCT DESCRIPTION:
      
VAX OPS5  is  a  powerful  tool for developing and delivering integrated,
high-performance rule-based expert  systems  under  VAX/VMS.  V3.0 of VAX
OPS5 delivered  ODE  the OPS5 Development Environment, a DECwindows based
environment for the creation of OPS5 applications.


REQUIREMENTS:

A  number   of  requirements  have  already  been  identified,  but  your
participation is needed  to  both  increase  and improve the requirements
list for Version 4.0.    Attached  is  a form which you may use to submit
your requirements.  Please use  a  separate form for each requirement and
forward the completed forms to ANDREW::OSTROM.

The major requirements identified to date include:

    o RISC/Ultrix Support
    
    o Motif Support
    
    o Enhanced integration  with other languages  through  NAS  compliant
      callback and VAX calling standard callout

    o Improvements to representational power and expressiveness
    
    o SQL Interface

    o Provide a migration path to the  next generation of Knowledge Based
      Systems development (TIN)

DEADLINE:

Please  forward all completed product requirement forms by July 15, 1991.
Please contact me if you require any additional information.


      Product Manager - Andy Ostrom, ANDREW::OSTROM
      Engineering Manager - Will Anderson, GUESS::ANDERSON
      Engineering Supervisor - Beatrice Walther, GUESS::WALTHER





                              DEC OPS5 V4.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:
         Include brief, single paragraph description of requirement.
    
    4.   Description:
         Include detailed description of requirement.
    
    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.