Relevant bibliographies by topics / Software portability

Contents

  1. Journal articles
  2. Dissertations / Theses
  3. Books
  4. Book chapters
  5. Conference papers
  6. Reports

Academic literature on the topic 'Software portability'

Author: Grafiati
Published: 4 June 2021
Last updated: 26 January 2023

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Software portability.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Journal articles on the topic "Software portability"

1

Tanner, Paul. "Software portability." StandardView 4, no. 2 (1996): 88–93. http://dx.doi.org/10.1145/234999.235001.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

de Groote, C. "Software portability." Information and Software Technology 31, no. 9 (1989): 509. http://dx.doi.org/10.1016/0950-5849(89)90153-5.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Holyoake, T. J. "CADCAM software portability." Computer-Aided Engineering Journal 4, no. 6 (1987): 224. http://dx.doi.org/10.1049/cae.1987.0056.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Kaindl, Hermann. "Portability of software." ACM SIGPLAN Notices 23, no. 6 (1988): 59–68. http://dx.doi.org/10.1145/44546.44551.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Bengtsson, Bengt. "Portability of Educational Software." Journal of Research on Computing in Education 23, no. 2 (1990): 160–72. http://dx.doi.org/10.1080/08886504.1990.10781953.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Stanchev, Ivan. "Software Engineering for Portability." Journal of Research on Computing in Education 23, no. 2 (1990): 203–24. http://dx.doi.org/10.1080/08886504.1990.10781957.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Deshpande, G., T. Pearse, and P. Oman. "Software portability annotated bibliography." ACM SIGPLAN Notices 32, no. 2 (1997): 45–53. http://dx.doi.org/10.1145/251621.251632.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Silakov, D. V., and A. V. Khoroshilov. "Ensuring portability of software." Programming and Computer Software 37, no. 1 (2011): 41–47. http://dx.doi.org/10.1134/s0361768811010051.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Trimble, Geoffrey, and Kenneth Franc. "Software portability for microcomputers." International Journal of Project Management 3, no. 1 (1985): 6–12. http://dx.doi.org/10.1016/0263-7863(85)90036-5.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Mooney, James D. "A course in software portability." ACM SIGCSE Bulletin 24, no. 1 (1992): 53–56. http://dx.doi.org/10.1145/135250.134522.

Full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "Software portability"

1

Johansson, Andreas, and Jonas Svensson. "Techniques for Software Portability in Mobile Development." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-2758.

Full text
Abstract:
When attempting to get a software product to reach a larger part of the market, portability is a key factor. Unfortunately, it is often neglected from the software development cycle, and rather achieved by ad hoc methods in not very cost-effective ways. This thesis investigates portability in the context of mobile development. Previous research in this particular area has been hard to find, despite there obviously being special aspects surrounding it which are worth investigating further. The project was initiated with a literature study to find out the current state-of-the-art for portability. After this step the development of a mobile application was conducted, before which a market analysis had been carried out in order to explore which mobile platforms would be the most relevant to develop it for. The point of this case study was to attempt to achieve as high a degree of portability as possible, to later port the application to another platform. Based on the data gathered from this, conclusions were drawn and a general model with guidelines for developing mobile applications with portability as a main attribute was constructed. Among the more important lessons learned was that portability is more important in mobile development, due to the market being so diverse, while it also is a lot harder to achieve properly. This research will hopefully help development teams see the strengths and weaknesses of mobile application portability more clearly, allowing them to more easily design for it as well as making it a more intricate part of their process.
APA, Harvard, Vancouver, ISO, and other styles
2

Knutsen, Henrik Holenbakken. "Enhancing Software Portability with Hardware Parametrized Autotuning." Thesis, Norges teknisk-naturvitenskapelige universitet, Institutt for datateknikk og informasjonsvitenskap, 2013. http://urn.kb.se/resolve?urn=urn:nbn:no:ntnu:diva-24568.

