
5th ISPW 1989: Kennebunkport, Maine, USA
- Dewayne E. Perry:
Proceedings of the Fifth International Software Process Workshop (ISPW '89), October 1989, Kennebunkport, Maine, USA. IEEE Computer Society 1989, ISBN 0-8186-2104-4 - Robert Balzer:
Tolerating inconsistency. 41-42 - Barry W. Boehm, Frank C. Belz:
Experiences with the spiral model as a process model generator. 43-45 - David Carr, Ron Koestler:
System dynamics models of software development. 46-48 - Thomas E. Cheatham Jr.:
Process programing and process model. 49-51 - Bill Curtis, Diane B. Walz, Joyce J. Elam:
Studying the process of software design teams. 52-53 - Wolfgang Deiters, Volker Gruhn, Wilhelm Schäfer:
Process programming: a structured multi-paradigm approach could be achieved. 54-57 - Peter H. Feiler:
Software process support through software configuration management. 58-60 - Anthony Finkelstein:
A structural framework for the formal representation of cooperation. 61-63 - David Garlan:
The role of formalized domain-specific software frameworks. 64-66 - Dennis Heimbigner:
P4: a logic language for process programming. 67-70 - Karen E. Huff:
Software process instatiation and the planning paradigm. 71-73 - Watts S. Humphrey:
Modelling implications of the personal software process. 74-77 - Takuya Katayama, Masato Suzuki:
Mechanisms for software process dynamics. 78-81 - Gail E. Kaiser:
Experience with marvel. 82-84 - Marc I. Kellner:
Experience with enactable software process models. 85-88 - Kouichi Kishida:
Position paper for ISPW. 89-90 - M. M. Lehman:
The role of process models in software and systems development and evolution. 91-94 - Yoshihiro Matsumoto, Kiyoshi Agusa, Tsuneo Ajisaka:
A software process model based on unit workload network. 95-97 - Naftaly H. Minsky:
Law-governed software processes. 98-100 - Ataru T. Nakagawa, Kokichi Futatsugi:
Product-based process models. 101-105 - Tsuyoshi Nakajima:
A method for recording and analyzing design processes. 106-108 - Leon J. Osterweil:
Experiences with process programming. 109-111 - Manuel H. Penedo:
Acquiring experiences with executable process models. 112-115 - Samuel T. Redwine Jr.:
Software process dependability. 116-120 - Steven P. Reiss:
Conceptual programming. 121-123 - Clive Roberts, A. Jones:
Dynamics of process models in PML. 124-126 - H. Dieter Rombach:
Specification of software process measurement. 127-129 - Walt Scacchi:
Experiences with operational software process modelling in the system factory project. 130-133 - Yasuhiro Sugiyama, Ellis Horowitz:
OPM: an object process modelling environment. 134-136 - Ian Thomas:
The software process as a goal-directed activity. 137-139 - Jack C. Wileden:
Experiments with typing in process modelling. 140-144 - Pamela Zave:
Domain understanding and the software process. 145-150 - Anthony Finkelstein:
An example of software development modelling. 151-153 - Dennis Heimbigner:
An example P4 process program for rebus. 154-155 - Karen E. Huff:
GRAPPLE example: processes as plans. 156-158 - Gail E. Kaiser:
Marvel strategy language example. 159-160 - Takuya Katayama, Masato Suzuki:
An example of process description in HFSP. 161-162 - Marc I. Kellner:
software process modelling example. 163-166 - Yoshihiro Matsumoto, Tsuneo Ajisaka:
An example of a software process model based on Unit workload network. 167-168 - Leon J. Osterweil:
Example process program code, coded in Appl/A. 169-170 - Yasuhiro Sugiyama, Ellis Horowitz:
Describing working environments in OPM. 171-174

manage site settings
To protect your privacy, all features that rely on external API calls from your browser are turned off by default. You need to opt-in for them to become active. All settings here will be stored as cookies with your web browser. For more information see our F.A.Q.