A Longitudinal Study of Identifying and Paying Down Architectural Debt

Architectural debt is a form of technical debt that derives from the gap between the architectural design of the system as it "should be" compared to "as it is". We measured architecture debt in two ways: 1) in terms of system-wide coupling measures, and 2) in terms of the number and severity of architectural flaws. In recent work it was shown that the amount of architectural debt has a huge impact on software maintainability and evolution. Consequently, detecting and reducing the debt is expected to make software more amenable to change. This paper reports on a longitudinal study of a healthcare communications product created by Brightsquid Secure Communications Corp. This start-up company is facing the typical trade-off problem of desiring responsiveness to change requests, but wanting to avoid the ever-increasing effort that the accumulation of quick-and-dirty changes eventually incurs. In the first stage of the study, we analyzed the status of the "before" system, which indicated the impacts of change requests. This initial study motivated a more in-depth analysis of architectural debt. The results of this analysis were used to motivate a comprehensive refactoring of the software system. The third phase of the study was a follow-on architectural debt analysis which quantified the improvements made. Using this quantitative evidence, augmented by qualitative evidence gathered from in-depth interviews with Brightsquid's architects, we present lessons learned about the costs and benefits of paying down architecture debt in practice.Comment: Submitted to ICSE-SEIP 201

The Nimbus II Data Code Experiment

Nimbus II Data Code information for acquiring and locating Automatic Picture Transmission and Direct Readout Infrared Radiometer dat

Survey of users of earth resources remote sensing data

A user survey was conducted to determine current earth resources survey (ERS) data use/user status and recommendations for strengthening use. Only high-altitude aircraft and satellite (primarily LANDSAT) data were included. Emphasis was placed on the private sector/industrial user. Objectives of the survey included: who is using ERS data, how they are using the data, the relative value of current data use as well as obtaining user views as to possible ways of strengthening future ERS data use. The survey results are documented and should provide relevant decision making information for developing future programs of maximum benefit to all end users of satellite ERS data

The Fix Was In: Mitre's "Independent" Review of Free File

In this Special Report, Ventry analyzes Mitre Corp.’s review of the IRS Free File program. He argues that Mitre’s lack of professional distance from the IRS prevented it from delivering an independent report. He discusses how Mitre found a majority of Free File Alliance (FFA) companies hid their Free File websites from eligible Free File users, and lured them to commercial sites. He shows how Mitre reinforced the view that FFA companies participate in Free File for economic gain rather than “philanthropy,” and warned the IRS against challenging the “free-to-fee” model. Mitreʹs warning was unnecessary, Ventry concludes, because the IRS is complicit in the FFAʹs abusive and potentially illegal actions

Habitat automation

A habitat, on either the surface of the Moon or Mars, will be designed and built with the proven technologies of that day. These technologies will be mature and readily available to the habitat designer. We believe an acceleration of the normal pace of automation would allow a habitat to be safer and more easily maintained than would be the case otherwise. This document examines the operation of a habitat and describes elements of that operation which may benefit from an increased use of automation. Research topics within the automation realm are then defined and discussed with respect to the role they can have in the design of the habitat. Problems associated with the integration of advanced technologies into real-world projects at NASA are also addressed

Information flow in house building organisations

This research describes an investigation into the information flows within the technical and commercial functions of house building organisations. It was initiated because of the evidence of poor data transfer and communications within the construction industry as identified by previous research. Little previous research had addressed the particular problems of the house building industry which accounts for up to a third of total new construction output in the UK. The organisational and information structures of six house building companies were examined and a typical organisational model developed. This model highlighted the importance of the technical and commercial functions of estimating, purchasing, valuations and cost monitoring/comparisons and the need for effective transfer of information between them. The information flows between these functions were studied and modelled using systems analysis techniques of data flow diagrams and entity-relationships models. The requirements for a computer-aided management system to improve and rationalise the information flows were identified and an integrated system, known as DEVELOP, was developed. The system was installed into a collaborating company and its advantages and disadvantages monitored over time. The main outcomes of the research are: (a) an organisational model for a typical house building organisation; (b) data flow and entity-relationship models for the functions of estimating, purchasing, valuations and cost monitoring/comparisons; and (c) an operational integrated management system for house builders that provides: (i) faster throughput of information (for example the time required to aggregated dwelling quantities for a typical development is reduced from three man days to one hour);(ii) greater consistency of information (by the provision of a company data library); and (iii) better communications between the functions (due to the integrated nature of the system and the adoption of a common coding system)

Glossary of software engineering laboratory terms

A glossary of terms used in the Software Engineering Laboratory (SEL) is presented. The terms are defined within the context of the software development environment for flight dynamics at Goddard Space Flight Center. A concise reference for clarifying and understanding the language employed in SEL documents and data collection forms is provided

Utah Chapter of the Sierra Club, et al v. Utah Division of Oil, Gas and Mining, Utah Board of Oil, Gas and Mining, Alton Coal Development, LLC, and Kane County, Utah : Brief of Appellee

BRIEF OF RESPONDENT-APPELLEES

System design and performance of earth/lunar horizon sensor BEC project 3744

An infrared horizon sensor system has been designed which is capable of searching over a wide field for the edges of a planet and, upon locating such edges, stations itself in a position which provides signals which identify the local vertical to the planet. In this fixed attitude it requires no continuous mechanical movement and operates with a minimum utilization of power. The system is thus capable of providing a high degree of accuracy when used for local vertical determination in orbits around the earth, the moon, or other planets. A detailed description of the design and operating features of the horizon scanner is given and the evaluation test data which have been completed are presented