Software

About: Software is a research topic. Over the lifetime, 130577 publications have been published within this topic receiving 2028987 citations. The topic is also known as: computer software & computational tool.

Directed Sonar Sensing for Mobile Robot Navigation

Abstract: List of Figures. List of Tables. List of Abbreviations and Symbols. Preface. 1. Introduction. 2. A Sonar Sensor Model. 3. Model-Based Localization. 4. Map Building. 5. Simultaneous Map Building and Localization. 6. Directed Sensing Strategies. 7. Why Use Sonar? A. Hardware and Software. Bibliography. Index.

Detecting large-scale system problems by mining console logs

Abstract: Surprisingly, console logs rarely help operators detect problems in large-scale datacenter services, for they often consist of the voluminous intermixing of messages from many software components written by independent developers We propose a general methodology to mine this rich source of information to automatically detect system runtime problems We first parse console logs by combining source code analysis with information retrieval to create composite features We then analyze these features using machine learning to detect operational problems We show that our method enables analyses that are impossible with previous methods because of its superior ability to create sophisticated features We also show how to distill the results of our analysis to an operator-friendly one-page decision tree showing the critical messages associated with the detected problems We validate our approach using the Darkstar online game server and the Hadoop File System, where we detect numerous real problems with high accuracy and few false positives In the Hadoop case, we are able to analyze 24 million lines of console logs in 3 minutes Our methodology works on textual console logs of any size and requires no changes to the service software, no human input, and no knowledge of the software's internals

User Guide for Minpack-1

Abstract: MINPACK-1 is a pack of FORTRAN subprograms for the numerical solution of nonlinear equations and nonlinear least-squares problems. This report provides an overview of the algorithms and software in the package, and includes the documentation and program listings.

A cost-value approach for prioritizing requirements

Abstract: Developing software systems that meet stakeholders' needs and expectations is the ultimate goal of any software provider seeking a competitive edge. To achieve this, you must effectively and accurately manage your stakeholders' system requirements: the features, functions, and attributes they need in their software system. Once you agree on these requirements, you can use them as a focal point for the development process and produce a software system that meets the expectations of both customers and users. However, in real world software development, there are usually more requirements than you can implement given stakeholders' time and resource constraints. Thus, project managers face a dilemma: how do you select a subset of the customers' requirements and still produce a system that meets their needs? The authors developed a cost-value approach for prioritizing requirements and applied it to two commercial projects.

Property-based software engineering measurement

Abstract: Little theory exists in the field of software system measurement. Concepts such as complexity, coupling, cohesion or even size are very often subject to interpretation and appear to have inconsistent definitions in the literature. As a consequence, there is little guidance provided to the analyst attempting to define proper measures for specific problems. Many controversies in the literature are simply misunderstandings and stem from the fact that some people talk about different measurement concepts under the same label (complexity is the most common case). There is a need to define unambiguously the most important measurement concepts used in the measurement of software products. One way of doing so is to define precisely what mathematical properties characterize these concepts, regardless of the specific software artifacts to which these concepts are applied. Such a mathematical framework could generate a consensus in the software engineering community and provide a means for better communication among researchers, better guidelines for analysts, and better evaluation methods for commercial static analyzers for practitioners. We propose a mathematical framework which is generic, because it is not specific to any particular software artifact, and rigorous, because it is based on precise mathematical concepts. We use this framework to propose definitions of several important measurement concepts (size, length, complexity, cohesion, coupling). It does not intend to be complete or fully objective; other frameworks could have been proposed and different choices could have been made. However, we believe that the formalisms and properties we introduce are convenient and intuitive. This framework contributes constructively to a firmer theoretical ground of software measurement.