2004
DOI: 10.1007/s11741-004-0070-y
|View full text |Cite
|
Sign up to set email alerts
|

Functionality semantics of predicate data flow diagram

Abstract: SOZL (structured methodology + object-oriented methodology + Z language) is a language that attempts to integrate structured method, object-oriented method and formal method. The core of this language is predicate data flow diagram (PDFD). In order to eliminate the ambiguity of predicate data flow diagrams and their associated textual specifications, a formalization of the syntax and semantics of predicate data flow diagrams is necessary. In this paper we use g notation to define an abstract syntax and the rel… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2017
2017
2021
2021

Publication Types

Select...
1
1

Relationship

0
2

Authors

Journals

citations
Cited by 2 publications
(2 citation statements)
references
References 6 publications
0
2
0
Order By: Relevance
“…There have been earlier attempts to formalize DFDs to reduce ambiguity and detect inconsistency and incompleteness (e.g., [27,21,19,9,20,26]), and some works provide formal techniques to support the definition of hierarchical DFDs (e.g., [31,10,27,24]). Representing DFDs in different levels of abstraction does not automatically guarantee consistency between the different abstract models.…”
Section: Related Workmentioning
confidence: 99%
“…There have been earlier attempts to formalize DFDs to reduce ambiguity and detect inconsistency and incompleteness (e.g., [27,21,19,9,20,26]), and some works provide formal techniques to support the definition of hierarchical DFDs (e.g., [31,10,27,24]). Representing DFDs in different levels of abstraction does not automatically guarantee consistency between the different abstract models.…”
Section: Related Workmentioning
confidence: 99%
“…[2] Its advantages are as follows: more errors were found in the early stage of the software life cycle, because in the creation of test model, test designers will find the original software requirements or model some inconsistent or incomplete information can easily achieve requirements tracking, because it is completely based on the model, and the model can be well back, according to the test case can find more defects than the traditional test case generation coverage criteria automatically from the formal model.…”
Section: Introductionmentioning
confidence: 99%