The viable system model for software

We are investigating the application of Beer’s Viable System Model to the development of software for “complex” applications. We use this model as the basis for a component system architecture, the Viable System Architecture. A key construct of the architecture is the structure of a component and its special set of interfaces, a “viable component.” After presenting the Viable System Model and the Viable System Architecture, we outline a design methodology for development of software components in this approach.

[1]  J. R. Beaumont.  Diagnosing the System for Organizations , 1985 .

[2]  John Derrick,et al.  Formalising ODP enterprise policies , 1999, Proceedings Third International Enterprise Distributed Object Computing. Conference (Cat. No.99EX366).

[3]  Stephen Yurkovich,et al.  Fuzzy Control , 1997 .

[4]  Peter Checkland,et al.  Diagnosing the system for organizations: S. BEER Wiley, Chichester, 1985, 152 + xiii pages, £7.50 , 1986 .

[5]  Charles Herring,et al.  Cybernetic Components: A Theoretical Basis for Component Software Systems , 1998 .

[6]  Gene F. Franklin,et al.  Feedback Control of Dynamic Systems , 1986 .

[7]  Simon M. Kaplan,et al.  Viable systems: the control paradigm for software architecture revisited , 2000, Proceedings 2000 Australian Software Engineering Conference.

[8]  Simon M. Kaplan,et al.  Component-based software systems for smart environments , 2000, IEEE Wirel. Commun..

[9]  Mary Shaw,et al.  Beyond objects: a software design paradigm based on process control , 1995, SOEN.

[10]  Zoran Milosevic,et al.  Implementing B2B contracts using BizTalk , 2001, Proceedings of the 34th Annual Hawaii International Conference on System Sciences.