Abstract not found

Today’s software developments are faced with steadily increasing expectations: software has to be developed faster, better, and cheaper. At the same time, application complexity increases. Meeting these demands requires fast, continuous learning and the reuse of past experience on the part of the project teams. Thus, learning and reuse should be supported by well-defined processes applicable to all kinds of experience which are stored in an organizational memory. In this paper, we introduce a tool architecture supporting continuous learning and reuse of all kinds of experience from the software engineering domain and present the underlying methodology. 1.

. Reuse of software knowledge is a principle for improving productivity and reliability of software development. To achieve this, reuse must be done systematically. This means that processes for retrieving, reusing, revising, and retaining have to be defined. At the same time organizational issues (such as the establishment of a separate organizational unit responsible for organizational learning) must be considered. In this paper we compare software knowledge reuse models to the CBR cycle of Aamodt and Plaza [1] and show that the approaches are very similar. We suggest to extend the CBR cycle by including organizational issues explicitly and conclude that CBR is a promising technology for realizing software knowledge reuse if our suggested organizational extensions are considered. Keywords. Organizational View on CBR, Organizational Learning, Experience Factory, Quality Improvement Paradigm, Software Knowledge Reuse 1 Introduction Reuse practice appears to exhibit consid...

: This paper presents a method for evaluating and selecting off-the-self software components to be reused in software development. The paper describes the main motivation and principles of the method and provides a provides a detailed description of it. The method has been tried out in two case studies and initial results of these studies are reported. * This work has been supported by the Hughes Information Technology Corporation and the EOS Program. 2 Copyright ESEG 1995 Table of Contents 1.

The inability of software reuse to reach its full potential lies partially in the product-centric way in which we view software development. Methods are needed that help us reason about product families and degrees of support that can be offered for problem domains. This paper uses a "domain lifecycle" to formalize a process in which increasing levels of formality can be provided as a domain matures. The first step in this process is to collect and disseminate project experiences that can accelerate the process of identifying and refining application domains with significant impact in a software development organization. This approach facilitates the reuse of a broad spectrum of knowledge at multiple levels of formality. Based on empirical investigations of a software development organization, a prototype of a case-based organizational memory repository for software development practices is presented and assessed for its impact on reusing software development knowledge. Keywords: doma...

In this paper we characterize and model the cost of rework in a Component Factory (CF) organization. A CF is responsible for developing and packaging reusable software components. Data was collected on corrective maintenance activities for the Generalized Support Software reuse asset library located at the Flight Dynamics Division of NASA’S GSFC. We then constructed a predictive model of the cost of rework using the C4.5 system for generating a logical classification model. The predictor variables for the model are measures of internal software product attributes. The model demonstrates good prediction accuracy, and can be used by managers to allocate resources for corrective maintenance activities. Furthermore, we used the model to generate proscriptive coding guidelines to improve programming practices so that the cost of rework can be reduced in the future. The general approach we have used is applicable to other environments.

{hoecht} @ rhrk.uni-kl.de Abstract. Self-organized reuse of artifacts from software and system development, using the lightweight Wiki-Technology, promises a sustainable preservation and availability of business-critical information. However, due to the organic, sometimes chaotic growth of content inside a Wiki, additional support for structuring the knowledge and finding interrelated useful content is needed. The enhancement of Wiki content with ontologies – named semantic Wikis- can solve these problems. The application of such semantic Wikis and the development of reasoning mechanisms for software engineering is subject of the project RISE (Reuse in Software Engineering).

Today's software developments are faced with steadily increasing expectations: software has to be developed faster, better, and cheaper. At the same time, application complexity increases. Meeting these demands requires fast, continuous learning and the reuse of experience on the part of the project teams. Thus, learning and reuse should be supported by well-defined processes applicable to all kinds of experience which are stored in an organizational memory. In this paper, we introduce a tool architecture supporting continuous learning and reuse of all kinds of experience from the software engineering domain and present the underlying methodology.

Software developers and project managers are struggling to assess the appropriateness of agile processes to their development environments. This paper identifies limitations that apply to many of the published agile processes in terms of the types of projects in which their application may be problematic.

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. This paper investigates the possibilities of providing measurement-based project guidance using explicit project plans. Following a summary of technologies developed by the process modeling and measurement subcommunities of software engineering, a method for integrating these technologies is suggested, and the potential benefits for project guidance are discussed. Examples from the MVP Project at the University of Kaiserslautern are used throughout for illustration purposes. Keywords: improvement-oriented engineering model, measurement, explicit models, project modeling, project guidance. 1 Introduction Software development and maintenance projects a...