About
43
Publications
11,292
Reads
How we measure 'reads'
A 'read' is counted each time someone views a publication summary (such as the title, abstract, and list of authors), clicks on a figure, or views or downloads the full-text. Learn more
4,940
Citations
Publications
Publications (43)
Many project risks in distributed software development are very different from the ones in collocated development and therefore are often overlooked. At the same time, they depend to a large extent on project-specific characteristics. This article presents a model for identifying risks early in a project. This model systematically captures experien...
Models for effort and cost estimation are important for distributed software development as well as for collocated software and system development. Standard cost models only insufficiently consider the characteristics of distributed development such as dissimilar abilities at the different sites or significant overhead due to remote collaboration....
The allocation of tasks can be seen as a success-critical management activity in distributed development projects. However, such task allocation is still one of the major challenges in global software development due to an insufficient understanding of the criteria that influence task allocation decisions. This article presents a qualitative study...
Today, software-intensive systems are increasingly being developed in a glob- ally distributed way. However, besides its benefit, global development also bears a set of risks and problems. One critical factor for successful project man- agement of distributed software development is the allocation of tasks to sites, as this is assumed to have a maj...
Software inspections, reviews, and walkthroughs have become a standard process component in many software development domains. Maturity level 3 of the CMM-I requires establishment of peer reviews [12] and substantial sustained improvements in quality and productivity have been reported as a result of using reviews ([16], [21], [22], [27]). The NSF...
Distributing development tasks in the context of global software development bears both many risks and many opportunities. Nowadays, distributed development is often driven by only a few factors or even just a single factor such as workforce costs. Risks and other relevant factors such as workforce capabilities, the innovation potential of differen...
Humans are getting permanently older. Age-related disabilities and diseases increase dramatically with growing age, and often force the respective persons to continue their life in nursing homes. Can ambient-intelligent technology help to extend a self-conducted life of elderly people in their own homes? This article attempts to provide answers to...
The session was structured into fours parts:
1
Two presentations, which addressed the use of empirical validation in software engineering.
1
Two presentations about exploratory versus confirmatory experiments.
1
A working session, which addressed questions that arose from the presentations and which involved splitting into three working groups to...
This paper first reasons on understanding software frameworks for defect detection, and then presents an experimental research for comparing the effectiveness and defect detection rate of code-reading techniques, once applied to C++ coded object-oriented frameworks. We present and discuss the functionality-based approach to framework understanding....
Reuse of products, processes, and experience originating from the system life cycle is seen today as a feasible solution to the problem of developing higher quality systems at a lower cost. In fact, quality improvement is very often achieved by repeatedly reusing and modifying the same elements, learning about them by direct experience.
This articl...
As with any engineering discipline, software development requires a measurement mechanism for feedback and evaluation. Measurement supports creating a corporate memory and is an aid in answering a variety of questions associated with the enactment of any software process. Measurement also helps, during the course of a project, to assess its progres...
Intellectual control over software development projects requires the existence of an integrated set of explicit models of the products to be developed, the processes used to develop them, the resources needed, and the productivity and quality aspects involved. In recent years the development of languages, methods and tools for modeling software pro...
Although software engineers generally agree that software measurement must be goal oriented, little has been published on the results of shifting to goal-orientation and still less on how to systematically make that transition. Thus, when we at Schlumberger RPS decided to adopt the Goal/Question/Metric approach, we resolved to document each step an...
Intellectual control over software development projects requires the existence of an integrated set of explicit models of the products to be developed, the processes used to develop them, the resources needed, and the productivity and quality aspects involved. In recent years the development of languages, methods and tools for modeling software pro...
This paper gives a solution in MVP--L to the Software Process Modeling Example Problem that was presented at the 7th International Software Process Workshop. MVP--L is a prototype process specification and design language developed as part of the MVP project at the University of Maryland. The solution presented here is a revision of the solution su...
This paper contains a solution to the Software Process Modeling Example Problem in MVPL1, intended for presentation and discussion at the 6th International Software Process Workshop in Hakodate, Japan, in October 1990. MVP-L1 is a prototype process modeling language developed as part of the MVP project at the University of Maryland. The discussion...
Techniques for detecting defects in source code are fundamental to the success of any software development approach. A software development organization therefore needs to understand the utility of techniques such as reading or testing in its own environment. Controlled experiments have proven to be an effective means for evaluating software engine...
Software development organizations are beginning to recognize that measurement is a prerequisite for systematic process improvement, and have started to measure their products and processes in order to understand, analyze, plan, and guide their projects. Successful measurement requires a solid understanding of the products, processes, and resources...
Developing and maintaining software systems involves a variety of highly interrelated activities. The discipline of software engineering studies processes of both product engineering and process engineering. Product engineering aims at developing software products of high quality at reasonable cost. Process engineering in contrast aims at choosing...
ion Sheet GQM plan quality model hypothesis data representation question metrics hypothesis data representation question metrics process/product definition 89 A Process Model for GQM-Based Measurement STTI-95-04-E A Detailed View on the GQM Process Deriving questions for the process or product definition The first step is to check the completeness...
Intellectual control over software development projects requires the existence of an integrated set of explicit models of the products to be developed, the processes used to develop them, the resources needed, and the productivity and quality aspects involved. In recent years the development of languages, methods and tools for modeling software pro...
All software projects are experiments in the sense of the
scientific method because the outcomes are not known in advance,
theories and hypotheses may be tested in the project empirically, and
data must be collected and analyzed. Empirical data allows us to
characterize projects, gauge improvements in an environment, and reason
about the value of n...
As with any engineering discipline, software development requires a measurement mechanism for feedback and evaluation. Measurement is a mechanism for creating a corporate memory and an aid in answering a variety of questions associated with the enactment of any software process. It helps support project planning (e. g., How much will a new project...
As first steps towards establishing software engineering as an engineering discipline, we need to create explicit models of its building blocks, i.e., projects, processes, products, and various quality perspectives; organize these models for effective reuse across project boundaries, and establish measurable criteria for project guidance. The paper...
An experimental framework for assessing process formalisms from
project members' points of view is proposed. This framework is based on
the goal/question/metric paradigm and uses role definitions to state the
assessment goals. The assessment goals are then used to identify the
information that must be supplied by a formalism to support a project
ro...
We have only begun to understand the experimental nature of software engineering, the role of empirical studies and measurement within software engineering, and the mechanisms needed to apply them successfully. This volume presents the proceedings of a workshop whose purpose was to gather those members of the software engineering community who supp...
Experience from a dozen years of analyzing software engineering processes and products is summarized as a set of software engineering and measurement principles that argue for software engineering process models that integrate sound planning and analysis into the construction process. In the TAME (Tailoring A Measurement Environment) project at the...
This paper gives an overview of the INCAS (INCremental Architecture for distributed Systems) multicomputer project, which aims at the development of a comprehensive methodology for the design and implementation of locally distributed systems. A structuring concept for distributed operating systems has been developed and integrated into the system i...
This paper presents a methodology for improving the software process by tailoring it to the specific project goals and environment. This improvement process is aimed at the global software process model as well as methods and tools supporting that model. The basic idea is to use defect profiles to help characterize the environment and evaluate the...
this document. The described process model is based on the experiences of the partners gained in the ESSI-project CEMP to a great extent. For the exchange of experiences we would like to thank Helmut Woda from Robert Bosch GmbH, Frank van Latum, Erik Rodenbach, Rini van Solingen from Schlumberger RPS, Markku Oivo from Schlumberger SMR, Stefano Cint...
Software-Projekte bestehen aus einer Vielzahl von Teil- aufgaben, die durch komplexe Wechselbeziehungen mit- einander verknüpft sind. Systematische Unterstützung bei der Durchführung von Software-Projekten erfordert des- halb nicht nur die isolierte Unterstützung einzelner Teil- aufgaben, sondern insbesondere der Wechselbeziehungen. Ziel des MVP-Pr...