Full text
Abstract:
Akselerator teknologi skal brukes til å muliggjøre fortsatt skalering av numerisk software. Ytelses-begrensninger som ett resultat av å flytte en applikasjon fra arkitektur til arkitektur er ett problem, siden egenskapene til arkitekturer endres raskere enn programmer kan oppdateres. For å øke flyttbarheten til kode må program-logikken og egenskapene til arkitekturen uttrykkes som parametre, slik at utforskingen av forskjellige maskin-spesifikke optimaliseringer kan delvis automatiseres.Dette prosjektet søker å undersøke moderne metoder og verktøy for å muliggjøre automatisering av å flytte kodebaser mellom arkitekturer uten ytelsestap. Teorien vil tas i bruk på en applikasjon fra PRACE prosjektet
APA, Harvard, Vancouver, ISO, and other styles
3

Cooper, D. Kelly. "ACHIEVING PORTABILITY FOR LEGACY SOFTWARE USING JAVA." International Foundation for Telemetering, 2007. http://hdl.handle.net/10150/604488.

Full text
Abstract:
ITC/USA 2007 Conference Proceedings / The Forty-Third Annual International Telemetering Conference and Technical Exhibition / October 22-25, 2007 / Riviera Hotel & Convention Center, Las Vegas, Nevada<br>Increasingly, many software developers are facing the challenge of adapting software applications developed on one platform to work on multiple platforms. While software standards have helped this effort, they do not go far enough, and many platforms only partially support these standards leaving many needed functions in platform specific libraries. This is particularly evident in the areas of graphics and user interfaces, threading and synchronization, and in network and file access. Fortunately, Java offers a common interface where native libraries diverge. This paper outlines a phased strategy for migrating platform specific applications to be platform independent while reusing the robust, existing algorithms.
APA, Harvard, Vancouver, ISO, and other styles
4

Lawson, Edwin W. "On software reusability, portability and user interface acceptability in UNIX -based aplications." Thesis, Cardiff University, 1990. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.278631.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Chapin, John, and Alok Shah. "SOFTWARE RADIO TECHNOLOGY AND CHALLENGES." International Foundation for Telemetering, 2002. http://hdl.handle.net/10150/607499.

Full text
Abstract:
International Telemetering Conference Proceedings / October 21, 2002 / Town & Country Hotel and Conference Center, San Diego, California<br>This paper provides an overview of software radio and its current state in the industry. Software radio is a technology in which all of the waveform processing, including the physical layer, of a wireless device moves into software. If designed properly, this approach leads to dramatically improved device flexibility, software portability, and reduced development costs. Of course, such a technology brings with it numerous challenges, from hardware components to power constraints to the regulatory environment.
APA, Harvard, Vancouver, ISO, and other styles
6

Smith, Robert. "A component-based layered abstraction model for software portability across autonomous mobile robots." Thesis, Queensland University of Technology, 2005. https://eprints.qut.edu.au/16406/1/Robert_Smith_Thesis.pdf.

Full text
Abstract:
Today's autonomous robots come in a variety of shapes and sizes from all terrain vehicles clambering over rubble, to robots the size of coffee cups zipping about a laboratory. The diversity of these robots is extraordinary; but so is the diversity of the software created to control them even when the basic tasks many robots undertake are practically the same (such as obstacle detection, tracking, or path planning). It would be beneficial if some reuse of these coded sub-tasks could be achieved. However, most of the present day robot software is monolithic, very specialised and not at all modular, which hinders the reuse and sharing of code between robot platforms. One difficulty is that the hardware details of a robot are usually tightly woven into the high-level controllers. When these details are not decoupled and explicitly encapsulated, the entire code set must be revised if the robot platform changes. An even bigger challenge is that a robot is a context-aware device. Hence, the possible interpretations of the state of the robot and its environment vary along with its context. For example, as the robots differ in size and shape, the meaning of concepts such as direction, speed, and distance can change { objects that are considered far from one robot, might seem near to a much larger robot. When designing reusable robot software, these variable interpretations of the environment must be considered. Similarly, so must variations in context dependent robot instructions { for example, `move fast' has different abstractions; a `virtual robot' layer to manage the robot's platform abstractions; and high-level abstraction components that are used to describe the state of the robot and its environment. The prototype is able to support binary code portability and dynamic code extensibility across a range of different robots (demonstrated on eight diverse robot platform configurations). These outcomes significantly ease the burden on robot software developers when deploying a new robot (or even reconfiguring old robots) since high-level binary controllers can be executed unchanged on different robots. Furthermore, since the control code is completely decoupled from the platform information, these concerns can be managed separately, thereby providing a flexible means for managing different configurations of robots. These systems and techniques all improve the robot software design, development, and deployment process. Different meanings depending on the robot's size, environmental context and task being undertaken. What is needed is a unifying cross-platform software engineering approach for robots that will encourage the development of code that is portable, modular and robust. Toward this end, this research presents a complete abstraction model and implementation prototype that contain a suite of techniques to form and manage the robot hardware, platform, and environment abstractions. The system includes the interfaces and software components required for hardware device and operating system abstractions; a `virtual robot' layer to manage the robot's platform abstractions; and high-level abstraction components that are used to describe the state of the robot and its environment. The prototype is able to support binary code portability and dynamic code extensibility across a range of different robots (demonstrated on eight diverse robot platform configurations). These outcomes significantly ease the burden on robot software developers when deploying a new robot (or even reconfiguring old robots) since high-level binary controllers can be executed unchanged on different robots. Furthermore, since the control code is completely decoupled from the platform information, these concerns can be managed separately, thereby providing a flexible means for managing different configurations of robots. These systems and techniques all improve the robot software design, development, and deployment process.
APA, Harvard, Vancouver, ISO, and other styles
7

