Software development: A paradigm for the future

A new paradigm for software development that treats software development as an experimental activity is presented. It provides built-in mechanisms for learning how to develop software better and reusing previous experience in the forms of knowledge, processes, and products. It uses models and measures to aid in the tasks of characterization, evaluation and motivation. An organization scheme is proposed for separating the project-specific focus from the organization's learning and reuse focuses of software development. The implications of this approach for corporations, research and education are discussed and some research activities currently underway at the University of Maryland that support this approach are presented

Software development predictors, error analysis, reliability models and software metric analysis

The use of dynamic characteristics as predictors for software development was studied. It was found that there are some significant factors that could be useful as predictors. From a study on software errors and complexity, it was shown that meaningful results can be obtained which allow insight into software traits and the environment in which it is developed. Reliability models were studied. The research included the field of program testing because the validity of some reliability models depends on the answers to some unanswered questions about testing. In studying software metrics, data collected from seven software engineering laboratory (FORTRAN) projects were examined and three effort reporting accuracy checks were applied to demonstrate the need to validate a data base. Results are discussed

Integrating automated support for a software management cycle into the TAME system

Software managers are interested in the quantitative management of software quality, cost and progress. An integrated software management methodology, which can be applied throughout the software life cycle for any number purposes, is required. The TAME (Tailoring A Measurement Environment) methodology is based on the improvement paradigm and the goal/question/metric (GQM) paradigm. This methodology helps generate a software engineering process and measurement environment based on the project characteristics. The SQMAR (software quality measurement and assurance technology) is a software quality metric system and methodology applied to the development processes. It is based on the feed forward control principle. Quality target setting is carried out before the plan-do-check-action activities are performed. These methodologies are integrated to realize goal oriented measurement, process control and visual management. A metric setting procedure based on the GQM paradigm, a management system called the software management cycle (SMC), and its application to a case study based on NASA/SEL data are discussed. The expected effects of SMC are quality improvement, managerial cost reduction, accumulation and reuse of experience, and a highly visual management reporting system

Diversity as Width

It is argued that if the population of options is a finite poset, diversity comparisons may be conveniently based on widths i.e. on the respective maximum numbers of pairwise incomparable options included in the relevant subposets. The width-ranking and the undominated width-ranking are introduced and characterized

Cost Efficiency and Returns to Scope in Italian Investment Firms

This paper estimates cost efficiency and returns to scope of Italian investment firms during the period 1998-2002, following the stochastic frontier function approach. Results indicate a large inefficiency for Italian investment firms (with a high standard deviation across sample) and the absence of significant returns to scopeStochastic Frontier, Efficiency, Returns to scope, Investment Firms

Deterrence and Compliance in a Demerit Point System

This paper attempts to outline the virtues and the perverse effects of a Demerit Point System (DPS). Under a DPS, once overcome a given threshold of demerit points, infringers are punished by severe non-monetary sanctions (such as the temporarily suspension of driving license in traffic enforcement). Surprisingly, no comprehensive economic theory has been provided to support the widespread implementation of DPS. This paper tries to fill this gap. We show that the impact of a DPS depends on the distribution of preferences of the population of potential infringers. For some agents a DPS far from increasing deterrence may actually reinforce deviant behavior. Only for some group of agents, once a given threshold of accumulated penalties has been reached compliance may occur. Thus compliance is obtained only after some level of under-deterrence is tolerated. We then provide some policy suggestions in order to improve general deterrence under a DPS for any given level of detection policy. Our results seem to be consistent with available evidence.Demerit Point System, Deterrence, Compliance, Recidivism, Public Law Enforcement, Traffic Law Enforcement

Analyzing the test process using structural coverage

A large, commercially developed FORTRAN program was modified to produce structural coverage metrics. The modified program was executed on a set of functionally generated acceptance tests and a large sample of operational usage cases. The resulting structural coverage metrics are combined with fault and error data to evaluate structural coverage. It was shown that in the software environment the functionally generated tests seem to be a good approximation of operational use. The relative proportions of the exercised statement subclasses change as the structural coverage of the program increases. A method was also proposed for evaluating if two sets of input data exercise a program in a similar manner. Evidence was provided that implies that in this environment, faults revealed in a procedure are independent of the number of times the procedure is executed and that it may be reasonable to use procedure coverage in software models that use statement coverage. Finally, the evidence suggests that it may be possible to use structural coverage to aid in the management of the acceptance test processed

Measuring the software process and product: Lessons learned in the SEL

The software development process and product can and should be measured. The software measurement process at the Software Engineering Laboratory (SEL) has taught a major lesson: develop a goal-driven paradigm (also characterized as a goal/question/metric paradigm) for data collection. Project analysis under this paradigm leads to a design for evaluating and improving the methodology of software development and maintenance