Development methodologies for event and message based application systems
Very few of the existing software analysis and design methodologies provide a facility for developing and specifying system components containing cooperating parallel processes. In this paper we develop a general specification technique which allows to precisely describe processes, process-classes, events and messages.
The proposed methodology is based on Petri Nets which have been extended with higher level concepts to allow the straight forward specification of processes and their cooperation and to avoid the principle problem of Petri Nets, i.e. the large complexity of such nets when specifying even simple mechanisms.
Care has been taken to provide for the adaption of the many formal analysis principles available for Petri Nets to the proposed technique. The development, design and specification technique is then used to extend four of the most popular design methodologies — Jackson, SADT, HIPO and Nassi Shneiderman — with process and event/message specification facilities.
KeywordsControl Flow Detailed Design Process Class Control Flow Mechanism Control Flow Technique
Unable to display preview. Download preview PDF.
- 1.Ross, D.T.: Structured Analysis: A Language for Communicating Ideas. IEEE Trans. on Software Eng. 3(1), 1977Google Scholar
- 2.Lundeberg, M., Goldkuhl, G., Nilsson, A.: A Systematic Approach to System Development. Information Systems 4(1), 1979Google Scholar
- 3.Jackson, M.: Principles of Program Design. Academic Press, London, 1975Google Scholar
- 4.Nassi, I., Shneiderman, B.: Flowchart Technique for Structured Programming. ACM Sigplan Notices, 8(8), 1973Google Scholar
- 5.Peterson, J.L.: Petri Nets. ACM Computing Surveys, 9(3), 1977Google Scholar
- 6.Genrich, H.J., Lautenbach, K.: System Modelling with High-Level Petri Nets. J.of Theor. Comp. Science, 13(2), 1981Google Scholar
- 7.ITT Corp.: Software Development Tools — SAFP2 Documentation. ITT Doc. No. 723 ITT 01011, 1980Google Scholar
- 8.IBM Corp.: HIPO — A Design Aid and Documentation Technique. IBM GC 20–1851, 1974Google Scholar