Towards a formal definition of methods Export

@article{citeulike:2902797, abstract = {Abstract\ \ 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.}, author = {Prakash, Naveen}, citeulike-article-id = {2902797}, citeulike-linkout-0 = {http://dx.doi.org/10.1007/BF02802896}, day = {18}, doi = {10.1007/BF02802896}, journal = {Requirements Engineering}, keywords = {definition, method}, month = {March}, number = {1}, pages = {23--50}, posted-at = {2008-06-17 17:18:48}, priority = {0}, title = {Towards a formal definition of methods}, url = {http://dx.doi.org/10.1007/BF02802896}, volume = {2}, year = {1997} }

TY - JOUR ID - citeulike:2902797 L3 - citeulike-article-id:2902797 N2 - Abstract  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. IS - 1 JF - Requirements Engineering EP - 50 TI - Towards a formal definition of methods VL - 2 SP - 23 KW - definition KW - method AU - Prakash, Naveen PY - 1997/03/18/ UR - http://dx.doi.org/10.1007/BF02802896 ER -