Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Carlos Puchol

dblp:54/1583 · DBLP profile ↗
← Back
8ranked-venue papers
2as first author
0since 2021 · last 1998
0000-0003-3104-3380ORCID · verified

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 5Theory of computation · 2Applied, interdisciplinary, general and emerging computing · 2 · 2 first-author

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
4 papers
Requirements engineering and software design · 48% Software testing · 38% Program verification · 14%
Computer architecture, parallel and distributed computing, and storage systems
3 papers
Embedded and real-time systems · 73% Electronic design automation · 27%

Topics — the 11 heaviest of 15, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Electronic design automation
design methodology
0.011998
Integrated Design Tools for Hard Real-Time Systems · RTSS 1998
Embedded and real-time systems
real-time system design
0.011998
Integrated Design Tools for Hard Real-Time Systems · RTSS 1998
Software testing › test generation
automated test generation
0.011997
Specification-based Testing of Reactive Software: Tools and Experiments (Experience Report) · ICSE 1997
Software testing
specification-based testing
0.011997
Specification-based Testing of Reactive Software: Tools and Experiments (Experience Report) · ICSE 1997
Requirements engineering and software design › specification
reactive system specification
0.011996
A Framework for Evaluating Specification Methods for Reactive Systems Experience Report · IEEE Trans. Software Eng. 1996
Requirements engineering and software design › specification
specification methods
0.011996
A Framework for Evaluating Specification Methods for Reactive Systems Experience Report · IEEE Trans. Software Eng. 1996
Requirements engineering and software design
formal specification
0.011995
A Framework for Evaluating Specification Methods for Reactive Systems: Experience Report · ICSE 1995
Program verification
safety verification
0.011995
Safety Property Verification of ESTEREL Programs and Applications to Telecommunications Software · CAV 1995
Embedded and real-time systems › real-time programming languages
modechart
0.011995
Compiling Modechart Specifications · RTSS 1995
Embedded and real-time systems
reactive systems
0.011995
A Framework for Evaluating Specification Methods for Reactive Systems: Experience Report · ICSE 1995
Embedded and real-time systems
synchronous programming
0.011995
Compiling Modechart Specifications · RTSS 1995

Methods — techniques the papers use, named apart from their topics

safety verification · 0.0model checking · 0.0resource scheduling · 0.0control/data-flow modeling · 0.0evaluation criteria · 0.0case study · 0.0simulation · 0.0compilation · 0.0
YearPublicationVenuePosition
1998 Integrated Design Tools for Hard Real-Time Systems
abstract
We propose a toolset for designing real-time systems. The toolset is based on a design methodology for real-time systems. The purpose of a design methodology is to provide a set of procedures and guidelines that, with human intervention and interaction, allow designers to systematically obtain implementations of systems that conform precisely to their design specifications. Our methodology is designed for automation. We present the toolset and case study of the design of a simple VCR system. The methodology is based on a formal model and precise descriptions of the components of the system. The underlying model of our methodology is composed of a control level and a data-flow level that, together with a resource scheduler and the application-specific code, make up the system under design.
Carlos Puchol, Aloysius K. Mok
RTSS1
1998 Specification-based testing of reactive software: A case study in technology transfer
Lalita Jategaonkar Jagadeesan, Lawrence G. Votta, Adam A. Porter, Carlos Puchol, J. Christopher Ramming
J. Syst. Softw.4
1997 Specification-based Testing of Reactive Software: Tools and Experiments (Experience Report)
abstract
Testing commercial software is expensive and time consuming.Automated testing methods promise to save a great deal of time and money throughout the software industry.One approach that is well-suited for the reactive systems found in telephone switching systems is specification-based testing.We have built a set of tools to automatically test software applications for violations of safety properties expressed in temporal logic.Our testing system automatically constructs finite state machine oracles corresponding to safety properties, builds test harnesses, and integrates them with the application.The test harness then generates inputs automatically to test the application.We describe a study examining the feasibility of this approach for testing industrial applications.To conduct this study we formally modeled an Automatic Protection Switching system (APS), which is an application common to many telephony systems.We then asked a number of computer science graduate students to develop several versions of the APS and use our tools to test them.We found that the tools are very effective, save significant amounts of human effort (at the expense of machine resources), and are easy to use.We also dis-
Lalita Jategaonkar Jagadeesan, Adam A. Porter, Carlos Puchol, J. Christopher Ramming, Lawrence G. Votta
ICSE3
1996 A Formal Approach to Reactive Systems Software: A Telecommunications Application in ESTEREL
Lalita Jategaonkar Jagadeesan, Carlos Puchol, James Von Olnhausen
Formal Methods Syst. Des.2
1996 A Framework for Evaluating Specification Methods for Reactive Systems Experience Report
abstract
Numerous formal specification methods for reactive systems have been proposed in the literature. Because the significant differences between the methods are hard to determine, choosing the best method for a particular application can be difficult. We have applied several different methods, including Modechart, VFSM, ESTEREL, Basic LOTOS, Z, SDL, and C, to an application problem encountered in the design of software for AT&T's 5ESS telephone switching system. We have developed a set of criteria for evaluating and comparing the different specification methods. We argue that the evaluation of a method must take into account not only academic concerns, but also the maturity of the method, its compatibility with the existing software development process and system execution environment, and its suitability for the chosen application domain.
Mark A. Ardis, John A. Chaves, Lalita Jategaonkar Jagadeesan, Peter Mataga, Carlos Puchol, Mark G. Staskauskas, James Von Olnhausen
IEEE Trans. Software Eng.5
1995 Safety Property Verification of ESTEREL Programs and Applications to Telecommunications Software
Lalita Jategaonkar Jagadeesan, Carlos Puchol, James Von Olnhausen
CAV2
1995 A Framework for Evaluating Specification Methods for Reactive Systems: Experience Report
abstract
Numerous formal specification methods for reactive systems have been proposed in the literature.Because the significant differences bet ween the methods are hard to determine, choosing the best method for a particular application can be difficult.We have applied several different methods, including Modechart, VFSM, ESTEREL, Basic LOTOS, Z, SDL and C, to an application problem encountered in the design of software for AT&T's 5ESS o telephone switching system.We have developed a set of criteria for evaluating and comparing the different specification methods.We argue that the evaluation of a method must take into account not only academic concerns, but also the maturity of the method, its compatibility with the existing software development process and system execution environment, and its suitability for the chosen application domain.
Mark A. Ardis, John A. Chaves, Lalita Jategaonkar Jagadeesan, Peter Mataga, Carlos Puchol, Mark G. Staskauskas, James Von Olnhausen
ICSE5
1995 Compiling Modechart Specifications
abstract
The Modechart specification language is a formalism for the specification of real-time systems. A toolset for specification, analysis and simulation for Modechart specifications exists for supporting the design and construction of real-time systems. This paper introduces a new tool in the toolset: a compiler for a class of Modechart specifications, namely, that of deterministic system specifications, extended by a subclass of the non-deterministic system specifications. The object code that the compiler generates is in ESTEREL, a member of the synchronous family of programming languages for real-time systems. We discuss a broad approach to the implementation of timing specifications, providing a range of implementation options, from the basic time step unrolling of states in ESTEREL, to the use of system timers. The compiler presented herein allows the specifier to obtain a correct implementation of a Modechart program, including timing constraints.
Carlos Puchol, Aloysius K. Mok, Douglas A. Stuart
RTSS1