On the Irreducibility of Commuting Varieties of Nilpotent Matrices

Given an nxn nilpotent matrix over an algebraically closed field K, we prove some properties of the set of all the nxn nilpotent matrices over K which commute with it. Then we give a proof of the irreducibility of the variety of all the pairs (A,B) of nxn nilpotent matrices over K if either char K = 0 or char K isn't less than n/2. We get as a consequence a proof of the irreducibility of the local Hilbert scheme of n points of a smooth algebraic surface over K with the previous condition on char K.Comment: LaTex, 27 pages, to appear in J. Algebr

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

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

Models and metrics for software management and engineering

This paper attempts to characterize and present a state of the art view of several quantitative models and metrics of the software life cycle. These models and metrics can be used to aid in managing and engineering software projects. They deal with various aspects of the software process and product, including resources allocation and estimation, changes and errors, size, complexity and reliability. Some indication is given of the extent to which the various models have been used and the success they have achieved

Software Engineering Laboratory (SEL) report to the National Aeronautics and Space Administration

Software development predictors, error analysis, reliability models and software metric analysis are studied. The use of dynamic characteristics as predictors for software development is also studied

Ambiguity and uncertainty in Ellsberg and Shackle

This paper argues that Ellsberg’s and Shackle’s frameworks for discussing the limits of the (subjective) probabilistic approach to decision theory are not as different as they may appear. To stress the common elements in their theories Keynes’s Treatise on Probability provides an essential starting point. Keynes’s rejection of well-defined probability functions, and of maximisation as a guide to human conduct, is shown to imply a reconsideration of what probability theory can encompass, that is in the same vein of Ellsberg’s and Shackle’s concern in the years of the consolidation of Savage’s new probabilistic mainstream. The parallel between Keynes and the two decision theorists is drawn by means of a particular assessment of Shackle’s theory of decision, namely, it is interpreted in the light of Ellsberg’s doctoral dissertation. In this thesis, published only as late as 2001, Ellsberg developed the details and devised the philosophical background of his criticism of Savage as first put forward in the famed 1961 QJE article. The paper discusses the grounds on which the ambiguity surrounding the decision maker in Ellsberg’s urn experiment can be deemed analogous to the uncertainty faced by Shackle’s entrepreneur taking “unique decisions.” The paper argues also that the insights at the basis of the work of both Shackle and Ellsberg, as well as the criteria for decision under uncertainty they put forward, are relevant to understand the development of modern decision theory.uncertainty, weight of argument, non-additive probability

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