Building a Body of Knowledge on Model Checking for Software Development

Taguchi, Kenji; Nishihara, Hideaki; Aoki, Toshiaki; Kumeno, Fumihiro; Hayamizu, Koji; Shinozaki, Koichi

doi:10.1109/compsac.2013.129

Cited by 13 publications

(6 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This may eventually lead to the creation of a body of knowledge for modeling and its effective use in practice. Existing work tends to focus on surveying approaches and tools, such as MCBOK, a body of knowledge on model checking for software development [22]; we hope that more fundamental cognitive and process-level issues will also be covered in the future.…”

Section: Discussionmentioning

confidence: 99%

With an Open Mind: How to Write Good Models

Artho¹,

Hayamizu²,

Ramler

et al. 2014

Communications in Computer and Information Science

Self Cite

View full text Add to dashboard Cite

Abstract. Writing effective models for systems and their environment is a challenge. The task involves both mastering the modeling tool and its notation, and faithfully translating all requirements and specifications into a complete model. The former ability can be learned, while the latter one is a continuous challenge requiring experience and tools supporting the visualization and understanding of models. This paper describes our experience with incomplete models, the types of changes that were made later, and the defects that were found with the improved models.

show abstract

Section: Discussionmentioning

confidence: 99%

With an Open Mind: How to Write Good Models

Artho¹,

Hayamizu²,

Ramler

et al. 2014

Communications in Computer and Information Science

Self Cite

View full text Add to dashboard Cite

show abstract

“…Graph theory to build a knowledge engineering method to represent and optimize the learning processes, and its Empirical Validation, is shown in [4]. In [5], the authors used knowledge representation techniques through the design of graphs that enable knowledge based reasoning. In [6], a pattern oriented knowledge model that considers four dimensions of the pattern knowledge space is shown.…”

Section: Previous Research Work On Knowledge Representation Basementioning

confidence: 99%

“…Professional communities have created and used BOK to consolídate their disciplines, standardize practices, and improve processes and warehouse community knowledge. In [5], it is also described the use BOK for both extending skills and career development. Moreover, in [8] BOK is used to créate materials, programs, and curriculums.…”

Section: Theorical Background Of Bokmentioning

confidence: 99%

Knowledge Representation Model for Bodies of Knowledge Based on Design Patterns and Hierarchical Graphs

et al. 2020

View full text Add to dashboard Cite

Bodies of Knowledge (BOK) contain relevant knowledge for several áreas. Knowledge representation for BOK is essential to understand the true context and the possible application of BOK in science. Knowledge can be symbolically represented in many ways, and in this paper graphs and software desing patterns were chosen to develop knowledge representation techniques for BOK. INDEX TERMS Body of Knowledge, design patterns, BOK elements, knowledge engineering, graphs I.

show abstract

“…According to Taguchi (et al), who briefly sketched their ideas on 'building a body of knowledge on model checking for software development' in [81], a body of knowledge (BOK) "is a collection of substantial concepts and skills that represent knowledge of a certain area in engineering/scientific discipline, and ensures its common understanding. A BOK may include technical terms and theoretical concepts as well as recommended practices" [81](pp. 784-785).…”

Section: Other Approaches To Hb Constructionmentioning

confidence: 99%

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

Building a Body of Knowledge on Model Checking for Software Development

Cited by 13 publications

References 11 publications

With an Open Mind: How to Write Good Models

With an Open Mind: How to Write Good Models

Knowledge Representation Model for Bodies of Knowledge Based on Design Patterns and Hierarchical Graphs

On the Construction of Engineering Handbooks

Contact Info

Product

Resources

About