Formal methods for web services

Chan, K. S. May

doi:10.1145/1810295.1810392

Cited by 3 publications

(4 citation statements)

References 9 publications

(7 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Alas, this project was prematurely aborted and did not produce more than a few brief and vague suggestions. A small classification graph was shown in [18](figure 5: p. 360); unfortunately, that graph does not explain anything beyond what was already known from other literature. In its conclusion, the paper merely stated "that a taxonomy is needed for guiding the combination and usage of formal methods" [18](p. 360).…”

Section: Other Classifications Of Formal Methodsmentioning

confidence: 92%

“…A small classification graph was shown in [18](figure 5: p. 360); unfortunately, that graph does not explain anything beyond what was already known from other literature. In its conclusion, the paper merely stated "that a taxonomy is needed for guiding the combination and usage of formal methods" [18](p. 360). As in our own approach, however, formal concept analysis (FCA) was proposed in [18] as a step towards achieving such classifications.…”

Section: Other Classifications Of Formal Methodsmentioning

confidence: 92%

“…A 'taxonomic approach' to classifying Formal Methods specifically for the application domain of web services was attempted in [18] in 2010. Alas, this project was prematurely aborted and did not produce more than a few brief and vague suggestions.…”

Section: Other Classifications Of Formal Methodsmentioning

confidence: 99%

“…In its conclusion, the paper merely stated "that a taxonomy is needed for guiding the combination and usage of formal methods" [18](p. 360). As in our own approach, however, formal concept analysis (FCA) was proposed in [18] as a step towards achieving such classifications. Like ours, the classification attempt sketched in [18] was also domain-specific, in contrast to most of the other Formal Methods classification attempts, which are unrelated to specific application domains.…”

Section: Other Classifications Of Formal Methodsmentioning

confidence: 99%

See 3 more Smart Citations

On the Construction of Engineering Handbooks

Roggenbach

Grüner²,

Kumar³

et al. 2020

SpringerBriefs in Computer Science

View full text Add to dashboard Cite

Among the earliest engineering handbooks are those of the Greek authors Ktesibios, Philon and Heron on the making of catapults (c. 350 BC). They had formulae that enabled makers to scale the catapult to the ammunition with a view to maximising the range and impact. Their texts address practical technologies and respond to pressing needs of the day, not least the subject of the even earlier handbook of Aineias Tacticus How to survive under siege. Their books are a remarkable testimony to the sophistication of Greek technology, upon which the Romans built so effectively. Writing down of a body of knowledge that can be learned, transmitted and used in the world's work is not new. 1 Today, the world's work is everywhere technical and professional. It is supported by curricula, qualifications, accreditation, charters, and -when particularly new, in development or transformation-by concepts of best practice, communities and regulation. The invasion of software into everything has created many software engineering domains that are self-sustaining with their own bodies of knowledge and practices, e.g., in science, engineering, business, entertainment and transport. The pace and scale of new developments suggest that the formulation and writing down of a body of knowledge and practice that can be used in specialised domains of software engineering is invaluable and necessary.This little book tackles questions about the nature of engineering knowledge and practice through the concept of the practitioners' handbook. The conception of a handbook is demanding as its purpose is to seek and record what knowledge and know how really matters and to make it usable. The authors of this book combine ideas from many quarters and reflect on how to identify and organise 'settled' knowledge into a handbook, in particular regarding our capabilities for making software that is safe, secure, resilient, 1 The catapult is an extraordinary case study when thinking about the nature of engineering knowledge; see T.E. Rihll, The Catapult, Westholme Publishing, 2007; and T.E. Rihll, Technology and Society in the Ancient Greek and Roman Worlds, The American Historical Association and the Society for the History of Technology, 2013. vii viii Foreword etc. The roots, inspiration and focus of the book are in Formal Methods for software engineering. The distilled handbook production approach however applies to engineering in general. Their exemplar is of a domain of software engineering that is coming of age, the design and implementation of software based signalling in railways. The authors' perspective is novel, and their discussion is revealing and stimulating. They offer us an intriguing new way of thinking about contemporary technological knowledge. Swansea, February 2020John V. TuckerThis book is rooted in the philosophy and methodology of engineering. It provides a clear definition of settled knowledge and concise presentation of methodologies for HB development, exemplified in the railway domain. These cover the question of how to identify set...

show abstract

Section: Other Classifications Of Formal Methodsmentioning

confidence: 92%

Section: Other Classifications Of Formal Methodsmentioning

confidence: 92%

Section: Other Classifications Of Formal Methodsmentioning

confidence: 99%

Section: Other Classifications Of Formal Methodsmentioning

confidence: 99%

See 2 more Smart Citations

On the Construction of Engineering Handbooks

Roggenbach

Grüner²,

Kumar³

et al. 2020

SpringerBriefs in Computer Science

View full text Add to dashboard Cite

show abstract

An Assessment of Several Taxonomies of Volunteered Geographic Information

Cooper

Coetzee

Kourie

2012

Discovery of Geospatial Resources

View full text Add to dashboard Cite

User-Generated Content (UGC) in general, and Volunteered Geographical Information (VGI) in particular, are becoming more important as sources for official data bases, such as those used in national Spatial Data Infrastructures (SDIs). Discovering and assessing VGI as suitable geospatial resources for one’s purposes is hence becoming more important, but can be difficult. One way of assessing VGI resources is by classifying them into different types of resources, i.e. a taxonomy of resources. The question is whether such taxonomies can accurately identify suitable VGI resources. We assess five taxonomies both subjectively and using formal concept analysis to determine their discrimination adequacy, that is, how well the taxonomies discriminate between repositories containing UGC in general, or VGI in particular.

show abstract