Topic
Application software
About: Application software is a research topic. Over the lifetime, 12185 publications have been published within this topic receiving 219822 citations. The topic is also known as: software application & application software.
Papers published on a yearly basis
Papers
More filters
15 Apr 2002
TL;DR: This paper examines the explicit communication characteristics of several sophisticated scientific applications, which, by themselves, constitute a representative suite of publicly available benchmarks for large cluster architectures by focusing on the Message Passing Interface (MPI) and by using hardware counters on the microprocessor.
Abstract: This paper examines the explicit communication characteristics of several sophisticated scientific applications, which, by themselves, constitute a representative suite of publicly available benchmarks for large cluster architectures. By focusing on the Message Passing Interface (MPI) and by using hardware counters on the microprocessor, we observe each application's inherent behavioral characteristics: point-to-point and collective communication, and floating point operations. Furthermore, we explore the sensitivities of these characteristics to both problem size and number of processors. Our analysis reveals several striking similarities across our diverse set of applications including the use of collective operations, especially those collectives with very small data payloads. We also highlight a trend of novel applications parting with regimented, static communication patterns in favor of dynamically evolving patterns, as evidenced by our experiments on applications that use implicit linear solvers and adaptive mesh refinement. Overall, our study contributes a better understanding or the requirements of current and emerging paradigms of scientific computing in terms of their computation and communication demands.
189 citations
TL;DR: The strategy of using multiple versions of independently developed software as a means to tolerate residual software design faults is discussed and the effectiveness of multiversion software is studied by comparing estimates of the failure probability of these systems with the failure probabilities of single versions.
Abstract: The strategy of using multiple versions of independently developed software as a means to tolerate residual software design faults is discussed. The effectiveness of multiversion software is studied by comparing estimates of the failure probabilities of these systems with the failure probabilities of single versions. The estimates are obtained under a model of dependent failures and compared with estimates obtained when failures are assumed to be independent. The experimental results are based on 20 versions of an aerospace application developed and independently validated by 60 programmers from 4 universities. Descriptions of the application and development process are given, together with an analysis of the 20 versions. >
188 citations
TL;DR: The design and implementation of a storage and retrieval structure for software components that is based on formal specifications and on the refinement ordering between specifications are discussed.
Abstract: Software libraries are repositories which contain software components; as such, they represent a precious resource for the software engineer. As software libraries grow in size, it becomes increasingly difficult to maintain adequate precision and recall with informal retrieval algorithms. In this paper, we discuss the design and implementation of a storage and retrieval structure for software components that is based on formal specifications and on the refinement ordering between specifications.
187 citations
Patent•
15 Mar 2001
TL;DR: In this article, a method of conducting a financial transaction by a purchaser over a communications network is provided where the purchaser does not transmit his or her "real" payment card information over the network but instead secure payment application software is provided which allows for the transmission of a pseudo account number that is cryptographically processed for purposes of responding to an authorization request based on the real account number.
Abstract: A method of conducting a financial transaction by a purchaser over a communications network is provided where the purchaser does not transmit his or her 'real' payment card information over the network but instead secure payment application software is provided which allows for the transmission of a pseudo account number that is cryptographically processed for purposes of responding to an authorization request based on the real account number.
187 citations
TL;DR: In the study, a similarity degree based algorithm is proposed to aggregate the objective information about ERP systems from some external professional organizations, which may be expressed by different linguistic term sets.
186 citations