There is, I think, something ethereal about i —the square root of minus one. I remember first hearing about it at school. It seemed an odd beast at that time—an intruder hovering on the edge of reality.

Usually familiarity dulls this sense of the bizarre, but in the case of i it was the reverse: over the years the sense of its surreal nature intensified. It seemed that it was impossible to write mathematics that described the real world in …

I and i

物件導向軟體之架構(Object-Oriented Software Construction)探討

Organizational learning II: Theory, method and practice

Like other sciences and engineering disciplines, software engineering requires a cycle of model building, experimentation, and learning. Experiments are valuable tools for all software engineers who are involved in evaluating and choosing between different methods, techniques, languages and tools. The purpose of Experimentation in Software Engineering is to introduce students, teachers, researchers, and practitioners to empirical studies in software engineering, using controlled experiments. The introduction to experimentation is provided through a process perspective, and the focus is on the steps that we have to go through to perform an experiment. The book is divided into three parts. The first part provides a background of theories and methods used in experimentation. Part II then devotes one chapter to each of the five experiment steps: scoping, planning, execution, analysis, and result presentation. Part III completes the presentation with two examples. Assignments and statistical material are provided in appendixes. Overall the book provides indispensable information regarding empirical studies in particular for experiments, but also for case studies, systematic literature reviews, and surveys. It is a revision of the authors book, which was published in 2000. In addition, substantial new material, e.g. concerning systematic literature reviews and case study research, is introduced. The book is self-contained and it is suitable as a course book in undergraduate or graduate studies where the need for empirical studies in software engineering is stressed. Exercises and assignments are included to combine the more theoretical material with practical aspects. Researchers will also benefit from the book, learning more about how to conduct empirical studies, and likewise practitioners may use it as a cookbook when evaluating new methods or techniques before implementing them in their organization.

Experimentation in Software Engineering

Since DeLone and McLean (D&M) developed their model of IS success, there has been much research on the topic of success as well as extensions and tests of their model. Using the technique of a qualitative literature review, this research reviews 180 papers found in the academic literature for the period 1992–2007 dealing with some aspect of IS success. Using the six dimensions of the D&M model – system quality, information quality, service quality, use, user satisfaction, and net benefits – 90 empirical studies were examined and the results summarized. Measures for the six success constructs are described and 15 pairwise associations between the success constructs are analyzed. This work builds on the prior research related to IS success by summarizing the measures applied to the evaluation of IS success and by examining the relationships that comprise the D&M IS success model in both individual and organizational contexts.

https://link.springer.com/content/pdf/10.1057%2Fejis.2008.15.pdf

Measuring information systems success: models, dimensions, measures, and interrelationships

The authors report the results of an empirical research project on the consistency and limitations of the number of function points as an a priori measure of system size rather than the traditional lines-of-code measure. They conclude that function points are a more consistent a priori measure of system size. The results also indicate that the function-point estimate of size is lower for analysts experienced both in software development and in function-point estimation. >

Function points in the estimation and evaluation of the software process

User-led development is gaining popularity with organizations wishing to increase user involvement and control. Typically in this approach a small group of users is given the responsibility for managing the project and representing the user community in determining requirements, testing, training, and system implementation. This paper explores the end user's perception of the quality of his or her representation and satisfaction with the application system within an organization employing user-led development. The end-user communities for two systems developed in a large Australian government corporation were surveyed. The results indicate that the user perception of representation is the most significant influence on user satisfaction-the correlation scores for the two systems studied were in excess of 0.6. Also of importance is the user's perception of management support. Both systems recorded a low average score for user representativeness (2.5 and 2.7), which is attributed in part to the large number and geographic spread of the users and to the approach adopted by the user representatives in the user-led development team.

Exploring individual user satisfaction within user-led development

In some areas of software engineering research, there are several metamodels claiming to capture the main issues. Though it is profitable to have variety at the beginning of a research field, after some time, the diversity of metamodels becomes an obstacle, for instance to the sharing of results between research groups. To reach consensus and unification of existing metamodels, metamodel-driven software language engineering can be applied. This paper illustrates an application of software language engineering in the agent-oriented software engineering research domain. Here, we introduce a relatively generic agent-oriented metamodel whose suitability for supporting modeling language development is demonstrated by evaluating it with respect to several existing methodology-specific metamodels. First, the metamodel is constructed by a combination of bottom-up and top-down analysis and best practice. The concepts thus obtained and their relationships are then evaluated by mapping to two agent-oriented metamodels: TAO and Islander. We then refine the metamodel by extending the comparisons with the metamodels implicit or explicit within five more extant agent-oriented approaches: Adelfe, PASSI, Gaia, INGENIAS, and Tropos. The resultant FAML metamodel is a potential candidate for future standardization as an important component for engineering an agent modeling language.

/pdf/faml-a-generic-metamodel-for-mas-development-48dli68wlg.pdf

FAML: A Generic Metamodel for MAS Development

Collaboration between industry and academia supports improvement and innovation in industry and helps to ensure industrial relevance in academic research. This article presents an exploratory study of the factors for successful collaboration between industry and academia in software research.

/pdf/the-success-factors-powering-industry-academia-collaboration-p32n2e7u9d.pdf

The Success Factors Powering Industry-Academia Collaboration

http://tavana.us/publications/IJPM-DEA.pdf

Graham Low

Papers

Function points in the estimation and evaluation of the software process

Exploring individual user satisfaction within user-led development

FAML: A Generic Metamodel for MAS Development

The Success Factors Powering Industry-Academia Collaboration

A methodology for selecting portfolios of projects with interactions and under uncertainty