VLDB 2026 Research / reviewers in the wild / expert
Enoch Y. Wang
dblp:64/5000
· DBLP profile ↗
5ranked-venue papers
2as first author
0since 2021 · last 2002
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 3 · 2 first-authorArtificial intelligence and machine learning · 1Systems, architecture and hardware · 1Security and privacy · 1
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Software engineering, system software, and programming languages
2 papers |
Requirements engineering and software design · 70% Programming languages and type systems · 30% | |
| Theoretical computer science
1 paper |
Logic in computer science · 100% |
Topics — the 7 heaviest of 7, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Programming languages and type systems › language semantics
formal semantics |
0.0 | 1 | 2002 | Formalizing and Integrating the Dynamic Model for Object-Oriented Modeling · IEEE Trans. Software Eng. 2002 |
Requirements engineering and software design › software modeling
object-oriented modeling |
0.0 | 1 | 2002 | Formalizing and Integrating the Dynamic Model for Object-Oriented Modeling · IEEE Trans. Software Eng. 2002 |
Logic in computer science
algebraic specification |
0.0 | 1 | 2002 | Formalizing and Integrating the Dynamic Model for Object-Oriented Modeling · IEEE Trans. Software Eng. 2002 |
Logic in computer science › algebraic specification
behavioral specification |
0.0 | 1 | 2002 | Formalizing and Integrating the Dynamic Model for Object-Oriented Modeling · IEEE Trans. Software Eng. 2002 |
Requirements engineering and software design
formal specification |
0.0 | 1 | 1997 | Formalizing and Integrating the Dynamic Model within OMT · ICSE 1997 |
Requirements engineering and software design
model-driven engineering |
0.0 | 1 | 1997 | Formalizing and Integrating the Dynamic Model within OMT · ICSE 1997 |
Requirements engineering and software design › inconsistency management
consistency checking |
0.0 | 1 | 2002 | Formalizing and Integrating the Dynamic Model for Object-Oriented Modeling · IEEE Trans. Software Eng. 2002 |
Methods — techniques the papers use, named apart from their topics
algebraic specification · 0.1LOTOS · 0.1
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2002 | Formalizing and Integrating the Dynamic Model for Object-Oriented ModelingabstractThe Object Modeling Technique (OMT), a commonly used object-oriented development technique, comprises the object, dynamic, and functional models to provide three complementary views that graphically describe different aspects of systems. The lack of a well-defined semantics for the integration of the three models hinders the overall development process, particularly during the design phase. Previously, we formalized the object model in terms of algebraic specifications. However, the algebraic specifications only capture the static, structural aspects of a system. They do not explicitly describe the behavior, which is critical for system development especially for the design phase. It is necessary to formalize the dynamic model in terms of the structural descriptions in order to specify and verify the system behavior using rigorous techniques. This paper presents a well-defined formal model for both the object and dynamic models and their integration. The formal model is described in terms of a well-known specification language, LOTOS. Formalization of the graphical notation enables numerous automated processing and analysis tasks, such as behavior simulation and consistency checks between levels of specifications. Betty H. C. Cheng, Enoch Y. Wang |
IEEE Trans. Software Eng. | 2 |
| 2000 | Enabling Automated Analysis through the Formalization of Object-Oriented Modeling DiagramsabstractAs the impact of and demand for software increases, there is greater need for rigorous software development techniques that can be used by a typical software engineer. In order to integrate informal and formal approaches to software development, we added formal syntax and semantics definitions to existing object-oriented modeling notations. This formalization enables developers to construct object-oriented models of requirements and designs and then automatically generate formal specifications for the diagrams. This paper describes how the resulting diagrams via their specifications can be analyzed using automated techniques to validate behavior through simulation or to check for numerous properties of the diagrams, including inter- and intramodel consistency. Betty H. C. Cheng, Laura A. Campbell, Enoch Y. Wang |
DSN | 3 |
| 2000 | Formalizing the Functional Model within Object-Oriented DesignabstractThe data flow diagram (DFD), originally introduced for structured design purposes, depicts the functions that a system or a module should provide. The objective of a software system is to implement specific functionalities. The function-oriented decomposition strategy of DFDs in the conventional design process for structured design conflicts with the spirit of object-orientation. So far, there is no object-oriented method that has successfully integrated DFDs into the object-oriented development process. In this paper, we demonstrate how DFDs can be modified in order to be integrated into object-oriented development. The Object Modeling Technique (OMT) is used as the context for object-oriented development. In addition, a set of formalization rules are proposed to provide formal semantics for DFDs in order to integrate the functional model with the other two models of OMT, namely, the object and dynamic models, in terms of the underlying formal semantics. Enoch Y. Wang, Betty H. C. Cheng |
Int. J. Softw. Eng. Knowl. Eng. | 1 |
| 1997 | Formalizing and Integrating the Dynamic Model within OMTabstractThe Object Modeling Technique (OMT), a commonly used object-oriented development technique, comprises the object, dynamic, and functional models to provide three complementary views that graphically describe different aspects of systems.The lack of a well-defined semantics for the integration of the three models hinders the overall development process, particularly during the design phase.Previously, we formalized the object model in terms of algebraic specifications.However, the algebraic specifications only capture the static, structural aspects of a system.They do not explicitly describe the behavior, which is critical for system development, especially for the design phase.It is necessary to formalize the dynamic model in terms of the structural descriptions in order to specify and verify the system behavior using rigorous techniques.This paper presents a well-defined formal model for both the object and dynamic models and their integration.The formal model is described in terms of a well-known specification language, LOTOS.Formalization of the graphical notation enables numerous automated processing and analysis tasks, such as behavior simulation and consistency checks between levels of specifications. Enoch Y. Wang, Heather Lipford, Betty H. C. Cheng |
ICSE | 1 |
| 1994 | A Graphical Environment for Formally Developing Object-Oriented SoftwareabstractThis paper describes a graphics-based software development environment that takes advantage of the visual nature of the Object Modeling Technique (OMT) notation and the benefits of formal methods. We have developed a prototype environment, VISUALSPECS, which enables a user to perform object-oriented analysis graphically using the OMT notation. VISUALSPECS generates a formal specification of the object-model, which can be systematically analyzed for completeness and consistency prior to implementation. The formal specifications can be used to guide the formal software. This graphical environment facilitates the development of reliable software using formal methods, enables automated of requirements and design information, and promotes software design reuse based on graphical notations.> Betty H. C. Cheng, Enoch Y. Wang, Robert H. Bourdeau |
ICTAI | 2 |