Technical Test and Evaluation

Technical Test and Evaluation

 Up one level
Diagram of Sub-process
Name: Developer Validation of Test Data Object notes: An email or document stating the developer has looked at the test dataset and job structure and is satisfied with them. Name: Model Software Structure Analysis Object notes: This is confirmation that the production analyst has looked at the scripts and the design of them to insure they fit within the standard of production. This analysis may point out changes to the design the analyst has suggested to make it more production reliable. Name: Notification of Test Data Available Object notes: This is an email notification to the NCO Branch Chiefs that a set of test data is ready to be evaluated. This email will list the location of the test data. Name: Technical Analysis of Results Object notes: This is an overall review of the technical testing which weighs the pros and cons of the implementation. This review will be used as a source of information in the overall analysis of the technical, science and customer evaluation. This analysis should include an executive summary. Name: Analyze Model Source/Script Structure Name: Generate Working Test Job Structure Name: Structure Meets Standards Name: Generate Test Run Data Name: Test Setup Correctly Name: Validation of Test Output by Developer Name: Perform Technical Analysis of Results Name: Consult With Developer Name: Production Test Jobs Setup Object notes: This is the setup of SMS and job scripts, parms and executables in the production test area. Name: Production Test Data Set Object notes: The test datasets generated by the production test runs. These test datasets will be used to assist other stakeholders in evaluating the implemenation. Name: NCO PMB Analyst Name: NCO PMB Analyst Name: NCO PMB Analyst Name: Developer Name: Notify NCO Branches Test Data Available Name: NCO PMB Analyst Name: NCO PMB Analyst Name: Developer Name: Output Name: Input Name: Conditional Flow Name: Conditional Flow Name: Output Name: Conditional Flow Name: Conditional Flow Name: Output Name: Input Name: Output Name: Input Name: Flow Name: Output Name: Input Name: Conditional Flow Name: Conditional Flow Name: Responsibility Name: Responsibility Name: Responsibility Name: Responsibility Name: Responsibility Name: Output Name: Conditional Flow Name: Conditional Flow Name: Input Name: Input Name: Conditional Flow Name: Conditional Flow Name: Output Name: Output Name: Input Name: Input Name: Output Name: Input Name: Responsibility Name: Responsibility Name: Model Data Requirements Analysis Package Object notes: This analysis verifies whether the implementation will have an appropriate amount of disk space available on the supercomputer and the downstream NCEP servers. This analysis also verifies if NCEP has the appropriate amount of bandwidth to the remote centers. Name: Product Format & Content Analysis Package Object notes: This analysis verifies whether the implementation performs correctly inside NCEPs main infrastructure software applications. Name: Production Resource & Schedule Impact Analysis Package Object notes: This package validates whether the implementation is stable enough computationally and that it fits into its specified production time window. Name: Analyze Data Requirements Name: Analyze Product Content Name: Analysis of Production Resources & Schedule [Technical Test and Evaluation]


 Process Model Summary


Occurrence modified: 01/29/2003 11:32:51
Object modified: 02/26/2003 15:48:48

This document was created using Process Sourcerer ® .
Process Sourcerer is a registered trademark of Electronic Data Systems Corporation.