Preliminary
UN/EDIFACT ORDERS Message
Implementation and Test Plan

for the

DOD CALS IDE Project

March 1998

In support of
Contract DASW01-97-D-0006

TABLE OF CONTENTS

LIST OF FIGURES
LIST OF TABLES
1.0  INTRODUCTION

1.1  Overview and Background
1.2  Approach

2.0  ARCHITECTURE FRAMEWORK MODEL FOR TESTING

2.1  Layer 1:  Application Interface:  Outbound
2.2  Layer 2:  Transaction Generation:  Outbound
2.3  Layer 3:  Network Communications:  Outbound/Inbound
2.4  Layer 4:  Transaction Interpretation:  Inbound
2.5  Layer 5:  Application Interface:  Inbound

3.0  TEST SCHEDULE

3.1  Test Planning, Scheduling, and Resources
3.2  Government Activities
3.3  Test Report
3.4  Outreach

4.0  TEST METHODOLOGY

4.1  Testing Strategy
4.2  Assumptions and Constraints
4.3  Risk Assessment

4.3.1  Risk Identification and Impact

4.3.1.1  Communications/Network
4.3.1.2  Operational
4.3.1.3  Administrative

4.3.2  Control Objectives

4.4  Test Requirements

4.4.1  Basic Functions
4.4.2  Data Format and Content

4.5  Test Results Analysis and Reporting

4.5.1  Data Analysis
4.5.2  Test Documentation

5.0  FEDORDER D.97A TEST CASES

5.1  FEDORDERS D.97A Test Case Basic Information

5.1.1  Test Objective
5.1.2  Test Requirements
5.1.3  Software Test Environment
5.1.4  Hardware Test Environment
5.1.5  Installation, testing, and control
5.1.6  Data Recording and Analysis

5.2  FEDORDERS D.97A Test Case Scenarios

5.2.1  Scenario 1:  Use ECI with translation occurring within ECI
5.2.2  Scenario 2:  Use ECI with Translation Outside of ECI
5.2.3  Scenario 3:  Bypass ECI with Local Translation

6.0  SUMMARY AND CONCLUSIONS
APPENDIX A:  GLOSSARY
APPENDIX B:  ABBREVIATIONS AND ACRONYMS

LIST OF FIGURES

Figure 1.2-1  UN/EDIFACT ORDERS Message Prototype Testing Approach
Figure 1.2-2  Business Process Requirements Assessment Methodology
Figure 2.0-1  Electronic Purchasing Testing Architecture
Figure 2.0-2  UN/EDIFACT ORDERS Message Prototype Test Suite Matrix
Figure 2.1-1  Application Interface:  Outbound
Figure 2.2-1  Transaction Generation:  Outbound
Figure 2.3-1  Network Communications:  Outbound/Inbound
Figure 2.4-1  Transaction Interpretation:  Inbound
Figure 2.5-1  Application Interface:  Inbound
Figure 4.2-1  ManTech Testing Agent DataFlow
Figure 5.2-1  Task 3 Architecture