By Topic

Porting Ada: a report from the field

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$31 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

1 Author(s)
Skazinski, J.G. ; Magnavox Electron. Syst. Co., Fort Wayne, IN, USA

With the constant barrage of new systems, porting software applications is inevitable. This article takes a look at the problems involved in porting an Ada/C application. The porting effort begins when the software architecture is defined and the code implemented. The task is completed with the successful execution of the software on all target platforms. The AFATDS porting effort to the HP RISC platform was completed successfully. The effort to port AFATDS to an InteVSCO Unix platform is still incomplete and is awaiting an Ada compiler upgrade that can pass the AFATDS messaging schema's large arrays to generic procedures. With the numerous operating systems available, the constant barrage of new operating system releases, and the continual hardware advancements, the need to port software applications is evident. The success of any porting effort depends on the maturation and reliability of the tools being used. If the Department of Defense's dual-use strategy is to succeed, DoD must also foster the development of reliable and affordable Ada tools.<>

Published in:

Computer  (Volume:27 ,  Issue: 10 )