Analysis
The process to initiate and complete the APIS validation project is defined below.

2.1 Gather detailed specifications and definitions

• All MMF1 database columns must be mapped or otherwise deemed unneccessary and thus ignored.
• Determine the best format to store the APIS translation definitions in.
• For each column determine the computer readable details needed to implement the translation (this is based on the spreadsheet which contains the mappings) using the above APIS translation definitions.
• Determine the best method to store the APIS translation definition
• Determine an appropriate naming scheme for the clob files, status report files, and intake files.

2.2 Programming Tools & Techniques

• Programming Language: Perl
• Database: DB2
• OS: Solaris
• The application will be written in perl in a Solaris 8 (UNIX) environment. The Data files are plain text and will be parsed and validated using the perl scripts written.

2.3 Deliverables

• Data Collection - Work flow diagrams, spreadsheet that describes the translations neccessary to move the contents of MMF1 to MMF2
• Diagram of the workflow for the APIS Translator application
• Finalize a naming scheme for the clob files, status report files, and intake files.
• Development code ready for QA
• Application code ready for production