Software requirements & specifications: a lexicon of practice, principles and prejudices
Software requirements & specifications: a lexicon of practice, principles and prejudices
Formal Object-Oriented Development
Formal Object-Oriented Development
Formal Methods and Object Technology
Formal Methods and Object Technology
IEEE Transactions on Software Engineering
Improving access of the commercial software developer to formal methods: integrating MERISE with Z
Methods'96 Proceedings of the 1996 international conference on Methods Integration
Mapping object diagrams into B specifications
Methods'96 Proceedings of the 1996 international conference on Methods Integration
A tale of two case studies: using integrated methods to support rigorous requirements specication
Methods'96 Proceedings of the 1996 international conference on Methods Integration
Methods'96 Proceedings of the 1996 international conference on Methods Integration
Methods'96 Proceedings of the 1996 international conference on Methods Integration
| Hi-index | 0.00 |
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.