Smith, Robert. "A component-based layered abstraction model for software portability across autonomous mobile robots." Queensland University of Technology, 2005. http://eprints.qut.edu.au/16406/.

Full text
Abstract:
Today's autonomous robots come in a variety of shapes and sizes from all terrain vehicles clambering over rubble, to robots the size of coffee cups zipping about a laboratory. The diversity of these robots is extraordinary; but so is the diversity of the software created to control them even when the basic tasks many robots undertake are practically the same (such as obstacle detection, tracking, or path planning). It would be beneficial if some reuse of these coded sub-tasks could be achieved. However, most of the present day robot software is monolithic, very specialised and not at all modular, which hinders the reuse and sharing of code between robot platforms. One difficulty is that the hardware details of a robot are usually tightly woven into the high-level controllers. When these details are not decoupled and explicitly encapsulated, the entire code set must be revised if the robot platform changes. An even bigger challenge is that a robot is a context-aware device. Hence, the possible interpretations of the state of the robot and its environment vary along with its context. For example, as the robots differ in size and shape, the meaning of concepts such as direction, speed, and distance can change { objects that are considered far from one robot, might seem near to a much larger robot. When designing reusable robot software, these variable interpretations of the environment must be considered. Similarly, so must variations in context dependent robot instructions { for example, `move fast' has different abstractions; a `virtual robot' layer to manage the robot's platform abstractions; and high-level abstraction components that are used to describe the state of the robot and its environment. The prototype is able to support binary code portability and dynamic code extensibility across a range of different robots (demonstrated on eight diverse robot platform configurations). These outcomes significantly ease the burden on robot software developers when deploying a new robot (or even reconfiguring old robots) since high-level binary controllers can be executed unchanged on different robots. Furthermore, since the control code is completely decoupled from the platform information, these concerns can be managed separately, thereby providing a flexible means for managing different configurations of robots. These systems and techniques all improve the robot software design, development, and deployment process. Different meanings depending on the robot's size, environmental context and task being undertaken. What is needed is a unifying cross-platform software engineering approach for robots that will encourage the development of code that is portable, modular and robust. Toward this end, this research presents a complete abstraction model and implementation prototype that contain a suite of techniques to form and manage the robot hardware, platform, and environment abstractions. The system includes the interfaces and software components required for hardware device and operating system abstractions; a `virtual robot' layer to manage the robot's platform abstractions; and high-level abstraction components that are used to describe the state of the robot and its environment. The prototype is able to support binary code portability and dynamic code extensibility across a range of different robots (demonstrated on eight diverse robot platform configurations). These outcomes significantly ease the burden on robot software developers when deploying a new robot (or even reconfiguring old robots) since high-level binary controllers can be executed unchanged on different robots. Furthermore, since the control code is completely decoupled from the platform information, these concerns can be managed separately, thereby providing a flexible means for managing different configurations of robots. These systems and techniques all improve the robot software design, development, and deployment process.
APA, Harvard, Vancouver, ISO, and other styles
8

