Conclusion
Software design and portability
Archive REF: H3288 V1
Conclusion
Software design and portability

Authors : Patrick BELLOT, Bernard ROBINET

Publication date: November 10, 1998 | Lire en français

Logo Techniques de l'Ingenieur You do not have access to this resource.
Request your free trial access! Free trial

Already subscribed?

6. Conclusion

Software portability is not a matter of formalized technique. Common sense and the search for information guide the developer in making the right choices. Knowing which level of integration into the operating system is possible, or which external tools to use, is the result of serious study to avoid setbacks. The choice of languages is a key element. Our preference is for the abstract machine when the software being developed is destined to live for a long time. But this technique requires considerable skills and resources. Otherwise, a standardized language is a good choice. You should also try to respect your own programming techniques and carefully organize your code. Experience shows that impasses in this area always prove costly when software is ported. Finally, it may be worthwhile to look for code generation tools on the market that guarantee the portability of application modules...

You do not have access to this resource.
Logo Techniques de l'Ingenieur

Exclusive to subscribers. 97% yet to be discovered!

You do not have access to this resource. Click here to request your free trial access!

Already subscribed?


Ongoing reading
Conclusion

Article included in this offer

"Software technologies and System architectures"

( 227 articles )

Complete knowledge base

Updated and enriched with articles validated by our scientific committees

Services

A set of exclusive tools to complement the resources

View offer details