1. Condor Technology Solutions, Inc. Grace RFTS Application Extension Phase

2. Presentation Overview Review of RFTS Project completed Successes and Work to still be done Proposal & Requirements review for RFTS Extension Phase Meeting Agenda

3. RFTS Original Goals Business Objectives Assess and become acclimated to the current RFTS System -SUCCESS Complete Development on the new RFTS System - SUCCESS Compile Technical Documentation - SUCCESS Production Implementation - POSTPONED Critical Success Factors Preservation of historical data going back to 1985 - SUCCESS Maintain connections to “Packages” database - SUCCESS Maintain references and connections to Word documents - SUCCESS Project Review

4. RFTS Project Breakdown Prototype Modules System Arch Definition System App Design Business Component Process Definition Data Quality Create Loading Plan Code/Test SQL Code & Test Modules Create UAT Plans Standards & Procedures Create DB System Test User Acceptance Test Part 1: Evaluation of Code and Business Rules Part 2: Analysis and Data Transfer Prep. Part 3: Testing Create Test Data System Implementa tion Post- Implementa tion Part 4: Implementation Transfer Data Project Review

5. Deliverables Part I - Evaluation of Code and Documentation of Business Rules –System Application Design Document –Business Component Flow Diagram –Business Component Process Definition Document Based on these deliverables, Grace decided that there were additional system requirements Project Review

6. Deliverables Part II - · Technical Documentation and Historical Data Transfer Analysis –Document representing the physical data model –Data Quality Document –Loading Plan for Historical Data Project Review

7. Deliverables Part III - Testing –Representative Test Data –Complete and Fully Tested System Unit testing - OK System testing - OK User Acceptance - New Requirements! Project Review

8. RFTS Project Successes Documented Business Requirements Documented System Technical Design Analyzed and Prepared for Transfer of Historical Data Tested Application Project Evaluation

9. Closer Look at Some ordinary testing ‘bugs’ occurred during User Acceptance Testing –example: the cut & paste tool bar missing some places End Users were quite dissatisfied with some of the application function. Decision was made to not complete the testing phase as system redesign was needed User Acceptance Testing Project Evaluation

10. Work Still to be done Requirements - Do we have all the requirements defined ??? Best way to determine all requirements for extension phase –Formal Facilitated Requirements Session –Repeat User Acceptance Testing Project Evaluation

11. Requirements Analysis and Development Data Modeling & Create Database – Data model ERA analysis with Grace team. Change or create data model solution. Test SQL, Code & Test Module – Code and test changes to forms, queries, modules and event procedures. Documents the problems and solutions and then apply selected solution. Data Quality – Identify and document changed tables and relationships. Map new table dependencies. Update Loading Plan – Prepare a solution by verifying key values. Develop and test queries for data transfer. Update documentation. Documentation – Update documentation on System Application Design, Business Component Process Definition, Physical Data Model, Data Quality Document and Loading Plan. Proposal

12. Testing System Testing – Condor will run user scenarios on the development system. Tests will be based on the new requirements. Condor will document problems and recommend solutions. Regression Testing - Condor will run user scenarios on the development system to test the existing functionality and confirm that errors were not introduced during modification. Tests will be based on a system test plan. Condor will document problems and recommend solutions. Proposal

13. Testing User Acceptance Testing – Your organization will perform repeat User Acceptance Testing. Tests are built from the requirements specified in the Business Component Process Definition Document. This is a period of time for the user to test the system and verify that all requirements were met. The Engagement Manager will document and prioritize issues. The engagement team will be available to resolve mission critical issues. Proposal

14. Data Transfer and Implementation Data Transfer – Condor will complete loading and verification of historical data according to the loading plan. System Implementation – The RFTS System will be implemented on the target platform. Condor will provide support before going into production. Condor will turn over and obtain sign-off for approval of the system. Proposal

15. Data Transfer and Implementation Post Implementation Support – GCP’s internal IT Department will address all hardware and infrastructure issues. Condor fully expects all mission critical software issues will be resolved during testing and implementation. Should a mission critical software issue be discovered post implementation Condor will assign highest priority to resolving this issue in a timely manner on a time and materials basis. Non critical software issues can be addressed in subsequent phases of the project. Proposal

16. Partnering for Success