Lenhard, Jörg [Verfasser], and Guido [Akademischer Betreuer] Wirtz. "Portability of Process-Aware and Service-Oriented Software: Evidence and Metrics / Jörg Lenhard. Betreuer: Guido Wirtz." Bamberg : University of Bamberg Press, 2016. http://d-nb.info/1098185196/34.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Günther, Daniel Verfasser], Gerd [Akademischer Betreuer] [Ascheid, and Cristina [Akademischer Betreuer] Silvano. "Hardware and software design methodologies for portability, flexibility and versatility in multi-standard MIMO baseband processing / Daniel Günther ; Gerd Ascheid, Cristina Silvano." Aachen : Universitätsbibliothek der RWTH Aachen, 2017. http://d-nb.info/1162499524/34.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Günther, Daniel [Verfasser], Gerd [Akademischer Betreuer] Ascheid, and Cristina [Akademischer Betreuer] Silvano. "Hardware and software design methodologies for portability, flexibility and versatility in multi-standard MIMO baseband processing / Daniel Günther ; Gerd Ascheid, Cristina Silvano." Aachen : Universitätsbibliothek der RWTH Aachen, 2017. http://d-nb.info/1162499524/34.

Full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "Software portability"

1

Lecarme, Olivier. Software portability. McGraw-Hill, 1986.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
2

Pellissier, Gart Mireille, ed. Software portability. McGraw-Hill, 1986.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
3

Software portability. Gower Technical Press, 1988.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
4

DuBois, Paul. Software portability with imake. 2nd ed. O'Reilly & Assoc., 1996.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
5

Software portability with imake. O'Reilly & Assoc., 1993.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
6

Lecarme, Olivier. Software portability: With microcomputer issues. McGraw-Hill, 1989.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
7

Lecarme, Olivier. Software portability: With microcomputer issues. McGraw-Hill, 1989.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
8

Portability and the C language. Hayden Books, 1988.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
9

Abdel-Hamid, Tarek K. On the portability of quantitative software estimation models. Sloan School of Management, Massachusetts Institute of Technology, 1988.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
10

AISE Software Portability Task Group. Software portability in the steel industry: Step 1--project formulation. Association of Iron and Steel Engineers, 1985.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Book chapters on the topic "Software portability"

1

Ohta, Tadashi, Takashi Terasaki, Toshikazu Ohkubo, Mitsuru Hanazawa, and Masayuki Ohtaka. "CTRON Software Portability Evaluation." In TRON Project 1990. Springer Japan, 1990. http://dx.doi.org/10.1007/978-4-431-68129-8_8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Takeda, Kenji, Ivan Wolton, and Denis Nicole. "Software Portability and Maintenance." In High-Performance Computing. Springer US, 1999. http://dx.doi.org/10.1007/978-1-4615-4873-7_13.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Staroste, R., H. Schmutz, M. Wasmund, A. Schill, and W. Stoll. "A Portability Environment for Communication Software." In Hector Heterogeneous Computers Together A Joint Project of IBM and the University of Karlsruhe. Springer Berlin Heidelberg, 1988. http://dx.doi.org/10.1007/978-3-642-73574-5_5.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Grandi, Steven. "Hardware and Software Portability and Performance." In Instrumentation for Ground-Based Optical Astronomy. Springer New York, 1988. http://dx.doi.org/10.1007/978-1-4612-3880-5_39.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Rzehak, Helmut. "Portability of Software Systems for Real Time Applications." In Innovationen bei Rechen- und Kommunikationssystemen. Springer Berlin Heidelberg, 1994. http://dx.doi.org/10.1007/978-3-642-51136-3_45.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Byckling, Mikko, Juhani Kataja, Michael Klemm, and Thomas Zwinger. "OpenMP $$^*$$ SIMD Vectorization and Threading of the Elmer Finite Element Software." In Scaling OpenMP for Exascale Performance and Portability. Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-319-65578-9_9.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Munnecke, Thomas H., and Ingeborg M. Kuhn. "Large-Scale Portability of Hospital Information System Software Within the Veterans Administration." In Computers and Medicine. Springer New York, 1989. http://dx.doi.org/10.1007/978-1-4612-3488-3_8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Shabash, Boris, Kay Wiese, and Edward Glen. "Improving the Portability and Performance of jViz.RNA – A Dynamic RNA Visualization Software." In Pattern Recognition in Bioinformatics. Springer Berlin Heidelberg, 2012. http://dx.doi.org/10.1007/978-3-642-34123-6_8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Kuznetsov, Evgeny, Nikolay Kondratyuk, Mikhail Logunov, Vsevolod Nikolskiy, and Vladimir Stegailov. "Performance and Portability of State-of-Art Molecular Dynamics Software on Modern GPUs." In Parallel Processing and Applied Mathematics. Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-43229-4_28.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Koltashev, Andrey. "A Practical Approach to Software Portability Based on Strong Typing and Architectural Stratification." In Lecture Notes in Computer Science. Springer Berlin Heidelberg, 2003. http://dx.doi.org/10.1007/978-3-540-45213-3_13.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Software portability"

