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...
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? Log in!
The Ultimate Scientific and Technical Reference
This article is included in
Software technologies and System architectures
This offer includes:
Knowledge Base
Updated and enriched with articles validated by our scientific committees
Services
A set of exclusive tools to complement the resources
Practical Path
Operational and didactic, to guarantee the acquisition of transversal skills
Doc & Quiz
Interactive articles with quizzes, for constructive reading
Conclusion
Bibliography
References
Standardization
French Standards Association (AFNOR)
- Technologies de l'information. Évaluation des produits logiciels. Caractéristiques de qualité et directives d'utilisation. - NF ISO/CEI 9126 - 10-92
Theses
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? Log in!
The Ultimate Scientific and Technical Reference