Abstract is missing.
- IntroductionDewayne E. Perry. 3-5 [doi]
- Review of the state-of-the-art (session summary)Watts S. Humphrey. 7-11 [doi]
- Mechanisms (session summary)Gail E. Kaiser. 13-15 [doi]
- Policies (session summary)Peter H. Feiler. 17-20 [doi]
- Data (session summary)Maria H. Penedo. 21-25 [doi]
- Control (session summary)Dewayne E. Perry. 27-31 [doi]
- Emerging issues (session summary)David Garlan. 33-38 [doi]
- Tolerating inconsistencyRobert Balzer. 41-42
- Experiences with the spiral model as a process model generatorBarry W. Boehm, Frank C. Belz. 43-45
- System dynamics models of software developmentDavid Carr, Ron Koestler. 46-48
- Process programing and process modelThomas E. Cheatham Jr.. 49-51
- Studying the process of software design teamsBill Curtis, Diane B. Walz, Joyce J. Elam. 52-53
- Process programming: a structured multi-paradigm approach could be achievedWolfgang Deiters, Volker Gruhn, Wilhelm Schäfer. 54-57
- Software process support through software configuration managementPeter H. Feiler. 58-60
- A structural framework for the formal representation of cooperationAnthony Finkelstein. 61-63
- The role of formalized domain-specific software frameworksDavid Garlan. 64-66
- P4: a logic language for process programmingDennis Heimbigner. 67-70
- Software process instatiation and the planning paradigmKaren E. Huff. 71-73
- Modelling implications of the personal software processWatts S. Humphrey. 74-77
- Mechanisms for software process dynamicsTakuya Katayama, Masato Suzuki. 78-81
- Experience with marvelGail E. Kaiser. 82-84
- Experience with enactable software process modelsMarc I. Kellner. 85-88
- Position paper for ISPWKouichi Kishida. 89-90
- The role of process models in software and systems development and evolutionM. M. Lehman. 91-94
- A software process model based on unit workload networkYoshihiro Matsumoto, K. Agusa, Tsuneo Ajisaka. 95-97
- Law-governed software processesNaftaly H. Minsky. 98-100
- Product-based process modelsAtaru T. Nakagawa, Kokichi Futatsugi. 101-105
- A method for recording and analyzing design processesTsuyoshi Nakajima. 106-108
- Experiences with process programmingLeon J. Osterweil. 109-111
- Acquiring experiences with executable process modelsManuel H. Penedo. 112-115
- Software process dependabilitySamuel T. Redwine Jr.. 116-120
- Conceptual programmingSteven P. Reiss. 121-123
- Dynamics of process models in PMLClive Roberts, A. Jones. 124-126
- Specification of software process measurementH. Dieter Rombach. 127-129
- Experiences with operational software process modelling in the system factory projectWalt Scacchi. 130-133
- OPM: an object process modelling environmentY. Sugiyama, Ellis Horowitz. 134-136
- The software process as a goal-directed activityIan Thomas. 137-139
- Experiments with typing in process modellingJack C. Wileden. 140-144
- Domain understanding and the software processPamela Zave. 145-150
- An example of software development modellingAnthony Finkelstein. 151-153
- An example P4 process program for rebusDennis Heimbigner. 154-155
- GRAPPLE example: processes as plansKaren E. Huff. 156-158
- Marvel strategy language exampleGail E. Kaiser. 159-160
- An example of process description in HFSPTakuya Katayama, Masato Suzuki. 161-162
- software process modelling exampleMarc I. Kellner. 163-166
- An example of a software process model based on Unit workload networkYoshihiro Matsumoto, Tsuneo Ajisaka. 167-168
- Example process program code, coded in Appl/ALeon J. Osterweil. 169-170
- Describing working environments in OPMY. Sugiyama, Ellis Horowitz. 171-174
- An overview of the ALF projectColin Potts. 175 [doi]
- The Arcadia research project176-177 [doi]
- ESF and software process modelingWilhelm Schäfer, P. Broekman, L. Hubert, J. Scott. 178 [doi]
- Dynamics of process models in PMLRobert A. Snowdon, Clive Roberts. 179-180 [doi]
- Summary of software designer's associates projectMasatoshi Matsuo. 181 [doi]