Methods integration: time for reflection (and reorientation?)

Taking the presentations given at this workshop as a snapshot of current work on "Methods Integration" (MI), we consider current and future aspirations for the topic within the overall context of software production. There are significant differences in what has been attempted. The intellectual gulf between the types of methods which workers seek to bridge is huge. And the rationale for seeking to link them also varies widely; some try to hide any semblance of formalism, others seek to make formal methods more accessible. Whilst making undoubted progress in numerous local situations, we are, at the same time, fostering diversification. Unfortunately the substantial effort invested tends to reinforce the 'not invented here' syndrome which bodes ill for those who search for a single universal method. Once we have achieved sufficient understanding of the problems and processes involved, all should become clearer and the methods easier to use. As a small contribution in the search for simplicity we attempt rationalisation of certain key terms/procedures, and suggest how MI might be embedded within the software construction process.

[1]  Michael A. Jackson,et al.  Software requirements and specifications - a lexicon of practice, principles and prejudices , 1995 .

[2]  M. A. Lockyer,et al.  CASE support for methods integration: implementation of a translation from a structured to a formal notation , 1996 .

[3]  Hussein Zedan,et al.  Refinement of Complex Systems: A Case Study , 1995, Comput. J..

[4]  Antony Bryant,et al.  Methods integration : proceedings of the Methods Integration Workshop, Leeds, 25-26 March 1996 , 1996 .

[5]  M. M. Larrondo-Petrie,et al.  A tale of two case studies: using integrated methods to support rigorous requirements specication , 1996 .

[6]  C. H. Lindsey,et al.  ALGOL 68 with fewer tears , 1972, Comput. J..

[7]  David W. Bustard,et al.  Integrating process modelling and soft systems analysis , 1996 .

[8]  Andy Smith,et al.  Improving access of the commercial software developer to formal methods: integrating MERISE with Z , 1996 .

[9]  Laurence Duchien,et al.  A spanning tree object-oriented distributed algorithm: specification and proof , 1996 .

[10]  Robert B. France,et al.  Integrated Structured Analysis and Formal Specification Techniques , 1992, Comput. J..

[11]  Manfred Broy Mathematics of Software Engineering , 1995, MPC.

[12]  S. J. Goldsack,et al.  INTEGRATED FORMAL and OBJECT-ORIENTED METHODS: The VDM ++ Approach , 1996 .

[13]  Kaisa Sere,et al.  Data modelling in ZIM , 1996 .

[14]  T. H. Tse,et al.  NOODLE + + : a 3-dimensional Net-based Object-Oriented Development Model , 1996 .

[15]  James E. Rumbaugh,et al.  To Form a More Perfect Union: Unifying the OMT and Booch Methods , 1996, J. Object Oriented Program..

[16]  S. J. Goldsack,et al.  Formal Methods and Object Technology , 1996, Formal Approaches to Computing and Information Technology.

[17]  Régine Laleau,et al.  Mapping object diagrams into B specifications , 1996 .

[18]  Leslie Lamport,et al.  TLA in Pictures , 1995, IEEE Trans. Software Eng..

[19]  Martyn Spink,et al.  Application of Structured Analysis/Formal Design Method to a Case Study from the Nuclear Industry , 1996 .

[20]  Mark Rawson,et al.  Synthesis - An Integrated, Object-Oriented Method and Tool for Requirements Specification in Z , 1996 .

[21]  Manfred Broy,et al.  Mathematical System Models as a Basis of Software Engineering , 1995, Computer Science Today.

[22]  Richard S. Bird,et al.  Generic functional programming with types and relations , 1996, Journal of Functional Programming.

[23]  Kevin Lano,et al.  Formal object-oriented development , 1995, FACIT: Formal approaches to computing and information technology.