scispace - formally typeset
K

Kenichi Taniguchi

Researcher at Osaka University

Publications -  64
Citations -  527

Kenichi Taniguchi is an academic researcher from Osaka University. The author has contributed to research in topics: Synchronization (computer science) & Formal specification. The author has an hindex of 11, co-authored 64 publications receiving 526 citations.

Papers
More filters
Book ChapterDOI

Generating Test Cases for a Timed I/O Automaton Model

TL;DR: An algorithm to decide efficiently whether a given test sequence is executable is proposed and an algorithm to derive such a function from an executable test sequence automatically using a technique for solving linear programming problems is given.
Journal ArticleDOI

Decision Problems for Multivalued Dependencies in Relational Databases

TL;DR: In this paper, an algorithm is presented for deciding whether or not a multivalued dependency can be derived from sets F of functional dependencies and M ofMultivalued dependencies on a set U of attributes, whose running time is proportional to min.
Book ChapterDOI

Automatic generation of extended UIO sequences for communication protocols in an EFSM model

TL;DR: An automatic test case derivation method for an extended finite state machine model called EFSM/pres where extended UIO sequences called E-UIO sequences are generated.
Journal ArticleDOI

A result on the equivalence problem for deterministicpushdown automata

TL;DR: It is decidable whether or not two deterministic pushdownautomata, one of which is nonsingular (introduced by L. G. Valiant), are equivalent (in the sense that they accept the same languages by empty stack).
Proceedings ArticleDOI

Synthesis of protocol entities specifications from service specifications in a Petri net model with registers

TL;DR: An algorithm which synthesizes a correct protocol entity specification automatically from a service specification in a Petri Net model with Registers called PNR model, which can easily understand what events can be executed in parallel at each protocol entity.