Towards a formal definition of methods

The absence of a formal specification of methods permits application engineers to interpret method concepts in any way they want. Further, different CASE tool designers can implement the same method concepts in different ways. The approach to formal method specification described here is in three levels: the generic level, the method independent level, and the method level. The generic level provides a model of a method which can be instantiated to yield a method-independent view of methods. This view can, in turn, be instantiated to yield the formal method of interest. The attempt is to represent methods independently of any underlying way-of-working or paradigm, remove the process/product dichtomy by tight coupling of the process and product aspects of methods, and permit extensibility of methods. The formal specification can be used as a basis for building CASE tools, as an output to be produced by a CAME tool, and for defining development processes.

[1]  K. Smolander,et al.  OPRR – A Model for Modelling Systems Development Methods , 2003 .

[2]  William E. Lorensen,et al.  Object-Oriented Modeling and Design , 1991, TOOLS.

[3]  Ivar Jacobson,et al.  Object-oriented software engineering - a use case driven approach , 1993, TOOLS.

[4]  Shamkant B. Navathe,et al.  Conceptual Database Design: An Entity-Relationship Approach , 1991 .

[5]  Arkady B. Zaslavsky,et al.  The Role of Metamodels in Federating System Modelling Techniques , 1993, ER.

[6]  S. Joosten.  Lazy functional Meta-CASE programming , 1996 .

[7]  Henk Sol,et al.  Information Systems Methodologies: A Framework for Understanding , 1988 .

[8]  David Lorge Parnas,et al.  An Invitation to Formal Methods , 1996, Computer.

[9]  M. Suzuki,et al.  Meta-Operations in the Process Model Hfsp for the Dynamics and Flexibility of Software Processes , 1991, Proceedings. First International Conference on the Software Process,.

[10]  Naveen Prakash,et al.  A Process View of Methodologies , 1994, CAiSE.

[11]  Annie I. Antón,et al.  Goal Decomposition and Scenario Analysis in Business Process Reengineering , 1994, CAiSE.

[12]  Sjaak Brinkkemper,et al.  Situational method engineering for informational system project approaches , 1994, Methods and Associated Tools for the Information Systems Life Cycle.

[13]  Gerard M. Wijers,et al.  Modelling support in information systems development , 1991 .

[14]  Colette Rolland,et al.  An Approach for Defining Ways-of-Working , 1995, Inf. Syst..

[15]  Tom Rodden,et al.  Process Modelling and Development Practice , 1994, EWSPT.

[16]  Judy L. Wynekoop,et al.  System Development Methodologies: Unanswered Questions and the Research-Practice Gap , 1993, ICIS.

[17]  J. N. Brinkkemper,et al.  Formalisation of information systems modelling , 1990 .

[18]  Sjaak Brinkkemper,et al.  Method engineering : principles of method construction and tool support : proceedings of the IFIP TC8, WG8.1/8.2 Working Conference on Method Engineering, 26-28 August 1996, Atlanta, USA , 1996 .

[19]  Naveen Prakash,et al.  Building CASE Tools For Methods Represented As Abstract Data Types , 1996, OOIS.

[20]  Carine Souveyet.  Validation des specifications conceptuelles d'un systeme d'information , 1991 .

[21]  J. N. Brinkkemper,et al.  Computer Aided Method Engineering based on existing meta-CASE technology , 1993 .

[22]  Kalle Lyytinen,et al.  MetaEdit - A Flexible Graphical Environment for Methodology Modelling , 1991, CAiSE.

[23]  John Grundy,et al.  Towards an integrated environment for method engineering , 1996 .