Topic
Software portability
About: Software portability is a research topic. Over the lifetime, 8987 publications have been published within this topic receiving 164922 citations. The topic is also known as: portability.
Papers published on a yearly basis
Papers
More filters
•
01 Jan 2006TL;DR: Software Architecture Evaluation Methods for Performance, Maintainability, Testability, and Portability
Abstract: Software Architecture Evaluation Methods for Performance, Maintainability, Testability, and Portability
49 citations
•
30 Jul 1999
TL;DR: In this article, a method for providing number portability in a telecommuncations network is disclosed, which includes receiving a call, determining how to route the call by looking at an identity information field and determining whether the call is ported or non-ported by analyzing the identity information fields.
Abstract: A method for providing number portability in a telecommuncations network is disclosed. The method provides number portability database queries that uses existing fields. The method includes receiving a call, determining how to route the call by looking at an identity information field and determining whether the call is ported or non-ported by analyzing the identity information field. The method further includes providing routing information associated with the call, the routing information including the identity information field, the identity information field further including a mobile station roaming number field and an international mobile subscriber identity field. The determining how to route the call further includes determining how to route the call by looking at a mobile station roaming number field in the information identity field. The determining whether the call is ported or non-ported further includes determining whether the call is ported or non-ported by analyzing an international mobile subscriber identity field in the information identity field.
49 citations
••
TL;DR: A methodology based on large community efforts in engineering and standardisation is outlined, which will depend on identifying a taxonomy of key activities– perhaps based on existing efforts to develop domain-specific languages, identify common patterns in weather and climate codes, and develop community approaches to commonly needed tools and libraries – and then collaboratively building up those key components.
Abstract: . Weather and climate models are complex pieces of software which include many individual components, each of which is
evolving under pressure to exploit advances in computing to enhance some combination of a range of possible
improvements (higher spatio-temporal resolution, increased fidelity in terms of resolved processes, more quantification of
uncertainty, etc.). However, after many years of a relatively stable computing environment with little choice in processing
architecture or programming paradigm (basically X86 processors using MPI for parallelism), the existing menu of processor
choices includes significant diversity, and more is on the horizon. This computational diversity, coupled with ever
increasing software complexity, leads to the very real possibility that weather and climate modelling will arrive at
a chasm which will separate scientific aspiration from our ability to develop and/or rapidly adapt codes to the available
hardware. In this paper we review the hardware and software trends which are leading us towards this chasm, before describing
current progress in addressing some of the tools which we may be able to use to bridge the chasm. This brief introduction
to current tools and plans is followed by a discussion outlining the scientific requirements for quality model codes which
have satisfactory performance and portability, while simultaneously supporting productive scientific evolution. We assert
that the existing method of incremental model improvements employing small steps which adjust to the changing hardware
environment is likely to be inadequate for crossing the chasm between aspiration and hardware at a satisfactory pace, in
part because institutions cannot have all the relevant expertise in house. Instead, we outline a methodology based on
large community efforts in engineering and standardisation, which will depend on identifying a taxonomy of key
activities – perhaps based on existing efforts to develop domain-specific languages, identify common patterns in weather
and climate codes, and develop community approaches to commonly needed tools and libraries – and then collaboratively
building up those key components. Such a collaborative approach will depend on institutions, projects, and individuals
adopting new interdependencies and ways of working.
49 citations
••
29 Nov 1999TL;DR: The combination of the Java programming language with the worldwide reach of the Internet now promises a solution to the problem of remote monitoring and control of manufacturing operations as mentioned in this paper, and the concept of virtual engineers or "remote engineers" who, armed with real-time plant information, can optimize machine setting or process control parameters, and troubleshoot problems before they escalate.
Abstract: Manufacturers have long wished for a tool that would permit remote monitoring and control of manufacturing operations. The combination of the Java programming language with the worldwide reach of the Internet now promises a solution to this problem. Java's scalability, portability, and platform independence allow remote monitoring and control applications ("applets") to run on any web browser. Java applets eliminate the need to build custom hardware/software when implementing remote monitoring and control systems. Any browser can be configured to display graphical representations of the plant or process and to annotate the image with real time data; thus, any Internet-enabled computer is a potential control station (assuming security concerns are satisfied). This gives rise to the concept of "virtual engineers" or "remote engineers" who, armed with real-time plant information, can optimize machine setting or process control parameters, and troubleshoot problems before they escalate.
49 citations
••
25 May 2004TL;DR: It is demonstrated that reduced middleware footprint can be achieved while maintaining real-time properties of applications running on networked embedded systems, and evidence that empirical measurement using a representative application is crucial to guide selection of feature subsets from general purpose middleware is given.
Abstract: General purpose middleware has been shown to be effective off-the-shelf, in meeting diverse functional requirements for a wide range of distributed systems. However, middleware customization is necessary for many networked embedded systems because of the resource constraints in the networked nodes. We demonstrate that reduced middleware footprint can be achieved while maintaining real-time properties of applications running on such systems. We also give evidence that empirical measurement using a representative application is crucial to guide (1) selection of feature subsets from general purpose middleware and (2) trade-offs among different dimensions of design metrics including real-time, footprint, and portability.
49 citations