Results 1 - 10
of
10
Knowledge Based Techniques to Increase the Flexibility of Workflow Management
- Data and Knowledge Engineering, North-Holland
, 1997
"... This paper describes how knowledge-based techniques can be used to overcome problems of workflow management in engineering applications. Using explicit process and product models as a basis for a workflow interpreter allows to alternate planning and execution steps, resulting in an increased flexibi ..."
Abstract
-
Cited by 16 (0 self)
- Add to MetaCart
(Show Context)
This paper describes how knowledge-based techniques can be used to overcome problems of workflow management in engineering applications. Using explicit process and product models as a basis for a workflow interpreter allows to alternate planning and execution steps, resulting in an increased flexibility of project coordination and enactment. To gain the full advantages of this flexibility, change processes have to be supported by the system. These require an improved traceability of decisions and have to be based on dependency management and change notification mechanisms. Our methods and techniques are illustrated by two applications: Urban land-use planning and software process modeling. 1 Motivation On account of global competition, the efficiency of business processes has to be improved, resulting in a reduction of process requirements in terms of time and cost. This business objective leads to approaches as lean management and business process reengineering & optimization. In ord...
Process-Oriented Knowledge Management For Learning Software Organizations
- Proceedings of 12th Knowledge Acquisition For Knowledge-Based Systems Workshop 1999 (KAW99
, 1999
"... This paper discusses how a process-centered knowledge management and coordination support approach can be used to create learning software organizations. We discuss how process models can be used in project planning and how project plans can be enacted. Then we illustrate how a feedback loop can be ..."
Abstract
-
Cited by 14 (1 self)
- Add to MetaCart
This paper discusses how a process-centered knowledge management and coordination support approach can be used to create learning software organizations. We discuss how process models can be used in project planning and how project plans can be enacted. Then we illustrate how a feedback loop can be created to update the process model stored in an experience factory. The result is a knowledge management approach that is process-oriented and supports continuous process improvement. 1. INTRODUCTION Creating effective knowledge management structures is one of the key factors in software process improvement initiatives (like the Capability Maturity Model, Spice, Trillium, etc.). Most often the knowledge management needs are only mentioned implicitly. Specific organizational structures (e. g. a software process group) are developed for the purpose of managing and distributing knowledge about software development. These structures are costly to maintain and improving the efficiency of their...
Graph-Based Software Process Management
, 1997
"... this paper mainly focuses on the underlying formal specification. In fact, DYNAMITE is a sophisticated practical application of graph rewriting. Thus, we describe our specification approach in some detail and discuss its advantages and shortcomings. In Sec. 2, we introduce dynamic task nets informal ..."
Abstract
-
Cited by 9 (5 self)
- Add to MetaCart
this paper mainly focuses on the underlying formal specification. In fact, DYNAMITE is a sophisticated practical application of graph rewriting. Thus, we describe our specification approach in some detail and discuss its advantages and shortcomings. In Sec. 2, we introduce dynamic task nets informally. Sec. 3, which constitutes the main part of this paper, presents and discusses the formal specification. Related work is compared in Sec. 4, and a short conclusion is given in Sec. 5.
Integrating Process Support and Knowledge Management for Virtual Software Development Teams
- Annals of Software Engineering
, 2002
"... In this paper we describe how knowledge management and software process support can be integrated to improve the efficiency of virtual software teams. The approach presented here integrates a process enactment environment with an on-demand knowledge delivery strategy that is based on parameterized i ..."
Abstract
-
Cited by 9 (0 self)
- Add to MetaCart
(Show Context)
In this paper we describe how knowledge management and software process support can be integrated to improve the efficiency of virtual software teams. The approach presented here integrates a process enactment environment with an on-demand knowledge delivery strategy that is based on parameterized information needs models. The parameters in the information needs models are bound at project execution time to values extracted from the process enactment engine. Thus, the approach supports virtual teams by establishing a platform for systematic and task-specific knowledge exchange. The proposed approach is prototypically implemented in the MILOS system, an open source project of the University of Calgary (Canada) and the University of Kaiserslautern (Germany).
Rationale Support for Maintenance of Large Scale Systems
- In Workshop on Evolution of Large-Scale Industrial Software Applications (ELISA), ICSM '03
, 2003
"... Software maintenance has long been one of the most difficult and expensive phases of the software life-cycle. Maintenance is especially difficult for large-scale systems. The more code involved, the larger the chance that there may be unexpected interactions that may cause problems when updates and ..."
Abstract
-
Cited by 4 (0 self)
- Add to MetaCart
(Show Context)
Software maintenance has long been one of the most difficult and expensive phases of the software life-cycle. Maintenance is especially difficult for large-scale systems. The more code involved, the larger the chance that there may be unexpected interactions that may cause problems when updates and corrections are made during maintenance. The large number of developers who were probably involved at various points in the system’s creation means that it is likely to be difficult to answer questions about the intent behind the design and implementation decisions. The designer’s, or developer’s, intent can be captured as their Design Rationale. Unlike standard design documentation, which is a description of the final design, Design Rationale (DR) offers more: not only the decisions, but also the reasons behind each decision, including its justification, other alternatives considered, and argumentation leading to the decision. To drive and evaluate our research into using rationale for software maintenance, we are developing the SEURAT (Software Engineering Using RATionale) system to support the software maintainer. This system will present the relevant DR when required and allow entry of new rationale for the modifications. The new DR will then be verified against the existing DR to check for inconsistencies. There are several types of inferences that should be made: structural inferences to ensure that the rationale is complete, evaluation, to ensure that it is based on well-founded arguments, and comparison to rationale collected previously for similar modifications to see if the same reasoning was used.
The REMIS Approach for Rationale-Driven Process Model Evolution
- Proceedings of Software Process Scoping Software Process Models - Initial Concepts and Experience from Defining Space Standards 13 Dynamics and Agility. International Conference on Software Process (ICSP'2007
, 2007
"... Abstract. In dynamic and constantly changing business environments, the need to rapidly modify and extend the software process arises as an important issue. Reasons include redistribution of tasks, technology changes, or required adherence to new standards. Changing processes ad-hoc without consider ..."
Abstract
-
Cited by 4 (2 self)
- Add to MetaCart
(Show Context)
Abstract. In dynamic and constantly changing business environments, the need to rapidly modify and extend the software process arises as an important issue. Reasons include redistribution of tasks, technology changes, or required adherence to new standards. Changing processes ad-hoc without considering the underlying rationales of the process design can lead to various risks. Therefore, software organizations need suitable mechanisms for storing and visualizing the rationale behind process model design decisions in order to optimally introduce future changes into their processes. This paper presents REMIS (Rationale-driven Evolution and Management Information System), a prototype tool we have developed for providing support to process engineers during the task of collecting the reasons for process changes, introducing the changes, and storing them together in a process model evolution repository. Additionally, we present lessons learned with REMIS during the evolution of a reference process model for developing service-oriented applications.
Process-Centered Knowledge Organization for Software Engineering
- In (Aha & Mu��oz-Avila
, 1999
"... This paper argues for using process models as the primary means to structure and organize knowledge in software organizations. We discuss how process models can support project planning and illustrate how a process-centered organization of knowledge helps the individual developer to find appropriate ..."
Abstract
-
Cited by 2 (0 self)
- Add to MetaCart
This paper argues for using process models as the primary means to structure and organize knowledge in software organizations. We discuss how process models can support project planning and illustrate how a process-centered organization of knowledge helps the individual developer to find appropriate background information for his current task during process enactment. The paper concludes with an overview on our MILOS system: a process-centered, Internet-based, knowledge management and process support environment.
Charles J. Petrie Automated Configuration Problem Solving – Monograph –
, 2012
"... Automated Configuration has long been the subject of intensive research, especially in Artificial Intelligence, as it is a pervasive problem to be solved and is a good test of various knowledge representation and reasoning techniques. The problem itself shows up in applications as various as electri ..."
Abstract
- Add to MetaCart
(Show Context)
Automated Configuration has long been the subject of intensive research, especially in Artificial Intelligence, as it is a pervasive problem to be solved and is a good test of various knowledge representation and reasoning techniques. The problem itself shows up in applications as various as electrical circuit design, utility computing, and even concurrent engineering. We define this ubiquitous problem and show the various solution techniques. We survey about twenty years of these techniques, from the mid 70’s until the mid-90’s. During this time, various general approaches were developed, as well as more specialized techniques. We survey the development of the general problem solving techniques for automated configuration, based on both published academic work and patents. This book is intended to be an introduction to the topic and a gateway to more detailed descriptions of configuration technology while presenting a possibly different perspective in some regards and covering previously overlooked material, especially the commercial development of configuration technology. This was discovered
Feedback Handling in Dynamic Task Nets
, 1997
"... While a software process is being executed, many errors and problems occur which require to reconsider previously executed process steps. In order to handle feedback in a process-centered software engineering environment, several requirements need to be addressed (adaptability, human intervention, i ..."
Abstract
- Add to MetaCart
While a software process is being executed, many errors and problems occur which require to reconsider previously executed process steps. In order to handle feedback in a process-centered software engineering environment, several requirements need to be addressed (adaptability, human intervention, impact analysis, change propagation, restoration of the work context, and traceability). Feedback management in DYNAMITE meets these requirements. DYNAMITE is based on dynamic task nets and specifically supports feedback through feedback relations, task versions, and customized semantics of data flows. A methodology for feedback handling is also represented. A programmed graph rewriting system serves to specify analysis, planning, and enactment --- which may be interleaved seamlessly --- in a uniform formal framework. Keywords: Software process management, feedback handling, graph rewriting 1 Introduction It has been recognized by many researchers that software processes are highly dynamic ...
Researching Under Uncertainty 1 Design Rationale: Researching Under Uncertainty
"... Abstract. Rationale research in software development is a challenging area because while there is no shortage of advocates for its value, there is also no shortage of reasons for why rationale is unlikely to be captured in practice. Despite more than thirty years of research there still remains much ..."
Abstract
- Add to MetaCart
Abstract. Rationale research in software development is a challenging area because while there is no shortage of advocates for its value, there is also no shortage of reasons for why rationale is unlikely to be captured in practice. Despite more than thirty years of research there still remains much uncertainty—how useful are the potential benefits and how insurmountable are the barriers? Will the value of the rationale (design and otherwise) justify the cost of collecting it? While there have been numerous rationale research projects, many, if not most, received little or no empirical evaluation. There also have not been many studies examining what the needs are of the practitioners who would be supported by the rationale. This paper discusses the “doom and gloom ” predictions of rationale’s failure, provides a survey of evaluations of rationale systems, and discusses what we hope is a brighter outlook for rationale research in the future. There are development standards and synergistic research areas that may help with rationale research and its acceptance in the software community that we should be working with. This paper also presents the results of a pilot survey of software developers who were asked how they would envision using rationale and what they believe the most important barriers are. While some results were as expected, there were some surprises too. Research on technology transfer indicates that, among other things, to transition successfully from research into practice we need to understand the need that is being met and demonstrate the value of our approach. Until we have determined how our work is needed by the people we are trying to help we will remain researching under uncertainty.
