ABSTRACT
The ProcessWall is a process state server providing storage for process states plus operations for defining and manipulating the structure of those states. It separates the state of a software process from any program for constructing that state. Instead, client programs implement the processes for operating on the process state. This approach has a number of potential benefits such as support for process formalism interoperability, support for multiple process languages, low-cost retro-fitting of process into existing environments, and support for long-term execution of processes. The process server interface provides descriptive mechanisms for representing process state as well as product state. A classification of client programs is provided to show how the state server can be used in a variety of ways.
- 1.Michael Carey et al. The EXODUS Extensible DBMS Project: an Overview. In Stan Zdonik and David Maier, editors, Readings in Object-Oriented Databases. Morgan Kaufmann, San Mateo, CA, 1990. Google ScholarDigital Library
- 2.Don Cohen. AP5 Manual. Univ. of Southern California, Information Sciences Institute, March 1988.Google Scholar
- 3.Stuart I. Feldman. Make - a program for maintaining computer programs. Software - Practice and Experience, 9:255 - 265, 1979.Google Scholar
- 4.NIST ISEE Working Group and ECMA TC33 Task Group. Reference Model for Frameworks of Software Engineering Environments. Technical Report Technical Report ECMA TR/55, 2nd Edition, ECMA & NIST, December 1991.Google Scholar
- 5.Dennis Heimbigner. Proscription Versus Prescription in Process-Centered Environments. In Proceedings of the 6th International Software Process Workshop, Hokkaido, Japan, October 1990.Google Scholar
- 6.Dennis Heimbigner. Experiences with an Object- Manager for A Process-Centered Environment. In Proceedings of the Eighteenth International Conf. on Very Large Data Bases, Vancouver, 27 August 1992. Google ScholarDigital Library
- 7.Hewlett-Packard. HP Encapsulator: ing Applications into the HP SoftBench Platform, 1989. HP Part No. B1626-90000.Google Scholar
- 8.Karen E. Huff. Plan-based intelligent assistance: An approach to supporting the software development process. Technical Report COINS Technical Report 89-97, University of Massachusetts, Amherst, September 1989. Google ScholarDigital Library
- 9.Gail E. Kaiser. Rule-Based Modeling of the Software Development Process. In Proc. 4th International Software Process Workshop, October 1988. Published in ACM SIGSOFT Software Engineering Notes, v. 14, n. 4, June, 1989. Google ScholarDigital Library
- 10.Gail E. Kaiser, Naser S. Barghouti, and Michael H. Sokolsky. Preliminary Experience with Process Modeling in the Marvel Software Development Environment Kernel. In Bruce D. Shriver, editor, 23rd Annual Hawan International Conference on System Sciences, volume II, pages 131- 140, 1990. Kona, Hawaii, January, 1990.Google ScholarCross Ref
- 11.T. Katyama, editor. Proceedings of the 6th International Software Process Workshop: Support for the Software Process. IEEE Computer Society Press, Hakodate, Hokkaido, Japan, 28-31 October 1990.Google Scholar
- 12.Marc I. Kellner et al. Software Process Modeling Example Problem. In Takuya Katayama, editor, Proceedings of the 6th Internattonai Software Process Workshop: Support for the Software Process. IEEE Computer Society Press, 1991. Hakodate, Hokkaido, Japan, October, 1990.Google Scholar
- 13.Leon J. Osterweil. Software Processes are Software Too. In Proc. Ninth International Conference on Software Engineering, 1987. Monterey, CA, March 30- April 2, 1987. Google ScholarDigital Library
- 14.Steven P. Reiss. Connecting Tools Using Message Passing in the Field Environment. IEEE Sofiware, pages 57-67, July 1990. Google ScholarDigital Library
- 15.S. M. Sutton Jr. et al. Programming a Software Requirements Specification Process, In Proceedings of the First International Conference on the Software Process, Redondo Beach, CA, October 1991.Google ScholarCross Ref
- 16.Stanley M. Sutton, Jr. APPL/A: A Prototype Language for Software-Process Programmmg. PhD thesis, University of Colorado, August 1990. Google ScholarDigital Library
- 17.Ian Thomas, editor. Preprints for the 7th International Software Process Workshop. Rocky Mountain Institute of Software Engineering, Younteville, Ca.,15-18 October 1991.Google Scholar
Index Terms
- The ProcessWall: a process state server approach to process programming
Recommendations
The ProcessWall: a process state server approach to process programming
The ProcessWall is a process state server providing storage for process states plus operations for defining and manipulating the structure of those states. It separates the state of a software process from any program for constructing that state. ...
Performance evaluation of new methods of automatic redirection for load balancing of Apache servers distributed in the Internet
LCN '00: Proceedings of the 25th Annual IEEE Conference on Local Computer NetworksAn overloaded web server will lose incoming requests resulting in a "404 error" appearing at a client browser. Front-end application-level switches can redirect requests to less loaded servers. However, there exist no native methods within common web ...
Energy-aware passive replication of processes
In information systems, processes requested by clients have to be performed on servers so that not only QoS (quality of service) requirements like response time are satisfied but also the total electric power consumed by servers to perform processes has ...
Comments