Using Ada-C/C++ Changer as a Converter Automatically convert to C/C++ to reuse or redeploy your Ada code Eliminate the need for a costly and tedious code re-write for extensive cost and time savings Error free tool that prevents mistakes made in the error prone task of a manual rewrite Supports conversion of Ada 83, Ada 95 & a subset of Ada 2005 source code to ANSI C/C++ output Preserves Ada comments, files structures and variable names for easier code maintenance

Using Ada-C/C++ Changer as a Converter Keeps “static” trees as symbolic expressions rather than evaluating them to literal values Provides user configurable options to control the format and style of the C/C++ output Provides GNAT compiler compatibility Resultant C/C++ code can be integrated with OS Abstractor for real-time performance, portability and stability Available OS Interfaces OS Abstractor® – pSOS® – µC/OS™ Linux/POSIX – ThreadX® – FreeRTOS™ micro-ITRON – VxWorks® Nucleus® – Windows®

ROI: Cost of Converting – Manual vs. Ada-C/C++ Changer Small Medium Large 20K LOC 150K LOC 300K LOC Manual Conversion of Single Application * $ 381,351 $ 2,860,133 $ 5,720,265 Ada-C/C++ Changer License Fees $ 15,000 $ 60,000 $ 90,000 Est. Labor to use Ada-C/C++ Changer $ 8,000 $ 12,000 $ 16,000 Cost of Converting with Ada-C/C++ Changer $ 23,000 $ 72,000 $ 106,000 Savings (Manual minus Ada-C/C++ Changer) $ 358,351 $ 2,788,133 $ 5,614,265 Return on Investment 1,558 % 3,872 % 5,296 % Source: Software Engineering Institute, Carnagie Mellon, 2008. Bureau of Labor Statistics, May 2006. The Ada application code being converted is self-contained and compatible by an Ada 95 or Ada 83 compiler and on the same hardware/OS platform

Why use Ada-C/C++ Changer Instead of Manually Rewriting? Ada-C/C++ Changer includes a certified compiler (same one offered by Green Hills) front-end, which provides 100% code conversion (i.e. 0% manual code rewrite) Ada-C/C++ Changer offers the guarantee that the application will compile, link and execute successfully and effectively Only minimal testing is required (related to the task of changing a compiler tool) since you are not testing a new set of code Deciding against a manual rewrite means not needing to anticipate technical risks that could come from errors introduced during the effort

Why use Ada-C/C++ Changer Instead of Manually Rewriting? Conversion with Ada-C/C++ Changer is completed much faster than manual conversion, meaning the product can be deployed without many years of delay Ada-C/C++ Changer can handle large applications with multi-millions of LOC The more lines of code converted, the more the savings increase Provides many customization options for converted code Ex. Option to include Ada language exceptions in the converted code Our technical support team has expertise in Ada, C/C++, target tools and OS platforms If Ada-C/C++ Changer needs to be configured for a particular project, we can quickly make the needed changes to save our customers valuable time

Using Ada-C/C++ Changer as a Compiler Compile Ada code using C/C++ tools Support CPU architectures not supported by Ada compilers

Using Ada-C/C++ as a Compiler and Converter UNIFIED Transition Same tools across both old and new platforms Integrated Ada & C/C++ application development SMOOTH Transition Continue Ada development using the same tool that also offers effective conversion from Ada to C/C++ At your own phase: transition module by module; group by group Utilize unique/specialized MapuSoft expertise during transition ECONOMIC Transition Technology that will protect the existing investment while offering assurances for future platform changes Full conversion eliminating unnecessary coding/testing effort Carry through the existing valuable Ada product knowledge Single tool from one vendor across both platforms and languages

OS Abstractor Target Specific Module: Performance Features Not your typical wrapper Provides most of the OS features by itself and does not depend on the OS, except for a few features (ex. priority scheduling, change priority, semaphore, messaging, thread suspend/resume Quick support for a new OS MapuSoft can easily add support to a new commercial or in-house OS, typically in two weeks Process support to any OS Add software based process and shared memory functionality to an OS, even if they do not have those features Advanced process memory allocation scheme Applications can allocate required system heap memory during process creation to ensure that they will always have the required system memory Setting memory limits prevents an application from using up all system memory and impacting others

OS Abstractor Target Specific Module: Performance Features Thread pooling Applications can pool threads to increase platform robustness & performance by eliminating the overhead associated with actual task creation & deletion at run-time Mission Critical Features Applications have the ability to recover from software fatal errors through a soft reset by rolling the stack back to the start of the application API Flexibility Use one or more of the Cross-OS Development Platform Interface(s) Cross-OS Development Interface(s) can also be used within a single or across multiple applications Combine applications written with different OS APIs and run them on one or many OS

OS Abstractor Target Specific Module: Performance Features Zero copy message queues Cross-OS Queue APIs will not introduce data read and copy overhead API and application profiling, plus API optimization Profile applications and the Cross-OS Interface(s) functions on your target Optimize individual Cross-OS Interface functions based on profiler data Scalability specific to your application during code generation AppCOE reads your application to custom generate Interface code that is specific to your application to increase the performance with reduced memory footprint