The Evolving Philosophers Problem: Dynamic Change Management
IEEE Transactions on Software Engineering
A framework for dynamic reconfiguration of distributed programs
A framework for dynamic reconfiguration of distributed programs
A methodology for prototyping-in-the-large
ICSE '91 Proceedings of the 13th international conference on Software engineering
Prototyping in industrial software projects—bridging the gap between theory and practice
ICSE '93 Proceedings of the 15th international conference on Software Engineering
Prototyping interactive information systems
Communications of the ACM
Dynamic Software Reconfiguration Supports Scientific Problem-solving Activities
Proceedings of the IFIP TC2/WG 2.5 Working Conference on Programming Environments for High-Level Scientific Problem Solving
| Hi-index | 0.00 |
Prototyping is a means by which requirements for software projects can be defined and refined before they are committed to firm specifications for the finished software product. By this process, costly and time-consuming errors in specification can be avoided or minimized. Reconfiguration is the concept of altering the program code, bindings between program modules, or logical or physical distribution of software components while allowing the continuing execution of the software being changed. Combining these two notions suggests the potential for a development environment where requirements can be quickly and dynamically evolved. This paper discusses reconfiguration-based prototyping (RBP), that is, the simultaneous consideration of requirements, software behavior and user feedback within a running system in order to derive a clear specification of an intended product. Tools enabling RBP can coordinate the efforts of developers, users and subject matter specialists alike as they work toward consensus on an application's specification by means of a prototype.