scispace - formally typeset
Search or ask a question
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
More filters
Proceedings ArticleDOI
01 Feb 1997
TL;DR: ASEN (Automated Planning/Scheduling Environment), a modular, reconfigurable application framework which is capable of supporting a wide variety of planning and scheduling applications, is described.
Abstract: A number of successful applications of automated planning and scheduling applications to spacecraft operations have recently been reported in the literature. However, these applications have been one-of-a-kind applications that required a substantial amount of development effort. In this paper, we describe ASPEN (Automated Planning/Scheduling Environment), a modular, reconfigurable application framework which is capable of supporting a wide variety of planning and scheduling applications. We describe the architecture of ASPEN, as well as a number of current spacecraft control/operations applications in progress.

92 citations

Book
20 Dec 2018
TL;DR: The regular DBpedia extractors deviate further from the regular extractors in that they aggregate data from all Wikipedia pages as opposed to operating on a single article.
Abstract: dbo:abstract The first lines of the Wikipedia article Categories dc:subject Wikipedia categories assigned to the article Disambiguation dbo:wikiPageDisambiguates Disambiguation links External links dbo:wikiPageExternalLink Links to external web pages Geo-coordinates georss:point Geographical coordinates Homepage foaf:homepage Link to the official homepage of an instance Image foaf:depiction Link to the first image on the Wikipedia page Label rdfs:label The page title of the Wikipedia article Page links dbo:wikiPageWikiLink Links to other Wikipedia articles Redirect dbo:wikiPageRedirects Wikipedia page to redirect to See Table 2.4 for the URI prefixes them deviate further from the regular extractors in that they aggregate data from all Wikipedia pages as opposed to operating on a single article. The resulting datasets include grammatical gender (for entities of type person), lexicalizations (alternative names for entities and concepts), topic signatures (strongest related terms), and thematic concepts (the main subject entities/concepts for Wikipedia categories). 2.3.2.3 Datasets and Resources The output of each DBpedia extractor, for each language, is made available as a separate dataset. All datasets are provided in two serializations: as Turtle (N-triples) and as Turtle quads (N-Quads, which include context). The datasets can be divided into the following categories: • DBpedia Ontology: The latest version of the ontology that was used while extracting all datasets. • Core datasets: All infobox-based and specific feature extractors (including the ones listed in Table 2.3) belong here. • Links to other datasets: DBpedia is interlinked with a large number of knowledge bases. The datasets in this group provide links to external resources both on the instance level (owl:sameAs), e.g., to Freebase and YAGO, and on the schema level (owl:equivalentClass and owl:equivalentProperty), most notably to schema.org. • NLP datasets: This last group corresponds to the output of the statistical extractors. Namespaces and Internationalization The generic DBpedia URI namespaces are listed in the upper block of Table 2.4. As part of the internationalization efforts, some datasets are available both in localized and in canonicalized version.

92 citations

Proceedings ArticleDOI
23 Apr 2006
TL;DR: This paper characterizing and detecting relayed traffic generated by Skype, a popular voice over IP application that uses relays, relies solely on flow-level properties rather than on applicationor protocol-specific information and shows that the metrics proposed can be used to reliably detect Skype-relayed traffic.
Abstract: Networked application developers have recently started to use end-users’ computers as relay nodes – application instances that also act as bridges between pairs of hosts running the same application. Relay nodes can bring costs to both users and network operators, at least in terms of increased bandwidth consumption. An interesting problem is to characterize the nature of relayed traffic and to detect its presence in the network. This paper focuses on characterizing and detecting relayed traffic generated by Skype, a popular voice over IP application that uses relays. Our technique relies solely on flow-level properties rather than on applicationor protocol-specific information. Using two different controlled experimental environments we generate and collect a large amount of Skype-relayed traffic. We propose several metrics to characterize the nature of relayed traffic. These metrics together with the results obtained from the experimental characterization of Skype-relayed traffic are used to detect Skyperelayed traffic traversing the access point of a large network. We show that the metrics proposed can be used to reliably detect Skype-relayed traffic. Finally, we believe the metrics proposed could be applied more broadly in the detection of relayed traffic generated by other multimedia applications.

92 citations

Journal ArticleDOI
TL;DR: This paper describes two e-science infrastructures: Science and Engineering Applications Grid (SEAGrid) and molecular modeling and parametrization (ParamChem), which share a similar three-tier computational infrastructure that consists of a front-end client, a middleware web services layer, and a remote HPC computational layer.

92 citations

Proceedings ArticleDOI
18 Oct 1991
TL;DR: The environment prototype contains a set of performance data transformation modules that can be interconnected in user-specified ways and allows users to interconnect and configure modules graphically to form an acyclic, directed data analysis graph.
Abstract: As parallel systems expand in size and complexity, the absence of performance tools for these parallel systems exacerbates the already difficult problems of application program and system software performance tuning. Moreover, given the pace of technological change, we can no longer afford to develop ad hoc, one-of-a-kind performance instrumentation software; we need scalable, portable performance analysis tools. We describe an environment prototype based on the lessons learned from two previous generations of performance data analysis software. Our environment prototype contains a set of performance data transformation modules that can be interconnected in user-specified ways. It is the responsibility of the environment infrastructure to hide details of module interconnection and data sharing. The environment is written in C++ with the graphical displays based on X windows and the Motif toolkit. It allows users to interconnect and configure modules graphically to form an acyclic, directed data analysis graph. Performance trace data are represented in a self-documenting stream format that includes internal definitions of data types, sizes, and names. The environment prototype supports the use of head-mounted displays and sonic data presentation in addition to the traditional use of visual techniques.

92 citations


Network Information
Related Topics (5)
Software
130.5K papers, 2M citations
87% related
User interface
85.4K papers, 1.7M citations
84% related
Wireless sensor network
142K papers, 2.4M citations
82% related
Wireless
133.4K papers, 1.9M citations
82% related
Node (networking)
158.3K papers, 1.7M citations
82% related
Performance
Metrics
No. of papers in the topic in previous years
YearPapers
202191
2020151
2019237
2018321
2017359
2016364