1

Mooney, James D. "A course in software portability." In the twenty-third SIGCSE technical symposium. ACM Press, 1992. http://dx.doi.org/10.1145/134510.134522.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

van der Vegt, Wim, Wim Westera, Hub Kurvers, and Enkhbold Nyamsuren. "Portability of Serious Game Software Components." In 2019 IEEE Conference on Games (CoG). IEEE, 2019. http://dx.doi.org/10.1109/cig.2019.8848094.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Filipski, Alan. "A case study in software portability." In the 1985 ACM SIGSMALL symposium. ACM Press, 1985. http://dx.doi.org/10.1145/317164.317174.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Nori, Rahul, Nitin Karodiya, and Hassan Reza. "Portability testing of scientific computing software systems." In 2013 IEEE International Conference on Electro/ Information Technology (EIT). IEEE, 2013. http://dx.doi.org/10.1109/eit.2013.6632686.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Shafer, Jeffrey, Scott Rixner, and Alan L. Cox. "The Hadoop distributed filesystem: Balancing portability and performance." In amp; Software (ISPASS 2010). IEEE, 2010. http://dx.doi.org/10.1109/ispass.2010.5452045.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Kim, S., J. Park, and Y. B. Kwon. "An Embedded OCR Software Architecture for Enhancing Portability." In Ninth International Conference on Document Analysis and Recognition (ICDAR 2007) Vol 2. IEEE, 2007. http://dx.doi.org/10.1109/icdar.2007.4377066.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Coelho, César, Otto Koudelka, and Mario Merri. "NanoSat MO Framework: Achieving On-board Software Portability." In SpaceOps 2016 Conference. American Institute of Aeronautics and Astronautics, 2016. http://dx.doi.org/10.2514/6.2016-2624.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Lewis, Bruce. "Software portability gains realized with METAH and Ada95." In the 11th international workshop. ACM Press, 2002. http://dx.doi.org/10.1145/584418.584423.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Ghandorh, Hamza, Abdulfattah Noorwali, Ali Bou Nassif, Luiz Fernando Capretz, and Roy Eagleson. "A Systematic Literature Review for Software Portability Measurement." In ICSCA 2020: 2020 9th International Conference on Software and Computer Applications. ACM, 2020. http://dx.doi.org/10.1145/3384544.3384569.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Straub, Jeremy. "Portability scenarios for intelligent robotic control agent software." In SPIE Defense + Security, edited by Eric J. Kelmelis. SPIE, 2014. http://dx.doi.org/10.1117/12.2049506.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "Software portability"

1

Gamblin, T. Software Complexity Threatens Performance Portability. Office of Scientific and Technical Information (OSTI), 2015. http://dx.doi.org/10.2172/1223835.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Pennell, James P., Cy D. Ardoin, James Baldo, John M. Boone, and Bill R. Brykczynski. An Assessment of Software Portability and Reusability for the WAM program. Defense Technical Information Center, 1990. http://dx.doi.org/10.21236/ada251596.

Full text
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Software portability' for particular source types:
Journal articles Dissertations / Theses Books
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography